Okay, now we have an edit area.
What should it be editing?
It should edit a temporary tiddler:
$:/temp/NewTiddlerText
Please tell me that you’re saving snapshots as you go. I’m interested to see this progress.
1 Like
Nah, I’m not taking any milestone snapshots. I’ll leave that to anybody interested in keeping a little album of daily-ish progress/regress as we prototype the daylights out of pure TiddlyWiki/CSS/HTML and no touching the core.
We’ll see how far we can push this. Maybe even have multiple bare-bones UI options…
1 Like
Okay, the EditTextWidget is associated with a temporary tiddler.
What next?
The edit area needs a functioning SAVE button that saves the text content to a tiddler.
I’m going to setup as “Save As” button, so that you can give the tiddler a title.
Just to see.
Sounds perfect. I was going to suggest something like that, but I think you would like the suggestions as simple as possible, no?
Yup. Simple, and keeping anything “make pretty” for the end.
This is all about identifying the pieces, getting that inventory together, and getting the pieces working even if a little bit rough around the edges.
1 Like
Okay, we now have a button to create a new tiddler with the text entered in the input text field.
I’m done working on this for today.
However, for when I get back to it sometime in the next few days: what’s next?
Now we can make tiddlers but can’t see them, so how about a list of tiddlers that have been made?
I was going to say that! Yes. So be able to see existing titles and edit them?
Reduce reuse recycle?
I scammed some bits and pieces from BASIC Anywhere Machine.
Before doing anything else, I need to know: how does what we have so far work on mobile devices?
I only operate with my 17" Chromebook and a secondary 27" display. (Small display devices and I don’t particularly get along.)
Works well. I can type away, save and title my tiddler and then download the wiki quite happily all on my phone.
Hey, thanks for checking and reporting !
Now, is there anything done so far that isn’t quite in the spirit of “bare-bones” ? (We are kind of scoping out what bare-bones means as we prototype away.)
Something we can easily do is have multiple “bare-bones options”, too. Imagine levels 1 to whatever, 1 being the most minimal, and whatever being the most feature-full (and maybe busy just before getting to the point of simply going to the au-natural TiddlyWiki interface.
So at some point, we may want to say that we’ve reached the minimal interface (level 1), and the next thing we add has crossed the threshold to level 2.
As always, “make pretty” for way later.
What’s next, and is the next thing still “level 1” ?
Just a thought: maybe the next thing is a minimal “settings and configuration” dialog?
Like tiddlywiki title, editor font-size …
this looks (on initial scan) amazing !
(less is more)
oh!
…still playing ? 
i have some currently-prototypeing ui-thunks
initially
potentially this is an ideal start point for well
a whaleload of whatsits
i guess “hyper-shells”
im thunking along the lines of cli-like ftr
.Readline ( have you heard of/used it? ) - #4 by wiki_user
So many shiny objects competing for my attention, so few hours in a day …
I stopped playing when I wound up playing by myself.
Now, I’m consumed by projects I find immeasurably more interesting and purposeful.
1 Like
-
This is exactly what I’ve been looking for. I’ve been trying to find a way to hide all interfaces. My previous attempt to modify the tour plugin failed.
-
Currently, the feature to change tiddler titles is still missing.
-
No need for cumulative functionality. Next, everyone should build their own customized versions based on their requirements.
-
The feature I envision is a dual-pane layout with left and right columns for editing and previewing Markdown documents.
With in the editor, of course there is already the preview > output option that does this. Just making sure you have not missed that. There are also multi-story plugins as well.