[tw] Re: Question: Changing the tooltip font size?
hi this seems to be a browser setting. A short google search with firefox tooltip font size for FF gave some info. this seems to be interesting: http://userstyles.org/styles/8558 -m On Nov 17, 11:21 pm, Shankar shankar.sw...@gmail.com wrote: Hello, Is there a way to change the size of the fonts used for tooltip text? In particular, I am interested in increasing the font size of the tooltip text displayed in: [img[tooltip|path/to/filename.jpg][path/to/filename.jpg]] Thanks! Cheers; 'best, shankar swamy -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@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: Blank Tiddlyspace because I changed pre/post header/body
Thanks! Fixed. When logged in I had changed private MarkupPreBody. Using filter I could get the wiki to show when logged in and then delete that tiddler. F: I use Linux and would like to see example of cURL command. That would be useful. Daniel On 16 Nov, 12:52, rakugo jdlrob...@gmail.com wrote: Another thing you can consider doing is filtering out the offending tiddlers from your space.. http://dadi.tiddlyspace.com/?select=title:!MarkupPreHeadselect=title... will return your space with all tiddlers except MarkupPreHead and MarkupPostBody for example. Jon On Nov 16, 10:17 am, FND f...@gmx.net wrote: My mistake. I pasted in content in the pre/post header section that caused my tiddlyspace dadi.tiddlyspace.com to go blank. Can I delete those tiddlers and restore the view? Not even backstage shows. dadi.tiddlyspace.com looks fine to me - have you fixed it already? Perhaps try a force refresh? This might be of interest:http://groups.google.com/group/tiddlywiki/msg/b68fd8787528d69d You might also use TiddlyWebCommander to change the respective tiddler:http://commander.tiddlyspace.com However, since you don't have access to the backstage, including this now is gonna be tricky. What's your browser and operating system? If you're comfortable using the Unix command line, a few cURL commands would do the trick if you know what you need to delete. -- F. -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@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: Search - returning matching lines across all tiddlers
Hi Anthony On Nov 18, 1:40 am, Anthony Muscio anthony.mus...@gmail.com wrote: The options within tiddlywiki are virtually infinite. The point I am making is the value of content in tiddler size bites linked by tags is very powerful where as resorting to content loaded tiddlers is more limited. You are right. At the moment tag based todo lists are very powerfull. But it is different to, what Andrew wants. Imo Andrew's approach is quite interesting. It creates actions, todos ... while writing, which doesn't interrupt the flow of writing. It gets the todo out of your mind immideately, and it preserves the context, why a todo is needed. So you are free to concentrate, what is discussed in the meeting. You don't have to remember 27 todos. And at the end of the meeting you may remember the most important 3 (My most important 3 because my brain filters that way :)). I use GotoPlugin + SearchOptionPlugin from tiddlytools.com Then I open several tiddlers, which I think contain the text that I'am searching for, and use the browsers full text search and highlight capabilities. Which is a 3 step method, and sometimes annoying. A new plugin with a slightly formated full text output would be very interesting. And a one step method :) -mario -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@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: Search - returning matching lines across all tiddlers
How about using slices? That way, you can easily pull up all the todo or action slices (i.e. whole lines). w On Nov 18, 9:43 am, PMario pmari...@gmail.com wrote: Hi Anthony On Nov 18, 1:40 am, Anthony Muscio anthony.mus...@gmail.com wrote: The options within tiddlywiki are virtually infinite. The point I am making is the value of content in tiddler size bites linked by tags is very powerful where as resorting to content loaded tiddlers is more limited. You are right. At the moment tag based todo lists are very powerfull. But it is different to, what Andrew wants. Imo Andrew's approach is quite interesting. It creates actions, todos ... while writing, which doesn't interrupt the flow of writing. It gets the todo out of your mind immideately, and it preserves the context, why a todo is needed. So you are free to concentrate, what is discussed in the meeting. You don't have to remember 27 todos. And at the end of the meeting you may remember the most important 3 (My most important 3 because my brain filters that way :)). I use GotoPlugin + SearchOptionPlugin from tiddlytools.com Then I open several tiddlers, which I think contain the text that I'am searching for, and use the browsers full text search and highlight capabilities. Which is a 3 step method, and sometimes annoying. A new plugin with a slightly formated full text output would be very interesting. And a one step method :) -mario -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@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: Blank Tiddlyspace because I changed pre/post header/body
I use Linux and would like to see example of cURL command. It's pretty simple - for example, to delete a tiddler Foo from my private bag, I would use the following: $ curl -v -u fnd:mypassword -X DELETE \ http://fnd.tiddlyspace.com/bags/fnd_private/tiddlers/Foo There are more examples listed here: http://tiddlyweb.peermore.com/wiki/#curl We'd be happy to provide more details on the TiddlyWeb mailing list: http://groups.google.com/group/tiddlyweb -- F. -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@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: Facebook Like button for individual tiddlers
1) Last time I looked encodeURIComponent does not encode URLs in a sufficient manner. For example, it does not turn [] into corresponding entities. Therefore, tiddler titles with blank spaces might fail ...at least worth testing (again). On the other hand... I think it should actually be facebook's serverside that does the propper encoding... assuming that any non-standard characters in the url component are NOT eaten up for some security reason. 2) Trying TiddlyWiki URL's with [1] seems to work when pasted from the chrome address bar. However, the same URL - above all, any special characters in it - might look quite different in firefox, ie or opera. 3) Probably overkill, but maybe there's a url shortening service outthere that would allow (via xhr) to shorten url's which contain hashes, umlaute, brackets, etc. For performance reasons (on both ends), such a request should definetely only be fired, whenever a user clicks on the button, not when tiddlers load ...which means that some indication of please waitor error handling might be of need. Obviously, this would obfuscate the actual destination of the link and possibly mess with facebooks statistics as to how many people like the actual destination's url, e.g. people using their own shareaholics (or other) instead of your like button. X) All in all, I would tend to believe that the problem entirely lies in (incredibly huge) browser differences as for encoding uri's. There just does not seem to exist some agreed upon standard as to how (and when) url's are to be properly encoded ...which kind of sucks. On the other hand, encodeURIComponent does not harmonize crucial characters (yet) ...such that url's can be generated inside TW which would work across all major browsers... unless we're talking urls which do not contain a lot more than latin, alphanumeric characters. Cheers, Tobias. [1] http://developers.facebook.com/docs/reference/plugins/like -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@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: Blank Tiddlyspace because I changed pre/post header/body
Fantastic! Thanks a lot. On 18 Nov, 10:51, FND f...@gmx.net wrote: I use Linux and would like to see example of cURL command. It's pretty simple - for example, to delete a tiddler Foo from my private bag, I would use the following: $ curl -v -u fnd:mypassword -X DELETE \ http://fnd.tiddlyspace.com/bags/fnd_private/tiddlers/Foo There are more examples listed here: http://tiddlyweb.peermore.com/wiki/#curl We'd be happy to provide more details on the TiddlyWeb mailing list: http://groups.google.com/group/tiddlyweb -- F. -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@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] {{{ }}} alternative - make a div act like a pre
Hi, i was searching for a solution to my problem and i found this
discussion:
http://groups.google.com/group/tiddlywiki/browse_thread/thread/83d03dce6af33cad/af7bbc8807ab9279
What i needed was something different from the classic {{{ }}} markup
to replicate the functions of the others wiki around.
The user PMario came with a solution. Use a markup like this:
{{command{
your text here
}}}
Adding the following to the TW StyleSheet Tiddler:
/*{{{*/
.command {
background-color: #F9F9F9;
border: 1px dashed #2F6FAB;
color: black;
font-family: Courier New, Courier, mono;
font-size: 12px;
font-style: italic;
line-height: 1.1em;
padding: 1em;
margin: 0 0 0.8em;
}
/*}}}*/
That markup creates a div/div, formatting it like on common wikis.
The only problem was the text not correctly indented. I asked PMario,
who came with another solution, adding the following string to
the .command css class above:
white-space: pre;
In this way you can use different divbox to enhance the visualization
of things like code, command-line output, file-content, etc...
I hope this will be useful for someone. Thanks to the kindest PMario!
--
You received this message because you are subscribed to the Google Groups
TiddlyWiki group.
To post to this group, send email to tiddlyw...@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] Announcement of 2.6.2 beta release of TiddlyWiki
I'm pleased to announce the TiddlyWiki 2.6.2 beta release. This release consists of a number of minor usability and hackability enhancements, as described at http://trac.tiddlywiki.org/wiki/History, and one fairly major enhancement. The major enhancement is the addition of persistent options, also known as 'baked cookies'. This is the ability of TiddlyWiki to store some of its options in a tiddler, the SystemSettings tiddler, so that these options are retained even if the user deletes all their cookies, or moves the TiddlyWiki to another computer. The persistent options are more fully described at: http://tiddlywiki.com/beta/#PersistentOptions We are soliciting feedback about Persistent Options as part of this beta release, in particular: 1) Which options do you think should be persistent, and which options should be in cookies? 2) Do you think the persistent options have been explained properly, and do you have any suggestions to improve the explanation? 3) Which should take precedence a persistent option or a cookie? That is should a persistent option overwrite an option previously set in a cookie, or should the cookie value take precedence? This has been the subject of some discussion, and we are by no means sure which is the better option. In the beta the persistent option overwrites the cookie option. Note that for a standalone TiddlyWiki, the impact of the difference in precedence is not that great, but for TiddlySpace the impact is more significant: it means an option set locally by a user in a cookie can be overwritten by another user of the TiddlySpace, if that option is persistent. Martin -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@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: Announcement of 2.6.2 beta release of TiddlyWiki
That's great! Which options do you think should be persistent, and which options should be in cookies? This depends on the use of TW. If it's a document for myself, most of things should be backed, including authorName, autoSave, RegExpSearch, probably sliders' states. AutoSave is most important since some browsers (including Opera) don't notify when you close a tw- document without saving. On the other hand, if TW is used as a site (or part of a site) most of them should be cookie-based because they are for users. Which should take precedence a persistent option or a cookie? That is should a persistent option overwrite an option previously set in a cookie, or should the cookie value take precedence? I think this worths adding one more option. If you do so, when TW is used just by the author, it should be set so that backed ones are precedence. For use as a site, it's just switching that option that's enough to work it properly. Now, let's consider a situation if a tw-document is used by a team of editors. This goes more complicated. I think each author should have some structure describing his or her preferences, like a author_name_SystemSettings tiddler (and perhaphs group_name_SystemSettings). The thing is, TW should somehow recognize the author. This can be done either manually (by some sort of authentication) or automatically (based on cookies, I guess). As for now, I don't see any beatiful solution.. On 18 ноя, 16:06, Martin Budden mjbud...@gmail.com wrote: I'm pleased to announce the TiddlyWiki 2.6.2 beta release. This release consists of a number of minor usability and hackability enhancements, as described athttp://trac.tiddlywiki.org/wiki/History, and one fairly major enhancement. The major enhancement is the addition of persistent options, also known as 'baked cookies'. This is the ability of TiddlyWiki to store some of its options in a tiddler, the SystemSettings tiddler, so that these options are retained even if the user deletes all their cookies, or moves the TiddlyWiki to another computer. The persistent options are more fully described at: http://tiddlywiki.com/beta/#PersistentOptions We are soliciting feedback about Persistent Options as part of this beta release, in particular: 1) Which options do you think should be persistent, and which options should be in cookies? 2) Do you think the persistent options have been explained properly, and do you have any suggestions to improve the explanation? 3) Which should take precedence a persistent option or a cookie? That is should a persistent option overwrite an option previously set in a cookie, or should the cookie value take precedence? This has been the subject of some discussion, and we are by no means sure which is the better option. In the beta the persistent option overwrites the cookie option. Note that for a standalone TiddlyWiki, the impact of the difference in precedence is not that great, but for TiddlySpace the impact is more significant: it means an option set locally by a user in a cookie can be overwritten by another user of the TiddlySpace, if that option is persistent. Martin -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@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] Fields - what are they?
The question arised after considering tag-based CSS and some other aspects. How should I think of fields (or, what are they actually)? 1.1 Are they a part of the object model of TW only? Or they must have some DOM representation? 1.2 Is there a field generated for references? If not, why? Is it a part of another table in the relational database? 1.3 Is it true that TW has core mechanisms (simple API) for search based on fields? Some answers can be found in [1], but I'm looking for the concepts, more general answers than yes and no. Also, I have some questions about Filters that were extended in TW 2.6.2 [2]. 2.1. The first one is about set algebra. We can make a filter that sets a set of tiddlers with tag1 or tag2: list filter [tag[transcluded]] [tag[examples]] (in TW v2.6.1) but is there a syntax for defining an intersection of sets (tiddler with tag1 and tag2)? 2.2. Do the filters implement regular expressions search? If so, what syntax do the use? [1] http://tiddlywiki.org/wiki/Tiddler_Fields [2] http://trac.tiddlywiki.org/ticket/1261 Thanks in advance, Yakov. -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@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: CSS of macros?
Well, the :hover pseudo-class is one of the things I'm looking for. As for mouseclicking.. I forgot what the focus means but the example shows that it's somewhat like onclick. Yeah, thanks, this is actually enough since there's no need to inspect this, just if it looks not properly, we can set it manually. On 13 ноя, 23:55, PMario pmari...@gmail.com wrote: On Nov 12, 6:36 pm, Yakov yakov.litvin.publi...@gmail.com wrote: However, it doesn't allow me to study which styles are applied after onClick, onFocus and ~onUnfocus (I don't remember how it is called). Some JavaScript controls this, but I haven't got how to inspect this. Do you meanhttp://www.w3schools.com/css/css_pseudo_classes.asp Inspecting this is tricky. I don't know. -m -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@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: Tag-based CSS?
This is amazing, thanks a lot. This also leads to a question about fields, and I'll make a new thread for this. https://groups.google.com/group/tiddlywiki/browse_thread/thread/29742f8a233b806e?hl=ru On 14 ноя, 15:49, Eric Shulman elsdes...@gmail.com wrote: On Nov 14, 4:19 am, colmjude colmj...@gmail.com wrote: You can also use the ThemedTiddlerPlugin that looks for a theme field set on a tiddler. TaggedTemplateTweak already does this, using a field named 'template' (you can also config the plugin to use a different field name). This is good to use if you want to change the structure of the tiddler as well as the style of it. Indeed... that is precisely what TaggedTemplateTweak does. It allows you to specify alternative templates (i.e, the tiddler *structure*) for any tiddler, by using a three-tiered fallback as a *prefix* on ViewTemplate/EditTemplate: first the tiddler's title is tried, then the value from a custom 'template' field (if present), and then tag values (one at a time) Thus, a tiddler named TiddlerTitle can have a unique alternative *structure* (and styles, of course), simply by creating: TiddlerTitleViewTemplate TiddlerTitleEditTemplate If no corresponding title-specific templates are defined, and the tiddler has a 'template' field with a value of FieldValue, then it will use: FieldValueViewTemplate FieldValueEditTemplate If there is still no matching template(s) found, then each *tag* of the tiddler is tried, in turn, as a prefix: TagValueViewTemplate TagValueEditTemplate for more details, see: http://www.TiddlyTools.com/#TaggedTemplateTweak http://www.TiddlyTools.com/#TaggedTemplateTweakInfo enjoy, -e Eric Shulman TiddlyTools / ELS Design Studios -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@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] small CSS bug
Hi, while experimenting with CSS in TW I figured out somewhat like a bug. How to reproduce it: make a tiddler A with CSS other than than StyleSheet (or core StyleSheets); include it into the StyelSheet, change CSS in A. What happens: CSS is not changed until I open the StyleSheet in editMode and close it. Or restart TW. This was tried in Opera (9.64) and FireFox (somewhat latest version). Is this a bug or I do something wrong? Yakov. -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@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: Fields - what are they?
2.1. The first one is about set algebra. We can make a filter that sets a set of tiddlers with tag1 or tag2: list filter [tag[transcluded]] [tag[examples]] (in TW v2.6.1) but is there a syntax for defining an intersection of sets (tiddler with tag1 and tag2)? For full Boolean logic (and/or/not plus parens as needed), you can use: http://www.TiddlyTools.com/#MatchTagsPlugin It extends the core's syntax so that instead of using a single tag value: [tag[tagvalue]] you can use a Boolean tag 'expression': [tag[tag1 OR tag2 OR (tag3 AND NOT tag4)]] The plugin also provides a public API: store.getMatchingTiddlers(expr,sort,tids) where: expr is a text string containing the boolean tag expression sort is a tiddler fieldname to sort by (default=title) tids is an array of tiddlers to search (default=search ALL) note: both sort and tids are OPTIONAL arguments. Most of the time, these are omitted, and you can simply write: var result=store.getMatchingTiddlers(expr) as in: var result=store.getMatchingTiddlers(tag1 or tag2 and not tag3) enjoy, -e Eric Shulman TiddlyTools / ELS Design Studios -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@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: small CSS bug
make a tiddler A with CSS other than than StyleSheet (or core StyleSheets); include it into the StyelSheet, change CSS in A. What happens: CSS is not changed until I open the StyleSheet in editMode and close it. Or restart TW. This is a 'design weakness' of the current stylesheet handling. Because you can *nest* embedded CSS from other tiddlers, the Stylesheet definition is recursively retrieved, replacing the embedded [[TiddlerName]] references with their respective content. Only after all the content has been retrieved is the entire block handed to the brower and applied to the current rendered content. There is a TW core 'notification' mechanism that can automatically trigger a function whenever a given tiddler is changed. When [[StyleSheet]] is changed, it (and all the embedded CSS) is re- applied. However, as you noted, if a nested tiddler is changed, the notification for *StyleSheet* does not occur. Of course, there is a notification for the actual tiddler that was changed, but that tiddler has not been 'registered' with the core, so no side-effect CSS processing is triggered. To make nested tiddlers re-apply as you want, it would be necessary, during the recursive expansion of the CSS source, to collect the names of the all the tiddlers whose content is being embedded, and then register notifications for each of these tiddlers. One issue is that this could lead to a great deal of overhead processing if a lot of small CSS 'fragments' are used. Another potential problem is that, when switching themes, a lot of 'cleanup' work would be needed to *reset* the notifications on the currently used CSS tiddlers, before switching themes and then adding notifications for all the CSS tiddlers used by the new theme. Lastly, the lack of notifications for nested CSS tiddlers is, in general, only a minor problem that occurs while you are adjusting your CSS definitions. Once you have gotten the styles the way you want, it is unlikely that the StyleSheet (and nested CSS tiddlers it references) will be changing much at all. In any case, if you can live with a one-click *semi-manual* solution, you can put this bit of HTML into your document: htmla href=javascript:; onclick=story.switchTheme(config.options.txtTheme)refresh styles/ a/html It creates a 'command link' that, when clicked, forces the core to re- process the currently loaded systemTheme, which re-applies the StyleSheet (and, of course, any nested CSS it references). While not a totally automatic solution, it is just ONE click, and it does avoid having to 'touch' (edit/done) the [[StyleSheet]] just to apply the CSS changes made in another tiddler. enjoy, -e Eric Shulman TiddlyTools / ELS Design Studios -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@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: Fields - what are they?
Hi Yakov, You are busy tweaking :) On Nov 18, 5:55 pm, Yakov yakov.litvin.publi...@gmail.com wrote: 1.1 Are they a part of the object model of TW only? Or they must have some DOM representation? It is part of the TW meta data model. You can open a vanilla tw at http://tiddlywiki.com and __view the source__. Then search for div title= and you will see a tiddler source. There are some fields: modified, modifier ... These are standard tw fields. Programmers are able to create so called custom fields which look exactly like the standard fields. 1.2 Is there a field generated for references? If not, why? Is it a part of another table in the relational database? If you click the button references the list is dynamically created. There is no database model involved, in plain/vanilla tiddlywiki. There is a database for TiddlyWeb/TiddlySpace. But it is used as a storage only. You have no direct access to this database. TiddlyWiki client side is allways the same. 1.3 Is it true that TW has core mechanisms (simple API) for search based on fields? if you look at list macro it is simple list filter [tag[myTag]] [sort[modified]] Some answers can be found in [1], but I'm looking for the concepts, more general answers than yes and no. Also, I have some questions about Filters that were extended in TW 2.6.2 [2]. As described above. list filter [tag[myTag]] was possible because there was core code for it. but eg: list filter [tag[myTag]] [template[myListTemplate]] wasn't very easy to create. The new extension to the core, makes it much easier now, _for developers_ to add functions like the [template[]] which may be used to have custom list output formats. 2.1. The first one is about set algebra. We can make a filter that sets a set of tiddlers with tag1 or tag2: list filter [tag[transcluded]] [tag[examples]] (in TW v2.6.1) but is there a syntax for defining an intersection of sets (tiddler with tag1 and tag2)? see Erics post. 2.2. Do the filters implement regular expressions search? If so, what syntax do the use? The core doesn't. I made some plugins, that implement regular expression filtering. I don't know, how much JavaScript you know. But you can have a look at my Plugin sources at [1] Start with: NoCaseListPlugin .. its the easiest. NumberedTextListPlugin .. next XCaseListPlugin .. many possibilities but more complicated. all these plugins extend the core list macro. instead of list filter you can use list numberedText -title so filter is replaced by numberedText + parameters. === Since at the time I wrote the macros, I didn't fully understand how to extend the [tag[]] core mechanism, and I didn't want to totally hijack the list macro, I created my own parameter syntax, which is different to the core. Now I am thinking about to rewrite these macros and use the new core extension mechanism. eg: list filter [regExp[]] would be much easyer now. === If you need information, how the core builds its functions use Erics insideTW [2], which helped me a lot. You wrote: Some answers can be found in (http://tiddlywiki.org/wiki/Tiddler_Fields), but I'm looking for the concepts, more general answers than yes and no. All of the above is heavily dev related. So depending on your scripting skills it may be sometimes frustrating to get the overview. Be carefull :) If this information was too specific tell me, and I'll move back one step. -mario [1] http://apm-plugins.tiddlyspot.com/#XCaseListPlugin%20NumberedTextListPlugin%20NoCaseListPlugin [2] http://www.tiddlytools.com/insideTW/ -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@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: Fields - what are they?
There is a FieldsEditorPlugin [1], which may be of interest. Guessing, one of you next questions would be, who to tweak them :) [1] http://visualtw.ouvaton.org/VisualTW.html#FieldsEditorPlugin -m -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@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] Launching programs and folders from MPTW
Can anyone tell me how to get the LaunchApplicationPlugin or something similar working in MPTW. I've gone here http://remotely-helpful.com/TiddlyWiki/LaunchApplication.html#LaunchApplicationPlugin and picked up the tiddler but I can't get it to work. Thanks, Ohrange -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@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: Announcement of 2.6.2 beta release of TiddlyWiki
My suggestion would be that as part of the implementation of persistent (Baked) cookies, consideration be given to including the current file name as part of the cookie ids. I realize not everyone uses multiple open TW files at the same time, but the many uses of cookies in TW currently means that the same cookies are affecting multiple files. I may well want my sidebar hidden in one file but want it open in another. I often use separate TW files to keep separate what would otherwise be one large, slow file, at work, for example, my addressbook, my work diary, my primary collection of links, and my collections of technology notes. Even the username might vary between someone's personal files and a team-based TW file. I'm reasonably sure there would be others with similar needs for distinct cookies between TW files. My suggestion on precedence for identically named cookies would be for the persistent ones to be of lower priority than the session cookies. This would allow the same values at start as were valid at the beginning of the previous session (if the persistent cookies in the tiddlers were not changed and saved during that session) while allowing them to be changed for the session. -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@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: Launching programs and folders from MPTW
G'day Browser security constraints are still in effect. You can only launch programs from folders or sub-folders of the home of the tiddlywiki you are running it from. The following buttons work in Linux Firefox LaunchApplication Xterm An Xterm file:///usr/bin/xterm LaunchApplication TestTerm An Xterm from program TestTerm in the same directory as the TiddlyWiki TestTerm The following buttons work in Firefox on Windows LaunchApplication NotePad Test Notepad locally NotePad/ Notepad.exe LaunchApplication WordpadPad Local machines wordpad launch wordpad.exe LaunchApplicationButton Open Notepad Text Editing file:///c:/ Windows/system32/notepad.exe Nothing works in IE 8, any longer. Since I don't use IE, I am not particularly interested in figuring out why. :-) ...Lyall On Nov 19, 10:10 am, Ohrange toni.alsf...@gmail.com wrote: Can anyone tell me how to get the LaunchApplicationPlugin or something similar working in MPTW. I've gone herehttp://remotely-helpful.com/TiddlyWiki/LaunchApplication.html#LaunchA... and picked up the tiddler but I can't get it to work. Thanks, Ohrange -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@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: Announcement of 2.6.2 beta release of TiddlyWiki
I agree with Alan on using filename as part of the cookie name or perhaps a random ID. Recently, I had four different TWs open, and the username was same in all of them, even though it wasn't supposed to be. As for which should take precedence, I think the cookies. I mean, you set some default persistent options for yourself, which are supposed to be valid most of the time. But perhaps you want to temporarily change one of those options, which you can do with a cookie. Or, to make the discussion void, you could simply add an option for the users to decided for themselves (which would be a persistent option in itself :D). w On Nov 19, 4:10 am, AlanBCohen alanbco...@gmail.com wrote: My suggestion would be that as part of the implementation of persistent (Baked) cookies, consideration be given to including the current file name as part of the cookie ids. I realize not everyone uses multiple open TW files at the same time, but the many uses of cookies in TW currently means that the same cookies are affecting multiple files. I may well want my sidebar hidden in one file but want it open in another. I often use separate TW files to keep separate what would otherwise be one large, slow file, at work, for example, my addressbook, my work diary, my primary collection of links, and my collections of technology notes. Even the username might vary between someone's personal files and a team-based TW file. I'm reasonably sure there would be others with similar needs for distinct cookies between TW files. My suggestion on precedence for identically named cookies would be for the persistent ones to be of lower priority than the session cookies. This would allow the same values at start as were valid at the beginning of the previous session (if the persistent cookies in the tiddlers were not changed and saved during that session) while allowing them to be changed for the session. -- You received this message because you are subscribed to the Google Groups TiddlyWiki group. To post to this group, send email to tiddlyw...@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] Not Understanding EditFieldPlugin TaggedTemplateTweakPlugin
Hi:
I have a tiddlywiki with only the EditFieldPlugin and
TaggedTemplateTweakPlugin installed. I have a tiddler titled
personViewTemplate as follows:
|Prefix, First Name Middle Namebredit fname|Last Name
Suffixbredit lname|
|Titlebredit persontitle|
|Organizationbredit org|
|Desk Phonebredit phone|Extensionbredit ext|
|Cell Phonebredit cellphone|
|Emailbredit email|
|Notesbredit notes 6|
This tiddler correctly displays a simple input form in view mode and
the EditFieldPlugin correctly asks for confirmation as text is entered
in the input boxes.
What is the proper syntax in a macro button to open this form as a
template in view mode ready to accept user data entry? This macro
opens a new tiddler in edit mode rather than view mode:
newTiddler
label:New Person
text:{{store.getTiddlerText(personViewTemplate)}}
I thought this version would trigger the TaggedTemplateTweakPlugin:
newTiddler
label:New Person
tag:person
Instead, it produces an empty new tiddler in edit mode which when
closed produces this raw text in view mode:
|Prefix, First Name Middle Name
|Last Name Suffix
| |Title
| |Organization
| |Desk Phone
|Extension
| |Cell Phone
| |Email
| |Notes
|
The above text in view mode seems to indicate that the
TaggedTemplateTweakPlugin is being called, however the text is not
accompanied by a tiddler command menu.
I hope this is an adequate explanation of my problem. I'm just trying
to open an input form ready for user input. However, I will have 3 or
4 different input forms and I'd like to use the
TaggedTemplateTweakPlugin to open the appropriate form base on a
tiddler's tag (tags such as: person, project, issue). I have looked at
UdoBorkowski's form and data plugins, but I would like to have this
work with custom fields rather than JSON data because I think the
custom fields will be easier to work with as my tiddlywiki grows.
Thanks, Keith Silva
--
You received this message because you are subscribed to the Google Groups
TiddlyWiki group.
To post to this group, send email to tiddlyw...@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.
