Riz, Totally agree, I suppose I need to take the next step for playground and standard editions despite it being raised an number of times.
However If there is no download without selecting an option, how will it look to a new user?. To me it is a big thing to hide something so essential that was not before. Regards Tony On Wednesday, June 24, 2020 at 3:14:10 PM UTC+10, Riz wrote: > > > Single file HTML button should be at the top > > Noted. Will change. I am not up for keeping it open. The wizard is in > place specifically for those people who need help. People should make > informed decisions. Might be worthwhile to add download button to wizard > intro though. I would take suggestions on how the text should be. > > Regarding standard edition I agree with the necessity of such an edition. > However these require a entirely different and thorough discussion. What is > a standard edition?. What plugins goes into a standard edition? How are > users guided through the usage of a standard edition? Is there gonna be a > wizard inside standard edition that will tell user what to do step by step? > > When a standard edition is formed and available under tiddlywiki.com > domain, the GettingStarted Tiddler will be definitely revised to link to it > in appropriate places. It doesn't exist currently unfortunately. > > Similar is the case with playground edition. There should exist one in the > repo and under tiddlywiki.com domain. When they do, it will be linked. > > Sincerely, > Riz > > On Wed, 24 Jun 2020, 10:28 TW Tones, <anthon...@gmail.com <javascript:>> > wrote: > >> Riz, >> >> Thanks for your work here >> >> Some Quick points >> >> - Single file HTML button should be at the top, and possibly open to >> start with. This is where new users will be, lets not force a choice when >> they still do not know how to answer. >> - Personally I think at least download empty should always be visible >> above the choices as it will always be valid. >> However as argued elsewhere it would be better to use a Standard wiki >> with a little more than empty eg a few inclusions like contents, display >> the more page control, home close all and a little more. >> - I also believe once established a learn tiddlywiki and playground >> editions be pointed to here. If people can experience it without >> download/save of any other decisions I expect out adoption or conversion >> rate to go up. >> >> Regards >> TW Tones >> >> On Wednesday, June 24, 2020 at 2:40:44 PM UTC+10, Riz wrote: >>> >>> Hi, >>> >>> So I have uploaded the current draft of changes here: >>> https://ibnishak.github.io/TiddlyWiki5/ >>> >>> Apart from changed suggested by Eric, the text is practically same. Some >>> other major changes >>> >>> 1. The filters in Saver methods are done away with. As pointed out >>> above, most options appear whatever options you choose. Wherever options >>> are platform bound, it is mentioned clearly in the description. Otherwise >>> it is subdivided to meaningful categories keeping in mind "What average >>> users might want to see first". >>> 2. Text in "Installing Tiddlywiki with Node.JS" is slightly modified. >>> 3. Advice boxes CSS is updated. >>> 4. Wizard as discussed above. >>> >>> I have not updated individual savers. I have my doubts regarding a few - >>> HTA hack, Beaker, PHP saver. A few users in Reddit had complaints regarding >>> instructions about Noteself being outdated. Someone more knowledgeable >>> might want to look into these. Actual users of individual saver methods >>> could eventually update the docs with detailed instructions to set up >>> individual savers. >>> >>> Apart from general comments, I need specific feedback regarding the >>> following. >>> >>> 1. In the wizard intro, there need be a comment mentioning that only one >>> saver would work at a time. If you use GitHub saver, the local copy will >>> not be updated. This seems to be a frequent source of confusion. >>> 2. Right now in wizard the "Next" button appear only when next step >>> matters - like when user selects No or when there is a subquestion - like >>> which cloud service to use. Another option would be keeping the next button >>> appear always and urging user to click it on choosing an option. It might >>> involve animation- so could be costly wrt performance. >>> 3. How about changing all advice boxes (Tips, Warning, Preamble) in the >>> doc to the CSS given in the demo? Right now I have kept it limited to the >>> tiddlers I modified in this demo. >>> >>> Sincerely, >>> Riz >>> >>> -- >> 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/MpxrDwmt0S8/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> tiddl...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/tiddlywiki/a3ddae07-ec34-46d4-b823-95d83f6a3669o%40googlegroups.com >> >> <https://groups.google.com/d/msgid/tiddlywiki/a3ddae07-ec34-46d4-b823-95d83f6a3669o%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 tiddlywiki+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/42f69c00-b632-404f-b35b-2d09c41f87ddo%40googlegroups.com.
