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

Re: [Pharo-dev] Opal hook?

by Marcus Denker

On 04 Dec 2013, at 20:02, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> AnUnknownClass subclass: #Adaptor1Example >> instanceVariableNames: 'customers accountID address name phoneNumber' >> classVariableNames: '' >> poolDictionaries: '' >> category: 'Examples-Cookbook' >> >> executes the default action for OCUndeclaredVariableWarning, which is opening a pop-up titled: "Unknown variable ...". Here the error is raised at compilation time, therefore it would have no effect to wrap this with a #on:do: > > I > to me CompilerException should have nothing to do with UI and popup. Then we should be able to pass objects that knows how to handle > the errors in interactive way or not. > > 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â¦ Marcus

Dec. 4, 2013

Re: [Pharo-dev] Komitter

by StÃ©phane Ducasse

Nicolas >From what I understand Kommitter just filters the entities that will be passed as modified and as such does not change the ancestry of a package. Stef On Dec 4, 2013, at 8:12 PM, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > Does Kommitter enables partial commits (cherry picking) for a package? > If so, my question is how does it deal with MC ancestry? > > Imagine I have a package- A.247 from my-trunk. > I merge some A.312 from my-work repository with work in progress. > Now I want to cherry pick the changes which are OK, and publish only those to my-trunk. > I do so in my-trunk/A.313. > Will A.312 be in the ancestry of A.313? > Logically as MC is working, yes, because it is in the ancestry of in-image working copy. > > What if I later download A.313 from my-trunk in a fresh image and try to merge A.312 to finish the work in progress? > IMO, this is not possible, A312 being an ancestor, no change will happen. > > So, it sounds like when I committed my-trunk/A.313 with partial changes, I should have commited my-work/A.314 immediately after with the rest of pending changes... > If I forgot to do so and threw my image away, from a fresh image, it is still possible to load A.312, merge A.313, and publish A.314 in my-work repo. > > But then it rather complicates the flow... If we commit/merge carelessly, we might throw away some valuable work in progress. > The fear of such scenario prevented us to integrate a change from Bert in Squeak/trunk enabling such partial commits (directly from MC UI in Squeak case). > > > 2013/12/4 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > +1 > > > Thanks once more for your effort. This is a really important tool for me. > > > > Uko > > > > >

Dec. 4, 2013

Re: [Pharo-dev] Komitter

by Nicolas Cellier

Err, from a fresh image, we should not merge A.313 but adopt it in our ancestry, else merging will remove all the pending changes... 2013/12/4 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> > Does Kommitter enables partial commits (cherry picking) for a package? > If so, my question is how does it deal with MC ancestry? > > Imagine I have a package- A.247 from my-trunk. > I merge some A.312 from my-work repository with work in progress. > Now I want to cherry pick the changes which are OK, and publish only those > to my-trunk. > I do so in my-trunk/A.313. > Will A.312 be in the ancestry of A.313? > Logically as MC is working, yes, because it is in the ancestry of in-image > working copy. > > What if I later download A.313 from my-trunk in a fresh image and try to > merge A.312 to finish the work in progress? > IMO, this is not possible, A312 being an ancestor, no change will happen. > > So, it sounds like when I committed my-trunk/A.313 with partial changes, I > should have commited my-work/A.314 immediately after with the rest of > pending changes... > If I forgot to do so and threw my image away, from a fresh image, it is > still possible to load A.312, merge A.313, and publish A.314 in my-work > repo. > > But then it rather complicates the flow... If we commit/merge carelessly, > we might throw away some valuable work in progress. > The fear of such scenario prevented us to integrate a change from Bert in > Squeak/trunk enabling such partial commits (directly from MC UI in Squeak > case). > > > 2013/12/4 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > >> +1 >> >> > Thanks once more for your effort. This is a really important tool for >> me. >> > >> > Uko >> > >> >> >> >

Dec. 4, 2013

Re: [Pharo-dev] Komitter

by Nicolas Cellier

Does Kommitter enables partial commits (cherry picking) for a package? If so, my question is how does it deal with MC ancestry? Imagine I have a package- A.247 from my-trunk. I merge some A.312 from my-work repository with work in progress. Now I want to cherry pick the changes which are OK, and publish only those to my-trunk. I do so in my-trunk/A.313. Will A.312 be in the ancestry of A.313? Logically as MC is working, yes, because it is in the ancestry of in-image working copy. What if I later download A.313 from my-trunk in a fresh image and try to merge A.312 to finish the work in progress? IMO, this is not possible, A312 being an ancestor, no change will happen. So, it sounds like when I committed my-trunk/A.313 with partial changes, I should have commited my-work/A.314 immediately after with the rest of pending changes... If I forgot to do so and threw my image away, from a fresh image, it is still possible to load A.312, merge A.313, and publish A.314 in my-work repo. But then it rather complicates the flow... If we commit/merge carelessly, we might throw away some valuable work in progress. The fear of such scenario prevented us to integrate a change from Bert in Squeak/trunk enabling such partial commits (directly from MC UI in Squeak case). 2013/12/4 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > +1 > > > Thanks once more for your effort. This is a really important tool for me. > > > > Uko > > > > >

Dec. 4, 2013

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

by Torsten Bergmann

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

Re: [Pharo-dev] Opal hook?

by StÃ©phane Ducasse

> AnUnknownClass subclass: #Adaptor1Example > instanceVariableNames: 'customers accountID address name phoneNumber' > classVariableNames: '' > poolDictionaries: '' > category: 'Examples-Cookbook' > > executes the default action for OCUndeclaredVariableWarning, which is opening a pop-up titled: "Unknown variable ...". Here the error is raised at compilation time, therefore it would have no effect to wrap this with a #on:do: I do not understand why if an exception is raised why I cannot trap it. [AnUnknownClass subclass: #Adaptor1Example instanceVariableNames: 'customers accountID address name phoneNumber' classVariableNames: '' poolDictionaries: '' category: 'Examples-Cookbook'] on: OCUndeclaredVariableWarning do: [ self halt.] does not halt. The fact that is is at compilation time does not mean anything to me. So why? I'm totally confused by this bad and unexpected behavior. Do you imply that the warning is already trapped and that I cannot take precedence? Probably but this has nothing to do with compilation time. Then to me OCSemanticWarning should be enhanced so that we do not get these silly menus. An exception should work and clients should be able to customise it to (for example introduce menu and dialog with the users but they should not be the only default. We see again this plague of interactive environment not being rethought in the 2013 age. defaultAction self errorNotification ifFalse: [ ^nil ]. ^self openMenuIn: [:labels :lines :caption | UIManager default chooseFrom: labels lines: lines title: caption] but that we could specify the action to be executed instead. to me CompilerException should have nothing to do with UI and popup. Then we should be able to pass objects that knows how to handle the errors in interactive way or not. 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. Stef > [ OpalCompiler new evaluate: 'AnUnknownClass subclass: #Adaptor1Example > instanceVariableNames: ''customers accountID address name phoneNumber'' > classVariableNames: '''' > poolDictionaries: '''' > category: ''Examples-Cookbook''' ] on: OCSemanticWarning do: [ :e | e halt ] > > Here we catch the error, and you can handle it. > Now it is not easily possible to resume the error, because you want a global instead and Opal expects a temp (there are way to resume but with very deep stack manipulation that I do not want to show to young pharoers present on this mailing list). So the best is to retry it. One solution is therefore: > > [ OpalCompiler new evaluate: 'AnUnknownClass subclass: #Adaptor1Example > instanceVariableNames: ''customers accountID address phoneNumber'' > classVariableNames: '''' > poolDictionaries: '''' > category: ''Examples-Cookbook''' ] > on: OCSemanticWarning do: [ :e | > Smalltalk at: e node name put: StubRootClass. > e retry ] > > with e node name answering #AnUnknownClass here. > Now you need to make sure that the exception block is executed for the case of a missing superclass and not something else or you will end up creating loads of globals. > > The exception block should be something similar to: > > [ :e | > e node name first isUppercase and: [ "some condition" ] ifTrue: [ > Smalltalk at: e node name put: StubRootClass. > ^ e retry ]. > e pass ] > > How to undefined and OCUndeclaredVariableWarning relate? > > In your case, while loading from Monticello the code is compiled and evaluated in non interactive mode. Therefore it cannot trigger the default action of OCUndeclaredVariableWarning which is a UI event. So it sets by default the unknown global to: > > Undeclared at: varName asSymbol put: nil. > OCUndeclaredVariable new name: varName asSymbol > > in: OCUndeclaredVariableWarning >>defaultAction > > which then later triggers the code in UndefinedObject.

Dec. 4, 2013

Re: [Pharo-dev] 12259: FileSystem memory reads writesusing a binary stream by default

by Nicolas Cellier

Here would be the Xtream way IMHO: 1) At the end, the file should be handled as binary. 2) A facade BivalentReadStream (and BivalentWriteStream) would be created, able to switch encoding 3) The implementation would be to wrap either directly over the binary stream, or indirectly over an encoded stream which wraps other the binary stream. 4) For write, the facade should just ensure that buffers (if any) are properly flushed, and then just delegate to specialized wrapped streams. 5) For read, it might be a bit more involved if some buffer were used in intermediate wrappers, because they should push back the excess bytes read and restore the state of lower level binary stream... In all case, all should happen thru delegation and the facade should be rather dumb. 2013/12/4 Sven Van Caekenberghe <sven(a)stfx.eu> > > On 04 Dec 2013, at 13:14, Max Leske <maxleske(a)gmail.com> wrote: > > > Let me see what I can come up with. > > To be somewhat compatible with existing streams, your memory stream should > have the concept of âi am binary or textualâ and be able to switch in-place > between these two states (#binary, #ascii). Depending on its state it > should then return bytes or characters (or collections thereof). Have a > look at ZnLimitedReadStream>>#next and/or ZnBivalentWriteStream>>#nextPut: > > To be 100% correct, encoding should be selectable. But maybe a default to > utf-8 would be enough. You could have a look at > ZnCharacter[Read|Write]Stream for inspiration. > > My 2c. > > > On 03.12.2013, at 19:36, Damien Cassou <damien.cassou(a)gmail.com> wrote: > > > >> Thanks Max for the report. Do you have an idea on how we could solve > the problem ? The previous behaviour was not acceptable either because the > streams that came out of a memory filesystem were the only ones with binary > content > >> > >> On Dec 3, 2013 5:35 PM, "Max Leske" <maxleske(a)gmail.com> wrote: > >> Damien, Marcus > >> > >> this change breaks a lot of things in FileSystem-Git. I donât disagree > with the idea that reading characters should be default (one could argue > about itâ¦) but your change makes it IMPOSSIBLE to read bytes because > unprintable characters are discarded! So if my ByteArray is a NULL > terminated string, for instance, I can not check for the NULL termination > anymore. > >> > >> Cheers, > >> Max > > > > >

Dec. 4, 2013

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

by Stephan Eggermont

Nice! I directly tried it loading into 30618 with te latest vm on OS X Mavericks. When loading the configuration as shown in the manual, there was a complaint about a class not found yet. The examples showed up fine though. They look great. The first one with the square/cube I couldnât get the camera viewpoint to move to where I could see it was a cube. That worked much better with the later examples. The session management isnât working out well: saving the image with an open view and quitting, the image crashed on restart. Iâm looking forward to adding some 3D views to PetitDelphi. Stephan

Dec. 4, 2013

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

by StÃ©phane Ducasse

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

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

by StÃ©phane Ducasse

> Would be great to do that. I guess we would easily get the latex version from this right? this is automatic :) and the HTML version and the md version even if some bugs should be fixed. > How should we start? Which Pier installation can we use for this? everything is explained on github PharoForTheEntreprise Let us know if something does not work. Stef > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > On Dec 4, 2013, at 2:22 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> Alex >> >> what about taking the doc and turning it in pier syntax? >> >> Stef >> >> >> >> On Dec 4, 2013, at 2:29 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >> >>> Dear Friends and Colleagues, >>> >>> We are happy to (officially) announce Roassal 3d. Roassal 3d is about creating and animating 3d scenes. It is meant to visualize data. Roassal 3d recently got textures, translucence, additional layouts and various light models. >>> >>> It would be great to receive feedback. Ronie worked very hard on making Roassal3d happen. Milton has put quite some effort on writing documentation and writing examples. A very preliminary version of the documentation may be found on: >>> https://www.dropbox.com/s/mctbza5qfcdxbs3/Roassal3dtutorial.pdf >>> >>> The screenshots contained in this documentation should convey an accurate feeling of what Roassal 3d is up to. >>> >>> Loading Roassal 3d in Pharo 3.0 is trivial, thanks to a configuration. Simply open a workspace and do-it the following code: >>> Gofer new smalltalkhubUser: 'ronsaldo' project: 'roassal3d'; package: 'ConfigurationOfRoassal3d'; load. (Smalltalk at: #ConfigurationOfRoassal3d) loadDevelopment >>> >>> We are also looking for contributors to the documentation, we plan to have a book chapter on it. Get in touch with us! >>> >>> Thanks to Usman, Jean-Baptiste, Igor for their help and contributions. >>> >>> Cheers, >>> Alexandre >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > >

Dec. 4, 2013