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

[Pharo-project] Newbie question deploying smalltalk applications
by Torsten Bergmann Feb. 4, 2010

Feb. 4, 2010

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

3 2

[Pharo-project] Collect Screenshots for advertising
by stephane ducasse Feb. 4, 2010

Feb. 4, 2010

Hi torsten got a really nice initiative: collection screenshots of pharo http://code.google.com/p/pharo/issues/detail?id=1931 Stef

1 0

[Pharo-project] Pharo advertising/screenshots (OS/devices)
by Torsten Bergmann Feb. 4, 2010

Feb. 4, 2010

see http://code.google.com/p/pharo/issues/detail?id=1931 for details -- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/atbrowser

1 0

[Pharo-project] Final 1.0 Steps: list of actions performed in pharo 1.0
by stephane ducasse Feb. 4, 2010

Feb. 4, 2010

Hi guys I added the list of actions we performed in pharo 1.0 http://code.google.com/p/pharo/wiki/ActionsInPharoOne?ts=1265189477&updated… We should move on and make that list shinning a bit. Then use the trick of miguel and get done So mike can you have a look at the english. Adrian can you do a pass on them. Stef

4 4

[Pharo-project] DirectoryEntry does not inherit from ArrayedCollection [WAS] Re: [squeak-dev] 3.11 questions
by Mariano Martinez Peck Feb. 3, 2010

Feb. 3, 2010

On Wed, Feb 3, 2010 at 4:34 PM, Chris Muller <asqueaker(a)gmail.com> wrote: > > 4) I have refactored DirectoryEntry to no longer inherit from > ArrayedCollection. Is this an improvement with any community > interest? > > Do you think this is interesting ? What are the benefits of such change ? Jannik: do we kill a cycle dependency or something with this change ? Kind regards, Mariano

5 7

[Pharo-project] What about a "real" research group (was: Do you want to discuss about papers?)
by CÃ©drick BÃ©ler Feb. 3, 2010

Feb. 3, 2010

I'm ok for such a list... Nevertheless, I'm wondering if we could go a bit further by doing a kind of research group with a proper web site listing all people involved and the projects there're working on. We could then establish some categories and eventually sub-groups. List all published papers, gives ressources to people... We could also have a workshop every year (in ESUG or eventually independantly). More importantly than discussions on papers, I think we need to characterise people and their "expertise" area... For instance, I'm interested in some areas that are not really focussed in Computer Science problematics (new compiler, traits, etc...). To me Smalltalk is the vehicle (a fun one) to experiment my research stuffs. Here are some areas I'm working on: -Case Based Reasoning - essentially similarity measure with uncertainty -Constraint Satisfaction Programming (more interested in open models) and especially the coupling between CBR and CSP -NARS, a kind of General AI (logical stuff) -Dynamic open models in general -> Coevolution of model and their instances (something I'd really like to dig into) -Modeling Imperfect Information, ie. incomplete, uncertain, umprecise (-> so as to model expert information) - I would like to apply that to poker game in the future :) - This is maybe the central aspect of my work Here is a quick list of what I do or plan to do... Having a central web site would be excellent for visibility (of course a mailing can be setup too), both for Smalltalk and for people doing research with it. What others think ? Would you be ok for a central wiki where each person describe in one page what their research is, what their future projects are, what they need are... We could gather all confs calls that are potentially interesting... Of course this need some setup and reflexion to structure the group/website but I think it worth it... And count me in if people like the idea. CÃ©drick

4 5

[Pharo-project] Questions about ToolSet
by Mariano Martinez Peck Feb. 3, 2010

Feb. 3, 2010

Hi folks. I found I big problem with the way ToolSet works or at least with the way I think it works. Right now, there is the class ToolSet with certain methods like API and then a class side method to register a XXX ToolSet as default. So, we have for example, the StandardToolSet which implements/overrides some of the methods of ToolSet. Of course, that ToolSet (StandardToolSet) is the default. Evaluate ToolSet default and you will get that one. Becuase that is done is StandardToolSet class >> initialize Now...the first question, why StandardToolSet doesn't extend from ToolSet ? shouldn't that be better ? Anyway, this is the big problem. The only way right now to change the toolset is to create a new class and register it. Suppose I want to install NewInspector and put in the ToolSet that now, the inspector to use is NewInspector instead of old Inspector. The only way I see right now is to create new class and implement the method inspectorClassOf: As you can see, NewInspector had to do that in class NewInspectorToolSet. They had to create that class just to implement that method and register it... Now, suppose I want to install shout, and I want to say that the default workspace is SHWorkspace (shout one), not the normal one. Ok...easy, I do the same of the NewInspector (but changing the method openWorkspace instead of inspectorClassOf:) ....but...I cannot register 2 toolsets. So, I have or NewInspectorToolSet or ShoutToolSet. Of course, this has no sense AT ALL. So, my proposal is to change ToolSet, so that any tool can change certain things, without needing to do that. Examples: For example, in StandardToolSet, we have: StandardToolSet >> openWorkspace Workspace open I would change that for something like: StandardToolSet >> openWorkspace (Smalltalk at: #WorkspaceClassName) open Of course Smalltalk at: #WorkspaceClassName must be initialized the first time with something like Smalltalk at: #WorkspaceClassName put: Workspace I don't like the name WorkspaceClassName, we should look for better names. Then, I can just have a post do it when loading Shout that evaluates: (Smalltalk at: #WorkspaceClassName put: SHWorkspace) Here there is no need to create subclasses neither to register a new toolset. Ok...this is an example, but the idea is to apply this to most cases. What do you think ? Mariano

5 5

Feb. 3, 2010

I think that this would be the first mail to smalltalk-research Begin forwarded message: > From: Tom Van Cutsem <tvcutsem(a)vub.ac.be> > Date: February 3, 2010 5:13:00 AM GMT+01:00 > To: SOFT members <soft(a)soft.vub.ac.be> > Cc: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Subject: Communicating Event Loops > > Hi, > > For those interested in concurrency control: last week I gave a presentation about AmbientTalk's concurrency model at a meeting for Javascript industry developers. The presentation was recorded, and if you're interested you can see it here: > http://ssjs.pbworks.com/Communicating-Event-Loops > > (towards the end there is an interesting discussion about the pros and cons of Erlang-style vs AmbientTalk-style concurrency) > > Cheers, > Tom

4 5

Feb. 2, 2010

Hi all, I've made a bugfix release of Filesystem. From the release notes: - Added convenience methods for Windows drives (suggested by Eliot Miranda) - Fixed bug in resolving the user''s home directory (Andreas Raab) - Fixed bug in printing the root directory on Windows - Disks on Windows are now listed in alphabetical order - Renamed utility methods for converting strings. (suggested by Julian Fitzell) - Implemented FSReference class>>roots to allow discovery of fileystems. - Implemented a resolver for Unix. (Patrick Shouse) - Fixed a bug that would prevent streams from being flushed when closed. - Fixed a bug in writing ZipFilesystem contents to the underlying zip file. - Fixed a bug in copying directory trees specified with a relative path. - Fixed a bug in growing the file allocation when writing to a file in a memory filesystem. The SAR file is available for download here: http://www.wiresong.ca/downloads/Filesystem-1.0.1.sar Please note that it's OK to install this version over the previous version. The installer will detect the previous version and do an incremental update, rather than install from scratch. Colin

3 2

[Pharo-project] How do I actually start seaside using Workspace for Installing external projects?
by Matthias Berth Feb. 2, 2010

Feb. 2, 2010

Hi, It's great to see the welcome workspaces in the most recent pharo 1.0rc2! I have executed the loading of ConfigurationOfSeaside28, and now I want to see my little seaside app. I have followed the seaside book (made a subclass of WAComponent, registered it). Now I tried to go to http://localhost:8080/ but I get nothing. Looks like seaside is not started... What can I do? What should we write in the welcome workspace to fix this problem for beginners? What do I have to do to get a change in the text into the next release? Cheers Matthias

4 4