-
Photstream
-
Shop
cyrille@identi.ca- Calligra News
- OpenGTL News
Institut de la Francophonie numérique sponsoring offer to travel to Libre Graphics Meeting
L’Institut de la Francophonie numérique is sponsoring travel and lodging to the Libre Graphics Meeting in Bruxelles on 27-30 May, for people from one of the country of francophonie, that are not France:
Albanie, Arménie, Bénin, Bulgarie, Burkina Faso, Burundi, Cambodge, Cameroun, Cap Vert, Comores, Congo, Côte d’Ivoire, Djibouti, Egypte, Gabon, Ghana, Guinée, Guinée Bissau, Guinée équatoriale, Laos, Liban, Madagascar, Mali, Maroc, Maurice, Moldavie, Niger, RD Congo, République centrafricaine, Roumanie, Rwanda, Sénégal, Tchad, Togo, Tunisie, Vietnam
So if you are an artist using free software, a developer implicated in a graphic open source project, and want to make a presentation (in either French or English) at the Libre Graphics Meeting, or if you know anyone from those countries, and that would fit the requirements, please read this email or give this email from the Create mailing list. This is a great opportunity to travel to Bruxelles, and meet other people of the Free Graphics World:
Braindump 0.8.0
A bit overdue, the first release of Braindump is available. It has been a while since I announced the project of making a tool that gather allow to dump your thoughts into an electronic form. For those who have forget (which is probably most of you), Braindump is a collection of whiteboards on which you can put your notes, whether text notes, or drawing. It is entirely based on KOffice technologies. Which made Braindump quick and easy to develop, and it makes it very small, around 8000 lines of code.
I have been delaying that release because I wanted to make a video of Braindump in action, and have been too lazy to make one until now. On that video I first create new whiteboards, then I demonstrate how to add shapes, manipulate them, and finally the different layout:
I you look at Braindump development history, you will notice that over the past six months the development has been really slow, there are a few reasons to that, the first one is that most of the development is done by other people than me in the KOffice repository, the second one is that I feel that Braindump is already doing exactly what I want, with a few glitches, but as a geek I tend to live happily with those…
That said there is a couple of features I want:
- Search (and replace)
- Tagging, but then someone else (yeah again) is doing the work for me in KOffice
- Auto-growing text shape
- A solution to this problem: (almost) each time I create a new whiteboard, the first thing I do is to add a text shape. So I wonder about either having always a permanent text shape in the background, or always add a text shape when creating a white board.
I am also starting to be curious about ownCloud, since personally I find it to be the right direction of cloud computing, so I would probably be interested in the possibility of storing whiteboards on an ownCloud server. Lets see how it evolves.
If you have other ideas, do not hesitate to mention them, who knows, if I find them interesting, I might go on and implement them !
Download Braindump 0.8.0, this release will work only with KOffice 2.1.x, from now on I will work on porting Braindump to the upcoming KOffice 2.2.
Krita, a painting application, not really new news
The time when Krita was borne as KImageShop, as a Gimp-for-KDE is long gone. Not sure when this idea was killed, but it is clear that it has never really be the intention of the current team. The ambiguity of being only a paint application might only have been lift last weeks, and not trying anymore to be both. But now was the best time to lift it, Gimp is now going in a direction where it will be an excellent image manipulation tool, it does not make anymore sense to try to have half-baked support for this kind of work in Krita. Instead, we need to focus on what is truly missing, a high quality paint application that covers all the artists needs.
But this focus of Krita is not new. What is new is our willingness to focus on it.
Boudewijn has always said that he started on Krita to make a linux application that makes the most use of his newly tablet, he even said at LGM 2007 that he wanted Krita to be a “corel paint killer”. More recently Vera joined us in the hope of helping us to make a good open source painting application.
Personally I started with a joint interest for drawing and photography, and probably considered at first that I wanted to contribute to an application that work for both use. And this would explain why most photographic specific features were written by me. But when I started to make digital pictures, I thought that one of the main interest over silver film was the post-processing, but I have come to realise that colour and brightness adjustment were all the changes I wanted to do, and that otherwise, the pictures need to be shout correctly, correct framing, correct positioning of objects, this require more work in the composition, but this also give greater pictures than cloning. Meaning, that I have mostly used Krita for drawing attempts.
But some other members joined us for photographic interest, and some people would still want to use Krita for those uses, I hope that we manage to work together and allow them to find their place in the Krita Community, either the new extensions website will prove sufficient, maybe a krita-photographic-extension package will be made available by distributions, or it is even possible to build a different user interface on top of Krita libraries.
This is something we are ready to help with, but what we feel is important is that when a painter starts Krita, he get all what he needs, and nothing more.
Krita’s Hackfest, meeting with the Blender guys
During this week, Boudewijn is hosting Sven, Lukas and me for a Krita hackfest, dedicated to bug fixing, performance, UI improvement. Among the major improvements brought by that week are improvement in the memory consumption, thanks to a collaboration between Dmitry and me, where I did some tracking and experimentation, and he found the actual problem. This fixed has allowed us to go from 2 minutes of drawing to exhaust my 2GB of memory, to make it possible to paint for more than 30 minutes, there are still some issues that need to be found and fixed. In the area of performance, Lukas have improve the performance of the flood fill by 60%, and I have reduced the time needed for some gradients by six (the other types did not seem to have the problem), unfortunately those improvements are not really visible, for some reason Krita currently spend a lot of time recompositing the image. While Boudewijn and Sven have been working on a scratchpad, as a new way to test new brushes settings, and working on a widget to input value that should be simpler when used with tablets, after Boudewijn’s call for help someone else has offered to help us with that.
Yesterday we went to Amsterdam to meet the Blender‘s guys. Since most of us has never been to Amsterdam before, Boudewijn took us for a long walk in Amsterdam’s street (or should I say canal), which started in the overcrowded area around the central station, that we left as soon as possible to walk in more quieter area:
Then at the end of the walk we arrived at the Blender institute:
Where Ton took us on a visit of the Studio, and then we assisted to their weekly update, where all the members of team show what they have been working on, their difficulties and how to solve them. After the meeting, we went to a restaurant, as an opportunity to know each other, and to learn more on how their work, and in hope that one day Krita can be useful for them.
Tomorrow, I will go back home in Göteborg.
The difficult choice of removing features
Adding a new feature is usually considered easy in the open source world, and then it is taken for granted. Removing a feature, on the other hand, it is a different story. It is not about making Krita less useful, au contraire, it is about making the best for our vision. But why remove a feature, they don’t disturb, or take too much space. They still come in the way and clutter, and what is the point of a menu entry, if you are never going to use it ?
Krita is now focused on being a painting application
We have mentioned in our blogs entry (by me in Krita meeting 2010 – day 1 and by Boudewijn Rempt’s blog) on last week-end Krita meeting, that we had now decided for a vision oriented toward painting.
Where does that leave photography ? Well clearly, it is out. And honestly, between Gimp (especially with their work on 2.8) and Digikam, there is not really much room for an other linux photography application to prosper. Since Krita was always more oriented toward drawing and painting, and photographic features were available mostly because “we can”, and there is no high-end application for drawing and painting on linux, the logical conclusion, for us, was to focus on where we can be the best, and the most useful.
Removing photographic-specific features
The logical conclusion is to remove the features that are not useful for painting. This include many of the photographic plug-ins, like tonemapping, bracketingto-hdr, lens correction, noise reduction filters. As well as a set of artistic filters, but that are mostly useful to transform a picture in something that looks like a painting.
And anyway there are better tool for that job, like the excellent Qtpfsgui, in action below on Deventer’s mill:
I started a discussion on the subject on Krita’s mailing list, which triggered a bit of a uproar. Especially from people who have used Krita for photographic editing. Live with it, use Gimp or Digikam, or install the removed plugins from the future extension website, write your own, just do not count on us for that, we are going to be focused on other features.
An extension website
Since it would sadden me to kill forever some of those plug-ins, and also while we do not want to support photographic features, or features that are of no interest for painting, we also do not want to prevent people to have or use those features, they will simply not be part of the default distribution. We are going to setup a new website where those extensions will be hosted, hopefully with “nightly” build (more like regular build) to keep them buildable, and synchronized with git/hg, where a tag would trigger a new release automatically. In essence a revival of the krita-plugins project.
Krita Meeting 2010 – Day 2
Yesterday was the second day of the krita meeting 2010. It was oriented toward technical discussions, and UI design discussions.
In the technical area, I and Dmitry had a long talk on how to improve the filter API, to make it both easier to write effect filters, retain performance and ensure that it is less buggy with respect to selections and masks. In meantime Lukas was teaching Vera how to implement new painting operation, so that she can work on a water color brush engine.
When it came to the UI, we talked about what to do with painting op presets preview, and it was decided that it would be more useful for the user to have a scratchpad where he can make his own testing of the current settings, rather than having a computer generated preview. Boudewijn is now working on implementing exactly that. We also discussed painting presets management, it is going to be very basic for 2.2, with just a list name and a preview (either computer generated or made with the scratchpad). And later we would like to have tags, search by tags.
And between two discussions, we were working on bug fixes, polishing features, etc… All the small details to make Krita an even better application. And now is the hack week, with Boudewijn, Lukas, Sven and me.
Krita Meeting 2010 – Day 1
Today was the first real day of the Meeting, we met again in the basement of the Church to be in a place without any possible distraction, and to discuss the vision of Krita, and what we want Krita to be.
We decided to focus on painting, sketching, comic books and texturing. As well as making an application for high-end painters. The question of how much the digital painting should mimick real-world painting, and based on our experience of watercolor in 1.6 that was so advanced that it would simulate the drying itself, we decided that real world should be an inspiration, but that there is no point to make digital painting exactly like real world, if you want real world, you can just take a real brush and paint. But it does not mean that we should take inspiration in real physics, when it makes sense, like for color mixing.
In the end, it took us more than two hours to define the following vision:
Krita is a KDE program for sketching and painting, offering an end–to–end solution for creating digital painting files from scratch by masters.
Fields of painting that Krita explicitly supports are concept art, creation of comics and textures for rendering.
Modelled on existing real-world painting materials and workflows, Krita supports creative working by getting out of the way and with snappy response.
It does not mean you cannot use Krita for something else, or develop plug-ins that solve a problem that does not fit the vision. But it means that we are going to be focused on implementing that vision, and that the default of the application will be oriented toward that vision. And when we have to make choices, we will look at the vision and see which decision makes more sense for the vision.
After the lunch, we took a digestive walk in Deventer streets:
Then we discussed about finding GSoC ideas, that would help to implement our vision, and concluded that a new transform tool and a good UI to access ressources was the two main ideas we needed. Then everybody went back to his computer, to fix bugs, to discuss UI ideas, and just to make Krita “the best application ever” (Vera’s tm).
