[TW5] Is there a single, concise upgrade HowTo anywhere?

[Loyd Gravitt]

I have been using TWC since 2011, over the years making it my single main documentation repository for all of my IT notes and documentation.  As TWC had had more and more browser specific issues with javascript problems, save difficulties and everything else, I decided maybe it is time to look at upgrading to TW5.  I have done a couple of hours of reading and found the upgrade assistant.  I tried that and of course it now wants me to upgrade each tiddler as I open it to convert the classic tiddly markup to the new.  The problem is, It totally scrambles the formatting of every tiddler.  As an IT person, I have made extensive use of the {{{ ... }}} markup for blocks of code.  These are all pretty much illegible after the "upgrade".  So now it appears that I have the choice on whether or not I want to manually reformat between 600 and 700 tiddlers, stick with the growing pains of TWC, or just punt and use another tool.

Is there a simple, single document or sticky thread that contains instructions for moving from the classic platform to the 5 version?  And before someone says to search and read all of the messages already here, I do not have time.  My boss is paying me to administer databases and servers, not dig into the intricacies of jason, css, and node,js.  I am already regretting the time I invested in learning classic tiddly markup and plugin architecture as that is now worthless.

I have done some searching of the Google Group and seen some threads about further development of upgrade tools similar to what I am looking for.  Can anyone give a status or timeframe on these?

I apologize for the tone of frustration in this post, but time is limited and I am not wanting to do much tweaking or development within the platform.  I am just a user, by no means technically illiterate, who just wants to take almost six years of accumulated tiddlers and seamlessly upgrade them to the new format.

Thank you in advance for any help anyone can hopefully give me and Happy New Year.

[Mat]

 And before someone says to search and read all of the messages already here, I do not have time.  My boss is paying me to 

 

Haha, clearly you have a sense of humour which is very good when asking others to work for you for free so you can get paid!

<:-)

[Mark S.]

My "strategy" was to simply import everything and then fix what I needed as I needed it or encountered it, or in those "lull" times when the brain isn't fully occupied. I figured as time went on I'd become more comfortable with the new syntax and widget structure and know how to do this-for-that conversions more readily. The problem is, especially with so much dependent on plugins, that it's more like translating from Esperanto to Klingon. It kind of has to be done on a case-by-case basis.

Good luck!
Mark

[Loyd Gravitt]

Ah yes, someone saying, yes there is a link at ....... or no, there is no such document is so incredibly time consuming.

I have answered many such questions freely on many such boards before, it's called COMMUNITY.

And it is considered good practice to produce a test a migration path before one purposely renders a software product no longer backwards compatible.

[Loyd Gravitt]

I am not asking anyone to write such a guide, only if anyone has seen one.  Sorry for any misunderstanding. 

[PMario]

Hi Loyd,

I did create a comparison TW in 2014 for myself. It contains information that I did consider valuable. So I'm pretty sure it is incomplete.
http://compare-tw2-tw5.tiddlyspace.com/#CompareTwc-Tw5

Updating TWc to TW5 also depends on the number of plugins, that extend / change the TW syntax.

For me it was relatively simple to convert my stuff, since I was using a plugin called "lineBreakHack", that produced the same "paragraph" handling as TW5 does today. ...

Since tiddlyspace.com may be closed down anytime soon, you can find the stuff at the online-archive. http://web.archive.org/web/20161205103254/http://compare-tw2-tw5.tiddlyspace.com/

I personally use a "find and replace" workflow for content that needs conversion. For existing "read only" stuff I still use TWc.

have fun!
mario

[BJ]

there is also the tw classic plugin for tw5. This does not support tw2 plugins, only the the classic markup, but it does support macros and can embed tw5  markup in tw2 tiddlers.

all the best and a happy new year
BJ

http://tiddlywiki.com/plugins/tiddlywiki/tw2parser/#Markup

[Dmitry Sokolov]

Good stuff Loyd,

is your issued resolved?
Your thread is processed and seems being extremely valuable:
http://confocal-manawatu.pbworks.com/w/page/114222940/TW5%20Is%20there%20a%20single%2C%20concise%20upgrade%20HowTo%20anywhere
A number of nodes is added to the knowledge network.

Many thanks to you,
Dmitry
BTW, I am trying to develop a business model based on TW. Further development of TW into a stable platform could be an option. Would you (your boss) be interested to participate?
At the moment, I am collecting all relevant information for the case, see link above.
The knowledge network can also be browsed visually: http://debategraph.org/Stream.aspx?nid=457381&vt=bubble&dc=focus
It's all about "findability / discoverability for reuse".

[Jeremy Ruston]

Hi Lloyd

I have been using TWC since 2011, over the years making it my single main documentation repository for all of my IT notes and documentation.  As TWC had had more and more browser specific issues with javascript problems, save difficulties and everything else, I decided maybe it is time to look at upgrading to TW5.

There aren’t any browser-specific issues that affect TWC but not TW5. I would say that the only reason to upgrade an existing TWC wiki to TW5 is if you want to take advantage of the new features. If not, and TWC is working OK for you, there’s really no reason to upgrade. TiddlyFox and TiddlyDesktop support TWC alongside TW5, and will continue to do so.

Best wishes

Jeremy.

I have done a couple of hours of reading and found the upgrade assistant.  I tried that and of course it now wants me to upgrade each tiddler as I open it to convert the classic tiddly markup to the new.  The problem is, It totally scrambles the formatting of every tiddler.  As an IT person, I have made extensive use of the {{{ ... }}} markup for blocks of code.  These are all pretty much illegible after the "upgrade".  So now it appears that I have the choice on whether or not I want to manually reformat between 600 and 700 tiddlers, stick with the growing pains of TWC, or just punt and use another tool.

Is there a simple, single document or sticky thread that contains instructions for moving from the classic platform to the 5 version?  And before someone says to search and read all of the messages already here, I do not have time.  My boss is paying me to administer databases and servers, not dig into the intricacies of jason, css, and node,js.  I am already regretting the time I invested in learning classic tiddly markup and plugin architecture as that is now worthless.

I have done some searching of the Google Group and seen some threads about further development of upgrade tools similar to what I am looking for.  Can anyone give a status or timeframe on these?

I apologize for the tone of frustration in this post, but time is limited and I am not wanting to do much tweaking or development within the platform.  I am just a user, by no means technically illiterate, who just wants to take almost six years of accumulated tiddlers and seamlessly upgrade them to the new format.

Thank you in advance for any help anyone can hopefully give me and Happy New Year.

--
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+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/140a3491-18f3-46ac-a6f8-8502894cfa21%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.