Hello Edgar,Welcome to the community and great to know yoy are willing to create a new theme!
I may suggest to have a look atThis is one of the best collection of Tiddlywiki resources on the net.
Using good UI (theme) it can plant many roles like blog, notebook, website, database, image gallery, CMS and like that...
it really doesn't matter if something is accepted by Jeremy or any of the devs, you can make it anyway.
This is one of the best collection of Tiddlywiki resources on the net.
- TiddlyWiki can already do or be many things
- This presents a dilemma, because how do you set a basic standard look for a chameleon?
- TiddlyWiki is the answer to so many questions, but which question are you trying to answer?
- There are already innovative tiddlywiki layouts like a trello look alike, the Murri plugin and much more
I have a vision for such a solution I would be happy to share if you want to consider taking it on.
One way I would like to see the recent discussions evolve is a bit like how developers may use wordpress as the back end and write their own front end.
When it comes to static site generation, there are great mechanisms in tiddlywiki to do this already as no doubt people see, but to make it really powerful we need to improve and support the workflow and templates used to do this.
Tiddlywiki as a platform, Software Development Kit, Personal Productivity tool, site generator, database.... interface design ... is almost infinite.
I would like to see a responsive theme that contains elements that come into use only if given content and obeys a set of rules that allows almost any design structure, with default that result in what we currently see, but a small set of changes transforms it.
You are welcome to comment on top of prototype! And ask me if you want to edit!
Moving forward I see two main issues that prevents simplicity:
- The navigation when clicking links. Do you find it useful that tiddles are opening as a vertical stack? I find it kind of confusing, and not really helpful when you have increasingly large stack. I would like to explore alternative interactions:
- Swapping the tiddle with a new one, but keeping the breadcrumbs on top (if possible?)
- and giving < and > navigation, back and forward in time where you've been.
- Stacking tiddle when opening into tabs, so you can switch then by clicking or keyboard shortcut.
- Editing mode. How can we make the editing more fluent with viewing. It distances you from just writing if you have to click edit and save everytime. You should be able to navigate text with keyboard or just click anywhere in text right away and start editing. Saving should happen automatically (to local storage). All the text-type formatting could be hidden, unless it's relevant for the selected word or sentence. This will reduce visual clutter. Check the simplicity of text editing in Typora! → Quick demo
Maybe a sticky toolbar for the various parts of the edittemplate. Click to open fields, click to open types, click to open preview, click to have editor toolbar buttons visible, etc
I actually did this part a number of years ago.
Maybe a sticky toolbar for the various parts of the edittemplate
- The navigation when clicking links. Do you find it useful that tiddles are opening as a vertical stack? I find it kind of confusing, and not really helpful when you have increasingly large stack. I would like to explore alternative interactions:
- Swapping the tiddle with a new one, but keeping the breadcrumbs on top (if possible?) and giving < and > navigation, back and forward in time where you've been.
- Stacking tiddle when opening into tabs, so you can switch then by clicking or keyboard shortcut.
- Editing mode. How can we make the editing more fluent with viewing. It distances you from just writing if you have to click edit and save everytime. You should be able to navigate text with keyboard or just click anywhere in text right away and start editing. Saving should happen automatically (to local storage). All the text-type formatting could be hidden, unless it's relevant for the selected word or sentence. This will reduce visual clutter. Check the simplicity of text editing in Typora!
all of the functionality available in the default theme
need for backwards compatibility
Zoomin displays a single tiddler at a time with a transition animation as links are clicked
The difference between editing and view mode is hard to hide away.
It’s based on Quill.js which seems to be popular but I find it very clunky to use, particularly making links.
You are not the first to mention that saving should happen automatically to local storage.
I don’t think there’s a whole lot of low hanging fruit without significant development within the core.
IMO we can do everything. ... Installing those 3 themes in ONE wiki and make them switchable will be a challenge. ... But doable, if it needs to be ...
@Jeremy: this was such an interesting read, thank you!Just want to jot down some thoughts:
- It's the fist time I see the introduction walkthrough, this is going to become my go-to when telling people about TiddlyWiki!
- Tangential - I was about to share the link on Twitter, but checked here first and it looks like there's no link preview. It would be good in a future version to have default link preview parameters so links always look good on social media. Even better if the user can tweak them easily.
- If there are so many limitations in working with the full version of TiddlyWiki, I wonder if Edgaras couldn't design a version that's purposefully restrictive. For instance, we're not able to edit on click because we're not sure what complex transclusion may be computed in the background—maybe that super simple Starter Edition of TiddlyWiki would not support such complex transclusions and focus on pure note-taking? May not be possible at all but just throwing it out there.
- Also, side note that I personally never use Storyview, and what Dave Gifford is creating to look at two tiddlers side-by-side feels much more natural to me, but again may be too much of a departure from the way TiddlyWiki works.
@Edgaras: I don't think the WYSIWYG part is that important to be honest. The kind of users that will be early adopters of this Starter Edition will probably understand markdown fairly quickly, especially if the onboarding is done correctly. (tens of thousands of non-technical people did with Roam)I think what would be interesting from a design standpoint is figure out everything that should be removed for a Starter Edition, so people can get the best first impression, and then build upon this as they grow along their TiddlyWiki. Very excited to follow the progress on this!
On Saturday, April 25, 2020 at 4:06:09 PM UTC+1, PMario wrote:Hi Edgaras,Welcome to the club!It's nice to see a designer's point of view! I think your designs should be like brainstorming about UI and UX improvements. It's cool to explore new possibilities without thinking about the consequences ;)We developers and power-users should not think about, how of if we can implement "those visions". We shouldn't think about "design" backwards compatibility. The internals need to be compatible. They are ultra flexible already ... We will survive it!I think it's about the "First Impression" for new users. Newbies want to type formatted text. ... Have a TOC ... Create simple ToDo's / shopping / <you name it> lists. ... They seem to like "backlinking" more visible ;) ...I think, if those elements can be made simple and they have the possibility to "store", "reload" and make their stuff visible for others, they are "caught" already.If the second step like dynamic lists need an "extended editor" and transclusions, macros, widgets need an "advanced" editor this doesn't matter anymore. We got them already.-------------Themes can look like:- Hugo static site theme Ghostwriter or- Wordpress Moments or more TW like- Whitespace which IMO has a very nice sidebar concept.IMO we can do everything. ... Installing those 3 themes in ONE wiki and make them switchable will be a challenge. ... But doable, if it needs to be ...There is one more thing, I wanted to show, but it doesn't work atm ;) ... Link will follow.have fun!mario
--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+...@googlegroups.com.To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/8500c4e2-d7bf-4dbb-8de1-89ebf95a117d%40googlegroups.com.
- It's the fist time I see the introduction walkthrough, this is going to become my go-to when telling people about TiddlyWiki
@Mohammad: these look amazing! We need to have a proper gallery of themes in the new tiddlywiki.com - it will really help to get people excited.And talky talky looks amazing, but already a bit more technical :)
Plain editing, markup → Select word/sentence/paragraph to call a small toolkit pop-up → Toggle the toolbar → Reveal more advanced toolbar.
Here is a short screen recording of the prototype:
I've been prototyping a little bit further last weekend. I took in consideration many things we've discussed above. The prototype is far from final, but I hope it gives the idea of the minimalist vision.Here is a short screen recording of the prototype:
- Removed the box/frame and left text only to focus on writing experience.
- You can start writing just by clicking on text or TAB on keyboard
- Meta info like "fields" and "content type" is hidden one click away for simplicity.
- Simplier tag management.
- Added "mentions" for backlinks!
- Added a star icon for pinning/adding a tiddler to favorites.
- Added breadcrumb navigation on top
- Simplified sidebar with 4 tabs: opened tiddlers, pinned, recent and all.
- Clicking on a link, you navigate to another note, but you can still access all opened notes in sidebar until you close them all.
David Gifford Thank you! I was actually thinking something very similar! See the image attached. I tried it on the side stacking vertically, but the problem was titles are too long.So I gave 2 letter initials for each note. I think I should try like you suggest putting notes on top.By the way from your experience how many actual notes do you have open and it's still useful at a given time?–––––Mat, Mohammad woups, made the video file public now!
–––––Mohammad clicking on the "Mentions" (backlinks) will give you a dropdown searchable menu, similar to other dropdown menus like for tags that TiddlyWiki already has.Yes, links and images are very important to markup. Links with [[ ]] convention and images with markdown style to start with (![Kitten](/media/2018/08/kitten.jpg "A cute kitten")
Editor bar is the next thing to work on, but we need to consider minimalist. We could have just typing and markdown to start with (and give a quick popup for cheatsheets).Or we could make so the toolbar is very minimal, you open it by selecting/highlighting a word/sentence.
Yes, mobile design is the very next thing to address next too! Thanks!
Could you give a bit more detail to the comment about "loose arrangement"? Are you refering to the notes not having a box? This one I am inspiring again from simple editors like Typora, Notion, Roam. It gives the feeling of freedom and minimalism. It might be a bit hard to get the feeling now only from image prototype. It could feel different when it's real.
I really like how in Notion you start with the blank slate (see the screenshot attached)
You are already mentioning bunch of great points:
- TiddlyWiki can already do or be many things
- This presents a dilemma, because how do you set a basic standard look for a chameleon?
This is why I am so excited about, it's super powerful, but somehow it seems a bit overwhelming, with all the features shouting for the importance. The tool could be as blank as it can be, while displaying first possible actions, and then introducing complexity as you engage within a context.
- TiddlyWiki is the answer to so many questions, but which question are you trying to answer?
- There are already innovative tiddlywiki layouts like a trello look alike, the Murri plugin and much more
As I see it, TW should be as it is – super powerful personal notebook, with a possibility to quickly and simply publish static website, as if possible (don't know much about it) a collaborative writing tool. Some of the things that I see are missing:
I've seen some of TW themes, but it feels more like as a surface redesign, but underlying issues are there. Yes, some corrections on usability and some nice features like sidebar are there, but many things like fonts, icons, animations, white space feels odd, as most importantly, not much is improved in the usability of editing. Also, obviously I haven't seen enough! Please share if something minimal exist already.I have a vision for such a solution I would be happy to share if you want to consider taking it on.I would love to hear your vision if you are willing to share! Both on the strategy and design, let's collaborate. We can discuss here + draft a more structured google docs + prioritize tasks on Trello + share the actual design vision and comment on Figma prototype.
One way I would like to see the recent discussions evolve is a bit like how developers may use wordpress as the back end and write their own front end.Could you explain a bit more what do you mean here?
When it comes to static site generation, there are great mechanisms in tiddlywiki to do this already as no doubt people see, but to make it really powerful we need to improve and support the workflow and templates used to do this.I really want to dig deeper into the current state of art of TW's static site generation. It must be as simple as in any other SSG, but even simplier! I like what Publii is doing. You just write you site visually and then publish to GitHub Pages or SFTP as a static site with one click (+ first time simple settup).
Tiddlywiki as a platform, Software Development Kit, Personal Productivity tool, site generator, database.... interface design ... is almost infinite.
I would like to see a responsive theme that contains elements that come into use only if given content and obeys a set of rules that allows almost any design structure, with default that result in what we currently see, but a small set of changes transforms it.That's how I see it too! Simple, responsive, contextual, prioritised. There should no unnecessary switching "modes", viewing and editing should feel as one coherent flow. And all the power of the tool can come into the right place, but it should to be prioritised.
Thank you for in the depth feedback peeps! This really helps to consider more aspects and improve the design.––––––––––
For default it is not a good idea because the user needs to understand the concept of tiddlers and the framing helps with this conceptualization.
Mat is see what you mean now! I agree with you and maybe even in this theme, tiddlers should stay modular, and have the story view, it has many advantages! There are few things that bothers me in the story view and I want to address those. For example, I loose track of navigation when I jump from one to another tiddler. Maybe I need arrows < > so I can quickly navigate from where I've been before and combine with breadcrumbs. I already have that in the prototype and I can try to prototype
--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+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/f3812ef8-f439-4ec1-93a6-4f90612c95b6%40googlegroups.com.
Regarding the navigation, I installed Ton Gerner's tiddlerbar plug-in because of the same problem you describe. I find the tiddlerbar solved it. When you have many tids open the bar just overflows into an extra line of tabs.29 Apr 2020, 10:29 by edgar...@gmail.com:
Thank you for in the depth feedback peeps! This really helps to consider more aspects and improve the design.––––––––––For default it is not a good idea because the user needs to understand the concept of tiddlers and the framing helps with this conceptualization.Mat is see what you mean now! I agree with you and maybe even in this theme, tiddlers should stay modular, and have the story view, it has many advantages! There are few things that bothers me in the story view and I want to address those. For example, I loose track of navigation when I jump from one to another tiddler. Maybe I need arrows < > so I can quickly navigate from where I've been before and combine with breadcrumbs. I already have that in the prototype and I can try to prototype
--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 tiddl...@googlegroups.com.
For default it is not a good idea because the user needs to understand the concept of tiddlers and the framing helps with this conceptualization.
But... which mode is it we see in the demo/recording? Edit or View mode? How do I switch between these modes?
It is very elegant but in what way is it simpler?
(This is not seen in the demo, right?)
(Not seen in demo, right?)
I'm not sure about putting tab All there instead of More. How do you access the other subtabs of More?
Like normal/current TW, right?
Wonderful! I may prefer wikitext instead of markdown :-)
Hit the return key and get a new block, by default a paragraph, but that can be changed by hitting a shortcut or pressing a button to change the block type.
This is to show how you may not yet have imagined TiddlyWiki yet.
Another key wiki rins on Windows TiddlyDesktop and it interacts with my computer, folders, files links and supports automation, network troubleshooting and more.
this is not at all to diminish your approach, but perhaps even to broaden the possibilities further.
You give me a link or start a thread here or in my personal group
I am not suggesting something so extreme, I am suggesting with different themes and page structure tiddlywiki can and does do the same
The thing is a good design on top of tiddlywiki will benefit from the many advantages within tiddlywiki.
I agree, many need what you say here, but I do want to be able to switch modes
Yay for proper markdown integration out of the box!
Maybe move the mentions at the bottom of the writing or somewhere else? I think the dropdown menu at the top may make them feel like a second thought.
settings
I am so glad you are inspired. Your contribution will be appreciated. I think We are in furious agreement and share your visions.
Many of your ideas have had some consideration over recent years here and its good to see that you have insight into these issues even although you are new to tiddlywiki. The truth is tiddlywiki as at the leading edge of personal software in my view, if not yet as accessible to the general public as we wish. Tiddlywiki also has a history of absorbing and reinventing meaningful advances.
Many of us are skilled in diverse areas and expect very different things. From academics and authors to hackers and to Do list users.
Jeremy is the creator and has maintained some strict principals that have got us so far with each advance expanding possibilities exponentially. There are conceptual leaps needed for many to come to terms with tiddlywiki, but someone with your broad insight will find much can be plugged in to the platform. In some ways it is self documented, an important principal, but this sometimes, results less general (although not dummed down) documentation.
the best way is to learn its mechanisiums and build a plugin or edition that demonstrates new solutions. If there is a gap that can be addressed in the core tell us about it, but more often than not someone will have a method or a workaround.
It has being a long standing tradition to encourage people to search for solutions already there, but we ask do not hesitate to ask questions. I am often delighted at the number of different and elegant solutions that come forward.
This is my experienced viewpoint but others may have quite different view points.
I will restate, being able to generate sites is only one opportunity, although it has inspired many new members recently.
I believe its key advantage is how any change can be immediately reflected throughout the whole wiki extremely efficently. This is more powerful than most people recognise.
Also despite the server options, the single file wiki is also an importiant principal and again results in massive advantages. Although it is a rule that can be broken, in a particular instance it will always remain a key principal.
Count on my support, I hope my words help yourself and others gain insight to the current culture here including our openness to new ideas and cultural evolution.
Regards
Tony
Thanks for those details!
It helps to see how some of my points relate to the inner workings already. Note that I was mostly talking in the general sense for the concepts above, so many of the things I mentioned could already exist in some form.
I see your point on tiddlers usually being _the_ content and not the ones containing it via view templates and tag lists. I have this to some degree as well. However for new users, I think there's a big gap between "oh I can enter text and make it bold and save it, that's cool" and "I am the master of tag based filtered list macros" :D
What the above does point towards is that it would be better if the solution was extensible in some way, to support all the custom use cases that arise. Now all this could be at first is just a generic view template that you can install and that adds this functionality to all tiddlers by default.
I don't know how useful it would be for experienced users, but for new users I think it would help ease them into the syntax and help with writing text-based tiddlers.
I want to emphasize here that this would just be a potentially easier way to edit simple notes, it should of course integrate with all the existing TW functionality - meaning editing text would keep being reactive. The "blocks" I was referring to was a shorthand for parts of a note - this might have a big (full?) overlap with Widgets, so if it does, just replace block with Widget in my previous email ;)
Best,
Miha
At this point in time the learning curve is way to high for me to optimize the interface and workflow the way I want with TiddlyWiki.I think TiddlyWiki is still a super tool and is very promising with all what's done. But at the moment a bit too inconsistent, difficult to use. Plugins help but then everything is very patchy.I know for many people TW is a hobby. But I just want a tool that works, I don't want to tinker with it every day, keep fixing bugs and inconsistencies.Therefore, I think it requires a different organised approach to asses the vision and make it more modern, matching the nowadays needs and expectations (RoamResearch, Obsidian content editor, static site builders...).
[...] I just want a tool that works, I don't want to tinker with it every day, keep fixing bugs and inconsistencies.
--
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 tiddlywiki+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/150fc9a4-7675-4799-a6aa-ce6966ce9ceb%40googlegroups.com.
Given that HTML is the target for both
Mat I think there is a bit of difference tinkering in tiddlytext and something widespread and future proof as html/css/js.Also there are much more resources, people had every single problem thousands of times.
I strongly agree with central place where to publish stuff. Imagine if there was a website where top solutions are promoted, voted up. Those would get attention and be improved by donations and contributions. Over the month with TW I kept discovering great stuff, just couple of days ago I discovered Tekan by Riz. Truly amazing example of how TW can be anything.–––––––––––––––Riz I am up for a discussion and feedback! I really want to help TW. Let me try to explain.Given that HTML is the target for both
This is not true for me. I only want to publish some of my notes. It's important for me to also build a personal knowledge system. With the right format and organisation system Niklas Luhmann developed his "second brain" – the Zettelkasten modular noting system just by using paper notes. I want to achieve similar with modular human readable, file based digital notes. Markdown fits perfectly for this purpose, the format is universal, very portable, supported by many editors, systems. So I strongly agree with Scott here. Markdown is a strong original readable format. I like the idea of starting with Markdown (in some cases JSON or CSV) as a base data/model format
and then add logic and structure with html/css/js.Next very important thing for me is the editing experience. If I spend a lot of time writing, I want it to be pleasant and calm. That's why I love Typora, a super minimal text editor, doingone job well – editing content. The editing interface is separated from my data files, I can change to another editor at any time I want. That being said, I wish Typora had some of theRoamResearch superpowers. And funny enough something like that was released couple of months ago – Obsidian. I think in time we will see more and more editors that are madefor interconnected thoughts, complex thinking.
I also wish TW would become like that one day – a tool that connects well with other workflows and not a monolith system (that is super modular but internally).I use VSCode but it's optimized for coding and not for writing. The interface is way too complex for a writing tool.Maybe that's another thing that I would like to see in TW – much more separation between building the tool/tinkering and writing, thinking connecting thoughts. It's like when you are driving a car you don't wan to see all the engines and electronics (while some people still would enjoy that).
--
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 tiddlywiki+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/75d1df71-630e-4940-a7bd-5457dee823b4%40googlegroups.com.
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+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/CAO0b0pFAG%2BBgfunT-7kRzbs3qj3oVcoRCqDAn9JfJuFQLN%3DNpQ%40mail.gmail.com.
Definitely I think markdown should be the default to reach broader masses. The focus should be on easy to use interface, easy markup language. Tiddlytext can stay for configurations and customisations, but users don’t need to get there easily, it can be in settings.
--
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 tiddlywiki+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/c851050f-63b3-48af-bd93-04642cf48f54%40googlegroups.com.
Definitely I think markdown should be the default to reach broader masses. The focus should be on easy to use interface, easy markup language. Tiddlytext can stay for configurations and customisations, but users don’t need to get there easily, it can be in settings.
On 19 May 2020, at 02.43, Rizwan Ishak <madapeed...@gmail.com> wrote:
Glad you find Tekan amusing.So if let me try and summarise.If markdown was the main markup system, users would find TW5 more accessible?
On Tue, 19 May 2020, 05:41 Edgaras, <edgar...@gmail.com> wrote:
Mat I think there is a bit of difference tinkering in tiddlytext and something widespread and future proof as html/css/js.Also there are much more resources, people had every single problem thousands of times.I strongly agree with central place where to publish stuff. Imagine if there was a website where top solutions are promoted, voted up. Those would get attention and be improved by donations and contributions. Over the month with TW I kept discovering great stuff, just couple of days ago I discovered Tekan by Riz. Truly amazing example of how TW can be anything.–––––––––––––––Riz I am up for a discussion and feedback! I really want to help TW. Let me try to explain.Given that HTML is the target for bothThis is not true for me. I only want to publish some of my notes. It's important for me to also build a personal knowledge system. With the right format and organisation system Niklas Luhmann developed his "second brain" – the Zettelkasten modular noting system just by using paper notes. I want to achieve similar with modular human readable, file based digital notes. Markdown fits perfectly for this purpose, the format is universal, very portable, supported by many editors, systems. So I strongly agree with Scott here. Markdown is a strong original readable format. I like the idea of starting with Markdown (in some cases JSON or CSV) as a base data/model formatand then add logic and structure with html/css/js.Next very important thing for me is the editing experience. If I spend a lot of time writing, I want it to be pleasant and calm. That's why I love Typora, a super minimal text editor, doingone job well – editing content. The editing interface is separated from my data files, I can change to another editor at any time I want. That being said, I wish Typora had some of theRoamResearch superpowers. And funny enough something like that was released couple of months ago – Obsidian. I think in time we will see more and more editors that are madefor interconnected thoughts, complex thinking.I also wish TW would become like that one day – a tool that connects well with other workflows and not a monolith system (that is super modular but internally).I use VSCode but it's optimized for coding and not for writing. The interface is way too complex for a writing tool.Maybe that's another thing that I would like to see in TW – much more separation between building the tool/tinkering and writing, thinking connecting thoughts. It's like when you are driving a car you don't wan to see all the engines and electronics (while some people still would enjoy that).--
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 tiddl...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/75d1df71-630e-4940-a7bd-5457dee823b4%40googlegroups.com.
--
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 tiddl...@googlegroups.com.
May be TW5 can offer an edition where wikitext markup mimic the markdown syntax. It won't be hard, a few regex changes in 20-25 parser tiddlers. That way new users don't have to deal with learning a new markup. If they do not intend to dive deep to use widgets and macros and all, they can simply stick to using just what they want.
--
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 tiddlywiki+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/7cc7a473-59d2-48fa-945c-eda4e01a2202%40googlegroups.com.
The idea is to get users to use widgets and macros, definitely. However, the question is how to get them to that level quickly. If the syntax for normal things like headings, bold and italics are something they are already familiar with, users don't have to spend time picking them up. That time could be better spent on learning things like macros and widgets.
I also think, that the info button should be part of the EditTemplate. Same thing here. Most elements of the editor can be hidden behind it. [...]
Even the tag-editor and the title field can be removed, except, if the tiddler is named New Tiddler or something similar.
With a mechanism like this, plugins can add "reference / backlinking" output into the tiddler info section OR at the end of the xxTemplate, and the user can decide, if and when they want to see this info.
Similar to this example: https://wikilabs.github.io/editions/slant-01/#04-clicking-tag-opens-tagmap ... If you click a tag, it will open something that I called "Tag Map". [...]
If the (i)nfo button would be part of the default UI, I'm pretty sure users will click it, because it is something special and they want to know, what's behind it. I'm sure, the "more" chevron is completely ignored by most users.
--
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 tiddlywiki+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/dc1f486f-2630-400e-bdcf-128045403354%40googlegroups.com.
I also think, that the info button should be part of the EditTemplate. Same thing here. Most elements of the editor can be hidden behind it. [...]Hear hear.
Even the tag-editor and the title field can be removed, except, if the tiddler is named New Tiddler or something similar.Hmmm... ;-)
With a mechanism like this, plugins can add "reference / backlinking" output into the tiddler info section OR at the end of the xxTemplate, and the user can decide, if and when they want to see this info.Similar to this example: https://wikilabs.github.io/editions/slant-01/#04-clicking-tag-opens-tagmap ... If you click a tag, it will open something that I called "Tag Map". [...]Not sure about that particular proposal
- I think the current behaviour, i.e that you get a dropdown for the current tag is pretty good.
However, interestingly, there is no "feature" if you click tags in edit mode. IMO this place would be useful for tag settings etc.
If the (i)nfo button would be part of the default UI, I'm pretty sure users will click it, because it is something special and they want to know, what's behind it. I'm sure, the "more" chevron is completely ignored by most users.Where do you propose the content from the chevron should go? Or should the chevron stay and there should be four default toolbar buttons?
--
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 tiddlywiki+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/085df749-0bad-4ede-9af5-f1d28461eced%40googlegroups.com.
To unsubscribe from this group and all its topics, send an email to tiddl...@googlegroups.com.
[Edit] read the original post under the line belowUPDATED: 2020-05-21Google Document outlining the strategy for redesign: TW Rewamp Outline 📄Link to the latest prototype (on Figma design tool): TW revamp v0.03📐Link to the videos of the prototype: Prototype videos🎬–––––––––––––––––––––––––––Hello everyone!I've just recently discovered TiddlyWiki (crazy it's been around for 15 years already!) and I am very pumped up about it! It's not only a great note taking tool, but it's also a powerful CMS + Static Site Builder!I think that TW deserves and has a potential of reaching broader audiences!However, one of the biggest drawbacks for me is the design of TW. And not only the visual design, but also the whole experience of using it. The functionality and features seem very powerful (and I am just scratching the surface), but the first time experience of using the tool is not very pleasant. I really think we could greatly improve the visuals and usability of TW, to match the other modern tools, and people expectations.This would address many of the root causes of these problems: Rethinking tiddlywiki.comI am experienced UI designer and I am willing to volunteer on creating a new minimal and simple, yet still powerful TW theme!I am looking for a developer who knows TW well and who wants to collaborate on creating this new theme. I code myself a bit, but it would be way more effective to collaborate with a bit more experienced coder.If there will be more interest, I will share all the design files on Figma, so anybody can give feedback and we can improve the designs together!Anyhow, I would like to know if anybody can also see the value in what I am talking about? 😊Cheers!- Edgaras
Yes, certain features and abilities will get underplayed in favour of more affordances for others, and that is OK for now since we are not replacing the UI in the standard distribution.