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. 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). On Feb 13, 2010, at 4:42 PM, Ian Clarke wrote: > On Sat, Feb 13, 2010 at 11:06 AM, Evan Daniel <[email protected]> wrote: > > Actually, you don't know that any of them would disagree with me. Find me a > > designer who says they can redesign an entire website without touching the > > HTML - I bet you can't. > > I already did, and provided a link! The point of the web site is, > quite precisely, that you can do CSS based design. > > You are confusing graphic design with user interface design. CSS lets you do > a lot with the graphic design, but very little with the actual functionality > of the user interface. > > Ian. > > -- > Ian Clarke > CEO, SenseArray > Email: [email protected] > Ph: +1 512 422 3588 > _______________________________________________ > Devl mailing list > [email protected] > http://osprey.vm.bytemark.co.uk/cgi-bin/mailman/listinfo/devl
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Devl mailing list [email protected] http://osprey.vm.bytemark.co.uk/cgi-bin/mailman/listinfo/devl
