Author:halw

Date:2011-01-08T17:30:59.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@727 abb3cda0-5349-4a8f-a601-0c33ac3a8c38

documentation/current/eiffelstudio/eiffelstudio-how-tos/compiling/setting-syntax-variant.wiki

@@ -14,7 +14,7 @@ EiffelStudio project settings supports four of these syntax compilation variants
 Because the language, and by necessity the compilation technology too, may at times be a moving target, it is difficult to give precise definitions of what these variants mean at any given time. Today's valid identifier is tomorrow's keyword and vice versa. 
 
 
-{{Recommended|It's always a good idea to check the [[EiffelStudio release notes]] and [[Differences between standard ECMA-367 and Eiffel Software implementation]] when you install a new version to see if new language elements are supported or existing ones have been made obsolete. }}
+{{Recommended|It's always a good idea to check the [[EiffelStudio release notes]] and [[Differences between standard ECMA-367 and Eiffel Software implementation]] when you install a new version to see if new language elements are supported or existing ones have been made obsolete. <br/><br/>Additionally, you can see more detail on how these variants effect certain words in a particular version by checking the [[Syntax level variant settings by version|syntax level variant settings by version.]]}}
 
 
 Even so, we can use an example from a particular point in time to show the basic idea. At one time, the word '''indexing''' was a keyword, and the word '''note''' was available for use as a valid identifier. But there came a time that due to a consensus of opinion within the Eiffel standards committee, the role of the keyword <code>indexing</code> was replaced by a new keyword <code>note</code>. This meant two things. First that if you had used the keyword <code>indexing</code> in your classes (and who hadn't?), then at some point you would want to change those occurrences to <code>note</code>. Second, if you had used the word '''note''' as an identifier, then at some point you would have to change your code to use a different identifier it its place. 

documentation/current/platform-specifics/microsoft-windows/eiffelribbon/index.wiki

@@ -0,0 +1,28 @@
+[[Property:title|EiffelRibbon]]
+[[Property:weight|2]]
+[[Property:uuid|26bd5ec6-c29a-ac92-b683-39d6bf969b80]]
+{{UnderConstruction}}
+
+
+=Introduction=
+
+EiffelRibbon is a library of classes with an associated tool which allows the integration of the Microsoft Windows "Ribbon" into graphical user interfaces programmed with [[EiffelVision 2]] and targeted to Microsoft Windows. The ribbon is part of a [http://msdn.microsoft.com/en-us/library/aa338198.aspx#office2007uifordevelopers_detaileddesignofthenewuisystem revamped user interface approach] introduced by Microsoft with the 2007 release of the Microsoft Office applications. So you've experienced the ribbon if you've used Microsoft Word, PowerPoint, or Excel from 2007 or later. 
+
+=Current state of development=
+
+Initial distribution:
+:The EiffelRibbon library is not usable directly. The EiffelRibbon tool allows you to design a ribbon and will generate code that relies on the EiffelRibbon library.
+
+:A class <code>EV_RIBBON_TITLED_WINDOW</code> is provided with the library. <code>EV_RIBBON_TITLED_WINDOW</code> is a descendant of the standard EiffelVision 2 class <code>EV_TITLED_WINDOW</code>. The ribbon classes generated by EiffelRibbon tool can be added only to instances of <code>EV_RIBBON_TITLED_WINDOW</code>.
+
+=System requirements=
+
+To use the EiffelRibbon library and tools you must have:
+
+# Windows 7
+# The Microsoft C compiler provided with either:
+## Windows SDK 7.0 or greater
+## Visual Studio 2008 or greater
+
+
+