Neat Owlkettle Project ideas #147
Replies: 2 comments 2 replies
-
Building nice sidebars & applications with multiple pages is entirely possible without using GtkStack or GtkStackSidebar. You can use a |
Beta Was this translation helpful? Give feedback.
-
Generally though, I think it would be an important step for owlkettle to build an app and get it published on https://flathub.org/. I think it makes sense to build something that is useful not just to people using Nim. Maybe something like a nice vector graphics editor. The aim is building an app that people actually want to use and not an app that is just "the one owlkettle app on flathub". Ideally we could also use that experience to write a guide on publishing apps for the docs afterwards. |
Beta Was this translation helpful? Give feedback.
-
Honestly this is just me spitballing some ideas around to consider for myself later when owlkettle has more Widgets wrapped.
These could also be neat project ideas to point somebody to if they want to try out owlkettle but can't think of anything to build with it.
I'll expand the list here as I come up with more ideas or we can generally post more suggestions.
Here's the list:
1) GUI representation of nim docs
Write an application that reads in JSON output of
nim jsondoc
and visualizes it, similar to the HTML output.The application would be somewhat analogous to GTK's DevHelp application.
Easy and fast search for symbols, and their explanations, representation of modules etc.
Bonus feature down the line could be to enable opening a nim project in said application and it generates the JSON of nim jsondoc itself.
2) GUI for atlas
Nim 2.0 comes with the first iteration of a replacement for nimble: Atlas.
Could be neat to write a small GUI to use atlas.
Features it could have in general:
Features when looking at a specific project:
I'm sure there's more that could be done by just looking at the features the atlas CLI provides with
atlas -h
and seeing what could be sensibly wrapped and represented in a GUI.Note: In my eyes both of these currently face a blocker because in my opinion I'd want to have GtkStack fully wrapped and usable with GtkStackSidebar, which means we need to have a solved #115 as GtkStackSidebar requires a reference to the same stack that is being rendered.
Beta Was this translation helpful? Give feedback.
All reactions