Re: [Task]: POST GET -- Ready for test

[Davi Leal]

Victor Engmark wrote:
> IMO it's better to re-use any forms to show error messages. You can use
> e.g. the Yellow Fade Technique
> <http://www.yourtotalsite.com/archives/javascript/yellowfade_technique_for/> 
> and an error message tied to the form field to show what's amiss. That way,
>
>    1. users won't have to remember which fields were wrong (the flashing
>       ones with a prominent error message),
>    2. users won't have to remember what was wrong with the individual
>       fields (the error message will tell them),
>    3. users have one less page to familiarize themselves with, and
>    4. you don't break the back button 
>       <http://www.useit.com/alertbox/990530.html>

I agree with you.   When errors are raised, maybe we should add an extra 
general-error-message at the top of the page, due to the Qualifications and 
JobOffer forms are large and the error message could be 'hidden' at the 
bootom of the page.

  Task: https://savannah.nongnu.org/task/index.php?6540


> Reset and Cancel Buttons <http://www.useit.com/alertbox/20000416.html>
> are considered harmful to the user experience (in most cases).

Done.  I have removed the "Reset form" buttons which anyway were not able to 
clean the values loaded from the session variables.

About the Cancel buttons, I have not removed it due to I think they are useful 
due to they raise the clean of the session variables. Note that the JobOffer 
form does not use neither need the Cancel button due session variables are 
cleaned at its start.

Maybe we could use a similar business-logic at the Qualifications and Person, 
etc., and so be able to remove the Cancel buttons.

  Task: https://savannah.nongnu.org/task/index.php?6542


> The header of the GNU Herds pages is very tall, compared to
> the contents of https://savannah.nongnu.org/task/index.php?6542it. Beware of 
the fold <http://blog.clicktale.com/?p=19>.

> The Hackers' Guide link is probably used only by a minority of the users
> (those who want to hack will find it even if it's in the menu),
Removed.

> and the language options can be a separate floating div.
> That way, the header can contain 
> only the string "GNU Herds - Free Software Association", and there'll be a
> lot less scrolling for the users. The header space is the most valuable
> space on any web site.

I have reduced the image size.  However, I do not think we should remove the 
image, leaving just the "GNU Herds - Free Software Association" text line 
with a floating div for the languages.

Ironic: We could even remove the "GNU Herds - Free Software Association", due 
to it is at the windows title, and leave the floating div for the languages. 
Compare these:

  * http://www.gnuherds.org/Home.php?heading=No
  * http://www.gnuherds.org/Home.php

I like the heading as it is now. I have removed the "Languages" word, leaving 
just the language names.

The "Project state: Beta" string will be removed when the project be moved to 
the FSF and get the production state. So the header will be even more clean.


> Oh, and it would be great if the language options could use e.g.
> <a href="..." lang="en" xml:lang="en" title="Change default language to
> English"><img src="..." alt="English"/></a>
> in the language URLs for accessibility, and not show
> the current language option. 

I do not like using country flags due to some languages are spoken at more 
than one country, for example Spanish. I like use the language name, as the 
www.gnu.org does at the bottom of its page, instead of using a country symbol 
to be associated with a language. We expose languages not countries.

I have added   lang="en" xml:lang="en"   to the language links. Let me know if 
there is a mistake. I have not committed yet. You can download the current 
source code at: http://www.gnuherds.org/gnuherds-online.tar.gz

> Language auto detection could also be handy, but beware! I've got an
> English OS, using French regional settings, with a Norwegian / Dvorak
> keyboard, and Google is really annoying when they assume I want to read
> French.

The 'business-logic' the project is using now to try to autodetect the default 
language to show to the user is at: Layer-1__Page_builder/Web_Page.php

 1. If the user has set a language by hand use it: $_COOKIE['Language']
 2. else, process the user browser settings
 3. else, try to guess the best default language according to country code


> Sorry, got carried away there for a second.

Your feedback rocks Victor :)) .  As usual, I can be mistaken. Let me know any 
flame, comment, anything ...

Davi