@Mat: oh no The idea of a community repo is to ensure a parallel system of testing visual changes, documentation and other feature sets without bothering Jeremy for every silly thing. Pushing the important changes to core while keeping the rest in a community repo mirroring main repo, will keep the main repo clean.
I have not done this for two reasons 1. Such a community repo should be owned by members much senior to me. Somebody who has intimate knowledge of wikitext and JavaScript. A organisational Repo can have more than one owner - So may be 3 owners. 2. Even such a move should have Jeremy's go ahead. Because unlike individual plugin repos, organisational repos based on TW5 is a more serious affair. If such an community repo becomes real, there can be teams under that with jobs assigned to review new documentation and may be even a curated plugin list. I would my time and knowledge in whatever way I can to such an endeavour, but not initiative. I have learned well from Reddit experience :) Sincerely, Riz On Thu, 21 May 2020, 16:43 Mat, <[email protected]> wrote: > Edgaras wrote: >> >> - Arrows are for navigating back and forward, which tiddler you visited >> the latest (clicking on links). I updated arrows to look less like >> redo/undo. >> > > That indicates your vision is a single tiddler view mode - ? I would > definitely not like this for default TW because it makes open data much > more difficult to access. > > > >> - Icons and background I need to test. I was not fan of the original >> icons, but maybe that's bias, I will try them on the new layout. >> > > I believe, the icons are custom made by Jeremy. I personally like them but > a big disadvantage is that one cannot easily find new icons with a similar > style. The optimal would either be if we had a custom made, very rich set ( > ref <https://github.com/Jermolene/TiddlyWiki5/issues/3388>) or, more > easily, just use some rich open source alternative. > > > >> - I think we need some general consideration around system tiddlers. I >> think there could be a way to seperate content and system tiddlers. I've >> seen some interesting theme, where tiddlers were in the sidebar, I think >> some system tiddlers could be pinned to the sidebar, so they are always at >> reach. >> > > I'm not sure what you mean here with system tiddlers. System tiddlers are > (simply!) tiddlers that have the prefix $:/ and this hides them from > showing up in most lists. In my post to which you reply, I bring up system > fields, i.e the few "reserved words/names" that are used for data fields in > the system. > > > >> - Even if TW is for personal use, it does not have to be messy... Many >> people want to have a distraction free writing and thinking experience. >> That's the key for me. The "prettiness" come from practicality, hiding >> things that you don't use too often. It's a balance yet to be found, >> through iterations we will find way to prioritise more used items and make >> them more visible. >> > > We need to consider both "writing" and "using".... actually, for writing, > we should perhaps even differentiate between typing text (e.g a markup'ed > poem) and more complex "WikiTexting" where you need access to tools and you > need to look up titles for other tiddlers, etc. The former, i.e the typing > of simple text would benefit from distraction free (I like the OMM > interface <https://www.youtube.com/watch?v=n0rI9Is4z1Y>, old video I know > but those click sounds and the music... aaaah) - but WikiTexting probably > can't be quite that. > > > Again, it helps to be more specific – here I agree with you, sidebar >> should be more prominent, probably open by the default. I will work on >> sidebar. >> > > One could imagine a toggle up in corner for e.g "distraction free light > markup", "full WikiTexting with direct tool access", "full on display of > all features" > > > - Yes, toolbar needs to be re-introduced, I forgot in this iteration. My >> take on toolbar is like this: >> a. It should be possible to hide toolbar by default. (Maybe >> already is, but I want that on the spot) >> > > I like "hover to show" but I know Jeremy is not fond of this because he > thinks it is problematic on touch screens... yet, it is commonly used on > touch screens where, if I recall, it instead is "touch to show". > > > >> b. Balloon popup toolbox is super good idea. I would use that a >> lot when toolbar is hidden (also should be possible to customize on the >> spot, maybe small link icon that leads to settings.) >> > > Yeah, I find that controls should be as close to *here *as possible AND > also collected in a central place. TW and transclusion is perfect for this; > dispersed doses of local control for the context AN D a central > Controlplanel aggregating them all. > > > Referring back to @Riz point; maybe this discussion should be moved into a > Github repo (you created one, right @Riz?). The thread is split up here so > it is difficult to navigate to what is mentioned. > > <:-) > > <:-) > > -- > 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/gX0o8j7Coa8/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/77ef6bc2-a7fc-4fa7-adef-1f19fb3557b0%40googlegroups.com > <https://groups.google.com/d/msgid/tiddlywiki/77ef6bc2-a7fc-4fa7-adef-1f19fb3557b0%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/CAO0b0pGNNYTbo-PG_sK3-yrigZEv2FLY%2BD%2B4eMvbwee%3D8tSN-w%40mail.gmail.com.
