Am Dienstag, 15. Mai 2007 schrieb Philipp Bracher: > > Should we use FreeMarker for all Dialogs and Controls instead of > > that clumsy > > HTML inside the Java classes as DialogMultiSelect is already doing > > for some > > HTML? > > Yes we should! Till now we didn't go for it because we will re- > implement the dialogs/controls completely. But since we are waiting > for that step to get happen since a long time we can start extracting > the html code. Feel free to process them stepwise. This will > facilitate the process of rewriting anyway.
I'm no longer sure if it makes sense to extract the HTML. If we keep the custom controls and dialogs it would make sense, but if we drop it in favour of a standardized (JEE) component-based framework the work is quite useless. After researching the last day to find out which possibilities are there, I came to the conclusion that JSF comes close to what we need. The draft for 2.0 (http://jcp.org/en/jsr/detail?id=314) looks promising and tries to eliminate a lot of known disadvantages of prior versions. Which plans to reimplement the dialogs and controls do you have at Magnolia? ... Ok, I searched Jira after writing that and found MAGNOLIA-588 where you (Philipp) stated: "we use JSF!". Is there something in svn yet? Did you marry JSF and FreeMarker? Can we wait until Q1/Q2 2008 when JSF 2.0 should be ready? O. ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/docs/en/editor/stayupdated.html ----------------------------------------------------------------
