Re: [twdev] @dev - Why dev for Chrome is a MUST

Ciao Arlen I understand what you are saying but node.js is a SPECIALIST thing. Lets not lose ordinary users. Jeremy is modest often in his future perceptions, thinking something like the "TW Popular" may have to be be an online service eventually (note: wholly my interpretation, NOT his words)

Re: [twdev] @dev - Why dev for Chrome is a MUST

It can be a bit disconcerting at times, that's for sure. But I have to say that I think NodeJS is probably​ going to give us a good platform to replace what we've been using up to now. On Jun 1, 2017 05:56, "Jeremy Ruston" wrote: Hi Arlen Thanks for the clarification. It’s a shame that Google

Re: [twdev] @dev - Why dev for Chrome is a MUST

Hi Arlen Thanks for the clarification. It’s a shame that Google have killed Chrome Applications; they had some neat capabilities. But it’s also a reminder that Google’s habit of discontinuing technologies and platforms is pretty dispiriting from a developers perspective… Best wishes Jeremy >

Re: [twdev] @dev - Why dev for Chrome is a MUST

Good overview Jeremy. Just thought I'd mention that TiddlyChrome is a Chrome App, rather than an extension, and as such is given the privilege of editting such files as the user specifically chooses using an open file dialog. Because apps are going to be removed from Chrome within a year or so, I

Re: [twdev] @dev - Why dev for Chrome is a MUST

Some of your thoughts should get pinned. My issue with this is not on saving per se, its on what is a TW "standalone". Daniello's NoteSelf seems to instance a very interesting mid-place of easy saving and conventional TW authorial autonomy that makes this more rich, and interestingly, complex.

Re: [twdev] @dev - Why dev for Chrome is a MUST

> > I DO think that Chrome saving, IF it could be got to work as elegantly as > TiddlyFox currently does, could help TiddlyWiki get more widely used. There > has been much discussion about this. Not being a developer I don't really > understand the issues on how DIFFICULT overwrite saving has b

[twdev] @dev - Why dev for Chrome is a MUST

For anyone developing plugins or public TW stuff, I just wanted to clarify a general premise - in case you didn't know already: Assuming the intention is for people to *use* the plugin, it *has *to be developed with Chrome in mind: Visitors to w3schools 201