Thanks for the info Jasper. -- (o_ //\ Regards, Groeten, V_/_ Bas Burger.
On Fri, 13 Jul 2012 19:28:30 -0400 "Jasper St. Pierre" <jstpie...@mecheye.net> wrote: > On Fri, Jul 13, 2012 at 7:26 PM, Yaa101 <yaa...@xs4all.nl> wrote: > > On Fri, 13 Jul 2012 16:38:26 -0400 > > "Jasper St. Pierre" <jstpie...@mecheye.net> wrote: > > > >> On Fri, Jul 13, 2012 at 4:20 PM, Yaa101 <yaa...@xs4all.nl> wrote: > >> It should complain wildly in stderr, but maybe you weren't looking > >> there :) > > You mean in lookingglass on the error log? nope, no complaints > > there, not before my solution nor after. > > I mean in stderr. That's usually redirected to ~/.xsession-errors. > > >> >> Most CSS properties are supported by all elements, and you can > >> >> add your own properties by looking them up on the theme node. > >> > > >> > Can you explain further? looking up where? > >> > >> On the theme node > > theme node? please elaborate, just trying to learn here and > > sometimes I have to get pointed to what I am missing. > > If you have an StWidget on the stage, you can call get_theme_node on > it, and look up various CSS properties, and do whatever you want with > the values. > > >> > >> > And to come back at my first question, is there any reference > >> > document for ST besides the C version? > >> > >> Currently, no. There is going to be a new doc tool which will > >> handle language differences when generating docs, hopefully. It > >> should for the most part be a 1:1 mapping, except when it isn't > >> (destroy notify, gerror, out parameters). If work on the doc tool > >> doesn't improve, maybe we can lay down some rules of how to > >> translate the C API into the JS API. That would be a shitty last > >> resort, though. > > > > That is a bummer, also I cannot imagine that you, the developers, > > are able to keep track mentally the big complex beast you created. > > It's not that bad. I know that things are easy on the other side of the knowledge mirror, but I will get there, I just keep asking questions. :-) > > > I can say that I had easier targets to program, on the other hand > > the challenge of treading new territory is nice. > > > > I hope you succeed though. > > > >> > >> > -- > >> > (o_ > >> > //\ Regards, Groeten, > >> > V_/_ Bas Burger. > >> > > >> > > >> > On Fri, 13 Jul 2012 15:47:50 -0400 > >> > "Jasper St. Pierre" <jstpie...@mecheye.net> wrote: > >> > > >> >> On Fri, Jul 13, 2012 at 11:35 AM, Yaa101 <yaa...@xs4all.nl> > >> >> wrote: > >> >> > > >> >> > Hello all, > >> >> > > >> >> > Does somebody know where to find a proper reference on ST for > >> >> > gjs? I can find the C references > >> >> > ( http://developer.gnome.org/st/3.4/ ) but they lack detail on > >> >> > usage and interaction within the js system. > >> >> > > >> >> > What I am searching for is a document ala > >> >> > ( http://www.roojs.com/seed/gir-1.2-gtk-3.0/gjs/index.html ) > >> >> > but for ST. > >> >> > > >> >> > Is there any document that has this information? > >> >> > > >> >> > > >> >> > > >> >> > For instance I want to know what CSS properties each ST > >> >> > element use. > >> >> > >> >> Most CSS properties are supported by all elements, and you can > >> >> add your own properties by looking them up on the theme node. > >> >> > >> >> > Also I want to know how I can scroll a St.Table as putting it > >> >> > in a St.ScrollView will give an empty ScrollView on screen and > >> >> > using the table without a scrollview will show the table way > >> >> > too large. > >> >> > >> >> It needs to be in a St.Scrollable, like St.BoxLayout. > >> >> > >> >> > -- > >> >> > (o_ > >> >> > //\ Regards, Groeten, > >> >> > V_/_ Bas Burger. > >> >> > _______________________________________________ > >> >> > gnome-shell-list mailing list > >> >> > gnome-shell-list@gnome.org > >> >> > https://mail.gnome.org/mailman/listinfo/gnome-shell-list > >> >> > >> >> > >> >> > >> > > >> > >> > >> > > > > > _______________________________________________ gnome-shell-list mailing list gnome-shell-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-shell-list
