Forum OpenACS Q&A: Re: ]project-open[: Current status about AJAX, Sencha and AOLserver

Hey very nice. Seems like similar experiences as we've been doing our server-calls RESTful style too, and came up with tricks for sencha performance (gzipping/concatenation/minification, lazy rendering, buffered loading), and still supporting several openacs-based apps with newer interfaces.

One interesting thing I did reduced large amounts of reliance on tcl for an 'excel-like' interface that required all of the logic in the browser (for offline support). It was for what-if scenarios in the human resources work was write my own library for the client and re-use it on the backend in a plv8 function (javascript inside postgres). Openacs did nothing except handle the request and call the database function (after error checking, permissions). It allowed us just to 'replay' the front end actions in the database to keep the server in sync.

It would be interesting to have a chat one day and share techniques, especially relating to sencha, and patterns for highly dynamic apps. We could share a few things we've done that might have crossover to your apps, and vise versa (your ticket tracking app sounds cool).

Taras

Hi Taras,

gzipping/...

Rrright, we've also added gzipping and a way to select the columns returned in object lists in order to reduce data volume, but I'm interested to learn about the other ones.

I'll send you a private message in order to schedule a call.

what-if scenarios

_Very_ interesting, we will have to work with what-if scenarios for project resource planning at some point in the future...

share

Here is a quick way to look at our Sencha client-side stuff. It's a complete ticket tracker/helpdesk system written in Sencha:
cvs -d :pserver:mailto:anonymous@cvs.project-open.net:/home/cvsroot checkout intranet-sencha-ticket-tracker

Cheers,
Frank