[tw] Find and Replace in all tiddlers
is there a way to find and replace through all tiddlers? i searched the group and found: http://groups.google.com/group/tiddlywiki/browse_thread/thread/cfcec8... but the SearchAndReplacePlugin is not there anymore. Normally i just open the TiddlyWikiFile in an editor and do the find/ replace there. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to tiddlywiki@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Re: NEW: LinkifyPlugin - another improved version of RedirectMacro / AutoWeaving
Wow, already auto-link for all tiddlers - you're really evolving this!
Some thoughts on syntax:
Both for linkifying multiple words (eg: these multiple words) and for
matching exactly as-is (eg: zoOM not matching Zoom) I suggest using
regular double quotes ("..."), at least as an additional option to
your current syntax. For one it would be the same syntax for both
these cases but, more importantly, double quotes are somewhat of a
defacto standard to specify exactness and delimit multiple words, eg
in search engines (not to mention literature).
(A minor additional benefit, for the multiple words, is that it would
allow it to be the last word(s) defined also, not forcing the user to
come up with yet another word.)
For suffixes (that is one GREAT feature, btw) it'd be more natural
with the ^ in the end of the word, were all suffixes are added.
And if it could be a * instead of ^ it would again be more natural
although one may mistakenly assume it would include every possible
ending... unless (yet another suggestion):
How about letting the user define the "Suffixes" in LinkifyConfig?
This is very much desired for non-English users or the suffix feature
is lost. This would also make that * very natural (the user has
defined everything it covers).
Forgive me if I insensitively suggest things that are difficult to
implment. I can imagine it is difficult to work with double quotes etc
in code.
Again, what a wonderful plugin this is becoming Thank you
Tobias!!!
<:-)
On Apr 12, 12:10 am, Tobias Beer wrote:
> There now is a new Version for
> LinkifyPlugin:http://linkify.tiddlyspot.com/index.html#%5B%5BVersion%20History%5D%5D
>
> Version 0.9.1:> optional auto-linkification for all tiddlers> refactoring (
> addFormatters, linkifyHandler)> performance increase with respect to
> excluded tiddlers -> index of excluded tiddlers now rebuilt on saveTiddler >
> all linkification formatters are now inserted last in formatters array>
> target tiddlers prefixed with ~ in LinkifyConfig are no longer
> linkifiedthemselves>
> implemented marker 0! to prepend formatter to formatters array, instead of
> appending it (default)
>
> Tobias
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To post to this group, send email to tiddlywiki@googlegroups.com.
To unsubscribe from this group, send email to
tiddlywiki+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Re: NEW: LinkifyPlugin - another improved version of RedirectMacro / AutoWeaving
Hi Mario, Am Mittwoch, 11. April 2012 14:19:26 UTC+2 schrieb PMario: > > It seems the plugin creates a bunch of new formatters (this is a great > idea). But inside it uses "store.getTaggedTiddlers()" which needs to > iterate over the whole store, to create a static "exclude list" over > and over again. IMO the "exclude list" could be cached but some > measurements with big TWs would be needed. > This is now changed as of version 0.9.2... http://linkify.tiddlyspot.com/index.html#%5B%5BVersion%20History%5D%5D The index for excludes is (re)built upon load and whenever a tiddler is saved. Cheers, Tobias. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To view this discussion on the web visit https://groups.google.com/d/msg/tiddlywiki/-/lwDR8TV-jCgJ. To post to this group, send email to tiddlywiki@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Re: NEW: LinkifyPlugin - another improved version of RedirectMacro / AutoWeaving
Hi Mario, Am Mittwoch, 11. April 2012 14:19:26 UTC+2 schrieb PMario: > It seems the plugin creates a bunch of new formatters (this is a great > idea). But inside it uses "store.getTaggedTiddlers()" which needs to > iterate over the whole store, to create a static "exclude list" over > and over again. IMO the "exclude list" could be cached but some > measurements with big TWs would be needed. > This is now changed from version *0.9.1* on... http://linkify.tiddlyspot.com/index.html#%5B%5BVersion%20History%5D%5D The index for excludes is (re)built upon load and whenever a tiddler is saved. Cheers, Tobias. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To view this discussion on the web visit https://groups.google.com/d/msg/tiddlywiki/-/aWBSls9UH_AJ. To post to this group, send email to tiddlywiki@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Re: Find and Replace in all tiddlers
Try Eric's TiddlerTweakerPlugin (1). (1) http://www.TiddlyTools.com/#TiddlerTweakerPlugin w On Apr 12, 10:54 am, Niklas Wagner wrote: > is there a way to find and replace through all tiddlers? > > i searched the group and > found:http://groups.google.com/group/tiddlywiki/browse_thread/thread/cfcec8... > > but the SearchAndReplacePlugin is not there anymore. > > Normally i just open the TiddlyWikiFile in an editor and do the find/ > replace there. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to tiddlywiki@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Re: Find and Replace in all tiddlers
I dont think that will work I what i need is: for example i have links to the tiddler HardwareStore and to the tiddler LokalFarmersMarket in a tiddlers which contains an Interview about where People get their Plants from. Also i have somewhere some tiddlers that are tagged with HardwareStore. now i decide for example, that i dont want to have two tiddlers LokalFarmersMarket and HardwareStore but that i only want to have one Tiddler called Market. so i need a "find and replace option" like it is in every editor that doesn't care where in the tiddlywiki file the word should be replaced, and just simply replace LokalFarmersMarket and HardwareStore into Market everywhere. I am aware that this could destroy the tiddlywiki System. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to tiddlywiki@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Re: NEW: LinkifyPlugin - another improved version of RedirectMacro / AutoWeaving
On Apr 12, 11:11 am, twgrp wrote: > For suffixes (that is one GREAT feature, btw) it'd be more natural > with the ^ in the end of the word, were all suffixes are added. > And if it could be a * instead of ^ it would again be more natural > although one may mistakenly assume it would include every possible > ending... unless (yet another suggestion): I'd +1 this As I saw ^this the first time, I thought it means: find "this at the start of the line", which is the meaning if used within a regExp. === >How about letting the user define the "Suffixes" in LinkifyConfig? >This is very much desired for non-English users or the suffix feature >is lost. This would also make that * very natural (the user has >defined everything it covers). -1 If it is configurable, it will cause different types of configuration tiddlers, which will be incompatible. Imo this limits the "global" usability of the plugin, -m -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to tiddlywiki@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Re: NEW: LinkifyPlugin - another improved version of RedirectMacro / AutoWeaving
PMario wrote > If it is configurable, it will cause different types of configuration > tiddlers, which will be incompatible. Imo this limits the "global" > usability of the plugin, Could you please elaborate a little here. Why would defining the suffixes in the LinkifyConfig cause different types of configuration tiddlers? (Or do you mean between different users? Having only English suffixes literally limits the global usefulnes of it). An idea would perhaps be a hard coded standard set of suffixes, as already implementetd, but allowing the user to manually add additionall ones. Maybe this would not "limit the global usability" as you put it, or? <:-) On Apr 12, 4:59 pm, PMario wrote: > On Apr 12, 11:11 am, twgrp wrote:> For suffixes (that > is one GREAT feature, btw) it'd be more natural > > with the ^ in the end of the word, were all suffixes are added. > > And if it could be a * instead of ^ it would again be more natural > > although one may mistakenly assume it would include every possible > > ending... unless (yet another suggestion): > > I'd +1 this > > As I saw ^this the first time, I thought it means: find "this at the > start of the line", which is the meaning if used within a regExp. > > ===>How about letting the user define the "Suffixes" in LinkifyConfig? > >This is very much desired for non-English users or the suffix feature > >is lost. This would also make that * very natural (the user has > >defined everything it covers). > > -1 > > If it is configurable, it will cause different types of configuration > tiddlers, which will be incompatible. Imo this limits the "global" > usability of the plugin, > > -m -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to tiddlywiki@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Re: NEW: LinkifyPlugin - another improved version of RedirectMacro / AutoWeaving
Hello twgrp and PMario,
The current discussion might be a bit misleading in that I started by using
the term "prefix" and now you are talking about suffixes too.
In fact, these characters are rather meta characters, switches or flags.
1) They could be configurable since they (currently) do not end up in the
regex that is used for matching. BUT, I agree with Mario that for
readability's sake alone this should not be pursued. I believe that it is
fairly safe to expect people not to use characters like ^ ' * or ~ at the
beginning or end of either their tiddler titles or the text they want to
match. If one out of a Million should do this... well, bummer. Perhaps I
will allow \\ to escape a meta character in order to use it in its literal
sense.
2) You are right, Mario. The ^wordroot nomenclature is rather misleading. I
will therefore change it as you suggest to wordroot* which sure is a lot
more natural.
Thus, I would currently vote to change the meta characters like so:
^PrependToFormattersArray
-> instead of the ugly "prefix" 0!
'MatchLETTERSasis
-> a single quote would trigger matching lower and uppercase letters
exactly as defined
config*
-> the new wildcard at the end of the word instead of the beginning
~DoNotLinkify
-> to not linkify the first term but only define it as the tiddler to which
all other terms linkify ...separated by |
Keep in mind that - at the moment - the wildcard * is only intended to
serve for word endings.
It currently is not intended to be used as {wild*card} or {*card} or even
{*middle*}.
I might check as to how hard it would be to allow it both at the beginning
or at the end of a term.
Eventually, I don't think that these metacharacters should cover the full
range of what RegEx has in store, because *no one* will want to use that.
Perhaps, I can imagine another pair of metacharacters like this...
(any regex you want to be matched)
Thus, any term wrapped in parentheses is evaluated as a RegEx. However, I
am not sure that there will be many people that know how to make use of
that or even want to in the context of LinkifyPlugin.
Cheers, Tobias.
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/tiddlywiki/-/BK6qlaX4oCAJ.
To post to this group, send email to tiddlywiki@googlegroups.com.
To unsubscribe from this group, send email to
tiddlywiki+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Re: 2nd Beta of new TiddlySaver.jar with a renewed certificate
Fedora 16 with Oracle Java 1.7.0_04 ea b18 (ea = Early Access - not sure how I ended up with the ea version installed): Firefox 11.0 and luakit 2011.07.22.r1 both work fine. Mixed results under WinXP and Java 1.6.0_31: Firefox 11 - beta works fine. Chrome 18.0.1025.152 m - works with old version, but not with beta. Internet Explorer - works, but with ActiveX warning dialog when saving (I didn't spend any time trying to configure IE to permanently allow the interaction... I never use it for tiddlywiki content). XP with Java 1.7.0_03: Firefox - works fine Chrome - can't get java 7 and chrome to play nice - if anyone has it working, I'd love to know how. IE - same behavior as Java 1.6.0 On Apr 7, 7:56 am, Jeremy Ruston wrote: > If you use TiddlySaver.jar, it would be much appreciated if you could > try out the new beta. > > To use it, download this file and use it to replace your current > TiddlySaver.jar files: > > http://tiddlywiki.com/beta/TiddlySaver.jar > > Please give it a try, and leave any feedback here, > > Many thanks, > > Jeremy > > On Tue, Mar 13, 2012 at 5:43 PM, wrote: > > On Tue, 13 Mar 2012, Jeremy Ruston wrote: > > >> Yes, that was my mistake again, I was on the wrong branch. Please try > >> again now, > > > Yeah, looks right now, thanks. > > > -- > > Chris Dent http://burningchrome.com/ > > [...] > > -- > Jeremy Ruston > mailto:jeremy.rus...@gmail.comhttp://www.tiddlywiki.com -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to tiddlywiki@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Re: GetSimple theme for TiddlyWiki (needs some debugging for use with IE)
Looks great Måns, I like fonts very much and the colors. As you wrote "GetSimple" :) //Tobbe Den torsdagen den 12:e april 2012 kl. 03:13:02 UTC+2 skrev Måns: > > Hi TWWizards & Afficionados > > I made a couple of attempts to mimic GetSimple's Innovation Theme. [1] > > http://getsimple.tiddlyspot.com/ (English) > > http://xn--mns-ula.dk/TW/getsimpletw/#InnovationTheme (Danish & one- > tiddler-systemTheme) > > If you like the theme/idea and know what to fix to make it work with > IE - I'd apreciate some feedback... > > > [1] > http://get-simple.info/extend/theme/innovation-theme/104/ > http://xn--mns-ula.dk/side/ > > Ps: > I know there are more than a few css flaws in the StyleSheet tiddler - > however my skills are still pretty basic - > Please tell if you spot some obvious mistakes or unnecessary code in > the StyleSheet tiddler.. > Eventually I'd want to make this theme as simple as possible... > > > Cheers Måns Mårtensson -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To view this discussion on the web visit https://groups.google.com/d/msg/tiddlywiki/-/Nonp80-yfGgJ. To post to this group, send email to tiddlywiki@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Re: Find and Replace in all tiddlers
> for example i have links to the tiddler HardwareStore and to the > tiddler LokalFarmersMarket in a tiddlers which contains an Interview > about where People get their Plants from. Also i have somewhere some > tiddlers that are tagged with HardwareStore. > > now i decide for example, that i dont want to have two tiddlers > LokalFarmersMarket and HardwareStore but that i only want to have one > Tiddler called Market. > > so i need a "find and replace option" like it is in every editor that > doesn't care where in the tiddlywiki file the word should be replaced, > and just simply replace LokalFarmersMarket and HardwareStore into > Market everywhere. I am aware that this could destroy the tiddlywiki > System. TiddlerTweakerPlugin can be used to change text in *all* tiddlers at once. Simply select all the tiddlers from the listbox in the TiddlerTweaker control panel. Then check the [x] replace text option, enter your desired search text and the 'replace with' text, and press the 'update' button. Note that the [x]replace text function is only applied to the text content of the tiddler. To change tags, use the separate [x]tags option in TiddlerTweaker. First use the 'tags' selector (upper right above the listbox) and enter a tag value to select all tiddlers with that tag. Then, enable the [x]tags option and enter the old tag *and* new tag into the input, using the special "+" and "-" prefix symbols. For example, "-HardwareStore +Market" removes "HardwareStore" and adds "Market" to all selected tiddlers. Note also that, while TiddlerTweaker will change the *text* and/or *tags* of the selected tiddlers, it will not *automatically* rename tiddlers. However, you can use TiddlerTweaker to quickly rename individual tiddlers as well. Simply select a single tiddler from the listbox, check the [x]title option, enter a new title, and press update. enjoy, -e Eric Shulman TiddlyTools / ELS Design Studios WAS THIS ANSWER HELPFUL? IF SO, PLEASE MAKE A DONATION http://www.TiddlyTools.com/#Donations note: donations are directly used to pay for food, rent, gas, net connection, etc., so please give generously and often! 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 post to this group, send email to tiddlywiki@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Re: NEW: LinkifyPlugin - another improved version of RedirectMacro / AutoWeaving
Hi Tobias > So, now there's also LinkifyPlugin...http://linkify.tiddlyspot.com/index.html > Hope you enjoy it, You've just saved me hours and hours of tedious manual work ( http://synopse.tiddlyspace.gir.dk/ a slowly growing database of subjects/themes and texts for my students - "All Danish I'm afraid - however *very* usefull when you are a danish student and linkifyPlugin is at play "... ) THANKS A LOT!!! :-D 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 tiddlywiki@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Re: GetSimple theme for TiddlyWiki (needs some debugging for use with IE)
Hi Tobbe I like fonts very much and the colors. As you wrote "GetSimple" :) Thanks :) (Not my work - Cagintranet from http://get-simple.info/ designed it.) It's not quite as simple as I'd like it to be yet. It needs some cleaning up and fixes for IE. Fonts only work when you are online. They are embedded via the http://getsimple.tiddlyspot.com/#StyleSheetYanoneKaffeesatz tiddler. If you're offline it will "fallback" to normal fonts.. 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 tiddlywiki@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
[tw] TW5 and its style
Question about TW5. Is it going to be pushed to the public in its current style? I really don't like it, having that pop-up, scrolling, menu on the side. I was hoping TW5 would look similar to the current TW, but be much better on the back side and have that built-in editing present. Is there any way to get that? -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to tiddlywiki@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
Re: [tw] TW5 and its style
Question about TW5. Is it going to be pushed to the public in its current style? No. Intentionally, I've paid little attention to the appearance up until now, focusing instead on getting the mechanisms right that generate and refresh HTML. I've done enough styling to let me test it, but no more. Right now, it's all about the engine, and ensuring that TiddlyWik5i componentises well for inclusion in other systems (eg TiddlyWeb). I really don't like it, having that pop-up, scrolling, menu on the side. The zooming chooser on the left is highly experimental. I did it at this point to help me understand coding for touch events rather than mouse events, and to explore performance for the planned interactive features. Although the current design doesn't function properly, I'm pleased with the basic idea: making it easy to navigate to any tiddler without having to scroll the page. I was hoping TW5 would look similar to the current TW, but be much better on the back side and have that built-in editing present. Is there any way to get that? That is still pretty much the plan, in particular the improved internals. I'm using Twitter Bootstrap for styling at the moment, which gives a fairly basic aesthetic of its own. I hope to significantly declutter the basic user interface, but keep the basic idea of making it easy to interact with lots of tiddlers at once. By 'built in editing' do you mean WYSIWYG editing? Besides the things you mention, I think some other significant features of TW5 for end users are: - elevating bitmap and vector graphics to be first class citizens alongside textual tiddlers, allowing editing, transclusion and linking in the same way - JSON tiddlers for data - being able to run under node.js to break out of the constraints imposed by the browser. You'll be able to run TW5 as a personal web server - expanded wikitext and filter syntax Thanks for your interest, Best wishes Jeremy -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to tiddlywiki@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to tiddlywiki@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
[tw] EditSectionsPlugin + FoldHeadingsPlugin
Is there any way to implement both plugins simultaneously? Right now the <> clickable region covers the <> "edit..." button. The "edit..." button is visible but selecting it only fires the <> event. As opposed the the "edit..." link being immediately to the right of the heading text, could it be moved to the right of "more..." label or to the left of the heading text (with a negative margin-left)? Maybe a hack involving embedding in a table could be made to work but that certainly wouldn't be elegant. Suggestions? Thanks. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To view this discussion on the web visit https://groups.google.com/d/msg/tiddlywiki/-/SPpWt_PA9vsJ. To post to this group, send email to tiddlywiki@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Re: NEW: LinkifyPlugin - another improved version of RedirectMacro / AutoWeaving
On Apr 12, 6:44 pm, Tobias Beer wrote:
> The current discussion might be a bit misleading in that I started by using
> the term "prefix" and now you are talking about suffixes too.
hihi,
one finger is not enough, we'll take the hand.
> Thus, I would currently vote to change the meta characters like so:
>
> ^PrependToFormattersArray
> -> instead of the ugly "prefix" 0!
Do you have a special usecase, where it is necessary to put a user
defined formatter in front of the core formatters. I personally think,
this will only cause support requests because of broken core
formatting. Just my opinion.
I do like the other suggestions.
> Keep in mind that - at the moment - the wildcard * is only intended to
> serve for word endings.
that's what I thought.
> It currently is not intended to be used as {wild*card} or {*card} or even
> {*middle*}.
> I might check as to how hard it would be to allow it both at the beginning
> or at the end of a term.
I'd give that low priority.
A fast shot regexp for {wild*card} looks like: [\s](wild.*?card)[\s]
{*card} will be harder to create and imo
{*middle*} is a killer because of missing start and end definitions
(at least at 1am ;)
> Eventually, I don't think that these metacharacters should cover the full
> range of what RegEx has in store, because *no one* will want to use that.
I'd not implement this, until someone can name a really good reason
why s/he needs it :)
-mario
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To post to this group, send email to tiddlywiki@googlegroups.com.
To unsubscribe from this group, send email to
tiddlywiki+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Re: EditSectionsPlugin + FoldHeadingsPlugin
Put another way: my goal is to be able to expand/collapse headings AND edit each heading as a section. I prefer to manage fewer tiddlers so each tends to contain a lot of content. I prefer to edit small chunks of content in a single tiddler. These preferences are mutually exclusive. I currently use NestedSliderPlugin for expand/collapse of large sections of content (sometimes inline, sometimes embedded (smaller) tiddlers) but EditSectionsPlugin doesn't see any content for a section that is wrapped within NestedSliderPlugin. Mystery, conundrum, enigma, etc. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To view this discussion on the web visit https://groups.google.com/d/msg/tiddlywiki/-/r1zi1i4QMEwJ. To post to this group, send email to tiddlywiki@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Re: NEW: LinkifyPlugin - another improved version of RedirectMacro / AutoWeaving
Now, that's a done, done and... done! Check out the new version 0.9.5: http://linkify.tiddlyspot.com/#%5B%5BVersion%20History%5D%5D For the lazy bunch, these are the changes: > changed (prefixes to) modifiers - 0! is removed and replaced with ^ - to mark a tiddler to be prepended to the formatters array you now use the modifier ^ - ^ is replaced with * whereas wildcards are supported as both a prefix or a suffix to a *term*! > the sequence of modifiers (previously prefixes) is no longer of any relevance and can be freely assigned> you can now escape a *definition* termvia \\ and thus interrupt modifier detection for prefixes> in the rare case where you also want to prevent modifier detection for the very last suffix in the *configuration*, use \\ at the end of a term> refactoring -> sanitize () Enjoy! Tobias. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To view this discussion on the web visit https://groups.google.com/d/msg/tiddlywiki/-/jkPANl-CZ8IJ. To post to this group, send email to tiddlywiki@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Re: NEW: LinkifyPlugin - another improved version of RedirectMacro / AutoWeaving
Great to hear (from you) Mans! I am quite sure that all this work in the end is sure going to pay off for someone. :-D Cheers, Tobias. Am Donnerstag, 12. April 2012 20:47:45 UTC+2 schrieb Måns: > > Hi Tobias > > > So, now there's also LinkifyPlugin... > http://linkify.tiddlyspot.com/index.html > > > Hope you enjoy it, > > You've just saved me hours and hours of tedious manual work > > ( http://synopse.tiddlyspace.gir.dk/ a slowly growing database of > subjects/themes and texts for my students - "All Danish I'm afraid - > however *very* usefull when you are a danish student and linkifyPlugin > is at play "... ) > > THANKS A LOT!!! :-D > > Cheers Måns Mårtensson -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To view this discussion on the web visit https://groups.google.com/d/msg/tiddlywiki/-/EACjW43ntaMJ. To post to this group, send email to tiddlywiki@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Re: Grounded Theory Coding
Haven't thought about that yet... will give the idea some thought. To begin with, I thought it were meaningful to separate #tags from other tags or tiddlers... or to even allow "#tag" as tiddler titles. Probably a twitter willl eventually be best. The easiest thing would be to just provide a link to the actual tiddler from the search results. Tobias. Am Donnerstag, 12. April 2012 00:36:39 UTC+2 schrieb Niklas Wagner: > > > if a #tag is a # and a already existing TidllerTitle then it doesent > become a tag? > > I dont know if it is so useful to make a distinction between hastags > and tiddlers. i mean when i tag something with #compost the tiddler > "compost" should be connected with it. the concept that a tag is a > tiddler is so simple and powerful. didnt TaggelyTagging introduce that? > (i dont know, because i only found tiddlywiki in 2008) > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To view this discussion on the web visit https://groups.google.com/d/msg/tiddlywiki/-/tUohqzseQOwJ. To post to this group, send email to tiddlywiki@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Re: NEW: LinkifyPlugin - another improved version of RedirectMacro / AutoWeaving
Please forget my configurability suggestion, it was a misunderstanding
on my part. (..but, in cased the post at 11:11 was missed, I do think
that "zoOM" is more natural than 'zoOM ).
Here are some other thoughts:
1) How would you linkify a common multiple word root such as snow
board (snow boarding, snow boarder, snow boarders etc)?
2) Regarding ^ or 0!, if I understand it correctly, the purpose is to
first locally disable the CamelCase linking feature and apply linkify
instead.
If LinkifyPlugin is used, is there actually any need for the CC
linking feature? Please let me explain:
I use CC almost exclusively for one thing, ie. choosing a tiddler name
that AVOIDS forcing me to use [[ ]] later on. That, actually, is
pretty much it. If I didn't have to take this into consideration, I'd
gladly skip it. There is one more common *occurence* of the CC which
is an incidental (accidental?) one - namely when you write a text and
only later realize that "ah, darn, that was apparently a CC word...
gotto add ~". That is CORRECTING a mistake, which is at par with
AVOIDING, if now worse.
...my point? Well, just maybe it makes sense with an option (a
checkbox?) in LInkifyPlugin to turn off CC. If links are automatically
created with linkify, particularly for/to tiddler names, then I see
little point with the whole CC issue. Obviously(?) anyone can still
write things in CC format and if Linkify is later disabled then I
presume the CC feature would be activated again.
<:-)
On Apr 12, 6:44 pm, Tobias Beer wrote:
> Hello twgrp and PMario,
>
> The current discussion might be a bit misleading in that I started by using
> the term "prefix" and now you are talking about suffixes too.
>
> In fact, these characters are rather meta characters, switches or flags.
>
> 1) They could be configurable since they (currently) do not end up in the
> regex that is used for matching. BUT, I agree with Mario that for
> readability's sake alone this should not be pursued. I believe that it is
> fairly safe to expect people not to use characters like ^ ' * or ~ at the
> beginning or end of either their tiddler titles or the text they want to
> match. If one out of a Million should do this... well, bummer. Perhaps I
> will allow \\ to escape a meta character in order to use it in its literal
> sense.
>
> 2) You are right, Mario. The ^wordroot nomenclature is rather misleading. I
> will therefore change it as you suggest to wordroot* which sure is a lot
> more natural.
>
> Thus, I would currently vote to change the meta characters like so:
>
> ^PrependToFormattersArray
> -> instead of the ugly "prefix" 0!
>
> 'MatchLETTERSasis
> -> a single quote would trigger matching lower and uppercase letters
> exactly as defined
>
> config*
> -> the new wildcard at the end of the word instead of the beginning
>
> ~DoNotLinkify
> -> to not linkify the first term but only define it as the tiddler to which
> all other terms linkify ...separated by |
>
> Keep in mind that - at the moment - the wildcard * is only intended to
> serve for word endings.
> It currently is not intended to be used as {wild*card} or {*card} or even
> {*middle*}.
> I might check as to how hard it would be to allow it both at the beginning
> or at the end of a term.
>
> Eventually, I don't think that these metacharacters should cover the full
> range of what RegEx has in store, because *no one* will want to use that.
>
> Perhaps, I can imagine another pair of metacharacters like this...
>
> (any regex you want to be matched)
>
> Thus, any term wrapped in parentheses is evaluated as a RegEx. However, I
> am not sure that there will be many people that know how to make use of
> that or even want to in the context of LinkifyPlugin.
>
> Cheers, Tobias.
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To post to this group, send email to tiddlywiki@googlegroups.com.
To unsubscribe from this group, send email to
tiddlywiki+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Re: EditSectionsPlugin + FoldHeadingsPlugin
Hi Craig
I made my own way around not being able to style the foldheadings-
thing:
EditSectionPlugin + FoldheadingsPlugin and SectionLinksPlugin (most
notably the toc-feature)
I expanded the SectionToc with EditSection macros like this:
config.macros.sectionTOC = {
targetClass: 'sectionTOC',
handler:
function(place,macroName,params,wikifier,paramString,tiddler) {
var out=[];
var targetClass=params[0]||this.targetClass;
var t=story.findContainingTiddler(place); if (!t) return;
var elems=t.getElementsByTagName('*');
var level=5; // topmost heading level
for (var i=0; i>';
switch(elems[i].nodeName) {
case 'H1': out.push('#'+link);
level=1; break;
case 'H2': out.push('##'+link);
level=level<2?level:2; break;
case 'H3': out.push('###'+link);
level=level<3?level:3; break;
case 'H4': out.push(''+link);
level=level<4?level:4; break;
case 'H5': out.push('#'+link);
level=level<5?level:5; break;
default: if (hasClass(elems[i],targetClass))
var target=elems[i];
}
}
// trim excess bullet levels
if (level>1) for (var i=0; ihttp://puppy.tiddlyspace.gir.dk/#[[clone%20bootable%20USB%20stick]]
You'll have to find a way to invoke a fake editmode to actually see
the editSection buttons in the TOC...
Cheers Måns Mårtensson
On 13 Apr., 01:28l, Craig in Calgary wrote:
> Put another way: my goal is to be able to expand/collapse headings AND edit
> each heading as a section. I prefer to manage fewer tiddlers so each tends
> to contain a lot of content. I prefer to edit small chunks of content in a
> single tiddler. These preferences are mutually exclusive. I currently use
> NestedSliderPlugin for expand/collapse of large sections of content
> (sometimes inline, sometimes embedded (smaller) tiddlers) but
> EditSectionsPlugin doesn't see any content for a section that is wrapped
> within NestedSliderPlugin. Mystery, conundrum, enigma, etc.
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To post to this group, send email to tiddlywiki@googlegroups.com.
To unsubscribe from this group, send email to
tiddlywiki+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/tiddlywiki?hl=en.
[tw] Re: 2nd Beta of new TiddlySaver.jar with a renewed certificate
After thoroughly cleaning out all traces of java, I got 1.7.0ea19 working just fine under XP & Chrome (firefox and IE as well), but the new TiddlySaver.jar still doesn't work under chrome. The old one still works though, if you accept running it with the expired cert. On a side note - any idea why the new jar is 12K vs 5K in size? On Apr 12, 1:11 pm, perlguy wrote: > XP with Java 1.7.0_03: > > Chrome - can't get java 7 and chrome to play nice -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to tiddlywiki@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
Re: [tw] Re: A couple of Newbie Questions
ok so the following works but only if you put the tag in the tag field, I
still want to create an alias that does the same thing but can't figure out
how to apply css styling :
[[StyleSheet]]
.nobullets li {
list-style-type: none;
margin-left:-2em;
}
{{nobullets{<>}}}
Where 201203210105 is the tag. If anyone knows a better way that doesn't
require css styling, maybe something that can be put into an alias I would
appreciate it. Anyone?
On Wed, Apr 11, 2012 at 8:56 PM, andrew.j.harrison84 <
andrew.j.harriso...@gmail.com> wrote:
> I think the intent of this tread was to automatically change all the links
> in the wiki pointing back to a tiddler when you change the title. I have
> been using transclusion but to slices in another tiddler. Would it be
> possible to transclude or create a link to a tiddler using say it's created
> date which doesn't change but still have it display the title for that
> tiddler. I want a link that goes and gets what to display using existing
> core functions and not a plugin. Something like {{nobullets{< [tag[201203210105]]>>}}} but with created instead of tag. I guess you could
> put the created date in as a tag but this makes me wonder if there would be
> able to create an alias that you could then put something like <>
> where $ is the tag or something like < {{"\{\{nobullets\{\<\\>\}\}\}"}}>>. Anybody?
> On Apr 9, 2012 9:37 AM, "Måns" wrote:
>
>> Hi Andrew
>>
>> > It would be nice if we could use a transclusion in the title field
>> unless
>> > it is possible and I jusr don't know how.
>>
>> The view macro [1] *can* wikify macro calls etc:
>>
>> If you change the ViewTemplate from:
>>
>> to:
>>
>>
>> then it will wikify whatever is written in the slice "Slice" in the
>> current tiddler.
>>
>> Cheers Måns Mårtensson
>>
>>
>> [1] http://tiddlywiki.org/#[[view%20macro%20types]]
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "TiddlyWiki" group.
>> To post to this group, send email to tiddlywiki@googlegroups.com.
>> To unsubscribe from this group, send email to
>> tiddlywiki+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/tiddlywiki?hl=en.
>>
>>
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To post to this group, send email to tiddlywiki@googlegroups.com.
To unsubscribe from this group, send email to
tiddlywiki+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/tiddlywiki?hl=en.
