>
> Roam users: do you need to know when each bullet was added or edited? Can 
> you imagine a situation where you might? Does Roam even let you see this 
> information?


Nope, I don't care when a bullet point was added or edited.

I think my proposal of top level item not being bullet points, but 
> subsequent items being bullet points is best of both worlds.


I think it feels more natural to just import it exactly as it looks in 
Roam, especially as your proposal assumes people mainly write essays in 
Roam, when really my bullet points are often actual bullet points, and I 
would be annoyed to have to add them back. But I'm so excited to have a 
solution at all that I'm not fussed if we drop the top-level bullet points 
even if I find that arbitrary.

Whatever you decide - this is exciting!


On Tuesday, May 5, 2020 at 12:34:50 PM UTC+1, Yoni Balkind wrote:
>
> For this one I disagree with Yoni. It should be bullet points in 
>> TiddlyWiki as well, to stay as close as the Roam experience. 
>>
>
> I think my proposal of top level item not being bullet points, but 
> subsequent items being bullet points is best of both worlds. It respects 
> the nesting levels but allows user to import a flat "essay" if they had no 
> nesting.. But Anne-Laure's approach (which is what @Riz did in his 
> prototype) is understandable and workable
>
> ...in the spirit of staying as close as possible to Roam, to not even 
>> consider the question of tags. Whether #Title or [[Title]] these should all 
>> be converted to [[Title]] in TiddlyWiki.
>>
>
> Agreed. But with some additional thoughts about how to use tags as 
> reflected in my earlier post (the one beginning "Okay, this is looking 
> promising..") 
>

-- 
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/cacb9303-ca12-4638-bbb9-9e995a5b75fd%40googlegroups.com.

Reply via email to