I am a nobody and I feel if a person like Eric says something then something is going on which nobodies like me do not know of but somebodies who do know something should probably do something about this. Let the piece of goodness, which TW is, not be harmed due to any possible wrong policy.
On Mar 17, 11:13 pm, Eric Shulman <[email protected]> wrote: > > > > And it seems that Jon's <<list>> template stuff made it to the core. > > > > Which is > > > > cool. > > > Has it? > > > according to the alpha TS core yes > > TBH, I think the design of this new feature has not been properly > considered before being added to the core. It seems like this was > 'tossed in' as a quick tweak, without proper *public* discussion or > review of the design or usability issues. > > For example, one *minor* issue I have is with the choice of parameter > name. There is already a well-established "template" mechanism within > TiddlyWiki: a template is a tiddler containing HTML syntax used to > produce formatted output. However, Jon's <<list>> macro "templates" > do NOT build on that functionality... instead, Jon's list macro > "template" is really more like using <<tiddler>> transclusion that > merely renders wiki-formatted syntax, but without the ability to > substitute "with:" parameter values into the output. > > A more serious issue is the manner in which this addition has > triggered additional core changes in the <<view>> macro. Those core > changes were entirely *reactive*, and were made without much > discussion about appropriate syntax, usability, or even the features > actually desired by the community. If proper discussions had > occurred, then issues like the "case sensitivity problem" for slice > references could have been easily identified and addressed, *before* > the code was checked-in to the core. > > From my point-of-view, there appears to be a double standard at work > here. Proposed core changes developed *outside* Osmosoft get a lot of > resistance, languish for months (or *years*), or are repeatedly re- > scheduled for a later release, effectively forcing them to be > implemented as plugins, even if the proposed core change is minimal, > isolated, and well-tested. > > In contrast, it seems that changes developed *inside* Osmosoft often > get "fast-tracked" straight into the next release of the core, > resulting in follow-up tickets to fix problems (or add even more > functionality) that could have been identified and addressed > beforehand. > > -e -- 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.
