CVS commit by englich: A cleanup & corrections commit: * Normalized space and auto indented 4 spaces * Bloopers pointed about by Maksim: * Copyright stretches back to 1999 now * HIG->UIG * Forgot to mention before: I've moved out "Open for Discussion" sections to the TODO file. They've been there for quite long now. * XSL template for making guimenu & guimenuitemS use tt font * More spell checking/small fixes, and the never ending markuping (the readability edit patch was committed yesterday) Except for PDF generation, which will come in the future, this is feature complete. --- Here's a summary of the framework for those who will work with it and extend the guidelines: The main page is: www/areas/usability/hig When `make xhtml` is run in the above directory, the docbook source in: www/areas/usability/hig/src is generated into php, in a directory depending on a variable in the Makefile. Currently it is generated into: www/areas/usability/hig/current Good reads for infilitrating are: www/areas/usability/hig/current/{Makefile,README,src/GUIDELINES} (www/areas/usability/ == usability.kde.org/) Previous commits: http://lists.kde.org/?l=kde-cvs&m=109287817221751&w=2 http://lists.kde.org/?l=kde-cvs&m=109310487224905&w=2 If there's any details or information I can provide, I should be quickly accessible via mail. Also, feel free to CC this mail to anyone it may be of interest for. --- My plan is to cvs tag hig/src, and then generate a version 1.0 of the UIG into hig/1.0. In this way, we have a readable, accessible, _stable_ document for development, while aKademy people and all other interested can together work on a new version in hig/src which will be generated into hig/current. Safe, practical and flexible. My intentions is also make the old location redirect to the new one, and make it accessible via the usability.kde.org menu. Generating the 1.0 version will probably first be done when people decide to add actually add new content(in order to get as many fixes in as possible). However, all this depends on people's reactions. If there's a better way this can be done/timed/whatever, it is of course important to do that instead. All I know is what have been mentioned on KDE's lists(and related news/blog sites). Aaron, you've expressed strong opinions about this project -- this is a great opportunity to provide feedback so it doesn't crash with anything else you might know about. Frans CCMAIL: kde-usability@kde.org M +1 -1 Makefile 1.3 M +1 -1 README 1.2 M +24 -34 current/dnd-drag.php 1.3 M +29 -38 current/dnd-drop.php 1.3 M +15 -20 current/dnd.php 1.3 M +1 -1 current/index.php 1.3 M +258 -252 current/input-keyboard.php 1.3 M +176 -61 current/input-mouse.php 1.3 M +13 -16 current/introduction.php 1.3 M +7 -10 current/ln-legalnotice.php 1.2 M +37 -71 current/menus-menubar.php 1.3 M +356 -311 current/menus-standard.php 1.3 M +15 -22 current/principles.php 1.3 M +109 -100 current/system-processes.php 1.3 M +40 -67 current/system-settings.php 1.3 M +34 -32 current/visual-text.php 1.3 M +26 -11 current/widgets-systray.php 1.3 M +297 -378 current/windows-dialogs.php 1.3 M +90 -120 current/windows-parts.php 1.3 M +238 -276 current/windows-sdi.php 1.3 M +6 -1 current/windows-size.php 1.3 M +6 -11 current/windows.php 1.3 M +111 -151 src/dnd.xml 1.3 M +1690 -1244 src/input.xml 1.3 M +16 -27 src/introduction.xml 1.3 M +38 -41 src/kdehig.xml 1.2 M +1150 -1060 src/menus.xml 1.3 M +16 -42 src/principles.xml 1.3 M +284 -315 src/system.xml 1.3 M +144 -110 src/visual.xml 1.3 M +34 -30 src/widgets.xml 1.3 M +1101 -1481 src/windows.xml 1.3 M +5 -0 stylesheets/xhtml.xsl 1.4 R TODO 1.1.1.1 _______________________________________________ kde-usability mailing list kde-usability@kde.org https://mail.kde.org/mailman/listinfo/kde-usability