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

Versionner Suggestions

by Sean P. DeNigris

12877 Versionner: Make Project Editing More Prominent https://pharo.fogbugz.com/default.asp?12877 It wasn't immediately obvious to me that I had to double click on a project to edit the configuration. Maybe we should add a button? At minimum, it should be added to the context menuâ¦ 12878 Versionner: Filter Test Configurations https://pharo.fogbugz.com/default.asp?12878 Either test configs (e.g. VersionnerTestXMLWriter) should indicate their status, or Versionner should filter out known ones. Right now there seems to be half a dozen such entries shown in Versionner in a fresh Pharo 3.0. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Versionner-Suggestions-tp4743390.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Feb. 13, 2014

Re: [Pharo-dev] [Vm-dev] Simulator in Pharo 3

by Stefan Marr

Hi Phil: On 13 Feb 2014, at 11:31, phil(a)highoctane.be wrote: > Some changes I did. > There is also the issue of FileSystem :-) Thanks, I checked these changes, and they are already covered. Including FileSystem :) Well, the image should be reproducible. But Iâll try to set up a CI job soon. Best regards Stefan -- Stefan Marr INRIA Lille - Nord Europe http://stefan-marr.de/research/

Feb. 13, 2014

Re: [Pharo-dev] ARM, Raspbian: Good new everyone, Raspbian display is now fixed

by Nicolas Cellier

Just a question: did you switch back to bitmap fonts? 2014-02-13 19:01 GMT+01:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > Very nice, I will try it over the weekend ! > Thanks! > > On 13 Feb 2014, at 18:38, Jean Baptiste Arnaud <jbaptiste.arnaud(a)gmail.com> > wrote: > > > Small picture for you: > > > > <photo.jpeg> > > On 13 Feb 2014, at 18:27, Jean Baptiste Arnaud < > jbaptiste.arnaud(a)gmail.com> wrote: > > >

Feb. 13, 2014

Re: [Pharo-dev] [Vm-dev] Simulator in Pharo 3

by David T. Lewis

Sorry for top posting. Juan is right. The kind of differences we are discussing here are related to user interface and file system differences in the various images, and this can be handled with a compatibility package for Pharo. It also can be done by merging into VMMaker (oscog branch), although this tends to get messy as Pharo diverges further from Squeak. I would defer to Eliot as to which approach he would prefer, since it most directly affects the oscog branch for now. But FWIW, I think that Juan's suggestion is the most straightforward and easiest to maintain over time. Dave > Hi Folks, > > (below) > > Quoting Stefan Marr <smalltalk(a)stefan-marr.de>: > >> Hi Ron: >> >> On 13 Feb 2014, at 10:38, Ron Teitelbaum <Ron(a)USMedRec.com> wrote: >> >>>> I think the bigger question is whether you actually want to adopt >>>> those >>> things. >>> >>> That the vm stays in sync should be a core requirement for our >>> communities. >> >> I am with you on that Ron. But I need a technical solution to manage >> those things. >> Good intensions are one thing, but how do we do that? >> >> Examples: [https://github.com/pharo-project/pharo-vm/pull/18/commits] >> >> primitiveUpdateGZipCrc32 >> - self cCode:'' inSmalltalk:[zipCrcTable := CArrayAccessor on: >> GZipWriteStream crcTable]. >> + self cCode:Ã¢ÂÂ' inSmalltalk:[zipCrcTable := CArrayAccessor on: CRC >> crc32Table]. >> >> primitiveGetAttribute >> >> - attribute := Smalltalk getSystemAttribute: attr. >> + attribute := Smalltalk vm getSystemAttribute: attr. >> >> CogVMSimulator>> initialize >> - 'Display has not yet been installed' asDisplayText form. >> + 'Display has not yet been installed' asMorph imageForm. >> >> >> ioRelinquishProcessorForMicroseconds >> - Processor activeProcess == Project uiProcess ifTrue: >> + Processor activeProcess == UIManager default uiProcess ifTrue: >> >> >> And so far, I only fixed trivial things. Still need to figure out >> what is going wrong with more recent Pharo images. >> >> Best regards >> Stefan >> >> -- >> Stefan Marr >> INRIA Lille - Nord Europe >> http://stefan-marr.de/research/ > > All these can be handled without much trouble in a new package > "VMMaker compatibility for Pharo" or such. > > Cheers, > Juan Vuletich > >

Feb. 13, 2014

Re: [Pharo-dev] ARM, Raspbian: Good new everyone, Raspbian display is now fixed

by Sven Van Caekenberghe

Very nice, I will try it over the weekend ! Thanks! On 13 Feb 2014, at 18:38, Jean Baptiste Arnaud <jbaptiste.arnaud(a)gmail.com> wrote: > Small picture for you: > > <photo.jpeg> > On 13 Feb 2014, at 18:27, Jean Baptiste Arnaud <jbaptiste.arnaud(a)gmail.com> wrote:

Feb. 13, 2014

Re: [Pharo-dev] [Vm-dev] Simulator in Pharo 3

by phil＠highoctane.be

Well, I just had a look and vm-dev messages weren't coming to me anymore as it looks like there is some spam rejection active somewhere on my address. So, that's why - I hit reply but this was pharo-dev... Phil On Thu, Feb 13, 2014 at 6:40 PM, Eliot Miranda <eliot.miranda(a)gmail.com>wrote: > > > > On Thu, Feb 13, 2014 at 6:19 AM, <btc(a)openinworld.com> wrote: > >> phil(a)highoctane.be wrote: >> >>> Ron, >>> >>> Sure but at this time, not being able to run the simulator in a full >>> Pharo environment is a severe issue. >>> >>> The key advantage is that the Smalltalk VM is written in itself. >>> >>> Now, what do I experience is that it is hard to embark on VM work. >>> >>> Why? Even if the PharoVMBuilders help in generating and compiling the VM >>> for several platforms (I can build for Windows 8.1, OSX, iOS, Debian 7 etc) >>> this is only one part of the puzzle. >>> >>> The next step, is to understand how things do work for real, the >>> interpret() C loop isn't gonna help me one bit, I need to be able to >>> simulate this one in a Simulator. And I want to do that on the Pharo >>> platform. Currently on 2.0 - this will (again) be fun to get to work on 3.0. >>> >>> I am not in the league of the VM maintainers obviously. >>> >>> But Clement provided me with Eliot's Cog Simulation image, which works >>> for his own work. But only his own. We do not have something like a >>> Configuration to get the same thing. And that's a very acute pain. There >>> are only so many hours in a day, true. So, in order to bring in more >>> people/resources for the VM work, the barrier to entry should be moved a >>> tad down. >>> >>> We tried to have the StackSimulator working for a while (Stephan I'll >>> definitely get your version, thanks for it). This is also because >>> InterpreterSimulator doesn't work anymore and we have to use the >>> StackInterpreter instead (which is complicated already vs pure interpreter). >>> >>> All of this rant to say that having a clean interpreter and a basic >>> image (Maybe PharoKernel/Hazelnut/Boostrapping/Spoon will give us a >>> very simple image to simulate - the whole image isn't really needed. >>> Hopefully Oz will also move us forward on that front). >>> >>> A real Pharo image is overkill for this as a ton of plugins get involved >>> etc. >>> >>> The core system should be the same for Pharo/Squeak/... : >>> >>> VMMaker-MemoryManager >>> VMMaker-Interpreter >>> VMMaker-InterpreterSimulation >>> VMMaker-MemoryManagerSimulation >>> >>> and of course the Slang things (VMMaker-Support and VMMaker-Translation >>> to C). >>> >>> What I'd love to end up with is an embeddable VM that we could hook into >>> other environments, languages etc (a bit like TCL for example). This >>> requires work on how the VM core runs. And to explore this, simulation is >>> needed. >>> >>> Sorry for the long post. I wish I was a millionaire to pour in some cash >>> into the project to speed some areas up. Working on it :-) Maybe should we >>> work in that direction for funding. http://www.gv.com/ where are you? >>> >>> Phil >>> >>> Getting the simulator working in Pharo could be a GSoC project? or is >> it too advanced? >> > > If you guys would read and contribute to vm-dev you'd already know that > someone with no VM experience (tty) just implemented event processing for > the simulator window. The simulator only supported the old polling event > architecture. So no it's not too advanced. But more importantly why > aren't you all discussing vm stuff on the vm forum? > > >> cheers -ben >> > -- > best, > Eliot >

Feb. 13, 2014

Re: [Pharo-dev] [Vm-dev] Simulator in Pharo 3

by Eliot Miranda

On Thu, Feb 13, 2014 at 6:19 AM, <btc(a)openinworld.com> wrote: > phil(a)highoctane.be wrote: > >> Ron, >> >> Sure but at this time, not being able to run the simulator in a full >> Pharo environment is a severe issue. >> >> The key advantage is that the Smalltalk VM is written in itself. >> >> Now, what do I experience is that it is hard to embark on VM work. >> >> Why? Even if the PharoVMBuilders help in generating and compiling the VM >> for several platforms (I can build for Windows 8.1, OSX, iOS, Debian 7 etc) >> this is only one part of the puzzle. >> >> The next step, is to understand how things do work for real, the >> interpret() C loop isn't gonna help me one bit, I need to be able to >> simulate this one in a Simulator. And I want to do that on the Pharo >> platform. Currently on 2.0 - this will (again) be fun to get to work on 3.0. >> >> I am not in the league of the VM maintainers obviously. >> >> But Clement provided me with Eliot's Cog Simulation image, which works >> for his own work. But only his own. We do not have something like a >> Configuration to get the same thing. And that's a very acute pain. There >> are only so many hours in a day, true. So, in order to bring in more >> people/resources for the VM work, the barrier to entry should be moved a >> tad down. >> >> We tried to have the StackSimulator working for a while (Stephan I'll >> definitely get your version, thanks for it). This is also because >> InterpreterSimulator doesn't work anymore and we have to use the >> StackInterpreter instead (which is complicated already vs pure interpreter). >> >> All of this rant to say that having a clean interpreter and a basic image >> (Maybe PharoKernel/Hazelnut/Boostrapping/Spoon will give us a very >> simple image to simulate - the whole image isn't really needed. Hopefully >> Oz will also move us forward on that front). >> >> A real Pharo image is overkill for this as a ton of plugins get involved >> etc. >> >> The core system should be the same for Pharo/Squeak/... : >> >> VMMaker-MemoryManager >> VMMaker-Interpreter >> VMMaker-InterpreterSimulation >> VMMaker-MemoryManagerSimulation >> >> and of course the Slang things (VMMaker-Support and VMMaker-Translation >> to C). >> >> What I'd love to end up with is an embeddable VM that we could hook into >> other environments, languages etc (a bit like TCL for example). This >> requires work on how the VM core runs. And to explore this, simulation is >> needed. >> >> Sorry for the long post. I wish I was a millionaire to pour in some cash >> into the project to speed some areas up. Working on it :-) Maybe should we >> work in that direction for funding. http://www.gv.com/ where are you? >> >> Phil >> >> Getting the simulator working in Pharo could be a GSoC project? or is it > too advanced? > If you guys would read and contribute to vm-dev you'd already know that someone with no VM experience (tty) just implemented event processing for the simulator window. The simulator only supported the old polling event architecture. So no it's not too advanced. But more importantly why aren't you all discussing vm stuff on the vm forum? > cheers -ben > -- best, Eliot

Feb. 13, 2014

Re: [Pharo-dev] ARM, Raspbian: Good new everyone, Raspbian display is now fixed

by Jean Baptiste Arnaud

Small picture for you: On 13 Feb 2014, at 18:27, Jean Baptiste Arnaud <jbaptiste.arnaud(a)gmail.com> wrote:

Feb. 13, 2014

Re: [Pharo-dev] [Vm-dev] Simulator in Pharo 3

by Eliot Miranda

On Thu, Feb 13, 2014 at 2:01 AM, Stefan Marr <smalltalk(a)stefan-marr.de>wrote: > > Hi Ron: > > On 13 Feb 2014, at 10:38, Ron Teitelbaum <Ron(a)USMedRec.com> wrote: > > >> I think the bigger question is whether you actually want to adopt those > > things. > > > > That the vm stays in sync should be a core requirement for our > communities. > > I am with you on that Ron. But I need a technical solution to manage those > things. > Good intensions are one thing, but how do we do that? > I would implement isPharo/isSqueak/isNewspeak in VMClass. These can answer e.g. the value of a class variable. hence, below... > Examples: [https://github.com/pharo-project/pharo-vm/pull/18/commits] > > primitiveUpdateGZipCrc32 > - self cCode:'' inSmalltalk:[zipCrcTable := CArrayAccessor on: > GZipWriteStream crcTable]. > + self cCode:'' inSmalltalk:[zipCrcTable := CArrayAccessor on: CRC > crc32Table]. > primitiveUpdateGZipCrc32 self cCode:'' inSmalltalk:[zipCrcTable := CArrayAccessor on: (self isPharo ifTrue: [CRC] ifFalse: [GZipWriteStream]) crcTable]. > > primitiveGetAttribute > > - attribute := Smalltalk getSystemAttribute: attr. > + attribute := Smalltalk vm getSystemAttribute: attr. > This is just my code base being a little out of date. Smalltalk vm getSystemAttribute: works in Squeak. I'll update my code. > CogVMSimulator>> initialize > - 'Display has not yet been installed' asDisplayText form. > + 'Display has not yet been installed' asMorph imageForm. > This needs to be isPharo. > > > ioRelinquishProcessorForMicroseconds > - Processor activeProcess == Project uiProcess ifTrue: > + Processor activeProcess == UIManager default uiProcess ifTrue: > Ditto, until Squeak changes? > > > And so far, I only fixed trivial things. Still need to figure out what is > going wrong with more recent Pharo images. > But fab that the simulator is receiving attention on Pharo (and Tty's work with events is great too). Now if there could be an automatic job to export whatever git state is the current official Pharo VM to a Monticello VMMaker package I'll be very much happier. Also for this discussion should we continue to cross-post or is vm-dev an adequate forum? Answers from Pharoites please... I have to admit that I'm a bit troubled by how often subjects that are clearly vm-centric are raised on pharo-dev. To Pharoites perceive vm-dev as a squeak thing? If so, may I suggest pharo-vm-dev? If not, can the Pharo community make an effort to direct vm discussion towards vm-dev in future? > Best regards > Stefan > > -- > Stefan Marr > INRIA Lille - Nord Europe > http://stefan-marr.de/research/ > -- best, Eliot

Feb. 13, 2014

Re: [Pharo-dev] ARM, Raspbian: Good new everyone, Raspbian display is now fixed

by Jean Baptiste Arnaud

In addition all the semaphore should work well now for Raspbian. On 13 Feb 2014, at 17:38, Jean Baptiste Arnaud <jbaptiste.arnaud(a)gmail.com> wrote: > Hello > I finally successfully fixed the PharoS bug on Raspbian. > So now the UI is not completely block it is just slow. > > As it is not yet merge with the common Pharo repository (the pull request is send), but you can test it here: > https://ci.inria.fr/pharo-contribution/view/RaspberryPi-Experimentation/job… > > > Best Regards > Jean Baptiste Arnaud > jbaptiste.arnaud(a)gmail.com > > > > > > > Best Regards Jean Baptiste Arnaud jbaptiste.arnaud(a)gmail.com

Feb. 13, 2014