Re: [tw] Re: keyboard shortcut and mouse gestures?
Sounds good. I can live with the gesture being optional. On Sun, Mar 8, 2015 at 3:06 PM, Jed Carty wrote: > I agree with Danielo about not liking double clicking to open the editor. > Would it be possible to have a setting/plugin that can enable or disable > it? It shouldn't be too hard to add the event listener to the text area of > a tiddler that will open the editor. You may have to reload the wiki after > toggling it, but that isn't a problem unless you are going to be changing > it a lot. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "TiddlyWiki" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/tiddlywiki/aZ7tIGnFia4/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > tiddlywiki+unsubscr...@googlegroups.com. > To post to this group, send email to tiddlywiki@googlegroups.com. > Visit this group at http://groups.google.com/group/tiddlywiki. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: Is there a tiddler namespace that is not saved to disk?
Ok, cool. This looks like just what I was looking for. Thank you for your replys. :) So to summarize: * in the current Version (5.1.7) anything below `$:/state/popup/` will not be saved to disk. * if I wanted to extend my TW to change the core functionality (and possibly create a plugin) I would override the shadowtiddler `$:/core/save/all` and replace the `saveTiddlerFilter()` macro to add some logic which chains a filter or excludes blacklisted tiddlers and appends whitelisted tiddlers. Followup questions: * Which would you assume is the better and/or easier way to go about it: ** Find the core shadowtiddlers that use the tab widget and change the location where the state is saved to something below `$:/state/popup/` ** Extend the `$:/core/save/all` to evaluate and process some easily manageable lists that white-/blacklist tiddlers ** Find and mess around with the tab widget itself * Can you think of anything below `$:/state/` which you would definately not considder transient state, otherwise I might just add all of `$:/state/` to my ignore list Cheers -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: [TW5] widget to Goto Ranomized Tiddler
On Sunday, March 8, 2015 at 9:57:42 AM UTC-7, Neil Griffin wrote: > > If the $ is needed in some cases, is there an argument for allowing it for > all widget parameters to improve consistency? > Respectfully, that makes *no* sense! There is a need to differentiate parameters with the same name that are to be handled differently (e.g., "$tiddler" vs. "tiddler"). If all widget params have a $ prefix, we'd still need to invent *another* way to differentiate the parameters. Also, if *all* widget parameters use the $ prefix, then why have the prefix at all? As an example of the result of the confusion caused by inconsistency, a > couple of times I have neglected the $ in the $tiddler and $field > parameters of a $action-setfield widget, with the result that, when > activated, the action defaulted to the text field of the current tiddler, > overwriting all the text I was working on! That's extremely annoying, and > quite difficult to debug when you no longer have the wikitext that caused > the problem! > Changing the syntax won't provide a solution for your specific problem, as you still need to explicitly differentiate the use of the same parameter names, and the underlying cause of the problem is that you *forgot* to do that. Perhaps the better solution is to have a "developer debugging mode" setting that would add some extra checks with a prompt to confirm before a widget overwrites any data in the store (e.g., "Are you sure you want to change TiddlerName!!fieldname?")... Maybe it can just check for overwrites for the "text" field, and be limited to widgets that actually use the "$foo" vs "foo" parameter handling, so that it isn't too disruptive during development. Of course, the setting could be turned off after debugging, so that real-world use would nto be affected. enjoy, -e Eric Shulman TiddlyTools / ELS Design Studios "Inside TiddlyWiki: The Missing Manual" https://www.indiegogo.com/projects/inside-tiddlywiki-the-missing- manual/x/8816263 Note: the IndieGogo funding campaign has ended, but direct fundraising continues below... YOUR DONATIONS ARE VERY IMPORTANT! HELP ME TO HELP YOU - MAKE A CONTRIBUTION TO MY "TIP JAR"... http://TiddlyTools.github.com/fundraising.html#MakeADonation Professional TiddlyWiki Consulting Services... Analysis, Design, and Custom Solutions: http://www.TiddlyTools.com/#Contact -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: keyboard shortcut and mouse gestures?
I agree with Danielo about not liking double clicking to open the editor. Would it be possible to have a setting/plugin that can enable or disable it? It shouldn't be too hard to add the event listener to the text area of a tiddler that will open the editor. You may have to reload the wiki after toggling it, but that isn't a problem unless you are going to be changing it a lot. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
Re: [tw] Re: keyboard shortcut and mouse gestures?
I really hate the double click to edit. It's unnatural, no matter how used are some of you to it. IMO it would be better to have a custom right click menu and add the edit thing there. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: [TW5] widget to Goto Ranomized Tiddler
If the $ is needed in some cases, is there an argument for allowing it for all widget parameters to improve consistency? As an example of the result of the confusion caused by inconsistency, a couple of times I have neglected the $ in the $tiddler and $field parameters of a $action-setfield widget, with the result that, when activated, the action defaulted to the text field of the current tiddler, overwriting all the text I was working on! That's extremely annoying, and quite difficult to debug when you no longer have the wikitext that caused the problem! Neil. On Saturday, 7 March 2015 16:54:47 UTC, Eric Shulman wrote: > > On Saturday, March 7, 2015 at 8:00:53 AM UTC-8, Jed Carty wrote: >> >> Action widgets use $ for the parameters, I am assuming that is because >>> you can pass (some of) them lists of name=value pairs, like the setfield >>> widget. The $ in needed to distinguish between things like in this example >>> >> >> <$action-setfield $tiddler=SomeTiddler tiddler=hi/> >>> >> >> which sets the field called tiddler of SomeTiddler to hi. I am assuming >> that $ was picked because it isn't a valid symbol in a field name. >> > > > The $ prefix is used to differentiate parameters used by the widget itself > as compared to parameters without the $, which are simply "passed through" > to the specific macro or action being invoked by the widget. For most > widgets (except $macrocall and $action-xxx), the parameters do not have the > $ prefix. > > -e > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: Is there a tiddler namespace that is not saved to disk?
If you have a look at $:/core/save/all you can see that $:/state/popup/ would be an option. -mario -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Is there a tiddler namespace that is not saved to disk?
>From your description I understand that you are using the standalone version. >The node JS version works exactly as you describe. There are some namespace >that are not saved to disk. This should be possible also with the standalone >version, but you need to modify the filter that the saver is using. By default >it uses core save all. Maybe it's enough to just subtract the tiddler with >certain prefix. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Is there a tiddler namespace that is not saved to disk?
Hi,
I have been medling with TiddlyWiki5 now for a week or two and am liking it
allot thus far. And now I am trying to get TW to play along nicely with git
version control. I am pleasantly surprised how smooth it has been working
thus far, as the writer seems to do a nice job of making diff's work easier
than I would have expected from a xml-like data store. However it currently
still is a little bit more noisy than I would like, due to everything being
a tiddler.
Is there a way to specify which tiddlers should not be saved, regardless of
whether they were changed or not? Ideally is there a namespace for that? I
would have expected `$:/temp/` to behave that way, but alas it is also
written to disk.
In order to get a grip on what is changing I made myself this list tiddler:
```
!Volatile Systemsettings
<$list filter="[is[system]prefix[$:/state/]]">
<$button>
<$action-deletetiddler $tiddler={{!!title}}/>
Delete
<$link to={{!!title}}><$view field="title"/>
<$list filter="[is[system]prefix[$:/temp/]!prefix[$:/temp/info-plugin]]">
<$button>
<$action-deletetiddler $tiddler={{!!title}}/>
Delete
<$link to={{!!title}}><$view field="title"/>
<>
<>
```
in which I can review those paths that I have observed to be changing
frequently on disk and optionally delete them. Mostly it has been settings
specifying which tab is selected in various places and I personally in most
cases dont care to version/sync that information, as I would considder this
a transient state.
Ideally I would like to blacklist/whitelist/filter what gets saved to disk
in a configurable way, so that my random commit count gets reduced.
Does anyone have experience with or even a solution to this?
Cheers
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.
[tw] Re: Problem saving with TiddlyWiki
The TW version used by the site is: 2.6.4 ... which doesn't work with the current browser security restrictions. I did test it with FireFox and TiddlyFox addOn [1] -> works. IMO version 2.6.4 doesn't use the new fallback save mechanism. So you'll need to use FF or a newer TW version 2.8.1 [2]. Is FireFox an option for you? If yes it would work with the TiddlyFox addOn. If FF is no option you'll need to update your TW core. So Chrome can use the fallback save mechanism without any addOn or java plugin. This mechanism works, but is less convenient then with FF. -mario [1] https://addons.mozilla.org/de/firefox/addon/tiddlyfox/ [2] http://classic.tiddlywiki.com/ -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: Problem saving with TiddlyWiki
Of course! Here's the link: http://swn.emichron.com/ It generates a TiddlyWiki page, and fills it with random information based off of a seed. I thought there may be some issues with plug-ins, but i'm still not sure. Thanks for the help! Christian On Sunday, March 8, 2015 at 3:28:41 AM UTC-5, PMario wrote: > > Hi Christian, > Can you point us to the page and the TW, so we can test it? > -m > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
[tw] Re: Problem saving with TiddlyWiki
Hi Christian, Can you point us to the page and the TW, so we can test it? -m -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
