> Inherent contradiction there. TW's current (soon to be called "legacy" I > guess) implementation's storage model doesn't fit with modern browsers' > tighter security.
true... which is why I'm hoping that sometime soon, we have a platform independent desktop web-app engine... which I hope is firefox or chrome based, given their ubiquity. > The FOSS project upstream of Chrome has a Prism analog in the works, but I > imagine it will only work well with the future TW "NG". I'm having some initial success with the current xulrunner (10.0), the included "first_browser" sample, and running the current release of TW, even saving without requiring the java applet. If I can just manage to tweak it so that links launch using the default browser, instead of internally, I'll be happy with it... and will gladly put it on github or the like. > I have some legacy apps with very important data I haven't got around to > converting that I run in a VM when needed - a pain to get set up, but now > it's just like launching "just another app" - not much bigger or slower > than launching something like Photoshop (or a fully loaded FF 8-) either. Heh... thankfully, with TW, I didn't have to resort to such tactics... I just use the latest firefox... not my personal ideal, but perfectly usable. I hope I don't ever run into anything for personal use that requires me to run a Linux VM, for those reasons at least. I already run one for XP, for those times when it's impossible to do something in FF/Chrome under Linux. I manage systems for a living, which I really enjoy... but I'd rather not spend any more time off-hours than I have to, maintaining yet another. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
