LQ Suggestions & FeedbackDo you have a suggestion for this site or an idea that will make the site better? This forum is for you.
PLEASE READ THIS FORUM - Information and status updates will also be posted here.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I've got just one complaint--the "Quick Reply" frame.
Inside this frame is a button labeled "post reply". This button does NOT post the reply that was typed in, but actually erases that reply while going to the old fashioned post reply page.
Outside of the "Quick Reply" frame is the actual "submit reply" button which posts the reply the user just typed in.
I find this interface detail to be bizarre, counterintuitive, and prone to causing frustrating mistakes. My suggestions for a fix are:
1. Move the "post reply" button to somewhere outside the "Quick Reply" frame.
2. Modify the functionality of the "post reply" button so that it automatically reads what's in the Quick Reply text field and puts that into the post reply text field. Thus, the post reply text field starts off with what the user had typed in rather than starting blank.
There already are two other 'Post Reply' buttons (one right above the offending button), so I too think it should be removed. If it is changed to save the text like IsaacKuo suggested, it's appearance should be altered so it can be distinguished from the other buttons.
I don't see any harm in just making all of the "post reply" buttons copy over the contents of the Quick Reply field. By default, the Quick Reply field is blank, so the user wouldn't notice the difference if he's used to the old way of replying (before the Quick Reply field existed).
From a usability standpoint, the [Submit Reply] and [Spell Check] buttons should be moved nearer the edit box than the [Post Reply] button. The argument here is that the first two buttons act directly on what the user is working on.
Or at least, make the text above [Post Reply] clearer!
It really is confusing, especially since it's very typical for the "Submit Reply" and "Spell Check" buttons to NOT be visible at all! Try scrolling down a bit with the mouse-wheel...chances are good that a few ticks down, the Quick Reply frame will be visible, along with the "post reply" button, but the Submit Reply & Spell Check buttons will NOT be visible!
What's worse, is that the surrounding blue rectangle may be entirely visible--including its bottom edge. Visually, this tells the user that there isn't anything more to this control group below the box.
Furthermore, the "Submit Reply" and "Spell Check" buttons actually appear physically closer to the "Similar Threads" frame than the "Quick Reply" frame. These buttons are centered so they're lined up with the also centered "Similar Threads" title. Nothing in the Quick Reply frame is centered to line up with those buttons.
Basically, there are a lot of things visually distinguishing the Submit Reply and Spell Check buttons apart from the Quick Reply frame, and NOTHING visually connecting them. That wouldn't be so bad if it weren't for the presense of the "post reply" button. If that "post reply" button were removed from the Quick Reply frame, then any user would instantly realize something was missing and would then hunt for the "Submit Reply" button.
As it is, the "post reply" button is visually the obvious thing to press.
Distribution: Debian, Red Hat, Slackware, Fedora, Ubuntu
I can change the wording a bit if that would help. If it would look better, we could also put the Submit Reply and Spell Check button in a dark blue lower bar that is more a part of the Quick Reply table.