November 2013 - Pharo-users

Re: [Pharo-users] [Pharo-dev] moving moose to pharo 3.0

by StÃ©phane Ducasse

> Hi, > > We essentially finished moving Moose to Pharo 3.0 (we still have 6 yellow tests but they needed attention anyway). It took about 4 people looking into issues for a total probably around 2 man-days of effort. The largest impediment was actually SmalltalkHub being down for one day :). Excellent! I integrated the flatCollect: fix. > > What posed problems: > - RB visitor now has correct visit* methods instead of accept* methods. The deprecation messages helped quite a bit. This meant (1) that we had to rename in our visitors the methods, and (2) that we had to change the old accept* messages. Yes. > - RB nodes do not answer to #isLiteral anymore. Instead, they answer correctly to #isLiteralNode so that to avoid confusion with Object>>#isLiteral. This is good, and this meant that we had to hunt all #isLiteral usages in Moose. :) > - Categories are no longer mapped on RPackages through 1-to-1. This is also good because it is an important step in Pharo. Although originally we said we want to keep 1-to-1, this is probably a better solution now. For Moose, this meant that some of our older tests setup had to be modified a bit to rely on RPackage only. > - Some Morphs rely now on Announcements, and this had a little impact on the assumptions we make when we suspend announcements (to avoid infinite loops) that are being sent between Morphic and Glamour. We fixed this in Glamour. > - In FileSystem #ensureDirectory was renamed to #ensureCreateDirectory without a deprecation. For this one, we should add a deprecation for the old method. Fill up a bug entry and we will add this one. Good catch > - flatCollect had a conflicting behavior in Pharo. We are now integrating the Moose version so that it returns the same species. Done :) > - The new SpecDebugger expects the registered Inspector to be based on Spec, and this causes problems with the GTInspector. This problem still has to be fixed in Pharo. > > All in all, we encountered no significant problems and the problems we faced came from deep into Pharo. So, if your code is not relying directly on RB, RPackage or the Debugger, you are likely to have a smooth transition. Excellent news. > > Cheers, > Doru > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Nov. 4, 2013

Re: [Pharo-users] CogVM arguments in Win32

by Bernat Romagosa

Hi! Thanks Igor, that kinda worked! Pharo hides, but comes back after half a second or so. I'll keep digging, thanks! :) 2013/11/1 phil(a)highoctane.be <phil(a)highoctane.be> > Well, this should rather be: > > handle :=NativeBoostWin32 squeakWindowHandle. > window := NBWin32Window new value: handle; yourself. > window hide. > > or > > window setWindowText: 'im a main window blablabla'. > > Phil > > > On Thu, Oct 31, 2013 at 10:03 PM, Igor Stasenko <siguctua(a)gmail.com>wrote: > >> You can try something like this: >> >> | handle window | >> >> handle := NativeBoost forCurrentPlatform squeakWindowHandle. >> window := NBWin32Window new value: handle; yourself. >> window hide. >> >> or >> >> window setWindowText: 'im a main window blablabla'. >> >> :) >> >> i didn't tested it since its been implemented, but i think it should work. >> >> >> >> On 30 October 2013 11:20, Bernat Romagosa <tibabenfortlapalanca(a)gmail.com >> > wrote: >> >>> In this direction, I'm trying to call a function in the shell32.dll lib >>> that apparently should let you minimize an app to the system tray, but I'm >>> not having much luck... I guess I don't really understand what am I exactly >>> doing. >>> >>> This is what I found in the MSDN<http://msdn.microsoft.com/en-us/library/bb762159%28VS.85%29.aspx> >>> : >>> >>> BOOL Shell_NotifyIcon( >>> _In_ DWORD dwMessage, >>> _In_ PNOTIFYICONDATA lpdata >>> ); >>> >>> >>> So, I tried to translate this into Pharo as: >>> >>> MyClass >> minimizeToTray: dwMessage data: lpData >>> >>> <apicall: bool 'Shell_NotifyIcon' (dword PNOTIFYICONDATA) module: >>> 'shell32.dll'> >>> >>> >>> But it won't let me save the method, reporting it's expecting an >>> argument before PNOTIFYICONDATA. >>> >>> I realize PNOTIFYICONDATA is not a primitive type, but I just don't know >>> how to handle it... :( >>> >>> >> >> >> -- >> Best regards, >> Igor Stasenko. >> > > -- Bernat Romagosa.

Nov. 4, 2013

Re: [Pharo-users] Create a .exe application in Pharo 2.0

by Sven Van Caekenberghe

On 04 Nov 2013, at 11:37, prova email <prova213(a)hotmail.it> wrote: > > Hi Sven > > yes, i read PBE, it's a great book, i love it. You are right, Pharo is different, and i'm wrong in searching the way to do "old school" stuff. Well, it is not wrong, but maybe a bit too early. The main attraction of Pharo is the incredible environment that gives you âlive objects at your fingertipsâ. Once you get used to live debugging, workspaces, inspector/explorers, readable source code all the way down, etc.. it will be hard to go back to more primitive environments. > Best; > Paolo > > > From: sven(a)stfx.eu > > Date: Mon, 4 Nov 2013 11:25:47 +0100 > > To: pharo-users(a)lists.pharo.org > > Subject: Re: [Pharo-users] Create a .exe application in Pharo 2.0 > > > > Hi Paolo, > > > > On 04 Nov 2013, at 11:07, prova email <prova213(a)hotmail.it> wrote: > > > > > It's quite hard to me to explain what i need. When i ask something, i've never had the answer that i want. What do you mean for "There are some places in the system where you can put txt file"? What are the places you are talking about? Is it the Pharo 2.0 folder? > > > Can somebody tell me step-by-step how to create the .exe file? Why is it so difficult? As i said at the beginnning of one of my first messages, i'm a rookie in Pharo. So i need something more. > > > > > > Thanks again. > > > Paolo > > > > Pharo is quite different from C, C# or Java. Building a .exe can be done or be simulated, but it is not how Pharo is normally used, so it is not a simple, one-click option. I would consider it âadvanced'. > > > > When learning something new, especially when it is very different from what you are used to, it is best, in my opinion, to first do everything the way things are meant to be done. You will âget itâ much sooner that way. > > > > Working in an image without source files and using higher level distributed source code control feels very strange for newcomers. > > > > You should start with Pharo by Example (dated, but still the best intro), after that there is Deep into Pharo, or the upcoming Pharo for the Enterprise. > > > > Regards, > > > > Sven > > > > > > -- > > Sven Van Caekenberghe > > http://stfx.eu > > Smalltalk is the Red Pill > > > >

Nov. 4, 2013

Re: [Pharo-users] Create a .exe application in Pharo 2.0

by phil＠highoctane.be

As you do a *java -jar app.jar* you can do *pharo app.image* Now to get an executable, what for? For installing: check the list for a discussion on using InnoSetup for packaging installers: http://thread.gmane.org/gmane.comp.lang.smalltalk.pharo.devel/63395 For single exe file: have a look at http://www.abyssmedia.com/quickbfc/which does interesting black magic (with a touch of ghost mode: http://www.abyssmedia.com/quickbfc/execution-mode.shtml) for single exe appearance. There is also some pkzip black magic as well. http://www.computing.net/answers/programming/packaging-exe-and-batch-script… For launching: A simple C program doing an exec() of cmd.exe /c pharo.exe app.image would be good enough (some things to be aware of: http://stackoverflow.com/questions/14679058/c-using-exec-in-windows) I'd be curious to see what UPX (http://upx.sourceforge.net/) does to the pharo.exe BTW. For a nice icon for your exe, check http://angusj.com/resourcehacker/ Phil

Nov. 4, 2013

Re: [Pharo-users] Updating Pharo 2 - Unable to resolve ConfigurationOfFuel

by StÃ©phane Ducasse

Ok so that I know it and this is probably 3 changes of 500. I was thinking about what is the problem with 2.0 update. >> But marcus we are doing update all the time because this is the way we push new updates daily. >> So I do not understand why this would be different? >> > > It happens due to strange things: updates that access the web and URLs change, for example. > Or in the past one problem was that it could overload squeak-source to load for hours and hours packagesâ¦ > > And it takes quite some care to keep it going: when *really* bad things happen, we now (once or twice in a year) > upload a fixed image that is than taken as the base. If you want to support âtake pharo2 and update it to pharo3â, > (or even, take Pharo3 half a year agoâ¦), then we need to put *a huge* (very huge) effort into making sure that > we never ever upload a hand-fixed image. > This is a lot of work. > > And in addition, even that does not guarantee anything: you would need to actually test itâ¦ > > > >>> >>>> no you dont do anything wrong, unfortunately from what I have been told the update process is broken. Right now the best choices is to download directly from pharo website >>>> >>> The problem is that how images are used is shifting: People used to use an image for a long time, updating the base from time to time while their code >>> was in the image. >>> >>> These days, what people do is to have an automatic (and well defined) process that build a fresh image on >>> -> base system is updated >>> -> Own code commit >>> >>> So e.g. I never retain images after I finish something. I commit, wait for the build system to tell me everything is green, and I throw the image >>> away. Images are transient things. >>> >>> This in turn means nobody uses updating, and this means that it is not tested. and everything not tested brakes after a whileâ¦. >>> (In turn, everything we want to be sure works needs to be tested after every commit, but testing âupdating every old version to the newestâ >>> is not really testable, anaywayâ¦) >>> >>> When we move to an image-bootstrap for the development of Pharo itself (I guess in Pharo4), we should really check what and how (and if) we >>> support updating existing images, or if we declare the image to be something that *always* be the result of a deterministic build processâ¦ >>> >>> Marcus >>> >>> >> >> > >

Nov. 4, 2013

Re: [Pharo-users] Create a .exe application in Pharo 2.0

by prova email

Hi Sven yes, i read PBE, it's a great book, i love it. You are right, Pharo is different, and i'm wrong in searching the way to do "old school" stuff. Best;Paolo > From: sven(a)stfx.eu > Date: Mon, 4 Nov 2013 11:25:47 +0100 > To: pharo-users(a)lists.pharo.org > Subject: Re: [Pharo-users] Create a .exe application in Pharo 2.0 > > Hi Paolo, > > On 04 Nov 2013, at 11:07, prova email <prova213(a)hotmail.it> wrote: > > > It's quite hard to me to explain what i need. When i ask something, i've never had the answer that i want. What do you mean for "There are some places in the system where you can put txt file"? What are the places you are talking about? Is it the Pharo 2.0 folder? > > Can somebody tell me step-by-step how to create the .exe file? Why is it so difficult? As i said at the beginnning of one of my first messages, i'm a rookie in Pharo. So i need something more. > > > > Thanks again. > > Paolo > > Pharo is quite different from C, C# or Java. Building a .exe can be done or be simulated, but it is not how Pharo is normally used, so it is not a simple, one-click option. I would consider it âadvanced'. > > When learning something new, especially when it is very different from what you are used to, it is best, in my opinion, to first do everything the way things are meant to be done. You will âget itâ much sooner that way. > > Working in an image without source files and using higher level distributed source code control feels very strange for newcomers. > > You should start with Pharo by Example (dated, but still the best intro), after that there is Deep into Pharo, or the upcoming Pharo for the Enterprise. > > Regards, > > Sven > > > -- > Sven Van Caekenberghe > http://stfx.eu > Smalltalk is the Red Pill > >

Nov. 4, 2013

Re: [Pharo-users] Create a .exe application in Pharo 2.0

by Sven Van Caekenberghe

Hi Paolo, On 04 Nov 2013, at 11:07, prova email <prova213(a)hotmail.it> wrote: > It's quite hard to me to explain what i need. When i ask something, i've never had the answer that i want. What do you mean for "There are some places in the system where you can put txt file"? What are the places you are talking about? Is it the Pharo 2.0 folder? > Can somebody tell me step-by-step how to create the .exe file? Why is it so difficult? As i said at the beginnning of one of my first messages, i'm a rookie in Pharo. So i need something more. > > Thanks again. > Paolo Pharo is quite different from C, C# or Java. Building a .exe can be done or be simulated, but it is not how Pharo is normally used, so it is not a simple, one-click option. I would consider it âadvanced'. When learning something new, especially when it is very different from what you are used to, it is best, in my opinion, to first do everything the way things are meant to be done. You will âget itâ much sooner that way. Working in an image without source files and using higher level distributed source code control feels very strange for newcomers. You should start with Pharo by Example (dated, but still the best intro), after that there is Deep into Pharo, or the upcoming Pharo for the Enterprise. Regards, Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Nov. 4, 2013

Re: [Pharo-users] Create a .exe application in Pharo 2.0

by kilon alios

You dont need to create an exe file, pharo already comes with an exe file that contains the vm and pharo internals, everything else is in the image file. You can customize pharo to display only a specific gui, its a matter of creating the gui you want maximize it to whole screen and saving the image. Next time you open Pharo it will appear as it was when you saved it. You can also disable the world menu so your users dont have access to the pharo development tools. here are some valuable infos http://forum.world.st/How-to-disable-development-tools-on-Pharo-1-3-td43414… http://smalltalkzen.wordpress.com/2013/09/21/packaging-your-squeakpharo-ima… because Pharo is almost entirely coded in smalltalk you can customize it completely. How far you go to this will depend largely from your willingness to explore the system and learn about it. On Mon, Nov 4, 2013 at 12:07 PM, prova email <prova213(a)hotmail.it> wrote: > It's quite hard to me to explain what i need. When i ask something, i've > never had the answer that i want. What do you mean for "There are some > places in the system where you can put txt file"? What are the places you > are talking about? Is it the Pharo 2.0 folder? > Can somebody tell me step-by-step how to create the .exe file? Why is it > so difficult? As i said at the beginnning of one of my first messages, i'm > a rookie in Pharo. So i need something more. > > Thanks again. > Paolo >

Nov. 4, 2013

Create a .exe application in Pharo 2.0

by prova email

It's quite hard to me to explain what i need. When i ask something, i've never had the answer that i want. What do you mean for "There are some places in the system where you can put txt file"? What are the places you are talking about? Is it the Pharo 2.0 folder? Can somebody tell me step-by-step how to create the .exe file? Why is it so difficult? As i said at the beginnning of one of my first messages, i'm a rookie in Pharo. So i need something more. Thanks again.Paolo

Nov. 4, 2013

Multicolumn text view with spec

by Norbert Hartl

What would be the way to open a Systemwindow containing just a column view in spec? the column view is for aligning text that is one or two lines. No editing just displaying. thanks, Norbert

Nov. 4, 2013