February 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Newbie question deploying smalltalk applications

by Stan Shepherd

Hi Nathan, you may find these useful also http://wiki.squeak.org/squeak/3563 http://wiki.squeak.org/squeak/3563 http://n4.nabble.com/deploying-Squeak-applications-td110272.html#a110272 http://n4.nabble.com/deploying-Squeak-applications-td110272.html#a110272 I think the info in those remains valid. Cheers, ...Stan -- View this message in context: http://n4.nabble.com/Newbie-question-deploying-smalltalk-applications-tp146… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Feb. 4, 2010

Re: [Pharo-project] Newbie question deploying smalltalk applications

by Mariano Martinez Peck

> To reduce the size of the image I would also clear > Monticello caches, throw out unused Form instances, ... > There are many tricks here - depends on how far you want > to go. Google for "Squeak" and "shrinking" and you will find more. > > The best way I know how to do that is evaluate "ScriptLoader new cleanUpForProduction" Thanks Torsten for this wonderful tutorial. I have created a wiki page for it, and I formatted for the wiki: http://code.google.com/p/pharo/wiki/HowToDeployAnApplication Feel free to edit it :) Mariano

Feb. 4, 2010

Re: [Pharo-project] Latest Polymorph

by Mariano Martinez Peck

2010/2/4 GARY CHAMBERS <gazzaguru2(a)btinternet.com> > There is a new version of Polymorph on SqueakSource > (Polymorph-Widgets-gvc.103) that supports a background morph for the world > that resizes with the main window. > > I guess the backgroundSketch/Form stuff can be removed (I reused the > backgroundMorph inst var - no direct way of setting did remain, accessors > now). > > This can be used for background images (as requested): > > E.g. > > World backgroundMorph: > ((UITheme builder > newAlphaImage: (ImageReadWriter formFromFileNamed: 'Watery 2.jpg') help: > nil) > autoSize: false; > layout: #scaled; > lock) > > (AlphaImageMorph supports a few layout positions/tiling/scaling, more could > be added like aspect-maintaining scaling etc.) > > Gary: let me say it: you are my hero!!!! hahahaha Please please please can someone with a notebook and a good screen test this with the Pharo picture I used in the RC2? I attach here the picrture. Please tell me if it works so that to know if I continue including it or not. > Or could be helpful for deployed applications... set the background morph > to your main UI morph, for instance. > Thanks cool. There is just someone in another thread that is asking for something similar to this :) > > Regards, Gary > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 4, 2010

[Pharo-project] Latest Polymorph

by GARY CHAMBERS

There is a new version of Polymorph on SqueakSource (Polymorph-Widgets-gvc.103) that supports a background morph for the world that resizes with the main window. I guess the backgroundSketch/Form stuff can be removed (I reused the backgroundMorph inst var - no direct way of setting did remain, accessors now). This can be used for background images (as requested): E.g. World backgroundMorph: ((UITheme builder newAlphaImage: (ImageReadWriter formFromFileNamed: 'Watery 2.jpg') help: nil) autoSize: false; layout: #scaled; lock) (AlphaImageMorph supports a few layout positions/tiling/scaling, more could be added like aspect-maintaining scaling etc.) Or could be helpful for deployed applications... set the background morph to your main UI morph, for instance. Regards, Gary

Feb. 4, 2010

Re: [Pharo-project] Newbie question deploying smalltalk applications

by StÃ©phane Ducasse

excellent! Stef On Feb 4, 2010, at 12:07 PM, Torsten Bergmann wrote: > If you want to deploy a source package for others to consume just use > Monticello and SqueakSource. But I think you talk about deploying > to an end user (commercial product, ...) not about making code > available for other pharo developers. > > > So how to deploy a "consumer" app with Pharo: > ============================================= > As always that depends on kind of application and the target system > you want to deploy to. > Typically you distribute an image with the running/prepared > application together with the VM for the target platform: > > First the VM > ============ > > Some scenarios: > > A. If you have written a seaside web application you can deploy > the image/VM on your own root server or on a seaside hosting > platform (like www.seasidehosting.com) There is a good > description in the seaside book [1]. > > Thats an easy deployment since you just have to tell your > customer a URL where the app runs. > > B. If you want to deploy to iPhone just ask John McIntosh > how he packaged the app (iphone vm + image) for the Apple Store > Since the memory is limited you may have to reduce the image > size (unload packages, ...) with an own custom shrinking script > > C. If you want to deploy a desktop like app/or web app to > multiple platforms use the one click distribution since there > are already VM's for Linux, Win, Mac. Just exchange the image > with your own one. Have a look at the piercms.com application > or the seaside image. They use this kind of deployment with a ZIP. > > D. If you deploy to windows (Win32 only) you may want to > be closer to Windows app rules - so you may want to build a > custom Win VM executable (*.exe) with your own icons and a > platform specific installer copying the image and VM. > > See [2] how to do that. The Pharo Win32 Installer is built > this way. If you think VM building is rocket science > you can also exchange the icons using reshacker [3] in > a standard Pharo windows VM. > > And the image > ============= > > Anything other depends on how you prepare the image. Typically > you may want to > > 1. Reduce the image size by throwing out anything that > is not required by your app and which is useless for your > customer (unit tests, dev tools). > > This process is called "shrinking" an image. Take care since it > is often usefull to keep dev tools inside since you can easily > debug a failure situation at your customers place later. > At least you typically may want to disable developer facilities, > implement a different walkback window so the customer gets > a notification instead of a "debug it" button and so on, ... > > To reduce the size of the image I would also clear > Monticello caches, throw out unused Form instances, ... > There are many tricks here - depends on how far you want > to go. Google for "Squeak" and "shrinking" and you will find more. > > If size doesnt matter just use the image as it is or > use a pharo-dev image for development and a pharo-core image > for deployment. > > 2. However - typically you just want to deploy the VM only together > with the image, no changes and source file necessary for your > customer. > Therefore you may want to disable the two preferences > "warnIfNoSourcesFile" and "warnIfNoChangesFile" (see [2]) before > saving the image. So you dont have to redistribute the changes > and source files > > 3. Open your application, either manually or by a custom launcher > and the startup list (see [2]) > > 4. Save your image in this predefined "ready" state so when the > customer starts the image with the VM he can instantly use > your app. > > So "deployment" in Smalltalk is different and a little bit more > complicated since you have many options. > > It would help if you would tell us a little bit more so we > can answer specific questions... > > Bye > Torsten > > > [1] http://book.seaside.st/book/advanced/deployment > [2] http://squeakvm.org/win32/custom.html > [3] http://angusj.com/resourcehacker/ > > -- > GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Feb. 4, 2010

Re: [Pharo-project] Do you want to discuss about papers?

by Esteban Lorenzano

+1 On 2010-02-04 06:29:42 -0300, Serge Stinckwich <serge.stinckwich(a)gmail.com> said: > 2010/2/4 Mariano Martinez Peck > <marianopeck(a)gmail.com>: >> Ok....I need to host and create the mailing-list somewhere where I can have >> admin access and where we can trust and that has maitainance. The best place >> I have right now to do that is fgorge, from INRIA. Here the mailing-lists >> are inside projects, for example, Pharo. Then, the mailing-lists you create >> inside these projects have to follow the name: >> "pharo-XXX(a)lists.gforge.inria.fr" >> >> So, it will be >> pharo-research-smalltalk(a)lists.gforge.inria.fr I >> >> can change the name of the group after, I think, but not the mail. >> >> Although we WON'T discuss about forks or dialects and we WON'T be coupled to >> Pharo. We will be able to discuss ANY smalltalk dialect. >> >> Are you agree? > > I think it's not a good idea to make a link between pharo and > smalltalk-research. > Why not using google groups ? It's very easy to do and you can > subscribe to the mailing-list or read the messages on the web. > > http://groups.google.com/

Feb. 4, 2010

[Pharo-project] Newbie question deploying smalltalk applications

by Torsten Bergmann

If you want to deploy a source package for others to consume just use Monticello and SqueakSource. But I think you talk about deploying to an end user (commercial product, ...) not about making code available for other pharo developers. So how to deploy a "consumer" app with Pharo: ============================================= As always that depends on kind of application and the target system you want to deploy to. Typically you distribute an image with the running/prepared application together with the VM for the target platform: First the VM ============ Some scenarios: A. If you have written a seaside web application you can deploy the image/VM on your own root server or on a seaside hosting platform (like www.seasidehosting.com) There is a good description in the seaside book [1]. Thats an easy deployment since you just have to tell your customer a URL where the app runs. B. If you want to deploy to iPhone just ask John McIntosh how he packaged the app (iphone vm + image) for the Apple Store Since the memory is limited you may have to reduce the image size (unload packages, ...) with an own custom shrinking script C. If you want to deploy a desktop like app/or web app to multiple platforms use the one click distribution since there are already VM's for Linux, Win, Mac. Just exchange the image with your own one. Have a look at the piercms.com application or the seaside image. They use this kind of deployment with a ZIP. D. If you deploy to windows (Win32 only) you may want to be closer to Windows app rules - so you may want to build a custom Win VM executable (*.exe) with your own icons and a platform specific installer copying the image and VM. See [2] how to do that. The Pharo Win32 Installer is built this way. If you think VM building is rocket science you can also exchange the icons using reshacker [3] in a standard Pharo windows VM. And the image ============= Anything other depends on how you prepare the image. Typically you may want to 1. Reduce the image size by throwing out anything that is not required by your app and which is useless for your customer (unit tests, dev tools). This process is called "shrinking" an image. Take care since it is often usefull to keep dev tools inside since you can easily debug a failure situation at your customers place later. At least you typically may want to disable developer facilities, implement a different walkback window so the customer gets a notification instead of a "debug it" button and so on, ... To reduce the size of the image I would also clear Monticello caches, throw out unused Form instances, ... There are many tricks here - depends on how far you want to go. Google for "Squeak" and "shrinking" and you will find more. If size doesnt matter just use the image as it is or use a pharo-dev image for development and a pharo-core image for deployment. 2. However - typically you just want to deploy the VM only together with the image, no changes and source file necessary for your customer. Therefore you may want to disable the two preferences "warnIfNoSourcesFile" and "warnIfNoChangesFile" (see [2]) before saving the image. So you dont have to redistribute the changes and source files 3. Open your application, either manually or by a custom launcher and the startup list (see [2]) 4. Save your image in this predefined "ready" state so when the customer starts the image with the VM he can instantly use your app. So "deployment" in Smalltalk is different and a little bit more complicated since you have many options. It would help if you would tell us a little bit more so we can answer specific questions... Bye Torsten [1] http://book.seaside.st/book/advanced/deployment [2] http://squeakvm.org/win32/custom.html [3] http://angusj.com/resourcehacker/ -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

Feb. 4, 2010

Re: [Pharo-project] Newbie question deploying smalltalk applications

by StÃ©phane Ducasse

I asked oscar and we will put drafts of some cool chapters on the web :) BTW everybody is welcome to write. I like the idea of simon to get a living book. Stef On Feb 4, 2010, at 11:00 AM, George Herolyants wrote: > 2010/2/4 Mariano Martinez Peck <marianopeck(a)gmail.com>: >> Uffff sorry Thanks for checking George :) >> >> I was almost sure there was a chapter...maybe I am confusing with PBE2 which >> is in development. > > Sorry me :) It looks like I pick on your words. I checked only chapter > titles and completely forgot about sections :) But it's not a question > of terminology :). You were right, there is enough information about > Monticello. Sorry again. > > George > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Feb. 4, 2010

Re: [Pharo-project] Newbie question deploying smalltalk applications

by George Herolyants

2010/2/4 Mariano Martinez Peck <marianopeck(a)gmail.com>: > Uffff sorry Thanks for checking George :) > > I was almost sure there was a chapter...maybe I am confusing with PBE2 which > is in development. Sorry me :) It looks like I pick on your words. I checked only chapter titles and completely forgot about sections :) But it's not a question of terminology :). You were right, there is enough information about Monticello. Sorry again. George

Feb. 4, 2010

Re: [Pharo-project] Do you want to discuss about papers?

by Geert Claes

I am not sure what you mean with the "project", "hidden email" and "group" for your new mailing list? You can setup a mailing list anywhere, INRIA, Google Groups .... another option would be to setup a new mailing list directly on Nabble (look at "Start a Mailing List" on www.nabble.com) I started one for Dolphin since they currently only have an old Usenet: comp.lang.smalltalk.dolphin. By the way, I simply took the initiative to group all Smalltalk mailing lists together, I am quite happy to delegate and make others administrator of these mailing lists. ps. if you decide to use Nabble make sure to use the "n4" server so the new mailing list can be moved together with the others. -- View this message in context: http://n4.nabble.com/Do-you-want-to-discuss-about-papers-tp1457392p1468587.… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Feb. 4, 2010