Oh, well I don't necessarily agree with that. You see, your proposed solution may work well for your implementation, but I prefer to use the shorter syntaxes rather than having to qualify everything all the time. Your solution is still, when it comes down to it, just another imperfect workaround (like mine). It's still not a true namespace as Michael Peters stated. When the page loads, everything is at the same level. All you're really doing is a different version of what I'm doing; renaming functions that are in conflict. You're just taking a broader approach whereas I'm going to the granular function level...
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin Marinschek Sent: Tuesday, January 03, 2006 1:37 PM To: Michael Peters Cc: [email protected] Subject: Re: [Rails-spinoffs] Status of Prototype Ok, if you guys agree, then I would really think that we should try to get this into prototype. Why should each and every user necessarily do this if it could fixed by the framework itself? regards, Martin On 1/3/06, Michael Peters <[EMAIL PROTECTED]> wrote: > > > Ryan Gahl wrote: > > but the point is that some level of manual upkeep is > > almost always going to be required in this new age of web development > > until such a day as a good type-safe (and possibly compiled) javascript > > VM is supplied to us by the powers that be. > > You don't need type safety or compilation to achieve what the OP is after. You > just need real namespaces. > > -- > Michael Peters > Developer > Plus Three, LP > > -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces _______________________________________________ Rails-spinoffs mailing list [email protected] http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs The information transmitted in this electronic mail is intended only for the person or entity to which it is addressed and may contain confidential, proprietary, and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from all computers. _______________________________________________ Rails-spinoffs mailing list [email protected] http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
