Hi Tobias
> I think that the scenario you describe for dynamic grids is covered by the >> <$list> widget - the missing part at the moment is the ability to display >> the list as an HTML table. The goal is to enable tables to be produced as >> nested <$list> widgets >> > > That's where I would have expected it. Will widgets be extendible? Or will > the be constrained to a core feature set. I guess there's always the > possibility for hijacking, but perhaps not. > Some widgets are extensible in a modular way. For instance, the list widget features extensible listview modules that handle animating changes to a list. Hijacking isn't really part of the TW5 way of doing things, but JavaScript is JavaScript so anything is possible... > > >> I'm not sure if I fully understand your idea for static grids, what is >> the difference between a context tiddler and a transcluded tiddler? >> > > The idea would be to set the context tiddler for a given scope or context > once (e.g. a table, a table row or cell) and then be able to reuse that > reference throughout a number of subsequent macro calls... instead of > referring to the current tiddler, i.e. to act as if in another tiddler. > That sounds an awful lot like the way that the context tiddler works for transclusion at the moment. > Perhaps that stretches flexibility a bit too much, but then I think it's a > lot more flexible than tieing strict naming conventions to for use in a > single layout. > I'm not sure that I fully understand your proposals here, but as ever they are in interesting territory! Best wishes Jeremy Cheers, Tobias. -- Jeremy Ruston mailto:[email protected] -- 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/groups/opt_out.
