Stéphane, inlined responses here:
On 7/17/07, Stéphane Croisier <[EMAIL PROTECTED]> wrote: > Yes we did some compression of the Zimbra AJAX > lib in the SP1 of Jahia 5.0 as it was quite > memory consuming. This were not creating any > problems under Firefox as FF correctly caches > such file on first load but IE, as usual, as some > problems with such Javascript libs. So IE tends > to reload each time you open a pop-up the full > AJAX lib. Very weird, even with exactly the same URL and no no-cache directive? Never heard about that one. This explained while you rolled back that change then. Guys you really should communicate better on your dev; me and other people though this was simply package mistake while it was actually simply a lack of communication. > moreover IE tends to not correctly > garbage memory allocated to Javascript (look into > google for "IE AJAX Memory leak" and you should find some information) :-( Yeah, I'm aware of that. One of the worst GC implementation spread all over the world, a real shame... > Prototype is currently used in edit mode for the > chat, the process queue, etc... briefly speaking > the edit mode top bar. If you do not use the > default edit mode topbar of Jahia 5.0, you can > remove calls to Prototype. We did that for some projects indeed. You could document that better (how to start a clean project) if you have the resource. >Zimbra is only called > in edit mode when you activate time based > publishing icons. For Prototype we already remove > certain features that we were not using... > Perhaps we can still gain some Ko by compressing > Prototype (thx for the links) but I am not sure > this is something significative in term of performance.... Well, if you need the whole Zimbra stack it won't make any difference, granted. But with Prototype and Scriptaculous only, there is surely a difference when packed (half the page, this happens on the site I'm coding). > In all the case, we plan to move to GWT in the > near future (at least for the edit mode) as GWT > only loads the needed javascripts on a given page > and not the full lib... So if you only need one > Javascript component for such or such web page, > this is a bit overkill to load each time the full > JS library (even compressed). But excepted with > GWT, this is something quite complex to do with > other AJAX libs for the moment.... In the same > time we will work on a better edit mode with more > Web 2.0 oriented features such as drag'n drop of containers, etc... Actually, you can achieve some pretty web2.0 sites with Prototype and scriptaculous alone (see all those Rails sites arround, see the ActiveScaffold feature/code ratio for instance http://demo.activescaffold.com/users). But if you can drop Zimbra for GWT, that certainly a good move in my opinon. Again this is my view, but I don't consider that Zimbra lib is well factored (code duplication with Prototype), neither well documented, neither have a sustainable community... I had to hack in it with Firebug once and it has been one of the worst programming experience ever. Finally, it's only my view but I think Jahia is at a crucial time. On one hand you have quite sustainable marketshare in the CMS, but on the other hand, I see lots of code that seems really hard to refactor in a REST and web2 way in Jahia. So I mean I had doubts Jahia could ever take the web2.0 move. And when you know Google is buying companies such as Jotspot, or if you think about the simplicity of Rails apps, I wasn't so optimistic about the Jahia future. I'm glad you guys want to make the web2.0 move. I strongly believe it's gonna be the minimum standard customers will ask. I think every field should be editable in place without full page reload, much like GMail, cause massive page edition really sucks currently. Still, I fear you kill the code even more by trying at any cost to implement that over the already over bloated JSP/Struts 1 layer. I'm a JRuby on Rails fan and really think this is a more sustainable model. I mean, you could definitely use Struts tiles to achieve a clean modularization of your pages. But still, you'll have no REST API (and just how useful it is to have a free search engine in all the content of your sitesuch as Google Ajax Search (currently Lucene sucks for each paginated container cause it's not restful), the REST contribution web services...) you would also miss an effective way to factor ajax and non ajax code. Integrating that existing layer with GWT might be very entropic too. If I could, I would reinject your Spring layers and Hibernate models in a JRuby on Rails app such as decsribded here: http://mysterycoder.blogspot.com/2007/06/spring-jruby.html and similar thing for Struts progressive migration: http://www.newspiritcompany.com/railsandspringmvc/ I would drop all the JSP and View/Controller layer at the profit of Rails which I consider much better designed to achieve a Restfull and web2 model. Just think how ERB (Rails template system) integrate better than JSP or JSF when it comes to pass customized anonymous function to the Javascript libs such as Prototype. ERB makes it a simple hash parametrization while JSP or JSF will bloat it all in a static non versatile taglib. PS: and also: I feel like the data model might be more effective if it were smaller with some XML blobs at strategic places instead of so many table associations. But I might be wrong, just an intuition. Regards and good luck with your CMS. Raphaël Valyi. _______________________________________________ dev_list mailing list [email protected] http://lists.jahia.org/cgi-bin/mailman/listinfo/dev_list
