> due to some discussions regarding the size of the core, I can't skip > asking: why newJournal is still there? newTiddlers allows what it > does, it's not frequently used (I mean added to a new tiddler), > replacing > > <<newJournal "DD MMM YYYY" "journal">>
In practice, the newJournal macro doesn't involve much code (as you've surmised, it's largely shared with newTiddler), and so I'm not sure that removing it would be worth the trouble. Cheers Jeremy > with corresponding newTiddler macro would encourage users to use > newTiddler macro in various ways. The only thing is that modified > SideBarOptions would make an error if there's newJournal, but > elucidation can be put into a message in the upgrade area. > > > As a side note, I'd add that messages in the upgrade area can be used > more heavily, for instance, for translating change logs or some > notifications, not only for displaying errors. > > -- > You received this message because you are subscribed to the Google Groups > "TiddlyWikiDev" 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/tiddlywikidev?hl=en. > -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" 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/tiddlywikidev?hl=en.
