Hi Ruben,
On Feb 5, 2009, at 7:48 PM, Ruben Reusser wrote:
I retrieved the samples and installed the module. If I am seeing this right, the jsp samples are now limited to one template and two paragraphs.
As Philipp said, these are developer-oriented samples, i.e how-to's. At least that's what we tried to do. In the sample module, the freemarker samples are not more numerous nor advanced than the jsp ones. It's not like the previous samples were usable in real life, is it ?
This seems very limited, giving the fact that the basic templating (the sonic templating) site that should be used to create your own web site (according to the release notes) is fully done in ftl.
We had to do a choice, and as said before, we do believe freemarker is superior in many ways. But if *you* feel more comfortable with JSPs and want to use the standard templating kit paragraphs and templates, you still can.
Now we have a clear difference: the samples modules shows (or tries to show) developers how to build their own templates with a very limited set of examples to look at, and a focus on features. It should be fairly obvious that these are not meant for real life usage (again, that was the original goal, feel free to disagree and help make that clearer). The standard templating kit on the other hand is a turnkey solution that should enable you to build decent websites without a developer/templater. You may even use the default theme we provide, whereas I don't believe any one would have dared putting a website out there with the look and feel of the 3.x generation of samples.
Why would somebody in their right mind use jsp with magnolia and why do you expect a business to mix jsp and freemarker? That could be an awful business decision since you now need people to understand two technologies and not one.
It could indeed; it's only one extra possibility.
Adding new poeple with freemarker knowledge probably is not easy either since it is not a very commonly used technology (dice lists currently 17 positions that mention freemarker in the job description). It really feels to me that magnolia is abandoning JSP as the primary templating language and pushing freemarker. As mentioned before, I am not sure if that is a good message to send to the outside world.
That is simply not true. As I've said in my previous mail, "you still have the choice, we still support jsp, and you can still use any other templating mechanism you fancy by using custom renderers".
I don't personally see what there is to freak out about. We add flexibility and choices. That the message might not have been clear enough is possible, and I'm sure Boris will read this, but reading your mails, what I feel instead is simply fear of change - so I hope I calmed those fears down a little ;)
Cheers, -g ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
