I managed to set it fairly small but the rounding meant that as it got smaller less of it got useable. so once it got down to the "tiny" in kde3.5 sizes, over a third of the bar was just used on the corners.
the subset of POP3 or IMAP features that can be accessed by people whose technical knowledge doesn't extend far enough to set those up.
You mean people that haven't managed to follow a 5 step guide whose most difficult part is copy/paste, are using google gears & email? Scary times we live in!
I can't defend thier choice but from reading the blogs at the time of 4.0 it was quite clear, the people that have screwed over kde4 have been the ditros (looks at kubuntu & fedora) because they should have seen it wasn't really ready.
As for the naming reason I think the arguments went something like: 1) it cant be called 3. something 2) each release cycle produces a stable product at the end of its alpha,beta,rc cycle. Bear in mind that stable is in terms of what the release was for. kde4.0 was released stable enough to test and kde4.1 was stable enough to develop on. 3)security and stability fixes would be released for the previous versions 4)there is no golden rulebook of numbering so they didn't care too much
given these assumtions i cant think of a saner numbering scheme (i can however think of saner assumptions)
the otherday a friend asked for a fully blown music manager on windows and all i could recomend (begrudgingly) was itunes. while songbird is an up and coming music manager, if amarok2 is anything like amarok 1.4 it will become my default music player on windows and konqueror will be a necesity on any system i intend to maintain. kate is also good (although there are alternatives) and kopete is also a must as i have 2(+1) msn accounts and one from yahoo and i love resizing input boxes:P
I would also like the Webkit K-part to get some lovin', perhaps even always being installed. The KHTML/Webkit split needs to be evaluated. What is gained by ending KHTML? What is lost?
Oh NOES!2 options for what file manager to use. well i figured out how to compile the kernel but choosing between a webbrowser with tabs/frames style file manager and a simplified but more intuitive one is jsut too much.
Screw you guys, im going home^H^H^H^H back to windows
As a user that's stuck with kde3.5, i have just one question have they finally made the panel usable at the same size it was in kde3.5? What stops me switching is the large plasma panels, i just want a lean 24px bar at the top of the screen, last time i checked there was no way of disabling the rounding making it impossible to go below about 50
I disagree about the version numbering, from day 1 its been obvious 4.0 was for testing 4.1 was for developing 4.2 is the 1st end users release 4.3 the 1st release that will be truely ready for end users. 4.4 will be tweaked 4.5 will be so finished they'll get board and start over with a complete security overhaul because they went so far on the web integration that its going to be easier to start over than to just port kde4 to qt5
Second, the fact that libedit has the same binary interface as libreadline and perhaps does something that libreadline does (I haven't tried it) doesn't make it 100% clear that libedit is not derivative of libreadline
from a quick look at the mailing list it appears to me the problem is 1) company produces new hardware 2) company produces proprietary plug-in to produce asm for their hardware platform 3) they do not open their specifications 4) they are able to take advantage of GCC and its front ends while using a closed backend 5) ??? 6) profit
I may by wrong as i said this is just a quick read of the javabyte code discussion somebody linked to from here.
It appears you are trying to compile the linux kernel, do you want to: 1) Start writing a letter to re-license the code to SCO 2) Inform SCO the code is theirs, using a fax document 3) Open Excel to compare the TCO of linux to windows 4) watch a PowerPoint presentation on the failures of communism 5) open up MSDN help for more options
what distro are you on? im sure those on gentoo can compile with --nodcopservers or something. There is also the fact that kio_slaves is not bloat, in fact its anti-bloat as it allows for code reuse, the kio_slaves could be compiled into every single program to give them the ability to read from networks/drivers/etc but if you have 2 programs running then you'd have to load them twice.
Some of the many possible payloads are: a Linux kernel, FILO, GRUB2, OpenBIOS, Open Firmware, SmartFirmware, GNUFI (UEFI), Etherboot, ADLO (for booting Windows 2000 and OpenBSD), Plan 9, or memtest86.
that linux is only in coreboot when it is compiled as the payload, much like linux isn't intrinsically in grub
Don't forget games, iff you can ship the decoder with your software, you might aswell go ogg because vorbis has a slightly better file size at reasonable encoding and there are no downsides.
I use USB-pens to securly transfere my data from A -> B, gpg keys, documents, etc. Just because you use your USB-pens to spread viruses between windows pcs doesn't mean everybody does! I'd be quite interested to see ext2 vs reiserfs vs jfs vs fat.
I beg to differ, if you want a stable system capable of running well, consuming power, suspending, doing composting, flash, etc, intel are the only choice. Unless you play recent games intel really kick the pants out of ati/nividia for stability (the same can be said for windows drivers tbh)
Pretty much but without the need for anything other than ssh & unix commands (with the optional extention of a specific implementation). Basically if you read the link youll see its a technology originally developed by mc to make the gui interactions with remote servers easier. Its also a protocol for remote file management as compared to just remote file copying, so a comparision to a single tool is like saying that mc is just the same as cp or mv, which in turn are just the same as dd,
Fish means that you can do file movement over ssh (meaning you dont need anything more than ssh running on the server) Frames are well frames, as in its a filemanager that has a left/right or top/bottom divide, much like mc, so you can drag files from one side to the other.
I do think its not really fair to compare GUI tools to CLI tools as konqueror has the obvious disadvantages of being a gui tool, while i can also get an uninitiated friend to drag the music he wants to a second frame, while this is unlikely in mc or using any CLI tool. I'm a bit young for mc, but if it set the bar as far as CLI file managers go, and im fairly sure it did, why did nobody fork/clone it when it died? (i know redhat & novell have been patching it but its surprising nobody set up "new commander" or something like that to fix the blatant bugs)
Slashdot Mirror
I managed to set it fairly small but the rounding meant that as it got smaller less of it got useable. so once it got down to the "tiny" in kde3.5 sizes, over a third of the bar was just used on the corners.
erm doesnt every mail client post 1970s have threading?
the subset of POP3 or IMAP features that can be accessed by people whose technical knowledge doesn't extend far enough to set those up.
You mean people that haven't managed to follow a 5 step guide whose most difficult part is copy/paste, are using google gears & email? Scary times we live in!
I can't defend thier choice but from reading the blogs at the time of 4.0 it was quite clear, the people that have screwed over kde4 have been the ditros (looks at kubuntu & fedora) because they should have seen it wasn't really ready.
As for the naming reason I think the arguments went something like:
1) it cant be called 3. something
2) each release cycle produces a stable product at the end of its alpha,beta,rc cycle. Bear in mind that stable is in terms of what the release was for. kde4.0 was released stable enough to test and kde4.1 was stable enough to develop on.
3)security and stability fixes would be released for the previous versions
4)there is no golden rulebook of numbering so they didn't care too much
given these assumtions i cant think of a saner numbering scheme (i can however think of saner assumptions)
the otherday a friend asked for a fully blown music manager on windows and all i could recomend (begrudgingly) was itunes. while songbird is an up and coming music manager, if amarok2 is anything like amarok 1.4 it will become my default music player on windows and konqueror will be a necesity on any system i intend to maintain. kate is also good (although there are alternatives) and kopete is also a must as i have 2(+1) msn accounts and one from yahoo and i love resizing input boxes :P
I would also like the Webkit K-part to get some lovin', perhaps even always being installed. The KHTML/Webkit split needs to be evaluated. What is gained by ending KHTML? What is lost?
Screw that i want a gecko kpart
Oh NOES!2 options for what file manager to use. well i figured out how to compile the kernel but choosing between a webbrowser with tabs/frames style file manager and a simplified but more intuitive one is jsut too much.
Screw you guys, im going home^H^H^H^H back to windows
Im waiting till 4.3, 4.2 will most likely only meet the expectations of typical home users.
As a user that's stuck with kde3.5, i have just one question have they finally made the panel usable at the same size it was in kde3.5?
What stops me switching is the large plasma panels, i just want a lean 24px bar at the top of the screen, last time i checked there was no way of disabling the rounding making it impossible to go below about 50
I disagree about the version numbering, from day 1 its been obvious
4.0 was for testing
4.1 was for developing
4.2 is the 1st end users release
4.3 the 1st release that will be truely ready for end users.
4.4 will be tweaked
4.5 will be so finished they'll get board and start over with a complete security overhaul because they went so far on the web integration that its going to be easier to start over than to just port kde4 to qt5
im fairly sure linus uses fedora.
Second, the fact that libedit has the same binary interface as libreadline and perhaps does something that libreadline does (I haven't tried it) doesn't make it 100% clear that libedit is not derivative of libreadline
doesn't that make wine a derivative of windows
from a quick look at the mailing list it appears to me the problem is
1) company produces new hardware
2) company produces proprietary plug-in to produce asm for their hardware platform
3) they do not open their specifications
4) they are able to take advantage of GCC and its front ends while using a closed backend
5) ???
6) profit
I may by wrong as i said this is just a quick read of the javabyte code discussion somebody linked to from here.
It appears you are trying to compile the linux kernel, do you want to:
1) Start writing a letter to re-license the code to SCO
2) Inform SCO the code is theirs, using a fax document
3) Open Excel to compare the TCO of linux to windows
4) watch a PowerPoint presentation on the failures of communism
5) open up MSDN help for more options
what distro are you on? im sure those on gentoo can compile with --nodcopservers or something. There is also the fact that kio_slaves is not bloat, in fact its anti-bloat as it allows for code reuse, the kio_slaves could be compiled into every single program to give them the ability to read from networks/drivers/etc but if you have 2 programs running then you'd have to load them twice.
are you sure? i got the impression from:
Some of the many possible payloads are: a Linux kernel, FILO, GRUB2, OpenBIOS, Open Firmware, SmartFirmware, GNUFI (UEFI), Etherboot, ADLO (for booting Windows 2000 and OpenBSD), Plan 9, or memtest86.
that linux is only in coreboot when it is compiled as the payload, much like linux isn't intrinsically in grub
Don't forget games, iff you can ship the decoder with your software, you might aswell go ogg because vorbis has a slightly better file size at reasonable encoding and there are no downsides.
I use USB-pens to securly transfere my data from A -> B, gpg keys, documents, etc. Just because you use your USB-pens to spread viruses between windows pcs doesn't mean everybody does! I'd be quite interested to see ext2 vs reiserfs vs jfs vs fat.
why? by that i mean if linux doesn't need it why does windows?
because coreBoot doesn't run linux so the name is more relevant than LinuxBIOS
Thats a shame, i naively assumed that this meant windows 7 was no longer relying on the bios to report system information.
I beg to differ, if you want a stable system capable of running well, consuming power, suspending, doing composting, flash, etc, intel are the only choice. Unless you play recent games intel really kick the pants out of ati/nividia for stability (the same can be said for windows drivers tbh)
i believe i speak for all* linux users when i say:
HAHAHA, how does it feel now bitches!!! oh yeah now its your turn!
*well im sure that's how my mate feels and as microsoft has pointed out many a time, there are in fact only 3 people using linux.
Pretty much but without the need for anything other than ssh & unix commands (with the optional extention of a specific implementation). Basically if you read the link youll see its a technology originally developed by mc to make the gui interactions with remote servers easier. Its also a protocol for remote file management as compared to just remote file copying, so a comparision to a single tool is like saying that mc is just the same as cp or mv, which in turn are just the same as dd,
Fish means that you can do file movement over ssh (meaning you dont need anything more than ssh running on the server)
Frames are well frames, as in its a filemanager that has a left/right or top/bottom divide, much like mc, so you can drag files from one side to the other.
I do think its not really fair to compare GUI tools to CLI tools as konqueror has the obvious disadvantages of being a gui tool, while i can also get an uninitiated friend to drag the music he wants to a second frame, while this is unlikely in mc or using any CLI tool. I'm a bit young for mc, but if it set the bar as far as CLI file managers go, and im fairly sure it did, why did nobody fork/clone it when it died? (i know redhat & novell have been patching it but its surprising nobody set up "new commander" or something like that to fix the blatant bugs)