Hi Mario, As fot applying a theme... got it. I totally overlooked that low- constrast toolbar.
After having played a bit more with freestyle, I have a few questions. Would it make sense to extent the drop functionality, such that one can not only set the name of that template element but also its main parameter(s), e.g. the width (or the corresponding emastic shorthand)? You could easily implement a delimiter like "##" so one could input "name##width". Why did you make it a two-click process to get to that "edit" button for the template-code? Are you intending to add more features to that top-left corner of the template-element-header? Otherwise.. why not open the code directly in edit mode? If I understand right, this is intended to be a designer to facilitate the creation of a template(-system?) which - in order for it to run - is then to be imported into a kind of emastic-ready-tiddlywiki (leaving the designer-bulk outside your "realworld tw")... which you prepare by importing what is listed in "needed components". To understand the concept better, does a single "template" then consist of several template-element-tiddlers depending on, calling for and embedding each other upon display? ...or, would that rather be one big template to be imported? My current guess is to import all tiddler created during the design process ...all that which I thus gave a certain template-name, correct? Also, is it possible with this emastic system to "live-swap" templates, e.g. to call an alternative "left-column" depending on a certain tag? If yes, how? In my thinking, all these boxes "only" make much sense if there are ways to trigger "context sensitive" content. Meaning, for example, if I had some context-box in a right column and I opened a certain tiddler in what one might call the main-content-box, I would want for that context-box to be flexible, such that its content depends on what is displayed in the main-content-box. One could easily imagine something alike for a kind of context-sensitive topmenu. Without such context-sensitive triggering, the whole emastic grid seems to merely display static content. Well, one might try and do some DOM-inspection in the respective box to figure out which tiddler is being displayed in another one (and their properties, such as tags). After all, this context-sensitivity is what I would consider the main reason for using such a template system. Hope I didn't bombard you with too many questions. ;-) Tobias. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" 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/tiddlywiki?hl=en.
