rgoff
09-25-2006, 12:10 AM
I'm a web designer/programmer that didn't survive the crash, but I still dabble a bit. I'm going a bit cross-eyed looking at the examples and documentation, and I wonder if someone would give me some high-level suggestions for getting started in my application. I don't want anyone to write my code for me, or read the docs for me, just give me a little focus in this sea of information I find myself in. Something like "use this object to do this, then approach this in this manner..."
I'm starting an application that I want to design with AJAX principles - smaller amounts of data round-tripping to the server more frequently, usually transparent to the user. As part of the configuration, there will be SQL commands stored that server-side scripts use to fetch predefined datasets. Each stored SQL command will have a name for reference and a set of parameters that each have a name, datatype, and default value. Here's the problem statement: develop a page that displays command names, the associated strings, and the set of parameters with their attributes. Allow editing, deleting, and adding. Here's a mock-up page:
http://magpierising.com/QueryConfigProto.png
With traditional techniques, I'd use the recordset in the server script to write the HTML code for tables containing the information. I'd have buttons or checkboxes for deleting, and maybe a blank input form for adding. To edit, I'd probably select a table row and either reload the page with the data populated in an input form or open a new page for the form. How would you approach this with YUI and YUI.ext? Thanks for your time.
(As an aside, if anyone knows where I can learn how to reliably pass parameters to a Jet query in ASP/ADO, I'd be grateful if you'd tell me. I've spent the last two days and various amounts of time in the last two years trying to figure this out, and none of the techniques I've found work for me. This is the reason for the stored SQL command kludge.)
I'm starting an application that I want to design with AJAX principles - smaller amounts of data round-tripping to the server more frequently, usually transparent to the user. As part of the configuration, there will be SQL commands stored that server-side scripts use to fetch predefined datasets. Each stored SQL command will have a name for reference and a set of parameters that each have a name, datatype, and default value. Here's the problem statement: develop a page that displays command names, the associated strings, and the set of parameters with their attributes. Allow editing, deleting, and adding. Here's a mock-up page:
http://magpierising.com/QueryConfigProto.png
With traditional techniques, I'd use the recordset in the server script to write the HTML code for tables containing the information. I'd have buttons or checkboxes for deleting, and maybe a blank input form for adding. To edit, I'd probably select a table row and either reload the page with the data populated in an input form or open a new page for the form. How would you approach this with YUI and YUI.ext? Thanks for your time.
(As an aside, if anyone knows where I can learn how to reliably pass parameters to a Jet query in ASP/ADO, I'd be grateful if you'd tell me. I've spent the last two days and various amounts of time in the last two years trying to figure this out, and none of the techniques I've found work for me. This is the reason for the stored SQL command kludge.)