SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Wow. Lots of personalities in this thread. It seems to me that most of the posters in this thread are agreeing with each other in different ways that makes it seem as though you are all disagreeing. You all agree that Slackware fits a niche that it's users want filled - it's not a point and click distro and that is fine for Slackware and Slackers. But it is that way by design. I am perfectly confident that if Pat and Robby and Eric decided that they wanted everything on Slackware to be graphical and GUI based, then they would put in the hours to make it so. The fact that the installation and methodology hasn't changed for many years should alert everyone (including reviewers who often like to invent crises and problems) that it's not going to change anytime soon.
If you don't like the way the team do things but want to stick with Slackware you really have 2 options: either grab the software that will make Slackware more GUI based and install it or run one of the forks. No one is forced to run Slackware (except maybe Pat ) but if you do want to run it you have to accept that there are trade-offs: you have to do the work yourself and you won't get the package management that many people seem to need in built.
I have run Slackware for a few years* and can go from inserting the install disk to a working and usable environment in less than an hour. I take several more hours to compile and install the other stuff I need, but I can be connected wirelessly fairly quickly. The dev team deserve a massive round of applause and beer for getting such a bare bones looking distro to work so well out of the box with so few automatic configurations.
I seem to recall that KDE has long been plagued with the complaint that it's trying to be Windows. I am now seeing stories that say it is Windows that now has to play catch up. Which is nice.
Anyway, go back and read the posts dispassionately and ignore the petty name calling (which, if continued, will result in infractions. And we all know where that leads) and realise that no one is really disagreeing with anyone else here. So, to summarise: is Slackware perfect? No. Is any distro perfect? No. Does Slackware work exactly as designed? Yes.
* Declaration: I am currently on Kubuntu because of a failed hard drive and a need to get up and running quickly. I still have to tweak far more things regularly than I ever did on my Slack box.
Again, thank your for taking the time to reply, but I guess I didn't phrase my question properly.
Appearance is not that important to me, but so far, from what I've seen of KDE 4.x, it is not at all attractive! Looks like the splash page, sign on page, and panel were designed by a "Goth."
Since I grew up with gothic in the 80's that is not something I consider negative. You probably refer to the lack of colour in the KDM screen and the logon splash. That is all themeable of course.
Quote:
So, my question is, what are the "massive advantages"
The improvements made in Qt4 are described here http://doc.trolltech.com/4.4/qt4-intro.html but I think you have to be a programmer to appreciate fully how working with the Qt4 toolkit is better than with Qt3. Also, Qt4 is finally truely cross-platform which means KDE could be ported to Windows and MacOS, thereby expanding the potential user base.
Quote:
What does it do, or can it do, that will be of benefit to the end user? How can it improve, in whatever ways, productivity? Is it somehow "easier" to use? And, so on.
Thanks.
Oh, and I've been using it, and, sorry, I don't see anything about it which, imho, could be considered "improvement." Screen "tricks," while cute, are not productive.
These "screen tricks" are sometimes quite productive - look at the compositing features borrowed from compiz, which make it easier to un-clutter your desktop in search for an application window. Making the top-level window brighter than the background windows helps to focus on what you do.
Qt4 code is faster than Qt3, so there should be no sacrifice in KDE4's speed compared to the previous release. There are several new applications that are vastly better than their KDE3 equivalents- try the dolphin file manager for instance. Or okular, the document manager. Or gwenview, the image manager.
But the core workings of KDE are revamped too - handling of multimedia is way better now, thanks to the phonon framework. Artsd audio sound system is gone for good. The list is much longer, but I just want to make clear that all these improvements "under the hood" are not immediately visible, but should result in a more efficient way of working alltogether. To me, this feeling is obvious, I like working in KDE4 more than I did in KDE3.
Appearance is not that important to me, but so far, from what I've seen of KDE 4.x, it is not at all attractive! Looks like the splash page, sign on page, and panel were designed by a "Goth."
It's good. I hated bluish kde3 themes anyway
Quote:
Originally Posted by cwizardone
So, my question is, what are the "massive advantages"
What does it do, or can it do, that will be of benefit to the end user? How can it improve, in whatever ways, productivity? Is it somehow "easier" to use? And, so on.
As far as I know, Qt 3 is dead. It isn't being developed anymore, and it had to be dropped.
I'm still amazed by the fact that KDE4 has managed to take a few pages out of compiz' book and is able to pull of a lot of the same effects with a much smaller dent in performance. Maybe it's just on my rig, but I've noticed that KDE4 effects run much smoother and about 50 FPS faster than they did with KDE3.5+compiz.
That and it looks BEAUTIFUL, even if it was designed by a goth ;-).
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,085
Rep:
Quote:
Originally Posted by Alien Bob
Since I grew up with gothic in the 80's that is not something I consider negative. You probably refer to the lack of colour in the KDM screen and the logon splash. That is all themeable of course.
A matter of personal taste of course. Extremely negative to me, but, as you say, it is "themeable."
Quote:
Originally Posted by Alien Bob
The improvements made in Qt4 are described here http://doc.trolltech.com/4.4/qt4-intro.html but I think you have to be a programmer to appreciate fully how working with the Qt4 toolkit is better than with Qt3. Also, Qt4 is finally truely cross-platform which means KDE could be ported to Windows and MacOS, thereby expanding the potential user base.
From a business view, that makes sense.
Quote:
Originally Posted by Alien Bob
These "screen tricks" are sometimes quite productive - look at the compositing features borrowed from compiz, which make it easier to un-clutter your desktop in search for an application window. Making the top-level window brighter than the background windows helps to focus on what you do.
Have to disagree. It is distracting more than anything else, but I guess one can get use to it.
Quote:
Originally Posted by Alien Bob
Qt4 code is faster than Qt3, so there should be no sacrifice in KDE4's speed compared to the previous release. There are several new applications that are vastly better than their KDE3 equivalents- try the dolphin file manager for instance. Or okular, the document manager. Or gwenview, the image manager.
Never have liked Dolphin and would rather use Konqueror as the file manager, but really prefer Midnight Commander so as a compromise I sometimes use Krusader.
Okular is very good and I use it from time to time.
Edit in, 2 Jan. '09. I've just done a direct comparsion between Okular and Adode Reader (acroread) and Adobe, for .pdf viewing of course, is the better of the two packages. However, Okular does have its uses.
Gwenview I use almost daily and I can see where they are trying to go with it, but it is not, in its KDE 4.x present form as useful as the KE 3.5x version. It can't find any of the Kipi plugins, which makes it just another simple graphics viewer.
I use to, and still do in a now more limited matter, use it to view a graphic and if any editing needs to be done export it to The GIMP in about two clicks. You can still do that, but that is about all. Without the Kipi plugins, there is, as I said, not much you can do. I hope the Gwenview developers are working on that?
While on the subject of graphics is there hope that The GIMP 2.6x will be incorporated into Slackware anytime soon? It is a far superior to the 2.4x series.
Quote:
Originally Posted by Alien Bob
But the core workings of KDE are revamped too - handling of multimedia is way better now, thanks to the phonon framework. Artsd audio sound system is gone for good. The list is much longer, but I just want to make clear that all these improvements "under the hood" are not immediately visible, but should result in a more efficient way of working alltogether. To me, this feeling is obvious, I like working in KDE4 more than I did in KDE3.
Eric
Well, as you said they must be "under the hood" as they are not apparent, but hopefully KDE 4.2 will live up to the hype we have been hearing for the last year.
Last edited by cwizardone; 01-02-2009 at 05:53 PM.
While on the subject of graphics is there hope that The GIMP 2.6x will be incorporated into Slackware anytime soon? It is a far superior to the 2.4x series.
I've got gimp 2.6.3 (plus babl and gegl, it's new deps) in my personal repo for 12.2 if you're interested.
While on the subject of graphics is there hope that The GIMP 2.6x will be incorporated into Slackware anytime soon? It is a far superior to the 2.4x series.
I much prefer 2.4 to 2.6, 2.6 makes it look like they are trying to copy photoshop, which annoys me
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,085
Rep:
Quote:
Originally Posted by AceofSpades19
I much prefer 2.4 to 2.6, 2.6 makes it look like they are trying to copy photoshop, which annoys me
Well, it really doesn't matter to me, but I understand why they have done that. The "interface" for earlier versions of the The GIMP was probably the biggest, single negative to many users. By making the "command structure" similar to Photo Shop it is easier for Photo Shop users to make the switch to The GIMP.
Last edited by cwizardone; 12-31-2008 at 04:57 PM.
Well, it really doesn't matter to me, but I understand why they have done that. The "interface" for earlier versions of the The GIMP was probably the biggest, single negative to many users. By making the "command structure" similar to Photo Shop it is easier for Photo Shop users to make the switch to The GIMP.
One of those lovely "no-win" situations: for years the complaint has been that it doesn't look enough like PhotoShop and now it's becoming "too much like PhotoShop"
Well, it really doesn't matter to me, but I understand why they have done that. The "interface" for earlier versions of the The GIMP was probably the biggest, single negative to many users. By making the "command structure" similar to Photo Shop it is easier for Photo Shop users to make the switch to The GIMP.
But I liked the older GIMP interface. This is one of the points in which I don't understand about people that critize F/OSS, if its not enough like the comparative proprietary software, the interface sucks, but if its too similar, F/OSS developers are innovating enough
Regarding GIMP, the solution is obvious when an interface issue is so hotly contested and divided: provide both options and let the user decide which to use.
I never have understood developers taking an "either-or" approach. Support both and end the debate on both sides. Sure, some more code is needed and a few more check boxes in the preferences dialog box, but then everybody is happy.
It can depend on what the options are. If they are minor, like a skinning option, then I can see that they would include multiple options. Thing is that some programs would effectively turn into forks of themselves and every option would need to be separately maintained. It is sometimes easier to pick an option and tell everyone that that's it.
Regarding GIMP, the solution is obvious when an interface issue is so hotly contested and divided: provide both options and let the user decide which to use.
I never have understood developers taking an "either-or" approach. Support both and end the debate on both sides. Sure, some more code is needed and a few more check boxes in the preferences dialog box, but then everybody is happy.
This might not be easy, and availability of "both" options depends on program structure. Besides, for some reason I don't remember any MDI (Multi Document Interface - i.e. photoshop-like) applicaions written using GTK toolkit.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.