I intentionally only support excludeLists to reduce complexity. I
believe there was talk of someone forking the plugin to allow for more
sophisticated exclusion, but that hasn't happened yet.
tagsplorer exclude:foo does work to exclude tiddlers tagged with
foo from the filtered list, or have I
The current exclude parameter will accept (1) tag ie exclude:foo or
exclude:'my tag'
it does not support multiple tags (yet)
Mike
On Apr 16, 6:53 am, Anthony Muscio anthony.mus...@gmail.com wrote:
But what about
tagsplorer exclude:foo exclude:bar task urgent
TonyM
If you have not found
I found source at
http://svn.tiddlywiki.org/Trunk/contributors/FND/plugins/TagsplorerMacro.js
placed in a tiddler and I see the Exclude: parameter but It is not what I
was suggesting in my last email.
*I understand the current behavior to be*
tagsplorer Shows you all tiddlers
and
NEW allows you
I have the exclude parameter on my to do list, as a project to learn
more about JS and macro parameters, so I am taking my time (and I get
easily distracted by other project ideas)
feel free to create a patch and post it here if you have the time,
otherwise I will continue to work in that
Thanks FND,
It has been inspirational the possibilities and I do hope a Fork as per my
suggestions is developed.
It dose apply pressure once again for me to learn java script as I would
love to share the load and take such tools that little bit further to
Awesome Status.
Without making this
Folks,
Without me Trawling all these Posts can anyone tell me how to find the
latest version of the tagsplorer plugin ?
I am very impressed with the possibilities and functionality of the one
linked to in the first email, in this thread !
Also Has the question been put to add a Not Tag list
Not sure if you have already addressed this, but in my document the
tag selection popup was not closing after a selection was made
I had noticed this as well - while it is strange, it turned out to be
quite useful sometimes, so I didn't fix it immediately.
Thanks for the reminder though, as
Awesome !
I didn't know the core tag chooser had that option, but I will
probably use that now. . .
(I learn something new everyday)
Mike
On Apr 13, 3:06 pm, FND f...@gmx.net wrote:
Not sure if you have already addressed this, but in my document the
tag selection popup was not closing after
FND,
Not sure if you have already addressed this, but in my document the
tag selection popup was not closing after a selection was made
(I assume you can find a better way to patch this) (ff3.5 winXP - in
case it is a browser related issue)
My Patch:
onTagClick: function(ev) {
Is there any particular reason why the IncludePlugin doesn't support
getTiddlers - it sounds like perhaps it should? [...]
According to the comments in the source code it's because getTiddlers
is used for saving, and the idea of ImportPlugin is that external
tiddlers are imported but not saved.
Is there any particular reason why the IncludePlugin doesn't support
getTiddlers - it sounds like perhaps it should? [...]
According to the comments in the source code it's because getTiddlers
is used for saving, and the idea of ImportPlugin is that external
tiddlers are imported but
[...] implement those fancy image-less arrows
It seems there is no clean (as in KISS) way to achieve this.
So I settled for subtle rounded corners (supported by modern browsers,
degrades gracefully) - not perfect, but an improvement I guess:
http://fnd.lewcid.org/misc/jQueryAPI.html
-- F.
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
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:
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
Actually, I realized other separators are probably clearer such as a
(vertically centered) bullet or a simple . Indicates a gradual
refinement/path. A more subtle version of is › (ref number 155
here http://www.ascii-code.com/ )
Still think some color contrast is a good idea.
(Procrastinating
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 surrounded
by spaces
I'd experimented with this, but didn't come up with a satisfying solution.
Instead of adding an extra character (separation of concerns and all),
I admit that I wasn't sure about a seperator - untill I saw the css
arrows (delicious style) I think that would be awesome in low
contrast.
and it would add a bit of style w/ function.. ..
Mike
On Mar 31, 7:25 am, FND f...@gmx.net wrote:
it is very difficult to tell how many tags this is and
Another minor suggestion;
The problem becomes particularly obvious when viewing
http://fnd.lewcid.org/misc/jQueryAPI.html
and adding e.g the tag DOM Insertion, Inside resulting in a tags
list that looks like;
jQuery API DOM Insertion, Inside
Unless placing the mouse directly over a tag there, it
Would like to se a re-focus onto that top field, ie. to where the
chosen tags are listed. Currently, after selecting a second tag from
a longer(!) list as in your supplied example, the focus is set to the
top of the resulting list.
I'm guessing this should addess that issue:
When using TagsplorerMacro in a tiddlywiki run as an HTA file (with
IE6 as the browser), any click on the list of tags or the [+] button
leads to a blank window being opened. I fixed this by adding 'return
false;' at the end of any function that did not return a value
(handler, newTagClick,
I fixed this by adding 'return false;' at the end of any function
that did not return a value (handler, newTagClick, onTagClick,
delTag, refreshTags and refreshTiddlers).
Good catch - those returns got lost in some early refactoring.
Fixed now:
http://trac.tiddlywiki.org/changeset/11913
-- F.
Thank You FND,
great answers + awesome plugin + a new project for me :)
I appreciate your patience,
Mike
P.S. Can anyone reccomend a good JQuery book - websites are good, I
just learn better from a old school book (which will probably be
slightly out dated)
On Mar 29, 7:16 am, FND f...@gmx.net
Found a minor bug in the v1.2.0
tagsplorer (no parameters)
returns a error. . .(type error: tags is undefined)
Example:
http://www.strm.us/tw/examples_twgg/tagsplorer.h1
On Mar 27, 5:07 am, FND f...@gmx.net wrote:
I would still like to add a excludeLists parameter, but it is beyond
my
one more addition. . . can you exclude multiple tags?
My testings says no, but I may have the syntax wrong. . .
Great Work, need to compare v1.1 vs v1.2 to figure how you did it :P
Have a good day,
Mike
On Mar 27, 5:07 am, FND f...@gmx.net wrote:
I would still like to add a excludeLists
I would still like to add a excludeLists parameter, but it is beyond
my capabilities right now, I need to spend some time building some
simple macros w/ parameters before I can tackle this
Isolating the problem sounds like a good plan.
I was gonna give you some sample code, but then went ahead
No biggie, but still: Would like to se a re-focus onto that top field,
ie. to where the chosen tags are listed. Currently, after selecting a
second tag from a longer(!) list as in your supplied example, the
focus is set to the top of the resulting list.
On Mar 27, 11:07 am, FND f...@gmx.net
I guess it's a matter of aesthetics, or maybe it's for another plugin
all together, but I'm throwing out this idea;
Expand the concept to become a kind of semi-visual boolean filter for
tags, i.e other than just the current AND operator, start off the
drop down tags list by listing the basic
Question:
If using the config.options method to change variables
(IE my excludeLists hack) http://www.strm.us/tw/examples_twgg/tagsplorer.h1
how can I specify that when the status of the cookie changes to
refresh Display (would Display work in this context?)
Maybe I am in left field with my
I feel like I cheated. . .
I was having problems adding a parameter (and not messing up the tags
parameter)
so I opted for a configuration cookie. . .
http://www.strm.us/tw/examples_twgg/tagsplorer.h1
Let me know if this is a taboo solution.
(might also be a solution for adding sort order
passingby,
I think the default usage may still be a little confusing, the macro
by itself returns all tiddlers, by clicking new (+) you add a filter
from the dropdown which then shows only tiddlers with that tag, adding
additional filters continues to reduce the tiddler list.
the demo shows the
Starting here. . .
http://www.strm.us/tw/examples_twgg/tagsplorer.h1
Will work on excludeLists parameter tomorrow :P (Finishing may be
another subject)
Mike
On Mar 22, 9:45 pm, passingby passingby...@gmail.com wrote:
It took me some time to figure out but its great once one gets it.
There are
Also, I think new isn't the best label for that button. Perhaps any
of the following would be more intuitive.
- [+]
- filter
- add (filter)
- select (filter)
Tobias.
--
You received this message because you are subscribed to the Google Groups
TiddlyWiki group.
To post to this group, send
Another thought...
I think it might be quite powerfull to have a different dropdown (or
alternatively more than one)... one that can be configured in a way so
that one can (optionally) define a bracketed list of toplevel-tags or
main-tags... which will then give you a kind of treelike dropdown
I think it might be quite powerfull to have a different dropdown (or
alternatively more than one)... one that can be configured in a way so
that one can (optionally) define a bracketed list of toplevel-tags or
main-tags... which will then give you a kind of treelike dropdown
with all those
any other thoughts on excludeLists?
I am going to have some spare time this week and might play with
it . . .
Mike
On Mar 22, 7:29 am, Eric Shulman elsdes...@gmail.com wrote:
I think it might be quite powerfull to have a different dropdown (or
alternatively more than one)... one that can be
Thanks for the feedback, everyone.
any other thoughts on excludeLists?
I am going to have some spare time this week and might play with it
Your suggested patch seems quite elegant. (I haven't actually tested it
yet.)
I agree that it needs to be an optional parameter (not entirely sure
about
It took me some time to figure out but its great once one gets it.
There are still two questions though:
1. In the demo tiddler, when i remove a tag by clicking on it, it gets
added to the list below, which is fine. But when the very last tag is
removed two things happen, the list below gets
looks very nice
Thanks. It could certainly do with some improvements, as it doesn't seem
very intuitive at the moment - so I'm hoping someone with a better sense
of UI design will come along and offer suggestions...
was your concept to use it as a menu? Or as a new way to navigate?
The
I've started experimenting with this on TiddlyWeb documentation, which
proved useful and led to some unexpected insights
I've now also applied this to the jQuery API docs*, which seems even
more useful (due to the excellent metadata):
http://fnd.lewcid.org/misc/jQueryAPI.html
-- F.
*
I can see it functioning a little better inside a larger document !
So it creates a tags filter showing relevant information, with the
option to
add additional filters to drill down further (from menu bar via new
button)
or remove filters to drill out (from menu bar via click tag name)
somehow I
So it creates a tags filter showing relevant information, with the
option to add additional filters to drill down further (from menu bar
via new button) or remove filters to drill out
I guess that's how I should have explained it in the first place...
Thanks.
somehow I got a prompt box
I think this does the trick
var getTiddlers = function(tags) {
// var tiddlers = store.getTiddlers();
var tiddlers=store.getTiddlers('title','excludeLists');
My coding is beginner at best, (compared to others around here)
luckily it was pretty simple. . .
Unless you were thinking of
Only careful observation of the tooltips made me understand what the
exploring bits are actually about. I guess it's not so much the
interface but the name which was a bit confusing to me. Wouldn't
something like TagListFilter go better with it?
Tobias.
On 21 Mrz., 14:38, FND f...@gmx.net
hi
On Mar 21, 10:50 pm, Tobias Beer beertob...@googlemail.com wrote:
Only careful observation of the tooltips made me understand what the
exploring bits are actually about. I guess it's not so much the
interface but the name which was a bit confusing to me. Wouldn't
something like
I agree excludeLists as an optional parameter would probably be
better, would that be enough configuration, or are thinking something
more robust?
Mike
On Mar 21, 5:19 pm, PMario pmari...@gmail.com wrote:
hi
On Mar 21, 10:50 pm, Tobias Beer beertob...@googlemail.com wrote: Only
careful
might also look at changing macro name / tooltip to be more
informative (plugin name doesn't matter much to me)
the more I play with the plugin the more I like it. . .
After initial hurdle it is very intuitive
Mike
On Mar 21, 5:19 pm, PMario pmari...@gmail.com wrote:
hi
On Mar 21, 10:50 pm,
I agree excludeLists as an optional parameter would probably be
better, (than my code above)
I was thinking a true / false type option would that be enough
configuration, or are you thinking something more robust?
Mike
On Mar 21, 5:45 pm, Mike eris...@gmail.com wrote:
might also look at
49 matches
Mail list logo
