Image 01
profile-image

DarkLord

Dark Lord
kio-locate

Various KDE 1.-4. Improvements by arminstraub 178 comments

> I'm not sure about this. As you can see from your previous posting this may vary from distribution to distribution.

I see, it would only make sense if you worked directly with a distributor to provide kio-locate as a default option somewhere I guess.

>> If it's not possible to actually configure it from there there could be some hints and info about the current configuration and how to change it.

> A section in the help would certainly be nice. I will add it to my TODO list. Maybe a good link would suffice? Any good (easy) docs?

Maybe just a link to man:locate (again the slocate man page is shown in kubuntu, which is ok) would suffice.
I'd suggest putting a smal int on the configuration panel itself though and not only in help. So people just having a quick look about the options still can see that the logic behind it is configured somehwere else.

But actually there's not very much in the man page at all . It doesn't give any idea to look at the crontab or in /etc/cron.daily.

No idea what to do best, maybe some hint about man:locate and crontab in general would be enough, then. If there where a good cron frontend in KDE by default that would be an option, but i don't know about something like that. - Sep 14 2005
kio-locate

Various KDE 1.-4. Improvements by arminstraub 178 comments

> No. An item has to match at least one entry of the whitelist for being displayed (that's what the default entry '.' is for).
Oh, that's interesting. Actually I wouldn't have got that by looking at the interface itself. Probably I'd even remove "." because I thought I put it there unintentionally myself.
As far as I understood it "*" would be the expected symbol for me there, so basically all that matches "*" (= "anything") would be possibly included in the resutls.
Anyway I still could misunderstand this since I don't see a direct practical use of the white list - probably I think in the wrong direction.


> Perhaps the name whitelist is not optimal. What name would you propose?

Not sure if there's a good one-word explanation. A short one-liner what it does might be needed.

>> Are you expected to enter full file names or is it that you just put in somes strings?

> You may enter regular expressions (which by default may match anywhere, but you use something like '^...$' to force a full match).

I suppose this wouldn't match well with a system where you could put in a whole path (to a directory or file), that (including all subdirs) would be exluded from any locate: output? I think that might be useful for some people. maybe. :) - Sep 14 2005
kio-locate

Various KDE 1.-4. Improvements by arminstraub 178 comments

Oh I forgot:
would it be possible for the locater:config dialog to include configuration of locate / slocate (whatever's used) itself?
User's might preceive the locate: kio slave to be the same with the locate idea in general and expect any configuration there. So one could see (and change if necessary) all necessary settings, like when and maybe how the database is refreshed.

If it's not possible to actually configure it from there there could be some hints and info about the current configuration and how to change it.

Cheers,
Chris - Sep 13 2005
kio-locate

Various KDE 1.-4. Improvements by arminstraub 178 comments

Thanks for this nice app, it's really something that makes the whole kio concept (available everywhere) shine.

Here's a bit of feedback:

In the config dialog it's possible to change the command used. But the hint doesn't really apply at least on Kubuntu. Here locate is a symlink to slocate already. No harm done really but it's just confusing maybe, for those who don't know =)

The blacklist and whitelist features. If I understand them correctly the blacklist will contain elements that would never come up.
But the whtielist (by it's name) would mean those items always come up?

Are you expected to enter full file names or is it that you just put in somes strings? If the first is the case maybe a file-open dialog would be appripriate.
In any case some short informational text would be nice - and maybe some more using the "?" What's this feature tooltips as well.

Keep up the good work!

Cheers,
Chris - Sep 13 2005
Amarok

Audioplayers by amarok 574 comments

... but I can't resist to state that the screenshots as presented here make amaroK look worse than it actually is.

They are seemingly done in fullscreen and even on a 1280x1024 screen (which I assume is the resolution of the screenshots) I have to scroll to see everything.

It's just that I assume most people wouldn't ever want a music player that *has* to be used in a fullscreen mode. Normal operation for most music players and what most people expect or like seems to be a rather small window - maybe 1/4 of the whole screen.

The shots make amaroK look like it's not usable in such a way. Which I think isn't good at all.

Cheers :o) - Aug 15 2005
KBFX Silk (KBFX 0.4.9.3.1)

Various KDE 1.-4. Improvements by sirajr 613 comments

Actually I think it's a good idea. Having a "Menu" or "KDE" written on the button makes it easier to understand for new users, that this is 'the place' to have a look when they want to start something.

And it's easier to explain, when someone can press the "KDE" button, when it's written on the thing, than telling them to launch the K-Menu the way it is now.

Though I do not like the default theme, there has been a nice "Linux" and "KDE" theme here on the site, that makes it look pretty good =) - Jul 08 2005
KSystemLog

System Software by lastnico 117 comments

Nice :)

Just had another look to find the 'missing' logs on Kubuntu (boot,cron, cups web), but couldn't hmmmm. Ah well, it's still a very usefull app, thanks again. - Jun 27 2005
KSystemLog

System Software by lastnico 117 comments

Hmm, didn't find those logs either.

But anyway it's great to see this kind of reaction (and so fast); I really like this with open source :)

Btw. I did post to the kubuntu-dev mailing list - hope both of you don't mind that - maybe somebody there might help out with the information about cron and acpi logs needed.

Cheers,

Chris - Jun 24 2005
KSystemLog

System Software by lastnico 117 comments

I just tried out your nifty little tool - it's really something I've been looking for some time now, so thanks a lot!

Anyway I was about to send a mail to the Kubuntu list about the possibility to include this in the next release. But the I figured out, maybe I'm better of talking to the upstream developer first :)

Here are two minor things I'd like to suggest:

- Make "Details" the default action for double-clicking an entry - I guess some might expect exactly this.

- Have the "Log-Toolbar" visible by default, so user's don't have to go into a sub menu to change the log they're viewing.

Ok, these are only small things and maybe it's just my taste to expect it this way - don't know.

But unfortunately with the Kubuntu packages some logs don't work for me out of the box. For Example the kernel logs. The kernel logs aren't found where KSystemLog expects them (/var/log/kernel/info and so on), but at /var/log/kernel.log - so there's no seperation between warnings, infos and errors.

Would it be possible to modify the kubuntu package accordingly? Maybe the Kubuntu devs would really like this to be part of the next release - I do not know yet, but I'd definitely appreciate it.

Instead there is - Jun 24 2005
Virtual Filesystem

Various KDE 1.-4. Improvements by meneerdik 30 comments

Ok, but those "true beginners" won't be just that forever - even the slowest learner around will eventually become a more andvanced user over time and such a change is just too unusefull for anyone with the slightest idea of what "home" actually might mean, and that this IS the place to be on your filesystem... and it's not that hard to guess if you ask me.

Seriously, home beeing the start point for... well, everything makes it even more understandable to new users.
What else? A big fat STORE YOUR STUFF HERE sticker? I don't think that's needed.

Moving away from that only stirrs confusion as to why people shouldn't have all their data messed around their whole FS. - Jan 21 2005
Improving KDE

Various KDE 1.-4. Improvements by andrunko 313 comments

it's you ;)

No seriously I think it doesn't get in the way normally and we have the option here to make the trigger time a bit higher than it is in windows.

But I think this should be done just like it is in K3B. You can try it when you create a data project in the lower pane - it's not possible in the filesystem browser (upper pane) in K3B.

I suppose this feature would have to be in QT for this - which is what I'm suggesting.
I don't think it's very hard to do and could even be taken from K3B itself.

So the only question is IF we want it and IF someone is gonna do it.

I really think it doesn't get so much in the way as it could be usefull... think of it like this:

The only real-world situation where you would trigger it would be when you do a double-click (to open something) too slow.

- *with* this feature you would trigger the rename function and see "oh, that's not what I wanted". You click somewhere else and try to doubleclick again

- *without* this feature a doubleclick done too slow will just do - nothing. So instead of an immediate response you wonder why nothing happens.

Actually I do not think that the first option (with the feature) would result in a higher loss of time, when what you actually want to do is double-click something.
Reason for that is that the moment when nothing happens ("hey, what's that? it doesn't open?!") is just as long to humans as the immediate response (triggering the rename operation) including the workaround to click some other location to try again.

Ok, I suppose that this explanation is complicated to understand, but I re-read it and think it says what I mean - maybe some clever guy (or girl) comes around, thinks the same and implements it.

It's not "da-killer" feature but it's one o those niceties that make KDE so much more usable than other systems... erm, well kind of :) - Dec 01 2004
Improving KDE

Various KDE 1.-4. Improvements by andrunko 313 comments

Not sure if I already suggested that somehwere, so here we go:

Maybe you could add a patch to KDE (since you asked for ideas ;)) that enables users to rename files by clicking a file two times (non-doubleclick) similar to what windows does. K3B actually already allows this afair so it would only be logical to have this in Konqueror and all of KDE as well.

:) - Nov 30 2004
Lipstik

KDE 3.5 Themes by PaT 347 comments

Here's my current deb for 0.5:
http://www.deadhand.com/kde-debian/lipstik_0.5-1_i386.deb

It's a normal dh_make / dpkg-buildpackage deb. - Nov 28 2004
Improving KDE

Various KDE 1.-4. Improvements by andrunko 313 comments

Hmm, can't find the option to disable the new rubberband right now.

But about the hack (and is a hack, an ugly one) to remove the lines in the status bar - I thing andrunko shouldn't include this in these "improvements".
Application developers put those lines there for a reason and in many cases they are a visual help. Konqueror might not make very good use of the status bar lines, but in other cases they make a lot of sense, so it should NOT be done anything about it within the _style_. If at all it should be changed inside the application. - Nov 27 2004
OpenOffice.org Writer

Office Apps by kendy 34 comments

Well, for starters not everyone has the time, ressources or intention to use Gentoo Linux... - Nov 26 2004
Lipstik

KDE 3.5 Themes by PaT 347 comments

Hi,

I like the modifications made to Plastik. Though I'm not a fan of Active Heart I like the inverted gradients a lot - if nothing else than it's at least a fresh look :)
Only Just noticed that the status bar frames are gone. Looks good in Konqueror (file manager) but a bit awkward in ... Konqueror (web-browser). This is because in the file manager there is some text in the status bar normally, so the space is in no case unused. While webbrowsing I have mostly no text in the statusbar and it looks a bit strange - as if it shouldn't be there at all. Hmm not sure, but one thing about this is that I think this should be a change done in Konqueror, not in Plastik - because maybe (you never know) there is some application that uses those lines for good reason and doesn't work well with Lipstik because of that.

Btw. I'm glad you gave this another name instead of providing a patched Plastik.

The only other thing I don't like and think might confuse some are the fewer dots for moveable items. There are elements with jusst two or three dots and I don't think new users will know that these are 'handles'.

Nice work on the bigger slider-handles. (contrary to what I've said before ;))


Oh, almost forgot:
I made a debian package of the style and it is available here:
http://www.deadhand.com/kde-debian/kwin-style-lipstick_0.3-1_i386.deb

(for the moment just grab it directly - it's not in the repository right now) - Nov 26 2004
Improving KDE

Various KDE 1.-4. Improvements by andrunko 313 comments

As far as I remember you can disable the rubberband-effect specifically in KControl. Go to Style -> Effects and have a look at the Options under "Enable GUI Effects".
Be sure that "Enable GUI Effects" IS selected, otherwise you will have the new rubberband enabled.
I already mailed andrunko with this bug ("Enable GUI Effects" = OFF should mean to use the simple rubberband).

The debs on deadhand with the kalyxo ending are based on the 0.5.5 version of the patch and KDE versions are:
kdebase_3.3.1-2
kdeartwork_3.3.1-1
kdelibs_3.3.1-1
qt-x11-free_3.3.3-5

Have fun :) - Nov 22 2004
Debian Service Menu

Dolphin Service Menus by redclay 13 comments

Hmm, I had an alien service menu somewhere. Not sure if it was from here or if I did it myself - I'll have a look sometime next week. But anyway: This would make some sense for inclusion, though it will annoy those who whole-heartedly dislike rpm packages and only use deb (sometimes you can't, I know). - Nov 21 2004
Virtual Filesystem

Various KDE 1.-4. Improvements by meneerdik 30 comments

Doesn't take a hall full of usability experts to see this is a good idea overall - something that the immensely powerfull yet mostly unknown KIO Slaves actually *need* in my opinion.

But just to point this out directly: Making "locations:/" default instead of home is a bad bad thing. "normal users" (those who would not and should not need to know how to change the default back to "file:/home/user") will have to (read: should) work inside their home directory 90% of the time they open their "File Manager".

That said there should be a easily viewable and accessible icon on the desktop saying something like "Locations" or "Start Here" (oh.. that's another DE ;)). - Nov 14 2004
Improving KDE

Various KDE 1.-4. Improvements by andrunko 313 comments

Since andrunko didn't get around to add this yet here's the link to my debs of KDEbase, KDElibs and qt-x11-free with these patches:
http://www.deadhand.com/kde-debian/

There are all the debs that get build from those packages and you definitely don't need all of them - I have yet to sort out which ones are definitely needed and which ones aren't.

Common sense should help here though, since most probably won't need the doc or devel packages ;)


Another thing to keep in mind is that the kdebase version is 3.3.0a (with which the patches have been tested) and not version 3.3.1 that is only just now (short time after i build the packages) in debian unstable. So if that's what your're using keep a look out for the dependancies and keep in mind that apt-get upgrade will upgrade kdebase too :).

I will talk to andrunko about a better way to provide the debs in the future and maybe have a little repository for your convenience. But that's the future and depends on what KDE will do - if there's KDE 3.4 in two weeks (no, it won't) and it includes all the patches there's no need for such a repository, is it? ;)

For now I hope some of you can enjoy my packages - please note though that I won't be building new ones for about two weeks, so if something new happens here I'll see to it at the end of the month.

Cheers all,

Chris - Nov 12 2004
LaptopConfig

System Software by appy 5 comments

haven't been able to really test all the settings yet, but it looks pretty good to me already. One thing is that i'd rather have this under System Administration in KControl than as a seperate program - I believe I have read something like this before but can't find it right now. Actually it might make real sense to keep the dependencies for this low and make it usable for the GNOME and alternate folks as well, though. :-/

On thing:
I went to your site with the intention to fetch the sources and build my own .deb - which is a bit of work and iexplains why I did not test it before. I was of course pleased to see a .deb readily available. A simple click on "download" would have tought me that as well - but maybe a little remark that there is a download site behind "download" with rpm and deb instead of just the source would bring this to other's attention as well.
Alternatively you could add rpm, deb and the others as seperate downloads here and make sure than anyone as stupid as me sees what's available ;) - Nov 04 2004
kio_rar

System Software by rgfernandes 37 comments

I hope you keep up the work on this - seamless integration of rar and ace (like tar and zip already have) would really improve KDE for many users.

Btw. if you're using Debian (well, it could bem right? :)) you might possibly want to talk to the kalyxo guys - I'm sure your package (if you decide to make one) will fit nicely into their repository. You'll reach quite a few users this way. - Nov 02 2004
Improving KDE

Various KDE 1.-4. Improvements by andrunko 313 comments

Unfortunately my tries to build some nice deb packages have not been fully succesfull. WHile I build and even uploaded kdeartwork and kdelibs succesfully (at least I think so) there seems to be no use as long as qt and kdebase are not compiled correctly - nd that didn't work for me.

Thanks andrunko for the tips about kdelibs btw - compilation did finished when I placed the diff in /debian/patches but it seems that it didn't get applied.. or something else is missing (qt is) - anyway the new stuff doesn'T seem to be there.

Don't have enough free time to look into this now, but no matter if andrunko provides debs or not I'll be sure to get this to work for me =) - Oct 28 2004
Improving KDE

Various KDE 1.-4. Improvements by andrunko 313 comments

Argh... now I succesfully compiled kdelibs and kdeartwork with the patches (vanilla sources) and get an error with kdebase after an hour of compilation:

Can somebody helb me please?

/bin/sh ../../libtool --silent --mode=link --tag=CXX g++ -Wnon-virtual-dtor -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -Wall -W -Wpointer-arith -Wwrite-strings -DNDEBUG -DNO_DEBUG -O2 -Wformat-security -Wmissing-format-attribute -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -D_GNU_SOURCE -o libkonqsidebarplugin.la -rpath /usr/lib -version-info 3:0:2 -L/usr/X11R6/lib -L/usr/share/qt3/lib -L/usr/lib -no-undefined -Wl,--no-undefined -Wl,--allow-shlib-undefined konqsidebarplugin.lo -lkparts
/bin/sh ../../libtool --silent --mode=link --tag=CXX g++ -Wnon-virtual-dtor -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -Wall -W -Wpointer-arith -Wwrite-strings -DNDEBUG -DNO_DEBUG -O2 -Wformat-security -Wmissing-format-attribute -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -D_GNU_SOURCE -o konq_sidebar.la -rpath /usr/lib/kde3 -module -avoid-version -module -no-undefined -Wl,--no-undefined -Wl,--allow-shlib-undefined -L/usr/X11R6/lib -L/usr/share/qt3/lib -L/usr/lib konq_sidebar_la.all_cpp.lo -lkparts -lkio ../../libkonq/libkonq.la ./libkonqsidebarplugin.la -lkutils
make[5]: *** Keine Regel vorhanden, um das Target »move_konqsidebartng_entries.sh«,
benötigt von »all-am«, zu erstellen. Schluss.
make[5]: Verlasse Verzeichnis »/data/kdebuild/kdebase-3.3.1/obj-i386-linux/konqueror/sidebar«
make[4]: *** [all-recursive] Fehler 1
make[4]: Verlasse Verzeichnis »/data/kdebuild/kdebase-3.3.1/obj-i386-linux/konqueror/sidebar«
make[3]: *** [all-recursive] Fehler 1
make[3]: Verlasse Verzeichnis »/data/kdebuild/kdebase-3.3.1/obj-i386-linux/konqueror«
make[2]: *** [all-recursive] Fehler 1
make[2]: Verlasse Verzeichnis »/data/kdebuild/kdebase-3.3.1/obj-i386-linux«
make[1]: *** [all] Fehler 2
make[1]: Verlasse Verzeichnis »/data/kdebuild/kdebase-3.3.1/obj-i386-linux«
make: *** [build-arch-stamp] Fehler 2


I really want to get this done.
After that I will look into compiling qt, but for today it's enough. Hope somebody can give me a hint.

Thanks! - Oct 26 2004
KDE UI Tweaking

Various KDE 1.-4. Improvements by PaT 10 comments

Hurray for 2a, 2b and 3...

With 1. I'm not so sure. I think the (small) sliders are meant to be the way they are and could look out of place in many areas if made bigger. I kinda think it's a misuse to use it in playbar style areas, where it's moving without user interaction. But I think there might not be the right sized widged around these days (a 1cm long bar that would be), so the devs are forced to use this type of slider. - Oct 26 2004
Improving KDE

Various KDE 1.-4. Improvements by andrunko 313 comments

andrunko, do you have a close look as to which feature depends on what package to be patched?
I ask because it's proven troublesome for me to compile qt-x11-free, while kdelibs works (have yet to see kdeartwork and kdebase work) - so the less I need to patch the better =) - Oct 26 2004
Improving KDE

Various KDE 1.-4. Improvements by andrunko 313 comments

Sorry but doesn't look like I will be providing debs soon.

Guess I'm doing something wrong, but after patching debian's qt-x11-free and starting the deb creation via
dpkg-buildpackage -rfakeroot -uc -b

I get (after a lengthy compilation process):

freetype2 -I../../../../include -I.moc/release-shared/ -o .obj/qsql_odbc.o ../../../../src/sql/drivers/odbc/qsql_odbc.cpp
../../../../src/sql/drivers/odbc/qsql_odbc.cpp:61:1: Warnung: »SQLLEN« redefiniert
In Datei, eingefügt von /usr/include/sql.h:91,
von ../../../../src/sql/drivers/odbc/qsql_odbc.h:72,
von ../../../../src/sql/drivers/odbc/qsql_odbc.cpp:37:
/usr/include/sqltypes.h:139:1: Warnung: dies ist die Stelle der vorherigen Definition
../../../../src/sql/drivers/odbc/qsql_odbc.cpp:62:1: Warnung: »SQLULEN« redefiniert
/usr/include/sqltypes.h:140:1: Warnung: dies ist die Stelle der vorherigen Definition
../../../../src/sql/drivers/odbc/qsql_odbc.cpp: In function `QString
qGetStringData(void*, int, int, bool&, bool)':
../../../../src/sql/drivers/odbc/qsql_odbc.cpp:277: error: invalid conversion
from `SQLINTEGER*' to `long int*'
../../../../src/sql/drivers/odbc/qsql_odbc.cpp: In function `QByteArray
qGetBinaryData(void*, int, SQLINTEGER&, bool&)':
../../../../src/sql/drivers/odbc/qsql_odbc.cpp:333: error: invalid conversion
from `SQLUINTEGER*' to `long unsigned int*'

....
[more conversion errors here]
....
from `SQLINTEGER*' to `long int*'
../../../../src/sql/drivers/odbc/qsql_odbc.cpp:1219: error: invalid conversion
from `SQLINTEGER*' to `long int*'
make[4]: *** [.obj/qsql_odbc.o] Fehler 1
make[4]: Verlasse Verzeichnis »/data/kdebuild/qt-x11-free-3.3.3/plugins/src/sqldrivers/odbc«
make[3]: *** [sub-odbc] Fehler 2
make[3]: Verlasse Verzeichnis »/data/kdebuild/qt-x11-free-3.3.3/plugins/src/sqldrivers«
make[2]: *** [sub-sqldrivers] Fehler 2
make[2]: Verlasse Verzeichnis »/data/kdebuild/qt-x11-free-3.3.3/plugins/src«
make[1]: *** [sub-plugins] Fehler 2
make[1]: Verlasse Verzeichnis »/data/kdebuild/qt-x11-free-3.3.3«
make: *** [libqt-stamp] Fehler 2

Sorry for the german text - I really don't know where to look for the error.

It's really frustrating because of the long compilation time it takes to get to this error. Now I remember, why I don't like compiling on Linux :( - Oct 25 2004
Improving KDE

Various KDE 1.-4. Improvements by andrunko 313 comments

I'm right now trying to do so. Not that these would be the first debs I make, but something as big as KDE is not exactly what I do everyday for fun ;)

Anyway if everything works as planned I will provide them here. We'll see.. I had a problem with compiling qt-x11-free (debian source) but the kde stuff (vanilla source) seems to be fine, so I'll see about it.

Idon't really know right now whats the difference between debian and the vanilla sources of KDE / QT, so maybe some functionality gets lost... :(

But anyway it will be 3.3.1 and that's a step forward for debian users, isn't it :) - Oct 25 2004
Improving KDE

Various KDE 1.-4. Improvements by andrunko 313 comments

I fear this time it's me who doesn't really understand. :-/

Do you mean, that the light blue lines should not be there at all except for the first column (name), so that on the other columns (date, size, owner...) every line is white?
Propably not, but I really didn't get it - sorry.

Anyway I think the light blue lines are a good visual help to know what line you are looking at even if the 'name' column is not visible at the moment, so I think it's a great usability feature.

It's just that to me it feels wrong that the line is interrupted inside the 'name' column... I just don't see any benefit and therefor thought it just has not been noticed.
If it is intentional and I just don't see the reason that's ok of course - maybe you could explain again and I will see. - Oct 25 2004
Improving KDE

Various KDE 1.-4. Improvements by andrunko 313 comments

I'm not really against this feature and can see it's use (tiny screens with huge resolutions, bad eyesight), but just wanted to stress that the way SuSE implemented it is just bad.

I did not really bother to find out what to edit to get icons of usable size on my only SuSE system cause I hardly work at it's desktop.

But you can often see screenshots of systems running 800x600, 1024x768 or even less with those huge icons, which means that Kmenu is actually split in two without beeing very crowded. That's the worst usability I can think of.

That said - if done right (not like SuSE) this will add to usability.

(I don't dislike SuSE, but that specific behaviour is just nasty) - Oct 25 2004
Improving KDE

Various KDE 1.-4. Improvements by andrunko 313 comments

Maybe the new sidebar gets good enough that the old one can be ditched compeltely... that would be nice, like it has been said on kde-devel. But as it stands now the new one is not completely superiour to the old one - I DO prefer the new one I think.

Maybe having a look at something like opera (which is only a browser but no file manager) gives an idea of what to improve.

-----------------------------

On the bigger KMenu icons: I always hated that in SuSE. Not that such a feature wouldn't be of use for some, but in SuSE it always seemed to make them BIG automatically depending on the resolution / font size (don't know exactly) which is absolutely horrible.
So if it's an option the user can specifically set - ok. But then again, do the KDE developers want Yet another option? - Oct 25 2004
Improving KDE

Various KDE 1.-4. Improvements by andrunko 313 comments

I did not notice this before because my notebook's tft at home such have a great colour reproduction - so I did not notice the absence of the really light and subtile blue lines.

To me it looks kind of 'broken' because the line starts, then stops and starts again in the size/date columns.

Maybe somebody else (kde/konqueror core developer) will comment - it's not a big thing. - Oct 25 2004
Improving KDE

Various KDE 1.-4. Improvements by andrunko 313 comments

I've been downloading the KDE sources yesterday and will be patching today, but since I'm at work I had another look at the screenshots and noticed something:

The bugfix about too much space beeing marked when selecting a file has the effect that the light blue lines are interrupted where the dark blue marked area would have been before. It can be seen very good in screenshot 2. It looks a bit strange, though I still think it is better than to mark too much space, but I guess it won't be acceptable in KDE HEAD :(

Anyway what I've read at kde-devel sounds pretty good and I hope to see more from you in KDE - you got a pretty good idea what users want it seems. - Oct 25 2004
kio-locate

Various KDE 1.-4. Improvements by arminstraub 178 comments

Don't know how difficult a kio-slave specific modification to the context menu is, but anyway:

A nice feature would be to have an option "Open Folder" in the context menu of a located file, that would not open the file itself but a new konqueror window with the parent folder of the located file. Just like the option in KDE's find files dialog.

Otherwise, yes this should be included in KDE 3.4... ;) - Oct 24 2004
Improving KDE

Various KDE 1.-4. Improvements by andrunko 313 comments

Maybe that would be ok - the KDE developers seem to be quite ok when new developers submit enhancements - of course I don't know first hand.

If all of the patches are independant of each other chances are quite high at least some of this would make it into 3.4 - Oct 21 2004
Improving KDE

Various KDE 1.-4. Improvements by andrunko 313 comments

I still did not have the chance to try this out - but don't get this as a lack of interest (not that it would matter at 95% ;)) - just a lack of time on my side... really unfortunate for me. And what you are doing is just getting better and better - nice.

Now that I see how really advanced your abilities are (completely new feature (sidebar choice) already implemented as a per profile choice...) maybe there is a chance you could do something about the following as well.

You've kindly fixed the bug I pointed at about the width of the selection in tree view - thanks for that. There is one more issue that comes to my mind when I think about it - I have not yet opened a formal bug report because noone seemed willing to fix the first bug - but now you came along and I'll just give this a try:

(Forgive me if this is already fixed together with the previous bug... just could not try it yet - sorry)

If you select files with the rubber band in tree / detailed list view they are already selected, when the band is above any part of the name column (no matter where the actual filename is) - this is inconsistend with the area of effect of the files (rightclick and leftclick area) and (thanks to your patch) with the area that is shown as selected as well.

Ok, maybe this _has_ already been fixed with the previous bug... not sure.

Maybe someone using the latest patchset could verify this?

- Oct 21 2004
kio-locate

Various KDE 1.-4. Improvements by arminstraub 178 comments

Just got home and had a chance to test it - really nice.

Now I'm still more or less new to Linux and did not really use the locate command very much before - thus it was surprising to me how well and fast your kio slave works.. great!

Hope to see this (and maybe more from you) in the Kalyxo repository - in my opinion that's the next best thing to be part of upstream KDE itself =)

Thanks again for this usefull utility! - Oct 21 2004
kio-locate

Various KDE 1.-4. Improvements by arminstraub 178 comments

Now that sounds really usefull to me. One problem about kio slaves seems to be that you (me) don't always realize they are there.

I will give that a try - thanks for providing a debian binary btw. - I don't want to install something via make install and building debs is still a lot of work for me.

Mmmh using this in _every_ kio enabled app... really I like KDE more and more =)
Thanks! - Oct 21 2004
Konqueror GUI Ideas

Various KDE 1.-4. Improvements by PaT 12 comments

The more I think about it the more I agree the sidebar elements need this kind of re-work. Not that it's very hard to do, but I'd suggest to go near a KDE developer and see if this can make it into a future KDE release.

By now the two things I personally disagree with would be the icon size (already said) and the new tab button.
The problem with that is that it would really be in the way in detailed view or multicolumn view with small icons. It's exactly where the first icon - or worse the first "+" from tree view - would be... Now that I checked it again it would not work at all since detailed list view and tree view come with additional information bars above every column - thus the "New tab" button would really look out of place.

Having said that I can not come up with a better location for this button and thus tend to say it should be left out.
I *think* in file management and webbrowsing alike most situations where you want to open a new tab might happen when you open a link or folder - and that can be done with the context menu.
Therefor I think opening the first tab through "File -> New Tab" on the rare(?) occasions where you need a new tab unrelated to your current position is better than to have the button on screen all the time.

That's just my opinion and I hope you carry on no matter what others say ;)

If it will note make it into KDE you will at least have learned a lot about hacking our favorite project and there will be another developer capable of fixing bugs and adding features :) - Oct 16 2004
Konqueror GUI Ideas

Various KDE 1.-4. Improvements by PaT 12 comments

Hmm, I guess the feature to _partially_ hide the sidebar by clicking on the currently active element ("File Management" in the screenshots) would be gone - but this should be pretty much ok, since the sidebar button is there on the toolbar. And this one would (and does today if enabled or triggered via F9) completely remoove / enable the sidebar so that there would no space be wasted.

Otherwise I think there could be a little "x" where the configuration-button tool has been in the first version of the mockups.

The benefit of this:

a new user who doesn't know which toolbar button disabled the sidebar (ok, it's pretty obvious from the icon) could click on the "x" to close the sidebar and then see that the sidebar-button in the toolbar is no longer active...
And I think it's a more natural behaviour to search for a way to close something near the element itself first. - Oct 16 2004
Improving KDE

Various KDE 1.-4. Improvements by andrunko 313 comments

This might be an imensely stupid or rude question but since you're using debian I'll give this a shot anyway:

Is there any chance you might make the Debian Packages affected by these patches available online?

Now that you are using the original KDE sources I don't know if you will be building debs from them or just make isntall, but if - or if you decide that the debian source packages are ok really - would it mean a lot of work to you to make them available to the public?

I'd like to say I would do this myself since I really think some people would appreciate it, but as it stands I might not manage such a task with my current knowledge - and beeing on dialup is a problem here too.

If something like this means huge amounts of additional work it's surely a no-go, but if it's something along the lines of "the debs are there anyway, might aswell upload them" this would be cool.

Thanks for the nice patches and the hard work to fix the bugs! - Oct 16 2004
Konqueror GUI Ideas

Various KDE 1.-4. Improvements by PaT 12 comments

Yes, looks good and Konqueror's defaults could need some cleanup imo.

The first thing that I noticed that should really not go from the default set up was the "enter"/go button right to the adress bar.

Then I saw that you removed the home-button which I would consider a even more definite no-go... Really I would not want to imagine file browsing without a home button or the confusion of an unexperienced user getting lost in their filesystem and not finding a quick way back.

Great work on the sidebar though. Enabling a button to easily enable/disable.. great.

And the setup of three easily distinguishable tabs (in a nice place) - very nice, though I suppose most 'power users' will miss the root tab where there are no other services or the likes visible.

Oh and I still think it would be better (less bulky but still perfectly usable) to have smaller toolbar icons.
- Oct 16 2004
Improving KDE

Various KDE 1.-4. Improvements by andrunko 313 comments

Damn, just looking at screenshots 2 and 3 makes me _need_ this.. and I'm not the kind of guy that needs a new theme/style every two... this is so much more than just looks, I think these are some great usability improvements, too.

Well, now I have to look into this and see if I can compile it myself. - Oct 15 2004
Improving KDE

Various KDE 1.-4. Improvements by andrunko 313 comments

I don't think it would work, too.

Tree view kind of needs the squared selection type imo. - Oct 15 2004
Improving KDE

Various KDE 1.-4. Improvements by andrunko 313 comments

andrunko, you seem to be interested in the best possible look and feel a user can have - maybe (yes I know there have been other suggestions before) you can take a look at this:

http://bugs.kde.org/show_bug.cgi?id=88964

As amiroff suggested in his comment:
"Also, is it possible to make a selection with length equal to the length of file name? I think this was it will look better." (See: http://www.amiroff.com/drafts/kde/list2.png)

Maybe you could fix this independantly of the rounded edge feature in all of KDE - I especially hope to see this for Detailed List View in Konqueror (see bug #88964 above).

No matter what - thanks for the great patches, I'm even tempted to try and compile the libraries myself as you said it's unlikely they will make it into KDE. - Oct 14 2004
Improving KDE

Various KDE 1.-4. Improvements by andrunko 313 comments

Just checked the look of this in my current 3.3.0 KDE - it's the same as in this screenshot, so I think it already misfits a bit now.

But I would in no case like the selection to span across the whole width of the sidebar - best imo would be if the selection would just be limited to where the foldername-text really is. Because that is the 'clickable' area - where you could click to activate the folder 8or it's context menu).

Having the selection span across the whole width would result in an highlighted but unclickable area -> users don't get that as I have seen xseveral times now with the current (3.3.0) way how files are marked in Konqueror Tree View. - Oct 13 2004
Improving KDE

Various KDE 1.-4. Improvements by andrunko 313 comments

Exactly what KDE 3.4 needs to be _the best looking release ever_ - it just looks great.
What can be seen in your screenshots as the default look for KDE 3.4 (with Crystal* - maybe the final version - and a normal sized taskbar) would make it the absolutely best looking out-of-the-box system available today - and yes imo that includes OS X.

Unfortunately I'll propably among those only staring at the screenshots and not experiencing it first hand though - compiling parts of KDE themselves is something many users propably don't like very much. Thus I really hope this will be in KDE soon.

Maybe you can add this as the solution to Bug #90051

http://bugs.kde.org/show_bug.cgi?id=90051



*I like Nuvola but I guess there is probalby no way it could be default soon. - Oct 13 2004
Kmenc15

Video Apps by ods15 36 comments

Didn't test yet put judging from the screenshots and your wording this seems to be the VirtualDub equivalent KDE/Linux needs.

Keep up the good work! - Sep 22 2004
Amarok

Audioplayers by amarok 574 comments

Unfortunately there don't seem to be any 1.1-beta packages in the kalyxo usntable or experimental repositories.
Unless I missed them it might be good to remove the link from this here - so that poor dummies like myself don't all excited already ;) - Sep 02 2004
akregator

Groupware by smt 12 comments

thanks for another fine akregator beta :)

Hoped kalyxo would have a debian package up quickly but guess what? I build my own and it actually works! (first time making a deb for me)

Anyway I tend to agree that a notification in the same style KMail uses would feel more consistent.
I know Kopete has the same you use, but (1) it's a chat application and therefore this speech bubble type fits pretty well and (2) Kopete gives this message when you receive a single message, thus "view" and "ignore" are specific for this certain message. With akregator there will most of the time be more than one new feed thus "view" can be there (like with Kmail) but it's not so important since it can only open one of the new feeds anyway. - Aug 28 2004