On Jan 29, 3:34 am, Mike <eris...@gmail.com> wrote: > Speaking of fET, I was hoping to be able to migrate all of my scripts > (InlineJavascriptPlugin) > Last year I converted all of my fET to ILJS, and have an extensive > amount scripts throughout my daily use TW
I have been doing the same thing. While fET is tremendous it does cause one to avoid learning Javascript which is much more generally useful. Supporting migration of legacy fET might be necessary in the beginning, but I don't think it should ultimately take precedence as a core support over the Javascript standard. Morris On Jan 29, 3:34 am, Mike <eris...@gmail.com> wrote: > Speaking of fET, I was hoping to be able to migrate all of my scripts > (InlineJavascriptPlugin) > Last year I converted all of my fET to ILJS, and have an extensive > amount scripts throughout my daily use TW > > As all things go, I anticipate it may be a while before I could change > into TW5 completely, but I look forward to the new possibilities it > creates. > > I took a look at the source after reading Paul's comments, and that > also looks very tidy - a lot of it is over my head, but the general > organization is much better. > > Mike > > On Jan 28, 2:38 am, Jeremy Ruston <jeremy.rus...@gmail.com> wrote: > > > Paul's correct, out of the box, it won't be possible to drop existing > > TiddlyWiki plugins into TiddlyWiki5. This is because the underlying > > programming model has had to change quite a bit to enable the new > > features. > > > I believe that it would be possible to write a little mapping layer > > that would provide traditional TiddlyWiki APIs within TiddlyWiki5. > > With such a thing, it may be possible to get some plugins to run. I'm > > specifically interested in the little edge case of being able to > > migrate some decent percentage of foreachtiddler incantations. > > > Cheers > > > Jeremy > > > On Wed, Jan 27, 2010 at 9:00 PM, Paul Downey <paul.dow...@whatfettle.com> > > wrote: > > > On Wed, Jan 27, 2010 at 8:07 PM, Mike <eris...@gmail.com> wrote: > > >> Very nice ! > > > >> Thank you for sharing your vision of the future :D > > > > ditto > > > >> How will this effect current plugins? > > >> (I did see the tiddler upgrade, I am assuming this would be for data) > > > > I'm assuming there's no easy way to upgrade plugins, and this will > > > make a lot of them feel hacky and passe anyway. > > > > I'm happy with this direction given the jQuery / HTML centricity will > > > vastly simplify authoring new plugins - the core code looks far more > > > grokable than the current core. > > > >> I like the two column display, the lean layout > > > > I gather this is demonstrating multiple stories, which will make > > > building verticals much more interesting. > > > >> and the search bar > > >> static on the bottom of the browser. > > > > I like my search bar at the top of the page, but can see that's all > > > tunable. > > > > -- > > > Paul (psd) > > >http://blog.whatfettle.com > > > > -- > > > You received this message because you are subscribed to the Google Groups > > > "TiddlyWikiDev" group. > > > To post to this group, send email to tiddlywiki...@googlegroups.com. > > > To unsubscribe from this group, send email to > > > tiddlywikidev+unsubscr...@googlegroups.com. > > > For more options, visit this group > > > athttp://groups.google.com/group/tiddlywikidev?hl=en. > > > -- > > Jeremy Ruston > > mailto:jer...@osmosoft.comhttp://www.tiddlywiki.com -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To post to this group, send email to tiddlywiki...@googlegroups.com. To unsubscribe from this group, send email to tiddlywikidev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywikidev?hl=en.
