TiddlyWiki Plugin Library alpha release
FND
At long last, the Plugin Library is ready to be shown in public:
http://plugins.tiddlywiki.org
There's still a lot to be done, so don't be surprised if there are bugs,
the UI is horrible, plugins are missing from the index etc.
However, it should demonstrate what I've actually been working on all
this time (even though it doesn't seem very exciting on the surface).
I'll write up the details of what's actually happening there soon, so
both users and plugin authors know what to expect - and what I expect
from them...
Also, "library" is a bit of a misnomer, as the plugins are still gonna
be imported from the original authors' repositories.
Here are a few alternative suggestions (mostly not mine):
TiddlyWiki Plugin Catalog
TiddlyWiki Plugin Register
TiddlyWiki Plugin Index
TiddlyWiki PlugIndex
TiddlyWiki, Das PluginWerk
Should we stick with "Plugin Library", simply because it's an
established term by now, or should we pick something else?
-- F.
simon mcmanus
As for names, how about....
Plugin Hub?
PlugHub?
PlugBin?
Plugin Central?
Plugin Place?
Plugin Search?
Or maybe just use "TiddlyWiki Plugins" for the siteTitle and prefix
your current siteSubTitle with something slightly more descriptive.
"A place to find TiddlyWiki Plugins from all over the web" <<< or
something far better.
--
Simon McManus
blog : http://simonmcmanus.com
Dave Gifford
Problem: I typed in 'toggle' to see what plugins there were for
toggling, and got 58 tiddlers popping up. Things like
EasyHighlighterplugin that don't have anything to do with toggling. I
have a feeling the word toggle is part of many of the plugin codes?
I think a searchoptions list will be more practical than having a long
list of library cards like it has now.
As far as names, "Plugin Outlet" has the pun factor in its favor.
Also rans:
"TiddlyPluggy"
"Plug Inn"
"Mirror site to TiddlyTools with a few others thrown in" ;-)
"systemConfig Newton"
"Tiddly Surge Protector - where all the plugins are plugged in"
"Pluggypedia"
Dave
Scott Elcomb
>
> All,
>
> At long last, the Plugin Library is ready to be shown in public:
> http://plugins.tiddlywiki.org
> Also, "library" is a bit of a misnomer, as the plugins are still gonna
> be imported from the original authors' repositories.
> Here are a few alternative suggestions (mostly not mine):
> TiddlyWiki Plugin Catalog
> TiddlyWiki Plugin Register
> TiddlyWiki Plugin Index
> TiddlyWiki PlugIndex
> TiddlyWiki, Das PluginWerk
> Should we stick with "Plugin Library", simply because it's an
> established term by now, or should we pick something else?
In addition to Freds' and Daves' (and your own!), some more ideas:
Virtual Plugin Library
Plugins 411
Universal Plugin Locator
PluginReSource
TiddlyPlugger
I also ran a 'define: congress' on google due to an nagging memory
that wouldn't surface. Wikipedia scratched the itch:
In politics, a congress ("a gathering of people") is the name of
the main legislative body
in a state that operates under a congressional system of government. ...
en.wikipedia.org/wiki/Congress
"A gathering of people," is what I was after... How about TiddlyWiki's
Plugin Congress?
--
Scott Elcomb
http://www.psema4.com/
http://www.psema4.com/blog/
http://www.google.com/reader/shared/14892828400785741937
wolfgang
> http://plugins.tiddlywiki.org
>
> There's still a lot to be done, so don't be surprised if there are bugs,
> the UI is horrible, plugins are missing from the index etc.
Regards,
W.
BidiX
http://plugins.tiddlywiki.org
http://BidiX.info
Saq
Saq
On Sep 25, 10:51 pm, BidiX <bidi...@gmail.com> wrote:
> 2008/9/25 FND <F...@gmx.net>
Anthony Muscio
Plugin Plunder Place
:-)
TonyM
TonyM
If you have not found an easy way to do it with TiddlyWiki, you have missed something.
www.tiddlywiki.com
wolfgang
>
It only weights 310 kb, but when I make a search it opens hundreds of
plugin tiddlers ready to view, edit or save. With no obvious
difference to any other TiddlyWiki. - It's definitely much much more
than just the index.
W.
chris...@gmail.com
TheplugIndex is using TiddlyWeb[1] as a backend datastore. When you do
a search, a request is made that through lots of twisty paths
eventually ends up asking TiddlyWeb about information it is holding.
The response is brought into the UI (which is a TiddlyWiki) and
processed to form new Tiddlers.
[1] http://tiddlywiki.org/wiki/TiddlyWeb
FND
For the name, I'm inclined to go with Simon's PluginHub suggestion, because
a) it sounds kinda cool, and
b) it captures the idea of having a central place which leads off to the
individual authors' repositories.
Any objections to that?
> Problem: I typed in 'toggle' to see what plugins there were for
> toggling, and got 58 tiddlers popping up. Things like
> EasyHighlighterplugin that don't have anything to do with toggling. I
> have a feeling the word toggle is part of many of the plugin codes?
Yes - right now, we're doing a simple full-text search. That will evolve
to provide more elaborate search functionality (e.g. filters).
> I think a searchoptions list will be more practical than having a long
> list of library cards like it has now.
The UI is a very early prototype - I expect there to be massive changes
along the way.
Anyone is welcome to give a hand (it's fairly simple to get started, as
the PluginLibraryAdaptor provides all the necessary abstraction).
-- F.
Daniel Baird
>
> Thanks for the responses.
>
> For the name, I'm inclined to go with Simon's PluginHub suggestion, because
> a) it sounds kinda cool, and
> b) it captures the idea of having a central place which leads off to the
> individual authors' repositories.
> Any objections to that?
Only that "The Tiddly Plugdex" rocks that one out of the water. Or
maybe that's just me.
--
Daniel Baird
/to be or not to be/ => /(2b|[^2]b)/ => /(2|[^2])b/ => /.b/
...optimise your regexes, people!
Dave Gifford
> Only that "The Tiddly Plugdex" rocks that one out of the water. Or
> maybe that's just me.
Dave
Alex Hough
I think your wrong on this one.
Tiddly Plugdex is clearly ' ice'
Words ending with 'x' alway are cool. FACT
Alex
2008/9/27 Dave Gifford <gif...@gmail.com>:
--
t: 0161 442 2202
m: 0781 372 50 17
Vote for me: http://tinyurl.com/5ukadj
Morris Gray
still much to do. At least now you won't be working so alone. Of
course now you've got 3000 people watching :-)
I suggest TiddlyWiki Plugin Directory It's not really a repository or
library and what it really does, if I understand rightly, is 'direct'
you to the place from which, with a click, you can download. It might
sound conventional but it's accurate and dignified.
Morris
Alex Hough
and index would be best resolved by consultation with the librarians
in the TW comminity.
Tom Wilson might be a good start. Details below;
Tom Wilson <wils...@gmail.com>
--
Professor Tom Wilson, PhD, Hon.Ph.D.,
Publisher and Editor-in-Chief
Information Research: an international electronic journal
Website: http://InformationR.net/
E-mail: wils...@gmail.com
______________________________________
Lyall
The Tiddly Codex. ;-)
Maybe you could offer suggestions to authors of plugins to assist with
searching - maybe including some sort of metadata in the plugins that
the site searches in, by preference, otherwise, if the metadata is not
there, full text.
I for one, would be happy to apply such metadata to the plugins I
maintain. Maybe along -E uses for plugin configuration?
...Lyall
On Sep 29, 3:03 am, "Alex Hough" <r.a.ho...@googlemail.com> wrote:
> Issues along the lines of distinguishig between a directory, library
> and index would be best resolved by consultation with the librarians
> in the TW comminity.
> Tom Wilson might be a good start. Details below;
>
> --
> Professor Tom Wilson, PhD, Hon.Ph.D.,
> Publisher and Editor-in-Chief
> Information Research: an international electronic journal
> Website:http://InformationR.net/
> ______________________________________
FND
> and index would be best resolved by consultation with the librarians
Thanks. I think we're pretty clear on the distinction, though we might
make some compromises in favor of a more snazzy name...
As I've said, I'm leaning heavily towards "TiddlyWiki PluginHub", and
nobody has objected so far.
> Maybe you could offer suggestions to authors of plugins to assist with
> searching - maybe including some sort of metadata in the plugins
That's definitely gonna happen. Much of it is already in place by
convention* (e.g. I'm already using the Source slice for
disambiguation), and this is our chance to formalize it.
I'll give more details in the upcoming post.
-- F.
* cf. http://www.tiddlywiki.org/wiki/Dev:Plugin_Specifications
M)
comments right now concern scrolling and whitespace. I feel the
whitespace usage is excellent -- it feels very inviting. Regarding
scrolling, I feel it should be minimized while maintaining the
whitespace. I feel seeing more options on the screen at one time
allows for greater comparison, which helps the selection process. Is
'more...' essential? Can it be turned into a two column layout (title
- description)?
Maybe the 'close' needs to be more obvious, but maybe I feel this way
because the top plugins in the list had no description so I was
encouraged to not close not needed plugins. Maybe the close needs to
be 'collapse', because I might change my mind. Maybe the tiddler
title should be listed with the option to expand / collapse and close.
Okay, I found another. What does 'keep' (permanently store this
tiddler) do?
Cheers,
M)
FND
I think it definitely is necessary to provide access to the entire
plugin information.
However, it might be positioned differently - maybe in the toolbar?
> Can it be turned into a two column layout (title - description)
Not sure what that would look like, or why it would be better.
> Maybe the 'close' needs to be more obvious
Aren't the toolbar commands quite salient? Granted, the coloring isn't
perfect, but that's because I was simply reusing the existing
ColorPalette for this early prototype.
> the top plugins in the list had no description so I was
> encouraged to not close not needed plugins
I'm not quite following; how does the lack of a description relate to that?
> Maybe the close needs to be 'collapse', because I might change my mind.
> [...] What does 'keep' (permanently store this tiddler) do?
Well, my original idea was that after retrieving a batch of plugins,
you'd browse them and decide for each tiddler whether you wanna
a) keep it for reuse*,
b) close it for later review, or
c) dismiss/delete it entirely.
Then you could save the file and import plugins from there.
Of course this mainly applies when using the UI from your local HDD
(though I suppose Eric's SaveAsPlugin could be used to save the state of
the respective online document).
However, we're not sure yet whether that's what we actually want.
Not that this UI is just a TiddlyWiki file connecting to the plugin
server, so you can download and modify it to your liking - and hopefully
feed back any insights so they can be considered for inclusion in the
official branch.
-- F.
* by default, retrieved tiddlers are temporary, and thus not saved to disk
M)
the project. Please excuse my lack of knowledge. As always, I am
forever grateful for efforts by the TW team. You guys should be
nominated for something like the Nobel Peace Prize or something like
that. My comments are strictly ways of trying to give back value for
the value I've received.
Maybe the library needs a description for laypersons like me. I
didn't know it could be download and wouldn't have thought so due to
my knowledge created by TiddlyVault. Here's what could be described:
. "keep"
. download option
. How to import plugins (I initially thought I could get it from the
library)
. what the library is
> > Is 'more...' essential?
>
> I think it definitely is necessary to provide access to the entire
> plugin information.
> However, it might be positioned differently - maybe in the toolbar?
the two options? Both appear to present the same information. I'm
still not sure why it is necessary beyond the quickness of the
presentation. I must be missing something.
> > Maybe the 'close' needs to be more obvious
> > encouraged to not close not needed plugins
>
> I'm not quite following; how does the lack of a description relate to that?
not encouraged to close the tiddler just in case I might return to it
and dig deeper. This might happen if none of the other tiddlers are
what I am after. Are we on the same page yet?
When clicking 'more...', I was expecting the 'close' would return the
tiddler back to the search result list.
M)
FND
> the project. Please excuse my lack of knowledge.
No need to apologize for anything - we appreciate the feedback!
However, note that it's still in alpha stage - which technically means
it's not ready for end-users (also because of the lack of documentation).
> The 'more..' is quick, so it is better than the title link. But why
> the two options? Both appear to present the same information.
Fair point - however, since you're not supposed to import from the
plugin library directly (for reasons I won't go into here - can of
worms!), the link to the original author's repository is essential.
To avoid this sort of confusion, we might have to truncate the
information being displayed in the "More" view.
> When no description exists and the title is not informative, then I am
> not encouraged to close the tiddler [...]
So you click on More to get an idea of what the plugin is all about?
That makes sense.
> When clicking 'more...', I was expecting the 'close' would return the
> tiddler back to the search result list.
The "More" link opens the respective tiddler in place, only using a
different (non-reduced) ViewTemplate. Maybe we should call it "Expand"
instead?
-- F.