This is no secret. I just did not want to pollute the list with all the
details.
Right now my extension leaves some messages in a file that it creates.
Those messages are organized hierarchically and help me to understand if
something goes wrong. What I wanted instead is to direct those messages
(
We might be able to give you some ideas if you told us more about your
situation.
On Thu, Apr 11, 2013 at 3:04 PM, Vadim wrote:
> Sorry, I meant to write "no" instead of "know". Anyway, it seems to me
> that you are right about DBus: this is just too "heavy". I will try to
> think differently
Sorry, I meant to write "no" instead of "know". Anyway, it seems to me
that you are right about DBus: this is just too "heavy". I will try to
think differently and implement a different approach.
Vadim.
On 04/11/2013 02:00 PM, Jasper St. Pierre wrote:
> No. They are in separate processes. You ca
No. They are in separate processes. You can set up some form of
communication using DBus if you want, but it's not recommended.
On Thu, Apr 11, 2013 at 2:51 PM, Vadim wrote:
> It's not that it needs to know about it. The preferences are mainly
> intended to be specified through Gtk+ widgets. A
It's not that it needs to know about it. The preferences are mainly
intended to be specified through Gtk+ widgets. And there is even
explicit requirement to return a Gtk+ widget in prefs.js. But as far as
I understand now, there is know other connection between the running
extension and Gtk+ prefer
GNOME Shell is not built with GTK+. Why does GNOME Shell need to know about
a GTK+ widget?
On Thu, Apr 11, 2013 at 1:41 AM, Vadim wrote:
> Yes, I know about GSettings and use them a lot to store static options.
> Thanks a lot in any case.
>
> Here I wanted to store a reference to a gtkWidget t
That can't work, since prefs runs in a separate process to
gnome-shell. You will need to use dbus to communicate.
On 11/04/13 15:41, Vadim wrote:
Yes, I know about GSettings and use them a lot to store static
options. Thanks a lot in any case.
Yes, I know about GSettings and use them a lot to store static options.
Thanks a lot in any case.
Here I wanted to store a reference to a gtkWidget that is created in the
preferences dialog.
The way I wanted to do is: gtkWidget is created in pref.js, a global
variable is used to reference the wid
Hi Vadim,
Could you just use gsettings (i.e. the same thing that you use with
`prefs.js` to store extension settings) for this?
In the `prefs.js` your widget does a:
let settings = Convenience.getSettings();
settings.set_int('my-setting-name', 1);
and in the extension you connect to the
