Since GNOME’s move to using git and the fact that upstream is where all the cool kids hack I have decided to move D-Feet to the GNOME servers to make it easier for contributors to contribute and users to file bugs. That doesn’t mean I’m going to fix every feature request but it does mean others can help make D-Feet more useful.
I was sort of blown away that my humble little project was being used by more people than I had realized. I was even more amazed that it was mentioned in the literature for the GNOME Developer Training Days at this year’s GUADEC.
That is not to say I think D-Feet is a particularly shining example of how a D-Bus debugging app should be written. It kind of sucks but it does fill a niche, which is why I am starting a new design process for potentially developing a better D-Bus debugger. Here is the hitch, I don’t want feature requests, I don’t want your bug reports (those can go into bugzilla), what I want is your workflow. How do you debug your D-Bus apps? What are the pitfalls, the annoyances, the most repetitive tasks that you encounter? Please head to the Workflow Design page and add your own voice.
D-Feet is a D-Bus debugger written in PyGtk+ by John (J5) Palmieri[read this post in: ar de es fr it ja ko pt ru zh-CN ]