What's the backstage for?
73 views
Skip to first unread message
rakugo
Mar 14, 2011, 11:45:02 AM3/14/11
to TiddlyWiki
This is an open ended question that I'd like to understand from
different people's perspectives.
In TiddlyWiki it's primary purpose seems to be updating /
configuring / upgrading the TiddlyWiki.
In TiddlySpace we have used it to get consistency across TiddlyWiki's
which differ greatly in design/functionality and to act as a fallback
to access Tiddly[Wiki/Space]'s core functions such as saving, creating
new content and managing members of spaces when a user may have
disabled them in the UI or have an unusable theme.
The one thing that is common with both TiddlyWiki and TiddlySpace, is
the use of the backstage is completely optional. I for one tend to go
there infrequently (especially in TiddlyWiki) - the tool can be used
without it.
This weekend and today I have been experimenting with new themes and
in particular I explored putting the new tiddler, permaview and close
all buttons in the backstage (see http://backstage.tiddlyspace.com/).
My main motivation for doing this was so that the new tiddler button
was readily available, and I didn't have to scroll to the top of the
page to click it. Another advantage is that to non-TiddlyWiki users,
the new tiddler, permaview and close all buttons are meaningless and
concepts they must understand and use. Hiding it in the backstage,
hides away these concepts with other complicated concepts such as
inclusion, members and tweaking a Tiddly[Wiki/Space]. As a result it
feels more like a traditional website rather than something different
that looks too complicated to use. The emphasis is then put on reading
the content in the TiddlyWiki.
The downside of putting these buttons here is the height of the
backstage increases, it is a bit more overwhelming and it also seems
to extend the original remit of the backstage.
So really I'm just interested in people's thoughts on this. Am I a
lunatic to even think of putting the buttons up there or do you think
I'm on to something?
Jon
different people's perspectives.
In TiddlyWiki it's primary purpose seems to be updating /
configuring / upgrading the TiddlyWiki.
In TiddlySpace we have used it to get consistency across TiddlyWiki's
which differ greatly in design/functionality and to act as a fallback
to access Tiddly[Wiki/Space]'s core functions such as saving, creating
new content and managing members of spaces when a user may have
disabled them in the UI or have an unusable theme.
The one thing that is common with both TiddlyWiki and TiddlySpace, is
the use of the backstage is completely optional. I for one tend to go
there infrequently (especially in TiddlyWiki) - the tool can be used
without it.
This weekend and today I have been experimenting with new themes and
in particular I explored putting the new tiddler, permaview and close
all buttons in the backstage (see http://backstage.tiddlyspace.com/).
My main motivation for doing this was so that the new tiddler button
was readily available, and I didn't have to scroll to the top of the
page to click it. Another advantage is that to non-TiddlyWiki users,
the new tiddler, permaview and close all buttons are meaningless and
concepts they must understand and use. Hiding it in the backstage,
hides away these concepts with other complicated concepts such as
inclusion, members and tweaking a Tiddly[Wiki/Space]. As a result it
feels more like a traditional website rather than something different
that looks too complicated to use. The emphasis is then put on reading
the content in the TiddlyWiki.
The downside of putting these buttons here is the height of the
backstage increases, it is a bit more overwhelming and it also seems
to extend the original remit of the backstage.
So really I'm just interested in people's thoughts on this. Am I a
lunatic to even think of putting the buttons up there or do you think
I'm on to something?
Jon
PMario
Mar 14, 2011, 1:06:19 PM3/14/11
to TiddlyWiki
On Mar 14, 4:45 pm, rakugo <jdlrob...@gmail.com> wrote:
> In TiddlySpace we have used it to get consistency across TiddlyWiki's
> which differ greatly in design/functionality and to act as a fallback
> to access Tiddly[Wiki/Space]'s core functions such as saving, creating
> new content and managing members of spaces when a user may have
> disabled them in the UI or have an unusable theme.
Exactly because of this, I decided not changing anything there. If I
> In TiddlySpace we have used it to get consistency across TiddlyWiki's
> which differ greatly in design/functionality and to act as a fallback
> to access Tiddly[Wiki/Space]'s core functions such as saving, creating
> new content and managing members of spaces when a user may have
> disabled them in the UI or have an unusable theme.
make changes to one of the backstage tiddlers, it creates a local
copy. So there is no automatic update anymore. I want to have
backstage area, which is maintained by the developers.
-m
rakugo
Mar 14, 2011, 1:13:22 PM3/14/11
to TiddlyWiki
this is intentional to dissuade people from altering the backstage
behaviour. The interesting question is what have you wanted to change/
customise in the backstage... and why? What do you see its purpose as
being?
Måns
Mar 15, 2011, 11:01:35 AM3/15/11
to TiddlyWiki
Hi Jon
> As a result it
> feels more like a traditional website rather than something different
> that looks too complicated to use. The emphasis is then put on reading
> the content in the TiddlyWiki.
I feel the backstage should be hidden as default - Maybe it could be
accessed as a checkbox option you could put in the backstage in the
Tweaks tab??
I don't quite get the point, where you say that "the new tiddler
menuBar at the top of the PageTemplate - so you'll still have to
scroll up to see it?!
> to non-TiddlyWiki users,
> the new tiddler, permaview and close all buttons are meaningless and
> concepts they must understand and use. Hiding it in the backstage,
> hides away these concepts with other complicated concepts such as
> inclusion, members and tweaking a Tiddly[Wiki/Space].
The new tiddler is hidden in readonly mode, and I feel/think that the
permaview button should be available to readers who would want to
share a link to all open tiddlers (story).. TW *is* different in that
it doesn't provide breadcrumbs, unless you provide a plugin which
forces it to do so, and even then you'll only have a link to one open
tiddler - which isn't perfect, when you'd want to share the view of
several tiddlers in a story...
I feel this is one of the advantages of a TW - which readers should
become aware of - and it should be as obvious as possible :-)
Maybe the CloseAll button should/could be replaced with a Home -
button, which will prevent readers from getting "a blank story", and
let them start all over - just like you would expect on most
"traditional webpages" ....
> The downside of putting these buttons here is the height of the
> backstage increases, it is a bit more overwhelming and it also seems
> to extend the original remit of the backstage.
Yep - I don't like that...
I was quite thrilled, back then, when the backstage was made very
slim.
Cheers Måns Mårtensson
> As a result it
> feels more like a traditional website rather than something different
> that looks too complicated to use. The emphasis is then put on reading
> the content in the TiddlyWiki.
accessed as a checkbox option you could put in the backstage in the
Tweaks tab??
I don't quite get the point, where you say that "the new tiddler
button was readily available, and I didn't have to scroll to the top
of the page to click it."
It's still located in the SideBarOptions tiddler isn't it? - in the
of the page to click it."
menuBar at the top of the PageTemplate - so you'll still have to
scroll up to see it?!
> to non-TiddlyWiki users,
> the new tiddler, permaview and close all buttons are meaningless and
> concepts they must understand and use. Hiding it in the backstage,
> hides away these concepts with other complicated concepts such as
> inclusion, members and tweaking a Tiddly[Wiki/Space].
permaview button should be available to readers who would want to
share a link to all open tiddlers (story).. TW *is* different in that
it doesn't provide breadcrumbs, unless you provide a plugin which
forces it to do so, and even then you'll only have a link to one open
tiddler - which isn't perfect, when you'd want to share the view of
several tiddlers in a story...
I feel this is one of the advantages of a TW - which readers should
become aware of - and it should be as obvious as possible :-)
Maybe the CloseAll button should/could be replaced with a Home -
button, which will prevent readers from getting "a blank story", and
let them start all over - just like you would expect on most
"traditional webpages" ....
> The downside of putting these buttons here is the height of the
> backstage increases, it is a bit more overwhelming and it also seems
> to extend the original remit of the backstage.
I was quite thrilled, back then, when the backstage was made very
slim.
Cheers Måns Mårtensson
rakugo
Mar 15, 2011, 1:13:31 PM3/15/11
to TiddlyWiki
Thanks Mans for joining the conversation!
> I feel the backstage should be hidden as default - Maybe it could be
> accessed as a checkbox option you could put in the backstage in the
> Tweaks tab??
I agree it could be hidden as default. In TiddlySpace when closed you
get the icon in the top right hand corner which doesn't seem so
intrusive but invites one to click on it and explore further.
> I don't quite get the point, where you say that "the new tiddler
> button was readily available, and I didn't have to scroll to the top
> of the page to click it."
> It's still located in the SideBarOptions tiddler isn't it? - in the
> menuBar at the top of the PageTemplate - so you'll still have to
> scroll up to see it?!
Sorry I didn't explain this well. One could imagine making the
backstage "stick" to the top of the page so that when you scroll it
remains at the top. If there was a new tiddler button within the
backstage, one could easily access it without having to scroll.
> The new tiddler is hidden in readonly mode, and I feel/think that the
> permaview button should be available to readers who would want to
> share a link to all open tiddlers (story).. <snip>
experience. I see the closeAll and permaview buttons as useful
features which one grows used to then uses heavily. I've seen some
TiddlyWiki themes remove these buttons all together, so putting them
in the backstage would make sense from that point of view in making
them available across tiddlyspace.
> > The downside of putting these buttons here is the height of the
> > backstage increases, it is a bit more overwhelming and it also seems
> > to extend the original remit of the backstage.
>
> Yep - I don't like that...
> I was quite thrilled, back then, when the backstage was made very
> slim.
An implementation detail. I wonder if the new tiddler/close all/
permaview buttons could be made part of the backstage whilst keeping
it slim. http://twitter.com/ manages to keep it's thin whilst packing
in lots of functionality.
> I feel the backstage should be hidden as default - Maybe it could be
> accessed as a checkbox option you could put in the backstage in the
> Tweaks tab??
get the icon in the top right hand corner which doesn't seem so
intrusive but invites one to click on it and explore further.
> I don't quite get the point, where you say that "the new tiddler
> button was readily available, and I didn't have to scroll to the top
> of the page to click it."
> It's still located in the SideBarOptions tiddler isn't it? - in the
> menuBar at the top of the PageTemplate - so you'll still have to
> scroll up to see it?!
backstage "stick" to the top of the page so that when you scroll it
remains at the top. If there was a new tiddler button within the
backstage, one could easily access it without having to scroll.
> The new tiddler is hidden in readonly mode, and I feel/think that the
> permaview button should be available to readers who would want to
> I feel this is one of the advantages of a TW - which readers should
> become aware of - and it should be as obvious as possible :-)
Agreed, but for a first time user they are not essential to the
> become aware of - and it should be as obvious as possible :-)
experience. I see the closeAll and permaview buttons as useful
features which one grows used to then uses heavily. I've seen some
TiddlyWiki themes remove these buttons all together, so putting them
in the backstage would make sense from that point of view in making
them available across tiddlyspace.
> > The downside of putting these buttons here is the height of the
> > backstage increases, it is a bit more overwhelming and it also seems
> > to extend the original remit of the backstage.
>
> Yep - I don't like that...
> I was quite thrilled, back then, when the backstage was made very
> slim.
permaview buttons could be made part of the backstage whilst keeping
it slim. http://twitter.com/ manages to keep it's thin whilst packing
in lots of functionality.
rakugo
Mar 16, 2011, 12:03:00 PM3/16/11
to TiddlyWiki
This tiddler may also be of interest:
http://jon.tiddlyspace.com/#%5B%5BSideBarOptions%20in%20the%20Backstage%5D%5D
> it slim.http://twitter.com/manages to keep it's thin whilst packing
> in lots of functionality.
http://jon.tiddlyspace.com/#%5B%5BSideBarOptions%20in%20the%20Backstage%5D%5D
> in lots of functionality.
Måns
Mar 16, 2011, 12:14:01 PM3/16/11
to TiddlyWiki
Hi Jon
> This tiddler may also be of interest:http://jon.tiddlyspace.com/#%5B%5BSideBarOptions%20in%20the%20Backsta...
Could you replace text with icons - to save even more space?
I did like the symmetry when the tiddlyspace icon (docs&search) was in
the middle, between space and user, however I like your idea of having
the sidebaroptions tools just beside the show/hide button very
much :-) Please carry on..
Cheers Måns Mårtensson
> This tiddler may also be of interest:http://jon.tiddlyspace.com/#%5B%5BSideBarOptions%20in%20the%20Backsta...
Could you replace text with icons - to save even more space?
I did like the symmetry when the tiddlyspace icon (docs&search) was in
the middle, between space and user, however I like your idea of having
the sidebaroptions tools just beside the show/hide button very
much :-) Please carry on..
Cheers Måns Mårtensson
rakugo
Mar 16, 2011, 2:00:34 PM3/16/11
to TiddlyWiki
My thoughts exactly only reason we didn't replace them with icons was
due to lack of suitable icons...
due to lack of suitable icons...
Alex Hough
Mar 16, 2011, 3:07:15 PM3/16/11
to tiddl...@googlegroups.com
> My thoughts exactly only reason we didn't replace them with icons was
> due to lack of suitable icons...
> due to lack of suitable icons...
I have been experimenting with arrows as icons. And I've roughly
created a TiddlySpace [1] to show where I am going with it
The the MainMenu should have an arrow at the top pointing right: this
means new tiddler. Then from each tiddler is a newHere with an up
arrow. In my personal version, this newHere button is currently in the
Tagging <div> : it kinda makes sense here i think, but there is a
problem when the new tiddler is not tagging.
its all work in progress: i like having a shonky TW interface, one
which i am always changing, like a (bad) DIY enthusiast...
ALex
[1] http://arrows.tiddlyspace.com/
>
> On Mar 16, 4:14 pm, Måns <humam...@gmail.com> wrote:
>> Hi Jon
>>
>> > This tiddler may also be of interest:http://jon.tiddlyspace.com/#%5B%5BSideBarOptions%20in%20the%20Backsta...
>>
>> Could you replace text with icons - to save even more space?
>> I did like the symmetry when the tiddlyspace icon (docs&search) was in
>> the middle, between space and user, however I like your idea of having
>> the sidebaroptions tools just beside the show/hide button very
>> much :-) Please carry on..
>>
>> Cheers Måns Mårtensson
>
> --
> You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.
> To post to this group, send email to tiddl...@googlegroups.com.
> To unsubscribe from this group, send email to tiddlywiki+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
>
>
rakugo
Mar 18, 2011, 8:26:02 AM3/18/11
to TiddlyWiki
On Mar 16, 7:07 pm, Alex Hough <r.a.ho...@gmail.com> wrote:
> > My thoughts exactly only reason we didn't replace them with icons was
> > due to lack of suitable icons...
>
> I have been experimenting with arrows as icons. And I've roughly
> created a TiddlySpace [1] to show where I am going with it
> The the MainMenu should have an arrow at the top pointing right: this
> means new tiddler. Then from each tiddler is a newHere with an up
> arrow. In my personal version, this newHere button is currently in the
> Tagging <div> : it kinda makes sense here i think, but there is a
> problem when the new tiddler is not tagging.
>
intriguing.
> its all work in progress: i like having a shonky TW interface, one
> which i am always changing, like a (bad) DIY enthusiast...
the fun. TiddlyWiki is primarily for personal usage, so I guess
theme's are a way of expressing ourselves. :)
Maans, I borrowed some icons from pmario in the @icons space - it has
quite a nice effect:
http://backstage.tiddlyspace.com/
Måns
Mar 18, 2011, 9:08:53 AM3/18/11
to TiddlyWiki
Hi Jon
> Maans, I borrowed some icons from pmario in the @icons space - it has
> quite a nice effect:http://backstage.tiddlyspace.com/
Those are very beautifull icons!!, however they are almost invisible
untill hovered, I'd like to see the icons, before I find them with the
mouse... :-)
Another thing I noticed... If you run the bookmarklet:
javascript:void(eval(decodeURIComponent(%22(function()
{try{if(window.version%2526%2526window.version.title%253D
%253D'TiddlyWiki')%2520%257BreadOnly%253Dfalse%253Bif(window.backstage)
%257Bif(!backstage.button)backstage.init()%253Bbackstage.show()%253B
%257Dconfig.options.chkAnimate%253Dfalse%253BrefreshDisplay()%253B
%257D}catch(e){alert(e.description||e.toString())}})()%22)))
The backstage isn't refreshed to show the writable mode - therefore no
visible <<newTiddler>> macro!! (old FF 2.00.20 - old Puppy Linux 4.21)
I often switch back and forth to se the difference between readonly-
mode and writable-mode. When I use Eric's PasteUpPlugin I need this
function...
Cheers Måns Mårtensson
> Maans, I borrowed some icons from pmario in the @icons space - it has
> quite a nice effect:http://backstage.tiddlyspace.com/
untill hovered, I'd like to see the icons, before I find them with the
mouse... :-)
Another thing I noticed... If you run the bookmarklet:
javascript:void(eval(decodeURIComponent(%22(function()
{try{if(window.version%2526%2526window.version.title%253D
%253D'TiddlyWiki')%2520%257BreadOnly%253Dfalse%253Bif(window.backstage)
%257Bif(!backstage.button)backstage.init()%253Bbackstage.show()%253B
%257Dconfig.options.chkAnimate%253Dfalse%253BrefreshDisplay()%253B
%257D}catch(e){alert(e.description||e.toString())}})()%22)))
The backstage isn't refreshed to show the writable mode - therefore no
visible <<newTiddler>> macro!! (old FF 2.00.20 - old Puppy Linux 4.21)
I often switch back and forth to se the difference between readonly-
mode and writable-mode. When I use Eric's PasteUpPlugin I need this
function...
Cheers Måns Mårtensson
Måns
Mar 18, 2011, 9:17:59 AM3/18/11
to TiddlyWiki
Just tried it in Google Chrome 7.0.517.44 - still no go..
rakugo
Mar 18, 2011, 9:48:43 AM3/18/11
to TiddlyWiki
> > Maans, I borrowed some icons from pmario in the @icons space - it has
> > quite a nice effect:http://backstage.tiddlyspace.com/
>
> Those are very beautifull icons!!, however they are almost invisible
> untill hovered, I'd like to see the icons, before I find them with the
> mouse... :-)
All @pmario's wonderful work. I just made some slight changes.
> > quite a nice effect:http://backstage.tiddlyspace.com/
>
> Those are very beautifull icons!!, however they are almost invisible
> untill hovered, I'd like to see the icons, before I find them with the
> mouse... :-)
>
> Another thing I noticed... If you run the bookmarklet:
>
> javascript:void(eval(decodeURIComponent(%22(function()
> {try{if(window.version%2526%2526window.version.title%253D
> %253D'TiddlyWiki')%2520%257BreadOnly%253Dfalse%253Bif(window.backstage)
> %257Bif(!backstage.button)backstage.init()%253Bbackstage.show()%253B
> %257Dconfig.options.chkAnimate%253Dfalse%253BrefreshDisplay()%253B
> %257D}catch(e){alert(e.description||e.toString())}})()%22)))
>
> The backstage isn't refreshed to show the writable mode - therefore no
> visible <<newTiddler>> macro!! (old FF 2.00.20 - old Puppy Linux 4.21)
>
> I often switch back and forth to se the difference between readonly-
> mode and writable-mode. When I use Eric's PasteUpPlugin I need this
> function...
>
give icons to newTiddler, permaview and closeAll. It's a bit hacky so
could do with some work (essentially you run <<imageButton newTiddler
iconName>> to draw a newTiddler button with a given icon.
> Cheers Måns Mårtensson
Alex Hough
Mar 18, 2011, 11:25:06 AM3/18/11
to tiddl...@googlegroups.com
> I see lots of shonky TiddlyWiki interfaces.. I think that is part of
> the fun. TiddlyWiki is primarily for personal usage, so I guess
> theme's are a way of expressing ourselves. :)
> the fun. TiddlyWiki is primarily for personal usage, so I guess
> theme's are a way of expressing ourselves. :)
I've recently bought a book on Wabi-sabi and have been thinking how
to translate the aesthetic to TW.
http://www.amazon.com/Wabi-Sabi-Artists-Designers-Poets-Philosophers/dp/1880656124
http://en.wikipedia.org/wiki/Wabi-sabi
>I can't seem to see any arrows.. have you published everything? Sounds
intriguing.
It works on Firefox. I cut and pasted the arrow from MacBook's
character viewer. I guess I should encode it. I used css rotate too.
WOW!
The MainMenu keeps getting overwritten automatically by a default on
the space, so that I can't show the arrow in the menu.
http://arrows.tiddlyspace.com/
I've attached a screenshot to this message: don't know if google
groups likes this...
Alex
>
> Maans, I borrowed some icons from pmario in the @icons space - it has
> quite a nice effect:
> http://backstage.tiddlyspace.com/
>
Eric Shulman
Mar 18, 2011, 12:49:57 PM3/18/11
to TiddlyWiki
> I suspect this is due to my imageButton macro which I had to write to
> give icons to newTiddler, permaview and closeAll. It's a bit hacky so
> could do with some work (essentially you run <<imageButton newTiddler
> iconName>> to draw a newTiddler button with a given icon.
http://www.tiddlytools.com/#SetIconPlugin
> give icons to newTiddler, permaview and closeAll. It's a bit hacky so
> could do with some work (essentially you run <<imageButton newTiddler
> iconName>> to draw a newTiddler button with a given icon.
http://www.tiddlytools.com/#SetIconPluginInfo
enjoy,
-e
Måns
Mar 18, 2011, 1:19:03 PM3/18/11
to TiddlyWiki
Hi Jon
Eric's SetIconPlugin is very versatile (has a lot of knobs...)- I've
used it for quite a while - and I like the way it works!
It will display svgs as well...
My biggest problem wasn't really the visibility - rather that the
backstage does'nt reflect a change of mode from readonly to write...
I would need that when working on sth. which I want to test in the
process ie pasteup elements (See Eric's PasteUpPlugin) ..
Cheers Måns Mårtensson
Eric's SetIconPlugin is very versatile (has a lot of knobs...)- I've
used it for quite a while - and I like the way it works!
It will display svgs as well...
My biggest problem wasn't really the visibility - rather that the
backstage does'nt reflect a change of mode from readonly to write...
I would need that when working on sth. which I want to test in the
process ie pasteup elements (See Eric's PasteUpPlugin) ..
Cheers Måns Mårtensson
rakugo
Mar 18, 2011, 1:57:06 PM3/18/11
to TiddlyWiki
Wow, always amazes me how you have plugins for everything :)
Will have to take a look at this.
Thanks for sharing.
Jon
Will have to take a look at this.
Thanks for sharing.
Jon
Bauwe Bijl
Mar 18, 2011, 6:00:03 PM3/18/11
to TiddlyWiki
Jon,
I have used the SeticonPlugin on tiddlyspace...
Can be found here (and can be included):
http://seticonplugin.tiddlyspace.com
Bauwe
I have used the SeticonPlugin on tiddlyspace...
Can be found here (and can be included):
http://seticonplugin.tiddlyspace.com
Bauwe
Måns
Mar 18, 2011, 9:07:08 PM3/18/11
to TiddlyWiki
Hi Bauwe
If you want to have a lot of icons (mostly silk) in the bargain - then
you can include:
http://seticon.tiddlyspace.com/
Cheers Måns Mårtensson
If you want to have a lot of icons (mostly silk) in the bargain - then
you can include:
http://seticon.tiddlyspace.com/
Cheers Måns Mårtensson
Bauwe Bijl
Mar 19, 2011, 3:37:36 PM3/19/11
to TiddlyWiki
Hi Måns
> If you want to have a lot of icons (mostly silk) in the bargain - then
> you can include:http://seticon.tiddlyspace.com/
B-)
Yes could be useful!
But for inclusion purposes I decided to have a "plugin per space" in
this case.
Your space has somewhat extra for instance...you might include the
SeticonPlugin-space and skip the internal plugin...and/or make
"seticon" separate so it can be included with some other plugin (if
there is any...now or future)
Some thoughts....to discuss perhaps?:
Is a "plugin per space" the smallest chunk posible? (and is it
desirable ?)
Should there be a list of includable-plugin spaces to avoid
duplication (say 100 people upload the same plugin....while 99 could
benefit from 1 space)?
How could a group of users depend on 1 plugin maintainer... assuming
the latest version is the best (especially if the plugin is not
written by the "space-owner" / uploader, but think also about
translations-spaces....functionalityspaces)...
Wouldn't it be great if any tw-plugin (latest version) automatically
is an includable-space....where the tiddlyspace-server provides
includable-plugin spaces (perhaps loaded from git-master per plugin)
(always head)?
etc.
Bauwe
> If you want to have a lot of icons (mostly silk) in the bargain - then
> you can include:http://seticon.tiddlyspace.com/
Yes could be useful!
But for inclusion purposes I decided to have a "plugin per space" in
this case.
Your space has somewhat extra for instance...you might include the
SeticonPlugin-space and skip the internal plugin...and/or make
"seticon" separate so it can be included with some other plugin (if
there is any...now or future)
Some thoughts....to discuss perhaps?:
Is a "plugin per space" the smallest chunk posible? (and is it
desirable ?)
Should there be a list of includable-plugin spaces to avoid
duplication (say 100 people upload the same plugin....while 99 could
benefit from 1 space)?
How could a group of users depend on 1 plugin maintainer... assuming
the latest version is the best (especially if the plugin is not
written by the "space-owner" / uploader, but think also about
translations-spaces....functionalityspaces)...
Wouldn't it be great if any tw-plugin (latest version) automatically
is an includable-space....where the tiddlyspace-server provides
includable-plugin spaces (perhaps loaded from git-master per plugin)
(always head)?
etc.
Bauwe
Bauwe Bijl
Mar 19, 2011, 5:05:26 PM3/19/11
to TiddlyWiki
And back to the topic:
I can understand the move of these two functions (closeall and
permaview) to the backstagebar from a design point. (also have been
messing with these)...but I think they should not belong to a
backstage that is (or can be) hidden.
Some thoughts about what might be distracting for readers and content:
The sidebar
The backstage
The toolbar (function "view"....reader is already "viewing")
Multiple tiddlers v.s single page (close others and closeall are
related here)
How I use backstage:
Importing (on space: including spaces, users and switching spaces)
Plugin management (but mostly via tag systemConfig)
Sync
How I use closeall (mostly closeothers from the toolbar ) and
permaview:
Open some tiddlers
Rearrange these so my story is ordered as desired (with the
RearrangeTiddlersPlugin) (bookmarklet mostly)
Hit permaview
Copy the link from the address bar
Paste somewhere (groups, mail etc.)
What I would like to see is that these functions are not in the
backstage....(I saw the last dev where the icons where placed on the
right side of backstage)..
....but as a small panel (same place ...right-top) on a semi
transparent background. So it is always visible (with and without
backstage) and sticky to the top when scrolling down.
For the viewer/reader:
When in singlepage mode the closeall function seems confusing... so I
suggest only permaview in such case
However...the search-function does not work single-page-ish because of
function "openall".
!!The permaview should pop up the created link someway and a "copy to
clipboard" function/button must be presented...
For the writer:
newtiddler
closeall
permaview
(and all the other functions in tw .... savechanges etc.)
...just thinking loud....
Bauwe
I can understand the move of these two functions (closeall and
permaview) to the backstagebar from a design point. (also have been
messing with these)...but I think they should not belong to a
backstage that is (or can be) hidden.
Some thoughts about what might be distracting for readers and content:
The sidebar
The backstage
The toolbar (function "view"....reader is already "viewing")
Multiple tiddlers v.s single page (close others and closeall are
related here)
How I use backstage:
Importing (on space: including spaces, users and switching spaces)
Plugin management (but mostly via tag systemConfig)
Sync
How I use closeall (mostly closeothers from the toolbar ) and
permaview:
Open some tiddlers
Rearrange these so my story is ordered as desired (with the
RearrangeTiddlersPlugin) (bookmarklet mostly)
Hit permaview
Copy the link from the address bar
Paste somewhere (groups, mail etc.)
What I would like to see is that these functions are not in the
backstage....(I saw the last dev where the icons where placed on the
right side of backstage)..
....but as a small panel (same place ...right-top) on a semi
transparent background. So it is always visible (with and without
backstage) and sticky to the top when scrolling down.
For the viewer/reader:
When in singlepage mode the closeall function seems confusing... so I
suggest only permaview in such case
However...the search-function does not work single-page-ish because of
function "openall".
!!The permaview should pop up the created link someway and a "copy to
clipboard" function/button must be presented...
For the writer:
newtiddler
closeall
permaview
(and all the other functions in tw .... savechanges etc.)
...just thinking loud....
Bauwe
Eric Shulman
Mar 19, 2011, 6:06:22 PM3/19/11
to TiddlyWiki
> !!The permaview should pop up the created link someway and a "copy to
> clipboard" function/button must be presented...
see CoreTweak #607:
> clipboard" function/button must be presented...
http://www.TiddlyTools.com/#CoreTweaks
This tweak adds 'onmouseover' handling to the 'permaview' command, so
that the permaview URL is automatically generated and assigned to the
HREF of the command (which is currently unused). This allows you to
use the "Copy Link Location" function from your browser's standard
right-click popup menu. Note that this tweak does not 'auto-click'
the permaview command, so the URL in the browser's location bar is
*not* changed unless you actually *left*-click on the command.
enjoy,
-e
Reply all
Reply to author
Forward
0 new messages