Search options (Page 1 of 5)

I definitely see what you guys are talking about with moc -- I tried this before I landed on cmus, and have to admit that I really like the layout and the simplicity of the program.  My only qualm is that there's no way to sort through your music library by ID3 tags, which strikes me as a huge drawback.  I also find the keystrokes in cmus much more logically laid out, specifically the fact that z-x-c-v-b control << back - play - pause - stop - forward >>, as opposed to moc, which has its keystrokes designated by characters relating to the first and second letters of the function's name.

This in addition to the fact that you can create regular expression filters to generate playlists is really unique, and the vim-like :commands also make cmus much easier to navigate from within the application itself.

I installed wicd in place of NetworkManager, and find that I have mixed feelings about it.  I do appreciate the fact that wicd gives more detailed info for networks (MAC address, etc.), and think that the interface for setting up info on each individual network is much more intuitive and useful.  This I like.

I do feel, however, that wicd it falls short compared to NM in what I believe it's primary objective to be -- a simple interface for connecting to WiFi networks.  I say this for a couple of reasons -- rather than providing a dropdown list of the available networks like network manager, it opens up a new window for the client, which seems a bit more cumbersome when the user needs to identify the unprotected network with the best connection strength.  Also, the graphical representation of the strength of each network is less useful, as wicd only rates the networks to the nearest 25% increment (in a smaller, vertical bar), as opposed to NetworkManager which displays a more accurate, horizontal bar.  Yes, wicd does display the percentage of the connection below the bar graphic, but this is less elegant in my mind.

For the time being I've got wicd installed and I'm going to keep using it to see if it fits well with my daily use, and I'll report if my sentiments about it shift one way or another.

Interesting -- I haven't heard of fvwm-metisse.  I'll do a bit of research on it, but could you give me your two cents on what it is/what the benefits are?

Well, keep thinking about it raizenwolf.  In the meantime we're here to help you work through the thought process, and hopefully end up with some new features or even a paradigm shift that could further #! and its community.

Couple of things --

Raizenwolf -- thanks for the throrough and provocative post.  It can't be easy to suggest using a desktop environment to an entire community of #! users who have adopted Openbox as their own.  It's essential to ask questions like these in order to ensure the quickest possible development of our beloved distro.  Thanks for sticking to your guns.

Shaqarif -- I completely agree with you about Listen.  I've tried every gnome-like music player under the sun, and there's something about Listen that just feels the most well-laid out and, er, brilliant to me.  I have had trouble setting up media player device support, but it's more for lack of trying than anything else.  Also, I've since switched to cmus (CLI app) in favor of any GUI-based jukebox, and absolutely love it.  I'm going to give mpd + npmpc a shot too for consideration on our CLI/Terminal Apps final menu.

Additionally -- let's not confuse the terms user-friendliness and newbie friendliness.  That which is friendly for newbies, while 'easy' to use for more experienced users, often presents a number of caveats such as lack of speed, lack of customization, and a bloated of applications selected more for their popularity than utility.  By targeting more advanced and experienced users, Phillip has developed a distro that fits our needs perfectly, rather than developing a more noob-friendly distro that doesn't quite fit everyone's needs exactly (see Ubuntu).  The configurability of Openbox, for example, was enough for me to realize that I could do away with gnome without any major sacrifice, and, in fact, simultaneously become a more GUI-indenpendent linux user in doing so.  Even with the menu that #! presents by default, I find myself stripping away the options in the ~/.config/openbox/menu.xml everytime I become accustomed to editing one of them from the terminal, simultaneously increasing my understanding of the system, and lessening my dependency on graphical elements to utilize it.  In gnome, this kind of progression away from gui-dependence is all but a dream....

ggordon -- I completely agree with you, but when delving into which should be chosen by default an OS menu, software should be chosen a bit more objectively.  That's why I'm trying to weigh as many opinions about and strengths of each application as possible.

On further review, it seems that Opera's Presto engine performs exceptionally in the Acid 3 test:

http://en.wikipedia.org/wiki/Acid3

Certainly a feather in Opera's cap.

ggordon and omns -- I've done a bit more digging into the weechat vs. irssi battle, and decided that I was premature on selecting irssi.  I'm going to do some intense IRCing over the next couple of days, and see if that helps me come to a more logical conclusion about which of these should be featured in the CLI menu.

Ah!  Didn't even realize that it's Vladstudio!  Amazing stuff here -- the whale/island wallpaper was my default for a long, long time...

omns -- could you tell me where you got the gray/white wintery tree wallpaper?  I'm considering using it...

Hey Aku -- Welcome to the forums!

I tried to get mpd and npmpc running on a Hardy-based system, but despite hours of work came to the conclusion, as I read on some forums, that there was some inherent conflict between the two, which at the time seemed like too much of a pain to deal with.

That said, I'll give mpd/npmpc a shot on our shiny new #! platform, and see what's what.

Thanks again for the suggestion, Aku, and please let me know if there are any other apps you'd like considered for the CLI/Terminal menu.