This evening I wrote a blog entry about this and then lost everything I wrote. What fun...here it is again, I hope that this once again explains the meeting we had tonight about the Oxygen Icons...
We decided:
1) to start a style guide...Oxygen Style Guide Working Ground
2) a naming spec wiki page
3) a list of basic KDE icons needed for the first release. Aaron Seigo is helping with this. He is our developer contact with a gold tooth. Honestly, I think that Aaron has done more for KDE4 artwork than any other developer (although we have had a lot of help, which has amazed me).
4) to go through the icons to make ensure consistency (this will be a reoccurring process. We will begin with the action icons to make sure they have the same shadow and size Nuno Pinhiero promised to do this because he was the creator of the shadow for the action icons.
all in all, there is now a lot more info on http://developernew.kde.org/Projects ... check it out!
Thursday, December 28, 2006
Wednesday, December 20, 2006
Oxygen and more
On Monday we had a semi-spontaneous meeting concerning the Oxygen style and window decoration. Actually, we had already started this stuff but nothing really ever became of it and in the meantime some very courageous people stepped up and started work once again.
So here is what it was all about
1. Explicit division of labour (e.g. who's doing what)
Boemann has been and will be working on code. Ruphy will help on this as well.
Zack and Aaron will help both by fielding questions/issue as well as probably contributing code (see below).
Pinheiro and Eriolloan will keep making the artwork.
Ken will help with disseminating artwork information as well as trying to coordinate things.
Zack would like to see graphical side of things build from blocks. He'd like most effects in kde4 based on an actual physical model - that's what will give them organic nature. For that we need an image manipulation framework that does animations and physics engine connected to it. Zack has code
started on each of those elements.
2. Communication between artists and coders
We need to put everything in reach of the public in order to gain as much support as possible and to avoid bitterness from all sides. With things out in the open we can move as quickly as possible without any deterrents or wasted time/effort.
In addition, we will soon experience a problem with our style/windec and certain applications which do not behave well. This information needs to be attained as well as acted upon. By having a central place for code people can test it.
Once we know which problems are occurring we can do one of two things:
a) Let the developer in question know of the problems and ask them to fix them.
b) Fix them ourselves. Aaron mentioned that he has done and will do such in the future on a case by case basis.
3. communicate our expectations for this style to each other so we're working with the same aim in mind
In order to properly communicate the artistic needs to developers we need to include not only mockups of new ideas but also simple storyboards which explain interaction ideas (the organic building blocks from part 1).
Once an idea is "ready for coding" the artists need to include the mock-up and storyboard as well as precise details on the placement, size, and coloring, gradient definitions, et cetera, of all elements as well as any other information deemed useful.
In certain cases, including screenshots of gradient information taken directly from the graphical editorshould/could be very usefull. This information needs to be very fine, as Boemann put it "he wants truedecimals" :-) Using a copy/pasted and much simplified information cut from an SVG will be very useful here.
----
So that is what happened, as best I can remeber :-) Things are finally rolling along. Oxygen is really close to a first release and all is well.
Ohhh...almost forgot: you can get all this warm-goodness in the kde-svn/playgound/artwork/Oxygen
So here is what it was all about
1. Explicit division of labour (e.g. who's doing what)
Boemann has been and will be working on code. Ruphy will help on this as well.
Zack and Aaron will help both by fielding questions/issue as well as probably contributing code (see below).
Pinheiro and Eriolloan will keep making the artwork.
Ken will help with disseminating artwork information as well as trying to coordinate things.
Zack would like to see graphical side of things build from blocks. He'd like most effects in kde4 based on an actual physical model - that's what will give them organic nature. For that we need an image manipulation framework that does animations and physics engine connected to it. Zack has code
started on each of those elements.
2. Communication between artists and coders
We need to put everything in reach of the public in order to gain as much support as possible and to avoid bitterness from all sides. With things out in the open we can move as quickly as possible without any deterrents or wasted time/effort.
In addition, we will soon experience a problem with our style/windec and certain applications which do not behave well. This information needs to be attained as well as acted upon. By having a central place for code people can test it.
Once we know which problems are occurring we can do one of two things:
a) Let the developer in question know of the problems and ask them to fix them.
b) Fix them ourselves. Aaron mentioned that he has done and will do such in the future on a case by case basis.
3. communicate our expectations for this style to each other so we're working with the same aim in mind
In order to properly communicate the artistic needs to developers we need to include not only mockups of new ideas but also simple storyboards which explain interaction ideas (the organic building blocks from part 1).
Once an idea is "ready for coding" the artists need to include the mock-up and storyboard as well as precise details on the placement, size, and coloring, gradient definitions, et cetera, of all elements as well as any other information deemed useful.
In certain cases, including screenshots of gradient information taken directly from the graphical editorshould/could be very usefull. This information needs to be very fine, as Boemann put it "he wants truedecimals" :-) Using a copy/pasted and much simplified information cut from an SVG will be very useful here.
----
So that is what happened, as best I can remeber :-) Things are finally rolling along. Oxygen is really close to a first release and all is well.
Ohhh...almost forgot: you can get all this warm-goodness in the kde-svn/playgound/artwork/Oxygen
Subscribe to:
Posts (Atom)
