James, IMO, and I'm sorry to say this, JavascriptComponent now a days is no longer required. Now a days, with libs like jQuery, we rarely(web developers) need to write browser specific javascript, and with IE being more a more compliant with standards, the need for this is diminishing everyday.
Another point is that, my intent is to standardise only on JQuery. so no need to support prototype or scriptaculous. Regarding referencing external libs, is it really a time saver to include script tags for me? Specially now that there are 3 CDNs to pick from - http://docs.jquery.com/Downloading_jQuery#CDN_Hosted_jQuery Anyway this is just my 2 cents Cheers John On Oct 29, 12:40 pm, James Curran <[email protected]> wrote: > The problem is while they are mutually exclusive (i.e., you have to use one > or the other, not both), they presently don't overlap in functionality. > Further, I believe I could added the combine/compress functionality within > it's current syntax, while I don't believe I could add the features of the > Javascript VC to the CombineJS VC and maintain anything close to it's > syntax. > > Truth, > James > > On Thu, Oct 28, 2010 at 8:41 PM, John Simons > <[email protected]>wrote: > > > > > > > > > No point having 2 components that do identical things. > > In my opinion since CombineJSViewComponent is already part of MR > > framework, we should add + improve this one + document it in stw. -- You received this message because you are subscribed to the Google Groups "Castle Project Users" 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/castle-project-users?hl=en.
