4 ms·
I watched the movie on the linked website, but I really don't get what "fluid" editing is supposed to be and what problem it solves? (I've been using OmniOutlin
by elcapitan 4y ago
I watched the movie on the linked website, but I really don't get what "fluid" editing is supposed to be and what problem it solves? (I've been using OmniOutliner for years and never missed something like described there)
- Exuma 4y agoIf you don't see how that's fluid and why it's valuable then that feature isn't for you. But it's certainly unquestionably fluid unlike a lot of other trash apps.
- samatman 4y agoNot recognizing what the word is supposed to mean in this context doesn't imply any of those things.
- Exuma 4y agoIt most certainly does, lol. There's a lot of programmers who have literally zero design aesthetic. I bet 99% of the people who don't understand what "fluid" means in this context fall into that category. Anyone with even a remote sense of aesthetics and design will immediately recognize the fluidness of the navigation/animation/flow
- mikeg8 4y agoWhat a great non answer
- dchest 4y agoI made a tiny screencast showing the big difference: https://imgur.com/a/u1QTns6 https://imgur.com/a/u1QTns6 OmniOutliner feels like it has a separate text field for each node. Bike feels like a text editor when you're editing a document with nodes, which to me is more natural.
- ask_b123 4y agoI'd recommend using KeyCastr to show the keystrokes while recording.
- dchest 4y agoYeah, sorry for the lack of keystokes. I usually use ScreenFlow which also has this feature, but for this one I used LICEcap.
- elcapitan 4y agoThanks! So this is more about seemless navigation than about the actual editing, I guess. I've always used OmniOutliner as a sort of "Excel with Tree" (multicolumn outline), so having separate cells is kind of an obvious default or even main feature for me. I can see now how purely longform-text cases might profit from this version.