On Apr 6, 12:02 pm, Colin Mollenhour <[EMAIL PROTECTED]> wrote: > One important distinction between Prototype and some other frameworks is that > Prototype really focuses on basic functionality. It doesn't include widgets, > just wrappers and utility classes so there isn't much to demo. It's all about > using various parts of prototype along with other generic javascripting to > create your own widgets and functionality. Also, it is server-agnostic so > giving server-side code demos wouldn't make much sense, but these things > would be nice from the respective communities of each server-side platform.
Well the important word of any demo is not "eye candy", the important word is "working". Web tools have the big advantage that anybody can immediately see, what the code achieves. Therefore people expect it and are disappointed if none is found. This is a simple marketing argument which shouldn't be underestimated. Same goes for working sample code, it speeds up to become familiar. Think, anyone looking into a tool the first time is a newbie. > That said, I'll share with you my PHP-Ajax philosophies since I think they > may be useful. I don't use a standard templating library like I probably > should, but what I've done has worked well so far. Thanks a lot O. Wyss --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
