Re: Debugging a gnome-shell extension

["Jasper St. Pierre" <jstpierre mecheye net>]

On Sat, May 7, 2011 at 8:24 PM, rikutheronin gmail com <rikutheronin gmail com> wrote:

Hi!

I'm currently switching from gnome2 to gnome3. Is a very huge change, but I like most of things, like I'm more focused on one task and not on a lo of them.

But I have the problem that I *really* need Hamster time tracker application for my daily work, and actually the applet was very cool because I allways saw the current activity and don't forget to change it. But now there is no applets. I'm okay with that as long as you provide real alternatives to replace things we used before.

So I'm writing a gnome-shell extension with that purpouse: add a button to the panel where I can see an change my current activity. More or less it works, but I'm having problems with DBus (wich is for me a very ancient and rare kind of black magic) and I need to know what is failing. But is no easy:

• Is there anyway to debug "step-by-step" the execution of a gnome-shell extenion?
• Can I put breakpoints and debug it? 

Integrating jsd with the looking glass was planned, but the looking glass hasn't been worked on in a while. There's a lot of improvements *I* want to make to the looking glass (Firebug-level CSS tweaking), and I may do something about this and that next week...
 

If the answer is no, how the hell a mortal person can debug it's own application?

Log everything... You can also force a gdb breakpoint from _javascript_ with "global.breakpoint();"

The lack of documentation on this subject is something I think you should work on.

Best regards,

--
Pablo Recio Quijano


_______________________________________________
gnome-shell-list mailing list
gnome-shell-list gnome org
http://mail.gnome.org/mailman/listinfo/gnome-shell-list