<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br style="font-size: 8px; "><div style="font-size: 8px; "><div style="font-size: 8px; ">On 27 Jan 2010, at 16:31, keith wrote:</div><div style="font-size: 8px; "><br></div><br class="Apple-interchange-newline" style="font-size: 8px; "><br><blockquote type="cite" style="font-size: 8px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 8px; "><div style="font-size: 8px; "><blockquote type="cite" style="font-size: 8px; "><div style="font-size: 13px; ">John wrote:</div></blockquote></div></div></blockquote><br><blockquote type="cite" style="font-size: 8px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 8px; "><div style="font-size: 8px; "><blockquote type="cite" style="font-size: 8px; "><div style="font-size: 13px; ">So remind me why you want to do this. <br></div></blockquote><div style="font-size: 13px; "><br></div><span class="Apple-style-span" style="font-size: 13px; ">I wanted to be able to distribute a vm for Cuis, which is cross platform, and runs with a different icon and name in the menubar. The idea being to distribute everything except the image/changes, as a single zip file. The fact that it doesn't pick up the sources file from anywhere within the .app package, put the spanner in the works, but you have pointed me in the right direction.</span></div><div style="font-size: 8px; "><font class="Apple-style-span" size="6" style="font-size: 15px; "><span class="Apple-style-span" style="font-size: 13px; "><br></span></font></div><div style="font-size: 8px; "><font class="Apple-style-span" size="6" style="font-size: 15px; "><span class="Apple-style-span" style="font-size: 13px; ">The image/changes file can be combined into one if one felt the need, so Cuis becomes "normal" in the sense of having a document (the image) and an application.</span></font></div><div style="font-size: 8px; "><br style="font-size: 13px; "><blockquote type="cite" style="font-size: 13px; "><div>The one-click plugins are usually assembled by a third party and contain a mixture of things, there could be or could not be the most recent plugins, or VM in the set of folders. <br>On the macintosh the info.plist could be altered and not actually have a version number that matches what version the VM is. <br></div></blockquote><div style="font-size: 8px; "><br style="font-size: 8px; "></div><div style="font-size: 8px; "><span class="Apple-style-span" style="font-size: 13px; ">Secondly once I have this "universal vm" under scm with bazaar, I can keep it up to date easily everywhere it is deployed, irrespective of what vms are installed on the base machine.</span></div><div style="font-size: 8px; "><font class="Apple-style-span" size="6" style="font-size: 15px; "><span class="Apple-style-span" style="font-size: 13px; "><br></span></font></div><div style="font-size: 8px; "><font class="Apple-style-span" size="6" style="font-size: 15px; "><span class="Apple-style-span" style="font-size: 13px; ">Thirdly, using bazaar, we have a starting point for users to branch, forming derived vms, with different plugins, different icons for the dock, or classic one-click behaviour with the image/changes included. The branch can continue to merge in updates as they occur.</span></font></div><div style="font-size: 8px; "><font class="Apple-style-span" size="6" style="font-size: 15px; "><span class="Apple-style-span" style="font-size: 13px; "><br></span></font></div><div style="font-size: 8px; "><font class="Apple-style-span" size="6" style="font-size: 15px; "><span class="Apple-style-span" style="font-size: 13px; ">Finally, the ./Contents/Resources folder is looking pretty cluttered, and I tend to have enough clutter of my own. So I wanted to be able to have the working directory alongside the vm.app , or just inside it for one-click behaviour.</span></font></div><div style="font-size: 8px; "><br style="font-size: 8px; "></div><blockquote type="cite" style="font-size: 13px; "><div>However if you wish to stuff the sources in the *.app/Contents/Resources you would have to change the Smalltalk code where it hunts for the sources file and have it hunt <br>where you think the sources file should be. This is not a function of the VM, it's a Smalltalk code problem. <br></div></blockquote></div></div></blockquote><div style="font-size: 8px; "><br></div><div style="font-size: 8px; "><div><div><div><font class="Apple-style-span" color="#144FAE" size="3"><span class="Apple-style-span" style="font-size: 13px;">Unfortunately, I don't know where the sources should be, because there appears to be no function that will tell you the path into the .app tree which is where I wanted to put them. #primVmPath tells you the parent directory, but not the name of the .app</span></font></div><div><font class="Apple-style-span" color="#144FAE" size="3"><span class="Apple-style-span" style="font-size: 13px;"><br></span></font></div><div><font class="Apple-style-span" color="#144FAE" size="3"><span class="Apple-style-span" style="font-size: 13px;">any ideas?</span></font></div><div><font class="Apple-style-span" color="#144FAE" size="3"><span class="Apple-style-span" style="font-size: 13px;"><br></span></font></div><div><font class="Apple-style-span" color="#144FAE" size="3"><span class="Apple-style-span" style="font-size: 13px;">Keith</span></font></div></div></div></div></div></body></html>