Difference between revisions of "General LnF"

From Catglobe Wiki
Jump to: navigation, search
m
Line 20: Line 20:
 
#All pages must use style sheets. (*)  
 
#All pages must use style sheets. (*)  
 
#No text or border should move on mouse-over or selection.  
 
#No text or border should move on mouse-over or selection.  
#The buttons on search dialogues should be 'Search' and 'Cancel'. Please notice examples below of correct and incorrect way&nbsp;&nbsp;<br>&nbsp;[[Image:General-13-1.png]]<br>&nbsp;[[Image:General-13-2.png]]<br><br>
 
 
#Hyperlinks and tags written by users should only apply in viewers; e.g. emails, reports, questionnaires and the like; generally places set to using an HTML editor. Whenever a hyperlink or tag is presented in e.g. a list or form field it should be shown as pure string, i.e. the tags should be shown non-converted!&nbsp;<br>[[Image:General-14-1.png]]<br>[[Image:General-14-2.png]]<br>[[Image:General-14-3.png]]<br><br>  
 
#Hyperlinks and tags written by users should only apply in viewers; e.g. emails, reports, questionnaires and the like; generally places set to using an HTML editor. Whenever a hyperlink or tag is presented in e.g. a list or form field it should be shown as pure string, i.e. the tags should be shown non-converted!&nbsp;<br>[[Image:General-14-1.png]]<br>[[Image:General-14-2.png]]<br>[[Image:General-14-3.png]]<br><br>  
 
#Resource name: Length of a resource name must be a max length of 175 characters and not have "\" in it and never has same name in same path for same resource type  
 
#Resource name: Length of a resource name must be a max length of 175 characters and not have "\" in it and never has same name in same path for same resource type  

Revision as of 04:34, 23 December 2009

General LnF

  1. Whenever possible try to avoid refreshes in you content windows. Use server methods and Ajax enabled controls to make each interaction looks as if it was a desktop application.
  2. Avoid unneeded scroll bars.
  3. Always test that your interfaces look good in 1024x768 and widescreen. An interface that is not tested in small resolution environments is not thoroughly tested!
  4. From version 5.5 (Fire), full support of all existing modules and all new projects for multiple browsers. The features should fulfill all look and feel guidelines in the following browsers: IE, Firefox.
  5. Some viewers MUST work under all (larger) known browser platforms such as: IE, FF, Flock, Opera, Google Chrome, Safari:
    1. Report viewer
    2. Monitor portal
    3. My portal
    4. Questionnaire viewer
    5. Dashboard viewer
    6. My web shop
  6. The money should be shown as either '1,000,000' or '1.000.000' dependent on logged in user culture.
  7. Whenever an action may take more than 1 second, there should appear a waiting icon to ensure the user that the GUI has not stalled and the action has been accepted and started by the system.
  8. There should be a clear indication of when a save has been successfully completed. In the below circumstance a "Done" or "Saved" notification would be fine.
    General-7.jpg 

  9. There should be a "Close" button on all pages. Continuously closing windows will lead user to MyPage. 
    General-8.png 

  10. Make sure edit/list areas extend to the bottom of the screen or dialogue. Does not look good when user can see that the content area ends inside the screen dialogue area!
    General-9.png 

  11. Always use existing controls where possible. It is better to ask for an extension of a control than make a new one yourself.
  12. All pages must use style sheets. (*)
  13. No text or border should move on mouse-over or selection.
  14. Hyperlinks and tags written by users should only apply in viewers; e.g. emails, reports, questionnaires and the like; generally places set to using an HTML editor. Whenever a hyperlink or tag is presented in e.g. a list or form field it should be shown as pure string, i.e. the tags should be shown non-converted! 
    General-14-1.png
    General-14-2.png
    General-14-3.png

  15. Resource name: Length of a resource name must be a max length of 175 characters and not have "\" in it and never has same name in same path for same resource type
  16. Non-resource name: Length of a non-resource name must be
          +a max length of 256 characters, Ex: alias of report or PQ; OR
          +a max length of 64 characters where objects will be shown in limited space contexts may require limititation on string length of names, Ex: show object's name in HTML viewer as dashboard item