Glimmer DSL for LibUI - Prerequisite-Free Ruby Desktop Development Cross-Platform Native GUI Library - The Quickest Way From Zero To GUI - If You Liked Shoes, You'll Love Glimmer! - No need to pre-install any prerequisites. Just install the gem and have platform-independent GUI that just works on Mac, Windows, and Linux.
MIT License
497
stars
15
forks
source link
Release notes for libui-ng specific changes + glimmer-dsl-libui? #39
I see you were busy with rubyconf and probably some other things unrelated to
glimmer. cody271 is slowly adding more things to libui-ng ( https://github.com/libui-ng/libui-ng )
and kojix2 said some time ago that he will support only libui-ng eventually.
I have not really been keeping track of what exactly changed in regards to libui-ng specifically,
due to various reasons; in part due to other projects being more important, in part due to
some non-computer related things. Anyway.
If you ever get around to supporting all, or some, of the above, would it
be possible for you to also:
a) consider adding specific examples in glimmer-dsl-libui to showcase that
functionality? For instance, showcasing uiComboboxDelete() API or the
query uiTableColumnWidth() API via some examples.
Perhaps to simplify this you could just add a new meta-widget, similar to
how kojix2 (and other projects) show it via the libui-gallery; in this case,
a widget for glimmer-dsl-libui that would showcase all the new changes
available.
And b)
to somewhere or somehow document what glimmer-dsl-libui supports
and what not. This can probably be combined via a) already, so people
just run that widget, and can read the code to understand how to use
it too. But it could also be a separate document or something, if you
feel it is worthwhile to document this specifically. (Or perhaps not,
in the event that glimmer-dsl-libui will only run on libui-ng eventually,
anyway.)
Rationale for the above: the above is me being lazy, actually, so I am
hoping to leech off from your time. :D In the sense that I could have
one-widget-to-rule-them-all (aka in glimmer-dsl-libui) and then simply
look what is possible, and what has changed. The Changelog that cody
uses is nice, but it does not really tell me what exactly has changed now -
for this a widget would be ideal, to just showcase what is different not.
It could, however had, also be useful for people to keep track of what
has changed. For instance, baweaver, if he wrote some glimmer-specific
code, in two years may want to re-visit his widget, and then decide to
add some more things. So in this regard, a specification/documentation
would be useful for such users too, so my suggestion is NOT only
being selfish and lazy here. :D With the "one widget" this may also
reduce your own work load, as you can just write the things that
work into that file rather than have to update many different documents.
Anyway as always, please feel free to close this issue or disregard for
any reason at any moment in time. In case I may forget or not be
active (xmas I never know whether I have a lot of time or not),
happy new year soon and glimmer on for 2023! (And of course
whether glimmer works with the xmas release ruby too but I
assume it will.)
Hey there Andy,
I see you were busy with rubyconf and probably some other things unrelated to glimmer. cody271 is slowly adding more things to libui-ng ( https://github.com/libui-ng/libui-ng ) and kojix2 said some time ago that he will support only libui-ng eventually.
I have not really been keeping track of what exactly changed in regards to libui-ng specifically, due to various reasons; in part due to other projects being more important, in part due to some non-computer related things. Anyway.
cody271 keeps track of changes here
https://github.com/libui-ng/libui-ng/blob/master/CHANGELOG.md
which you probably know already.
Now to the reason why I filed this here:
a) consider adding specific examples in glimmer-dsl-libui to showcase that functionality? For instance, showcasing uiComboboxDelete() API or the query uiTableColumnWidth() API via some examples.
Perhaps to simplify this you could just add a new meta-widget, similar to how kojix2 (and other projects) show it via the libui-gallery; in this case, a widget for glimmer-dsl-libui that would showcase all the new changes available.
And b)
to somewhere or somehow document what glimmer-dsl-libui supports and what not. This can probably be combined via a) already, so people just run that widget, and can read the code to understand how to use it too. But it could also be a separate document or something, if you feel it is worthwhile to document this specifically. (Or perhaps not, in the event that glimmer-dsl-libui will only run on libui-ng eventually, anyway.)
Rationale for the above: the above is me being lazy, actually, so I am hoping to leech off from your time. :D In the sense that I could have one-widget-to-rule-them-all (aka in glimmer-dsl-libui) and then simply look what is possible, and what has changed. The Changelog that cody uses is nice, but it does not really tell me what exactly has changed now - for this a widget would be ideal, to just showcase what is different not. It could, however had, also be useful for people to keep track of what has changed. For instance, baweaver, if he wrote some glimmer-specific code, in two years may want to re-visit his widget, and then decide to add some more things. So in this regard, a specification/documentation would be useful for such users too, so my suggestion is NOT only being selfish and lazy here. :D With the "one widget" this may also reduce your own work load, as you can just write the things that work into that file rather than have to update many different documents.
Anyway as always, please feel free to close this issue or disregard for any reason at any moment in time. In case I may forget or not be active (xmas I never know whether I have a lot of time or not), happy new year soon and glimmer on for 2023! (And of course whether glimmer works with the xmas release ruby too but I assume it will.)