The "problem" is that it's a fundamentally different way of dealing with Metadata. Metaobjects is much more pro-active, whereas the Metadata plugin is passive in nature. That's not a bad thing, it's just different.
For example, with the Metaobjects plugin you can setup rules to have data bound to certain selectors, whereas in the Metadata plugin you can only attach JSON-formatted data to individual elements. And just to reply to one point on the Metaobjects site: "The 'element content' method is easily used with a SCRIPT element, because its content stays automatically hidden, but it can clash with your regular scripts." That is incorrect. You're supposed to use a script tag with a type of "application/json" - the official mimetype for JSON data. Browsers ignore script tags that completely, it is not executed in any way. It is true that the element is not cleaned up after itself, but that should be remedied - and it's an easy fix. The <object>/<param> style syntax could be included straight into the Metadata plugin, but I wouldn't want to undermine how the Metaobjects plugin works (while, at the same time, not providing the exact capabilities of the Metaobject plugin). With that being said - it's up to Andrea, while Metaobjects certainly won't replace the Metadata plugin, they could certainly be merged - it would simply require a little more work, but it may be worth it. It should also be noted that the Metaobjects plugin is, fundamentally, faster than the Metadata plugin as it can quickly search through a DOM structure for a specific pattern, rather than trying to load the information on the fly. (Granted this technique could be introduced into the Metadata plugin for the 'elem' style of Metadata, but I'd hate to duplicate efforts in this matter.) --John On 3/1/07, Erik Beeson <[EMAIL PROTECTED]> wrote: > I'm curious to hear other people's thoughts on this approach. If it's > a sound idea, why isn't it part of the official metadata plugin? > > --Erik > > > On 3/1/07, Andrea Ercolino <[EMAIL PROTECTED]> wrote: > > > > I was wondering if anyone is using my > > http://www.mondotondo.com/aercolino/noteslog/?page_id=105 Metaobjects plugin > > as a replacement for the metadata plugin. > > > > It's now at version 1.2 and I'm really proud of this simple tool. > > > > The best features of Metaobjects are: > > -- valid XHTML mark-up > > -- auto clean up by default > > -- attach data to properties of dom elements directly > > -- add any writable property or a brand new one > > -- each value is evaluated and then the result is assigned > > -- data can be any javascript expression: function declarations and calls > > too > > -- each metaobject can be further customized by a metaparam > > -- target is metaobject's parent by default, but can be changed to any > > jquery selector (sort of one metaobject to rule them all ;-) > > -- default behavior is customizable > > -- user decides what metaobjects are processed and when to do it > > > > > > -- > > View this message in context: > > http://www.nabble.com/metadata-by-means-of-metaobjects-tf3327825.html#a9252509 > > Sent from the JQuery mailing list archive at Nabble.com. > > > > > > _______________________________________________ > > jQuery mailing list > > discuss@jquery.com > > http://jquery.com/discuss/ > > > > _______________________________________________ > jQuery mailing list > discuss@jquery.com > http://jquery.com/discuss/ > _______________________________________________ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
