I just found a better reference (i.e. in-browser simple text 
editor):  https://browserpad.org/

That one knows filename when opening a file, and remembers that filename on 
"save" ("save/export", in my mind.)

If that thing had TW formatting buttons and a preview pane, it would be 
exactly what I'm looking for. (Well, I wouldn't want the spell-checking 
check box, nor that github button in the bottom-right.) 



On Saturday, August 7, 2021 at 1:41:35 PM UTC-3 Charlie Veniot wrote:

> In regards to open and save *(just for 
> reference:  https://www.outpan.com/app/e7d5b37405/mytextarea 
> <https://www.outpan.com/app/e7d5b37405/mytextarea>)* ...
>
> I'm thinking an open button like the one in that editor, and an 
> export/save button that works exactly like the tiddler export button in 
> TiddlyWiki, with just the TID option or with more/all options.
>
> So no save mechanisms.  Just enter WikiText-à-la-TiddlyWiki, preview, and 
> click export as TID.
>
>
> Whenever I just want to take down a quick note, TiddlyWiki is rarely my 
> first choice.  Using my Chromebook, I typically go to Gmail or Google Keep, 
> or even Google Calendar, first.
>
> Having a small HTML page, i.e. TidEdit app, available to me, I could see 
> myself going there first when I want to take down a note that is slightly 
> more substantial organization-wise, but not so substantial that I want to 
> open a TiddlyWiki (which I keep on Google Drive, using the TiddlyDrive 
> add-on app.)  So a bit like a simple text editor, but a little bit 
> StackEdit-like, with a way to get the content into a TID.
>
> With something like that, I might actually use my small+old smartphone for 
> more than just phone and text-messaging...
>
> On Saturday, August 7, 2021 at 1:01:22 PM UTC-3 Charlie Veniot wrote:
>
>> Define backward.
>>
>> To me, it is like the difference between a small text editor and a word 
>> processor.  Using a text editor for certain things, instead of a full Word 
>> Processor isn't going backwards.  It is just using the simplest tool that 
>> makes sense for an immediate need.
>>
>> Same thing for "TidEdit".  It is just about reaching for the simplest and 
>> quickest tool for an immediate need (just jot down a note) , yet having 
>> that WikiText available (and preview) for quick visual organization of that 
>> one note, however short/long, for later serious processing.
>>
>> In a way, it boils down to that difference (in my mind, anyway) between 
>> note-taking and note-making.
>>
>> I imagine TidEdit as something complimentary to TiddlyWiki, a really nice 
>> addition to a TiddlyWiki ecosystem of tools/components/workflow-enablers.
>>
>> A simple HTML page with a text area on the left, preview pane on the 
>> right, and buttons for WikiText markup, and buttons for "new", "open", and 
>> "save", always working with TID files for each drag and drop into a 
>> TiddlyWiki.
>>
>> Why would any "save" plugins be required?  "Save" would be like 
>> "download", and open would be like "upload".  Aren't those just basic 
>> javascript functions?
>>
>> I suppose it isn't really about stripping down TiddlyWiki.  It is about 
>> creating a single HTML file that provides something that is StackEdit-ish 
>> (no "notebook" and no multiple notes handling), with buttons that work like 
>> the tiddler edit buttons for WikiText formatting, and those "new" (clear 
>> text area and preview), "open" (pick a file and put the content of that 
>> file in the text area), "save" (i.e. just download a file that has the 
>> content from the textarea) buttons.
>>
>>
>> On Sat, Aug 7, 2021 at 12:41 PM PMario <[email protected]> wrote:
>>
>>> On Saturday, August 7, 2021 at 4:19:52 PM UTC+2 [email protected] wrote:
>>>
>>> i.e. just what is needed to create/edit/save WikiText (à la TiddlyWiki) 
>>>> to a TID file.  Nothing else.
>>>>
>>>
>>> TLDR;
>>>
>>> You are right, we may be able to strip about half of the *UI* size, but 
>>> this would mean we will go backwards. ... 
>>>
>>> --------------
>>>
>>> As you probably know, browsers will only let you save to the Downloads 
>>> directory and subdirectories with default browser plugins. 
>>> With Timimi you can choose the directory, but you will need 2 
>>> components. A browser AddOn and an executable.
>>>
>>> There is a new file-API for chromium based browsers, but they will also 
>>> need a server somewhere in the background to use the functionality in a 
>>> "secure" way. ... 
>>>  
>>>
>>>> No refresh mechanism going on, no loading up a whole TiddlyWiki (with 
>>>> all the tiddlers and plugins), blazingly fast open of a small HTML file to 
>>>> quickly enter some info/knowledge/content on the fly with whatever 
>>>> device, with ability to save that tiddler, parking its the TID file 
>>>> somewhere for later processing in the full TiddlyWiki.
>>>>
>>>
>>> In your first post you mentioned, that you don't need all toolbar 
>>> buttons but some of them. ... So if you only want 1 of them, the software 
>>> needed is the same as showing all of them. ... The mechanism to show 1 
>>> button is the same as to show many of them. It's only a different filter 
>>> and a list. 
>>>
>>> The same is true for the TW UI. It will be possible to create new 
>>> ...Templates, that are different to the existing ones, but the 
>>> functionality to handle Page-, Edit- and View templates is the same as with 
>>> a default TW. So I'm sure you don't safe anything in the core. 
>>>  
>>>
>>>> Sure I can tweak a TiddlyWiki by adding custom Tiddlers, but I'm 
>>>> talking about a major strip down to have a simple editor for simple 
>>>> note-taking.
>>>>
>>>
>>> As I wrote. There will be no major strip down in wiki size. The startup 
>>> may be faster, because less DOM elements are created. ... Especially no 
>>> sidebar. 
>>>
>>> At the moment there are 8 tiddlers tagged: $:/tags/PageTemplate ... 11 
>>> tiddlers tagged: $:/tags/ViewTemplate ... 9 tiddlers tagged: 
>>> $:/tags/EditTemplate ... 7 tiddlers tagged: $:/tags/SideBar ... and about 
>>> 33 toolbar buttons. 
>>>
>>> So you may safe some of them but that's basically it. TW consists of 
>>> about 2100 shadow tiddlers in empty.html.  Nobody knows, how they are 
>>> exactly interconnected. It would be possible to find it out, but that would 
>>> be a lot of work I wouldn't want to do. 
>>>
>>> TiddlyWiki 5.1.0 had 991 shadow tiddlers and about 1.1MByte in size. 
>>> About 460 shadows are $:/language tiddlers ... 
>>>
>>> In 6 years users requested new UI functionality, which resulted in about 
>>> 1000 shadow tiddlers more and about 1MByte more size of the file. The 
>>> system did grow organically, with a lot of interconnections here and there. 
>>>
>>> You are right, we may be able to strip about half of the *UI* size, but 
>>> IMO this would mean we will go backwards. ...
>>>
>>> just some thoughts
>>> mario
>>>
>>> -- 
>>> You received this message because you are subscribed to a topic in the 
>>> Google Groups "TiddlyWiki" group.
>>> To unsubscribe from this topic, visit 
>>> https://groups.google.com/d/topic/tiddlywiki/JuhpaVK_zts/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to 
>>> [email protected].
>>>
>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/tiddlywiki/35a5a231-04d0-4fd7-b6b4-9bbb97ac92cdn%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/tiddlywiki/35a5a231-04d0-4fd7-b6b4-9bbb97ac92cdn%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/ce746a1a-b221-4a00-8d8a-4b196f1f4a54n%40googlegroups.com.

Reply via email to