Irc-Unix.net

Ok, just a quick update on what we are doing / have done the last two days except drinking beer and eating quite a lot of food (though it never seems to be enough somehow….)

• Apol was polishing CMake support, speeding up KDevelop startup time when you enabled the QtHelp plugin, making sure that Kross plugins get loaded properly and some other things
• Adymo started some refactoring of Sublime in an experimental branch (actually they had quite a long discussion right now about things in the UI which should be changed/fixed). Besides that he also fixed some little bugs in the includepath resolver for CMake
• Nsams is fixing PHP support and adding new features here and there. Esp. completion inside a foreach over a Iterator class works now!
• and as always ZWabel did fix quite a lot of bugs, most of them which only were discoverable in a few corner cases, very nice indeed.
• shaforo who sadly already left us again to attend university fixed the sorting in the Project view among other things
• With Apols help I managed ...read more...

This is the follow-up to what I wrote before: hue subdivision for mortals.

Seems everyone echoes my sentiment: increasing the coverage area of green is not the right way to go. The easiest explanation is as follows. Since this is an additive color model, due to the higher sensitivity of green, its contribution to other primary colors should be reduced. Effectively, this means we should shrink the green region in the color wheel:

For the "Mortal" version in the above picture, I modified the conversion from hue to RGB (assuming fully saturated color), because I discarded the idea of curve-fitting to map the angle to the hue value. Another change is that I gave up keeping the triangle of the primaries, i.e. while 0 is still red (as an arbitrary reference), 0.333 is not green anymore. The actual position of a color component is now determined by the inverse proportion of its part to the grayscale function. I arrive at 26% red, 17% green, and 57% blue. Unsuprisingly, it means blue ...read more...

So Kopete got two slots for this year’s SoC. Tiago Salem Herrmann will be working on improving the MSN support and Pierre-Alexandre St-Jean will be working on turning the chatwindow into a library.

Congratulations to Tiago and Pierre-Alexandre and thanks to all other students that submitted proposals to Kopete SoC!

PS: For the ones that didn’t get accepted but still want to work on the projects, just send a mail to the Kopete mailing list and we will try to help mentoring the work.

1. the number 6 is a project specific detail and should not be pushed on every project because it won't fit every project (Mark notes he works on projects with 1, 3 and 6 month cycles; other cycle are also possible, of course); what we're really talking about it timed releases made with a relatively high level of consistency


2. The discussion is often coupled with the idea of coordinating different projects to the same cycle, which is really a different sort of conversation altogether with "length of the resulting release cycle" being an implementation detail within it


3. it's only one half of the equation, with the missing half being the non-high-level-of-consistency-time-interval releases; too often it was an either/or discussion where if you were doing one you couldn't have been doing the other

...read more...

The question in the title pertains if you use kdesvn-build. kdesvn-build creates a separate log directory for every single run it makes. If you’ve done a lot of kdesvn-build runs and you’ve never manually cleaned out your log directory you’ve probably got quite a few hundreds of log bundles.

Someone finally noticed and filed a bug. Attached to that bug is a patch I’ve created to remove all log directories but the ones referenced in the latest kdesvn-build run for a given module. I consider this the correct behavior so at this point I’m not looking to make it optional or require a magic incantation to Do the Right Thing.

So, if you use kdesvn-build I’d recommend trying out the patch (always use –pretend first!). If you want to skip straight to pruning directories you can use a command like kdesvn-build --no-svn --no-build --no-install kdelibs (replace kdelibs with a module in your rc file). Also, does anyone have a reason to retain more log directories than those in log/latest? (And has a reason that you can’t ...read more...

The use of HSV/HSL color space is obvious when we need to have several colors distributed in an optimal way, colors as unique as possible. For example, SpeedCrunch uses it to autogenerate the colors used for the syntax highlighting feature. The details behind its algorithm was already described by Helder in his Qt Quarterly article Adaptive Coloring for Syntax Highlighting. Basically we use the color wheel and subdivide the hue into equal parts. Primary additive color components are red, green, and blue. This distributes the colors in maximum angular distance with respect to the hue values.

So far so good. However, it was known that human eyes are generally more sensitive to green than other colors. In computer graphics, this is often manifested in the grayscale function, i.e. the function that converts RGB to a grayscale value. Take a peek at Qt's qGray(), it gives the red, green, and blue the weighting factors of 11, 16, and 5, respectively. Shall we take this into account ...read more...

"WebKit is an application framework that provides a foundation upon which to build a web browser.

Just like all the other cool KDE projects Amarok did of course also get their share of excellent students for GSoC this year.

• Teo Mrnjavac will make the playlist rock after having worked on tagging during last year’s Season of KDE.
• Sven Krohlas will give us some unit testing goodness to find all those nasty bugs before a user gets to see them.
• Alejandro Wainzinger will make sure our media device support will make people happy.

I am sure you’ll do awesome work! I hope I can soon add the names of those who are going to take part in Season of KDE (and another super cool thingy we arranged which I can’t yet talk about) to this list.

Thanks to Google for running GSoC and making this possible.

Linked by Thom Holwerda on Sat 5th Nov 2005 17:51 UTC, submitted by AdriAn Avila Rumors circulating that Novell is going to kill off its popular Linux desktop lines are completely false.

"Red: Thanks, Ken. The energy in this place is truly amazing! These two industry giants intend to settle the score once and for all, and only one can hold the title of Universal Linux Window Manager.

Topics: Personal, FOSS, KDE

Another month has passed without a blog post. My new year’s resolution is an epic fail. Luckily, the rest of my life didn’t follow suit. Since I’m trying not to beat around the bush, I’ll get straight to the point. This post will be all about Yakuake, specifically the cool new features you’ll be seeing in the next release.

First up is moving/rearranging tabs using drag and drop. Click and hold on a tab with the left mouse button (or right mouse button, if you’ve reversed them) and drag and drop to the desired location. Drop indicators will appear on the tab bar, indicating where you’re allowed to drop a tab. People using tabs in Konsole might be familiar with this behavior.

You can now prevent tabs (formally called “Sessions” in Yakuake) from being closed. You can do this through the tab’s context menu (right-click on the tab name) and setting the “Prevent Closing” option. If you try to close that tab, you will ...read more...

I've seen superlative after superlative concerning the release of Firefox 3.0 , and in all honesty, it is making my stomach ache.

There will be some new weather providers coming soon. I am currently working on adding a Netherlands source (current conditions only provided free). Someone is working on a German source and I plan on adding 7 day forecast info to the NOAA provider hopefully soon.

Just be aware, I do read what's out there from googleland and yes we do need more weather providers for you folks complaining
As for using Marble, I'd like to, as NOAA provides .kml files which would make radar display very nice to have. But I'm only one person you know, help me out and things happen faster!

Thanks to aseigo, we have Solid Network awareness support for the dataengine.

Thanks to Petri Damst

Userbase is the wiki for application user information. It fills in a vital gap of information between traditional documentation and the usually too technical developer chatter. For at least KOffice it’s still in need of help, though. We want more tutorials for starters.
People like Anne Wilson have put a tremendous amount of work into userbase and I’m especially happy with the work on KWord she did. Userbase is for and by users, though. So we need help.

Tutorials are in my experience the best way to get a new user starting with the application, get them over the initial threshhold if you may. Its also the easiest way to teach that new useful feature you like to others that may want to use it too. Spread the joy kind of way.
With the Release Candidate of KOffice2.0 out I want to call users everywhere to install the packages from their distro and play around with it. When they find something that they think is a “gotcha”, write about it. Put up ...read more...

My mobile phone recently stopped working, I handed it in for repair under warrenty. They fixed it, and flashed it with new firmware, removing all my settings and most importantly, my phone book.

So, dear all of you, please send me a text message with your name if you think you should be in my phone book.

And if anyone has any good backup strategies for phonebook and such of a nokia E71 for linux users, please use the comment field, preferably some thing nice clickyclicky thing that uses Qt4 or kdelibs of KDE 4

One of the most anticipated presentations at this year's KDE World Summit, better known as aKademy , was Zack Rusin's intriguing 'Beauty and Magic for KDE developers'. Zack is a long-time KDE developer who has recently been hired to work full time at Trolltech.

I've read various stories about how people are having problems with the KDE4 compositing effects.

• rsync to a new repo from KDE's rsync server repeatedly until the rsync'ed repository seemed pretty stable. I think that next time it'd be convenient to schedule the last rsync at 4am GMT so that the flux in the KDE repo is low.
• rsync one more time, noting any revs/ or revprops/ files that are changed.
• Use svn info to see if the rsync'ed repo is now consistent -- if it's not, it will typically print something like svn: No such revision 954115.
• Using creativity, think up which revs/ or revprops/ files are missing up to the revision reported by svn ...read more...