Announcement: TiddlyWiki 2.6.6 goes "live"

[Eric Shulman]

Greetings All!

I am *very* pleased to report that version 2.6.6 of TiddlyWiki Classic
has now been advanced from beta status to full "live" status, and is
available for viewing/downloading from the main TiddlyWiki Classic web
address:
http://www.TiddlyWiki.com
Please read the [[WhatsNew]] tiddler for a summary of changes from the
previous version.

Among the more notable functional changes: the backstage "sync"
command and internal "sync machine" code have been removed from the
TiddlyWiki core and will be migrated to an optional plugin in a future
release (schedule to be determined). This saves several K of space
for code that was not needed by many TiddlyWiki users and simply added
to the overhead of each TiddlyWiki document without providing much
benefit in most cases.

Another notable change is the internal handling for
"defaultCustomFields" when saving tiddlers to TiddlySpace documents.
This fix, though not visible to the user, will allow most existing
plugins to successfully create/modify tiddlers and then store them
properly on TiddlySpace. Also, plugin/script writers should be aware
that the copy of jQuery embedded in TiddlyWiki has been updated from
v1.6.4 to v1.7.2.

Although most of these changes are not likely to be particularly
significant for many TiddlyWiki users, this long-awaited update still
represents a major milestone, as it marks the completion of the first
full build cycle following the transition to new build scripts and
TiddlyWiki5/nodeJS-based tools.

Now that this new process is in place, you can expect incremental
updates will occur much more often (every few months), depending upon
the complexity of the changes being made. The next planned update of
TiddlyWiki Classic will be version 2.7.0, and will focus on file I/O
issues (errors when saving and/or importing) that have been caused by
browser-level changes that have tightened security restrictions.
Until then, please see [[TiddlyWiki Browser Compatibility]] for
information on some current fixes/workarounds for some of these
problems.

enjoy,
-e
Eric Shulman
TiddlyTools / ELS Design Studios

HELP ME TO HELP YOU - MAKE A CONTRIBUTION TO MY "TIP JAR"...
http://www.TiddlyTools.com/#Donations

Professional TiddlyWiki Consulting Services...
Analysis, Design, and Custom Solutions:
http://www.TiddlyTools.com/#Contact

[cdent]

On Sep 18, 4:27 pm, Eric Shulman <elsdes...@gmail.com> wrote:
> I am *very* pleased to report that version 2.6.6 of TiddlyWiki Classic
> has now been advanced from beta status to full "live" status, and is

Yay!

I've updated TiddlySpace and its dependent packages to use the new
2.6.6 version of TiddlyWiki, so now on http://tiddlyspace.com the
TiddlyWikis are up to date with the latest.

http://pypi.python.org/pypi/tiddlywebwiki
http://pypi.python.org/pypi/tiddlywebplugins.tiddlyspace

Thanks for bringing all the pieces together Eric.

[TonyM]

Great work folks.

I had to Shift reload in FireFox (15) to see the new version at tiddlywiki.com

I then made a backup of my tiddlywiki and tried to use the upgrade process in the Backstage and it is reporting you already have the latest version. I do not, I have 2.6.5

If something else required to be done ?

Thank
Tony

[Eric Shulman]

> I then made a backup of my tiddlywiki and tried to use the upgrade process
> in the Backstage and it is reporting you already have the latest version. I
> do not, I have 2.6.5
> If something else required to be done ?

The upgrade process looks at:
http://tiddlywiki-releases.tiddlyspace.com/upgrade
but that location has not been updated yet, so it still thinks 2.6.5
is current. I'll post a follow up whan that is corrected.

-e

[TonyM]

Great, Glad I could help point it out.

The TiddlyWjki community is one of the best.

Tony

[Tobias Beer]

Great job, Eric!

I'd very love to get a deeper understanding on the build process as well as source code management details used for the core / recomenneded for plugin authors.

If it doesn't overly bloat the thread, please be so kind reference any available background information on that floating around.

Thanks, Tobias.

[PMario]

Great Work!

I've seen, you marked some topics at github allready with milestone
2.7.0. ... good.
If changes are pushed to the main repo, in normal cases I'm going to
view and test them quite frequently. So if file IO testing is needed,
just push and notify me.

I can test with:

ubuntu 12.04,
-- FF (stable),
-- cromium (stable),
-- chrome(stable)

win 7
-- FF (stable)
-- Chrome
-- Opera
-- Safari
-- IE9

Just a reminder: The main repo should be tagged
https://github.com/TiddlyWiki/tiddlywiki/tags

regards
mario

[PTP]

This does not work for me: steps 1 and 2 works fine, but step 3 does not!

Importing (the exported ExportTiddlersPlugin with core code, see attached file) in my old wiki does not overwrite the core code. I still have the Version 2.6.5).

Any idea? TIA!

Am Dienstag, 2. Oktober 2012 22:12:08 UTC+2 schrieb Igor Perković:

From last two versions 2.6.5 and 2.6.6, I experienced problems with upgrade.

I've tried all suggestion I can read on web, with no luck.

Here is my solution:

1. Download the empty.html in my Tiddlywiki root directory

2. Save ExportTiddlersPlugin to empty.html

3. Export this plugin to my old TiddlyWiki file and because of exporting core code too, I easily managed to upgrade on latest version.

That works for me last two times. I'm using Opera 12.02 on Windows 7.

Maybe this could be helpful for someone.

Best regards!

IgorP 

[Igor Perković]

PTP,

In step 3.

Go to "export to:" item and in the box where is ...export.hrml  erase export and write exact name of your target file. Ie, if you have Organizer.html with TW 2.6.5, then type Organizer.html. Be sure that your original file and empty.html are in the same directory, or change path if not.

Then choose ExportTiddlersPlugin and export.

After export, go to original file, save all changes and refresh.

Hope it'll be ok.

Regards!

[Igor Perković]

Or, to be more concret:

http://youtu.be/qvf-doulu4E

Enjoy! 

[PTP]

Merci bien! :-) Works fine now!

BTW: I didn't know the "export into another TW" feature. :-/