- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] String deduplication

by Philippe Marschall

On 30.05.14 17:12, Chris Muller wrote: > I hope you're only considering this one-time for your Pharo release > image, and not something that will _continue_ to operating on an > on-going basis. Of course. Besides all the problems it's also way too slow. Cheers Philippe

June 2, 2014

Re: [Pharo-dev] ExternalPipe>>makePipe error

by Max Leske

On 01.06.2014, at 22:43, David T. Lewis <lewis(a)mail.msen.com> wrote: > Check if your VM has the UnixOSProcessPlugin plugin. It looks like PythonParser is > using OSProcess to connect to Python, so the plugin would need to be present in > order for this to work. > > As a quick check, inspect "OSProcess thisOSProcess pid". If you get an integer > (the pid of your VM process), then the plugin is available in your VM. Yep, âOSProcessâ isnât even a known globalâ¦ Thanks Dave. @Damien That means your answer on SO wonât work. And since the VM doesnât come with the OSProcess plugin (at least itâs not in the Plugins directory), thereâs no easy way of solving this other than updating ConfigurationOfPythonParser, I guess. > > Dave > > > On Sun, Jun 01, 2014 at 10:25:14PM +0200, Max Leske wrote: >> When trying to load PythonParser into 30 with >> >> Gofer it >> smalltalkhubUser: 'Pharo' project: 'MetaRepoForPharo30/'; >> configurationOf: 'PythonParser'; >> loadDevelopment >> >> I get the following error (tested with ?/30+vm and ?/30+vmLatest). Any ideas? >> I?m on a MacBook Pro, OS X 10.9.3 >> >> >> ExternalPipe(Object)>>error: >> ExternalPipe>>makePipe >> ExternalPipe>>initialize >> ExternalPipe class>>blockingPipe >> PipeableOSProcess>>createInputPipe >> PipeableOSProcess class>>new:arguments:environment:descriptors:workingDir:errorPipelineStream: >> PipeableOSProcess class>>forkAndExec:arguments:environment:descriptors:workingDir:errorPipelineStream: >> PipeableOSProcess class>>command:environment:workingDir:input:output:error:errorPipelineStream:shellSyntax: >> PipeableOSProcess class>>command:environment:workingDir:input:output:error:errorPipelineStream: >> PipeableOSProcess class>>command: >> MCFileTreeGitRepository>>gitVersions >> MCFileTreeGitRepository>>loadAncestry >> MCFileTreeGitRepository>>loadAllFileNames in Block: [ :bar | ... >> BlockClosure>>cull: >> Job>>run in Block: [ result := block cull: self ] >> BlockClosure>>on:do: >> Job>>run in Block: [ ... >> BlockClosure>>ensure: >> Job>>run >> MorphicUIManager(UIManager)>>displayProgress:from:to:during: >> ByteString(String)>>displayProgressFrom:to:during: >> MCFileTreeGitRepository>>loadAllFileNames >> MCFileTreeGitRepository>>allFileNames >> MCFileTreeGitRepository>>goferVersionFrom: >> MetacelloCachingGoferResolvedReference(GoferResolvedReference)>>version >> MetacelloCachingGoferResolvedReference>>version >> MetacelloFetchingMCSpecLoader>>resolveDependencies:nearest:into: in Block: [ :each | each version ] >> OrderedCollection>>do: >> MetacelloFetchingMCSpecLoader>>resolveDependencies:nearest:into: in Block: [ ... >> BlockClosure>>on:do: >> >> >> Cheers, >> Max >

June 2, 2014

Re: [Pharo-dev] ExternalPipe>>makePipe error

by Damien Cassou

I think the plugin is only required to load the source code with gitfiltree On Jun 1, 2014 10:44 PM, "David T. Lewis" <lewis(a)mail.msen.com> wrote: > Check if your VM has the UnixOSProcessPlugin plugin. It looks like > PythonParser is > using OSProcess to connect to Python, so the plugin would need to be > present in > order for this to work. > > As a quick check, inspect "OSProcess thisOSProcess pid". If you get an > integer > (the pid of your VM process), then the plugin is available in your VM. > > Dave > > > On Sun, Jun 01, 2014 at 10:25:14PM +0200, Max Leske wrote: > > When trying to load PythonParser into 30 with > > > > Gofer it > > smalltalkhubUser: 'Pharo' project: 'MetaRepoForPharo30/'; > > configurationOf: 'PythonParser'; > > loadDevelopment > > > > I get the following error (tested with ?/30+vm and ?/30+vmLatest). Any > ideas? > > I?m on a MacBook Pro, OS X 10.9.3 > > > > > > ExternalPipe(Object)>>error: > > ExternalPipe>>makePipe > > ExternalPipe>>initialize > > ExternalPipe class>>blockingPipe > > PipeableOSProcess>>createInputPipe > > PipeableOSProcess > class>>new:arguments:environment:descriptors:workingDir:errorPipelineStream: > > PipeableOSProcess > class>>forkAndExec:arguments:environment:descriptors:workingDir:errorPipelineStream: > > PipeableOSProcess > class>>command:environment:workingDir:input:output:error:errorPipelineStream:shellSyntax: > > PipeableOSProcess > class>>command:environment:workingDir:input:output:error:errorPipelineStream: > > PipeableOSProcess class>>command: > > MCFileTreeGitRepository>>gitVersions > > MCFileTreeGitRepository>>loadAncestry > > MCFileTreeGitRepository>>loadAllFileNames in Block: [ :bar | ... > > BlockClosure>>cull: > > Job>>run in Block: [ result := block cull: self ] > > BlockClosure>>on:do: > > Job>>run in Block: [ ... > > BlockClosure>>ensure: > > Job>>run > > MorphicUIManager(UIManager)>>displayProgress:from:to:during: > > ByteString(String)>>displayProgressFrom:to:during: > > MCFileTreeGitRepository>>loadAllFileNames > > MCFileTreeGitRepository>>allFileNames > > MCFileTreeGitRepository>>goferVersionFrom: > > MetacelloCachingGoferResolvedReference(GoferResolvedReference)>>version > > MetacelloCachingGoferResolvedReference>>version > > MetacelloFetchingMCSpecLoader>>resolveDependencies:nearest:into: in > Block: [ :each | each version ] > > OrderedCollection>>do: > > MetacelloFetchingMCSpecLoader>>resolveDependencies:nearest:into: in > Block: [ ... > > BlockClosure>>on:do: > > > > > > Cheers, > > Max > >

June 2, 2014

WhatsUp from: 2014-06-02 until: 2014-06-15

by seaside＠rmod.lille.inria.fr

Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! ### Here's what I've been up to since the last WhatsUp: - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS ### What's next, until 2014-06-15 (*): - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION (*) we'll be expecting results by then ;)

June 2, 2014

Re: [Pharo-dev] Initial versions for OSWindow and Woden

by Ronie Salgado

Now I added a prebuilt version of the VM for Windows in the same site. In Windows there are some bugs, but they are completely on image side. Even the Woden image with OpenGL works. Greetings Ronie 2014-05-31 5:54 GMT-04:00 Ronie Salgado <roniesalg(a)gmail.com>: > Hello There, > > I have been working in OSWindow, which is a cross platform API for dealing > with native operating system windows. This API requires using a custom VM > and the library SDL2. > > With this API, even the main Pharo window is handled almost completely in > image side using NativeBoost. > > The only support required from the VM is a small periodical check in the > heartbeat about the presence of events. This no more than 10 lines of code. > > This is currently working very well in my Linux machine, so I need to > start testing this stuff. > > For Windows, soon I will be building the custom VM. My last built was very > dirty and I want to do something more clean. > > For Mac OS X, I don't have one for testing. But Alex is going allow me to > borrow one for some time. So be patience. > > As for Woden, it is a new 3D graphics engine that I started making. This > one requires currently support of OSWindow and also shows some cool stuffs. > > As for prebuilt versions of the VM with OSWindow support along with > preloaded images for both, OSWindow and Woden. And screenshots. > > Well, I am putting them here: http://ronie.cl/OSWindow/ > > Greetings, > Ronie >

June 2, 2014

Re: [Pharo-dev] Improving Pharo By Example

by Ben Coman

June 2, 2014

Re: [Pharo-dev] GPU accelerated GUI

by Ben Coman

June 2, 2014

Re: [Pharo-dev] GPU accelerated GUI

by Esteban A. Maringolo

I don't know how long will it take to revamp Morphic, last time I saw a demo of it at Smalltalks conference (~circa 2007/8), it was really promising, but didn't hear about it again. Regards, Esteban A. Maringolo 2014-06-01 21:24 GMT-03:00 Darrin Massena <darrin(a)massena.com>: > Yes. Reading what Juan Vuletich is working on for the next Morphic there is > a lot said about things I imagine would negatively impact performance if a > lot of deliberate effort isn't made to offset them. > > > On Sun, Jun 1, 2014 at 5:12 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> > wrote: >> >> I couldn't tell exactly, I haven't used Cuis in the last year or so, >> but at that time (Pharo 2 was new) it was the faster of the three >> brothers (Pharo/Squeak/Cuis). >> >> Maybe that changed lately and Cuis got slower too. Apparently it is >> very easy to bloat Morphic. >> >> Regards, >> >> >> Esteban A. Maringolo >> >> >> 2014-06-01 21:07 GMT-03:00 darrinm <darrin(a)massena.com>: >> >> You get a Cuis image and it's super fast. >> > >> > What machine are you running on? I just gave the 2009 image of Cuis a >> > try on >> > my current-model Mac Pro (3.6 GHz, 6 cores, tons of RAM) and honestly >> > just >> > dragging a window around was terribly slow. Just guessing, I'd say 10 >> > FPS or >> > less which probably half what I see with Pharo. >> > >> > Is the VM a factor? Should I try a different one? >> > >> > Thanks. >> > >> > >> > >> > -- >> > View this message in context: >> > http://forum.world.st/GPU-accelerated-GUI-tp4760898p4761231.html >> > Sent from the Pharo Smalltalk Developers mailing list archive at >> > Nabble.com. >> > >> >

June 2, 2014

Re: [Pharo-dev] GPU accelerated GUI

by Darrin Massena

Yes. Reading what Juan Vuletich is working on for the next Morphic there is a lot said about things I imagine would negatively impact performance if a lot of deliberate effort isn't made to offset them. On Sun, Jun 1, 2014 at 5:12 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > I couldn't tell exactly, I haven't used Cuis in the last year or so, > but at that time (Pharo 2 was new) it was the faster of the three > brothers (Pharo/Squeak/Cuis). > > Maybe that changed lately and Cuis got slower too. Apparently it is > very easy to bloat Morphic. > > Regards, > > > Esteban A. Maringolo > > > 2014-06-01 21:07 GMT-03:00 darrinm <darrin(a)massena.com>: > >> You get a Cuis image and it's super fast. > > > > What machine are you running on? I just gave the 2009 image of Cuis a > try on > > my current-model Mac Pro (3.6 GHz, 6 cores, tons of RAM) and honestly > just > > dragging a window around was terribly slow. Just guessing, I'd say 10 > FPS or > > less which probably half what I see with Pharo. > > > > Is the VM a factor? Should I try a different one? > > > > Thanks. > > > > > > > > -- > > View this message in context: > http://forum.world.st/GPU-accelerated-GUI-tp4760898p4761231.html > > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > > >

June 2, 2014

Re: [Pharo-dev] GPU accelerated GUI

by Esteban A. Maringolo

I couldn't tell exactly, I haven't used Cuis in the last year or so, but at that time (Pharo 2 was new) it was the faster of the three brothers (Pharo/Squeak/Cuis). Maybe that changed lately and Cuis got slower too. Apparently it is very easy to bloat Morphic. Regards, Esteban A. Maringolo 2014-06-01 21:07 GMT-03:00 darrinm <darrin(a)massena.com>: >> You get a Cuis image and it's super fast. > > What machine are you running on? I just gave the 2009 image of Cuis a try on > my current-model Mac Pro (3.6 GHz, 6 cores, tons of RAM) and honestly just > dragging a window around was terribly slow. Just guessing, I'd say 10 FPS or > less which probably half what I see with Pharo. > > Is the VM a factor? Should I try a different one? > > Thanks. > > > > -- > View this message in context: http://forum.world.st/GPU-accelerated-GUI-tp4760898p4761231.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

June 2, 2014