This is a bit strange as an issue, also because I am more of a ruby-guy :-)
But I also know python, and oddly enough many python-gtk examples work
for ruby-gtk too.
Anyway.
I found the project here indirectly from a blog where custom pygtk widgets
were shown and explained, e. g. that talking wave-like thingy when speaking
to the phone or something. This was quite interesting; I did not know that
this can be done in pygtk as easily (or however the name is now with
gobject-introspection).
So, my request: do you guys think it would be possible to have some
"tutorial mini-series", perhaps every a few weeks or so, to not burden
you too much, discussing some GUI-specific elements in susi_linux?
This does not have to be anything long! Everyone has time constraints.
But I think this could be interesting, if susi_linux is maintained, then
GUI-specific decisions could be explained. So perhaps every 2
months or so, e. g. when enough time has passed, to also document
a few of them in some markdown file or something. It does not have
to be maintained either, so just to document when it was working,
a bit similar to the blog entry (I forgot from when I saw the blog
entry, already had the browser tab closed, but I am 100% sure
it mentioned susi_linux).
Anyway, please feel free to close this - this is more some comment,
not necessary to keep it open at all. Thank you for reading.
Hey there,
This is a bit strange as an issue, also because I am more of a ruby-guy :-)
But I also know python, and oddly enough many python-gtk examples work for ruby-gtk too.
Anyway.
I found the project here indirectly from a blog where custom pygtk widgets were shown and explained, e. g. that talking wave-like thingy when speaking to the phone or something. This was quite interesting; I did not know that this can be done in pygtk as easily (or however the name is now with gobject-introspection).
So, my request: do you guys think it would be possible to have some "tutorial mini-series", perhaps every a few weeks or so, to not burden you too much, discussing some GUI-specific elements in susi_linux? This does not have to be anything long! Everyone has time constraints. But I think this could be interesting, if susi_linux is maintained, then GUI-specific decisions could be explained. So perhaps every 2 months or so, e. g. when enough time has passed, to also document a few of them in some markdown file or something. It does not have to be maintained either, so just to document when it was working, a bit similar to the blog entry (I forgot from when I saw the blog entry, already had the browser tab closed, but I am 100% sure it mentioned susi_linux).
Anyway, please feel free to close this - this is more some comment, not necessary to keep it open at all. Thank you for reading.