Hi, I have a few parts that need to handle things differently in Linux than in windows. Up to now I have played with the "Config. Expressions" in the "Application Editions" browser so I could load the Linux sub app and play with those parts. That is a real pain as I forget just how to do it and always have to fumble around until I get it right. How should I be doing this? I'm thinking the answer may be to use Emsrv and work on the Linux parts from a Linux machine? If that is the case, is there a way to change an existing fileio install to Emsrv? Also, if working from on windows parts form windows and Linux parts form Linux, how does everything get version-ed into sub-apps under one app? Lou You received this message because you are subscribed to the Google Groups "VA Smalltalk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. To post to this group, send email to [hidden email]. Visit this group at http://groups.google.com/group/va-smalltalk. For more options, visit https://groups.google.com/d/optout. |
Administrator
|
On Thursday, March 20, 2014 6:42:09 AM UTC-7, Louis LaBrunda wrote:
--
In general, you cannot do too much with components designed for another platform. There are special cases in which you could hack the system to allow you to load the sub-application and edit its classes and methods. But it would be very unlikely that you could test them as you change them, so I think I'll fall back on the "it's not a good idea" answer. :-) In many cases, you cannot even load the sub-application because it defines classes or methods that already exist from the corresponding Windows-specific sub-application.
That is almost trivial. Of course, you need to run emsrv somewhere that is accessible by both machines. That's not hard, as emsrv is a very light process from all I have seen. Install it and run it as a Windows service, if the majority of your development work in on Windows. But I am suggesting that just for convenience. You could run it on any supported platform that remains available and is LAN linked. (WAN performance is bad, as you've no doubt heard.) The second step is to edit your ini file. You need to specify the name of the server running emsrv. In my case, it is ServerAddress=localhost. Likewise, the DefaultName needs to refer to the path of the repository file on the emsrv machine. Because I am running Windows, my path is simple: DefaultName=C:\Program Files (x86)\Instantiations\VA Smalltalk\8.5.2\manager\mgr85.dat. If I were to develop something on Linux, my ini file would still specify the same path, as the emsrv runs on the Windows machine. Likewise, if you run emsrv on a *nix machine, the path is going to be a *nix-style path, even if the file lives on a Windows system. It is emsrv's perspective that matters. Example from one of my images: [EmLibraryInterface] ; DefaultName: This is the full path (including the filename itself) of the ; manager library. The path must be one reachable by the manager ; server's file system. ; ServerAddress: This is the host name (or dotted address) of the server ; machine that provides access to the manager library. ; Leave this blank for FileI/O. DefaultName=C:\Program Files (x86)\Instantiations\VA Smalltalk\8.5.2\manager\mgr85.dat ServerAddress=localhost OpenReadOnly=false
In general, I recommend releasing newly opened sub-applications to their parent as soon as you open them. You can do this from the separate images or from the editions browser, as you have mentioned. (Create the new edition of the sub-application by browsing its editions and selecting the edition you want to base from. Theer is a Create Edition menu there.) Release applications to their configuration maps also when they are newly opened, as well. Ditto for releasing required maps into their requiring map's edition. It really doesn't make a difference when you open an edition of a platform-specific sub-application. In general, I would suggest you do it when you are working on the relevant platform so you know that you really need to open a given sub-application edition. You received this message because you are subscribed to the Google Groups "VA Smalltalk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. To post to this group, send email to [hidden email]. Visit this group at http://groups.google.com/group/va-smalltalk. For more options, visit https://groups.google.com/d/optout. |
Hi Richard, Thanks for all the info. I am now setup running Emsrv as an NT service. I haven't connected to it from Ubuntu yet but will soon. Lou You received this message because you are subscribed to the Google Groups "VA Smalltalk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. To post to this group, send email to [hidden email]. Visit this group at http://groups.google.com/group/va-smalltalk. For more options, visit https://groups.google.com/d/optout. |
Free forum by Nabble | Edit this page |