Hi Danielo

On Tue, Sep 2, 2014 at 3:10 PM, Danielo Rodríguez <rdani...@gmail.com>
wrote:

> I think this sentence is depressing:
>
>  we've adopted new prefixes for messages, classes and variables that mean
>> that this release will break almost all plugins and customisations created
>> for earlier versions.
>
>
I'm not a fan of making backward incompatible changes either.


> Specially the part
>
> we've adopted new prefixes for messages, classes and variables
>
>
> I find it a very poor explanation for something that breaks "all plugins
> and customisations". I would like a list of what was the previous value and
> what is the new one.
>

That passage isn't attempting to explain the reasoning for the change, it's
focussed on the consequences for end users.

In terms of the details of the change, it really is as simple as the
release note says: a search and replace from tw->tc, tm and tv. I think
that that is all anyone needs to know to adapt existing code to the change.
(There are some prefixless classes that have gained the tc prefix too, and
they are listed in the ticket referenced in the release note).


> On every TW release I have to spend a lot of time trying  how new things
> works. I can assume it for new features and small changes but not for
> everything.
>

That will stop once we get to the full release; then each release will be
backwards compatible.

I will think really carefully if I should spend time and effort developing
> anything for TW until it comes out of this unstable state.
>

As I mentioned above, the full release is scheduled for September 20th.

I'm pretty sure you have your reasons for do this, and I wish tiddlywiki to
> have a long life too,  but it takes me out of the scene for a long time. I
> will monitor TW closely, and I will only upgrade if there is no other
> option.
>

The reason for the change is that it was confusing for new users to be
using the same prefix for three completely different things:

 * Classes like tw-drop-down
 * Messages like tw-save-tiddler
 * Variables like tw-auto-open-on-import

The concern is that that makes it almost impossible for a newcomer to
figure out what's going on. I understand that you and other contemporary
users have got used to the situation, but I have to look at it from the
point of view of future new users as well.

If it is possible, I would like to have the 5.0.15 nodejs version available
> somewhere.
>

It's available via GitHub, but obviously I can't offer any support in the
future for old beta versions.

Best wishes

Jeremy




>
>
> El martes, 2 de septiembre de 2014 15:03:32 UTC+2, Jeremy Ruston escribió:
>>
>> I'm delighted to announce the release of TiddlyWiki 5.0.16-beta:
>>
>> http://tiddlywiki.com
>>
>> The new features and bug fixes are listed below, but the most significant
>> changes are internal. In particular, we've adopted new prefixes for
>> messages, classes and variables that mean that this release will break
>> almost all plugins and customisations created for earlier versions. See the
>> release note for more details.
>>
>> Making such a big change is always undesirable, and is not undertaken
>> lightly. I'm hoping that TW5 will enjoy a long life, and be used for many
>> decades to come. That's why I think it's worth taking some pain now in
>> order to try to make the eventual product better.
>>
>> Anyhow, other changes in this release include:
>>
>> * Amended behaviour of the tm-browser-refresh message so that it no
>> longer clears the location hash
>> * Fixed problem with single line macro definitions incorrectly including
>> whitespace in the value
>> * Extend TableOfContentsMacro to use the caption field if present
>> * Added suffix and removesuffix filter operators
>>
>> Another important addition is the introduction of a preliminary version
>> of the tw2parser plugin (developed by @buggyj). This component allows
>> TiddlyWiki5 to display wikitext created for TiddlyWiki Classic. As well as
>> supporting the classic WikiText format, tw2parser includes a number of
>> macros and other features from TWC. The new component is not yet ready for
>> primetime, but you can experiment and find out more at:
>>
>> http://tiddlywiki.com/classicparserdemo.html
>>
>> You can upgrade at http://tiddlywiki.com/upgrade.html - but please,
>> please make sure that you keep careful backups of your content.
>>
>> Any feedback or questions welcome here. Any questions from a development
>> perspective should be posted to the dev group over at
>> http://groups.google.com/group/TiddlyWikiDev.
>>
>> Many thanks to all the contributors for their patient work on this
>> release,
>>
>> Best wishes
>>
>> Jeremy
>>
>> --
>> Jeremy Ruston
>> mailto:jeremy...@gmail.com
>>
>


-- 
Jeremy Ruston
mailto:jeremy.rus...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tiddlywiki+unsubscr...@googlegroups.com.
To post to this group, send email to tiddlywiki@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

Reply via email to