[Vm-dev] [commit] r2150 - several changes that weren't checked in

commits at squeakvm.org commits at squeakvm.org
Wed Feb 24 13:23:13 UTC 2010


Author: andreas
Date: 2010-02-24 05:23:12 -0800 (Wed, 24 Feb 2010)
New Revision: 2150

Modified:
   trunk/platforms/win32/docs/compiling.html
   trunk/platforms/win32/docs/index.html
   trunk/platforms/win32/docs/settings.html
Log:
several changes that weren't checked in

Modified: trunk/platforms/win32/docs/compiling.html
===================================================================
--- trunk/platforms/win32/docs/compiling.html	2010-02-11 08:23:28 UTC (rev 2149)
+++ trunk/platforms/win32/docs/compiling.html	2010-02-24 13:23:12 UTC (rev 2150)
@@ -96,19 +96,6 @@
 <a href="http://wiki.squeak.org/squeak/2105">VMMaker</a> and 
 <a href="http://wiki.squeak.org/squeak/2444">VMMakerTool</a>.<p>
 
-First, check that you have a VMMaker version that is applicable for the build 
-structure. The best way to check this is to open a browser and see whether
-Win32VMMaker is a subclass of VMMakerWithFileCopying or just plain old
-VMMaker. If the latter (i.e., VMMaker subclass: #Win32VMMaker) leave
-everything is as is. If the former (i.e., VMMakerWithFileCopying subclass: 
-#Win32VMMaker) do the following:<p>
-<ul>
-<li> <b>REMOVE</b> Win32VMMaker completely. Yes, <b>NUKE IT</b>.
-<li> Load Win32VMMaker from the build directory of the C support code:
-  platforms/win32/build/Win32VMMaker.st
-</ul>
-<p>
-
 If you just want to rebuild the VM use the build location provided by the
 file release you are using. If you do your own development you need to decide
 where to put the build files. You have two choices:<p>

Modified: trunk/platforms/win32/docs/index.html
===================================================================
--- trunk/platforms/win32/docs/index.html	2010-02-11 08:23:28 UTC (rev 2149)
+++ trunk/platforms/win32/docs/index.html	2010-02-24 13:23:12 UTC (rev 2150)
@@ -42,6 +42,8 @@
 
 Specific information about the Win32 VM is available here:
 <ul>
+   <li><a href="custom.html">Building Your Product</a></br>
+   <b>NEW!</b> A complete tutorial for building a custom VM and packaging your product.
    <li><a href="compiling.html">Compiling the Win32 VM</a><br>
    This document discusses the steps to build a Win32 VM for yourself.
    <li><a href="settings.html">Win32 Ini File Settings</a><br>
@@ -52,6 +54,9 @@
 
 General information about the Squeak VM is available here:
 <ul>
+   <li><a href="http://wiki.squeak.org/squeak/6102">A Step-by-Step 
+   guide to create a plugin on Windows</a><br>
+   An updated set of instructions as of december 2008.
    <li><a href="http://www.rowledge.org/tim/squeak/OE-Tour.html">A Tour of 
    the Squeak Object Engine</a><br>
    A must read for the serious VM hacker, it outlines the fundamentals of
@@ -71,8 +76,8 @@
 
 For the <a href="http://www.squeak.org">Squeak.org</a> (SqueakVM) releases:
 <ul>
-  <li> The latest binary release is: <a href="release/SqueakVM-Win32-3.10.5-bin.zip">SqueakVM-Win32-3.10.5-bin.zip</a>. </li>
-  <li> The latest source release is: <a href="release/SqueakVM-Win32-3.10.5-src.zip">SqueakVM-Win32-3.10.5-src.zip</a>. </li>
+  <li> The latest binary release is: <a href="release/SqueakVM-Win32-3.11.5-bin.zip">SqueakVM-Win32-3.11.5-bin.zip</a>. </li>
+  <li> The latest source release is: <a href="release/SqueakVM-Win32-3.11.5-src.zip">SqueakVM-Win32-3.11.5-src.zip</a>. </li>
 </ul>
 
 For the <a href="http://croquetproject.org">CroquetProject.org</a> (CroquetVM) releases:

Modified: trunk/platforms/win32/docs/settings.html
===================================================================
--- trunk/platforms/win32/docs/settings.html	2010-02-11 08:23:28 UTC (rev 2149)
+++ trunk/platforms/win32/docs/settings.html	2010-02-24 13:23:12 UTC (rev 2150)
@@ -116,7 +116,9 @@
     is 1 (true).
     <li> <b>EnableAltF4Quit</b>: This entry allows you to specify whether 
     Alt-F4 (and the windows close button) should be honored or not. 
-    The default is 1 (true).
+    The default is 1 (true).<br>
+    <b>New for 3.10.8:</b>When this setting is disabled (0), the VM generates 
+    a window close event instead which can be handled by the image.
 </ul>
 
 Quit menu:
@@ -140,6 +142,11 @@
     The value is provided in milliseconds.
 </ul>
 
+Single Instance Settings:
+<ul>
+<li> <b>RunSingleApp</b>: When non-zero, only one instance of the VM will be run. A second attempt to launch the app will cause the first instance to be activated. When double-clicking on a file associated with the VM, the document file will be delivered as drop event to the running instance. This is consistent with the Mac behavior when trying to launch multiple documents with the same VM.
+<li> <b>WindowClassName</b>: The name for the window class to be used by the VM (something like "MyAppMainWindowClass"). The VM will only consider windows with this class name when determining whether the app already runs or not. This allows the VM to disambiguate different applications using the Squeak VM.
+</ul>
 
 <p><table bgcolor="#bdd3bd" width="100%">
   <tr><td cellvalign="center" align="center">



More information about the Vm-dev mailing list