VisualTW2 - VisualTW project rising from the ashes!

[huggyfee]

Hi there

Well, having been a firm TiddlyWiki advocate (at least to my
colleagues) for a good three years now, I thought it's about time I
started contributing something back.

Of the plugins around, I have found the VisualTW ones to be the
stalwarts - I come back to them time and time again. Sadly, it hasn't
been updated for a few years.

I was playing with the TagsTree plugin recently mainly to understand
how to use it properly, but along the way, made some changes / fixed a
problem I found with it.

So, great chance to contribute back. I've contacted Pascal, and he's
fine with me forking this, so if anyone would like to check it out
(early days yet) and let me know if you find any problems / have any
suggestions, let me know - ideally by adding to the 'Issues' log on
github, but posting in the TiddlyWiki forum is fine too.

The code can be found at: http://github.com/huggyfee/VisualTW2

Click on the 'Wiki' link for an overview of where I'm at and what my
current roadmap is. Hoping other people will help me with this.

I'm hoping to get a stable foundation first, and then start adding new
features / Plugins when I have a good understand of what's there
already!

Thanks to Jeremy for a fabulous idea (TiddlyWiki) and to Pascal for a
fabulous set of plugins to extend this (VisualTW)!

All the best

Simon.

[Ronen]

It's great to hear that plugins are still being updated, Thanks!

I've installed the plugin but I can't get any data when using
<<tagsTree>> :(

[huggyfee]

Try something like:

<<tagsTree menu "" 2 4>>

from the 'mainmenu' tiddler.

Then tag any tiddlers you want to appear in the mainmenu with 'menu' -
eg a tiddler called 'projects' with tag 'menu'
Then tag any tiddlers you want to appear under 'projects' with the
name of the tiddler - eg a tiddler called 'TiddlyWikiPluginProject'
with tag 'projects'
etc. etc.

The 2 refers to the number of levels deep to expand on the tree
automatically, and the 4 refers to the maximum depth of tiddlers to
show on the tree.

See if these seems to work - otherwise if you could drop me the sample
TiddlyWiki / Tiddlers you have created I'll take a look and see what
might be wrong.

Tx

Simon.

[Ronen]

Now it works perfect, thanks!

[Yakov]

Hello Simon,

May I ask a couple of questions (or rather pull requests):

* would you mind to add a changelog in plugin(s) you amend?
* do have plans of hosting an html version of the wiki somewhere? I
mean, in raw text it's rather useful to see the plugins only (tiddler
texts) while the whole TiddlyWiki should be rather available as a page
(the "raw" button at github doesn't provide this)
* is it possible that you establish an RSS feed of the updates? I
really wish this happen with all the repositories, but there are some
issues about it so if you do it, that would be a good contribution for
others also.
* and yet, why you (or Pascal) decided to host updates somewhere else,
not at [1]?

[1] http://visualtw.ouvaton.org/VisualTW.html

[huggyfee]

Hi - Sorry for the delay in responding:

In reply to your quesitons (replied inline) :

On Oct 29, 2:22 pm, Yakov <yakov.litvin.publi...@gmail.com> wrote:
> Hello Simon,
>
> May I ask a couple of questions (or rather pull requests):
>
> * would you mind to add a changelog in plugin(s) you amend?

Sure - that makes sense - I'll do that from my next change.

> * do have plans of hosting an html version of the wiki somewhere? I
> mean, in raw text it's rather useful to see the plugins only (tiddler
> texts) while the whole TiddlyWiki should be rather available as a page
> (the "raw" button at github doesn't provide this)

That would be an excellent idea. Although the ZIP version is better
for creating a blank TiddlyWiki, it would make sense to have a
'tryout' version from which the ZIP form can be downloaded (as on the
main TiddlyWiki site)

> * is it possible that you establish an RSS feed of the updates? I
> really wish this happen with all the repositories, but there are some
> issues about it so if you do it, that would be a good contribution for
> others also.

I think this is standard on github.

To subscribe to changes to the associated wiki, subscribe to:
https://github.com/huggyfee/VisualTW2/wiki.atom
To subscribe to commits on the project: https://github.com/huggyfee/VisualTW2/commits/master.atom
To subscribe to anything I'm doing on github: https://github.com/huggyfee.atom

> * and yet, why you (or Pascal) decided to host updates somewhere else,
> not at [1]?

If you look on the original site, it's not primarily about these
tools, and Pascal hasn't been able to maintain this for a few years,
so I offered to take this over. Rather than asking him to take on the
overhead of me asking to push all my updates, it made more sense to
host this on a more conventional platform for open source
development. If you search for TiddlyWiki on github, you'll see I'm
not the only one. It also allows others to easily fork from the
project (i.e. create their own versions) if they want to.

>
> [1]http://visualtw.ouvaton.org/VisualTW.html


Hope that answers your questions.

All the best

Simon.

[Bauwe Bijl]

Hi Simon

> That would be an excellent idea. Although the ZIP version is better
> for creating a blank TiddlyWiki, it would make sense to have a
> 'tryout' version from which the ZIP form can be downloaded (as on the
> main TiddlyWiki site)

Did you know can host a TiddlyWiki on git!? ... perhaps a good
idea ...:

""
Let’s say your GitHub username is “alice”. If you create a GitHub
repository named alice.github.com, commit a file named index.html
(!! :-) into the master branch, and push it to GitHub, then this file
will be automatically published to http://alice.github.com/
""

Bauwe

[huggyfee]

Hi Bauwe

Thanks for the suggestion. Yes, the project is hosted on github so
your suggestion would seem like a natural fit.

So as per your suggestion, I've created the initial fork in order to
get the 'site' you suggested - so as well as https://github.com/huggyfee/VisualTW2
there is a placeholder site at: http://huggyfee.github.com/VisualTW2/
- I'll take a look at this in the next few days and look at getting a
basic TiddlyWiki up there to act as a project homepage

As TiddlyWiki is now hosted on github as well, it seemed the natural
choice to house the project here. Looking at some of the other great
work on TiddlyWikis on github, it looks like the 'recipe' format might
be the best way to go ultimately, once I get my head around it. It
seems to break down TiddlyWiki into sensible components and sew them
back up again using a build process, making it easier to work on
definite parts of TiddlyWiki rather than one great big file - much
more natural wrt Source control. It might be worth me investigating
forking the main TiddlyWiki project as well to make sure nothing gets
broken - not sure if this is the best way to go though - this is my
first foray into Git, coming from a Svn / CVS background.

I've started getting a few other suggestions, which is really great at
this early stage, so will look at putting together a roadmap so people
can see when their suggestions get enacted.

Thanks again for your input,

Regards

Simon.

[Bauwe Bijl]

Hi Simon

> - I'll take a look at this in the next few days and look at getting a
> basic TiddlyWiki up there to act as a project homepage

For me it seems more useful if you use the new-visual tw in total as
project page...this way there is no need to download the entire zip.
And users can import plugins directly in their own tw.
The content in your current empty.html can be a default tiddler
(presenting the project)

Example (no worry...will remove this again in a couple of day's to get
my own tw back there):
http://bauwebijl.github.com/

Bauwe

[Bauwe Bijl]

correction:
The content in your current __INDEX.html__ can be a default tiddler
(presenting the project)

Bauwe