To all slicKer fans out there: friedmud writes "A post to KDE-Look 2 months ago spawned the Slicker Project (an ambitious project aimed at a Kicker alternative). With only 2 months behind us the project has come a long way. And now the first shots of all the applets being developed have started to flow in. In addition there is a nice interview with Zakariya (the man responsible for most of the framework) over at TinyMinds. Things are starting to progress faster, so if you are a developer that thinks you might be of use, get on the devel list and start hacking!"
http://www.pclinuxonline.com/modules.php?name=News&file=article&sid=4315 Source code: http://slicker.sf.net/ New updated screenshots here: http://www.umr.edu/~dgaston/ Cool interview of Zakariya here: http://www.tinyminds.org/modules.php?op=modload&name=News&file=article&sid=928&mode=thread&order=0&thold=0 Excerpt from the interview: ------------------------------------------------------------------------------------------------------------- I used to run BeOS and I enjoyed coding for it. It was a beautiful OS, with a beautiful API. But, Be clearly was about to tank so in '99 I faced the decision to either go to Linux or Windows. So, I gave Linux a shot (actually, it took several shots, each time returning to BeOS) and after about 6 months struggling with GNOME development, I decided to give KDE a shot. Back then, GNOME was all the rage and nobody had anything good to say about KDE, especially with regards to the then issue of Qt's being free or not. But anyway, I installed KDE, and it blew my mind. Then, I tried developing for KDE and my mind was blown further ;) KDE's API is actually better designed than BeOS... I had trouble believing it. So, I had printed out all sorts of gnome/gtk tutorials and frankly, after BeOS C++, programming GTK felt like having my eyes torn out by screaming lepers. The API works, but it simply has no elegance; and subclassing your own widgets is a sysiphean ordeal. KDE on the other hand looked like it was actually DESIGNED, as opposed to hacked. And that makes a big difference. Further, I installed kdevelop and realized it was 99% the ide that BeIDE was (for reference, BeIDE was based on code warrior) -- but 99% was more than good enough when my GTK programming was being done in vi and I was writing makefiles by hand. Never again. I can use vi, but I'll take kate or a full IDE any day. Well, if my completely objective reasoning above didn't make it clear ;) I just don't like gtk programming. Further, I like KDE -- it's a great desktop. Finally, KDE provides such an astonishingly mature framework for... well, damn nearly everything I have needed to do; if I were to write this with a different API I'd have had to triple my source code just to get half as much done. For reference, I am a C++ junkie, but I have had *plenty* of C and assembly experience. I'll tell you right now, you can't really appreciate a clean C++ API until you've written C and assembler for set top box MPEG decoders. That was a fun, but terrible job, and it made me look into C++. ------------------------------------------------------------------------------------------------------------- KDE rocks!!! Regards, optimus _ Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph To leave: send "unsubscribe" in the body to [EMAIL PROTECTED] Fully Searchable Archives With Friendly Web Interface at http://marc.free.net.ph To subscribe to the Linux Newbies' List: send "subscribe" in the body to [EMAIL PROTECTED]
