Thanks, Ahmed, but I've already read it. My point here is that -unless I missed something- Click forces me to at least tweak its configuration file each time I create a new velocity template page. Why would Click need to know each and existing url?! I know, if it's deep in the code, it's not trivial, but it could be worth spending the time to implement this page->pattern generalization. Just my two cents...
Claude Le lundi 04 février 2008 à 20:34 +0100, Ahmed Mohombe a écrit : > > What are the benefits of a pure page oriented architecture? > http://click.sourceforge.net/docs/why-click.html > > But I can recommend to take a look at the entire documentation too( > it is really very good documented) > http://click.sourceforge.net/ > > Ahmed. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
