|
| This Week... |
|
Work begins on 3d molecule visualisation features for Kalzium. More progress in the Kopete "OSCAR (AIM) File Transfer" and "KDevelop C# Parser" Summer Of Code projects. An enhanced version of the custom iconset developed during the 1.4 phase is re-enabled as the default option in Amarok. Following the brand clarifications of last week, oKular is now known as okular. Kitten is renamed Strigi. Two security issues are addressed.
|
Carsten Niehaus writes about the rapid progress himself and Benoît Jacob are having in implementing 3d visualisation features in Kalzium:
|
In the last couple of days, Kalzium has gained a new feature: a 3d molecule viewer. By taking advantage of OpenBabel 2 (a cross-platform framework to load and process chemistry file formats), Kalzium can read virtually any 3d chemistry format, for example .cml. These screenshots show rendered molecules, and in the second image, with a Carbon atom highlighted. This exciting new feature uses OpenGL. If you don't have a graphics card with 3d support, molecule rendering falls back to using MESA, which still performs very well.
In the coming week, Carsten and Benoît will be working on a lattice-viewer which will reuse most of the current moleculeviewer code.
|
|
The Amarok developers reflect on the KDE 4 Multimedia Meeting that took place 3 weeks ago:
|
The KDE multimedia meeting was an invaluable asset to the Amarok development team. It provided us with an optimal environment for meeting each other, having fun and developing effective roadmaps and understanding of the directions which we will take in the future.
Allowing the development squad to meet in a central location for a continuous amount of time was excellent. This has without a doubt strengthened our bond as co-developers, and fuelled great enthusiasm and motivation to work on the project.
Some of the technical achievements which occured include:- Substantial optimisations in the Context, Playlist and Media browsers
- Usage of iNotify technology
- Script manager UI changes
- Beginnings of a port to the new Qt4 api
- Major user interface redesigns
- Brainstorming of future, cutting edge technologies
These achievements would not have been possible in such a short period of time without the ability to discuss changes with those developers sitting beside each other. It was possible to sketch interfaces, create algorithm designs and decide upon appropriate design patterns in group meetings and each developer was able to provide personal opinions and feedback.
One of the highlights of the meeting was a substantial and thorough hour long discussion about the direction which we, as developers, should take. This forum included past experiences, future developments (Amarok 2.0, and general design methodologies), licensing, plugins, bugs, quality management and a host of further topics. This meeting no doubt exceeded anybody's expectations. Smoothly run, hassle free and productive - surely there could be no better way to create an effective environment for programming!
|
|
File indexing and searching, which is sure to be a central component of future desktops, has been bolstered in the KDE scene with the emergence of Strigi, which is now another viable option besides Kat, which has seen a slowdown in development pace as of late. Strigi, which is the new name for Kitten, and has been strongly developed in the past several weeks. Jos van den Oever announces version 0.3.0 this week:
|
The core code of Strigi is has no dependencies on KDE libraries. Only the GUI and the pluggable file analyzers (to come) will have these dependencies. Hopefully this will mean that strigi will be attractive to other desktop environments as well.
Right now, i'm attempting to add loadable modules for indexing files. After that, we will be working on GUI improvements, to improve the slightly rough state from a user point of view.
|
|
Egon Willighagen, another developer involved with Strigi, offers another perspective:
|
Now, Strigi has come along, with a fast indexing engine, just the thing where the Kat developed seemed to have stopped. The design is different from that of Kat, but it does not seem unlikely that Kat code can be ported. No support for PDF or OpenOffice.org documents yet, but that's really the easy part, and kfile is on its way.
One might wonder how Strigi could implement Tenor concepts. A simple approach is at least to allow users to tag files, just like we have become used to with blogs (e.g. Technorati.com) and websites (e.g. Connotea). This could be easily implemented using extended attributes (xattr), already used by Beagle.
My argument to use this, instead of putting these things in the Strigi database itself, is persistence: data and metadata are kept together. KDE's file properties dialog would be extended with an extra tab that allows editing these fields.
Strigi itself can be embedded in KDE applications to search specific information (e.g. search molecular data within Kalzium using the InChI), and even in the FileOpen dialog. We need patches for KDE 4 that allows this, soon.
|
|
And by the way, if you were wondering where the name "Strigi" comes from: Strigiformes is Latin for Owl, a bird that has excellent vision, particularly in low light. So, now you know!
|
|
| Statistics |
|
Commits: |
2404
by 184
developers, 5439
lines modified, 1662
new files. |
|
Open Bugs:
|
12666
|
|
Open Wishes:
|
11100
|
|
Bugs Opened:
|
275 in the last 7 days. |
|
Bugs Closed:
|
266 in the last 7 days. |
|
|
Commit Summary |
|
Module
|
Commits
|
|
/trunk/KDE |
|
|
/trunk/www |
|
|
/trunk/l10n |
|
|
/branches/stable |
|
|
/trunk/extragear |
|
|
/trunk/playground |
|
|
/trunk/koffice |
|
|
/branches/work |
|
|
/branches/KDE |
|
|
/trunk/kdenonbeta |
|
|
|
Lines
|
Developer
|
Commits
|
|
|
Laurent Montel
|
|
|
|
David Faure
|
|
|
|
Thomas Zander
|
|
|
|
Pino Toscano
|
|
|
|
Frans Englich
|
|
|
|
Dirk Mueller
|
|
|
|
Yukiko Bando
|
|
|
|
Carsten Niehaus
|
|
|
|
Allan Sandfeld Jensen
|
|
|
|
Ludovic Grossard
|
|
|
|
|
Internationalisation (i18n) Status
|
|
|
Bug Killers and Buzz |
|
Bug Killer
|
Number Of Bugs Closed
|
|
Alexandre Pereira de Oliveira
|
|
|
Olivier Goffart
|
|
|
Thiago Macieira
|
|
|
Allan Sandfeld Jensen
|
|
|
Tommi Tervo
|
|
|
Kevin Ottens
|
|
|
Mark Kretschmann
|
|
|
Andrew Walker
|
|
|
Seb Ruiz
|
|
|
Maks Orlovich
|
|
|
|
Program |
Buzz |
|
Amarok |
|
3424 |
|
|
Kopete |
|
|
1354 |
|
|
K3B |
|
|
Kate |
|
|
KMail |
|
|
SuperKaramba |
|
|
KDevelop |
|
|
Kontact |
|
|
Kicker |
|
|
aKregator |
|
|
|
Person |
Buzz |
|
Aaron Seigo
|
|
|
333
|
|
|
George Staikos
|
|
|
332
|
|
|
Waldo Bastian
|
|
|
317
|
|
|
John Tapsell
|
|
|
295
|
|
|
Jonathan Riddell
|
|
|
293
|
|
|
Anne-Marie Mahfouf
|
|
|
285
|
|
|
Boudewijn Rempt
|
|
|
260
|
|
|
Stephan Kulow
|
|
|
241
|
|
|
David Faure
|
|
|
241
|
|
|
Zack Rusin
|
|
|
235
|
|
|
|
|
|
| Contents |
|
|
Bug Fixes |
Features |
Optimise |
Security |
Other |
|
Accessibility |
 |
|
|
|
|
|
Development Tools |
|
![[*]](/images/standard/features) |
|
|
![[*]](/images/standard/other) |
|
Educational |
![[*]](/images/standard/bugfixes) |
|
![[*]](/images/standard/optimise) |
|
|
|
Graphics |
|
|
|
|
|
|
KDE-Base |
|
|
|
![[*]](/images/standard/security) |
|
|
KDE-PIM |
|
|
|
|
|
|
Office |
|
|
|
|
|
|
Konqueror |
|
|
|
|
|
|
Multimedia |
|
|
|
|
|
|
Networking Tools |
|
|
|
|
|
|
User Interface |
|
|
|
|
|
|
Utilities |
|
|
|
|
|
|
Games |
|
|
|
|
|
|
Other |
|
|
|
|
|
|
|
Bug Fixes |
|
Educational |
|
Jason Harris committed changes in /trunk/KDE/kdeedu/kstars/kstars:
|
Committing changes from James Bowlin to fix a rendering bug.
Constellation lines were disappearing at high zoom when one of the
endpoints was far off-screen. This patch uses interpolation to truncate
the constellation line at the edge of the visible skymap.
Thanks James!
|
|
|
|
|
|
|
KDE-Base |
|
Helge Deller committed changes in /branches/KDE/3.5/kdebase:
|
submit patch by Jahshan Bhatti to fix Bug 47242:
JJ: CDROM info not available from Control Centre
Thanks a lot Jahshan !!
FEATURE: 47242
|
|
|
|
|
|
|
|
|
|
|
Alexandre Pereira de Oliveira committed changes in /trunk/extragear/multimedia/amarok/src:
|
More patches by Markus Kaufhold (Thanks!):
- When playing a CD, show "Starting CD Audio track...", instead of "Connecting to stream source...";
- On Track Information Menu, show "CD Audio" for CD tracks, instead of "Remote Media";
- Disable inline editing for CD Audio Tracks.
BUG: 127881
|
|
|
|
|
|
|
|
|
|
|
Features |
|
Development Tools |
|
Jakob Petsovits committed changes in /branches/work/kdevelop-pg/examples/csharp:
|
A full pre-processor for the C# parser.
There is now a seperate pre-processor parser (csharp_pp) that works together
with the lexer so that the main parser only gets to see real tokens, with
no disruption from the pre-processor.
This commit also throws out the parser class's i/o actions from main.cpp
into a seperate, to-be-adapted-to-the-framework file called csharp-io.cpp.
So much for the foundations, now I can start with the actual C# grammar... |
|
|
|
|
|
|
Educational |
|
Jason Harris committed changes in /trunk/KDE/kdeedu/kstars/kstars:
|
Adding user option to toggle Antialiasing on/off. Eventually, this will
be set via the Options window, in the Advanced tab. However, that tool
is still not functioning, so for now I am binding it to the "A" key.I had said on the mailing list that I was not going to keep the
integer-pixel draw functions, because they weren't much faster than the
floating-pixel equivalents. After looking at it again, the
integer-pixel draw functions are 20-40% faster than their floating-point
counterparts.
So for now I am going to commit the changes that include
using integer draw functions when antialiasing is off.Also, I have fixed the problem where star colors get saturated when
antialiasing is turned off (this was noticeable before while the sky was
in motion). The problem was caused by the fact that the colored rim of
star images cannot be less than 1 pixel wide without antialiasing. I
solved it by keeping the width at 1 pixel, but desaturating the color of
the rim by an appropriate amount. It works pretty well.Related API change: I removed some arguments from fromScreen() and
toScreen(), because we were just passing around things like
Options::useAltAz(), which are already accessible from within any
function. We still need to pass a "bool useRefraction" to toScreen, but
this should almost always be left at its default value (true), which
actually means "adopt whatever Options::useRefraction() is set to". The
exception is the Horizon; these points must never be refracted, so we
pass "false" to the argument, which means "ignore
Options::useRefraction(); don't refract the point".There's also some code in this commit related to adding XYZ support to
SkyPoint, but nothing yet that you'll notice unless you look at the
code. |
|
|
|
|
|
