31 Mar 2006

It’s great to see gedit plugins pop up on planet gnome. I am already addicted to Richard’s devhelp plugin and seeing actual code for a collaboration plugin is awesome: remote editing is something we have talked about more than once in #gedit, but it looked like a fairly large task so we didn’t investigate the details yet. Leveraging Python and Twisted, jdahlin managed to create a first prototype in a handful of lines of code!

Speaking of plugins, Steve and Jesse agreed to maintain the gedit-plugins module which will contain a collection of useful plugins not included in the main gedit package. Inclusion of plugins in that module will be fairly liberal so feel free to get in touch we them if you want your plugin included[¹].

I feel this is a good time to give some visibility to some of the good plugins that people have developed in the last months:

  • Marcus Leyman developed an awesome FileTree plugin. This is something we really want to include upstream and David Jonas has been working on Leyman’s code to refactor it into a GtkWidget and adding some features to it.
  • Gábor Fekete has a CTags plugin. He is looking for someone to help him out, so if you are interested…
  • Frederic Back created a couple of useful plugins , in particular a python class browser
  • Markus Jonsson has a plugin to export an html file with syntax highlighted code
  • Guillaume Chazarain did a word completion plugin
  • seahorse includes a gedit plugin to encrypt documents
  • Mikael Hermansson has a small collection of plugins
  • Marcus Lunzenauer developed a plugin to add handy editing features like delete line etc
  • Probably more I forgot about… feel free to remind me :)

Thanks to all of you guys!

[1]: you still need to help them maintaining it, they are not superhumans :)

20 Mar 2006

displaying system info

I saw on planet kde a screenshot showing system information when you click on ‘Computer’. I agree that it is nice to offer the user easy access to that information and the screenshot is definately visually pleasing. However I doubt it’s useful to display all that stuff every time I open the ‘Computer’ folder and some of the items in the screenshot look fairly unrelated (e.g. CPU specs and common folders).

I think that a nicer place to put some of that info is in the Properties page that you get when right clicking on ‘Computer’ icon in nautilus, so yesterday evening I put together a quick hack with the awesome nautilus-python to prototype the idea:

Code is here in case anyone would like to play with it. It sure needs some more ‘bling’ (memory info and pretty icons), also I guess it would be better to fetch some of the info from HAL instead of parsing /proc, but hal-device-monitor shows all ‘unknown’ for the CPU on my system so I haven’t tried to use it.

03 Mar 2006


clubfan has written a new gtksourceview based editor for anjuta reusing gedit code. I am really happy to see this work and I’ll try it out soon. All the hard work done in the last months to make the gedit code clean and nicely split in GObjects pays off since apparently reusing it for anjuta has been pretty easy. Obviously all the cut&pasting is a subotimal solution since makes sharing fixes harder, but as a first step I am happy that at least we avoided to reinvent the wheel once again.

I also noticed that every object was renamed to the use the “anjuta” prefix… while in general properly namespacing the code is a good thing I would have preferred if the “gedit” prefix was kept: it would be one less problem when it comes to merging bugfixes.
I also suggest to keep a file in cvs with the date of the gedit “snapshot” you used so that you can see more easily what needs updating.

In the future we should really split things in a real library and push some of the bits in lower part of the stack like gtksourceview and gtk itself.

PS: Johannes, the comments are not in spanish, they are in italian and are just a few leftovers from developement discussions we had and that we plan to cleanup as soon as possible :)