General LnF - Revision history

Wikicatglobe at 02:39, 18 October 2013

2013-10-18T02:39:44Z

← Older revision		Revision as of 02:39, 18 October 2013
Line 1:		Line 1:
	<accesscontrol>~~Administrators~~</accesscontrol>		<accesscontrol>Main:MyGroup</accesscontrol>
	<span style="color: rgb(255, 153, 0);">'''General LnF'''</span>		<span style="color: rgb(255, 153, 0);">'''General LnF'''</span>

Cg_pham at 08:51, 4 October 2011

2011-10-04T08:51:37Z

← Older revision		Revision as of 08:51, 4 October 2011
Line 1:		Line 1:
			<accesscontrol>Administrators</accesscontrol>
	<span style="color: rgb(255, 153, 0);">'''General LnF'''</span>		<span style="color: rgb(255, 153, 0);">'''General LnF'''</span>

Catglobe at 09:07, 21 May 2010

2010-05-21T09:07:26Z

← Older revision		Revision as of 09:07, 21 May 2010
Line 5:		Line 5:
	#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!		#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!
	#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.		#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.
	#Some viewers MUST work under all (larger) known browser platforms such as: <span style="color: rgb(255, 102, 0);">IE, FF, ~~Flock,~~ Opera, Google Chrome, Safari</span>:		#Some viewers MUST work under all (larger) known browser platforms such as: <span style="color: rgb(255, 102, 0);">IE, FF, Opera, Google Chrome, Safari</span>:
			##Questionnaire viewer
	##Report viewer		##Report viewer
	##Monitor portal		##Monitor portal
			##Diagram viewer
			##Dashboard viewer
	##My portal		##My portal
	~~##Questionnaire viewer~~
	~~##Dashboard viewer~~
	##My web shop		##My web shop
	#The money should be shown as either '1,000,000' or '1.000.000' dependent on logged in user culture.		#The money should be shown as either '1,000,000' or '1.000.000' dependent on logged in user culture.

Catglobe at 03:34, 23 December 2009

2009-12-23T03:34:05Z

← Older revision		Revision as of 03:34, 23 December 2009
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  <br> [[Image:General-13-1.png]]<br> [[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! <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! <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

Catglobe at 07:33, 20 April 2009

2009-04-20T07:33:12Z

← Older revision		Revision as of 07:33, 20 April 2009
Line 1:		Line 1:
	<span style="color: ~~#ff9900~~">'''General LnF'''</span>		<span style="color: rgb(255, 153, 0);">'''General LnF'''</span>

	#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.		#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.
Line 5:		Line 5:
	#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!		#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!
	#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.		#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.
	#Some viewers MUST work under all (larger) known browser platforms such as:		#Some viewers MUST work under all (larger) known browser platforms such as: <span style="color: rgb(255, 102, 0);">IE, FF, Flock, Opera, Google Chrome, Safari</span>:
	## IE		##Report viewer
	## FF,		##Monitor portal
	## Flock,		##My portal
	## Opera,		##Questionnaire viewer
	## Google Chrome,		##Dashboard viewer
	## Safari		##My web shop
	~~The viewers include~~:
	## Report viewer
	## Monitor portal
	## My portal
	## Questionnaire viewer
	## Dashboard viewer
	## My web shop
	#The money should be shown as either '1,000,000' or '1.000.000' dependent on logged in user culture.		#The money should be shown as either '1,000,000' or '1.000.000' dependent on logged in user culture.
	#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.		#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.
	#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. <br>[[Image:General-7.jpg]] <br><br>		#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. <br>[[Image:General-7.jpg]] <br><br>
	#There should be a "Close" button on all pages. Continuously closing windows will lead user to MyPage. <br>[[Image:General-8.png]] <br><br>		#There should be a "Close" button on all pages. Continuously closing windows will lead user to MyPage. <br>[[Image:General-8.png]] <br><br>
	#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! <br>[[Image:General-9.png]] <br><br>		#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! <br>[[Image:General-9.png]] <br><br>
	#Always use existing controls where possible. It is better to ask for an extension of a control than make a new one yourself.		#Always use existing controls where possible. It is better to ask for an extension of a control than make a new one yourself.
	#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  <br> [[Image:General-13-1.png]]<br> [[Image:General-13-2.png]]<br><br>		#The buttons on search dialogues should be 'Search' and 'Cancel'. Please notice examples below of correct and incorrect way  <br> [[Image:General-13-1.png]]<br> [[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! <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! <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
	#Non-resource name: Length of a non-resource name must be<br>      +a max length of 256 characters, Ex: alias of report or PQ; OR<br>      +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		#Non-resource name: Length of a non-resource name must be<br>      +a max length of 256 characters, Ex: alias of report or PQ; OR<br>      +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

	[[Category:LnF_guidelines]]		[[Category:LnF_guidelines]]

Catglobe: Add more rule: some viewers MUST support more browsers

2009-04-20T07:18:45Z

Add more rule: some viewers MUST support more browsers

@@ Line 5: / Line 5: @@
 #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!
 #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.
 #The money should be shown as either '1,000,000' or '1.000.000' dependent on logged in user culture.
 #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.

Catglobe at 11:13, 30 December 2008

2008-12-30T11:13:38Z

Catglobe at 09:14, 24 December 2008

2008-12-24T09:14:47Z

Catglobe at 06:26, 24 December 2008

2008-12-24T06:26:14Z

← Older revision		Revision as of 06:26, 24 December 2008
Line 1:		Line 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.		<span style="color: #ff9900">'''General LnF'''</span>
	#Avoid unneeded scroll bars.
	#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!		#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.
	#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.		#Avoid unneeded scroll bars.
	#The money should be shown as either '1,000,000' or '1.000.000' dependent on logged in user culture.		#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!
	#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.		#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.
	#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.		#The money should be shown as either '1,000,000' or '1.000.000' dependent on logged in user culture.
			#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.
			#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.
	#There should be a "Close" button on all pages. Continuously closing windows will lead user to MyPage.		#There should be a "Close" button on all pages. Continuously closing windows will lead user to MyPage.
	#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!		#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!
	#Always use existing controls where possible. It is better to ask for an extension of a control than make a new one yourself.		#Always use existing controls where possible. It is better to ask for an extension of a control than make a new one yourself.
	#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		#The buttons on search dialogues should be 'Search' and 'Cancel'. Please notice examples below of correct and incorrect way
	#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!		#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!

	[[Category:LnF_guidelines]]		[[Category:LnF_guidelines]]

Catglobe at 04:49, 24 December 2008

2008-12-24T04:49:13Z

← Older revision		Revision as of 04:49, 24 December 2008
Line 1:		Line 1:
	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.~~<br>2.~~Avoid unneeded scroll bars.~~<br>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!~~<br>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.~~<br>5.~~The money should be shown as either '1,000,000' or '1.000.000' dependent on logged in user culture.~~<br>6.~~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.~~<br>7.~~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.~~<br>8.~~There should be a "Close" button on all pages. Continuously closing windows will lead user to MyPage. ~~<br>9.~~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! ~~<br>10.~~Always use existing controls where possible. It is better to ask for an extension of a control than make a new one yourself. ~~<br>11.~~All pages must use style sheets. (*)~~<br>12.~~No text or border should move on mouse-over or selection.~~<br>13.~~The buttons on search dialogues should be 'Search' and 'Cancel'. Please notice examples below of correct and incorrect way ~~<br>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! ~~<br>~~		#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.
			#Avoid unneeded scroll bars.
			#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!
			#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.
			#The money should be shown as either '1,000,000' or '1.000.000' dependent on logged in user culture.
			#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.
			#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.
			#There should be a "Close" button on all pages. Continuously closing windows will lead user to MyPage.
			#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!
			#Always use existing controls where possible. It is better to ask for an extension of a control than make a new one yourself.
			#All pages must use style sheets. (*)
			#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
			#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!

	[[Category:~~LnF guidelines~~]]		[[Category:LnF_guidelines]]

← Older revision		Revision as of 11:13, 30 December 2008
Line 7:		Line 7:
	#The money should be shown as either '1,000,000' or '1.000.000' dependent on logged in user culture.		#The money should be shown as either '1,000,000' or '1.000.000' dependent on logged in user culture.
	#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.		#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.
	#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. <br>[[Image:General-7.jpg]] <br>		#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. <br>[[Image:General-7.jpg]] <br><br>
	#There should be a "Close" button on all pages. Continuously closing windows will lead user to MyPage. <br>[[Image:General-8.png]] <br>		#There should be a "Close" button on all pages. Continuously closing windows will lead user to MyPage. <br>[[Image:General-8.png]] <br><br>
	#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! <br>[[Image:General-9.png]] <br>		#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! <br>[[Image:General-9.png]] <br><br>
	#Always use existing controls where possible. It is better to ask for an extension of a control than make a new one yourself.		#Always use existing controls where possible. It is better to ask for an extension of a control than make a new one yourself.
	#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  <br> [[Image:General-13-1.png]]<br> [[Image:General-13-2.png]]<br>		#The buttons on search dialogues should be 'Search' and 'Cancel'. Please notice examples below of correct and incorrect way  <br> [[Image:General-13-1.png]]<br> [[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! <br>[[Image:General-14-1.png]]<br>[[Image:General-14-2.png]]<br>[[Image:General-14-3.png]]<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! <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
			#Non-resource name: Length of a non-resource name must be<br>      +a max length of 256 characters, Ex: alias of report or PQ; OR<br>      +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

	[[Category:LnF_guidelines]]		[[Category:LnF_guidelines]]

← Older revision		Revision as of 09:14, 24 December 2008
Line 1:		Line 1:
	<span style="color: #ff9900">'''General LnF'''</span>		<span style="color: #ff9900">'''General LnF'''</span>

	#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.		#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.
Line 7:		Line 7:
	#The money should be shown as either '1,000,000' or '1.000.000' dependent on logged in user culture.		#The money should be shown as either '1,000,000' or '1.000.000' dependent on logged in user culture.
	#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.		#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.
	#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.		#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. <br>[[Image:General-7.jpg]] <br>
	#There should be a "Close" button on all pages. Continuously closing windows will lead user to MyPage.		#There should be a "Close" button on all pages. Continuously closing windows will lead user to MyPage. <br>[[Image:General-8.png]] <br>
	#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!		#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! <br>[[Image:General-9.png]] <br>
	#Always use existing controls where possible. It is better to ask for an extension of a control than make a new one yourself.		#Always use existing controls where possible. It is better to ask for an extension of a control than make a new one yourself.
	#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		#The buttons on search dialogues should be 'Search' and 'Cancel'. Please notice examples below of correct and incorrect way  <br> [[Image:General-13-1.png]]<br> [[Image:General-13-2.png]]<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!		#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! <br>[[Image:General-14-1.png]]<br>[[Image:General-14-2.png]]<br>[[Image:General-14-3.png]]<br>

	[[Category:LnF_guidelines]]		[[Category:LnF_guidelines]]