I suppose one thing I should mention here is that I'm a hacker type, and not a programming type especially when it comes to JavaScript.
> Plugins Either make a shadow stylesheets or use element styling: eg <div > > class="thingone" style="border:2px #FF0 solid"></div> > > What does the 'setStylesheet()" function do? > > Well at a closer look I stand correct: This function is part of this built in jQuery Plugin jQuery.twStylesheet.js jQuery plugin to dynamically insert CSS rules into a document Usage: jQuery.twStylesheet applies style definitions jQuery.twStylesheet.remove neutralizes style definitions It's function dose indeed inject CSS rulls into the document. I guess I have never noticed any plugin doing this on the basis that the users StyleSheets overrides it anyway, and I never thought about it as it seemed like a silly idea compared to making a shadow style sheet for the plugin or using element styles. > That doesn't mean you can't change things if they where made right you > > can still use the !important flag in your StyleSheet to override them. > eg: > > <div class="thingone" style="border:2px #FF0 solid;"></div> > > You are missing my point. > > If I don't know the names of the classes then I'm stuck. > maybe I can do good stuff the hard way, ignoring the name, surrounding > the macro with a <span> in the tiddler itself and doing it the hard, > pre-CSSway. If its not in the docco, if its not in reable source then > how can I know the name? > > Oh, right, take a dump of the page to a file and go though it line by > lie to wee what happens when the macro is expanded.... > Why not use the built in page inspection tools in most modern browsers? Or the great community tools for such tasks like FireBug: <https://lh4.googleusercontent.com/-mmEl6BZk-8I/Umx4aVgiAiI/AAAAAAAAANQ/qP4YlhfHoCY/s1600/2013-10-26_191940.jpg> Usually you can find the full CSS path of anything on the page in less than 3 clicks. > Otherwise you do like any other good hacker and learn to read machine > > optimized code. > > Yes, that's a great way to make TiddlyWiki popular; make it only > available to people who are able, willing and have the time to read > machine optimized, and compressed, code. > The vast majority of the time you will not need to hack plugins to style things. The vast majority of the time you will have plugins with the source available. It is not a developers job to make sure you can easily modify their code nor is it their responsibility to make sure it is always available even if they did unless they make it their jobs themselves. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" 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/tiddlywiki. For more options, visit https://groups.google.com/groups/opt_out.
