New Nautilus Screenshots 111
max cohen writes "Eazel has posted some new screenshots of Nautilus (as of August 2nd) and they're much improved from eariler versions. I can't wait to get my hands on the Nautilus preview release and give it a test drive!" They've come a long way since the last batch of shots: especially interesting is the way it handles albums of MP3s, and its integration with mozilla.
Who's the black dick? (Score:1)
Shaft!
One thing I noticed about the fullscreen shot ... (Score:1)
Re:Good news (Score:1)
Re:Major problem with nautilus (Score:1)
Debian Rulz
The ArsonSmith
Re:interface expert or not... (Score:1)
Okay that example was a bit contrived, too. But any time you have to do a lot of similar (yet slightly uncommon) tasks to a large number of files that can be categorised, Unix will be your friend. Doing repetitive tasks is what computers were made for anyway, right?
X-style GUIs vs. M$. (Score:2)
I have two questions...why is it, that with most of the *Nix community despising Microsoft, that every single new GUI that comes out ends up trying to be just like it?? Let's face it, that whole File View in Nautilus looks almost exactly like Win98/Win2k/IE4's 'Web View', which is a feature that is taken far too little advantage of. KDE has it too. The standard button alignment is also very close to that of Windows....what's the deal here people?? You've got a great product here, but you don't want to distinguish it for itself, or just running out of ideas?
My other question.....but I suppose this one contradicts the other above, is why is the menu bar always raised? This has always puzzled me about X-based GUIs. MacOS, Windows, and Be, all rely on a menubar that is flush with the rest of the window, and it looks nice. But even the most cutting edge of X-based GUIs have a raised menubar...what is the purpose of this? Its not like we don't see it...there may have been a purpose for it back years ago with monochrome displays or whatnot, but I think it's a practice whose time has come.
So on one hand, these guys seem to be doing everything they can to look like Windows(at least functionality wise), and then they have the one thing they cling to, and it's probably the one thing they shouldn't be clinging to.
-Julius X
Re:I was wondering. (Score:1)
You guys don't *get* it, do you? (Score:5)
Nautilus is great! Maybe some of you can step back a moment to see what Nautilus really it...of course not! this is slashdot! The only one who is allowed to include web browsing functionality into the file manager is Microsoft, right? Wrong! It just makes sense! FTP, HTML, file directories...they all are dependent on each other...they all make *sense* to exist together. Has anyone ever browsed an FTP site in IE? Notice how it looked *exactly* like any other folder in Windows Explorer? That is the *point*! It is called usability, people. It is called ease of use, people. The best interface is when everything looks the same! It is also called power.
You see, soon novice users will have the power to do some of things you *can't* on the command-line. And that makes you mad. And makes you label Nautilus a Windows clone. Grow up.
But lets just say for a moment, that you can, theoretically, think out of the box. Then you will see that Nautilus is more than just fancy file manager with web functionality. Did you see the screenshot with the mp3 player? You can play mp3's directly in the file browser! And don't tell me about big Microsoftian applications (again, another stupid comparison with Microsoft) that are monoliths. Nautilus uses components. That means that the web browser is a separate component, the mp3 player is a separate component, and maybe the file browser is a separate component...I don't know! But it is the Unix way, right? Except for the "easy" part which, as we all know...is way to Microsoftian for our own good, right?
So instead of piping|our|outdated|legacy|flat-text|utilities|to
(Note: My hostility is towards several posters who have already posted. I clicked in this story to see if others have seen what I saw in the screenshots of Nautilus. Instead I see anti-Microsoft zealotry. I just think the folks at Eazel deserve a little more. They have actually gone quite a ways beyond Microsoft in both power and ease-of-use. There. I said something bad about Microsoft. You can like me now.)
Re:Usefulness of a file manager (Score:1)
In any case this twerp is misinformed and has obviously prefers to judge without bothering to try graphical file managers which are on the whole moving towards offering the kind of features we like - even in KDE 1 you can select files based on a matching pattern - useful. Work in progress is EFM from the enlightenment guys that adds even more CLI functionality to a graphical file manager.
Nautilus: A pad++ rip-off? (Score:1)
Read more about pad++ here [umd.edu].
Nautilus is Great, but lest we forget, EFM. (Score:2)
It's very early in it's development, but it does the one thing that file managers never seem to do right. It acts as an interface to the system, less of a file manager, and more like a graphical shell.
Mandrake, one of the developers actually forced himself to avoid using the CLI for some time to figure out what EFM needed to do to replace it. And even now, it does reduce the amount of time I spend in the command-line drastically.
For example, you can still type using the typebuffer, so if you want to install an RPM, just type rpm in the dir to select the rpm and it'll open a term, show you the output, wait for you to type something and close. Honestly though, it also excels in the eye-candy realm, with full alpha-blended windows (true transparency, not the faux viewport stuff we're used to) and anti-aliased fonts. If you're looking for a file manager, I'd give it a look, over at enlightenment.org.
Re:What IS Eazel Nautilus? A File Manager replacer (Score:1)
no button to show/hide dotfiles
slow performance.
Needs a nice screen font... (Score:4)
MacOS and BeOs seem to be the GUIs with the nicest system screen fonts, IMHO. Chicago, the first Mac screen font was designed to be simple, readable and visually appealing.
The old Mac combo of Chicago (or even Charcoal) and Monaco was killer, and gave the Mac GUI a polished and visually clean look.
While I am aware you can probably change the font properties, I'm surprised that these former mac GUI gurus forgot to use a better default screen font.
Re:interface expert or not... (Score:1)
Re:Shouldn't Linux be an improvement? (Score:1)
No , whe need an interface even your grandma can operate, and preferably looks nice too. Nautilus looks like its on the right way.
---
obligatory mirror (Score:2)
http://dotslash.dynodns.net/00/ 08/05/1616256/i.html [dynodns.net]
If the eazel/nautilus guys or anyone wants it down, please mail me.
Re:Last Post (Score:2)
Personally, I use the Gnome panel (and nothing else from Gnome!), one 48-pixel panel on the bottom and a 24-pixel one on top. Both contain task lists, the top one containing the normal windows and the bottom, larger, one having the minimized windows. I have a clock/mailcheck applet and a few system monitors on the right side of the top taskbar, and the GTK+ Licq applet, a quicklaunch applet with icons for Netscape, Licq, XEmacs, Slrn, etc. on the left. I'm happy with it, and generally run programs from xterms as well.
Re:You guys don't *get* it, do you? (Score:1)
1) MSIE is componentized as well.
2) You make claims about power and ease-of-use based on some screenshots. Is this because the icons are prettier than MSIE's? Seems to me you can't talk about either property without having used the system to do something.
3) I agree that there is utility in blending functionality within a single GUI. But there is much greater utility in the command line because the command line can be utilized remotely, over a modem if need be, with very little loss of power or responsiveness. The UI you choose depends on the purpose for which you are using the system. If you're using it to replace a bunch of Windows terminals, then Nautilus is for you.
Re:Preview Release (Score:1)
Also this may be heretical but am I the only person who does not think gmc sucks
My opinion is it is fast does cool stuff lke shoing me contents of tar/rp files installs rp's from gmc
Useful stuff not crap features that you ca't turn off (eg most of what's in explorer)
Re:interface expert or not... (Score:1)
design.
Actually, Explorer is much faster than MC because I don't have to use the cursor keys to tick through one item at a time -- I can zoom to it with a mouse. Same benefit with GMC of course, but GMC is slower than Explorer in terms of responsiveness (probably because X and GTK and Imlib anf GNOME and so on are running in userspace).
Re:Looks (Score:1)
the reason explorer loads instantly in M$ is that it is already loaded - which is why it takes so long to boot up
Re:I was wondering. (Score:1)
couln't resist!!
Re:Looks (Score:2)
The reason that My Computer opens instantly is not that there is "no bloat". it is because the bloat has already been pre-loaded when you started up Windows. It's been made sure that the Windows Explorer code is sitting in memory right where it can be accessed most efficiently. Similarly, when you want to use the web, a lot of the web components are already in memory, which is why IE starts up so much faster than any other web browser.
This approach would be possible under Linux, but users would immediately cry foul. "This bloatware uses up xx Meg of RAM before it even _DOES_ anything! I just want to use it for the foo function, I don't want everything else to load as well!"
As for the problems of having to look at every file, this is why we Need A Better Filesystem For Workstations. Windows hacks its way around the requirement for looking at files by trusting a three-letter extension. This can often have really annoying effects (Like trying to work out how to save something from notepad so it _doesn't_ end up named foo.xml.txt) File managers that try this stunt in the Unix world do a terrible job, because file-extensions are not the Unix way. The only files on a Unix system that generally have dot-extensions are graphics and sound files. Finding out what kind of file something is, is what the 'file' command is there for.
What we need, of course, is real filesystem metadata. Being able to stat a file and get (directly from the fs, and therefore efficiently) a file-type magic number, or a MIME Type for the file would make file managers a hell of a lot more efficient. The problem is, the FS writers are busy writing filesystems for _servers_, which don't want to be loaded down with this sort of feature.
Charles Miller
--
Re:You guys don't *get* it, do you? (Score:2)
No, you are wrong. They are the same. FTP contains files and directories...so does your local file system. Web Pages are simply files in your filesystem. The differences between them are mere technicalities.
"A similar interface will just lead people to believe that it is a similar function. I'm sorry, but there is a big difference between files on your PC and files on some server across the Atlantic."
They *are* a similar function! Are you blind! Can you not percieve the similarity! They are simply different machines!
"TROLL!"
I am looking for you to back this one up.
"Save your amateur psychology for another day."
Okay. I deserve that one.
"And this is a good thing, why exactly?. Playing an MP3 is a very different thing to moving files around. It requires a very different interface."
Consistancy. Yes playing mp3 is a little different but Nautilus changes its interface slightly to compensate. But look at the advantages: the mp3 file is just like any other file...it has an icon associated with it. When the user clicks on it, the user sees a control to play and change tracks. The user expects it! It is natural and intuitive to the user! You can't get much better results than that.
"Oh right. So when it's done with a GUI, it's real power, but when it's done with a command-line, it's, what - fake power?"
Okay. Now you are responding to my words and not my meaning. I mean that piping flat files to each other might have been cool in the 1970's, we need something more for the 2000's. Nautilus seems to be there. We *need* applications that borrow the capabilities of other applications to fit their needs. And users are no longer programmers and computers are no longer stuck in a one-dimensional text-based world. We need the computer to obey the user and show the user what he needs to see---let the user *visualize* what the computer is trying to show him---and *interact* with the user. Computers are more complicated things now. And we need applications that deal with this complexity and present it comfortably to the user. It is the nature of the industry.
"Ever thought about not taking things so personally?"
Okay. It was the posts that got to me...not the poster.
But could you please try to respond to my meaning instead of taking pot shots at my choice of words?
Re:Exactly! (Score:1)
BTW, Windows 2000 (and I think 98) already supports media player previews. Windows 2000 also has some limited support for iconic content preview, but (I think) this functionality is limited to the "My Pictures" folder.
Re:How did they do that? (Score:1)
Re:humor (Score:1)
Thinking eh? Is that something I can find in a newsgroup?
What IS Eazel Nautilus? A File Manager replacer? (Score:4)
Mirror (Score:3)
Enjoy.
Ahem (Score:3)
Since when has integration of a file browser and a web browser been a good thing?
Yes, it's nice to have a file browser which can do useful things with the various types of files, but I define "useful things" as launching the application that works with files of that MIME type -- NOT loading another component into place in the file browser window.
You present new users with an interface that keeps changing, and doesn't give a clear line between different applications. This is confusing to people still struggling with the "executable programs and content data" split, not to mention probably not what the people experienced with computers wanted. I prefer to work with the data I've selected in a separate program, as opposed to in plae, so I can arrange them on my virtual desktops and continue to use the file manager for its purpose -- managing files.
---
Sweet man,sweet! (Score:1)
Also keep in mind that Nautilus is targeting new users. The seasoned vets among us may not have use for it, but the newbies will. Of course learning the innereds of Linux is the best way to go.
God bless! Geeky.org [geeky.org] All Things Geek
Geeky.org [geeky.org]
Re:interface expert or not... (Score:1)
[neural]~/tmp$ for file in *.html; do mv $file $file.old; done
That F2 key will get old real quick. It's much less CPU and memory intensive to load up a light viewer instead of a full blown application everytime just to view a file. That's why I use less to view text files and nedit to edit them. I don't load up the GIMP every time I want to get a quick look at a few PNGs. I don't know what to say, I haven't done that in years. Well ever since I started using Debian GNU Linux.
One request - good keyboard shortcuts/navigation (Score:2)
Re:How did they do that? (Score:1)
Re:interface expert or not... (Score:3)
Re:Patterns in the sand. (Score:1)
"The fact that GUIs are considerably more popular than CLIs is some evidence that more people are visually-oriented than verbally."
The problem with this popularity contest is that the majority have never really been given a choice. If one had set a CLI and a GUI side by side and said "pick which one you want" then you would have more of a point. But the majority haven't been given so objective a test. It has been more "this is what you'll be using from now on", and the alternative either is briefly (footnote) mentioned, or not at all.
True enough. What I was actually thinking of was the switch over from DOS to Windows in the late 80's/early 90's. A lot of people voted for a GUI over a CLI with their hard-earned greenbacks. And that was to a pretty crappy GUI (admitedly from a pretty crappy CLI :-) Of course there were other factors involved as well, such as upgrading of applications, but I do believe that a preference for GUIs over CLIs was a large part of this. If we were on DOS 15.7 right now, I don't believe there would be nearly as many computer users in the world.
Obviously a CLI like bash is going to be more efficient at expressing the commands for 1. But assuming that the files related to my web site are not organized according to a regular pattern, then doing operation 2 is going to be much easier using a GUI (I just click on the set of files I want and drag them)."
Assuming no organized pattern then both methods would be slow. Remember the brain is a pattern-matching machine, be it verbal,graphical, or otherwise. If their is a pattern then the deciding factor of one over the other is what comparative sense is being used. .
I agree, but if I want to identify three files from 50 in a GUI, all I have to do is find them in the list. If I want to do that in a CLI, I have to find them in the ls list, then copy each filename down into the cp command. Its more work that way.
How cool is this? (Score:2)
But the more I look at what Eazel is giving us, the more I think we're witnessing one of the biggest developments in the history of computing.
People, this could be the second biggest thing to happen to computers (first being C language).
I hope my karma can survive what is surely to come
-----
Shouldn't Linux be an improvement? (Score:1)
I thought they were going to rearchitect the UI and do something that would be an imporovement and make the GUI more efficient, intuitive, and faster to use. I thought they were going to do something that's better than Winows and better than MacOS.
But their strategy just seems to be yet another "I dunno what to do. Let's just copy Microsoft." strategy.
How do you convice people to switch from MS Windows when what they'll see is another Windows?
You don't. There has to be something better. We need a UI that mazimizes screen real estate, a UI that gives users automation/scripting capabilities, a UI that's faster to do things and find files and programs.
Re:X-style GUIs vs. M$. (Score:2)
Because of the intended audience. The only operating system the vast majority of potential users have any experience with is Windows. A smaller number has experience with Macs. For better or worse, the pre-existing experiences of these users has to be taken into account. Like it or not, Microsoft has defined the user interface "standard" for a while.
Exactly! (Score:2)
They will never be a "better Windows than Windows". OS/2 tried and failed. Then again this might not be surprising, if you consider that these are the people [eazel.com] who created the horrible General Magic PDA interface.
or maybe these screenshots are just a cover-up for the really cool stuff their developing...
Re:Nautilus is Great, but lest we forget, EFM. (Score:2)
--Ben
Re:interface expert or not... (Score:1)
slightly off topic but... (Score:1)
_joshua_
Re:Major problem with nautilus (Score:1)
Best of all, there's rpmfind --latest and a little bit of shell script.
Preview Release (Score:1)
Re:You guys don't *get* it, do you? (Score:2)
I guess it can be interpreted as a flame. But I really hate zealotry.
> 1) MSIE is componentized as well.
Yes. I don't understand the point though.
> 2) You make claims about power and ease-of-use
> based on some screenshots. Is this because the
> icons are prettier than MSIE's? Seems to me you
> can't talk about either property without having
> used the system to do something.
This is a GUI app. Much of the functionality is apparent from screenshots! The power claim is easy. Do you see the web browser? Do you see the mp3 player? That is power. Ease-of-use claim is left as a trivial exercise to the reader.
> 3) I agree that there is utility in blending
> functionality within a single GUI. But there is
> much greater utility in the command line because
> the command line can be utilized remotely, over
> a modem if need be, with very little loss of
> power or responsiveness. The UI you choose
> depends on the purpose for which you are using
> the system. If you're using it to replace a
> bunch of Windows terminals, then Nautilus is for
> you.
Nautilus *can* be used remotely (from others who have used it, I haven't). I am not here to tell you the command line is obsolete. There are thousands of people who are used to this interface and there will be things that can only be done in this form for quite some time. What I *am* trying to do is open your eyes. This isn't about Microsoft and it never was. It is about making more use out of the capabilities of modern computers. And bringing everyone else with us.
Re:interface expert or not... (Score:2)
Re:interface expert or not... (Score:2)
As for Microsoft, don't get me wrong. I am a big Microsoft fan, and I think it would be wise for Linux projects to emulate some of their practices. However, the fact remains that Windows by and large is heavily deteriorated by feature bloat. All this "whiz-bang" features that really aren't necessary hurt the environement. However, that is forgivable in Microsoft's case, they have upgrades to sell. However, projects like GNOME don't have that agenda.
As for COM, it is a gift from god. COM and DirectX are two technologies sorely missing from Linux. However, CORBA and COM are two entirely different beasts. Wheras COM is a (relativly) simple API, CORBA is quite a beast. Look at the two APIs. You can actually write something COM-like in a week or two. Most of the stuff is simply a standard and the C++ compiler handles most of it. However, implementing CORBA in a week or two is impossible. It is simply too complex. And in that complexity lies the problem. COM (not DCOM, the distributed version) is simple enough to allow you to use it for something like an API, or even reusable objects like stacks, etc. No way in hell you'd use CORBA for an API (oh wait, isn't that what they're doing in Berlin-land? Another stupid feature-bloat idea.) A CORBA-based stack object? I'd like to see that! In GNOME, CORBA is going to be much less usefull then another system would have been. It takes to many resources, and I predict that it will never gain the acceptance that COM has.
Re:X-style GUIs vs. M$. (Score:1)
We should be concentrating on making a unique(but also very user-friendly) experience, not one that copies what we already have.
-Julius X
You're searching for *WHAT*? (Score:1)
Nautilus, Konqueror, and Embedded parts (Score:2)
Have you really used Konqueror for much? I have.
Performance of gmc is much better than Konqueror. That's because gmc is much simpler and is currently only in maintenance while the "design wizards" (shudder) apply their techinique to Nautilus. I fear that Nautilus may blindly follow in the footsteps of Konqueror in designing in overcompexity using a component model that mimics Microsoft's COM without but the entire OS built around that system that MS has to enhance its performance at the expense of everything else.
When dealing with very large directories or very large lists of anything to be displayed using this component architecture where every item is an object at least (often several embedded objects) performance drags to a crawl even with a very fast computer. This is apparent when loading large web pages with thousands of tags (even with no frames and no tables) because the page is treated as thousands of html "objects". Ditto very large files in OOP word processors (KWord). All these great "component based" apps become unusable.
The architecture sucks because all these list and tree structures are fully loaded with data in their components which are created when data is read, instead of having their objects created and destroyed as needed for display and manipulation by the user. Moving these huge lists of objects around with every mouse click is insane. A solution to this problem has already been pointed out by a very competent observer on the kde mailing lists, "talin". No, that's not me. However, that solution was ignored.
This seems like nitpicking but the magnitude of the problem becomes apparent when using the Kde 2 betas and alredy is somewhat true of stable Gnome (1.12). Has the Eazel team thought about ways to deal with such design problems? Not just the above described problem, but the inherent instability and impracticality of a rigid adherence to object oriented methodology in general? Ways to bypass CORBA entirely, for example, if so desired? I hope so.
Currently Kde is fatally flawed because of over-reliance on parts and objects for everything, and every operation is also io-bound to the max. The degree of complexity and circluar dependencies in loading and unloading objects becomes unmanageable, and crashes become seemingly random and unpredictable. It is very obvious why things take so long to start - the loading and unloading of parts for every little thing, and the registering of so much io in the background.
This is a shame because otherwise Kde 2 is so promising. If these kinds of problems are not addressed and some of the object oriented "theory" taught in CS departments coupled with mimicry of MS COM is not acknowledged to be the problem rather than the solution, it will only get worse.
By that I mean a colossal, embarrassing failure.
Kde team wake up! Gnomers, learn your lessons from the mistakes Kde is making (as well as the things they are doing right)! I do want these new desktop systems to be usable. We need you!
Re:Usefulness of a file manager (Score:1)
I agree, and would like to offer these comments:
Compare the speed of:
Move all files to parent directory
Move all files starting with a-n to the parent directory
Move them back:
Conclusions:
If I were to build a desktop operating system/windowing system/file manager geared toward end users on desktop PC's, its first priority would be the user interface responsiveness. I don't care about disk writes, backup drives, underrunning CD-R's, whatever... the user interface, above all, must be perpetually snappy and responsive, no matter what else the system might want to do at the time. I get mad when my machine won't listen when I'm trying to tell it something. And I mean immediate. When that mouse button goes down, 1.5 seconds is far too long to wait for a popup menu.
If I were the designer of a windowing system and file manager, it would be a GUI at the very base-level (see the MacOS), and it would integrate a cool drag n drop GUI file manager with the BASH shell. As in, you could use a single keystroke to switch from GUI-Mode to terminal-mode. (Terminal using antialiased fonts, of course.) From there, maybe version 2 could implement a Mozshell-like blend to create a terminal that is supplemented with graphics. Anytbody know of existing software that approximates this?
Comments, whatever. Apologies for the poor grammar and lack of focus. I'm just textually mumbling to myself at this point.
Re:Stability, not purttyness (Score:1)
Here's my [radiks.net] DeCSS mirror. Where's yours?
Re:Last Post (Score:1)
Actually, wih reference to windows controls, they fucked up big time, by putting the close button right next to the non-destructive minimise/maximise buttons. One slip of the mouse, and that soon-to-be maximised window is now destroyed. The Mac platinum interface is much better as it has the close button on the left by itself, with the minimise/maximise buttons over on the right.
NICE (Score:1)
Displaying the properties of the mp3s is a nifty feature and i like it
--
Cumulative, cumulative, cumulative, the biggest advantage of open source is you dont have to reinvent the wheel.
Real-time Simulation (Score:5)
Cheers.
How did they do that? (Score:4)
Will the wonders of science never cease?
--
What I want to see... (Score:2)
My sucks grammar! (Score:1)
FileRunner (Score:1)
Among other things the fact that much of it is written in TCL makes it easy to hack customisations.
I use this all day at work.
Welps... (Score:1)
Oh well, hopefully the natilus shell and file manager will be stable and useful and included in GNOME. I think it'll attract many "newbie" style users. I like the idea of user levels and the structure/capibilities you can change. That's a good idea and hopefully it will be implemented carefully. I have faith in these guys. I never liked the mac but hell, I can say these guys can't hurt, they can only help. :-)
Oh welpers
Now we all the cynics can shut up! (Score:1)
interface expert or not... (Score:1)
I don't know what all this stylized presentation garbage is all about, but I can imagine it's a real hog of CPU and memory resources to preview the contents of every item in a folder. I thought we had "long" filenames covering the job of explaining to the user what the contents of a file are.
The single folder view is really obnoxious. With the Explorer "All Folders" panel, files can be moved just about anywhere with ease. When I upgraded my W2K workstation with a new hard drive and reinstalled the OS, it was EASY to drop files from the old drive into the new one before wiping it and giving the Linux box a nice upgrade, too. Interface experts be damned, I want my multi-panel display!
Good news (Score:4)
Hmm, a file browser + web browser without the bloat of two separate products. Sounds kind of like Internet Explorer minus the bugs and security holes.
--
Re:Usefulness of a file manager (Score:3)
While a file manager is useful to a newbie, I always find that I can get work done faster using a cli to a good shell like bash.
Then I would highly recommend you continue to use a CLI.
A file manager is to a cli as a first grade primer is to a novel.
Why be so offensive? Are you simply trolling? File Managers are not signficantly less powerful than CLIs. They are good at different types of operation, and they suit some people better than others. Many people are more visually-oriented than verbally-oriented. The former tend to prefer GUIs, the later CLIs. The fact that GUIs are considerably more popular than CLIs is some evidence that more people are visually-oriented than verbally.
One can be lot more expressive with text that with pictures. Sure, a picture is equal to a thousand words but the only problem is 'which one?!'
I disagree. Two scenarios:
1. I want to move all the files that end in .txt from directory A to directory B
2. I want to move all the files whose contents relate to my web site from directory A to directory B
Obviously a CLI like bash is going to be more efficient at expressing the commands for 1. But assuming that the files related to my web site are not organized according to a regular pattern, then doing operation 2 is going to be much easier using a GUI (I just click on the set of files I want and drag them).
Even when there is a regular pattern of files you want to work with, a GUI can often be easier (if less efficient) because I can just select the files I want directly, and I don't have to go through the cognitive process of forming the right pattern-matching command. If I want to pick 3 files out of 50, it often feels quicker to just click on them in a GUI view, than figure out the particular command that would select just those files. And in UI what feels quicker is often "better" (i.e. prefered by users) than the actually optimal strategy.
GUIs and CLIs are different tools that are optimized for different purposes. Both have strengths and weaknesses. I personally like to have both running and feel free to switch between them.
Mirror Request (Score:1)
Thank you!
rpmfind.net (Score:1)
Try rpmfind.net [rpmfind.net]. You can browse it online, or use the rpmfind [rpmfind.net] tool. Not quite as pointy-clicky as helix-update, but a great resource nonetheless...
---
I was wondering. (Score:1)
Re:interface expert or not... (Score:1)
This_is_another_picture_of_the_house_but_closer
Yet_another_picture.png
However, with preview, I can tell at a glance which is which. And just so you know, I didn't make those filenames up. Someone on our network dropped them on the shared drive.
Anyways, just a couple examples of why previewing files is sometimes more efficent (or userfriendly) then long_descriptive_filesnames.txt
it is (Score:2)
"What a waste it is to lose one's mind. Or not to have a mind is being very wasteful. How true that is"
Another mirror (Score:1)
Re:interface expert or not... (Score:1)
That's not what I said. Quality user interface design and bloated code are 2 completely different things.
GNOME these days is reeking of Microsoft.
Microsoft dominate more than 90% of the desktop market. They must have done *something* right. And code re-use with COM+ is one of those things.
Re:Having Trouble Loading Images? (Score:2)
Help?
----------
Re:Needs a nice screen font... (Score:2)
The standard console font is very nice for console work, but it's too big for X work, and doesn't scale down nicely.
For some reason, Chicago and Charcoal just don't feel right on X. This is probably because they were designed for other GUI's. A good font for X, would need to be bitmap (10, 12, 14 pt.), postscript, and probably truetype. Anti-aliasing would also help, Keith Packard of XFree is doing work on this, I have heard (doing rendering fast client side).
I have to agree it's time for a new X default non-monospaced font. Fixed in X is a pretty good monospaced font, but as it name implies, it's not at all scalable. Something existing just won't cut it -- even KDE's attempts at making a bolder default font (Helvetica Bold 10), seemed out of place.
Re:Welps... (Score:1)
(having given Microsoft the "inspiration")
--
Re:Nautilus is Great, but lest we forget, EFM. (Score:1)
Re:Last Post (Score:1)
To me this is a very bad bad thing. New revisions are supposed to offer improvements to products. I hardly call macintrashing an interface an improvement. Just like apple, the KDE group has shot itself in the foot. I think they may have done it in response to the anti-windows zealots who probably bitched to high heaven about KDE looking and working like windows. Once again, if it isn't broken, don't fix it. KDE is supposed to be a newbie friendly desktop environment. Well guess where most newbies are coming to linux from? I personally prefer the windows UI for many things. It stays out of your way for one thing. I can maximize all my apps and switch between them from the toolbar on the bottom. There aren't some screwy buttons or windows that you need to control the UI which are always on the screen getting covered up by maximized windows.
To me the perfect window manager is KDE 1.x, after some tweaking. I make the Kpanel run vertically along the left side of the screen and put the taskbar at the bottom of the screen. On the Kpanel I have an icons for Xterm and netscape. Another leads to a submenu with xxmix, xmcd, and xmms. I've got one other icon for xkill, so I can kill progs that are running awry without opening up an xterm and typing kill -9
Any other program I need to run I start from a shell prompt. The fact that KDE's maximize, minimize and kill buttons are in the same place as windows is a good thing.
Microsoft's OS's are buggy and bloated, but they did get the UI right in many ways. Like I said, the UI is simple, lets you get your work done, and stays out of your way. It doesn't make you jump through hoops to resize windows and it doesn't make you have to worry about whether app X is going to cover up window manager window Y that is needed to function Z.
I know this is in response to a troll, but the very idea that a project should "innovate" rather than make use of successful patterns that already exist simply because they come from microsoft is pretty damned stupid.
Religion belongs in church, not in OS design.
Re:Major problem with nautilus (Score:1)
small screen folks... (Score:2)
i have an 800x600 screen.
can't really change that. but gnome apps seem to want/expect 1024x768. open the control panel. look at the gnome gpg tool.
please, please, PLEASE remember us laptop users. please.
Now how do I actually get it? (Score:1)
cvs [login aborted]: recv() from server cvs.enlightenment.org: Connection reset by peer
Wah. Wish that there were daily snaps of EFM. It looks rather interesting.
Re:Major problem with nautilus (Score:1)
The impatient should probably try fiddling with their
ends up being much faster than ftp.debian.org because the former redirects to a number of different http hosts, while the latter is a single ftp server. -- $.02
EFM Stability (Score:1)
My favorite feature is that you can type commands, file names, and web sites right into the root window, and it does the appropriate thing. - for example you could just type "www.slashdot.org", and it brings up netscape with slashdot loading. You could type "/home/mp3", and it will bring up your mp3 directory. Or you could just type "killall mozilla-bin", and it would run the command.
And don't even get me started about the background image quality, antialiased truetype fonts, and font styles...
Abe
Re:Major problem with nautilus (Score:1)
Re:You guys don't *get* it, do you? (Score:1)
Re:Needs a nice screen font... (Score:1)
Re:You guys don't *get* it, do you? (Score:1)
Have you ever tried dragging files in IE's ftp? (Version 4, not 5+). You can't drag them to the desktop. An interface sucks if it is not consistant.
-- Thrakkerzog
Re:You guys don't *get* it, do you? (Score:1)
Re:You guys don't *get* it, do you? (Score:1)
I wasn't trashing anything. I'm just saying that using the same interface is pointless if the functionality is not the same.
-- Thrakkerzog
Re:interface expert or not... (Score:1)
This isn't an issue with the interface design. Since neither of us have either used it we can't really speculate on how fast it will be, but I bet that won't be an issue in the future - we'll all be running 4 ghz Athlons with gigs of RAM and Nautilus will fly. Think about it - Explorer is *much* slower than MC, but you seem to think it's a good design. The most important thing Nautilus has to concentrate on is good user interface design, and worry about performance optimization later.
Interface experts be damned, I want my multi-panel display!
I would be very surprised if the final release of Nautilus doesn't have this in one form or another. They probably just didn't take screenshots of it.
Re:You guys don't *get* it, do you? (Score:1)
You see, soon novice users will have the power to do some of things you *can't* on the command-line. And that makes you mad. And makes you label Nautilus a Windows clone. Grow up.
Yes, that does make me mad (er, just annoyed enough at the shortsightedness of it to speak up). No it's not immaturity at all.
Linux/unix's big strength relative to other operating systems is its scriptability. Don't get me wrong, I'm appreciating GUI's more all the time, in fact sometimes I feel grumpy if I have to open an rxvt to get something done.
So bring on the GUI, but most definitely, don't give up the scriptability. The ideal system allows you to do everything from a GUI and everything from a CLI, and to easily find out how doing something in one could have been done in the other.
Re:interface expert or not... (Score:1)
GMC and Explorer are similar in speed.
MC is so much faster that even in X I use MC most of the time.
In regards to using a mouse, perhaps you are thinking of Lynx in file manager mode? Rather than MC?
Re:humor (Score:2)
Having Trouble Loading Images? (Score:5)
I've mirrored some of the images. [taoriver.net] (They are quite impressive; Note that as you zoom in on a text file, you can actually read the text within the file..!)
Consider it an experiment in Slashdotting.
Re:interface expert or not... (Score:1)
Major problem with nautilus (Score:1)
Re:humor (Score:1)
--
Re:I was wondering. (Score:1)
Re:What IS Eazel Nautilus? A File Manager replacer (Score:4)
----
Window managers in general (Score:2)
A window manager is a program designed to help you make better use of other programs. As such it should not interfere with the function of other programs. It should stay out of your way.
A window manager should provide a simple method for starting new programs and an easy way to switch between running programs. The fewer steps necessary to do both the better.
If you look at windows, particularly win98 with its desktop enhancements, it does a very good job of this.
Running tasks are all shown in a bar along the bottom, allowing you to quickly switch to any task. When windows are maximized they do not cover this bar. The menus under the start button allow you to start up any application which is on the system. Links to frequently used programs can be inserted in an area next to the start menu so that they are always immediately accessible.
With other window managers more effort it needed to keep the desktop in a usable state. Maximize a window and it covers up things you don't want covered. Or it might only maximize vertically instead of truly maximizing. The users has to spend time and effort managing the windows when that is what a window manager is supposed to do.
It seems that people who create window managers spend a lot of time and effort making it look fancy and themable and all that instead of concentrating on making it useful. Also they may intentionally make it different from windows out of some misplaced zealousness against anything microsoft.
KDE for the most part gets it right, at least in the 1.x version. The default config for it isn't as good as it could be, but it is easy to fix.
2.x on the other hand has been broken. I'm going to have to find another window manager because I can't stand the one in KDE2. The only thing I use KDE for is its window manager anyway, so moving to something else is no big loss.
But unfortuneately it looks as if I'm going to have to write my own window manager. All the ones I've seen are broken in some way or another.
At one time we were all stuck with FVWM or MWM, or OLWM. Those days really sucked. We made do with those because there wasn't anything better. But then things like Afterstep started showing up and life got better. But now it seems that things are going backwards again, back towards cumbersome complex desktops that fight you rather than help you.
I won't have it. I'll write my own WM rather than be forced to play games with one that doesn't work right.
Lee
Looks (Score:2)
I am in no way a microsoft fan but I'm afraid microsoft has it right with Explorer. You click on My Computer, it opens up instantly, no bloat. You want to use the web, type a web address, THEN it loads up web components. Same thing with BeOS. The tracker is very efficient and small, and gets the job done. I'm beginning to feel like it isn't worth it to open up the file manager in KDE/Gnome to copy a few files since its 10x easier in a shell.