December 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Nautilus] Selecting package

by Roberto Minelli

Hi Stef, I spoke with Esteban before, however thanks for the clarification. IMHO however the current structure is confusing, and names are misleading. The thing about packages, categories, namespaces and what not has always been not perfect for me, nor in Pharo nor in many other PLs. The way I would have done it, conceptually, independently of Nautilus, Monticello and whatever else is the following: A package is a container used to structure a project, it contains - zero or more classes - zero or more other packages This model would be damn simple, and consistent and you should not explicitly think about how to structure your things.. I can create a package âDFlowâ put some classes, then I create another package 'DFlow-Coreâ which *automatically* goes into the âDFlowâ package because it starts with the same prefix plus the dash, which is somewhat our convention, right? And however we can think of mechanisms to cope with other kind of automatic sub-packaging and/or manual removal (in case our heuristics fail). For me having packages, groups, tags, and categories is too much. Cheers, R On Dec 4, 2013, at 6:59 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On Dec 4, 2013, at 4:10 PM, Roberto Minelli <roberto.minelli(a)usi.ch> wrote: > >> Hi guys, >> >> I recently moved my tool to Pharo 3 and I am experiencing problems with the Nautilus. >> >> Long story sort: Why the argument of Nautilus>>#selectedPackage: aPackage is *not* a package but some weird PackageTreeSelection or subclass of it? > > I guess that if you would get simply the rpackage ie the model you would be in trouble if you want to do some ui stuff with the representation of the package. > Now if you have a PackageTreeSelection then you can dispatch to the selection and avoid ifs and crawling from rpackage to nautilus. > > So have a look at the code it should not be that complex and last time I looked at the code when esteban was writing it, it looks good to me. > Less tests, more dispatch. > > >> I donât followed (unfortunately) the evolution of the PackageTreeModel in general.. so I donât really know how to proceed.. In the end Iâll need the RPackage of the PackageTreeSelectionâ¦ >> >> Another question: what is a RPackageTag? > > Packages contain tag for classes (like old categories but per packages) > >> >> I am confused. >> >> Cheers and thanks in advance for any answer, >> R > >

Dec. 4, 2013

Committing slices to Pharo30Inbox still doesn't work for me

by Stephan Eggermont

Hereâs a new slice, the corresponding packages are in the inbox.

Dec. 4, 2013

[update 3.0] #30621

by StÃ©phane Ducasse

30621 ----- - issue 12317: Better way to let the user handle missing class when loading code https://pharo.fogbugz.com/f/cases/12317/Better-way-to-let-the-user-handle-m… - issue 12335: Some fixes https://pharo.fogbugz.com/f/cases/12335/Some-fixes - issue 12336: Do not open Komitter modal https://pharo.fogbugz.com/f/cases/12336/Do-not-open-Komitter-modal Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-MorphicAdapters-Stephane… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Core-StephaneDucasse.254… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Komitter-StephaneDucasse.58.d… http://smalltalkhub.com/mc/Pharo/Pharo30/main/CodeImport-StephaneDucasse.42…

Dec. 4, 2013

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/30621 Home: https://github.com/pharo-project/pharo-core

Dec. 4, 2013

[pharo-project/pharo-core] 4f381f: 30621

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 4f381f0027728a768390f2f648edbdb1ac123088 https://github.com/pharo-project/pharo-core/commit/4f381f0027728a768390f2f6… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-12-04 (Wed, 04 Dec 2013) Changed paths: A CodeImport.package/MethodDeclaration.class/instance/importing/handleMissingBehavior.st M CodeImport.package/MethodDeclaration.class/instance/importing/importFor_.st A CodeImport.package/MissingClassError.class/README.md A CodeImport.package/MissingClassError.class/class/instance creation/className_.st A CodeImport.package/MissingClassError.class/definition.st A CodeImport.package/MissingClassError.class/instance/accessing/className_.st A CodeImport.package/MissingClassError.class/instance/accessing/superclassName.st A CodeImport.package/MissingClassError.class/instance/accessing/superclassName_.st A CodeImport.package/MissingClassError.class/instance/actions/asResumable.st A CodeImport.package/MissingClassError.class/instance/actions/defineClass.st A CodeImport.package/MissingClassError.class/instance/testing/isResumable.st M Komitter.package/Komitter.class/instance/accessing/stagingArea.st R Komitter.package/Komitter.class/instance/opening/open.st M Komitter.package/Komitter.class/instance/opening/openAndCommitToMonticello.st A Komitter.package/Komitter.class/instance/opening/openAndDo_.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script276.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30621.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Core.package/DialogWindowModel.class/instance/initialize/initialize.st M Spec-Core.package/SpecDialogWindow.class/instance/accessing/toolbar_.st M Spec-Core.package/SpecDialogWindow.class/instance/protocol/setToolbarFrom_.st M Spec-Core.package/TextInputFieldModel.class/instance/initialization/initialize.st A Spec-MorphicAdapters.package/MorphicDialogWindowAdapter.class/instance/spec protocol/toolbar_.st A Spec-MorphicAdapters.package/MorphicTextInputFieldAdapter.class/instance/spec protocol/encrypted_.st M Spec-MorphicAdapters.package/SpecTreeNodeModel.class/instance/protocol/lastClicked_.st Log Message: ----------- 30621 - issue 12317: Better way to let the user handle missing class when loading code https://pharo.fogbugz.com/f/cases/12317/Better-way-to-let-the-user-handle-m… - issue 12335: Some fixes https://pharo.fogbugz.com/f/cases/12335/Some-fixes - issue 12336: Do not open Komitter modal https://pharo.fogbugz.com/f/cases/12336/Do-not-open-Komitter-modal http://files.pharo.org/image/30/30621.zip

Dec. 4, 2013

Re: [Pharo-dev] Opal hook?

by StÃ©phane Ducasse

>> Ok I will check something on UndefinedObject to start with. >> Then it would be fun to prototype a kind of strategy hiearchy on the side (extracted from also) behavior of OCSemanticsError >> It was nice to see it and since now I'm ok to have a look at the compiler code it was interesting. >> > > The current design is motivated mostly by backward compatibility, not anything else. I see :) I would really to see an headless, interactive and scriptable scenarios to be exercised. So this is good it will get better :) Stef

Dec. 4, 2013

Re: [Pharo-dev] Opal hook?

by Marcus Denker

On 04 Dec 2013, at 20:34, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >>> As a clear example, this is just bad that each time we want to change the UI message we have to change the compiler exception. >>> ugly at wish. >>> >>> I have no cycle to fix that now. I will check if I can get something in UndefinedObject so that I can continue to work on my task. >>> >> >> The whole exception / error handling of the compiler needs to be deeply rethought. >> Sadly I have no cycles free in my brain to even start to think about it, and, even more important, we should wait until the old >> Compiler is removedâ¦ > > Ok I will check something on UndefinedObject to start with. > Then it would be fun to prototype a kind of strategy hiearchy on the side (extracted from also) behavior of OCSemanticsError > It was nice to see it and since now I'm ok to have a look at the compiler code it was interesting. > The current design is motivated mostly by backward compatibility, not anything else. Marcus

Dec. 4, 2013

Re: [Pharo-dev] Opal hook?

by StÃ©phane Ducasse

>> As a clear example, this is just bad that each time we want to change the UI message we have to change the compiler exception. >> ugly at wish. >> >> I have no cycle to fix that now. I will check if I can get something in UndefinedObject so that I can continue to work on my task. >> > > The whole exception / error handling of the compiler needs to be deeply rethought. > Sadly I have no cycles free in my brain to even start to think about it, and, even more important, we should wait until the old > Compiler is removedâ¦ Ok I will check something on UndefinedObject to start with. Then it would be fun to prototype a kind of strategy hiearchy on the side (extracted from also) behavior of OCSemanticsError It was nice to see it and since now I'm ok to have a look at the compiler code it was interesting. Stef > > Marcus >

Dec. 4, 2013

Re: [Pharo-dev] [ANN] Roassal 3d

by Marcus Denker

On 04 Dec 2013, at 20:30, milton mamani <akevalion(a)gmail.com> wrote: > > 3. Providing a script is so "old style" and hard to remember - why not define a #stable > and put your config into MetaRepoForPharo30 > So others can easily load it via ConfigurationBrowser with a few clicks in a fresh image. even better: have a jerkins build where people can download an imageâ¦ Marcus

Dec. 4, 2013

Re: [Pharo-dev] [ANN] Roassal 3d

by milton mamani

Hi Alexandre, Ronie, Milton, first: this is a cool project! Then a few comments: 1. When using the script in a fresh Pharo3.0 Latest update: #30620 it complains: This package depends on the following classes: ROAthensMorph You must resolve these dependencies before you will be able to load these definitions: R3MorphOverlay clear Nonetheless one can proceed and it loads This is a bug, we are working to fix it. 2. If I use the samples from the tutorial PDF and copy them into a Pharo workspace they are not accepted by Pharo - looks like an encoding issue in the PDF (when copying from Adobe PDF viewer on Windows into Pharo) When I type the samples manually they work There is an issue with dropbox and PDF. You can download the file and open it, that should work. 3. Providing a script is so "old style" and hard to remember - why not define a #stable and put your config into MetaRepoForPharo30 So others can easily load it via ConfigurationBrowser with a few clicks in a fresh image. We are going to review|work on that 4. Did I already told you that this is a cool project? 5. See 4. Thank you Bye 2013/12/4 Torsten Bergmann <astares(a)gmx.de> > Hi Alexandre, Ronie, Milton, > > first: this is a cool project! > > Then a few comments: > > 1. When using the script in a fresh Pharo3.0 Latest update: #30620 it > complains: > > This package depends on the following classes: > ROAthensMorph > You must resolve these dependencies before you will be able to load > these definitions: > R3MorphOverlay > clear > > Nonetheless one can proceed and it loads > > 2. If I use the samples from the tutorial PDF and copy them into a Pharo > workspace they are not accepted by Pharo - looks like an encoding > issue in the PDF > (when copying from Adobe PDF viewer on Windows into Pharo) > > When I type the samples manually they work > > 3. Providing a script is so "old style" and hard to remember - why not > define a #stable > and put your config into MetaRepoForPharo30 > So others can easily load it via ConfigurationBrowser with a few > clicks in a fresh image. > > 4. Did I already told you that this is a cool project? > > 5. See 4. > > Bye > T. > >

Dec. 4, 2013