#sensiblledev

After about 2 and a half years of using Tapestry 5.3, T5.4 was starting to take shape.  It has a brand new JavaScript framework based on JQuery, Bootstrap and requireJS.  I figured that it was a good direction to be headed, so I started a pilot project of converting my code into 5.4. Good news was that there were not much Java code changes required, well, it was good and bad because all the same issues in Tapestry-IOC were still present in 5.4.  At least it was Java 8 compatible. In order to take advantage on the new JS framework, all infrastructure and patches that I made to make T5.3 usable had to be completely rewritten in T5.4, which was not a simple task.  After spending about a month researching and updating all components to T5.4 (again undocumented) JS infrastructure, I finally got things to work, kind of. Partly because of Bootstrap layout engine in T5.4, all the pages looked wrong.  I tried to figure something out to generically fix the layout, but it turned out what I had to do is manually fix up all the pages.  BeanEditor and company had particular layout issues, and every on of those looked wrong with no way to fix it.  Suggestions I was getting from Tapestry community was to stop using BeanEditor.