I am porting lots of my old ruby-gtk2 applications to ruby-gtk3 finally. It was quite painful
but ruby itself is great, so this is finally going quite well (for me).
Before I switched to ruby in 2005 or so, I used php. I wrote quite a lot of web-related parts
in php. When I switched to ruby, the PHP parts I rewrote in ruby and have extended them
I have a lot of websites that have a structure such as:
This gets translated into a HTML img tag, with the correct path
automatically used, so that I don’t have to remember it.
Just as an example. This would find the local path to some image
showing a sunshine setting. This is embedded in a webpage.
Now the thing is … the way this is described, I can easily use this
in ruby-gtk too. So the above could simply map a gtk-image and
embed it into a widget.
What I am saying is that all my web stuff could, in THEORY, be also
used in ruby-gtk (thus gtk).
Even css will work, to some extent (I can autogenerate the css
“dialect” gtk uses, via ruby).
Via ruby-gtk, I can avoid it! The things I can do via ruby-gtk
GTK popover widget? That is quite similar to balloon widgets
Take gtk-text-view and stuff. I have, sort of, a table, that I
can dynamically update, change, and so forth. In some ways
the way I use ruby-gtk is a bit similar to the www; just that
focus on the MAIN functionality here. I don’t need
everything really. I also use jquery for image-effects or
widget-relocation, so I’d look for something like this
in gtk as well.)
Ok so far so good - I hope you can understand the background
Now … as I was thinking about things such as:
There are some things I can do in ruby + web, via jquery,
that I am not sure I can easily do in gtk. For example,
dragging a gtk widget holding an image; I can do this
very easily in jquery. Not sure how to do this via
gtk; I assume it is possible but I don’t know how.
Has anyone thought about this? Wouldn’t it be quite
cool if, say, a gtk application could seamlessly work
on the modern www as well? Sort of like providing
a mapping between the main parts of gtk, to the
www. Again - just for the simple parts. We don’t
necessarily need ALL of the functionality. Keep it
simple; and then afterwards it can always be extended
if it is important.
Note - I am NOT suggesting a 1:1 mapping. We don’t
have some meta-project that could be used by different
people; gtk, qt and so forth, where applications in gtk or
qt could, quite easily, also work on the www.
But I know way too little right now to know if anyone has
done this. There are many potential benefits. For example,
the game wesnoth could perhaps be played via the www but
the default bindings could be retained (I think they will
rewrite it in godot or whatever the name of that engine
is … godrin not sure).