- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core] 075ec6: 50550

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 075ec66df6ea08e7be71d5275b08ca095432aa2b https://github.com/pharo-project/pharo-core/commit/075ec66df6ea08e7be71d527… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-01-27 (Wed, 27 Jan 2016) Changed paths: M Alien.package/Alien.class/class/class initialization/ensureInSpecialObjectsArray.st M Alien.package/Alien.class/class/class initialization/initialize.st M Alien.package/Alien.class/class/examples/libcName.st M Alien.package/Alien.class/class/instance creation/atAddress_.st M Alien.package/Alien.class/class/instance creation/atAddress_dataSize_.st M Alien.package/Alien.class/class/instance creation/forPointer_.st M Alien.package/Alien.class/class/instance creation/newC_.st M Alien.package/Alien.class/class/instance creation/newGC_.st M Alien.package/Alien.class/class/instance creation/new_.st M Alien.package/Alien.class/class/instance creation/rawNewC_.st M Alien.package/Alien.class/class/system startup/startUp_.st M Alien.package/Alien.class/definition.st R Alien.package/Alien.class/instance/as yet unclassified/isPointer.st M Alien.package/Alien.class/instance/printing/storeOn_.st A Alien.package/Alien.class/instance/testing/isPointer.st M Alien.package/AlienSunit.class/instance/testing/testLongLong.st R ConfigurationOfFFI.package/ConfigurationOfFFI.class/README.md R ConfigurationOfFFI.package/ConfigurationOfFFI.class/class/accessing/project.st R ConfigurationOfFFI.package/ConfigurationOfFFI.class/class/catalog/catalogContactInfo.st R ConfigurationOfFFI.package/ConfigurationOfFFI.class/class/catalog/catalogDescription.st R ConfigurationOfFFI.package/ConfigurationOfFFI.class/class/catalog/catalogKeywords.st R ConfigurationOfFFI.package/ConfigurationOfFFI.class/class/loading/load.st R ConfigurationOfFFI.package/ConfigurationOfFFI.class/class/metacello tool support/isMetacelloConfig.st R ConfigurationOfFFI.package/ConfigurationOfFFI.class/class/metacello tool support/lastMetacelloVersionLoad.st R ConfigurationOfFFI.package/ConfigurationOfFFI.class/class/metacello tool support/metacelloVersion_loads_.st R ConfigurationOfFFI.package/ConfigurationOfFFI.class/class/private/bootstrapPackage_from_.st R ConfigurationOfFFI.package/ConfigurationOfFFI.class/class/private/ensureMetacello.st R ConfigurationOfFFI.package/ConfigurationOfFFI.class/definition.st R ConfigurationOfFFI.package/ConfigurationOfFFI.class/instance/accessing/project.st R ConfigurationOfFFI.package/ConfigurationOfFFI.class/instance/baselines/baseline10_.st R ConfigurationOfFFI.package/ConfigurationOfFFI.class/instance/baselines/baseline12_.st R ConfigurationOfFFI.package/ConfigurationOfFFI.class/instance/baselines/baseline13_.st R ConfigurationOfFFI.package/ConfigurationOfFFI.class/instance/baselines/baseline14_.st R ConfigurationOfFFI.package/ConfigurationOfFFI.class/instance/baselines/baseline15_.st R ConfigurationOfFFI.package/ConfigurationOfFFI.class/instance/doits/ffiExampleInitialization10.st R ConfigurationOfFFI.package/ConfigurationOfFFI.class/instance/symbolic versions/development_.st R ConfigurationOfFFI.package/ConfigurationOfFFI.class/instance/symbolic versions/stable_.st R ConfigurationOfFFI.package/ConfigurationOfFFI.class/instance/versions/version1%5F10%5F1_.st R ConfigurationOfFFI.package/ConfigurationOfFFI.class/instance/versions/version1%5F10_.st R ConfigurationOfFFI.package/ConfigurationOfFFI.class/instance/versions/version1%5F9%5F1_.st R ConfigurationOfFFI.package/ConfigurationOfFFI.class/instance/versions/version10_.st R ConfigurationOfFFI.package/ConfigurationOfFFI.class/instance/versions/version11_.st R ConfigurationOfFFI.package/ConfigurationOfFFI.class/instance/versions/version12_.st R ConfigurationOfFFI.package/ConfigurationOfFFI.class/instance/versions/version13_.st R ConfigurationOfFFI.package/ConfigurationOfFFI.class/instance/versions/version14_.st R ConfigurationOfFFI.package/ConfigurationOfFFI.class/instance/versions/version15_.st R ConfigurationOfFFI.package/ConfigurationOfFFI.class/instance/versions/version16_.st R ConfigurationOfFFI.package/ConfigurationOfFFI.class/instance/versions/version17_.st R ConfigurationOfFFI.package/ConfigurationOfFFI.class/instance/versions/version18_.st R ConfigurationOfFFI.package/ConfigurationOfFFI.class/instance/versions/version19_.st R ConfigurationOfOldAlien.package/ConfigurationOfOldAlien.class/README.md R ConfigurationOfOldAlien.package/ConfigurationOfOldAlien.class/class/accessing/project.st R ConfigurationOfOldAlien.package/ConfigurationOfOldAlien.class/class/catalog/catalogContactInfo.st R ConfigurationOfOldAlien.package/ConfigurationOfOldAlien.class/class/catalog/catalogDescription.st R ConfigurationOfOldAlien.package/ConfigurationOfOldAlien.class/class/catalog/catalogKeywords.st R ConfigurationOfOldAlien.package/ConfigurationOfOldAlien.class/class/development support/DevelopmentSupport.st R ConfigurationOfOldAlien.package/ConfigurationOfOldAlien.class/class/development support/validate.st R ConfigurationOfOldAlien.package/ConfigurationOfOldAlien.class/class/loading/load.st R ConfigurationOfOldAlien.package/ConfigurationOfOldAlien.class/class/loading/loadBleedingEdge.st R ConfigurationOfOldAlien.package/ConfigurationOfOldAlien.class/class/loading/loadDevelopment.st R ConfigurationOfOldAlien.package/ConfigurationOfOldAlien.class/class/metacello tool support/isMetacelloConfig.st R ConfigurationOfOldAlien.package/ConfigurationOfOldAlien.class/class/private/baseConfigurationClassIfAbsent_.st R ConfigurationOfOldAlien.package/ConfigurationOfOldAlien.class/class/private/ensureMetacello.st R ConfigurationOfOldAlien.package/ConfigurationOfOldAlien.class/class/private/ensureMetacelloBaseConfiguration.st R ConfigurationOfOldAlien.package/ConfigurationOfOldAlien.class/definition.st R ConfigurationOfOldAlien.package/ConfigurationOfOldAlien.class/instance/accessing/project.st R ConfigurationOfOldAlien.package/ConfigurationOfOldAlien.class/instance/baselines/baseline10_.st R ConfigurationOfOldAlien.package/ConfigurationOfOldAlien.class/instance/symbolic versions/stable_.st R ConfigurationOfOldAlien.package/ConfigurationOfOldAlien.class/instance/versions/version1%5F2_.st R ConfigurationOfOldAlien.package/ConfigurationOfOldAlien.class/instance/versions/version10_.st R ConfigurationOfOldAlien.package/ConfigurationOfOldAlien.class/instance/versions/version11_.st A ConfigurationOfUnifiedFFI.package/ConfigurationOfUnifiedFFI.class/instance/baselines/baseline0%5F11_.st M ConfigurationOfUnifiedFFI.package/ConfigurationOfUnifiedFFI.class/instance/symbolic versions/development_.st M ConfigurationOfUnifiedFFI.package/ConfigurationOfUnifiedFFI.class/instance/symbolic versions/stable_.st A ConfigurationOfUnifiedFFI.package/ConfigurationOfUnifiedFFI.class/instance/versions/v0%5F11%5F2_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50549.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50550.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50549.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50550.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50550 17482 load UnifiedFFI 0.11.2 https://pharo.fogbugz.com/f/cases/17482 17479 Interval class comment mixes step/stop when explaining Instance Variables https://pharo.fogbugz.com/f/cases/17479 http://files.pharo.org/image/50/50550.zip

Jan. 27, 2016

[ANN] First release of FFICHeaderExtractor

by Mariano Martinez Peck

Dear all, I am happy to announce the first release of FFICHeaderExtractor project. You can find the project and the documentation here: https://github.com/marianopeck/FFICHeaderExtractor Any feedback is more than welcome. Best, -- Mariano http://marianopeck.wordpress.com

Jan. 27, 2016

Re: [Pharo-dev] Contributing to Pharo

by Dale Henrichs

On 1/27/16 12:03 AM, Thierry Goubier wrote: > Hi Dale, > > then a question: how does one query a baselineOf or a configOf to > retrieve the current project state (i.e. packages) loaded in the image? > > Thierry > Thierry, Good question:) To start with in tODE I have a class TDMetacelloProjectRegistrationDefinition which is part of the following hierarchy: Object TDDefinition TDPackageBasedDefinition TDAbstractProjectRegistrationDefinition TDGitProjectRegistrationDefinition TDMetacelloProjectRegistrationDefinition TDMetacelloRegistrationDefinition TDMetacelloBaselineRegistrationDefinition TDMetacelloConfigurationRegistrationDefinition TDMetacelloHybridRegistrationDefinition TDMetacelloUnloadedProjectRegistrationDefinition The method TDMetacelloProjectRegistrationDefinition>>workingCopies[1] calculates the list of MCWorkingCopy instances for the loaded packages associated with a project (including the configurationof or baselineof... or both). The key Metacello methods called include: MetacelloProjectRegistration>>projectVersion[2] MetacelloMCVersion>>packages[3] MetacelloPackageSpec>>workingCopy[4] MetacelloMCProjectSpec>>projectPackage[5] This is really the key information for doing all of the other operations for a "Project Browser" like "save all dirty packages and commit" and "give me diffs for all dirty packages in project"... Dale [1] https://github.com/dalehenrich/tode/blob/master/repository/Topez-Server-Cor… [2] https://github.com/dalehenrich/metacello-work/blob/master/repository/Metace… [3] https://github.com/dalehenrich/metacello-work/blob/master/repository/Metace… [4] https://github.com/dalehenrich/metacello-work/blob/master/repository/Metace… [5] https://github.com/dalehenrich/metacello-work/blob/master/repository/Metace…

Jan. 27, 2016

Re: [Pharo-dev] Contributing to Pharo

by Sven Van Caekenberghe

Dale, That looks like something very interesting and worth considering. How easy is it to load tODE in a current (4.x 5.x) Pharo image ? I assume there is a Metacello configuration ;-) Is it possible to experiment with it in Pharo, independent from Gemstone ? I did not see it in the Catalog Browser (our current point & click installer). Making tODE easily loadable would, IMHO, be the first step to a broader adaption of your work (in one form or another). The next step would be a getting started tutorial. Sven > On 27 Jan 2016, at 15:13, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> wrote: > > Haha, I certainly understand the lack of time/manpower ... Just in case it wasn't clear, when I said "project browser" I wasn't talking about replacing the code browser (Nautilus), but replacing/augmenting the Monticello Browser - which should turn out to be a much simpler undertaking --- "Project Browser" that manages the projects within the image - load, save, changes, etc.: > > <Screen Shot 2016-01-27 at 6.11.33 AM.png> > > > Dale > > On 1/26/16 11:29 PM, Christophe Demarey wrote: >> Hi Dale, >> >> Le 27 janv. 2016 Ã 04:11, Dale Henrichs a Ã©crit : >> >> >>> I've been wondering no-one in the Pharo community has started building a "Project Browser" to replace the "Package Browser" .... I've had a "project browser" in tODE for several years now and you work with a manageble list of Metacello projects like the following: >>> >> Of course, we have that in mind. We would love to have it but lack of time / manpower ... >> We are not happy with the current browser (Nautilus). We could have something really more powerful. It will come but we have other projects to achieve before ;) >> If someone comes with a better browser, we would love to set it as default. >> >> Cheers, >> Christophe >> >

Jan. 27, 2016

Re: [Pharo-dev] Contributing to Pharo

by Dale Henrichs

Haha, I certainly understand the lack of time/manpower ... Just in case it wasn't clear, when I said "project browser" I wasn't talking about replacing the code browser (Nautilus), but replacing/augmenting the Monticello Browser - which should turn out to be a much simpler undertaking --- "Project Browser" that manages the projects within the image - load, save, changes, etc.: project list screenshot Dale On 1/26/16 11:29 PM, Christophe Demarey wrote: > Hi Dale, > > Le 27 janv. 2016 Ã 04:11, Dale Henrichs a Ã©crit : > >> I've been wondering no-one in the Pharo community has started building a "Project Browser" to replace the "Package Browser" .... I've had a "project browser" in tODE for several years now and you work with a manageble list of Metacello projects like the following: > Of course, we have that in mind. We would love to have it but lack of time / manpower ... > We are not happy with the current browser (Nautilus). We could have something really more powerful. It will come but we have other projects to achieve before ;) > If someone comes with a better browser, we would love to set it as default. > > Cheers, > Christophe

Jan. 27, 2016

Call for Participation: Virtual Machine Summer School 2016

by Tim Felgentreff

Call for Participation Virtual Machines Summer School 2016 (#vmss16) May 31 - June 3 2016 Cumberland Lodge, UK http://soft-dev.org/events/vmss16/ Early Bird Registration Period: January 11 - February 15, 2016 Regular Registration Period: February 16 - April 30, 2016 The Virtual Machines Summer School (VMSS) will take place in Cumberland Lodge, UK in summer 2016 just outside London. The aim of the summer school is to give early career researchers (PhD students and postdocs particularly) an overview of the field, and to meet some of its top thinkers. Venue: Cumberland Lodge is a former royal hunting lodge in Windsor Great Park, a few miles south of Windsor castle. Since all participants will be staying at the Lodge, a concentrated and inspiring atmosphere is guaranteed. Registration is subsidised by the EPRSC, so costs are low, particularly for those who register early. There are travel grants available for students that might otherwise be unable to attend the summer school. For further information and registration please visit: http://soft-dev.org/events/vmss16/ Confirmed Speakers: Antony Hosking (Purdue University) Ben Titzer (Google) Carl Friedrich Bolz (King's College London) Chris Seaton (Oracle Labs) Cliff Click (H2O) Edd Barrett (King's College London) Gilles Duboscq (Oracle Labs) Jennifer Sartor (Vrije Universiteit Brussel) Mario Wolczko (Oracle Labs) Paul Tarau (University of North Texas) Richard Jones (University of Kent) Steve Blackburn (Australian National University) Vyacheslav Egorov (Google) Organizers: Laurence Tratt & Carl Friedrich Bolz (King's College London)

Jan. 27, 2016

Re: [Pharo-dev] fixing our tools

by stepharo

thanks nicolai I discussed a while ago with alain about it and the problem occured because suddenly requirements changed in terms of what can be done (syntax highligth, menuitems) and where Stef > > 2015-12-03 9:16 GMT+01:00 Marcus Denker <marcus.denker(a)inria.fr > <mailto:marcus.denker@inria.fr>>: > > Hi, > > Yes, I think we really need to unify both the editor (get really > rid of the old one) and > the toolsâ¦ e.g. it is strange that all the changes we did for > breakpoint visuals now have > to be redone 3 times to get them in all toolsâ¦ > > I will have a look at these, many seem to be related to the > suggestions-menu. > > > I added a fix to > 17385 > <https://pharo.fogbugz.com/f/cases/17385/DiffMorph-menus-are-broken> > DiffMorph menus are broken > > this will fix the menu in some, but not all tools. > > > > > On 03 Dec 2015, at 08:47, Nicolai Hess <nicolaihess(a)gmail.com > <mailto:nicolaihess@gmail.com>> wrote: > > > > please take a look at this errors: > > > > (I don't want to open 20 bug entries, and I think those issues > are related > > to two changes for Suggestions menu and one problem on rubric > (the current menu builder > > does not work for all tools where rubric is used) > > So, maybe there are only 2 or 3 "real" issues. > > > > Help appreciate, especially for the rubric issue. Every time I > tried to fix one > > tool, there is at least one other tool with a broken menu. > > > > Open Nautilus on a method: > > (Morph>>#drawOn:) browse > > without any other interaction, right click on the code pane > > -> a menu appears with embedded "why you see this menu/debug" > debug menu > > caused by empty selection interval > > as soon as you select once one method entry, the right click > menu works again. > > > > Open VersionBrowser (or any other tool (MC-changes / merge) with > diff morph > > right click in one of the diff code panes > > -> error contextFor: 'Not defined context for a RubEditingArea' > > > > Open Transcript > > right click > > -> error contextFor: 'Not defined context for a RubEditingArea' > > > > Open Finder > > right click in the lower code pane > > -> 'Not defined context for a RubEditingArea' > > > > Open ProcessBrowser > > right click in the lower code pane > > -> 'Not defined context for a RubEditingArea(808452096)' > > > > Open TimeProfiler > > select an entry from the time-"tree" > > right click in the code pane > > deprecation warning -> The method SmalltalkEditor > class>>smalltalkEditorMenuOn: has been deprecated. > > > > Open a basic inspector (EyeInspector) > > right click in the workspace pane > > -> EyeIntegerInspector(Object)>>doesNotUnderstand: #selectedMessage > > > > Open ChangesBrowser > > right click in the lower code pane (regardless whether you > select a changed class and method > > or not you'll get always) > > -> ChangeSorterApplication(Object)>>doesNotUnderstand: > #selectedMessage > > > > Open CriticsBrowser > > right click on the code pane > > -> SingleCodeCriticResultList(Object)>>doesNotUnderstand: > #selectedMessage > > > > Open recover lost changes > > right click on the lower code pane > > -> ExternalChangesBrowser(Object)>>doesNotUnderstand: > #selectedMessage > > > > The same in external browser > > ExternalBrowser(Object)>>doesNotUnderstand: #selectedMessage > > > > Open debugger > > select a inst var or context var > > right click in the var "value"-pane > > -> MorphicTextAdapter(Object)>>doesNotUnderstand: #acceptAllowed > > > > Open VersoinBrowser > > change from "Side-by-Side" to "Source" view > > right click in the code pane > > -> UndefinedObject(Object)>>doesNotUnderstand: #ast > > > > >

Jan. 27, 2016

Re: [Pharo-dev] "Pharo" Name Overload

by stepharo

+ 1 Le 27/1/16 09:48, Denis Kudriashov a Ã©crit : > > 2016-01-27 3:06 GMT+01:00 Ben Coman <btc(a)openinworld.com > <mailto:btc@openinworld.com>>: > > It would be great for Pharo Launcher to be the default download, but > why can it not still be called "PharoLauncher.app". > > > +1

Jan. 27, 2016

Re: [Pharo-dev] "Pharo" Name Overload

by Damien Cassou

Ben Coman <btc(a)openinworld.com> writes: > On Wed, Jan 27, 2016 at 5:27 AM, Damien Cassou <damien.cassou(a)inria.fr> wrote: >> "Sean P. DeNigris" <sean(a)clipperadams.com> writes: >> >>> I now have three Pharo.app files on my Mac - Launcher, Spur, and non-Spur. It >>> would be great if we can agree to call one thing Pharo, and add appropriate >>> modifiers to the other two names. >> >> I'm not an OS X user, but I have the impression that .app is reserved >> for graphical applications, one you can start with a double click. For >> me, no Pharo VM is a graphical application and thus none deserve its >> .app file in /Applications. >> >> On the contrary, what we currently call the Pharo Launcher is a >> graphical application so it deserves a .app file. I called it just >> Pharo.app because I didn't see any concurrence on the name and some in >> the Pharo board would like the launcher to be the default Pharo download >> (the one behind the big Download button on the website). > > It would be great for Pharo Launcher to be the default download, but > why can it not still be called "PharoLauncher.app". It is still just > an app on top of *real* Pharo and calling the launcher Pharo.app I > believe presents a cognitive dissonance for a newcomer to understand > the distinction. The launcher is used to start non-/more-than-Pharo > applications like Moose, so to me the launcher application is more > generic than just Pharo. Seeing a launcher is generically "a > computer program that helps a user to locate and start other computer > programs" [1] to me it makes sense to explicitly keep "Launcher" in > the app name as the default download. I disagree but I don't care enough to argue. If OS X users agree (and maybe the board as well), someone should make the change (that won't be me :-)). -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

Jan. 27, 2016

Re: [Pharo-dev] gtdebugger debug actions buttons

by Blondeau Vincent

I agree with Christophe. Maybe put the buttons on the line under? Cheers, Vincent > -----Message d'origine----- > De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de > Christophe Demarey > EnvoyÃ© : mercredi 27 janvier 2016 09:07 > Ã : Pharo Development List > Objet : [Pharo-dev] gtdebugger debug actions buttons > > Hi, > > I find the new debugger quite but after using it a while, I figure out that the > placement of debug actions (into, over, etc.) buttons leads to make me > overuse the mouse and loose time. > With the spec debugger, buttons are huge and easily accessible . With > GTDebugger, there are at the top right of the window and you need to > move the mouse over the whole window to reach them. > I know there are shortcuts but I would like to see if we can find a better place > for these buttons (and maybe bigger buttons). > > Regards, > Christophe Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

Jan. 27, 2016