Hi Danielo, > Why would there be (more) collisions than with using jQuery tiddlers? >> > > What are jQuery tiddlers? >
A tiddler of type *application/javascript* containing ...jQuery, rather than loading it via *<script>*. And sorry for my the recent flood of typos... pulling what's left of my hair out. ^^ What do you expect to collide with what? >> > > Not with names, but maybe accessing and modifying dom nodes. TW has its > own way to modify the DOM and jQuery has a different one. > To properly make use of jQuery in light of Tiddlywiki internals seems a different issue than ho to have it meaningfully loaded to begin with. Loading such libraries should be a plugin-agnostic step, imho, not part of >> a plugin. >> > > Most of the plugins are a port of a popular library or based on a popular > library, so I have to disagree with you. A javascript library can not be > ported to TW without adaptations. > You wouldn't adapt jQuery, though, but implement it... and I am suggesting that, generally, it is a good thing if plugins implement the same jQuery library rather than have each ship with their own version and then trying to sandbox-call exactly theirs. I'm not sure, but I don't think macros are initialized on startup. Their code is surely run, e.g.: http://alert.tiddlyspot.com That is what startup modules are for. I believe what defines a startup module is that it is chained before (some) other stuff, not exactly sure which. Macros are just functions that returns plain text. Running the macro itself, yes. Running the code that defines the macro, not so much. > They should not modify the dom or the tiddlers store. Macros sure modify the DOM with the output they generate... and, if it was some jQuery function, it could well modify the dom of whatever was rendered before so as to enhance that. As for the store... sure, macros should not be saving tiddlers, only the things they render may trigger that, e.g. buttons. > And no, you don't need a macro for Galleria, you need a widget. Not quite true. Can be a widget, can be a macro ...just like the one above that reads <<galleria>> and turns images in a preceding *.galleria* div into ...a galleria. I know the widgets development could be scary, but it is not so hard and it > is the correct way of doing things. I will implement widgets when I need them, but I will gladly skip them when I don't. Best wishes, Tobias. -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywikidev. For more options, visit https://groups.google.com/d/optout.
