About
wind&oil, Weblog
Syndicate:
Subscribe to a syndicated feed of my weblog,
brought to you by the wonders of RSS.
Projects:
www.behrmann.name
www.oyranos.org
ColourWiki
CinePaint
Others Bogs:
Color hacks
mulebakken.net
Linux Photography
home :: docs
Welcome to Wind&Oil
Here is Kai-Uwe Behrmann's blog for your pleasure.
/docs | 1 comment | permanent link |
CMake hassle
CMake is wrong in claiming it generates unix makefiles. It generates lots of
dependend files, which must be read to understand the whole process. Nothing
selfcontained. All is spread over many files and various dependencies. Cmake
feels much like a PHP hack. If CMake could render it true to generate native
build files, I mean selfcontained unix Makefiles and projects files for other
build environments, CMake would be a great tool and probably help reducing
complexity. Currently it is more close to autotools laboriousness.
Changing the paradigm from
automated configure scripts to a full interactive only configuration process
moves the new build environment clearly to Windows. In the same way CMake looses
a clear Unix feeling.
To make it clear, I dont like to use libtool with its timeconsuming complexity.
But what makes Cmake substancially better? As I often try to compile many
different projects, my benchmark is, how quickly can I overcome a unexpected
problem during the build process?
The following questions arise quickly [with CMake answeres]:
Do I need to learn a new syntax? [yes]
Are all tools and dependencies in one place, making needed adaptions easy and straight forward? [no]
Does I get a project relevant help message by default to change options or set variables? [no]
Can I easily trace wrong parameters to its source, without the need to go
through various files and possible learn theire syntax? [no]
Can I use the tool in existing automated envioronments? [not obvious]
If you search for a elegant and simple buildenvironment, chances are high
you dont find it with a current version of this tool.
/docs | 1 comment | permanent link |
Plug-ins for Compositing WMs
this text is solely about a idea for a project.
The KDE4 site [1] has given their reasoning on why to reject Compiz.
Expectedly Gnome will jump in similiar wording. I just want to raise one
point about compositing effects/plug-ins. Plug-ins form a great users
space to interact with ideas and code.
It is correct stated that Compiz exposes too much details about its
internals into plug-ins. So its hard to reuse compiz plug-in code for say
kwin.
Anyway the underlying logic is pretty simple.
Shaders are small text files.
The desktop has a visible and virtual size, workspaces, monitor outputs,
windows, subwindows, edges, a task bar, shortcuts, a property system
(Xorg Xatom's) and some more.
So from a logical point of view it could be possible to write one
plug-in for serveral compositing engines.
What I, as a plug-in author, would find great is a project, which
developes a common script language and implements native plug-ins for each
of those window managers acting as a script host.
Based on a simple and common logic script authors could write text only
plug-ins. Obviously shaders are very likely to be part of such a system or
possibly OpenCL if mature enough.
I know coming with code or a detailed proposal is nicer. But if someone
searches for a nice Summer of Code project, that might become one.
[1] http://techbase.kde.org/Projects/KWin/4.0-release-notes
/docs | no comments | permanent link |
Drupa 2008
was a impressive tradeshow, with lots of people from the printing industry.
Showing machines is one part. One can get a good idea of what is actual in
printing effects, costs and handling, at least if some experience already
exists. What wondered me was, that at such a show, where much money is put into
booths, still occure obvious lapse with very simple things.
So at the Epson booth, which was fairly large, opalescence or broncing in the
proofs was rather the standard, even for the Oris RIP. I had expected they
sorted such things out and present the optimum of the K3 devices. But possibly
the connection of selling machinery and software in one part is more of an
objective in a customer relation. So customers see what they get after buying.
This helps decreasing support requests, while increasing satisfaction.
Minolta showed a very nice, and large, laser copier/printer. The colours
seemed constant, which is a major concern in using this technology for proofs.
Just the selected image was squeezed through a assumedly 8 bit rendering path or
a terrible profile. One could easily see in the presented gradients. It's hard
to recommend such a expensive device, if one does
not know how it can be done better from the software side.
What was really missed was a open source booth.
ArgyllCMS/LProf could be shown for calibration and profiling. There is
Ghostscript for rendering PDF's, CUPS for spooling, littleCMS for colour
conversions and Gutenprint for driving ink jets.
I would offer to demonstrate live my CinePaint proofing tutorial. This would be
the right audience.
To center around Linux/BSD seems not that much of a break there, with some
companies running Linux since years as servers for their workflows. At least
Samba would be a good add to the open source list above.
Well, whether it is possible to sort out broncing and provide a better rendering
path with pure open source components, would be a good toppic at the open source
booth.
/docs | no comments | permanent link |
OpenICC and Google Summer of Code 2008
OpenICC is a Freedesktop project that brings together just about everyone
who is interested in color for free software applications. That's:
ArgyllCMS, CinePaint, Cups, GraphicsMagick, Gimp, Gutenprint, ImageMagick,
Inkscape, Krita, karbon, LittleCMS, LPROF, Scribus and Oyranos. And, of
course, what's happening here has influence on the the Linux desktops.
This year OpenICC has been selected again as one of the projects that
can participate in the Google Summer of Code!
Hot topics for this year are the integration of a colour management system
into low level services, like Xorg and Cairo, HDR colour management,
hardware accelerated colour conversions, true multiple monitor support,
again Tonemapping and a toolkit independent GUI layer for plug-ins and CMM's.
Of course we are happy about continuing and improving our existing
applications, libraries and all being mentored by experienced developers.
The project ideas range from very simple "get familiar with open source"
style projects to advanced topics. Given they are all cross platform, they
have potential to influence colour management not only on Linux. With
students entering this round we hope to get closer to a colour managed
desktop with fun.
/docs | no comments | permanent link |
Libre Graphics Meeting 2008
The LGM happens to take place 8th to 11th may at the Wroclaw University of
Technology. I am quite curious about the city and the people to meet there, most
the first time in person. Even though we had sometimes contact some years
before.
There are primarily three themes for me,
- be present in a talk about the goals of OpenICC
- give a talk about the Oyranos colour management system
- discuss a, to be prepared, CM strategy for Cairo
For giving you a chance to help in the success of the event, you can donate to cover part of the cost for the attending developers.
/docs | no comments | permanent link |
LGM 2008
was for me a really impressive meeting. Really good was the talking on the
OpenICC BoF and with other project workers face to face to more easily
get a impression about, what are requirements and objections.
We met Carl Worth, and he and Behdad Esfahbod took the time to conceptually
let coincide the colour and Cairo internals.
One interessting talk was given about spectral imaging in Krita. Really nice
topic shared with the audience by Emanuele Tamponi.
Most talks are covered here.
Kamila Giedroj , Dave Neary, Louis Dejardins and all the other organisers made
good preparations. It was a pleasure to attent. Thanks.
/docs | no comments | permanent link |
Libre Graphics Meeting 2009 - Montreal
This years Libre Graphics Meeting will happen to be in
Montreal from 6 to 9 may 2009. LGM is a major community organised event to
bring open source graphic programmers and users together. On the last years
meeting, I could meet many persons en face for the first time and discuss one
of OpenICC's
Google Summer of
Code projects. It was a great bazaar of exchanging ideas in a friendly
atmosphere and I expect it to be a very helpful event this year too.
For giving you a chance to help in the success of the event, you can donate to
cover part of the cost for the attending developers:
/docs | no comments | permanent link |