Announcing two versions of updated TW Notes

[Morris Gray]

Here are two customized versions of Dave Gifford's NoBrainerNotes.

You can now easily create multiple Master Topics (the meaning of
Master Topics has changed from the original since multiples are
allowed now). The topics in the MainMenu are now tiddlers instead of
hard coding so they can easily be used elsewhere in the TiddlyWiki if
need be, or copied/imported to other TW Notes. SubTopics are now
easily created within each Master Topic.

TW Notes like the original NoBrainerNotes uses the history plugin
allowing forward and back movement between tiddlers as well as a drop
down history.

http://twnotes.tiddlyspot.com/

TW T-Notes is a tabbed version that has all the same functionality as
TW Notes but uses TiddlersBarPlugin to provide a tab for each opened
tiddler. I believe this gives greater ease moving between tiddlers
when organizing notes and cutting and pasting between them.

http://twt-notes.tiddlyspot.com/

I used TW Notes in a sometimes wild free flowing culture exchange with
35 students year 5 to year 8 and the ease with which it was done I was
thanking Dave Gifford several times a day.

Thanks again Dave. I wouldn't mind your comments on my customization
of your masterpiece and if you can find any flaws in it.

Morris Gray
http://twhelp.tiddlyspot.com
A TiddlyWiki help file for beginners

[Dave Gifford - http://www.giffmex.org/]

Wow, Morris, it is indeed a Merry Christmas for TW users. First the
fadingmessagesplugin today and now these cool modifications!

The TW-T notes is fascinating. It is both one tiddler at a time and
multiple tiddlers at a time. What a great combination. The only
drawback of course is the need to close every one separately later. I
would recommend reinstating 'close others' to the tiddler toolbar if
you are doing that, and maybe just maybe have a 'close all' macro
somewhere visible.

I will have to update NBN with a few of your features if you don't
mind, especally having the history macros in each tiddler. I assume
you have made that so that it won't print when the tiddler is printed?

I'm wondering if you can explain the mish-mash thing. I looked at the
thread and still don't get it. Is it something that improves the left-
hand TOC in some way?

One smallísimo suggestion: change index to indexes in the sidebar,
since there are several indexes there.

Another possibility: I made one small tweak this month to NBN that you
might want to incorporate. A friend wanted to create a 'Print all'
tiddler with a FET code in it pulling up all note and topic tiddlers
in alphabetical order. But the way NBN was set up before, the
subtopics and subsubtopics and note tiddlers created with newhere
weren't getting tagged as notes. So what I did was change the
newhereplugin so that it adds the tag 'note' to all tiddlers created
with the newhere macro. Then all topics, subtopics and notes will be
listed by any ForEachTiddler index anyone creates. Just grab the
Newhereplugin off my NBN. I really should change the name of it since
I have modified it. I'll get to all this stuff one of these days...

Again, kudos to you. Blessings and Merry Christmas,

Dave Gifford

[Dave Gifford - http://www.giffmex.org/]

Morris, I see you *haven't* made it so that the history macro in the
tiddlers doesn't print. I'm sure it's an easy fix, but I confess that
I tried two ideas to fix it and they didn't work. When you get that
done, make sure to post or send me instructions on that...

Dave

[Eric Weir]

On 12/22/2008 Morris Gray wrote:

> TW T-Notes is a tabbed version that has all the same functionality as
> TW Notes but uses TiddlersBarPlugin to provide a tab for each opened
> tiddler. I believe this gives greater ease moving between tiddlers
> when organizing notes and cutting and pasting between them.
>
> http://twt-notes.tiddlyspot.com/

Thanks for this, Morris. I was tempted by No-Brainer Notes when Dave
first released it, but by that time I had gotten used to working with
TiddlersBarPlugin and was reluctant to switch over to HistoryPlugin. In
addition to that, you've incorporated many of the tweaks I've been using
in MPTW TWs along with TagglyTagging functionality. I like also that
plugins have been put under a separate tab in the tiddlers list in the
sidebar, something that was next on my list of contemplated tweaks.

There are some things that are not to my tastes -- choice of colors,
font size in the top menu, duplication of the search window, etc. -- but
those can be my next learning projects. TW T-Notes [or TW Notes-Tabbed]
may just become my default TW.

> I used TW Notes in a sometimes wild free flowing culture exchange with
> 35 students year 5 to year 8 and the ease with which it was done I was
> thanking Dave Gifford several times a day.

Might be a little off-topic, but I'm kinda curious about this. Hadn't
envisioned you as an elementary school teacher, and maybe you're not,
but this is intriguing. Could you tell us a little more?

Thanks,
------------------------------------------------------------------------
Eric Weir
Decatur, GA USA
eew...@bellsouth.net

[Dave Gifford - http://www.giffmex.org/]

Actually, I figured it out now. I changed the class to toolbar, which
killed two birds with one stone: made the color the way I wanted it,
and kept it from being printed.

Dave

[MrMakeveli]

I really like the sidebar/main menu that you guys have. I tried
looking for the Tiddler that contains but was unable to. How might I
incorporate a similar structure to my main menu? I like the simple
tree-like structure and the easy expansion/collapse.

> Morris Grayhttp://twhelp.tiddlyspot.com

[Dave Gifford - http://www.giffmex.org/]

@MrMakaveli

Morris' mainmenu is built on mine so I don't think I'm out of line by
answering this.

It's not easy to explain our MainMenus since it is a rather
complicated web of plugins and scripts. Double click on the tiddler
MainMenu and you will see the script and the macro used there. One is
for the refresh button, and the next is the foreachtiddler index. That
index is what populates the table of contents.

Also see the tag systemConfig to see what plugins were used. I
basically liked Simon's SiteMapMacro and used that, but it required a
few other plugins. If I'm not mistaken, InlineJavascriptPlugin and
NestedSlidersPlugin (which I had to adapt slightly). There are also
CSS styles applied to it for the look of it.

One difference between Morris' and mine: With Morris' the scripts
mentioned above are in the tiddlers for the main topics (He has Topic
and Topic2 on display for you). The advantage of this is that the
topics show up with bold red titles in contrast to the notes and
subtopics within them. Nice visual touch. The drawback is that you
have to manually add the topics to the mainmenu, and that you can't
collapse the main topics down, you have to see the entire menu for
each topic. With mine, the topics subtopics and notes are all the same
font styles, but they get automatically added to the mainmenu and can
be collapsed completely. You can pick which is the better fit for you.

I'm sure that doesn't help much, but I'm really at a loss as to what
else to tell you. Blessings

Dave Gifford

[MrMakeveli]

> Morris' mainmenu is built on mine so I don't think I'm out of line by
> answering this.

Not at all, it was aimed at you both!

> It's not easy to explain our MainMenus since it is a rather
> complicated web of plugins and scripts. Double click on the tiddler
> MainMenu and you will see the script and the macro used there. One is
> for the refresh button, and the next is the foreachtiddler index. That
> index is what populates the table of contents.

For my purposes (information archive) a static menu is preferred, so I
shouldn't need an auto-populating menu. I could see that being an
extremely useful application, though.

> Also see the tag systemConfig to see what plugins were used. I
> basically liked Simon's SiteMapMacro and used that, but it required a
> few other plugins. If I'm not mistaken, InlineJavascriptPlugin and
> NestedSlidersPlugin (which I had to adapt slightly). There are also
> CSS styles applied to it for the look of it.

The NestedSlidersPlugin was exactly what I was looking for. I now have
a smooth and visually pleasing, yet simple, main menu.

Thanks so much.
Jon

[Eric Shulman]

> The NestedSlidersPlugin was exactly what I was looking for. I now have
> a smooth and visually pleasing, yet simple, main menu.

I really recommend installing an up-to-date version of
NestedSlidersPlugin directly from www.TiddlyTools.com. The version
in Dave and Morris' documents is really, really old (v1.9.0 from May,
2006), and lacks all the latest enhancements, optimizations and bug
fixes. In addition, as near as I can tell, Dave's tweak was to add
arrows following the slider button text, so that they could toggle
between ">" when closed and "<" when closed. When you update to using
the latest TiddlyTools distribution (v2.4.9), you can use the
'alternative label' syntax to specify the text to toggle, like this:

+++[click to open >][click to close <]
content goes here
===

enjoy,
-e
Eric Shulman
TiddlyTools / ELS Design Studios

P.S. To Morris and Dave: Inasmuch as your documents are being
specifically published for redistribution to TiddlyWiki newbies,
please try to use the latest versions of TiddlyTools plugins, so that
new users are getting the most up-to-date features and bug fixes, and
I don't have to field lots of questions related to problems with
'legacy' code from much older versions of those plugins. Thanks.

[Dave Gifford - http://www.giffmex.org/]

Dave's tweak was to add
> arrows following the slider button text, so that they could toggle
> between ">" when closed and "<" when closed.  When you update to using
> the latest TiddlyTools distribution (v2.4.9), you can use the
> 'alternative label' syntax to specify the text to toggle, like this:
>
> +++[click to open >][click to close <]
>    content goes here
> ===

Eric, but if my 'slider' is a script and not a slider as such, where
and how do I put this?

> P.S. To Morris and Dave: Inasmuch as your documents are being
> specifically published for redistribution to TiddlyWiki newbies,
> please try to use the latest versions of TiddlyTools plugins, so that
> new users are getting the most up-to-date features and bug fixes, and
> I don't have to field lots of questions related to problems with
> 'legacy' code from much older versions of those plugins.  Thanks.

Better idea: stop updating stuff so often, you silly nut!

Dave

[Dave Gifford - http://www.giffmex.org/]

The version
> in Dave and Morris' documents is really, really old (v1.9.0 from May,
> 2006),

Eric, I just updated the plugin for No-Brainer Notes but reinserted my
tweak. I put a note in the plugin in all caps that users should get
clean updated copies from your site.

Dave

[Eric Shulman]

> > arrows following the slider button text, so that they could toggle
> > between ">" when closed and "<" when closed.  When you update to using
> > the latest TiddlyTools distribution (v2.4.9), you can use the
> > 'alternative label' syntax to specify the text to toggle, like this:
>
> > +++[click to open >][click to close <]
> >    content goes here
> > ===
>
> Eric, but if my 'slider' is a script and not a slider as such, where
> and how do I put this?

I assume you are talking about sliders generated by <<siteMap>>...

If so, then the formats for those sliders are defined within the
SiteMapMacro plugin code.

You can re-define these formats by creating a separate
[[SiteMapMacroTweak]] tiddler, tagged with 'systemConfig', containing:

config.macros.siteMap.sliders.formatString="[[%1]]+++[&#x25BA;]
[&#x25C4;]\n%2===\n\n";
config.macros.siteMap.openSliders.formatString="[[%1]]++++[&#x25BA;]
[&#x25C4;]\n%2===\n\n";
config.macros.siteMap.popups.formatString="[[%1]]+++^[&#x25BA;]
[&#x25C4;]\n%2===\n\n";
config.macros.siteMap.openPopups.formatString="[[%1]]++++^[&#x25BA;]
[&#x25C4;]\n%2===\n\n";

The only difference between the above and the existing format defned
by the plugin is the addition of:
"[&#x25BA;][&#x25C4;]"

Basically, what these lines do is to use the right (&#x25BA;) and left
(&#x25C4;) arrow symbols as the slider label and alt label. When the
slider is closed, the right arrow (25BA) is shown. When the slider is
open, the left arrow (25BA) is shown. Of course, you could use any
label/alt label pair you like to suit your purposes...

By using a separate 'tweak' tiddler to overlay to SiteMapMacro, you
will then be able to distribute an *unmodified* version of
NestedSlidersPlugin, while still achieving the same end-user
appearances and behavior.

[Dave Gifford - http://www.giffmex.org/]

Eric

I got this error

URIError: malformed URI sequence

Any advice?

Dave

[Dave Gifford - http://www.giffmex.org/]

> I assume you are talking about sliders generated by <<siteMap>>...

Not exactly. I have this:

<<forEachTiddler
where
'tiddler.tags.contains("Topics")'
script
'
function getFirstLine(s) {
var m = s.match(/\s*(.*)/);
return m != null && m.length >= 1 ? m[1] : "";
}
'
write
'getFirstLine(tiddler.text)'
>>

[Morris Gray]

> There are some things that are not to my tastes -- choice of colors,
> font size in the top menu, duplication of the search window, etc. -- but
> those can be my next learning projects. TW T-Notes [or TW Notes-Tabbed]
> may just become my default TW.

Choice of colours is personal but you can change them to suit yourself
that's the fun of a TiddlyWiki :-) I'm actually using a graphic with
a badly designed gradient fallback for offline use (It's in TopMenu)
The font size can be also be changed in TopMenu in style="font-size:
10pt;" I've just upped it from 9pt for you.

> Might be a little off-topic, but I'm kinda curious about this. Hadn't
> envisioned you as an elementary school teacher, and maybe you're not,
> but this is intriguing. Could you tell us a little more?

LOL, thank goodness I am not a teacher :-) I was just working with
Granite Bay Montessori school in California and recording the
proceedings here in Australia. If you want to see it I'll send you
the link privately. It has some really good stuff in it to show them
some of the capabilities of TiddlyWiki.

I'm pleased you like the customization.

Morris

[Eric Shulman]

> URIError: malformed URI sequence

hmmm... try changing
[&#x25BA;][&#x25C4;]
to
[\u25BA][\u25C4]

Not sure if that'll fix it, but it's worth a try...

-e

[Dave Gifford - http://www.giffmex.org/]

Nope, didnt work

Dave

[Eric Shulman]

> > I assume you are talking about sliders generated by <<siteMap>>...
>
> Not exactly. I have this:
>
> <<forEachTiddler
>  where
>  'tiddler.tags.contains("Topics")'

...
> write
>  'getFirstLine(tiddler.text)'

Actually, all this script does is output the first line of each
tiddler tagged with "Topics"... and, based on the SampleTopic in your
doc, it seems that line is simply an invocation of <<siteMap>>...

-e

[Morris Gray]

On Dec 23, 6:18 am, "Dave Gifford - http://www.giffmex.org/"

<giff...@gmail.com> wrote:

> The drawback is that you
> have to manually add the topics to the mainmenu, and that you can't
> collapse the main topics down, you have to see the entire menu for
> each topic. With mine, the topics subtopics and notes are all the same
> font styles, but they get automatically added to the mainmenu and can
> be collapsed completely. You can pick which is the better fit for you.

Dave you've forgotten there is an important major, major difference
between TW Notes and NoBrainer.

As I noted in TW Notes, the meaning of Master Topic has changed from
the NoBrainer version. In TW Notes the Master Topic as you can see is
in red and each one of those is the same as the single one in
NoBrainer that you call Topic Index. They each behave exactly the
same as Topic Index and collapse just as far.

They each individually automatically add sub topics exactly the same.
They don't collapse because what you call a Master Topic in NoBrainer
is actually the first sub-topic in TW Notes. (With a single topic in
TW Notes it's the same as NoBrainer.) If you understand what I mean.

The only manual adding is after you've created a new Master Topic is
to insert it into MainMenu. And it's worth the effort because what
you are actually doing is creating another NoBrainer within TW Notes.
Please understand they are two different animals and TW Notes is
higher up the food chain :-)

TW Notes in the demo as you see it is worth two NoBrainers and can
easily evolve further.

I have incorporated most of your changes and suggestions including the
updated plugins and printing considerations. The cooperation is great
but we might be creating a rod for our own backs with two versions of
both:-)

I have Christmas presents to wrap now and may take a short break.

All the best and blessings to you and yours for the holidays.

Morris


On Dec 23, 6:18 am, "Dave Gifford - http://www.giffmex.org/"

[MrMakeveli]

>When you update to using
> the latest TiddlyTools distribution (v2.4.9), you can use the
> 'alternative label' syntax to specify the text to toggle, like this:

Thanks for the tip, I actually searched online for it rather than get
it from that source just to be sure it was up-to-date. Fortunately, I
have 2.4.9 in there already.

> +++[click to open >][click to close <]
>    content goes here
> ===

I didn't see this in the documentation (its not in the syntax or
examples).

Thanks for the info. I will try it out.
Jon

[Eric Shulman]

> > +++[click to open >][click to close <]
> >    content goes here
> > ===
>
> I didn't see this in the documentation (its not in the syntax or
> examples).

The documentation includes this:

{{class{[label=key|tooltip][altlabel|alttooltip]}}}
uses label/tooltip/accesskey. {{class{...}}}, =key, |tooltip and
[altlabel|alttooltip] are optional. 'class' is any valid CSS class
name, used to style the slider label text. 'key' must be a single
letter only. altlabel/alttooltip specify alternative label/tooltip for
use when slider/floating panel is displayed.

-e

[Dave Gifford - http://www.giffmex.org/]

> <giff...@gmail.com> wrote:
> > The drawback is that you
> > have to manually add the topics to the mainmenu, and that you can't
> > collapse the main topics down, you have to see the entire menu for
> > each topic. With mine, the topics subtopics and notes are all the same
> > font styles, but they get automatically added to the mainmenu and can
> > be collapsed completely. You can pick which is the better fit for you.
>
> Dave you've forgotten there is an important major, major difference
> between TW Notes and NoBrainer.
>
> As I noted in TW Notes, the meaning of Master Topic has changed from
> the NoBrainer version.  In TW Notes the Master Topic as you can see is
> in red and each one of those is the same as the single one in
> NoBrainer that you call Topic Index.  They each behave exactly the
> same as Topic Index and collapse just as far.

Hi Morris, I hope you didn't take my comment as a slight of your new
creation, because it wasn't meant that way. I understood perfectly
what you are describing here when I wrote. I realize that each Master
topic is its own No-Brainer index. It's a cool idea. And I like being
able to have separate formatting for the master topics. It's something
I always wished I could do in NBN but don't see how it can be done
except your way. My comment was only meant to point out the advantages
and disadvantages of each approach. With your way, the advantage, as I
see it, is the formatting, a definite weakness of mine, since whatever
CSS is applied to master topics gets applied to the whole index. With
my way the advantage is that all the subtopics and notes can be buried
under the master topic, whereas your first layer of subtopics for
every master topic is always visible, taking up valuable vertical real
estate.

> The only manual adding is after you've created a new Master Topic is
> to insert it into MainMenu.  And it's worth the effort because what
> you are actually doing is creating another NoBrainer within TW Notes.

I agree that it is worth the effort. I too have projects that require
a little assembly to make them work well. My comment about it being a
drawback is just from experience here, especially with the original
TiddlyDu2 creation process, that newbies don't want to have to add
anything. So for them it's a drawback.

> Please understand they are two different animals and TW Notes is
> higher up the food chain :-)

In versatility, yes. In simplicity, no. That's why I think having two
versions is worth it. Many will appreciate your more nuanced search
options, your take on master topics, your gradients, your extra
quickedit options, your more complete instructions, etc. Others will
want my simplicity, my clean flat spaces and the full collapsibility
of my mainmenu.

I hope that you don't see my revisions today as competition or
oneupmanship. Long ago you came out with the first TW Notes as a tweak
of mine. I thought at the time that I needed to incorporate a couple
of your changes, and never got to it. Today upon seeing your further
improvements, and because a couple things I meant to do today got shot
down by circumstances, I found the time and motivation to do what I
always meant to do before.

So to sum up, once again thanks for the new TW toy under the tree. And
have a wonderful Christmas!

Dave

[MrMakeveli]

> {{class{[label=key|tooltip][altlabel|alttooltip]}}}
> uses label/tooltip/accesskey. {{class{...}}}, =key, |tooltip and
> [altlabel|alttooltip] are optional. 'class' is any valid CSS class
> name, used to style the slider label text. 'key' must be a single
> letter only. altlabel/alttooltip specify alternative label/tooltip for
> use when slider/floating panel is displayed.

Uhh.. I still don't see that in there, so it must just be the fact
that I'm new to this and all that doesn't mean anything to me. haha. I
do know the tool tip, and the altlabel, but I don't know what an
accesskey is.

[Eric Shulman]

> > {{class{[label=key|tooltip][altlabel|alttooltip]}}}

...

>
> Uhh.. I still don't see that in there

hmmm.... puzzling... are you looking at NestedSlidersPluginInfo (the
*documentation* for NestedSlidersPlugin)? If so, you should be seeing
a section labeled "usage" that starts with a short paragraph, followed
by some bullet points summarizing the NestedSliders features, and then
a yellow box containing the complete syntax, followed by an
explanation of each part of that syntax.

If this is not the case, then please go here to get the documentation:
http://www.TiddlyTools.com/#NestedSlidersPluginInfo

-e

[MrMakeveli]

> hmmm.... puzzling... are you looking at NestedSlidersPluginInfo (the
> *documentation* for NestedSlidersPlugin)?

I did have that tiddler, and now I understand now how it works. The
first [..] is the txt, and then the second [..] is the alt text
(displayed after it has been clicked/hovered over), is that correct?