4 ms·
Interesting tool, I like that it works with GitHub and the repo support will be cool to see. The design is neat (I generally like dark themes) although the fad
by lol768 10y ago
Interesting tool, I like that it works with GitHub and the repo support will be cool to see.
The design is neat (I generally like dark themes) although the fading animations got a bit annoying after a few minutes using it. Some of the dialogs could do with supporting common shortcuts (e.g. enter to create a new track, escape to close the dialogs). Sometimes I managed to click outside of the presentation view without realising, and then left/right arrow keys stopped working. Sometimes I wasn't sure where to find certain functions (e.g. I looked for "Edit" on a presentation item on the context menu, but then realised I had to click it and then click the pencil icon). I couldn't get the Share functionality to work, and wasn't sure why it was in its own context menu with no other items.
I'm not sure I understand the purpose of the tracks/channels distinction. I can understand creating a project to store presentations (items) in, but why is there another level in Kobble?
- kobble 9y agoPublic and private repos are available now.
- kobble 10y agoAs you mention, a track is like a project. It's a tree of items, and the items can be markdown, presentations, links, etc. Channels are for organizing tracks. Everything in Kobble can be shared. So say you make a track for some project and want to share it. Another user can add your track to a channel to follow it. It's similar to sharing in YouTube or Spotify, except that instead of grouping videos or songs in channels, you're grouping tracks.