pnajax with json further developments
With a little help from e-voc i made the json serializer work.
No well go soon to be async and the all will be much better.
Besides i started work hard on the integration of jsobjects. I guess ill have to rewrite some of the code to make it work w.o. evil eval.
The grid example is still simple, dropping notices etc .. but the api is growing. I dont have this much time, bus as ill make pnAjax a important component on the pncommerce project, reusing the grid and the tree for basic gui layout, it will get a lot of commits anyway.
The big Ajax discussion has come in place to postnuke. Again it looks like writing down things, instead of write code in the first blink of an idea is considered to be a bad thing there. Markwest requested a unified ajax Project for the postnukeworld, but i guess that will not take place .. why ?
The Approaches are too different
Chestnuts Ajax example is
- not using serialization
- relies on handcoded servers
- has no framework components
- has no event model catching errors from the serverside
Frank Schummertz pnForum Stuff:
- is using AHAH data (returning HTML instead of XML or serialized data
- relies on handcoded servers
- has no framework components
- has no event model catching errors from the serverside
pnAjax
- uses json data serialization
- has a tested gui kit / framework
- relies on no handcoded server to use ajax funcs on the client
- has a event model catching errors from the serverside
Anyway, i am really opposing doing 3 times the same work, but as i see from the mailing list postings, there is a request for a lot of functionality that is already in pnAJax. So i guess it was worth the time to sit down and thing of a framework that can totally integrate with postnuke instead of building stuff on top, that might be sexy, but is ugly code.
You migth call me a thread , but if there is no movement twoards a performant approach for the data stuff and nothing more that, hey, integrate scriptacolous into postnuke, Ill not be the one to jump in and make the lead on such a project .. ill guess it takes a year to explain to others what they need to develop .... pnAjax is rather complex on the code side of the project development ... but easy to use for the final developer, implementing his own apps with just a buch of loc.
No well go soon to be async and the all will be much better.
Besides i started work hard on the integration of jsobjects. I guess ill have to rewrite some of the code to make it work w.o. evil eval.
The grid example is still simple, dropping notices etc .. but the api is growing. I dont have this much time, bus as ill make pnAjax a important component on the pncommerce project, reusing the grid and the tree for basic gui layout, it will get a lot of commits anyway.
The big Ajax discussion has come in place to postnuke. Again it looks like writing down things, instead of write code in the first blink of an idea is considered to be a bad thing there. Markwest requested a unified ajax Project for the postnukeworld, but i guess that will not take place .. why ?
The Approaches are too different
Chestnuts Ajax example is
- not using serialization
- relies on handcoded servers
- has no framework components
- has no event model catching errors from the serverside
Frank Schummertz pnForum Stuff:
- is using AHAH data (returning HTML instead of XML or serialized data
- relies on handcoded servers
- has no framework components
- has no event model catching errors from the serverside
pnAjax
- uses json data serialization
- has a tested gui kit / framework
- relies on no handcoded server to use ajax funcs on the client
- has a event model catching errors from the serverside
Anyway, i am really opposing doing 3 times the same work, but as i see from the mailing list postings, there is a request for a lot of functionality that is already in pnAJax. So i guess it was worth the time to sit down and thing of a framework that can totally integrate with postnuke instead of building stuff on top, that might be sexy, but is ugly code.
You migth call me a thread , but if there is no movement twoards a performant approach for the data stuff and nothing more that, hey, integrate scriptacolous into postnuke, Ill not be the one to jump in and make the lead on such a project .. ill guess it takes a year to explain to others what they need to develop .... pnAjax is rather complex on the code side of the project development ... but easy to use for the final developer, implementing his own apps with just a buch of loc.
Comments
Frank Schummertz
@ 23.02.2006 18:19 CESTMy Ajax implementation is work-in-progress and still under development. But its not from a well-known professionell programmer so it must be bad....
At least it works... and it does not need a "framework" component because PostNuke is my framework.
And its using JSON too now for data exchange and it catches errors and yes, it returns HTML where it is appropriate in form of pnRendered templates...
So whats the point?
Frank Chestnut
@ 23.02.2006 18:29 CEST
Strange that my tiny little experiments (that are mostly for fun and learning my way into javascript that is probably the language I hate the most) are considered as an "approach".
I never said that and to the contrary, I thought I said loud enough that it wasn't to be considered as an "approach".
Viva the misunderstanding...
On the real subject, looking for the "easy to use" pnAjax...
FC !
Strange that my tiny little experiments (that are mostly for fun and learning my way into javascript that is probably the language I hate the most) are considered as an "approach".
I never said that and to the contrary, I thought I said loud enough that it wasn't to be considered as an "approach".
Viva the misunderstanding...
On the real subject, looking for the "easy to use" pnAjax...
FC !
Sebs
@ 24.02.2006 17:07 CEST
Yes, the system was good 0 minutes setup and someone else is the one who needs to admin it. You come to a point where youre not this evangelistic about stuff like that.
And when you take a closer look to the system, youll see there is a lot we at postnuke can learn from it ;)
Yes, the system was good 0 minutes setup and someone else is the one who needs to admin it. You come to a point where youre not this evangelistic about stuff like that.
And when you take a closer look to the system, youll see there is a lot we at postnuke can learn from it ;)
No new comments allowed (anymore) on this post.