Okay, just a few things to clear up. First, I'm using the Tiddylpedia
theme, which also shows which tiddlers are tagging the current
tiddler. Eric's plugin only coveres the tags, namely the tags of the
current tiddler. For some reason, my first solution didn't work in all
tiddlers. It did in some,
And another thing, I'm using the plugin version 1.0.1, because I can't
seem to get version 2.0.0 working.
On Apr 1, 9:10 am, whatever kbrezov...@gmail.com wrote:
Okay, just a few things to clear up. First, I'm using the Tiddylpedia
theme, which also shows which tiddlers are tagging the current
Almost all of this discussion is way, way over my head. I understand -- or
misunderstand! -- enough to make me anxious, though.
I hope you have no need to be anxious. TiddlyWiki5 is a functional
superset of classic TiddlyWiki, no-one is going to lose features if
they choose to make the
The new css border styling looks good + it's much cleaner than hard-
coding, semantically useless separators.
Tobias.
On 31 Mrz., 14:25, FND f...@gmx.net wrote:
it is very difficult to tell how many tags this is and exactly what
they are. I suggest a separator between tags, such as pipe
Hi all,
I am a new TiddlyWiki user and group member. I would like to enter
mathematical formulas in my tiddlers and to that end I have been
investigating the two plugins MathSVGPlugin and ASCIIMathMLPlugin,
both written by Paulo Soares. My question is: which one should I use?
MathSVGPlugin
Hi,
Did you solve it allready?
On Mar 22, 8:21 pm, Måns humam...@gmail.com wrote:
Here's my go at
it:http://dl.dropbox.com/u/3105342/TW/karakaterer/karakterMM.html#testCo...
Maybe you can tell me what to change - to make it work...
Regards Måns Mårtensson
On 22 Mar., 16:18, Måns
To ensure tiddlers included using IncludePlugin are listed, it would
be good if the first line of the getTiddlers function could use
reverseLookup, so:
var tiddlers = store.reverseLookup(title, excludeTag);
I've also added a cross after the tags by amending refreshTags as
follows:
Hello Jeremy,
On Apr 1, 1:08 am, Jeremy Ruston jeremy.rus...@gmail.com wrote:
I hope you have no need to be anxious. TiddlyWiki5 is
a functional superset of classic TiddlyWiki, no-one
is going to lose features if
TW is a great product, and I certainly appreciate the effort that has
gone into
I'm writing an end-user manual for TW so this information is very
welcome. I will update the community wiki when i get around to it.
Excellent, thanks!
[After locally modifying a plugin tiddler] I select the plugin and
click sync. What happens?
You'll get a message Changed while unplugged
While it may be true in the technical sense that no one will lose
features, the fact that there will be no backward compatibility with
existing macros/plugins will have an immediate impact on anyone not
using the barebones TW.
Let's be clear: if we wanted TiddlyWiki5 to be compatible with
I admit that I wasn't sure about a seperator - untill I saw the css
arrows (delicious style) I think that would be awesome
I haven't had time to look into this yet, and probably won't for a
while. CSS wizardry contributions (or research into prior art) would be
most welcome...
The new css
Is there any particular reason why the IncludePlugin doesn't support
getTiddlers - it sounds like perhaps it should? (I'm not intimately
familiar with that particular plugin.)
According to the comments in the source code it's because getTiddlers
is used for saving, and the idea of ImportPlugin
Any thought paid to supporting semantically rich tagging in TW 5?
That is, being able to associate a relationship type with the tag
instead of just assuming generic isA? Extended fields does this to
some extent, but they are hidden and not as easy to use as tags. It
would be cool to combine the
Any thought paid to supporting semantically rich tagging in TW 5?
That is, being able to associate a relationship type with the tag
instead of just assuming generic isA? Extended fields does this to
some extent, but they are hidden and not as easy to use as tags. It
would be cool to combine
Thanks for the reply Måns but I still can't get it to work.
The quick start document seems to be really helpful but no matter what
I can't get the gotoplugin to appear where I want it to, even when
changing the stylesheet information.
Can anyone tell me how to make the gotoplugin appear where you
I think simply (tongue in cheek)
1) extending the tag definition to optionally allow definition of the
relationship type as:
tags = conventionalUntypedTag1 isA(tagA) conventionalUntypedTag2
belongsTo(tagB) dependsOn(tagC)
2) then storing these under the cover as extended fields
isA =
this is on Mark S's list, but I would like to second support for
InlineJavascript (plugin or native) w/ TW5
Mike
On Apr 1, 10:19 am, Saverio saverio.mavig...@gmail.com wrote:
Oops, tagA would be stored under the isA extended field, as well:
isA = conventionalUntypedTag1
Hello Jeremy,
On Apr 1, 6:11 am, Jeremy Ruston jeremy.rus...@gmail.com wrote:
Calendar reminder plugins are essential if TW is
going to compete with existing PIM software.
I think a basic calendar plugin would be useful for
the core, but in general I've learned that what I
might call the
this is on Mark S's list, but I would like to second support for
InlineJavascript (plugin or native) w/ TW5
TW5 will definitely support InlineJavaScript via a plugin, but I'm
very cautious about putting it into the core. In shared environments
it could be a vector for malicious code. It'd be OK
plugins are great, allows the core to remain small, and gives
customization options to the end user. I know you mentioned backwards
compatibility - are you thinking of something like
DepreciatedFunctions? Allowing some old plugins to get in, but not
creating a core code increase. . . Kind of a
In following this discussion as to what plugin functionality to
consider moving into the core for TW5, I am left wondering about fET?
This is the single, most important extension for any of my TW files;
calendar, status reporting, addressbook, knowledge databases of
various subjects, and blood
plugins are great, allows the core to remain small, and gives
customization options to the end user. I know you mentioned backwards
compatibility - are you thinking of something like
DepreciatedFunctions? Allowing some old plugins to get in, but not
creating a core code increase. . . Kind of
I recognise the significance of fET, and think that something like it
needs to be built into the core.
The prototype includes the bare bones of support for a jQuery-like
filter chaining syntax that will permit tiddler selection and sorting
in an efficient and readable form of JavaScript. I'm
@ELS, obviously, but anyone is free to jump in to tell me what I
misunderstand :-)
GridPlugin[1] is wonderful, rendering tables to show - and even
directly edit - meta data of specified tiddlers; fields, slices and
sections... but not tags.
Tags are used to filter out tiddlers, but you cannot
This might be an easy one for you TiddlyWikisperts:
I am making a kind of glossary of words for English language students.
Each of my tiddlers consists of an English word (the title), along
with a definition, examples, etc. I would like to include links to
Google Translate for certain languages
Saverio wrote;
Any thought paid to supporting semantically rich tagging in TW 5?
That is, being able to associate a relationship type with the tag
A note here, assuming I understand you right; Because tags are
interchangeable with tiddler names, it *is* possiblt to type a tag...
by tagging it!
are you executing via the viewTemplate via tiddler macro?
Mike
On Apr 1, 3:03 am, whatever kbrezov...@gmail.com wrote:
Hi! In a previous thread (http://groups.google.com/group/tiddlywiki/
browse_thread/thread/b816052d3d6a07a3) I found that Eric's
ToggleTiddlerTags plugin solved my problem.
Via toolbar command.
On Apr 1, 11:22 pm, Mike eris...@gmail.com wrote:
are you executing via the viewTemplate via tiddler macro?
Mike
On Apr 1, 3:03 am, whatever kbrezov...@gmail.com wrote:
Hi! In a previous thread (http://groups.google.com/group/tiddlywiki/
28 matches
Mail list logo
