Forum OpenACS Q&A: Re: ajaxhelper and its tests
Of course we could opt for including some of the less intrusive ones into specific UI features in OpenACS. I refer to "light" frameworks as JQuery or such.
However we choose, I fear this "marriage" could abruptly be broken on the next change of direction for web technologies, and would of course mean more work from the community to keep pace with framework development. A real example of this is Ajax Filestorage, build on ExtJS 2 if I recall correctly, and now quite useless, until someone finds time and will to rework it.
From a platform point of view I think we should focus on server side, either by producing plain text, markups/XML or JSON from data, as OpenACS is really good at it and leave fancy client side tecnology to the taste and needs of the single.
I wonder. Why is a server-side web app development platform such as OpenACS including /resources/acs-subsite/core.js in acs-core the way it does?
core.js in the generic template has mobile usability issues
It seems like a poor example of how to use js in a dynamic templating environment.
Have you already pointed out where it happens in templates?
packages/openacs-default-theme/lib/plain-master.adp refers to blank-master
If I can boil down what you're saying, it's that trying to be as general as possible isn't really possible, or at least it's the typical thing of generalities having diminishing returns.
So then my (opinion eliciting) question to you becomes, do you think ajaxhelper should just go away? Or, what uses do you see it applied to?
PS to anyone, could you post something about its original purpose?