TiddlyWiki Revision 1.2.32

[Jeremy Ruston]

I've just published revision 1.2.32 of TiddlyWiki. It's a fairly minor
revision, mostly just tidying up (holidays and work have seen to
that). As usual, a big thank you to the people who have contributed
code and ideas for this revision; it's a pleasure to get such high
quality feedback.

Here's the rundown:

* Added to AdvancedOptions a checkbox for disabling editting when
working over HTTP
* Fixed problem with MonospacedText blocks appearing all on one line
in InternetExplorer, thanks to JoshGoebel and TiagoDionízio
* Fixed problem with an image followed by a link in the same
paragraph, thanks to JoshGoebel
* Fixed problem with tiddler lists in the MainMenu not getting updated
correctly, thanks to JonnyLeRoy
* Improved saving so that the <title> element of the document is set
to the SiteTitle, thanks to JonnyLeRoy. This helps search engines see
the 'real' title of a TiddlyWiki
* Fixed some stylesheet issues, thanks to TiagoDionízio
* Various minor refactoring to facilitate macro writing, thanks to a
bunch of useful suggestions from the discussion group
* Fixed problem with generating an RSS feed with fewer entries than
are specified in config.numRssItems, thanks to bsittler
* Improved fix for focus problems after editting a tiddler, thanks to
KevinKleinfelter
* Moved 'All' tab from the MoreTab up to the top level

I'm away from the web (again) for a few days now, but expect 1.2.33 next week...

Cheers

Jeremy.

--
Jeremy Ruston
mailto:jer...@osmosoft.com
http://www.tiddlywiki.com

[AlanH]

I see "disabling editing" over http is a new feature in TW. For
WebView users, this could replace one or two of the WebView settings,
but WebView also lets you show/hide tags, tabs, etc. so it will
continue to be a viable plugin (for now). I'm actually thinking of not
making any changes to WV at the moment figuring that folks have two
options:

1. TW's native checkbox to disable editing only
2. WV plugin that includes disabling editing as well as other interface
settings

~AlanH

[Jeremy Ruston]

Yeah, I was just trying to burn in the really basic functionality; I
agree that a macro is the best place for the fancier stuff.

Cheers

Jeremy.

[AlanH]

Jeremy Ruston wrote:
> expect 1.2.33 next week...

One (hopefully simple) wish list item. Can we separate the toolbar
button class from the tag button class? Right now they both use
".button" class. I'd like to be able to have the toolbar buttons
styled as actual buttons but have the tags appear as words until the
user hovers over them. I could hijack the function to change one of
their classes, but that seems a bit extreme.

~Alan

[AlanH]

Sorry to barrage...1.2.32 has some pretty nifty mods.

But how about using:
var newSiteTitle = getElementText("siteTitle");
if(!newSiteTitle || newSiteTitle == "")
newSiteTitle = "TiddlyWiki";

instead of:
var newSiteTitle =
store.getTiddlerText("SiteTitle","TiddlyWiki").htmlEncode();

This way, if there is wiki syntax in the title tiddler, it will not be
displayed in the document's title tag (which could trip up Google).

~AlanH

[Paul Dickson]

On Thu, 18 Aug 2005 08:16:37 -0700, AlanH wrote:

>
> I see "disabling editing" over http is a new feature in TW. For
> WebView users, this could replace one or two of the WebView settings,
> but WebView also lets you show/hide tags, tabs, etc. so it will
> continue to be a viable plugin (for now). I'm actually thinking of not
> making any changes to WV at the moment figuring that folks have two
> options:

Has anyone gotten this feature to work? I'm using using Firefox (Deer
Park Alpha 2 - Aug 2) and the edit option is there and usable.

The checkbox in AdvancedOptions follows the setting I placed in the
systemConfig tiddle.

-Paul

[AlanH]

Jeremy said in the TW documentation that you need to put a line into a
systemConfig tiddler that reads:

config.options.chkHttpReadOnly = true;

Did you try that?

The check box under AdvancedOptions is simply an override feature. It
doesn't disable the editing, but it will enable editing if it is set to
disabled when accessed via http.

More info at: http://www.tiddlywiki.com/#HideEditingFeatures

[Paul Dickson]

On Thu, 18 Aug 2005 11:47:32 -0700, AlanH wrote:

> Jeremy said in the TW documentation that you need to put a line into a
> systemConfig tiddler that reads:
>
> config.options.chkHttpReadOnly = true;
>
> Did you try that?

The setting of this value affects the checkbox, but the edit option
remains regardless.

> The check box under AdvancedOptions is simply an override feature. It
> doesn't disable the editing, but it will enable editing if it is set to
> disabled when accessed via http.
>
> More info at: http://www.tiddlywiki.com/#HideEditingFeatures

-Paul

[AlanH]

One idea I see for using this new TW feature is that subsequent plugins
can look at this value to set the editing on/off for any new plugin
features. For example, a calendar plugin might not allow a new tiddler
to be created for a clicked date on the calendar if editing is disabled
on the wiki when accessed via a website.

[Clint Checketts]

Alan quick note for styling the toolbar buttons versus mainmenu:

.footer .button{normal CSS rules for tags}
.toolbar .button{add rules to make toolbar buttons look like buttons}

This is my prefered usage because keeping classes the same is prefered for 'just in case' someone awanted to style them the same, then differences can be singled out by looking at the parents.

-Clint

[AlanH]

Thanks, Clint. I tried a number of things, but not that one. Sounds
like a much better approach.

Nix my previous request, JeremyR.

[Jonny]

An extra trick that might keep both sides happy is to apply multiple
classes to the buttons.

You can have <a href"blah" class="button tagButton"> - you can then
just style it using .button if you want or with .tagButton - or a
combination of the two.

[Will]

I can't get this to work either. Setting this to be checked via the
systemConfig tiddler had no effect.