> For better > segregation, I was considering using the ChangeMode plugin from > Bidix's site (love that plugin, Bidix!) but I'm not considering <= ''Typo'' > splitting up the TiddlyWiki into a content file and admin/editing file > and hiding a tiddler in the content file that will import the the > admin/editing tools/ViewTemplates.
See ''Typo'' above: //but I'm NOT considering// should have been //but I'm NOW considering// Sorry! scooter (Scott) On May 13, 4:30 pm, Scott Steele <[email protected]> wrote: > Hi, > > I have a TiddlyWiki set up with Reader and Author/Admin views fairly > well segregated (by using TaggedTemplateTweak and toggling in and out > of edit mode by extending the ToggleReadOnly tiddler). For better > segregation, I was considering using the ChangeMode plugin from > Bidix's site (love that plugin, Bidix!) but I'm not considering > splitting up the TiddlyWiki into a content file and admin/editing file > and hiding a tiddler in the content file that will import the the > admin/editing tools/ViewTemplates. The file size of the single file is > growing too fast and this would help keep the regular visitor file > size down while also providing a tidier separation of content and > editing. > > I plan to use Eric Schulman's LoadTiddlersPlugin in combination with > his TemporaryTiddlersPlugin to temporarily pull the admin tools into > the content file. This works great for things like the advance import/ > export plugins and the long formatting guide I made up to help the > content editors -- They're pulled in upon clicking my 'Load' button > and loaded so that they provide additional functionality, but they > never saved into the file. Perfect. > > However: > > What I'm doing now does not work as well for tiddlers that are over- > written upon Load. Example: > I was previously using a ToggleSideBarTabs mixed with ToggleReadOnly > to hide/unhide my SideBarTabs. With the Load/TemporaryTiddlers setup, > though, I could reduce the complexity of the site by making the > SideBarTabs tiddler in the content file blank and then Loading from > the admin file will pull in one that works (assuming I've edited it, I > think, so that it's not a default Shadow tiddler(?) ). However, on > save, NO SideBarTabs tiddler is written to the content file, and the > way that save works, the blanked-out one is deleted so that upon > closing and re-opening the page, TiddlyWiki loads up the default > shadow tiddler, which I want to be invisible prior to loading in the > admin tools. > > Question: > > Is there a way that Load/Temporary could still store the original, > overwritten tiddlers in the background so that they are included > during a save of the file? Or would it be possible to use the export > plugin as a save mechanism? And have it export/overwrite to file only > those tiddlers that have changed and which are not tagged temporary? > > I have figured out a few ways to manually close out the content file > -- for instance by permanently re-loading blanked out tiddlers like > SideBarTabs from a third TiddlyWiki file or pure store file before > saving. I'd really like to avoid this though to keep it simple for the > content editors. I convinced my organization to give TiddlyWiki a try > because of the low technical complexity for content authoring. > > Will appreciate any help. Thanks, > > Scott -- 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.
