Re: DB Maintenance Design Patterns

[Henrik Rützou <hr@xxxxxxxxxxxx>]

Nathan,

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

http://www.radile.com/rdweb/temp/icecream.html


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.
>
> http://www.onepoint.com/rdweb/temp/icecream.html
>
>
> 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
>
> Nathan,
>
> 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
> 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.