That seems like a possibility - the sniffing part is easy but I'd rather 
not have to due this via a theme. Plus I'm not sure how I would use the 
Reveal widget to hide things that are already part of the Control panel 
without heavily re-writing the control panel tiddlers (I could be totally 
wrong here).

Ideally, I really want to be able to use any intact stand-along HTML wiki 
file and keep it so that it that can still be opened in a web browser as 
necessary. This means leaving in all the standard themes that show save 
buttons, etc... I also don't want the user to have to switch themes based 
on which host they opened the file in - the UI should be adjusted 
automatically. I just want a way to hide that parts that don't make sense 
when it is loaded in something that is not a standard web browser.

Maybe themes could be a way to do this but I'd need a way to cause the 
custom theme to only be activated when it was loaded in my custom host and 
also not be able to be changed by the user. Plus, I'd like to respect 
whatever theme the user has selected if they then load the wiki in their 
web browser at a later point.

My gut makes me think that this might be better done in code, i.e. my 
plugin does the hiding of the elements to suppress them from the UI when it 
detect the custom host. I have no problem maintaining a list of things that 
need suppressing, the question becomes how do I suppress them from within 
my plugin's code. Maybe I could target CSS styles but it seems better to 
somehow temporarily hide or deactivate tiddlers if possible but in a way 
that also doesn't change what gets saved when the wiki is save, i.e. it 
should be a temporary state somehow.

Thanks

-- 
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/d/optout.

Reply via email to