[Esbox-commits] r2219 - in www/2nd_edition: . images/vm
eswartz at garage.maemo.org
eswartz at garage.maemo.org
Wed Sep 23 21:31:51 EEST 2009
Author: eswartz
Date: 2009-09-23 21:31:49 +0300 (Wed, 23 Sep 2009)
New Revision: 2219
Added:
www/2nd_edition/images/vm/esbox-launch-vm-bad-network.png
www/2nd_edition/images/vm/esbox-launch-vm-expanded.png
www/2nd_edition/images/vm/esbox-launch-vm.png
www/2nd_edition/images/vm/esbox-launching-vm-expanded.png
www/2nd_edition/images/vm/esbox-launching-vm.png
www/2nd_edition/images/vm/esbox-shut-down-vm.png
Modified:
www/2nd_edition/images/vm/prefs-esbox-build-machines-machine-access.png
www/2nd_edition/images/vm/prefs-esbox-build-machines-qemu.png
www/2nd_edition/images/vm/prefs-esbox-build-machines-shared-folders.png
www/2nd_edition/images/vm/prefs-esbox-build-machines-virtualbox.png
www/2nd_edition/images/vm/prefs-esbox-build-machines-vmware.png
www/2nd_edition/images/vm/prefs-esbox-build-machines.png
www/2nd_edition/release_integration.html
www/2nd_edition/virtual_machines.html
Log:
Update notes for release
Added: www/2nd_edition/images/vm/esbox-launch-vm-bad-network.png
===================================================================
(Binary files differ)
Property changes on: www/2nd_edition/images/vm/esbox-launch-vm-bad-network.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: www/2nd_edition/images/vm/esbox-launch-vm-expanded.png
===================================================================
(Binary files differ)
Property changes on: www/2nd_edition/images/vm/esbox-launch-vm-expanded.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: www/2nd_edition/images/vm/esbox-launch-vm.png
===================================================================
(Binary files differ)
Property changes on: www/2nd_edition/images/vm/esbox-launch-vm.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: www/2nd_edition/images/vm/esbox-launching-vm-expanded.png
===================================================================
(Binary files differ)
Property changes on: www/2nd_edition/images/vm/esbox-launching-vm-expanded.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: www/2nd_edition/images/vm/esbox-launching-vm.png
===================================================================
(Binary files differ)
Property changes on: www/2nd_edition/images/vm/esbox-launching-vm.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: www/2nd_edition/images/vm/esbox-shut-down-vm.png
===================================================================
(Binary files differ)
Property changes on: www/2nd_edition/images/vm/esbox-shut-down-vm.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Modified: www/2nd_edition/images/vm/prefs-esbox-build-machines-machine-access.png
===================================================================
(Binary files differ)
Modified: www/2nd_edition/images/vm/prefs-esbox-build-machines-qemu.png
===================================================================
(Binary files differ)
Modified: www/2nd_edition/images/vm/prefs-esbox-build-machines-shared-folders.png
===================================================================
(Binary files differ)
Modified: www/2nd_edition/images/vm/prefs-esbox-build-machines-virtualbox.png
===================================================================
(Binary files differ)
Modified: www/2nd_edition/images/vm/prefs-esbox-build-machines-vmware.png
===================================================================
(Binary files differ)
Modified: www/2nd_edition/images/vm/prefs-esbox-build-machines.png
===================================================================
(Binary files differ)
Modified: www/2nd_edition/release_integration.html
===================================================================
--- www/2nd_edition/release_integration.html 2009-09-23 16:31:18 UTC (rev 2218)
+++ www/2nd_edition/release_integration.html 2009-09-23 18:31:49 UTC (rev 2219)
@@ -53,24 +53,81 @@
integration releases here.</a></p>
-<h3 id="heading"><a name="I2009xxxx">ESbox 2.0.0-I2009xxxx</a></h3>
+<h3 id="heading"><a name="I20090923">ESbox 2.0.0-I20090923</a></h3>
<ul>
+<li>Added Qt build support, plus template projects for C/C++ and Python (PyQt4
+and PySide) to the product. You can install packages for these during the project
+wizard or using Validate Installed Packages.
+<p>
+Currently you may only have one *.pro file in the root of your project, and this will be converted to
+a Makefile using qmake. There is no way to configure this. (If you want full control and
+want to avoid letting Mica recreate the Makefile,
+turn off the "Mica QMake Project Builder" from <tt>Project > Properties > Builders</tt> and
+run <tt>qmake</tt> yourself.)
+</p>
+<p>Note: currently the required plugins seem to be missing from the Mica repository.
+Use the full ESbox product archive in the meantime.
+</p>
+<p>
+Note: Python support for Qt is quite unstable in both Diablo and Fremantle due to
+shifting APIs and other vagaries. I couldn't find any less-than-dead-simple test
+programs that successfully launched for both frameworks. You're on your own :)
+</p>
+See:
+<ul>
+<li><a href="http://pyqt.garage.maemo.org/">PyQt4 (Python for Maemo 4)</a>
+</li>
+<li><a href="http://www.pyside.org/">PySide (Python for Maemo 5)</a>
+</li>
+</ul>
+</li>
+<li>Fixed: Usability problems with first configuring a new virtual machine
+<a href="https://garage.maemo.org/tracker/index.php?func=detail&aid=4009&group_id=192&atid=1420">[#4009]</a>
+<a href="https://garage.maemo.org/tracker/index.php?func=detail&aid=4595&group_id=192&atid=1420">[#4595]</a>
+<p>The process of setting up a virtual machine, as well as launching it and diagnosing problems,
+should be much improved.</p>
+<p>ESbox no longer silently launches a VM, or worse, kills a VM when it
+is not configured properly. It will always ask whether to launch, and indicates whether it
+thinks the problem is that the VM engine is not running or that the network settings might
+be incorrect. This solves frustrating problems where ESbox keeps launching a machine you
+don't want (and also helped diagnose a bug where the previous machine would still be launched
+when you were changing machines).</p>
+<p>Also, fixed an issue in not properly detecting whether VMware was running on Mac OS X.
+</p>
+<p>When launching a machine, a progress dialog is always displayed rather than waiting for
+a minute, and the "look here" help is collapsed as well
+to avoid giving the impression that there is an error.
+</p>
+<p>Also, in the "Build Machines" UI, the "Apply and Validate" button is now
+"Validate", so you can test changes to an unsaved machine without triggering side effects in
+the rest of the IDE.
+</p>
+</li>
<li>Fixed: Hover help local- local/remote update fails
<a href="https://garage.maemo.org/tracker/index.php?func=detail&aid=4510&group_id=192&atid=1420">[#4510]</a>
</li>
<li>Fixed: Building debian package for template projects does not work on MacOS
-(more specifically, you couldn't create the Debian structure in the Shared Library
-template because the original fix for this bug introduced softlinks that pointed to themselves)
<a href="https://garage.maemo.org/tracker/index.php?func=detail&aid=3955&group_id=192&atid=1420">[#3955]</a>
+<p>More specifically, you couldn't create the Debian structure in the Shared Library
+template because the original fix for this bug introduced softlinks that pointed to themselves.</p>
</li>
<li>Fixed: Python Project: Fails to build debian package
<a href="https://garage.maemo.org/tracker/index.php?func=detail&aid=3358&group_id=192&atid=1420">[#3358]</a>
<p>This was fixed in Mica by adding extensions for Python-specific support; see more details there.</p>
</li>
+<li>Fixed: Maemo 5 template projects, enhancement for "debianization"
+<a href="https://garage.maemo.org/tracker/index.php?func=detail&aid=4561&group_id=192&atid=1420">[#4561]</a>
+</li>
+<li>Fixed: VirtualBox config: offer to set up port forwarding for NAT
+<a href="https://garage.maemo.org/tracker/index.php?func=detail&aid=4490&group_id=192&atid=1420">[#4490]</a>
+</li>
+<li>Fixed: Cygwin X failed to restart
+<a href="https://garage.maemo.org/tracker/index.php?func=detail&aid=4535&group_id=192&atid=1420">[#4535]</a>
+</li>
</ul>
<p>
-See <a href="http://mica.garage.maemo.org/2nd_edition/release_integration.html#I2009xxxx">Mica changes here</a>.
+See <a href="http://mica.garage.maemo.org/2nd_edition/release_integration.html#I20090923">Mica changes here</a>.
</p>
Modified: www/2nd_edition/virtual_machines.html
===================================================================
--- www/2nd_edition/virtual_machines.html 2009-09-23 16:31:18 UTC (rev 2218)
+++ www/2nd_edition/virtual_machines.html 2009-09-23 18:31:49 UTC (rev 2219)
@@ -1,6 +1,8 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head>
+
+
@@ -10,8 +12,8 @@
- <meta http-equiv="content-type" content="text/html; charset=utf-8">
- <title>ESbox Virtual Machines</title>
+ <meta http-equiv="content-type" content="text/html; charset=utf-8"><title>ESbox Virtual Machines</title>
+
@@ -50,11 +52,7 @@
- <link rel="shortcut icon" href="images/favicon.ico">
-
-
-
-</head><body>
+ <link rel="shortcut icon" href="images/favicon.ico"></head><body>
<script type="text/javascript">
var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
@@ -139,7 +137,7 @@
VM over a shared
folder. (This choice exposes occasional problems when Unix filesystem
semantics are not fully emulated over shares, and is a little slower
-than native filesystem builds. Butwe chose to optimize for ease
+than native filesystem builds. But we chose to optimize for ease
of Eclipse integration and speed of IDE/editor/debugger-time activity
over build-time activity.) <br>
</p>
@@ -262,14 +260,18 @@
</li>
<li>
- After closing the dialog, use the <em>Apply</em> button to accept the changes and immediately
- launch the virtual machine.
- </li>
-<li>
- Use the <em>Apply and Validate</em> button to apply the changes
- and launch the machine, and immediately run through a
- series of tests to validate that the machine is configured properly.</li></ul>
+ Use the <em>Validate</em> button to launch the machine or find a running instance and run through a
+ series of tests to validate that the machine is configured properly.</li>
+<li>After closing the dialog, use the <em>Apply</em> button to accept the changes and launch the virtual machine if needed.</li></ul>
+<p>If you have previously configured a Build Machine and have changed the settings, ESbox may present this dialog:</p>
+<p><img src="images/vm/esbox-shut-down-vm.png" alt=""></p>
+<p>If the machine and disk are the same as the running machine, and you
+are just synchronizing network settings, you may be able to leave it
+running. In any event, the supported VM engines themselves will not be
+able to write to the same disk images opened by another engine. <br>
+</p>
+
<h4>More details</h4>
<p>The Machine Access tab allows you to configure the networking and
@@ -301,7 +303,15 @@
</li><li>For VMware, the port must be configured using the Virtual
Network Editor > NAT > Edit >
Port Forwarding... dialog. Redirect SSH by adding an <em>Incoming TCP port</em> entry with <em>Host Port</em> 22, <em>Virtual Machine Address</em> matching the Target Address,
-and a <em>Port</em> like 2222 or 2244 matching the Target SSH Port setting.</li>
+and a <em>Port</em> like 2222 or 2244 matching the Target SSH Port setting.
+<p>Note: in Windows VMware, if the VMnet1 and VMnet8 devices are not enabled or do not
+work as expected, be sure they are associated with TCP/IP services. In some situations these can
+remain unconfigured. Go to <strong>Control Panel >
+Network Connections</strong> and bring up <strong>Properties</strong> for
+"VMware Virtual Ethernet Adapter for ...".
+In the "General" tab, under "This connection uses the following items:", enable "Internet Protocol (TCP/IP)".
+</p>
+</li>
<li>Note: if you use both VirtualBox and VMware, be sure
to use different SSH ports when enabling port forwarding; otherwise
they will conflict.</li>
@@ -405,21 +415,47 @@
<h3 id="heading">ESbox Virtual Machine Behavior</h3>
-<p>ESbox will accept any running virtual machine responding to the target
-address and port in the current Machine Access settings (it
-doesn't have to be the specific one you have selected). If no machine
-responds to the target address and port, then ESbox will launch the
-configured machine.<br>
+<p>ESbox will connect to any running virtual machine that responds to
+the configured target address and SSH port in the Machine Access
+settings (it
+doesn't have to be the specific engine you have selected). <br>
+</p>
+<p>If no machine
+responds to the target address and port, and ESbox detects the virtual
+machine is not running, then it will prompt you to launch the
+configured machine:</p>
+<p><img src="images/vm/esbox-launch-vm.png" alt="">
</p>
+
+<p>If the virtual machine is running, but the target can't be
+contacted, it presents this variant, which indicates the network
+settings are probably incorrect:</p>
+<p><img src="images/vm/esbox-launch-vm-bad-network.png" alt=""></p>
+<p>Both dialogs allow you to launch the virtual machine anew or take
+one of the actions under "Help" (which will cancel the current
+operation) and let you look for other solutions.<br>
+</p>
+
<p>
Usually, only an explicit user action (like starting a wizard or viewing ESbox or Maemo
preference panels) will require the VM to be running.</p>
-<p>ESbox will attempt to restart the virtual machine if it detects that the machine has been terminated.</p>
+<p>While the VM is launching, this dialog is shown:</p>
+<br>
+<p><img src="images/vm/esbox-launching-vm.png" alt=""></p>
+<p>The dialog will remain for a few seconds after boot time. You
+may expand it in case the machine has booted but the dialog remains:</p>
+<br>
+<p><img src="images/vm/esbox-launching-vm-expanded.png" alt=""></p>
+<p>Closing this dialog will not cancel any operation. It is only
+informative, to help you look for common problems and solutions while
+configuring the machine.<br>
+</p>
+
<p id="indexing">
</p>
@@ -668,7 +704,7 @@
<li>Eclipse sometimes triggers builds for all projects in the
workspace, which may be a problem if you are using other products in
your installation and do not want to
-launch the VM automatically. <br>
+be prompted to launch the VM. <br>
</li><li>The easiest solution is to switch the <em>Build Machine</em> to <em>None</em>.
(With this setting, you will not be able to use most ESbox actions,
since no installed targets except for Remote Connections will be
More information about the Esbox-commits
mailing list