On Wednesday 17 January 2007 06:38, Colin Mollenhour wrote:
Sounds like maybe IPE isn't for you. First of all, I prefer
generating forms client-side using helpful tools such as
Builder.node, and more specialized wrappers that I write myself, and
leaving the server to handle only data. I think it is a much cleaner
design philosophy, and assuming your site is one that will take
advantage of user cache, is much quicker and less demanding of your
server and makes debugging a hell of a lot easier.
This approach doesn't fit well in my case, I think. For an ajax-heavy
app it surely is a good option to move lots of stuff to the client and
essentially implement (or use Dojo, YUI, ...) a client-side UI
framework. My app is more mundane HTML, spiced-up with some ajax where
useful. The hierarchical stuff is only for administration and there are
no performance concerns at all.
I do have a skill concern, however. I'll be working on this app for
about another week. I may get another contract in the future, but
that's not settled. While I'm not squirmish touching JavaScript, the
other people who will have to live with the codebase further on, are
only somewhat familiar with Ruby/Rails. A likely scenario is that one
of the hierarchical nodes gets some more attributes. In that case, it
would be very easy to add suitable input elements to a form represented
by an RHTML view.
So, what I want is client-side code for these semi-separate things.
(1) An IPE that adds editability to displayed information by means of a
form that it retrieves from the server.
(2) An IPE that can create new objects.
(3) An IPE + some more code that allows editing, adding, deleting of
items in nested ULs.
(1) I already have, by deriving from and mutilating the scriptaculous
Ajax.IPE. (2) works too, I think. It is (3) that's causing me troubles.
I realize that a major cause of them is that I stick very closely to
the HTML. The entire tree is not represented anywhere, I have just
affixed my IPEs to the individual items and as much as they can they do
their stuff locally. If I can't get this to work at all, my best way
out is to forgo the ajax entirely and gracefully degrade from the
start.
Michael
--
Michael Schuerig
mailto:[EMAIL PROTECTED]
http://www.schuerig.de/michael/
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby on
Rails: Spinoffs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---
