I have started to use jsObjects in pnAjax, it seems to be a ideal cadidate for all the utility functions i dont have implemented in the util functions.
You can find some documentaion regarding jsObjects here:
http://services.jonandnic.com/jsObjects/
As far as my own reserch goes, its a good balance inbetween a good lib, license and some fixes that have to be done.
LOL, itgets worse every day. i really cant stand it anymore. People re-use the word ajax for everything:
- its web 2.0
- its used for funky Javascript popups
- its used for form validation
- oo javascritpt
- inline html editors
Sorry folks, this is not true: its as simple as loading data from a server. Maybe youre to shimpy to be true in one fact: all of us demonized the eveil javascript the last years, and now when we need it to do the ajax thingie: we need to get a new word or weell be the ones to confess that we wre wrong.
Ther will be the day when someone will use ajax for a cleaner and we all can uy this at a local store ..
sorry must go .. to real life, the pizza boy is ringing ;)
i have added some stuff ....
Grid Widget
The grid will help to show and edit tabular data. Its programmed by Uwe Pries in finest pure javascript code.
Finalize Handler
The finalize handler can be used to execute n pieces of Javascript callbacks on the end of the Request. Nice feature to fill your data in the grid widget.
function foo() {
var pn_ajax = init_ajax();
pn_ajax.add_pnmodapifunc('pnAjax', 'user', 'test', {}, function(ret){
data.push(ret);
});
pn_ajax.add_pnmodapifunc('pnAjax', 'user', 'test', {}, function(ret){
data.push(ret);
});
var cb_fin = function() {
var cols = {
PLZ: { label: "PLZ", size: 5, maxlength: 5 },
NAME: { label: "Name", size: 30 },
LAND: { label: "Land", size: 30 }
};
grid.build(
document,
"grid",
cols,
data
);
grid.attach_to(document.getElementById("dg"));
}
pn_ajax.add_on_finalize(cb_fin);
pn_ajax.execute();
}
All the naming conventions may change while development .. but this one shows in which direction the whole thing will go.
I have started to work on a complete Ajax Framework for Postnuke. Sounds like a stupid idea on first hand, there are dozens only for php and a lot of will emerge til i am finished. The point on this one lies on one hand in the technical abilities of the frameworks around and on the other hand that there is need for tools that fit into postnuke 100%.
I work a year on a solution in my company that is used in XUL / Javascript and i hope to get some of the foo to the real world. This is no copy attempt but i think some of the mechanisms will be reused, since they make sense and no other framework has them.
Client
The client willbe implemented in pure Javascript using Jses prototyping and inheritance (as far as you can call it inheritance)
Server
The Server will be small Component implemented in Postnuke Core Api functions.
Helper API
The Helper API will provide a Tabular Grid to edit list based data and a Tree API that is still missing in oldstyle html.
Page API
The Page API is used as a glue inbetween the serverside/ajax code and the helper api. Mainly its a binding for the dom events.
So far, a lot to do .. and this blog will be my new hangout on this topic.