September 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] PID of VM ?

by Sven Van Caekenberghe

> On 14 Sep 2015, at 18:46, David T. Lewis <lewis(a)mail.msen.com> wrote: > >> On Mon, Sep 14, 2015 at 8:25 PM, Esteban Lorenzano <estebanlm(a)gmail.com> >> wrote: >>> >>>> On 14 Sep 2015, at 14:21, David T. Lewis <lewis(a)mail.msen.com> wrote: >>>> >>>> >>>> No, OSProcess should not be included in the image. It is intended to be >>>> an external package. >>> >>> mmmÃ¢ÂÂ¦ we want to include it as more and more people requires it and we >>> can profit from having it in the image (same as FFI). >>> why do you think it should be external? >> >> We should distinguish between having it traditionally-in-Image where >> that is the only place it exists and fixes are integrated, and the >> current trend (e.g. in-Image Glamorous Tools) where fixes are >> integrated "upstream" into an external package >> > > Yes, that is what I meant. > > Dave Several packages are in that situation: Zinc, STON, FUEL, ... it works quite well.

Sept. 14, 2015

Re: [Pharo-dev] PID of VM ?

by David T. Lewis

> On Mon, Sep 14, 2015 at 8:25 PM, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: >> >>> On 14 Sep 2015, at 14:21, David T. Lewis <lewis(a)mail.msen.com> wrote: >>> >>> >>> No, OSProcess should not be included in the image. It is intended to be >>> an external package. >> >> mmmÃ¢ÂÂ¦ we want to include it as more and more people requires it and we >> can profit from having it in the image (same as FFI). >> why do you think it should be external? > > We should distinguish between having it traditionally-in-Image where > that is the only place it exists and fixes are integrated, and the > current trend (e.g. in-Image Glamorous Tools) where fixes are > integrated "upstream" into an external package > Yes, that is what I meant. Dave

Sept. 14, 2015

Re: [Pharo-dev] TextAttributes in source code or class comment?

by Martin Dias

On Tue, Sep 8, 2015 at 12:29 PM, Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: > >> On 08 Sep 2015, at 11:03 , Martin Dias <tinchodias(a)gmail.com> wrote: >> >> On Sat, Sep 5, 2015 at 1:10 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: >>> The same for the ]lang[ tag (see issue 15750) >> >> Ok. But I still don't know how to add a url to a method's source code >> or comment from the UI. >> >> I mean, people with a non-English keyboard can produce source code >> with ]lang[, but how can I produce a ]style[ ? >> >> MartÃn > > The whole mechanism is quite broken in Pharo4 upwards: Not sure what to do in Pharo: parse the Text or just ignore the ]style[, but at least file-in should not raise an error. I reported it: https://pharo.fogbugz.com/f/cases/16575/CodeImporter-doesn-t-parse-style-ch… MartÃn

Sept. 14, 2015

[pharo-project/pharo-core]

by GitHub

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

Sept. 14, 2015

[pharo-project/pharo-core] 309117: 50323

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 30911717587a2fa15bc22339ddd55620746dbbdc https://github.com/pharo-project/pharo-core/commit/30911717587a2fa15bc22339… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-09-14 (Mon, 14 Sep 2015) Changed paths: M AST-Core.package/BISimpleFormatter.class/instance/initialization/initialize.st M AST-Core.package/RBMethodNode.class/instance/private/reformatSource.st M AST-Core.package/RBParseTreeSearcher.class/class/private/buildSelectorString_.st M AST-Core.package/RBParser.class/instance/accessing/parseLiterals_.st M AST-Core.package/RBParser.class/instance/private-parsing/parseLiteralArray.st M AST-Core.package/RBParser.class/instance/private-parsing/parseLiteralByteArray.st M AST-Core.package/RBScanner.class/instance/accessing/contents.st M AST-Core.package/RBScanner.class/instance/initialize-release/on_.st M NautilusCommon.package/NautilusClassSelected.class/definition.st R NautilusCommon.package/NautilusClassSelected.class/instance/accessing/selectedClass.st R NautilusCommon.package/NautilusClassSelected.class/instance/accessing/selectedClass_.st R NautilusCommon.package/NautilusClassSelected.class/instance/compatibility/itemClass.st M NautilusCommon.package/NautilusMethodSelected.class/definition.st R NautilusCommon.package/NautilusMethodSelected.class/instance/accessing/selectedMethod.st R NautilusCommon.package/NautilusMethodSelected.class/instance/accessing/selectedMethod_.st R NautilusCommon.package/NautilusMethodSelected.class/instance/compatibility/method.st M NautilusCommon.package/NautilusPackageSelected.class/definition.st R NautilusCommon.package/NautilusPackageSelected.class/instance/accessing/selectedPackage.st R NautilusCommon.package/NautilusPackageSelected.class/instance/accessing/selectedPackage_.st R NautilusCommon.package/NautilusPackageSelected.class/instance/compatibility/package.st M NautilusCommon.package/NautilusProtocolSelected.class/definition.st R NautilusCommon.package/NautilusProtocolSelected.class/instance/accessing/selectedProtocol.st R NautilusCommon.package/NautilusProtocolSelected.class/instance/accessing/selectedProtocol_.st R NautilusCommon.package/NautilusProtocolSelected.class/instance/compatibility/category.st A NautilusCommon.package/NautilusSelectionAnnouncement.class/README.md A NautilusCommon.package/NautilusSelectionAnnouncement.class/definition.st A NautilusCommon.package/NautilusSelectionAnnouncement.class/instance/accessing/selectedClass.st A NautilusCommon.package/NautilusSelectionAnnouncement.class/instance/accessing/selectedClass_.st A NautilusCommon.package/NautilusSelectionAnnouncement.class/instance/accessing/selectedMethod.st A NautilusCommon.package/NautilusSelectionAnnouncement.class/instance/accessing/selectedMethod_.st A NautilusCommon.package/NautilusSelectionAnnouncement.class/instance/accessing/selectedPackage.st A NautilusCommon.package/NautilusSelectionAnnouncement.class/instance/accessing/selectedPackage_.st A NautilusCommon.package/NautilusSelectionAnnouncement.class/instance/accessing/selectedProtocol.st A NautilusCommon.package/NautilusSelectionAnnouncement.class/instance/accessing/selectedProtocol_.st A NautilusCommon.package/NautilusSelectionAnnouncement.class/instance/compatibility/category.st A NautilusCommon.package/NautilusSelectionAnnouncement.class/instance/compatibility/itemClass.st A NautilusCommon.package/NautilusSelectionAnnouncement.class/instance/compatibility/method.st A NautilusCommon.package/NautilusSelectionAnnouncement.class/instance/compatibility/package.st A Polymorph-Widgets.package/MorphicUIManager.class/instance/display/showWaitCursorWhile_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50322.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50323.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50322.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50323.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M System-Changes.package/ChangeRecord.class/instance/initialization/fileIn.st M System-Changes.package/ChangeSet.class/instance/filein%2Fout/fileOut.st A UIManager.package/UIManager.class/instance/display/showWaitCursorWhile_.st Log Message: ----------- 50323 16566 Replace WriteStream with writeStream message send in AST-Core https://pharo.fogbugz.com/f/cases/16566 16556 Nautilus selection announcements intersect as they are in a hierarchy https://pharo.fogbugz.com/f/cases/16556 16539 System-Changes and Compression should not depend on Graphics-Display Objects https://pharo.fogbugz.com/f/cases/16539 http://files.pharo.org/image/50/50323.zip

Sept. 14, 2015

Re: [Pharo-dev] Querying hierarchical entities in Voyage

by Yuriy Tymchuk

Thanks Norbert! > On 14 Sep 2015, at 17:31, Norbert Hartl <norbert(a)hartl.name> wrote: > > >> Am 14.09.2015 um 15:41 schrieb Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: >> >> Hi, >> >> how can I query all the objects from a hierarchy? Should a do separate query for each subclass and then concatenate the results? Is there a more efficient solution? >> > You can put something like that in your base class > > mongoContainer > <mongoContainer> > ^ VOMongoContainer new > collectionName: 'user'; > yourself > > So every subclass will be stored in the user collection as well. If you query on the base class you will get all subclasses as well. > > Norbert > >> Also what is the place to read about Voyage? >> > > >

Sept. 14, 2015

Re: [Pharo-dev] Querying hierarchical entities in Voyage

by Norbert Hartl

> Am 14.09.2015 um 15:41 schrieb Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > > Hi, > > how can I query all the objects from a hierarchy? Should a do separate query for each subclass and then concatenate the results? Is there a more efficient solution? > You can put something like that in your base class mongoContainer <mongoContainer> ^ VOMongoContainer new collectionName: 'user'; yourself So every subclass will be stored in the user collection as well. If you query on the base class you will get all subclasses as well. Norbert > Also what is the place to read about Voyage? >

Sept. 14, 2015

Re: [Pharo-dev] [Pharo-users] [Survey] QualityAssistant experience mini-survey

by Mariano Martinez Peck

OK...I see some of those. Look attached screenshot. On Mon, Sep 14, 2015 at 11:56 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Iâve downloaded a fresh Pharo 4 image and opened browser at: > Object>>#at:put: > > Looking at it should show you: > > If you donât see the âtoolsâ and âcrossâ icons, then something strange is > going on. In this case, can you send me the image that you are using? > > Also the âban" is described as âskippingâ in doc. I forgot to update it. > > Uko > > On 14 Sep 2015, at 16:20, Mariano Martinez Peck <marianopeck(a)gmail.com> > wrote: > > Hi Yuriy, > > Another thing I cannot see in the documentation is about ban. To me is > really important how is persisted the banning. > How do you prevent the banning from being lost when I take a new image? > Can I export bans to fuel and re import in another image? > Some time ago when there was the manifiesto classes, the banning was > stored there, and so such class could be stored in monticello as part of > your code, which was a nice idea. But at the same time, it's hard to keep a > banning since you refactor... so..that's another question..do you do > something with banning upon certain refactors? > > Thanks! > > > On Mon, Sep 14, 2015 at 10:25 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> > wrote: > >> Hi Mariano, >> >> thanks for participating! You can read about the features here: >> https://github.com/Uko/QualityAssistant#actions >> >> If something is not clear please let me know, so I can improve. >> >> On 14 Sep 2015, at 15:21, Mariano Martinez Peck <marianopeck(a)gmail.com> >> wrote: >> >> OK Done. >> Where I can see the answers now? :) I put I didn't know many of the >> features (I use it 99% of the time in Nautilus) and I do want to know now! >> >> >> On Mon, Sep 14, 2015 at 5:01 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> >> wrote: >> >>> Dear Pharoers, >>> >>> I kindly ask you to participate in the QualityAssistant mini-survey: >>> http://rio.inf.usi.ch/survey/index.php/818331. >>> It will take only a few minutes of your time (or less), and will give us >>> a better understanding of how QualityAssistant is currently used and how to >>> improve it. >>> >>> Cheers! >>> Yuriy >>> >> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > > > -- Mariano http://marianopeck.wordpress.com

Sept. 14, 2015

System-Announcements: add a ProtocolRenamed announcement

by Skip Lentz

Hello, Right now, when you add or remove a protocol to a class you get two announcements (ignoring methods that may have been removed): 1. Protocol{Added,Removed} 2. ClassReorganized. But when you rename a protocol, you get just ClassReorganized (again, ignoring the method recategorizations). >From this announcement, you only have access to the new class. So there is no way to tell the change. To resolve this, I think a ProtocolRenamed announcement should be added, just like there is a CategoryRenamed announcement. This way Epicea can also log this, which it currently does not do. It logs the recategorizations of the methods in the protocol, but not the rename of the protocol. So as far as we can tell from the log, we canât see if the renamed protocol still exists or not. Please share your thoughts, Skip

Sept. 14, 2015

Re: [Pharo-dev] [Pharo-users] [Survey] QualityAssistant experience mini-survey

by Yuriy Tymchuk

Iâve downloaded a fresh Pharo 4 image and opened browser at: Object>>#at:put: Looking at it should show you: If you donât see the âtoolsâ and âcrossâ icons, then something strange is going on. In this case, can you send me the image that you are using? Also the âban" is described as âskippingâ in doc. I forgot to update it. Uko > On 14 Sep 2015, at 16:20, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > Hi Yuriy, > > Another thing I cannot see in the documentation is about ban. To me is really important how is persisted the banning. > How do you prevent the banning from being lost when I take a new image? Can I export bans to fuel and re import in another image? > Some time ago when there was the manifiesto classes, the banning was stored there, and so such class could be stored in monticello as part of your code, which was a nice idea. But at the same time, it's hard to keep a banning since you refactor... so..that's another question..do you do something with banning upon certain refactors? > > Thanks! > > > On Mon, Sep 14, 2015 at 10:25 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>> wrote: > Hi Mariano, > > thanks for participating! You can read about the features here: https://github.com/Uko/QualityAssistant#actions <https://github.com/Uko/QualityAssistant#actions> > > If something is not clear please let me know, so I can improve. > >> On 14 Sep 2015, at 15:21, Mariano Martinez Peck <marianopeck(a)gmail.com <mailto:marianopeck@gmail.com>> wrote: >> >> OK Done. >> Where I can see the answers now? :) I put I didn't know many of the features (I use it 99% of the time in Nautilus) and I do want to know now! >> >> >> On Mon, Sep 14, 2015 at 5:01 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>> wrote: >> Dear Pharoers, >> >> I kindly ask you to participate in the QualityAssistant mini-survey: http://rio.inf.usi.ch/survey/index.php/818331 <http://rio.inf.usi.ch/survey/index.php/818331>. >> It will take only a few minutes of your time (or less), and will give us a better understanding of how QualityAssistant is currently used and how to improve it. >> >> Cheers! >> Yuriy >> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com <http://marianopeck.wordpress.com/> > > > > > -- > Mariano > http://marianopeck.wordpress.com <http://marianopeck.wordpress.com/>

Sept. 14, 2015