Ben Alex wrote:
> I approach the client design as if it were a
> rich client and not a web view. That means DTOs instead of
> domain objects (DO), and a services layer facade to help with
> DTO to DO mapping.
FWIW, I found that the same approach works well with PHP. I started
down a path of trying to get PHP to generate the QX code. This didn't
work for a lot of reasons.
- many of the properties of the QX objects are not available until
the JavaScript is executing, so your PHP is creating objects that
it can't fully inspect
- adding event handlers gets ugly, as you are mixing little snippets
of JavaScript in with the server-side language. This is not worth
the headache.
Now I build large chunks of my UI in JavaScript files and use the PHP
to check credentials and control what portions of the UI are delivered.
I suppose you could just deliver the entire UI and use JavaScript code
to control access to the different parts of the UI, but it seems that
would be vulnerable to JavaScript hacks.
Communications with the server are handled via Sajax, using JSON for
passing objects between client and server.
Jason Priebe
CBC New Media
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
_______________________________________________
Qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
