here is the correct link to you own demo ;-)

On Mon, Jan 28, 2013 at 7:00 PM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

Paul, I changed the HTML template to display a check box in the list, to
be consistent with the check box in the detail panel.

Under this design pattern the key to the record is embedded in the table
row (the <tr> tag). The key is asynchronously sent to the server by several
possible events (onClick, arrowDown, arrowUp, Home, End, etc.). Hence, the
detail panel is updated asynchronously as the user navigates the list,
using the mouse or keyboard.

Required fields are validated first using JavaScript, and validated again
on the server, using RPG, with appropriate error messages.

- Nathan

From: Paul Holm <pholm@xxxxxxxxxxxxxxxxx>
To: web400@xxxxxxxxxxxx
Sent: Monday, January 28, 2013 10:00 AM
Subject: Re: [WEB400] DB Maintenance Design Patterns


I like the presumed AJAX? to update the detail section of the page. I
assume the pattern is to display a list of records and a detail section,
and then onCLICK use ajax to go get the full record and display it in
the detail section? How do you know what complete record to get
onCLICK? Do you use the icecream key field?

A few questions:
1. How can we handle required fields? For example, I added
"strawberry" but failed to enter the other fields. We need a easy way
to enforce "required fields"?

2. The available field seems to be a 1/0 boolean field. It's rendered
as a checkbox on detail but not on the subfile?

Thanks, Paul Holm
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].