On Sunday 14 February 2010 00:52:00 steve oliver wrote: > I've been following this for a while, and it took me a bit to see both sides. > > Whatever the project ends up doing in the long run with the web interface(s), > the first thing that should be done even if fproxy doesn't change at all, is > to move the HTML out of the java code, and start using a templating engine of > some kind. HTML, while intended for structure, is a presentational system for > displaying data, it should not be mixed in with backend code that actually > generates that data.
This has been suggested in the past. Generally it hasn't happened because: - It would significantly increase complexity in the short run. - It would reduce performance. - It would increase the size of the download by approx 500K. It may well be that all of these reasons are now obsolete. Our download is over 9MB already, so the last is irrelevant. Our HTMLNode stuff is not without overhead, so the other two may be invalid too. > > I can't speak for the Java templating engines available (though i will look > around to get a feel for what is available), but the ones I've used with > Python use separate template files on disk. This would make it much easier > for interface designers to try new layouts and add functionality to the > interface(s) without needing to compile the java code each time (or at all). Pupok is a capable Java coder and the original plan was to use GWT. So there will definitely be Java code involved, one way or the other. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 835 bytes Desc: This is a digitally signed message part. URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20100215/87f2f809/attachment.pgp>
