The speed difference between the "script tag technique" and the
"object/param technique" is negligible (or, will be, once I fix the
"script tag technique" in the Metadata plugin to be more pro-active).
The primary difference between those two techniques and the
"classname" and "data attribute" tec
> 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.
I'm unclear about the performance difference between the tw
I just got to version 1.3 thanks to the feedback generated by this thread.
Daniel Wachsstock sent me his shorter version, which I could easily
integrate.
I fixed some bugs (he cut too much), but it's ok now.
I updated the Metaobjects manual with your words, John :-)
I must admit that I didn't g
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
I read thru the site and I must admit that I not exactly sure of the
benefit. Are there real work examples? Can you explain the benefits?
Thanks,
--
Benjamin Sterling
http://www.KenzoMedia.com
http://www.KenzoHosting.com
___
jQuery mailing list
discu
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=10
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 cl
