- Pharo-dev - lists.pharo.org

[Spec] ComposableModel renamed to ComposablePresenter

by Pavel Krivanek

Hello, important change for the Spec users. In "The Spec UI Framework" book you can read: Considering the construction and orchestration of the different widgets in > a user interface, Spec is inspired by the Model-View-Presenter pattern. The > model that is defined in Spec corresponds to a presenter in the MVP triad. > Note that because of this, future versions of Spec may rename the > ComposableModel into ComposablePresenter for naming consistency. This change was done in the Pharo 7 development images by this pull request: https://github.com/pharo-project/pharo/pull/344 All other Spec presenters that use suffix -Model were renamed too to end with -Presenter suffix. This is the complete list: AbstractFormButtonModel AbstractWidgetModel ButtonModel CheckBoxModel ComposableModel ContainerModel DateModel DialogWindowModel DiffModel DropListModel DynamicComposableModel FastTableModel IconListModel ImageModel LabelModel ListModel ListSelectionModel MenuGroupModel MenuItemModel MenuModel MultiColumnListModel PickListModel RadioButtonGroupModel RadioButtonModel SliderModel TabManagerModel TabModel TableContainerModel TestingComposableModel TextInputFieldModel TextModel TickingWindowModel TransferModel TreeColumnModel TreeModel TreeNodeModel WindowModel WorldModel To be sure that most of the current code which uses the old name will work, we created for every renamed class a subclass with the old name. These subclasses are moved (mostly) into Spec-Deprecated package. Currently such deprecation does not make any action so no exception is generated nor no code is rewritten. We will add such mechanisms in future as soon as most users and documentation will adopt his change. This deprecation can cause problems in two cases: you use code like 'isKindOf:' or if your package adds extension methods to the basic Spec classes. To rename these classes was only the first step. We need to rename some Spec tests classes and mainly touch methods like *instantiateModels:* and later make them deprecated. We are sorry for troubles that these changes can cause but it is necessary to make the Spec code less confusing. Cheers, -- Pavel

Oct. 12, 2017

[Pharo 7.0-dev] Build #185: 20513-Rename-ComposableModel-to-ComposablePresenter

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #185 was: SUCCESS. The Pull Request #344 was integrated: "20513-Rename-ComposableModel-to-ComposablePresenter" Pull request url: https://github.com/pharo-project/pharo/pull/344 Issue Url: https://pharo.fogbugz.com/f/cases/20513 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 12, 2017

Re: [Pharo-dev] Working Directory Changes

by Alistair Grant

Hi Guille, On Thu, Oct 12, 2017 at 11:53:15AM +0200, Guillermo Polito wrote: > > ** The most important argument, that at least I did not see anybody complain > about, is backwards compatibility. This implementation may break backwards > compatibility, because this does not hold anymore: > > FileSystem imageDirectory == FileSystem workingDirectory > > Well, yes, it holds if you start your vm/image from the same directory where > the image is located. Which is what most users do. > I gave poor Rajula quite a bit of trouble over this concern. The end result was that several people replied to say they don't care. I later found out that this assumption was only introduced about half way through Pharo 6 development. Prior to that it was possible to change the workingDirectory as it was stored in an instance variable that could be changed. So there will be very little code in existence that makes this assumption. Cheers, Alistair

Oct. 12, 2017

Re: [Pharo-dev] Working Directory Changes

by Guillermo Polito

Hi all, Now I had some minutes to take a further look at this. ** Mariano, yes, I remember that conversation. What we propose is aligned to that: FileSystem workingDirectory shouldBe == getcwd And **almost always** FileSystem workingDirectory shouldBe == $PWD This is because the real working directory is the one held by the process. $PWD is managed by bash and it can get out of sync with getcwd. For more info take a look at rajula's blogpost in the first email. ** About security, I don't really buy the argument. - There are many aspects of security: internal in the image, external. FFI is not the only thing to *care about* - right now we can do stuff like - FileSystem root ensureDeleteAll (and given pharo started with sudo...) - nil become: true - OpalCompiler compile: 'someMethodThatOverriddenBreaksEverything ...' - FFI plugin is shipped with the VM - so removing FFI support is as easy as removing the plugin - but this means that even if that FFI support is not in the image, any piece of code can do: - Myclass compile: 'test Metacello install: ''FFI''; please'; test. - or create a method calling the FFI primitives This does not mean I don't think about security, but I believe it should be managed in some other way. A security solution for real needs to manage reflection as well as external resources, and control how dependencies and packages are loaded. Because, moreover, I believe that while you may want to forbid FFI calls in some part of your app, you may want that some other parts of the system can use FFI. ** About modularity. But I'm sure I'm one of the guys that cares the most about modularity and cries aloud every time we introduce bad dependencies. Now, I'm proposing the introduction of FFI because I think its manageable and it's being controlled. It does not affect the bootstrap, and I don't think it will forbid us to get even smaller kernels. ** The most important argument, that at least I did not see anybody complain about, is backwards compatibility. This implementation may break backwards compatibility, because this does not hold anymore: FileSystem imageDirectory == FileSystem workingDirectory Well, yes, it holds if you start your vm/image from the same directory where the image is located. Which is what most users do. ** I also talked with Esteban about his reasons. His concern was about consistency. If you take a look at how getEnv is resolved: getEnv: varName "This method calls the Standard C Library getenv() function." "OSEnvironment current getEnv: 'HOME' " <primitive: 'primitiveGetenv' module: '' error: ec> ec ifNil: [ ^self getEnvViaFFI: varName ]. ec == #'bad argument' ifTrue: [ varName isString ifFalse: [ ^self getEnv: varName asString ] ]. self primitiveFail If first tries to call a primitive and then, as fallback, it calls FFI by default. I changed the pull request to do the same thing about the working directory. That way, as soon as we have implemented the primitive, that will be in usage instead of the FFI call. Guille On Wed, Oct 11, 2017 at 3:07 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > > 2017-10-11 14:14 GMT+02:00 Alistair Grant <akgrant0710(a)gmail.com>: > >> On Wed, Oct 11, 2017 at 01:32:52PM +0200, Denis Kudriashov wrote: >> > 2017-10-11 10:54 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >> > >> > in general, this core-core functions is better to implement them as >> > primitives. >> > and you put a fallback using UFFI (in case the primitive is not >> there). >> > of course, your solution works? but it adds dependency with >> FFI-Kernel, >> > which is also not good to have it in the bootstrap IMO. >> > >> > take a look at OSEnvironment>>getEnv implementation. >> > >> > we can go that direction and I think it will be better. >> > >> > >> > +1 for new primitive. Because instead any new platform will require >> implemented >> > FFI which is not easy. >> >> >> Would it make sense to add this to FilePlugin? The plugin has to be >> working for general file system access anyway. >> > > I think it is good idea > > >> >> >> Cheers, >> Alistair >> >> >> > Esteban >> > >> > >> > On 11 Oct 2017, at 10:27, Guillermo Polito < >> guillermopolito(a)gmail.com> >> > wrote: >> > >> > Hi all, >> > >> > I'd like to push a really core change in file management: the >> working >> > directory. This is really needed for command line apps, when >> you have >> > your app deployed in some directory and you're launching it from >> > another one. The current implementation, where workingDirectory >> = >> > imageDirectory, forces to have absolute paths or extra handling >> all >> > over the place to manage this complexity. >> > >> > Rajula proposed a couple of months ago a solution for this >> based on the >> > getcwd functions. You can read in his blogpost why using getcwd >> is >> > better than $PWD in general here: >> > >> > https://vineetreddy.wordpress.com/2017/05/17/pwd-vs-getcwd/ >> > >> > Now, since accessing the working directory is a core part of >> Pharo but >> > based on UFFI, his implementation was breaking the build >> process. We >> > cannot and we will not integrate UFFI in the bootstrap because >> it >> > depends mainly on the compiler which is a big beast. Instead, I >> propose >> > that only for this core-core-core feature, we use directly FFI. >> > >> > In other words, the bootstrap will include just a couple of >> classes to >> > manage the basics of FFI. And the working directory will be >> fetched by >> > using this low level API. Such a call looks like this: >> > >> > (ExternalLibraryFunction >> > name: 'getcwd' >> > module: 'libc.dylib' >> > callType: 1 >> > returnType: ExternalType char asPointerType >> > argumentTypes: { >> > ExternalType char asPointerType. >> > ExternalType long }) >> > invokeWith: buffer with: bufferSize. >> > >> > We reviewed it with Pablo two days ago. The build process works >> with >> > this implementation and tests are still running. The pull >> request is in >> > here: >> > >> > https://github.com/pharo-project/pharo/pull/92 >> > >> > >> > Thanks, >> > Guille, Pablo and Rajula >> > >> > -- >> > [presentation] Guille Polito >> > [CNRS-filaire] Research Engineer >> > >> > >> > Centre de Recherche en Informatique, >> Signal et >> > Automatique de Lille >> > CRIStAL - UMR 9189 >> > French National Center for Scientific >> Research - >> > http://www.cnrs.fr >> > >> > Web: http://guillep.github.io >> > Phone: +33 06 52 70 66 13 >> > >> > >> > >> > >> >> > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Oct. 12, 2017

Re: [Pharo-dev] XPath chapter...

by Dimitris Chloupis

Dont worry Stef you are not alone, I may no longer use Pharo as much I used to but I will keep stalking you :D So I have not quit from adding to the pharo documentation. You can at least expect some video tutorials, minor updated to PBE and minor updates to Pharo Wiki. Of course I agree we need more people on this, if every pharo users jusr dedicated 10 minutes per day on documentations we would have a mind blowing documentation in quality and quanity. 10 minutes is all it takes to update a page of documentation , 100 people, 100 pages per day. 36.500 pages per year and our documentation needing updating is not nowhere near this number OR 10 minutes to write 100 words of documentation (average writting speed is 40 WPM but I dropped this down to 10 WPM to include research, testing, taking pictures , general foramt etc) , thats about 1/3rd of a page . 100 people. 30 pages per day. 10.950 pages per year. so that means with just 100 people contributing 10 minutes of their time per day we could release around 20 NEW books per year !!!! I am sure Pharo has more than 100 users ;) On Wed, Oct 11, 2017 at 9:13 AM monty <monty2(a)programmer.net> wrote: > Great effort. The guide is concise and beginner friendly. I emailed you a > git commit patch you can apply with `git am` (I don't use github) that > fixes some things and expands on others. > > And for the record, I'm not "Monty Kamath" and I don't know him. > > > Sent: Sunday, September 24, 2017 at 1:03 PM > > From: "Stephane Ducasse" <stepharo.self(a)gmail.com> > > To: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > > Subject: [Pharo-dev] XPath chapter... > > > > Hi > > > > I'm fully convinced that we can have the best language if we do not > > let people find their way super easily to do what they want to do we > > will fail. > > Documentation is KEY and I feel a bit alone. > > > > Since I always wanted to learn XPath I started to write a chapter on > > XPath. I hope that I did not write too many mistakes. > > > > Pull requests are welcome here > > https://github.com/SquareBracketAssociates/Booklet-Scraping > > > > I would love to have one booklet on SAX and DOM handling. > > > > > > Stef > > > >

Oct. 11, 2017

[Pharo 7.0-dev] Build #182: 20514 Recategorise detectIndex: to not be an extension method

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #182 was: SUCCESS. The Pull Request #343 was integrated: "20514 Recategorise detectIndex: to not be an extension method" Pull request url: https://github.com/pharo-project/pharo/pull/343 Issue Url: https://pharo.fogbugz.com/f/cases/20514 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Oct. 11, 2017

Re: [Pharo-dev] Working Directory Changes

by Denis Kudriashov

2017-10-11 14:14 GMT+02:00 Alistair Grant <akgrant0710(a)gmail.com>: > On Wed, Oct 11, 2017 at 01:32:52PM +0200, Denis Kudriashov wrote: > > 2017-10-11 10:54 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > > > > in general, this core-core functions is better to implement them as > > primitives. > > and you put a fallback using UFFI (in case the primitive is not > there). > > of course, your solution works? but it adds dependency with > FFI-Kernel, > > which is also not good to have it in the bootstrap IMO. > > > > take a look at OSEnvironment>>getEnv implementation. > > > > we can go that direction and I think it will be better. > > > > > > +1 for new primitive. Because instead any new platform will require > implemented > > FFI which is not easy. > > > Would it make sense to add this to FilePlugin? The plugin has to be > working for general file system access anyway. > I think it is good idea > > > Cheers, > Alistair > > > > Esteban > > > > > > On 11 Oct 2017, at 10:27, Guillermo Polito < > guillermopolito(a)gmail.com> > > wrote: > > > > Hi all, > > > > I'd like to push a really core change in file management: the > working > > directory. This is really needed for command line apps, when you > have > > your app deployed in some directory and you're launching it from > > another one. The current implementation, where workingDirectory = > > imageDirectory, forces to have absolute paths or extra handling > all > > over the place to manage this complexity. > > > > Rajula proposed a couple of months ago a solution for this based > on the > > getcwd functions. You can read in his blogpost why using getcwd > is > > better than $PWD in general here: > > > > https://vineetreddy.wordpress.com/2017/05/17/pwd-vs-getcwd/ > > > > Now, since accessing the working directory is a core part of > Pharo but > > based on UFFI, his implementation was breaking the build > process. We > > cannot and we will not integrate UFFI in the bootstrap because it > > depends mainly on the compiler which is a big beast. Instead, I > propose > > that only for this core-core-core feature, we use directly FFI. > > > > In other words, the bootstrap will include just a couple of > classes to > > manage the basics of FFI. And the working directory will be > fetched by > > using this low level API. Such a call looks like this: > > > > (ExternalLibraryFunction > > name: 'getcwd' > > module: 'libc.dylib' > > callType: 1 > > returnType: ExternalType char asPointerType > > argumentTypes: { > > ExternalType char asPointerType. > > ExternalType long }) > > invokeWith: buffer with: bufferSize. > > > > We reviewed it with Pablo two days ago. The build process works > with > > this implementation and tests are still running. The pull > request is in > > here: > > > > https://github.com/pharo-project/pharo/pull/92 > > > > > > Thanks, > > Guille, Pablo and Rajula > > > > -- > > [presentation] Guille Polito > > [CNRS-filaire] Research Engineer > > > > > > Centre de Recherche en Informatique, > Signal et > > Automatique de Lille > > CRIStAL - UMR 9189 > > French National Center for Scientific > Research - > > http://www.cnrs.fr > > > > Web: http://guillep.github.io > > Phone: +33 06 52 70 66 13 > > > > > > > > > >

Oct. 11, 2017

TechTalk on Artificial Intelligence & Neural Networks

by Alexandre Bergel

Dear All, A TechTalk on Artificial Intelligence is soon approaching. The talk will be about implementing a neural networks in Pharo. It is scheduled on Tuesday 17Oct, 2017 (5:00 PM - 7:00 PM (UTC+02:00)) I need your input. Which example to you want me to use? - Data manipulation, or - Designing a small AI for a game Please answer: https://twitter.com/alexbergel/status/918084438197784578 Some info about the event: https://association.pharo.org/event-2642664 https://www.facebook.com/events/133683180530368 Thanks Marcus Denker and the RMoD crew for their help in organizing it. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Oct. 11, 2017

Re: [Pharo-dev] Working Directory Changes

by Alistair Grant

On Wed, Oct 11, 2017 at 01:32:52PM +0200, Denis Kudriashov wrote: > 2017-10-11 10:54 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > > in general, this core-core functions is better to implement them as > primitives. > and you put a fallback using UFFI (in case the primitive is not there). > of course, your solution works? but it adds dependency with FFI-Kernel, > which is also not good to have it in the bootstrap IMO. > > take a look at OSEnvironment>>getEnv implementation. > > we can go that direction and I think it will be better. > > > +1 for new primitive. Because instead any new platform will require implemented > FFI which is not easy. Would it make sense to add this to FilePlugin? The plugin has to be working for general file system access anyway. Cheers, Alistair > Esteban > > > On 11 Oct 2017, at 10:27, Guillermo Polito <guillermopolito(a)gmail.com> > wrote: > > Hi all, > > I'd like to push a really core change in file management: the working > directory. This is really needed for command line apps, when you have > your app deployed in some directory and you're launching it from > another one. The current implementation, where workingDirectory = > imageDirectory, forces to have absolute paths or extra handling all > over the place to manage this complexity. > > Rajula proposed a couple of months ago a solution for this based on the > getcwd functions. You can read in his blogpost why using getcwd is > better than $PWD in general here: > > https://vineetreddy.wordpress.com/2017/05/17/pwd-vs-getcwd/ > > Now, since accessing the working directory is a core part of Pharo but > based on UFFI, his implementation was breaking the build process. We > cannot and we will not integrate UFFI in the bootstrap because it > depends mainly on the compiler which is a big beast. Instead, I propose > that only for this core-core-core feature, we use directly FFI. > > In other words, the bootstrap will include just a couple of classes to > manage the basics of FFI. And the working directory will be fetched by > using this low level API. Such a call looks like this: > > (ExternalLibraryFunction > name: 'getcwd' > module: 'libc.dylib' > callType: 1 > returnType: ExternalType char asPointerType > argumentTypes: { > ExternalType char asPointerType. > ExternalType long }) > invokeWith: buffer with: bufferSize. > > We reviewed it with Pablo two days ago. The build process works with > this implementation and tests are still running. The pull request is in > here: > > https://github.com/pharo-project/pharo/pull/92 > > > Thanks, > Guille, Pablo and Rajula > > -- > [presentation] Guille Polito > [CNRS-filaire] Research Engineer > > > Centre de Recherche en Informatique, Signal et > Automatique de Lille > CRIStAL - UMR 9189 > French National Center for Scientific Research - > http://www.cnrs.fr > > Web: http://guillep.github.io > Phone: +33 06 52 70 66 13 > > > >

Oct. 11, 2017

Re: [Pharo-dev] DelaySpinScheduler and DelayExperimentalSpinScheduler

by Ben Coman

On Wed, Oct 11, 2017 at 4:24 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > Two questions from https://pharo.fogbugz.com/f/cases/20510 > > 1. DelaySpinScheduler needs a good comment. Anyone? > Sorry I should have done better. I'll do it now. > > 2. DelayExperimentalSpinScheduler is not used, can we remove it? > yes. I'll do it at the same time. cheers -ben

Oct. 11, 2017