- Pharo-dev - lists.pharo.org

[Pharo-project] Stability of RPackage
by Goubier Thierry Aug. 29, 2012

Aug. 29, 2012

Hi, what is your level of confidence in RPackage / Monticello at the moment in Pharo 2.0 ? I issued a few bugs on RPackage/Nautilus and I'm now starting to understand they may have been caused by the existence of two instances of RPackageOrganizer in my image, one being clearly out of sync with my code. Has anybody noticed the same problem ? I'm now planning to rebuild an image from scratch. Issues related are 6613, 6611 and 6610. Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

3 2

[Pharo-project] Xtreams in Pharo 2.0
by Sven Van Caekenberghe Aug. 29, 2012

Aug. 29, 2012

Hi, Xtreams (the port from VW done by Nicolas Celier) works out of the box with Pharo 1.4. To get it working on Pharo 2.0, just do the same load (ignoring the warning about FileDirectory being gone). Next load the following changeset: --- 'From Pharo2.0a of ''18 April 2012'' [Latest update: #20245] on 29 August 2012 at 2:08:32 pm'! !AbstractFileReference methodsFor: '*xtreams-terminals-converting' stamp: 'SvenVanCaekenberghe 8/29/2012 10:22'! appending | handle | handle := XTIOHandle forFiles open: self resolve fullName forWrite: true. ^ handle writing position: handle fileSize; isPositionable: false; yourself! ! !AbstractFileReference methodsFor: '*xtreams-terminals-converting' stamp: 'SvenVanCaekenberghe 8/29/2012 10:22'! reading ^ (XTIOHandle forFiles new open: self resolve fullName forWrite: false) reading! ! !AbstractFileReference methodsFor: '*xtreams-terminals-converting' stamp: 'SvenVanCaekenberghe 8/29/2012 10:24'! writing ^ (XTIOHandle forFiles new open: self resolve fullName forWrite: true) writing! ! --- Next, change the following test setup method: --- XTFileReadingWritingTest>>#setUp file := (self class name , '-' , testSelector) asFileReference. output := file writing. input := nil --- Now all tests are green ! Thanks, Camillo and Martin. >From ESUG, Sven

5 4

[Pharo-project] Spec Question
by Goubier Thierry Aug. 29, 2012

Aug. 29, 2012

Hi, with Spec, how do we build a GUI without opening it ? It would be convenient to do unit testing on GUIs. Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

2 2

[Pharo-project] Seaside 3.1 on Pharo 2.0
by Sven Van Caekenberghe Aug. 29, 2012

Aug. 29, 2012

I am happy to report that, thanks to some extra work done by Philippe Marschall - Thx, Philippe ! -, there is now a way to get Seaside 3.1 working on the current version of Pharo 2.0. The trick is to use the following script: https://github.com/renggli/builder/blob/master/scripts/seaside31-pharo2.st Here is the code to execute in a Workspace: "Basic" Gofer new squeaksource: 'Seaside31'; package: 'Grease-Core'; package: 'Grease-Pharo20-Core'; package: 'Grease-Tests-Core'; package: 'Grease-Tests-Pharo20-Core'; package: 'Seaside-Core'; package: 'Seaside-Pharo20-Core'; package: 'Seaside-Tests-Core'; package: 'Seaside-Tests-UTF8'; package: 'Seaside-Tests-Pharo20-Core'; package: 'Seaside-Canvas'; package: 'Seaside-Pharo-Canvas'; package: 'Seaside-Tests-Canvas'; package: 'Seaside-Session'; package: 'Seaside-Tests-Session'; package: 'Seaside-Component'; package: 'Seaside-Tests-Component'; package: 'Seaside-RenderLoop'; package: 'Seaside-Tests-RenderLoop'; package: 'Seaside-Tools-Core'; package: 'Seaside-Widgets'; package: 'Seaside-Environment'; package: 'Seaside-Pharo-Environment'; package: 'Seaside-Tests-Environment'; load. ! "Traditional" Gofer new squeaksource: 'Seaside31'; package: 'Seaside-Tests-Functional'; package: 'Seaside-Tests-Pharo-Functional'; package: 'Seaside-Pharo-Continuation'; package: 'Seaside-Tests-Pharo-Continuation'; package: 'Seaside-Flow'; package: 'Seaside-Pharo-Flow'; package: 'Seaside-Tests-Flow'; package: 'Seaside-Tools-Web'; package: 'Seaside-Pharo20-Tools-Web'; package: 'Seaside-Tests-Tools-Web'; package: 'Seaside-Development'; package: 'Seaside-Pharo-Development'; package: 'Seaside-Tests-Development'; package: 'Seaside-Tests-Pharo-Development'; package: 'Seaside-Examples'; package: 'Seaside-Tests-Examples'; load. ! "RSS" Gofer new squeaksource: 'Seaside31'; package: 'RSS-Core'; package: 'RSS-Tests-Core'; package: 'RSS-Examples'; load. ! "Javascript" Gofer new squeaksource: 'Seaside31'; package: 'Javascript-Core'; package: 'Seaside-JSON-Core'; package: 'Seaside-Pharo-JSON-Core'; package: 'Javascript-Pharo20-Core'; package: 'Javascript-Tests-Core'; package: 'Javascript-Tests-Pharo-Core'; package: 'Seaside-Tests-JSON'; package: 'JQuery-Core'; package: 'JQuery-Tests-Core'; package: 'JQuery-JSON'; package: 'JQuery-Tests-JSON'; package: 'JQuery-UI'; package: 'JQuery-Tests-UI'; package: 'Prototype-Core'; package: 'Prototype-Tests-Core'; package: 'Scriptaculous-Core'; package: 'Scriptaculous-Tests-Core'; package: 'Scriptaculous-Components'; package: 'Scriptaculous-Tests-Components'; package: 'Comet-Core'; package: 'Comet-Examples'; package: 'Comet-Pharo-Core'; package: 'Comet-Tests-Core'; load. ! "Other Packages" Gofer new squeaksource: 'Seaside31'; package: 'Seaside-Welcome'; package: 'Seaside-Pharo-Welcome'; package: 'Seaside-Tests-Welcome'; package: 'Seaside-HTML5'; package: 'Seaside-Tests-HTML5'; package: 'Seaside-InternetExplorer'; package: 'Seaside-Tests-InternetExplorer'; package: 'Seaside-Email'; package: 'Seaside-Tests-Email'; package: 'Seaside-Pharo-Email'; package: 'Seaside-Tests-Pharo-Email'; load. ! "REST" Gofer new squeaksource: 'Seaside31'; package: 'Seaside-REST-Core'; package: 'Seaside-Pharo-REST-Core'; package: 'Seaside-Tests-REST-Core'; load. This does not yet load an adaptor. You can go find ZnZincServerAdaptor in the Zinc repository, like this (updating all Zn): Gofer new url: 'http://mc.stfx.eu/ZincHTTPComponents'; package: 'Zinc-HTTP'; package: 'Zinc-Tests; package: 'Zinc-FileSystem'; package: 'Zinc-Seaside'; load. And finally, ZnZincStaticServerAdaptor startOn: 8080. ZnZincStaticServerAdaptor stop. (The Seaside control panel is not there). All but one, less relevant test, pass. Thanks again, Philippe. Sven PS: The ConfigurationOfSeaside is in the process to be updated as well. -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

2 1

[Pharo-project] Why FileSystemHandle has writable flag, but not readable?
by Igor Stasenko Aug. 29, 2012

Aug. 29, 2012

you know, it can happen that you can open a file for write but not for read. i do not see how i can say "this reference is for write only" -- Best regards, Igor Stasenko.

2 1

[Pharo-project] [ANN] NativeBoost v 1.3
by Igor Stasenko Aug. 28, 2012

Aug. 28, 2012

Hi, all yesteray i committed new version of NativeBoost configuration. Some details about last few months changes: NativeBoost: - introduced a NBExternalTypeValue class - introduced a NBNativeFunction class, a reification of external function generated dynamically - introduced an NBExternalResourceManager and integration with other classes - a lot of cleanup and better comments - some updates to NativeBoost-Help package (currently it is not part of configuration by default, so you have to load this package manually from NB repository) AsmJit: - the package is split on several small packages + configuration to load it - more documentation - more nicer instruction printing output - fixed some instructions (some FPU / jump instructions was non-functional) - and a lot of effort by Camillo, who made x64 assembler working. (but we cannot use it with NB since our VMs is 32bit) To load NativeBoost you can follow an instructions on project page: -- Best regards, Igor Stasenko.

6 15

Re: [Pharo-project] Again: Basic Questions about NativeBoost
by drush66 Aug. 28, 2012

Aug. 28, 2012

Does NB support writing callbacks in smalltalk that can be called by external library? ----- http://www.cloud208.com/ -- View this message in context: http://forum.world.st/Again-Basic-Questions-about-NativeBoost-tp4645447p464… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

3 2

Re: [Pharo-project] Multiple worlds // how to switch between them...
by H. Hirzel Aug. 28, 2012

Aug. 28, 2012

To be more precise. Is there another way than WorldManager instance createOrSwitchToWorldNamed: 'myOtherDesktop'. and then back with WorldManager instance createOrSwitchToWorldNamed: 'Pharo'. On 8/28/12, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > Hello again, > > A follow-up question. > > I loaded the TilingWindowManager (TWM) by Laurent Laffont. > ( MetacelloConfigurationBrowser open. ) > > TWM is supposed to support multiple virtual desktops. > How do I start using this feature? > > E.g. a pointer to a blog entry? > > Thank you in advance. > > --Hannes > > On 8/28/12, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >> Hello >> >> Any news on having multiple virtual desktops in Pharo? >> >> I currently use Pharo 1.4, maybe it is in 2.0? >> >> Regards >> --Hannes >> >> On 5/2/12, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> Esteban >>> >>> Having multiple virtual desktops is cool and this is not the full >>> project >>> syndrome so we should check the code and if it is small >>> and nice integrate it. >>> >>> Stef >>> >>> >>>> Hi, >>>> >>>> I propose to just close the issue... having different words don't seems >>>> to >>>> match with current pharo approach and future envisioned scenarios. >>>> (I'm sorry if someone is expecting that) >>>> >>>> best, >>>> Esteban >>>> >>>> On May 2, 2012, at 3:28 PM, Marcus Denker wrote: >>>> >>>>> >>>>> On May 2, 2012, at 3:23 PM, H. Hirzel wrote: >>>>> >>>>>> Hello >>>>>> >>>>>> This issue >>>>>> http://code.google.com/p/pharo/issues/detail?id=3545 >>>>>> is about the feature of having multiple worlds. Status is 'Accepted'. >>>>>> >>>>> Accepted means accepted for thinking about, there is no commitment. >>>>> >>>>>> I assume it is now in Pharo 1.4. >>>>>> >>>>>> How can I use it. >>>>>> >>>>>> The code I found from Sean is >>>>>> >>>>>> "Add a world:" >>>>>> WorldManager instance createOrSwitchToWorldNamed: 'JustAnotherWorld'. >>>>>> >>>>>> "Return to the default world:" >>>>>> WorldManager instance createOrSwitchToWorldNamed: 'Pharo'. >>>>>> >>>>>> What are the proper instructions? >>>>> >>>>> >>>>> It's a bug tracker entry. Not a package for users to use. >>>>> >>>>> Marcus >>>>> >>>>> -- >>>>> Marcus Denker -- http://marcusdenker.de >>>>> >>>>> >>>> >>>> >>> >>> >>> >> >

1 0

[Pharo-project] RPackage question
by Goubier Thierry Aug. 28, 2012

Aug. 28, 2012

If I'm up to date with Pharo 2.0, PackageInfo is gone and RPackage is replacing it, right ? I'm trying to get the AltBrowser to work with RPackage... At the moment, RPackage seems to be organized in the following way. If there are the following Monticello packages : RPackage-Core RPackage-Tests RPackage-SystemIntegration Then, when querying the RPackage organizer, I get the following 4 packages : RPackage RPackage-Core RPackage-Tests RPackage-SystemIntegration In RPackage, I find 3 tags : RPackage-Core RPackage-Tests RPackage-SystemIntegration In RPackage-Core, RPackage-Tests, RPackage-SystemIntegration, I have a single tag, but apparently, by exploring each RPackage info, all the original package references (class definitions, methods etc...), with all that duplicated in RPackage. However, if I query RPackageOrganizer, all classes definitions in RPackage-Core, RPackage-Tests, RPackage-SystemIntegration are reported as belonging to RPackage. Is that expected ? Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

1 0

[Pharo-project] Small Spec / Announcement question.
by Goubier Thierry Aug. 28, 2012

Aug. 28, 2012

Is there a reason for the use or lack of weak in whenChanged for NewValueHolder ? NewValueHolder>>whenChanged:do: announcer weak on:do: NewValueHolder>>whenChangedSend:to: announcer on:send:to: Thanks, Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

2 1