Forum OpenACS Q&A: Re: ajaxhelper and its tests
Yeah, the things you're saying make sense,,, in any case, I did run 2 of the test files by browsing to them, the tests themselves are located in ajaxhelper/www/tests, so I could run the tests by browsing to /(place ajaxhelper mounted)/tests/test_foo (where there existed /(place ajaxhelper mounted)/tests/test_foo.tcl and .adp). Neither worked, so it was at that point of failure that I also doubted the future of the package, but I've been wrong enough times (i.e., things worked anyway) to let that sway me too far. I also remember when we were playing with yui a few years before yahoo killed it, at that time what was on a few minds was to recraft ajaxhelper, as they felt that while the idea of an "ajax helper" was a good one, things were changing such that the then-current content of ajaxhelper had to be replaced or reworked.
Do you, or does anyone, have recommendations on how to use ajax currently (if not thru the use of ajaxhelper)?
It seems ajaxhelper has an automount set in the package metadata, for /ajax, and it has been declared to be a singleton.
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.
"Do you, or does anyone, have recommendations on how to use ajax currently (if not thru the use of ajaxhelper)?"
Just wanted to point out that ajaxhelper includes some useful icons; That's the only way I use it.
The icons comply with the GPL license --a task that may otherwise be tedious to verify individually.
Some icons use reasonably standardized imagery for UI --and is a larger set than available at: acs-subsite/resources
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?
OK, so would it be in any way useful to factor those out into another package? Was anything like this done already?