Hello everyone, this week as usually I’ve been doing quite some things:
- I released gedit, gtksourceview and gedit-plugins. This means that there is already one release with the Tab Groups feature, so please test it and let us know if you find any bug on it.
- I’ve been reviewing quite some patches, lang files etc and also I’ve been fixing bugs in the Tab Groups thingie.
- Apart from that, I’ve invested quite some time on getting ready the step 2 of my GSoC, the splitview. As commented in my previous post, last week I was working on it, and this week I continued that work. Right now the core part is almost ready, I just need to fix a few things and discuss with my mentors some API needed for plugins. You can find this work as usually in my github. In the splitview branch. It is already usable but if you want to try it, remember to disable the plugins first, or you will experience casual crashes.
So, what am I going to do next week?
Next week I’ll try to have ready at least the core part of the splitview, and I’ll start porting the plugins to use the new API. A few of them will work for free, but the ones that modifies the document or the view, will need to be changed. As you can see I’m beeing carefully about what I can achieve next week, as I have my last examn and probably I’ll not be able to invest as many time as I want. Though, I finished the Tab Groups thingie sooner than I thought (mainly because I started working on it before the code time started) so the schedule I made in my proposal is still good for me.
In case anybody is interested I made a screencast about the splitview working. You can find it here.
Hello everyone, this week I’ve been working on several tasks that I think you might find interesting:
- As I said last week I was working on getting support in gedit for tab groups, and this week we’ve been reviewing the work and fixing several bugs that we found. The code is now merged in the master branch, so please test it and let us know what you think about it, and if you find any bug please file it under bugzilla.
- Now that the notebook thingie is ready, I have started to work in the second step of my GSoC, the splitview. It will allow us to split a document, and see and edit several parts of it. This is not an easy task, as for each split we have to create a new view and a new document and keep them sync with the real ones. I’ve spent quite some time thinking about the best way to implement it, and I also started to implement a few things, but the hard work is still coming.
- Apart from this, I also spent quite some time reviewing patches and fixing some bugs that came around.
- Finally, in the weekend apart from working in the GSoC, jesse was making some awesome in gitg, so I decided to resurrect a branch to convert gitg into a library, and with jesse’s help we made it and is now in master. So now, if you want a really cool backend to add git support to your application, libgitg is a really good one. If you didn’t try gitg yet, I tell you that you should as it is a fantastic tool. gitg rocks!!
As I blogged before, I am going to be working in the first step of the gedit multiviews SoC, adding tab groups to gedit. This week I’ve been working on this and I think I’m quite close to have something stable to push to master. So what have I really done this week?
- Yesterday I’ve released gedit, gedit-plugins and gtksourceview
- I’ve been testing a bit pygi because of libpeas
- I updated the gedit dependencies in my jhbuild to test how it behaves with gtk+3
- I’ve been refactoring and fixing some issues in GeditWindow needed for the tab group thingie. These fixes are already pushed into master.
- I’ve been working in two branches in my github:
- notebook2: In this one I implemented the tab group directly in the GeditWindow
- notebook3: As the previous implementation in notebook2 added too much complexity to GeditWindow I factored out the code and created a new class GeditNotebookGroup
Also as usual the mandatory screenshot:
I want to inform that gedit is finally using gsettings. There are still some missing things that I don’t know how to do yet so if somebody can tell me would be great:
- Add short and long descriptions (See that we use the revolutionary scheme format
- Mark a key as translatable
- Have bindings for gsettings to use them in the python plugins
We really need some testing here so if anybody is able to test it and inform us about errors would be great. Also I’d like to thank to everybody who helped making this port and the ones working in gsettings
So this year I decided to send a proposal to be a student in the summer of code, and I’ve been chosen!! In my project I’m going to be working on some awesome for gedit, see: http://live.gnome.org/Gedit/Multiviews for what we have in mind. I hope to have some news soon.
Also I’d like to thank Google, GNOME, the great community and specially to my mentors Jesse, Paolo and not my mentor but still there when is needed Steve
The other day I saw the announce by Sven Herzberg about the gutachter tool, so I decided to make a plugin for gedit. The plugin can be downloaded from my github: http://github.com/nacho/gutachter . I hope you enjoy it, and kudos to Sven for making this tool and a so easy to use API.
In this post I want to comment a little bit about the progress on gtranslator. In the past months I fixed several critical bugs and I added a few cool features. Though nowadays I’m not having so much time to invest on implementing big things, I’m just bugfixing. So I was wondering if anybody would like to invest some time in this project helping us to implement some things that I have in mind:
- A new backend for the translation memories using sqlite. Currently we are using libdb and it is becoming a pain to maintain.
- Provide a way to fill automagically the header fields.
- A plugin to provide a glosary (Easy stuff but it would take some time)
- Finish the project manager I made some time ago and maybe deal with damned-lies with it.
- Add some interfaces to be able to open different documents. Right now gtranslator only deals with PO files. Or maybe create some conversors and manage everything with po files internally.
- Seal the API and provide bindings for python or vala.
- Bug fixes in general.
So if you are interested in this project feel free to join us in the #gtranslator channel on GIMPNET to tell you how you can start helping.
I think there was quite some time since my last post about gtranslator. After some months without touching anything on gtranslator I decided to come back to it and fix several critical bugs and I think that right now is in quite a good state. We still have to seal the API and fix here and there but now I think it is usable and quite useful for gnome translators.
About the latest news:
- As you can see we have a new logo!! I think it is really good and I’d like to thanks Ulisse Perusin.
- Removed the subversion plugin as it is quite useless right now. (Hope we will have a git plugin soon)
- I refactored all the api using gtr instead of gtranslator. (Quite a pain task)
- No more weird crashes with the header.
- Now we use libunique so we use a single instance (I’d like to thanks to the libunique devs for their great work)
- And quite a lot of bugfixes.
So if you are a translator please test this program and let us know what you think about it, how you would improve it and file bugs!!
Yeah!! that is our current logo, it looks sooooo old, so we are starting a contest to pick a new one. If you feel brave enought to make us one, here are a few requisites for the logo:
- The logo should be under a free license compatible with gedit’s license
- The logo should be in a format editable with free tools and possibly realized with free tools
- The logo should say gedit, not Gedit or GEdit or gEdit
- The logo should be stylish but simple with not too many colors
- The logo should have a transparent background to fit in different contexts like web-pages, about dialog etc
While you are free to come up with something that looks totally new, here are some suggestions to please some of the maintainers that are going to pick the winning logo:
- We would like to avoid cartoonish logos and cartoonish fonts
- Do not simply take the text-editor icon and stick “gedit” on top
- For historical reasons we would like to keep the current dark red color
Finally, to send us your proposals, you have to send us an email with the logo to: “pborelli AT gnome DOT org”, “jessevdk AT gnome DOT org” and “icq AT gnome DOT org”
Thanks in advance.
Thanks to the great work from John Stowers we finally have updated packages of pygtk, pygobject and pycairo.
So these days we’ve been working a bit on having python plugins working on gedit, and of course we made it!!
You can download the installer from here.
Please test it and let us know which problems you find by commenting here or in the next bug:
PS: The “External tools” plugin as you can imagin doesn’t work on windows.