Re: The "Presentation" Layer

Further to my previous reply.

IceBreak has an a feature that allows you cache the SQL query on the server
and return the result page by page.

SQL_Execute_CallBack(sqlstr:start:limit:%PADDR(iRenderJson));

Variable sqlstr contains you query - eg:

sqlstr = 'Select PBORDN,PBORDL,PBORDQ,PBJNO,PBDESC,PBQRCV,' +
'PBDELD,PBGRND,PASUPP,PAORDD,PBLSTS,' +
'(PBORDQ - PBQRCV) As OUTSTANDING,' +
'(PASUPP Concat ' + QUOTE + ':- ' + QUOTE +
' Concat XPNAME) As SUPPLIER ' +
'From PUR002P Left Outer Join PUR001P On ' +
'PBORDN = PAORDN Left Outer Join XPUR016L1 On ' +
'PASUPP = XPCCDE Where PBJNO = ' + %CHAR(jobno) +
' Order By PBORDN,PBORDL';

The "start" specifies which record to start at and "limit" is the page size.
The procedure, in this case, iRenderJson, handles each cell in the result
set and sends data back to the server. In this example Json, but it could be
XML.

An Ext Paging Grid with IceBreak using Sort, Search for values, etc is
really quite simple.

Syd


-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On
Behalf Of Aaron Bartell
Sent: 18 July 2008 20:05
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] The "Presentation" Layer

Just to comment on things like the ExtJS grid...

... the thing that drives me nuts the most is that out of the box most of
these grid controls don't promote the use of paging. For example, if you
have 100,000 records in a file then the user should only be returned the
actual number of records they are viewing (or you could buffer a page before
and a page after if you wanted to).

What type of paging capabilities does Ext JS provide to "go back to the
well" for the next pages worth of data vs. loading the entire dataset in the
browser all at once?

Aaron Bartell
http://mowyourlawn.com

On Fri, Jul 18, 2008 at 1:45 PM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

From: Walden H. Leverich
The page comes up and I see a grid, but nothing in the grid.
Is this correct?

Hmmm, I don't know what happened. Maybe the result set was too large for
my slow modem. I don't know. I changed the cursor filter to generate a
smaller result set. Try again. Be patient for the response. This is my
first attempt at communicating with an Ext JS client.

Regarding losing the ability to bookmark a rich-client interface, that's
fine for the type of applications I deploy, but the point is well taken.

Nathan.



--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.