- Pharo-dev - lists.pharo.org

Re: [Pharo-project] about the VM and Pharo

by Igor Stasenko

On 23 January 2013 18:07, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Igor Stasenko wrote >>> Also, is the Pharo branded VM on the static file server based on Jit Cog >>> (as >>> opposed to stack, etc)? >>> >> which server? > > http://pharo.gforge.inria.fr/ci/vm/pharo/ > yes, this is JIT Cog VMs branded for Pharo > > > -- > View this message in context: http://forum.world.st/about-the-VM-and-Pharo-tp4664887p4664909.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > -- Best regards, Igor Stasenko.

Jan. 23, 2013

Re: [Pharo-project] about the VM and Pharo

by Esteban Lorenzano

On Jan 23, 2013, at 5:27 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > EstebanLM wrote >> Pharo 2.0 will be released with a stable, branded vm with a bunch of >> useful plugins and libraries (like freetype) and out-of-the-box support >> for NativeBoost. >> ... >> For Pharo 3.0 we are even more ambitious: we want to start replacing some >> important parts of the vm with plugins (like extract a "DisplayPlugin", so >> we can control from image side the initialization of a morphic world or >> something extra. And we want to replace BitBlt plugin with Athens, so that >> will keep us busy enough time. > > Wow, very exciting! Thank everyone for the hard work :) > > > EstebanLM wrote >> - ephemerons support. > > Is this currently available? If so, does that mean that weak announcements > taking a block are now working properly? > > Also, is the Pharo branded VM on the static file server based on Jit Cog (as > opposed to stack, etc)? which server? I'm currently working on that... it will be a Jit and a Stack version of the branded VMs, but so far I'm working on the Jit (simple to adapt, anyway) so far you can find it here: https://ci.inria.fr/pharo/view/VM/job/PharoVM/ but as you can see, I'm having some problems :P cheers, Esteban > > Cheers, > Sean > > > > -- > View this message in context: http://forum.world.st/about-the-VM-and-Pharo-tp4664887p4664902.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Jan. 23, 2013

Re: [Pharo-project] about the VM and Pharo

by Sean P. DeNigris

Igor Stasenko wrote >> Also, is the Pharo branded VM on the static file server based on Jit Cog >> (as >> opposed to stack, etc)? >> > which server? http://pharo.gforge.inria.fr/ci/vm/pharo/ -- View this message in context: http://forum.world.st/about-the-VM-and-Pharo-tp4664887p4664909.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 23, 2013

Re: [Pharo-project] about the VM and Pharo

by Igor Stasenko

On 23 January 2013 17:27, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > EstebanLM wrote >> Pharo 2.0 will be released with a stable, branded vm with a bunch of >> useful plugins and libraries (like freetype) and out-of-the-box support >> for NativeBoost. >> ... >> For Pharo 3.0 we are even more ambitious: we want to start replacing some >> important parts of the vm with plugins (like extract a "DisplayPlugin", so >> we can control from image side the initialization of a morphic world or >> something extra. And we want to replace BitBlt plugin with Athens, so that >> will keep us busy enough time. > > Wow, very exciting! Thank everyone for the hard work :) > > > EstebanLM wrote >> - ephemerons support. > > Is this currently available? If so, does that mean that weak announcements > taking a block are now working properly? > no it is not integrated yet. After discussing with Eliot, he recommended to use last object format to denote ephemerons. Existing implementation is a bit hackish way to determine if object is ephemeron. So, before we do such change, assume they are not working yet. > Also, is the Pharo branded VM on the static file server based on Jit Cog (as > opposed to stack, etc)? > which server? > Cheers, > Sean > -- > View this message in context: http://forum.world.st/about-the-VM-and-Pharo-tp4664887p4664902.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > -- Best regards, Igor Stasenko.

Jan. 23, 2013

Re: [Pharo-project] TxTextMorph based on new text model

by Sean P. DeNigris

Denis Kudriashov wrote > I upload new version of TxText with new TxTextMorph Denis, thank you for taking this on! This is /so/ important. There are many times in my experiments with reinventing the tools when I've gotten confused and frustrated by the way text / editors work and chosen to revert to a more standard way of doing things. Two things: 1. Have you read about the experiments from VPRI? There is even an active essay where you can see each rule being applied individually 2. Have you considered growth as text is typed in? The current "hold the width and grow down" approach is very poor in certain applications. There was a "growable" version that increased to a maximum length, but it was very hacky due to the complexity of hooking into the existing objects. My point is, it would be great to be able to plugin different strategies here. Thanks for tackling this urgent and complicated topic! Sean -- View this message in context: http://forum.world.st/TxTextMorph-based-on-new-text-model-tp4663219p4664903… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 23, 2013

Re: [Pharo-project] about the VM and Pharo

by Sean P. DeNigris

EstebanLM wrote > Pharo 2.0 will be released with a stable, branded vm with a bunch of > useful plugins and libraries (like freetype) and out-of-the-box support > for NativeBoost. > ... > For Pharo 3.0 we are even more ambitious: we want to start replacing some > important parts of the vm with plugins (like extract a "DisplayPlugin", so > we can control from image side the initialization of a morphic world or > something extra. And we want to replace BitBlt plugin with Athens, so that > will keep us busy enough time. Wow, very exciting! Thank everyone for the hard work :) EstebanLM wrote > - ephemerons support. Is this currently available? If so, does that mean that weak announcements taking a block are now working properly? Also, is the Pharo branded VM on the static file server based on Jit Cog (as opposed to stack, etc)? Cheers, Sean -- View this message in context: http://forum.world.st/about-the-VM-and-Pharo-tp4664887p4664902.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 23, 2013

[Pharo-project] [update 2.0] #20484

by Marcus Denker

Jan. 23, 2013

Re: [Pharo-project] about the VM and Pharo

by Esteban Lorenzano

and is already there... I just forgot to mention it :P he, I was writing by memory... I probably miss a lot of the work we did last year ;) On Jan 23, 2013, at 5:13 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 23 Jan 2013, at 17:03, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> >> On Jan 23, 2013, at 4:56 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: >> >>> On 23 January 2013 16:40, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>> Hi, >>>> >>>> Maybe this was talked before, and everybody knows what I'm going to say, but I want to talk about one of the issues we are tackling for 2.0 release: The VM and its Plugins. >>>> >>>> Of course you all know that at least for now (and the next couple of years, he), we use Eliot's Cog for running Pharo. >>>> But probably some of you don't know that we actually make some changes to the VM in order to make it suitable for Pharo. This changes are sometimes incorporated to the regular VM, but some others not. So, part of our work is to keep the sources in sync with Eliot's trunk and introduce our "things" in it. >>>> What are those things? Well, a small list: >>>> >>>> - the adaptation of interpreter to run NativeBoost >>>> - external semaphores enhancement to grow easily over 250. >>>> - ephemerons support. >>>> >>> >>>> in the plugins area, this year we improved some of the existing ones: >>>> - FilePlugin, now can retrieve file permissions and knows if file is a symlink >>>> - SerialPlugin, now works in Macs (it was never implemented) > > The SSL Plugin is also very important ;-) > >>> you forgot: >>> >>> - OSProcess (VMs should include it default, so then we can use it instead >>> of writing bash scripts) >> yup >> >>> >>> - Freetype (this is already default) >> yup >> >>> >>> - .. and bundling Cairo library >> afaik, thats for 3.0 :) >> >>> >>> >>>> in addition, we are supporting the Cocoa VM for Mac (the Cocoa framework for Mac is the Objective-C replacement for Carbon, the old and legacy UI framework), and thanks to Mariano and Square[i] now we have headless support for macs (we are just missing complete headless support for windows, now). >>>> >>>> So, for Pharo 2.0 now we are working on this twi issues: >>>> >>>> - Stability! We need a stable VM, and as I already said it, we still have some problems there. >>>> - Improve the build process, to make it easier. >>>> - Branding. We need a VM that says "Pharo" and not "Cog" or "Squeak"... why? just because we make Pharo :) also, if we improve this process, then ppl doing desktop applications can reproduce it with their own branding (I suppose if you do a Mac or Windows app, you want your icon in the dock bar, not a pharo, or a cog, or a mouse... and in mac is trivial to adapt, but in windows is complicated :) >>>> >>>> Pharo 2.0 will be released with a stable, branded vm with a bunch of useful plugins and libraries (like freetype) and out-of-the-box support for NativeBoost. >>>> >>> >>> >>>> For Pharo 3.0 we are even more ambitious: we want to start replacing some important parts of the vm with plugins (like extract a "DisplayPlugin", so we can control from image side the initialization of a morphic world or something extra. And we want to replace BitBlt plugin with Athens, so that will keep us busy enough time. >>>> >>> sounds like a lot of work for me :) >> yes it is... well... we'll see :) >> >> >>> >>>> Cheers, >>>> Esteban >>> >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko. >>> >> >> > >

Jan. 23, 2013

Re: [Pharo-project] about the VM and Pharo

by Sven Van Caekenberghe

On 23 Jan 2013, at 17:03, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > On Jan 23, 2013, at 4:56 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > >> On 23 January 2013 16:40, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> Hi, >>> >>> Maybe this was talked before, and everybody knows what I'm going to say, but I want to talk about one of the issues we are tackling for 2.0 release: The VM and its Plugins. >>> >>> Of course you all know that at least for now (and the next couple of years, he), we use Eliot's Cog for running Pharo. >>> But probably some of you don't know that we actually make some changes to the VM in order to make it suitable for Pharo. This changes are sometimes incorporated to the regular VM, but some others not. So, part of our work is to keep the sources in sync with Eliot's trunk and introduce our "things" in it. >>> What are those things? Well, a small list: >>> >>> - the adaptation of interpreter to run NativeBoost >>> - external semaphores enhancement to grow easily over 250. >>> - ephemerons support. >>> >> >>> in the plugins area, this year we improved some of the existing ones: >>> - FilePlugin, now can retrieve file permissions and knows if file is a symlink >>> - SerialPlugin, now works in Macs (it was never implemented) The SSL Plugin is also very important ;-) >> you forgot: >> >> - OSProcess (VMs should include it default, so then we can use it instead >> of writing bash scripts) > yup > >> >> - Freetype (this is already default) > yup > >> >> - .. and bundling Cairo library > afaik, thats for 3.0 :) > >> >> >>> in addition, we are supporting the Cocoa VM for Mac (the Cocoa framework for Mac is the Objective-C replacement for Carbon, the old and legacy UI framework), and thanks to Mariano and Square[i] now we have headless support for macs (we are just missing complete headless support for windows, now). >>> >>> So, for Pharo 2.0 now we are working on this twi issues: >>> >>> - Stability! We need a stable VM, and as I already said it, we still have some problems there. >>> - Improve the build process, to make it easier. >>> - Branding. We need a VM that says "Pharo" and not "Cog" or "Squeak"... why? just because we make Pharo :) also, if we improve this process, then ppl doing desktop applications can reproduce it with their own branding (I suppose if you do a Mac or Windows app, you want your icon in the dock bar, not a pharo, or a cog, or a mouse... and in mac is trivial to adapt, but in windows is complicated :) >>> >>> Pharo 2.0 will be released with a stable, branded vm with a bunch of useful plugins and libraries (like freetype) and out-of-the-box support for NativeBoost. >>> >> >> >>> For Pharo 3.0 we are even more ambitious: we want to start replacing some important parts of the vm with plugins (like extract a "DisplayPlugin", so we can control from image side the initialization of a morphic world or something extra. And we want to replace BitBlt plugin with Athens, so that will keep us busy enough time. >>> >> sounds like a lot of work for me :) > yes it is... well... we'll see :) > > >> >>> Cheers, >>> Esteban >> >> >> >> -- >> Best regards, >> Igor Stasenko. >> > >

Jan. 23, 2013

Re: [Pharo-project] Must OSPlatform class>>osVersion be deprecated?

by David T. Lewis

On Wed, Jan 23, 2013 at 03:08:57PM +0100, Marcus Denker wrote: > > On Jan 23, 2013, at 7:28 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >>>> > >>> > >>> Could you capture for deprecation of OSPlatform osVersion, and resend the > >>> other method (Smalltalk osVersion current osVersion)? Or, trap for > >>> Deprecation and resume it (ignore deprecation - once it is removed, you'll > >>> automatically fail-over to the new code). > >> > >> No, Pharo 2.0 is writing console output whenever an exception occurs, so > >> catching the exception is not good. But not raising the exception in the > >> first place works just fine ;) > >> > > I will un-deprecate the osVersion methods in 2.0 and mark it as compatibility. > > > Ok, this should end up in the image by tomorrow: > > Issue 7306: un-deprecate OSPlatform osVersion for compatibility > http://code.google.com/p/pharo/issues/detail?id=7306 > Thank you :)) Dave

Jan. 23, 2013