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

Re: [Pharo-dev] Compiling a method with a new iv raises DNU

by Yuriy Tymchuk

Hi Stef. Can you tell me in which class do you add this? Because it does not happen for every class. There was an issue that one on the rules destroying ASTs, but we solved it about a month ago. Uko > On 04 Sep 2015, at 10:45, stepharo <stepharo(a)free.fr> wrote: > > Apparently there is something wrong in the ASTCache. > The only solution I found to continue to work was to remove the QAPlugin. > > > Le 4/9/15 10:21, stepharo a Ã©crit : >> Here is the scenario >> >> I added the method >> >> comment >> >> ^ comment >> >> and I get now a DNU >> >> doSemanticAnalysisIn: >> >> >> at: aCompiledMethod >> ^ self >> at: aCompiledMethod >> ifAbsentPut: [ >> aCompiledMethod parseTree doSemanticAnalysisIn: aCompiledMethod methodClass ] >> >> >> where aCompiledMethod is StoreBlessing>>#comment >> >> but the parseTree is nil :( >> >> How this behavior can happen? >> >> Stef >> >> > >

Sept. 4, 2015

Re: [Pharo-dev] Compiling a method with a new iv raises DNU

by stepharo

Apparently there is something wrong in the ASTCache. The only solution I found to continue to work was to remove the QAPlugin. Le 4/9/15 10:21, stepharo a Ã©crit : > Here is the scenario > > I added the method > > comment > > ^ comment > > and I get now a DNU > > doSemanticAnalysisIn: > > > at: aCompiledMethod > ^ self > at: aCompiledMethod > ifAbsentPut: [ > aCompiledMethod parseTree doSemanticAnalysisIn: > aCompiledMethod methodClass ] > > > where aCompiledMethod is StoreBlessing>>#comment > > but the parseTree is nil :( > > How this behavior can happen? > > Stef > >

Sept. 4, 2015

Re: [Pharo-dev] [Pharo5] Improvements for Anonymous classes

by stepharo

in my 99 JOOP paper :) Le 21/8/15 08:34, Yuriy Tymchuk a Ã©crit : > Hi, where can I read more about anonymous classes. They look like amazing stuff to be used in tests. > > Uko > > >> On 21 Aug 2015, at 08:38, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> Hi, >> >> Besides cleaning for the bootstrap, another thing we did yesterday was improving handling of >> Anonymous classes. >> >> 1) you can now browse methods of anonymous classes with nautilus *if* they inherit from Object (the main case) >> >> myClass := Object newAnonymousSubclass. myClass compile: 'test ^5'. myClass browse >> >> 2) #classInstaller for anonymous classes now returns an AnonymousClassInstaller >> >> 3) class builder name checking was fixed to not raise an error for the ânamesâ used for Anonymous classes >> >> ==> you can use #addSlot: on anonymous classes. >> >> >> To improve: >> >> - browser should show some kind of class definition so one can see the superclass >> - it would be nice to be able to browse "Behavior newâ, but in most cases people use >> anon subclasses of existing classes, so not that important. >> >> Marcus > >

Sept. 4, 2015

Re: [Pharo-dev] Announcements in Nautilus

by stepharo

I will not reply publicly on the true reason of that situation :) Now what we should do is to continue to simplify the code of Nautilus (we made great steps with Franck). And yuriy if you have some fixes please let us know. Stef Le 4/9/15 09:22, Yuriy Tymchuk a Ã©crit : > Hi, > > I find announcements in Nautilus a bit strange. I guess you are familiar with QualityAssistant. To display the critics about the currently selected entity I need to know which one is selected. There is NautilusMethodSelected and NautilusClassSelected announcements. But here is a small detail, if you select a method, both of them are fired i.e. for the methodâs class and the method itself. For me it does not make any sense because I need to show critics only for currently selected source code. > > Moreover if I need to show something about the class while a method is selected, I can just ask the method for its class, right? > > Does anybody need this double announcing? (Maybe it is quadruple, I havenât checked for a package and protocol) > > Cheers! > Uko >

Sept. 4, 2015

Compiling a method with a new iv raises DNU

by stepharo

Here is the scenario I added the method comment ^ comment and I get now a DNU doSemanticAnalysisIn: at: aCompiledMethod ^ self at: aCompiledMethod ifAbsentPut: [ aCompiledMethod parseTree doSemanticAnalysisIn: aCompiledMethod methodClass ] where aCompiledMethod is StoreBlessing>>#comment but the parseTree is nil :( How this behavior can happen? Stef

Sept. 4, 2015

Re: [Pharo-dev] Announcements in Nautilus

by Nicolai Hess

Another related issue: 12535 <https://pharo.fogbugz.com/f/cases/12535/To-many-updates-on-the-methods-list> To many updates on the methods list (changes aren't applicable anymore, because to many things had changed). Sometimes I am working on this and try to solve this. But I failed so far. The way Nautilus holds the current selection (model and UI) and how it propagate changes (selectX, selectXwithoutChangingSelection, select silenty ...) doesn't really work good ( or I just don't understand it). (And with rubric as TextModel, this is getting even more complicated). 2015-09-04 9:34 GMT+02:00 Christophe Demarey <Christophe.Demarey(a)inria.fr>: > > Le 4 sept. 2015 Ã 09:22, Yuriy Tymchuk a Ã©crit : > > > Hi, > > > > I find announcements in Nautilus a bit strange. I guess you are familiar > with QualityAssistant. To display the critics about the currently selected > entity I need to know which one is selected. There is > NautilusMethodSelected and NautilusClassSelected announcements. But here is > a small detail, if you select a method, both of them are fired i.e. for the > methodâs class and the method itself. > > > Does anybody need this double announcing? (Maybe it is quadruple, I > havenât checked for a package and protocol) > > > And the best is that the UI is refreshed for each announcement. Then you > understand why Nautilus is slow. > Franck did some improvements but Nautilus still refresh itself far too > much (there was 12 refresh calls for the source code panel ...). > > It looks like a design flaw: there should be only one announcement for a > selection change. You could define PackageSelectionChanged, > ClassSelectionChanged, ProtocolSelectionChanged, MethodSelectionChanged, > each one with more or less info (I mean method will have the protocol, > class, and package).

Sept. 4, 2015

Re: [Pharo-dev] Need a decision on subString: vs substring:

by Thierry Goubier

2015-09-04 9:39 GMT+02:00 Christophe Demarey <Christophe.Demarey(a)inria.fr>: > I don't like so much compatibility packages because people will not update > their code and expect the compatibility package to always work. > Why not just use what Marcus did for deprecations? Create a rule to > transform ANSI Smalltalk to Pharo "magicly'? > An extension package with a set of rewrite rules that we can use to: - port code for old Pharo versions to new Pharo versions (in some areas of Pharo, many things disappear/are renamed without deprecation between versions) - port non-Pharo code to Pharo. It would be really great if those rules could be applied when loading the package via MC or FileIn, not when the package is already loaded, otherwise you need both a compatibility layer, and the rewriting rules. Probably a lot easier to do by, say, replacing the MC code model by the RB code model. Or, when loading a package, loading it through a MC defintion, convert it to RB model, apply rules, convert to Ring, compile Ring... I like simple things :) Thierry > > Le 3 sept. 2015 Ã 22:44, Gabriel Cotelli a Ã©crit : > > I've second Sven here. In case anybody wants the old method put it in some > ANSICompatibility package to ease porting packages from ANSI-compliant > Smalltalks. > > On Thu, Sep 3, 2015 at 4:54 PM, Sven Van Caekenberghe <sven(a)stfx.eu> > wrote: > >> We went through a lot of effort/pain to move to substring, I think for >> good reasons. >> >> > On 03 Sep 2015, at 21:31, Dimitris Chloupis <kilon.alios(a)gmail.com> >> wrote: >> > >> > why not both ? >> >> Because the proper English spelling is with lowercase >> >> https://duckduckgo.com/?q=define%3A+substring&ia=definition >> >> > On Thu, Sep 3, 2015 at 9:45 PM stepharo <stepharo(a)free.fr> wrote: >> > *) It appears that Pharo is removing subString: in favor of >> > substring:. The ANSI standard defines subString:. >> > >> > I was not aware of it. In fact ANSI is bad and totally incomplete >> > (for example we studies strings and this is a mess and totally >> > incomplete). >> > Now we should probably add it. I will send the mail to the >> > mailing-list and let people decide. >> > >> > >> > >> > >> >> >> > >

Sept. 4, 2015

Re: [Pharo-dev] Need a decision on subString: vs substring:

by Christophe Demarey

I don't like so much compatibility packages because people will not update their code and expect the compatibility package to always work. Why not just use what Marcus did for deprecations? Create a rule to transform ANSI Smalltalk to Pharo "magicly'? Le 3 sept. 2015 Ã 22:44, Gabriel Cotelli a Ã©crit : > I've second Sven here. In case anybody wants the old method put it in some ANSICompatibility package to ease porting packages from ANSI-compliant Smalltalks. > > On Thu, Sep 3, 2015 at 4:54 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > We went through a lot of effort/pain to move to substring, I think for good reasons. > > > On 03 Sep 2015, at 21:31, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > > > > why not both ? > > Because the proper English spelling is with lowercase > > https://duckduckgo.com/?q=define%3A+substring&ia=definition > > > On Thu, Sep 3, 2015 at 9:45 PM stepharo <stepharo(a)free.fr> wrote: > > *) It appears that Pharo is removing subString: in favor of > > substring:. The ANSI standard defines subString:. > > > > I was not aware of it. In fact ANSI is bad and totally incomplete > > (for example we studies strings and this is a mess and totally > > incomplete). > > Now we should probably add it. I will send the mail to the > > mailing-list and let people decide. > > > > > > > > > > >

Sept. 4, 2015

Re: [Pharo-dev] Announcements in Nautilus

by Christophe Demarey

Le 4 sept. 2015 Ã 09:22, Yuriy Tymchuk a Ã©crit : > Hi, > > I find announcements in Nautilus a bit strange. I guess you are familiar with QualityAssistant. To display the critics about the currently selected entity I need to know which one is selected. There is NautilusMethodSelected and NautilusClassSelected announcements. But here is a small detail, if you select a method, both of them are fired i.e. for the methodâs class and the method itself. > Does anybody need this double announcing? (Maybe it is quadruple, I havenât checked for a package and protocol) And the best is that the UI is refreshed for each announcement. Then you understand why Nautilus is slow. Franck did some improvements but Nautilus still refresh itself far too much (there was 12 refresh calls for the source code panel ...). It looks like a design flaw: there should be only one announcement for a selection change. You could define PackageSelectionChanged, ClassSelectionChanged, ProtocolSelectionChanged, MethodSelectionChanged, each one with more or less info (I mean method will have the protocol, class, and package).

Sept. 4, 2015

Announcements in Nautilus

by Yuriy Tymchuk

Hi, I find announcements in Nautilus a bit strange. I guess you are familiar with QualityAssistant. To display the critics about the currently selected entity I need to know which one is selected. There is NautilusMethodSelected and NautilusClassSelected announcements. But here is a small detail, if you select a method, both of them are fired i.e. for the methodâs class and the method itself. For me it does not make any sense because I need to show critics only for currently selected source code. Moreover if I need to show something about the class while a method is selected, I can just ask the method for its class, right? Does anybody need this double announcing? (Maybe it is quadruple, I havenât checked for a package and protocol) Cheers! Uko

Sept. 4, 2015

When I drag and drop a method between two classes and two nautilus browser

by stepharo

When I drag and drop a method between two classes and two nautilus browser. I get a DNU isDefault because package returns nil This is due to the execution of RBUnpackageCOdeRule isUnpackaged: anEntity ^ anEntity package isDefault https://pharo.fogbugz.com/f/cases/16474/When-I-drag-and-drop-a-method-betwe…

Sept. 4, 2015

Re: [Pharo-dev] Need a decision on subString: vs substring:

by Dale Henrichs

+1 for an ANSICompatibility package ... ANSI shouldn't hold Pharo back, and an ANSICompatibility package allows for cross-dialect code sharing which was the aim of the ANSI standard in the first place. Dale On 9/3/15 5:51 PM, Ben Coman wrote: > On Fri, Sep 4, 2015 at 4:44 AM, Gabriel Cotelli <g.cotelli(a)gmail.com> wrote: >> I've second Sven here. In case anybody wants the old method put it in some >> ANSICompatibility package to ease porting packages from ANSI-compliant >> Smalltalks. >> >> On Thu, Sep 3, 2015 at 4:54 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> We went through a lot of effort/pain to move to substring, I think for >>> good reasons. >>> >>>> On 03 Sep 2015, at 21:31, Dimitris Chloupis <kilon.alios(a)gmail.com> >>>> wrote: >>>> >>>> why not both ? >>> Because the proper English spelling is with lowercase > +1. As a consequence, its the form that has won industry wide. > Aligning on this provides a small part of an accumulation of items > that lower the friction of adoption from the wider industry. On the > flip side, even though are potentially more non-Smalltalkers who may > adopt Pharo, others from existing Smalltalker dialects may be more > likely to transfer, so its good to not alienate them. So it may be > useful to have an ANSICompatibility package available in the Catalog > Browser that you can point people to - a box to tick on the checklist > to reduce the barriers to entry. > > cheers -ben > >>> https://duckduckgo.com/?q=define%3A+substring&ia=definition >>> >>>> On Thu, Sep 3, 2015 at 9:45 PM stepharo <stepharo(a)free.fr> wrote: >>>> *) It appears that Pharo is removing subString: in favor of >>>> substring:. The ANSI standard defines subString:. >>>> >>>> I was not aware of it. In fact ANSI is bad and totally incomplete >>>> (for example we studies strings and this is a mess and totally >>>> incomplete). >>>> Now we should probably add it. I will send the mail to the >>>> mailing-list and let people decide. >>>> >>>> >>>> >>>> >>>

Sept. 4, 2015

Re: [Pharo-dev] Need a decision on subString: vs substring:

by Ben Coman

On Fri, Sep 4, 2015 at 4:44 AM, Gabriel Cotelli <g.cotelli(a)gmail.com> wrote: > I've second Sven here. In case anybody wants the old method put it in some > ANSICompatibility package to ease porting packages from ANSI-compliant > Smalltalks. > > On Thu, Sep 3, 2015 at 4:54 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> We went through a lot of effort/pain to move to substring, I think for >> good reasons. >> >> > On 03 Sep 2015, at 21:31, Dimitris Chloupis <kilon.alios(a)gmail.com> >> > wrote: >> > >> > why not both ? >> >> Because the proper English spelling is with lowercase +1. As a consequence, its the form that has won industry wide. Aligning on this provides a small part of an accumulation of items that lower the friction of adoption from the wider industry. On the flip side, even though are potentially more non-Smalltalkers who may adopt Pharo, others from existing Smalltalker dialects may be more likely to transfer, so its good to not alienate them. So it may be useful to have an ANSICompatibility package available in the Catalog Browser that you can point people to - a box to tick on the checklist to reduce the barriers to entry. cheers -ben >> >> https://duckduckgo.com/?q=define%3A+substring&ia=definition >> >> > On Thu, Sep 3, 2015 at 9:45 PM stepharo <stepharo(a)free.fr> wrote: >> > *) It appears that Pharo is removing subString: in favor of >> > substring:. The ANSI standard defines subString:. >> > >> > I was not aware of it. In fact ANSI is bad and totally incomplete >> > (for example we studies strings and this is a mess and totally >> > incomplete). >> > Now we should probably add it. I will send the mail to the >> > mailing-list and let people decide. >> > >> > >> > >> > >> >> >

Sept. 4, 2015

Re: [Pharo-dev] [squeak-dev] FFI callbacks

by Eliot Miranda

Hi Craig, you need Alien-eem.24 Here's Alien class>>exampleCqsort "Call the libc qsort function (which requires a callback)." "Alien exampleCqsort" "(Time millisecondsToRun: [100 timesRepeat: [Alien exampleCqsort]]) / 100.0" | cb rand nElements sizeofDouble values orig sort | rand := Random new. values := Alien newC: (nElements := 100) * (sizeofDouble := 8). 1 to: values dataSize by: sizeofDouble do: [:i| values doubleAt: i put: rand next]. orig := (1 to: values dataSize by: sizeofDouble) collect: [:i| values doubleAt: i]. cb := Callback signature: #(int (*)(const void *, const void *)) block: [ :arg1 :arg2 | ((arg1 doubleAt: 1) - (arg2 doubleAt: 1)) sign]. (Alien lookup: 'qsort' inLibrary: Alien libcName) primFFICallResult: nil with: values pointer with: nElements with: sizeofDouble with: cb thunk. sort := (1 to: values dataSize by: sizeofDouble) collect: [:i| values doubleAt: i]. values free. ^orig -> sort The above example uses Alien to make the callout. To use it with the FFI simply pass cb pointer as the argument as is done above. Implementation: The way that it works is in two parts - the VM passes up a pointer to a structure from which all arguments, stacked and in registers (because the VM has copied the register args into the struct) can be accessed, and through which the result can be returned. - the image level provides marshalling methods that match the signature in the callback So e.g. with a callback of Callback signature: #(int (*)(const void *, const void *)) block: [ :arg1 :arg2 | ((arg1 doubleAt: 1) - (arg2 doubleAt: 1)) sign] the marshalling methods are in Callback's signature protocol: Callback>>voidstarvoidstarRetint: callbackContext sp: spAlien <signature: #(int (*)(const void *, const void *)) abi: 'IA32'> ^callbackContext wordResult: (block value: (Alien forPointer: (spAlien unsignedLongAt: 1)) value: (Alien forPointer: (spAlien unsignedLongAt: 5))) where spAlien is an Alien pointing to a VMCallbackContext32. For ARM support we would add Callback>>voidstarvoidstarRetint: callbackContext sp: spAlien intRegArgs: regsAlien <signature: #(int (*)(const void *, const void *)) abi: 'ARMV5'> ^callbackContext wordResult: (block value: (Alien forPointer: (regsAlien unsignedLongAt: 1)) value: (Alien forPointer: (regsAlien unsignedLongAt: 5))) Basically the idea is that the selector of the method doesn't matter except for the number of arguments. What's important is the pragma which defines the signature and the ABI for which this is a valid marshalling method. When the callback is instantiated, Callback introspects to find the marshalling method that matches the signature. If one doesn't already exist you can write one. Hopefully we'll write an ABI compiler that will automatically generate these marshalling methods according to the platform's ABI, but for now its a manual process. But at least it's open and flexible. When the callback is invoked the evaluator is performed with the current callbackContext and pointer(s) to the arguments. There is a 32-bit and a 64-bit callback context, and it can have a stack pointer, integer register args and floating point register args. So it's general enough for any callback. To pass back the result, a value is assigned into the struct via the accessor in the marshalling method and control returns to teh point where teh callback comes in, and this uses a primitive to return. Inside the callbackCOntext is a jmpbuf from a setjmp. The primitive longjmp's back to the entry point in the VM which extracts the result and the code for the kind of result and returns: Callback class>>invokeCallbackContext: vmCallbackContextAddress "<Integer>" "^<FFICallbackReturnValue>" "The low-level entry-point for callbacks sent from the VM/IA32ABI plugin. Return via primReturnFromContext:through:. thisContext's sender is the call-out context." | callbackAlien type | callbackAlien := (Smalltalk wordSize = 4 ifTrue: [VMCallbackContext32] ifFalse: [VMCallbackContext64]) atAddress: vmCallbackContextAddress. [type := Callback evaluateCallbackForContext: callbackAlien] ifCurtailed: [self error: 'attempt to non-local return across a callback']. type ifNil: [type := 1. callbackAlien wordResult: -1]. callbackAlien primReturnAs: type fromContext: thisContext On Thu, Sep 3, 2015 at 5:22 AM, Craig Latta <craig(a)netjam.org> wrote: > > Hi all-- > > I'd like to use a C shared library via FFI from Squeak or Pharo. > Specifically, I want to call a C function which takes as one of its > parameters a pointer to an array of callback function addresses. Does > one of the FFI approaches floating around handle that, and provide a > relatively pleasant mapping between Smalltalk block closures and C > callback function addresses? > > I was doing this so far in GemStone, but apparently its FFI only > supports passing callback function addresses one at a time as direct > parameters of C callouts. I suppose I could write a wrapper C library > around the one I really want to use, that provides the callback setup > interface that GemStone expects, but whenever I have to write actual C > code I start to think "Hm, why don't I just use a Smalltalk VM for which > I have the source?" :) All the fancy distributed object-database stuff > that my project also wants can wait for a bit. > > > thanks! > > -C > > -- > Craig Latta > netjam.org > +31 6 2757 7177 (SMS ok) > + 1 415 287 3547 (no SMS) > > > -- _,,,^..^,,,_ best, Eliot

Sept. 3, 2015

Re: [Pharo-dev] Need a decision on subString: vs substring:

by Gabriel Cotelli

I've second Sven here. In case anybody wants the old method put it in some ANSICompatibility package to ease porting packages from ANSI-compliant Smalltalks. On Thu, Sep 3, 2015 at 4:54 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > We went through a lot of effort/pain to move to substring, I think for > good reasons. > > > On 03 Sep 2015, at 21:31, Dimitris Chloupis <kilon.alios(a)gmail.com> > wrote: > > > > why not both ? > > Because the proper English spelling is with lowercase > > https://duckduckgo.com/?q=define%3A+substring&ia=definition > > > On Thu, Sep 3, 2015 at 9:45 PM stepharo <stepharo(a)free.fr> wrote: > > *) It appears that Pharo is removing subString: in favor of > > substring:. The ANSI standard defines subString:. > > > > I was not aware of it. In fact ANSI is bad and totally incomplete > > (for example we studies strings and this is a mess and totally > > incomplete). > > Now we should probably add it. I will send the mail to the > > mailing-list and let people decide. > > > > > > > > > > >

Sept. 3, 2015

Re: [Pharo-dev] Need a decision on subString: vs substring:

by Sven Van Caekenberghe

We went through a lot of effort/pain to move to substring, I think for good reasons. > On 03 Sep 2015, at 21:31, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > > why not both ? Because the proper English spelling is with lowercase https://duckduckgo.com/?q=define%3A+substring&ia=definition > On Thu, Sep 3, 2015 at 9:45 PM stepharo <stepharo(a)free.fr> wrote: > *) It appears that Pharo is removing subString: in favor of > substring:. The ANSI standard defines subString:. > > I was not aware of it. In fact ANSI is bad and totally incomplete > (for example we studies strings and this is a mess and totally > incomplete). > Now we should probably add it. I will send the mail to the > mailing-list and let people decide. > > > >

Sept. 3, 2015

Re: [Pharo-dev] Need a decision on subString: vs substring:

by Dimitris Chloupis

why not both ? On Thu, Sep 3, 2015 at 9:45 PM stepharo <stepharo(a)free.fr> wrote: > *) It appears that Pharo is removing subString: in favor of > substring:. The ANSI standard defines subString:. > > I was not aware of it. In fact ANSI is bad and totally incomplete > (for example we studies strings and this is a mess and totally > incomplete). > Now we should probably add it. I will send the mail to the > mailing-list and let people decide. > > > > >

Sept. 3, 2015

Need a decision on subString: vs substring:

by stepharo

*) It appears that Pharo is removing subString: in favor of substring:. The ANSI standard defines subString:. I was not aware of it. In fact ANSI is bad and totally incomplete (for example we studies strings and this is a mess and totally incomplete). Now we should probably add it. I will send the mail to the mailing-list and let people decide.

Sept. 3, 2015

Re: [Pharo-dev] Removing name from Object

by stepharo

yes but first name out :) Le 2/9/15 14:08, Peter UhnÃ¡k a Ã©crit : > > Off the top of my head, in the worst case implementing #name on the > class-side can be fatal. > > > TBH using generic names (for both variables and methods) on class side > is like running through a mine field. > I blew up my image more than once. > > From UX perspective the system should warn the user if he is trying to > override some system method or variable, but that is perhaps issue of > its own. > > Peter >

Sept. 3, 2015

Re: [Pharo-dev] Removing name from Object

by stepharo

Yes we know but first we should just make sure that the system is still working without this $#%^^&*^(&)*%^& method. Le 2/9/15 10:29, Esteban Lorenzano a Ã©crit : > but if we deprecate, that means we need to remove it from the system. > deprecated is for external users, not for Pharo it self. > > Esteban > > ps: We *can not* remove #name from the system just like that. It is > too widely use, we need to give users time to adapt. Doing otherwise > is not professional and expect a lot of people yelling (and with > reason, in this case). > >> On 02 Sep 2015, at 10:21, Guillermo Polito <guillermopolito(a)gmail.com >> <mailto:guillermopolito@gmail.com>> wrote: >> >> The problem is if (like in the past) name is extensively used by some >> library we depend upon (like... let's say morphic), a deprecation >> that raises an exception may turn the system unusable. It's not that >> it is not doable, but we should do it gently and with love. >> >> El miÃ©., 2 de sept. de 2015 a la(s) 9:30 a. m., Esteban Lorenzano >> <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> escribiÃ³: >> >>> On 02 Sep 2015, at 09:25, Peter UhnÃ¡k <i.uhnak(a)gmail.com >>> <mailto:i.uhnak@gmail.com>> wrote: >>> >>> On Wed, Sep 2, 2015 at 8:40 AM, Nicolai Hess <nicolaihess(a)web.de >>> <mailto:nicolaihess@web.de>> wrote: >>> >>> How can we find out, which external projects depend on this? >>> >>> >>> Is #name in any way special? Why not just deprecate it like any >>> other method change or removal? (And then remove it in Pharo 6) >> >> +1 >> thatâs the way to do it :) >> >>> >>> Peter >> >

Sept. 3, 2015

Re: [Pharo-dev] Removing name from Object

by stepharo

> The problem is if (like in the past) name is extensively used by some > library we depend upon (like... let's say morphic), a deprecation that > raises an exception may turn the system unusable. It's not that it is > not doable, but we should do it gently and with love. The devil is in the details... they say.

Sept. 3, 2015

Re: [Pharo-dev] size of MCbrowser should be proportional

by stepharo

ok I understand. I think that we should rebuild these tools but time time time Le 3/9/15 16:19, Peter UhnÃ¡k a Ã©crit : > On Thu, Sep 3, 2015 at 4:14 PM, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > I'm sorry but you have to think modularly. > I do not see why having multiple repositories is a problem. > > > This is not what I meant, having system modular is a good thing. > > What I was getting at is that the need to have the MCBrowser larger is > primarily (in my eyes at least) because now they are suddenly more > packages. > That's why I proposed to have them hidden from the view by default. > > That way > 1. the system can be separated into as many repos as we want > 2. the MC Browser wouldn't need to be so large > 3. it will be easier for end users to see their repos > 4. if you need to see them, you just click on a button/checkbox > > Peter >

Sept. 3, 2015

[pharo-project/pharo-core]

by GitHub

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

Sept. 3, 2015

[pharo-project/pharo-core] be04d6: 50302

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: be04d6787cc11acb9510da2fb55a0b762aae7886 https://github.com/pharo-project/pharo-core/commit/be04d6787cc11acb9510da2f… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-09-03 (Thu, 03 Sep 2015) Changed paths: M Morphic-Core.package/Morph.class/instance/layout/layoutProportionallyIn_.st A Morphic-Widgets-Pluggable.package/PluggableTextMorph.class/instance/testing/isAutoFit.st A Morphic-Widgets-Scrolling.package/ScrollPane.class/instance/layout/layoutProportionallyIn_.st A Morphic-Widgets-Scrolling.package/ScrollPane.class/instance/testing/isAutoFit.st M OpalCompiler-Core.package/IRBuilder.class/instance/instructions/pushClosureCopyCopiedValues_args_jumpTo_.st M Reflectivity-Tests.package/ReflectivityControlTest.class/instance/tests - after/testAfterAssignment.st M Reflectivity.package/RFASTTranslator.class/definition.st A Reflectivity.package/RFASTTranslator.class/instance/reflectivity/emitMetaLinkAfterNoEnsure_.st M Reflectivity.package/RFASTTranslator.class/instance/reflectivity/emitMetaLinkAfter_.st A Reflectivity.package/RFASTTranslator.class/instance/reflectivity/emitPrepareLinkAfter_.st R Reflectivity.package/RFASTTranslator.class/instance/reflectivity/hasSeen_.st R Reflectivity.package/RFASTTranslator.class/instance/reflectivity/recordSeen_.st R Reflectivity.package/RFASTTranslator.class/instance/reflectivity/removeSeen_.st M Reflectivity.package/RFASTTranslator.class/instance/reflectivity/visitVariableValue_.st M Reflectivity.package/RFASTTranslator.class/instance/visitor-double dispatching/emitMessageNode_.st M Reflectivity.package/RFASTTranslator.class/instance/visitor-double dispatching/visitArrayNode_.st M Reflectivity.package/RFASTTranslator.class/instance/visitor-double dispatching/visitAssignmentNode_.st M Reflectivity.package/RFASTTranslator.class/instance/visitor-double dispatching/visitLiteralArrayNode_.st M Reflectivity.package/RFASTTranslator.class/instance/visitor-double dispatching/visitLiteralNode_.st M Reflectivity.package/RFASTTranslator.class/instance/visitor-double dispatching/visitMethodNode_.st R Reflectivity.package/RFASTTranslator.class/instance/visitor-double dispatching/visitNode_.st M Reflectivity.package/RFASTTranslator.class/instance/visitor-double dispatching/visitVariableNode_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50301.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50302.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50301.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50302.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50302 16452 Improve Morph>>layoutProportionallyIn: https://pharo.fogbugz.com/f/cases/16452 16471 Pass over #after: make after work for assignment https://pharo.fogbugz.com/f/cases/16471 http://files.pharo.org/image/50/50302.zip

Sept. 3, 2015

Re: [Pharo-dev] size of MCbrowser should be proportional

by Peter UhnÃ¡k

On Thu, Sep 3, 2015 at 4:14 PM, stepharo <stepharo(a)free.fr> wrote: > I'm sorry but you have to think modularly. > I do not see why having multiple repositories is a problem. > > This is not what I meant, having system modular is a good thing. What I was getting at is that the need to have the MCBrowser larger is primarily (in my eyes at least) because now they are suddenly more packages. That's why I proposed to have them hidden from the view by default. That way 1. the system can be separated into as many repos as we want 2. the MC Browser wouldn't need to be so large 3. it will be easier for end users to see their repos 4. if you need to see them, you just click on a button/checkbox Peter

Sept. 3, 2015

Re: [Pharo-dev] size of MCbrowser should be proportional

by stepharo

I'm sorry but you have to think modularly. I do not see why having multiple repositories is a problem. Stef Le 3/9/15 11:22, Peter UhnÃ¡k a Ã©crit : > > The new, large size, makes it a very scary tool. That many > packages? That many repositories? > > > Pharo 4 image has just 2 external repos (Pharo + PharoInbox), > Pharo 5 has 19 fucking repositories. > > I don't want to generalize, but how often does an end user care about > any of them? > For example the only time I interact with Pharo or PharoInbox is when > I am fixing issues and I do that from clean image. > > So my proposal: > Why not hide them? There could be a checkbox "[ ] Show system > repositories" (default unchecked). > That way the window can be much much smaller and users will see what > is important for them. > > Peter

Sept. 3, 2015

Re: [Pharo-dev] size of MCbrowser should be proportional

by stepharo

> >> >> >> and for "size of MCbrowser should be proportional": >> >> We don't have any other windows with a size proportional to the >> display size. >> Why should only MCBrowser behave like that? (Nautilus uses the same >> size). >> >> And what would be a good size, max. half the screen? >> >> And if we want a display screen dependent window size, this should be >> done by >> RealEstateAgent, and not for every single tool. > > I really donât know if it should be proportional. I has never been > like that. What I do know is that now is too big (while before was to > small) :) > So maybe best is to play a bit with the sizesâ¦ it was small, now is > big, lets find something in the middle :) > + 1

Sept. 3, 2015

Re: [Pharo-dev] [Reflectivity] Slides ESUG talk

by roberto.minelli＠usi.ch

Very good talk Marcus. In the next weeks I will finally have some time to try Reflectivity out! Thanks a lot for all your effort! Cheers, Roberto > On 31 Jul 2015, at 13:23, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > >> On 15 Jul 2015, at 10:15, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> Hi, >> >> the slides for my ESUG talk are online: >> >> http://www.slideshare.net/MarcusDenker/reflection-in-pharo5 >> >> > > Video is online, too: > > https://www.youtube.com/watch?v=Ik539CtjtTI > > > > Marcus >

Sept. 3, 2015

Re: [Pharo-dev] Image-specific "cache"

by Martin Dias

There is also SnapshotDone, announced in SystemAnnouncer. Martin On Thu, Sep 3, 2015 at 1:32 PM, Max Leske <maxleske(a)gmail.com> wrote: > You could also use the session checking logic NativeBoost uses. Take a > look at NativeBoost>>sessionChanged et al. > > Cheers, > Max > > On 03 Sep 2015, at 12:33, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > Sorry, my last email is UNREADABLE! > > Here is the spellchecked version: > > Hi, > > I want to persist some value (in a singleton), but when a user creates a > copy of the image, I want to regenerate that data, so there will be no two > images with the same persisted data. Is there some way to act on an image > launch? Or maybe you have better suggestionsâ¦ > > Cheers, > Uko > > > On 03 Sep 2015, at 12:25, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > Hi, > > I want to persist some value (in a singleton), but when a user creates a > copy of the image, it want to regenerate that data, so the will be no who > images with the same persisted data. Is there some way to act on image > launch? Or maybe you have more suggestionsâ¦ > > Cheers, > Uko > > > >

Sept. 3, 2015

Re: [Pharo-dev] Looking for a way to build SQL query

by olivier auverlot

Hi Stef, I have not knowledge about a framework to build SQL queries from Pharo syntax. However, Garage provides a solution to build easily SQL query with arguments. Take a look at https://guillep.github.io/DBXTalk/garage/prepared_statements.html Olivier :-) 2015-09-03 11:45 GMT+02:00 Peter UhnÃ¡k <i.uhnak(a)gmail.com>: > Maybe Querier? > It was presented on ESUG, but I don't know how production ready it is, you > would have to ask Michal. > > http://querier.xmb.cz/ > https://www.youtube.com/watch?v=c2yhd8BjFjU > > Peter > > On Thu, Sep 3, 2015 at 11:32 AM, stepharo <stepharo(a)free.fr> wrote: > >> Hi guys >> >> I'm looking for a lib that I can use to build sql queries instead of >> manipulating strings. >> ROE? >> >> Stef >> >> >

Sept. 3, 2015

Re: [Pharo-dev] Image-specific "cache"

by Max Leske

You could also use the session checking logic NativeBoost uses. Take a look at NativeBoost>>sessionChanged et al. Cheers, Max > On 03 Sep 2015, at 12:33, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > Sorry, my last email is UNREADABLE! > > Here is the spellchecked version: > > Hi, > > I want to persist some value (in a singleton), but when a user creates a copy of the image, I want to regenerate that data, so there will be no two images with the same persisted data. Is there some way to act on an image launch? Or maybe you have better suggestionsâ¦ > > Cheers, > Uko > > >> On 03 Sep 2015, at 12:25, Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>> wrote: >> >> Hi, >> >> I want to persist some value (in a singleton), but when a user creates a copy of the image, it want to regenerate that data, so the will be no who images with the same persisted data. Is there some way to act on image launch? Or maybe you have more suggestionsâ¦ >> >> Cheers, >> Uko >

Sept. 3, 2015

Re: [Pharo-dev] Image-specific "cache"

by Stephan Eggermont

On 03-09-15 12:33, Yuriy Tymchuk wrote: > I want to persist some value (in a singleton), but when a user creates a copy of the image, I want to regenerate that data, so there will be no two images with the same persisted data. Is there some way to act on an image launch? Or maybe you have better suggestionsâ¦ You could use SHA1 hashMessage: FileSystem workingDirectory fullName to see if you are in the same image, and you could add a class to the startuplist like GTPlayBook does Stephan

Sept. 3, 2015

Re: [Pharo-dev] Image-specific "cache"

by Craig Latta

Hoi Uko-- > I want to persist some value (in a singleton), but when a user > creates a copy of the image, I want to regenerate that data, so there > will be no two images with the same persisted data. Is there some way > to act on an image launch? Sure, you can tie into the StartUpList and ShutDownList in SmalltalkImage. This is how the delay scheduler is restarted on system startup, for example. > Or maybe you have better suggestions... This seems like the conventional way of doing things like that, as long the system doesn't need the assistance of another running system to compute the data. cheers, -C -- Craig Latta netjam.org +31 6 2757 7177 (SMS ok) + 1 415 287 3547 (no SMS)

Sept. 3, 2015

Re: [Pharo-dev] size of MCbrowser should be proportional

by Stephan Eggermont

On 03-09-15 11:22, Peter UhnÃ¡k wrote: >> >> The new, large size, makes it a very scary tool. That many packages? That >> many repositories? >> > > Pharo 4 image has just 2 external repos (Pharo + PharoInbox), > Pharo 5 has 19 fucking repositories. > So my proposal: > Why not hide them? There could be a checkbox "[ ] Show system repositories" > (default unchecked). > That way the window can be much much smaller and users will see what is > important for them. Currently we have a dropdown switching between Package and All, with Package the default. We could add a third one System, and when no package is selected default to only showing the package cache. Stephan

Sept. 3, 2015

Re: [Pharo-dev] Image-specific "cache"

by Yuriy Tymchuk

Sorry, my last email is UNREADABLE! Here is the spellchecked version: Hi, I want to persist some value (in a singleton), but when a user creates a copy of the image, I want to regenerate that data, so there will be no two images with the same persisted data. Is there some way to act on an image launch? Or maybe you have better suggestionsâ¦ Cheers, Uko > On 03 Sep 2015, at 12:25, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > Hi, > > I want to persist some value (in a singleton), but when a user creates a copy of the image, it want to regenerate that data, so the will be no who images with the same persisted data. Is there some way to act on image launch? Or maybe you have more suggestionsâ¦ > > Cheers, > Uko

Sept. 3, 2015

Image-specific "cache"

by Yuriy Tymchuk

Hi, I want to persist some value (in a singleton), but when a user creates a copy of the image, it want to regenerate that data, so the will be no who images with the same persisted data. Is there some way to act on image launch? Or maybe you have more suggestionsâ¦ Cheers, Uko

Sept. 3, 2015

Re: [Pharo-dev] Looking for a way to build SQL query

by Peter UhnÃ¡k

Maybe Querier? It was presented on ESUG, but I don't know how production ready it is, you would have to ask Michal. http://querier.xmb.cz/ https://www.youtube.com/watch?v=c2yhd8BjFjU Peter On Thu, Sep 3, 2015 at 11:32 AM, stepharo <stepharo(a)free.fr> wrote: > Hi guys > > I'm looking for a lib that I can use to build sql queries instead of > manipulating strings. > ROE? > > Stef > >

Sept. 3, 2015

Re: [Pharo-dev] block brace alignment (Re: feedback from J Brant)

by Peter UhnÃ¡k

> > self xxx > ifTrue: [ self bla. > self foo I don't like this very much because equivalent messages are formatted differently (they are not aligned). Now when you introduce block parameters, which everybody so far (Kent's book included) has ignored, it suddenly makes more sense to leave the first row empty. self xxx ifTrue: [ :param | self nicely. self aligned. ] Also the examples in the book seem to be picked to fit the rectangle criteria: ifTrue: [ [self clearCaches. self recomputeAngle] ifTrue: [ [self at: each put: 0] they both fit into a rectangle with a reason quite nicely. But if I pick [:each | aShape sendCommandAt: each; to: self] or a block which is very top heavy (long methods at top, short at bottom) I can hardly consider the bottom bracket as corner of a rectangle. But why not add a new option to the formatter to fit your criteria? (Btw I would love to have what IDEs often have -- code preview next to it to which all the options are being applied as you select it.) Peter On Thu, Sep 3, 2015 at 11:01 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > I also code in the same way as Svenâs example. For more advanced things, > why not to have: > > self xxx > ifTrue: > [ self bla. > self foo > > or > > self xxx > ifTrue: [ self bla. > self foo > > this are the interesting things to me. I guess I should read Kent Beck's > formatting rules :) but one more thing that I like to have is > > anObject > a: param1; > cascading: param2; > message: param3; > formatted: param4 > > Although there are some issues around it. > > Uko > > On 03 Sep 2015, at 07:29, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > And what happened to the plain normal (in my mind/experience) ? > > self xxx > ifTrue: [ > self bla. > self foo ]. > > I would say that is the most common one I've seen in the image. And it is > how the old formatter worked. > > On 03 Sep 2015, at 03:39, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > Hi Ben, > > have you read Kent Beck's formatting rules? I wish we would adhere to > these in our formatters. And I wish he would put the formatting rules in > the public domain on the web (Kent?). He actually justifies the rules he > chooses; they're not just personal preferences. And IMO they produce > eleant, readable Smalltalk. I have to say your block formatting below is > horrible. Blocks are blocks. [ & ] are /not/ the same as { & } in C. > [...] define an *object*, not merely delimit syntax. As such any good > Smalltalk format will emphasize the objectness of blocks. And IMNERHO that > is to make them rectangles as in > > self ifIWantedYouToWriteC ifTrue: > [self useABloodyCCompiler. > self useCCMinusPToMakeSenseOfTheDamageDoneByTheCPreProcessor] > > > On Wed, Sep 2, 2015 at 6:23 PM, Ben Coman <btc(a)openinworld.com> wrote: > On Thu, Sep 3, 2015 at 2:28 AM, stepharo <stepharo(a)free.fr> wrote: > > > I do not really like all the formattings of kent. Because sometimes it just > does not work. > But this is why we ask franck (an interns to start to have a look). > > For example I do not like > > self xxx > ifTrue: > [ > self bla > self foo. > > > Agreed. Unneccessary waste of a line. > > in the current default formatter. > and I prefer > > self xxx > ifTrue: [ self bla. > self foo > But here the problem is that the self foo is not tab aligned because > ifTrue: [ > > self xxx > ifTrue: > [ self bla. > self foo > So may be this one is a nice compromise > > > Not quite there. The "self bla" is still not actually vertically aligned. > > I think that we should change some settings. In fact in alpha things are > there to evolve until the release :) > > > I like... > self xxx > ifTrue: > [ self bla. > self foo. > ]. > > for three reasons: > * the first statement of the block is vertically aligned with the rest > * vertical alignment of paired brackets makes visual matching *simple* > * the vertical whitespace enforced by the closing bracket on its > own visually groups blocks. > > Now some people don't like the closing brace on its own because they > prefer code density. So maybe this... > > self xxx > ifTrue: > [ self bla. > self foo. ] > ifFalse: > [ self baa. > self moo. ]. > > But still I prefer... > > self xxx > ifTrue: > [ self bla. > self foo. > ] > ifFalse: > [ self baa. > self moo. > ]. > > cheers -ben > > > > > -- > _,,,^..^,,,_ > best, Eliot > > > > >

Sept. 3, 2015

Looking for a way to build SQL query

by stepharo

Hi guys I'm looking for a lib that I can use to build sql queries instead of manipulating strings. ROE? Stef

Sept. 3, 2015

Re: [Pharo-dev] Removing name from Object

by Sven Van Caekenberghe

I am reviving the following (old) case: https://pharo.fogbugz.com/f/cases/7241/Object-name-should-best-be-removed I will add some more comments there. Sven > On 02 Sep 2015, at 13:53, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > EstebanLM wrote >> deprecate it like any other method change or removal? (And then remove it >> in Pharo 6) >> >> +1 >> thatâs the way to do it :) > > +1. I'm glad we're finally getting around to this :) > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Removing-name-from-Object-tp4847514p4847641.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Sept. 3, 2015

Re: [Pharo-dev] size of MCbrowser should be proportional

by Peter UhnÃ¡k

> > The new, large size, makes it a very scary tool. That many packages? That > many repositories? > Pharo 4 image has just 2 external repos (Pharo + PharoInbox), Pharo 5 has 19 fucking repositories. I don't want to generalize, but how often does an end user care about any of them? For example the only time I interact with Pharo or PharoInbox is when I am fixing issues and I do that from clean image. So my proposal: Why not hide them? There could be a checkbox "[ ] Show system repositories" (default unchecked). That way the window can be much much smaller and users will see what is important for them. Peter

Sept. 3, 2015

Re: [Pharo-dev] block brace alignment (Re: feedback from J Brant)

by Yuriy Tymchuk

I also code in the same way as Svenâs example. For more advanced things, why not to have: self xxx ifTrue: [ self bla. self foo or self xxx ifTrue: [ self bla. self foo this are the interesting things to me. I guess I should read Kent Beck's formatting rules :) but one more thing that I like to have is anObject a: param1; cascading: param2; message: param3; formatted: param4 Although there are some issues around it. Uko > On 03 Sep 2015, at 07:29, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > And what happened to the plain normal (in my mind/experience) ? > > self xxx > ifTrue: [ > self bla. > self foo ]. > > I would say that is the most common one I've seen in the image. And it is how the old formatter worked. > >> On 03 Sep 2015, at 03:39, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >> >> Hi Ben, >> >> have you read Kent Beck's formatting rules? I wish we would adhere to these in our formatters. And I wish he would put the formatting rules in the public domain on the web (Kent?). He actually justifies the rules he chooses; they're not just personal preferences. And IMO they produce eleant, readable Smalltalk. I have to say your block formatting below is horrible. Blocks are blocks. [ & ] are /not/ the same as { & } in C. [...] define an *object*, not merely delimit syntax. As such any good Smalltalk format will emphasize the objectness of blocks. And IMNERHO that is to make them rectangles as in >> >> self ifIWantedYouToWriteC ifTrue: >> [self useABloodyCCompiler. >> self useCCMinusPToMakeSenseOfTheDamageDoneByTheCPreProcessor] >> >> >> On Wed, Sep 2, 2015 at 6:23 PM, Ben Coman <btc(a)openinworld.com> wrote: >> On Thu, Sep 3, 2015 at 2:28 AM, stepharo <stepharo(a)free.fr> wrote: >>> >>> I do not really like all the formattings of kent. Because sometimes it just >>> does not work. >>> But this is why we ask franck (an interns to start to have a look). >>> >>> For example I do not like >>> >>> self xxx >>> ifTrue: >>> [ >>> self bla >>> self foo. >> >> Agreed. Unneccessary waste of a line. >> >>> in the current default formatter. >>> and I prefer >>> >>> self xxx >>> ifTrue: [ self bla. >>> self foo >>> But here the problem is that the self foo is not tab aligned because >>> ifTrue: [ >>> >>> self xxx >>> ifTrue: >>> [ self bla. >>> self foo >>> So may be this one is a nice compromise >> >> Not quite there. The "self bla" is still not actually vertically aligned. >> >>> I think that we should change some settings. In fact in alpha things are >>> there to evolve until the release :) >> >> I like... >> self xxx >> ifTrue: >> [ self bla. >> self foo. >> ]. >> >> for three reasons: >> * the first statement of the block is vertically aligned with the rest >> * vertical alignment of paired brackets makes visual matching *simple* >> * the vertical whitespace enforced by the closing bracket on its >> own visually groups blocks. >> >> Now some people don't like the closing brace on its own because they >> prefer code density. So maybe this... >> >> self xxx >> ifTrue: >> [ self bla. >> self foo. ] >> ifFalse: >> [ self baa. >> self moo. ]. >> >> But still I prefer... >> >> self xxx >> ifTrue: >> [ self bla. >> self foo. >> ] >> ifFalse: >> [ self baa. >> self moo. >> ]. >> >> cheers -ben >> >> >> >> >> -- >> _,,,^..^,,,_ >> best, Eliot > >

Sept. 3, 2015

Re: [Pharo-dev] size of MCbrowser should be proportional

by Thierry Goubier

2015-09-03 10:29 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > > On 03 Sep 2015, at 10:03, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > > 2015-09-03 7:56 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > >> +1 >> >> I also submitted an issue about MCBrowser not taking into account the >> size of the world window (and then appearing with part of it hidden out of >> the visible area) >> > > > That one is fixed: > 16401 > <https://pharo.fogbugz.com/f/cases/16401/opening-monticello-window-does-not-…> > opening monticello window does not respect world size > > > hehâ¦ I missed that one :) > > > > and for "size of MCbrowser should be proportional": > > We don't have any other windows with a size proportional to the display > size. > Why should only MCBrowser behave like that? (Nautilus uses the same size). > > And what would be a good size, max. half the screen? > > And if we want a display screen dependent window size, this should be done > by > RealEstateAgent, and not for every single tool. > > > I really donât know if it should be proportional. I has never been like > that. What I do know is that now is too big (while before was to small) :) > So maybe best is to play a bit with the sizesâ¦ it was small, now is big, > lets find something in the middle :) > The previous size, small, made it not too scary. The new, large size, makes it a very scary tool. That many packages? That many repositories? Ok, that was there before, but in XXL size, it becomes a bit too obvious there is a lot in there. Thierry > > Esteban > > > > > > >> > On 02 Sep 2015, at 10:07, stepharo <stepharo(a)free.fr> wrote: >> > >> > Hi guys >> > >> > now when I open MCBrowser it gets 80% of my window. >> > So this is good to make it larger but it should be proportional to the >> actual size. >> > >> > >> https://pharo.fogbugz.com/f/cases/16451/MCBrowser-default-size-should-propo… >> > Could the person that originally changed it fix it? >> > >> > Stef >> > >> >> >> > >

Sept. 3, 2015

Re: [Pharo-dev] size of MCbrowser should be proportional

by Esteban Lorenzano

> On 03 Sep 2015, at 10:03, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > > 2015-09-03 7:56 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: > +1 > > I also submitted an issue about MCBrowser not taking into account the size of the world window (and then appearing with part of it hidden out of the visible area) > > > That one is fixed: > 16401 <https://pharo.fogbugz.com/f/cases/16401/opening-monticello-window-does-not-…> opening monticello window does not respect world size hehâ¦ I missed that one :) > > > and for "size of MCbrowser should be proportional": > > We don't have any other windows with a size proportional to the display size. > Why should only MCBrowser behave like that? (Nautilus uses the same size). > > And what would be a good size, max. half the screen? > > And if we want a display screen dependent window size, this should be done by > RealEstateAgent, and not for every single tool. I really donât know if it should be proportional. I has never been like that. What I do know is that now is too big (while before was to small) :) So maybe best is to play a bit with the sizesâ¦ it was small, now is big, lets find something in the middle :) Esteban > > > > > > > On 02 Sep 2015, at 10:07, stepharo <stepharo(a)free.fr <mailto:stepharo@free.fr>> wrote: > > > > Hi guys > > > > now when I open MCBrowser it gets 80% of my window. > > So this is good to make it larger but it should be proportional to the actual size. > > > > https://pharo.fogbugz.com/f/cases/16451/MCBrowser-default-size-should-propo… <https://pharo.fogbugz.com/f/cases/16451/MCBrowser-default-size-should-propo…> > > Could the person that originally changed it fix it? > > > > Stef > > > > >

Sept. 3, 2015

Re: [Pharo-dev] size of MCbrowser should be proportional

by Nicolai Hess

2015-09-03 7:56 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > +1 > > I also submitted an issue about MCBrowser not taking into account the size > of the world window (and then appearing with part of it hidden out of the > visible area) > That one is fixed: 16401 <https://pharo.fogbugz.com/f/cases/16401/opening-monticello-window-does-not-…> opening monticello window does not respect world size and for "size of MCbrowser should be proportional": We don't have any other windows with a size proportional to the display size. Why should only MCBrowser behave like that? (Nautilus uses the same size). And what would be a good size, max. half the screen? And if we want a display screen dependent window size, this should be done by RealEstateAgent, and not for every single tool. > > On 02 Sep 2015, at 10:07, stepharo <stepharo(a)free.fr> wrote: > > > > Hi guys > > > > now when I open MCBrowser it gets 80% of my window. > > So this is good to make it larger but it should be proportional to the > actual size. > > > > > https://pharo.fogbugz.com/f/cases/16451/MCBrowser-default-size-should-propo… > > Could the person that originally changed it fix it? > > > > Stef > > > > >

Sept. 3, 2015

Re: [Pharo-dev] Garage-OpenDBX does not load on Pharo 50 because it uses Timestamp

by Ben Coman

On Thu, Sep 3, 2015 at 1:33 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> On 03 Sep 2015, at 06:01, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >> >> On 9/2/15, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> But Timestamp was already removed completely from 4.0, why re-add it, even >>> deprecated ? >> >> Because it will be added in a compatibility layer package which is >> only loaded by packages which need it. There might be other things in >> the Pharo 5/4 compatibility package. > > But still, if external packages do load that code, they will never have to change, and the class will remain in the image forever. > > It is like when you load certain Squeak packages that are 'ported' with compatibility layers to Pharo: they just add again all the methods that we tried to clean up. Unfortunately this is a pragmatic engineering approach to porting. I haven't done a lot of this in practice, but I expect much of the effort in replacing deprecated methods in applications is ensuring that the replacement *really* is functionally equivalent. So the quickest route is reintegrating those methods. The downside is that: * When reading existing code, use of deprecated method is not obvious. * Deprecated methods can be accidently reused for new code. So just brainstorming... perhaps these downsides can be addressed by a deprecation-compatability package that makes use of it more explicit by prepending each deprecated method with "deprecatedNN", e.g... SomeClass>>xyz self deprecated: 'Blahblah' on: 'April 2015' in: #Pharo4.0. self deprecated40xyz. SomeClass>>deprecated40xyz "original code or call to replacement code..." So this splits porting into a few steps. 1. Loading the deprecation-compatability package gives *functional-equivalence* with Deprecation Warnings turned off. 2. Gradually (manually or with rewrite tool) replacing #xyz calls with #deprecated40xyz calls, results in *functionally-equivalent* but *ugly* and obvious code. 3. Gradually migrate #deprecated40xyz calls to whatever the final replacement is. 4. Easy to search for remaining users of #deprecated40 and when none are left (btw, is there a deprecation-compatability package/repository somewhere? I couldn't see one on Smalltalkhub) cheers -ben >> --HH >> >>> I am sure many external packages are already modified, I know I did it for >>> mine. >> >>>> On 02 Sep 2015, at 13:19, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>>> >>>> >>>>> On 02 Sep 2015, at 12:32, stepharo <stepharo(a)free.fr> wrote: >>>>> >>>>> Hi guille >>>>> >>>>> there is not stress. I just wanted to let you know. >>>>> I was wondering if just subclassing DateAndTime would not be enough for >>>>> now. >>>> >>>> Yes, as far as I remember Timestamp was just an empy subclass. >>>> >>>> We could: >>>> >>>> -> add it back to Deprecated50 or maybe even to a âCompatibilityâ package >>>> -> Write a Quality Check rule. >>>> >>>>> I will go back to code with Pharo 40 >>>>> >>>>> stef >>>>> >>>>> Le 2/9/15 10:30, Guillermo Polito a Ã©crit : >>>>>> If somebody can check it and fix it it would be good :). I've just >>>>>> started my new job and my evenings are busy looking for an apartment or >>>>>> staying in a hostel without a proper internet connection... >>>>>> >>>>>> If not, I think we can wait a bit. The first step should be enabling CI >>>>>> jobs for pharo5. Also, I do not think the intersection between 'people >>>>>> using garage opendbx' and 'people using pharo5' is that big to justify a >>>>>> rush. >>>>>> >>>>>> Guille >>>>>> >>>>>> El miÃ©., 2 de sept. de 2015 a la(s) 10:12 a. m., stepharo >>>>>> <stepharo(a)free.fr> escribiÃ³: >>>>>> for your info... >>>>>> >>>>>> Garage-OpenDBX does not load on Pharo 50 because it uses Timestamp >>>>>> >>>>>> Stef >>>>>> >>>>> >>>> >>> >>> >>> >> > >

Sept. 3, 2015

Re: [Pharo-dev] block brace alignment (Re: feedback from J Brant)

by Peter UhnÃ¡k

> > I like... > self xxx > ifTrue: > [ self bla. > self foo. > ]. Check the settings. It's called "align brackets" I think. He actually justifies the rules he chooses; they're not just personal > preferences. This is thin ice. The justifications can still be based on personal preferences. Imagine tabs vs spaces flame wars, where both side do have valid arguments and you pick side based on what is more important to you. Now with the new Rubric and BlueInk you can automatically have methods formatted for you, so it doesn't matter as much what other people use. But generally agreement is a good thing. And what happened to the plain normal (in my mind/experience) ? > self xxx > ifTrue: [ > self bla. > self foo ]. I'm pretty sure this is a bug; I've reported it few days ago. https://pharo.fogbugz.com/f/cases/edit/16422/BlueInk-Formatter-breaks-line-… And there is settings for that also. Peter On Thu, Sep 3, 2015 at 7:29 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > And what happened to the plain normal (in my mind/experience) ? > > self xxx > ifTrue: [ > self bla. > self foo ]. > > I would say that is the most common one I've seen in the image. And it is > how the old formatter worked. > > > On 03 Sep 2015, at 03:39, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > > > Hi Ben, > > > > have you read Kent Beck's formatting rules? I wish we would adhere > to these in our formatters. And I wish he would put the formatting rules > in the public domain on the web (Kent?). He actually justifies the rules > he chooses; they're not just personal preferences. And IMO they produce > eleant, readable Smalltalk. I have to say your block formatting below is > horrible. Blocks are blocks. [ & ] are /not/ the same as { & } in C. > [...] define an *object*, not merely delimit syntax. As such any good > Smalltalk format will emphasize the objectness of blocks. And IMNERHO that > is to make them rectangles as in > > > > self ifIWantedYouToWriteC ifTrue: > > [self useABloodyCCompiler. > > self useCCMinusPToMakeSenseOfTheDamageDoneByTheCPreProcessor] > > > > > > On Wed, Sep 2, 2015 at 6:23 PM, Ben Coman <btc(a)openinworld.com> wrote: > > On Thu, Sep 3, 2015 at 2:28 AM, stepharo <stepharo(a)free.fr> wrote: > > > > > > I do not really like all the formattings of kent. Because sometimes it > just > > > does not work. > > > But this is why we ask franck (an interns to start to have a look). > > > > > > For example I do not like > > > > > > self xxx > > > ifTrue: > > > [ > > > self bla > > > self foo. > > > > Agreed. Unneccessary waste of a line. > > > > > in the current default formatter. > > > and I prefer > > > > > > self xxx > > > ifTrue: [ self bla. > > > self foo > > > But here the problem is that the self foo is not tab aligned > because > > > ifTrue: [ > > > > > > self xxx > > > ifTrue: > > > [ self bla. > > > self foo > > > So may be this one is a nice compromise > > > > Not quite there. The "self bla" is still not actually vertically aligned. > > > > > I think that we should change some settings. In fact in alpha things > are > > > there to evolve until the release :) > > > > I like... > > self xxx > > ifTrue: > > [ self bla. > > self foo. > > ]. > > > > for three reasons: > > * the first statement of the block is vertically aligned with the > rest > > * vertical alignment of paired brackets makes visual matching > *simple* > > * the vertical whitespace enforced by the closing bracket on its > > own visually groups blocks. > > > > Now some people don't like the closing brace on its own because they > > prefer code density. So maybe this... > > > > self xxx > > ifTrue: > > [ self bla. > > self foo. ] > > ifFalse: > > [ self baa. > > self moo. ]. > > > > But still I prefer... > > > > self xxx > > ifTrue: > > [ self bla. > > self foo. > > ] > > ifFalse: > > [ self baa. > > self moo. > > ]. > > > > cheers -ben > > > > > > > > > > -- > > _,,,^..^,,,_ > > best, Eliot > > >

Sept. 3, 2015

[pharo-project/pharo-core]

by GitHub

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

Sept. 3, 2015

[pharo-project/pharo-core] 04ba21: 50301

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 04ba21efe60fcec9543080ea3ef277e53071be12 https://github.com/pharo-project/pharo-core/commit/04ba21efe60fcec9543080ea… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-09-03 (Thu, 03 Sep 2015) Changed paths: A Compression-Tests.package/ZipArchiveTest.class/README.md A Compression-Tests.package/ZipArchiveTest.class/definition.st A Compression-Tests.package/ZipArchiveTest.class/instance/tests/setUp.st A Compression-Tests.package/ZipArchiveTest.class/instance/tests/tearDown.st A Compression-Tests.package/ZipArchiveTest.class/instance/tests/testAddNonExistentFile.st A Compression-Tests.package/ZipArchiveTest.class/instance/tests/testCreateWithRelativeNames.st A Compression-Tests.package/ZipArchiveTest.class/instance/tests/testDate29Feb2000.st A Compression-Tests.package/ZipArchiveTest.class/instance/tests/testFilePermissions.st A Compression-Tests.package/ZipArchiveTest.class/instance/tests/testParseSqueakZipTimestamp.st A Compression-Tests.package/ZipArchiveTest.class/instance/tests/testSetLastModification.st A Compression-Tests.package/ZipArchiveTest.class/instance/tests/testZip.st A Compression-Tests.package/ZipCrcTests.class/README.md A Compression-Tests.package/ZipCrcTests.class/definition.st A Compression-Tests.package/ZipCrcTests.class/instance/tests/testInvalidGZipCrc.st A Compression-Tests.package/ZipCrcTests.class/instance/tests/testInvalidZLibCrc.st A Compression-Tests.package/ZipCrcTests.class/instance/tests/testInvalidZipCrc.st A Compression-Tests.package/ZipCrcTests.class/instance/tests/testMissingGZipCrc.st A Compression-Tests.package/ZipCrcTests.class/instance/tests/testMissingZLibCrc.st A Compression-Tests.package/ZipCrcTests.class/instance/tests/testMissingZipCrc.st A Compression-Tests.package/ZipCrcTests.class/instance/tests/testValidGZipCrc.st A Compression-Tests.package/ZipCrcTests.class/instance/tests/testValidZLibCrc.st A Compression-Tests.package/ZipCrcTests.class/instance/tests/testValidZipCrc.st A Compression-Tests.package/ZipWriteStreamTests.class/README.md A Compression-Tests.package/ZipWriteStreamTests.class/definition.st A Compression-Tests.package/ZipWriteStreamTests.class/instance/tests/testEmptyStrings.st R CompressionTests.package/ZipArchiveTest.class/README.md R CompressionTests.package/ZipArchiveTest.class/definition.st R CompressionTests.package/ZipArchiveTest.class/instance/tests/setUp.st R CompressionTests.package/ZipArchiveTest.class/instance/tests/tearDown.st R CompressionTests.package/ZipArchiveTest.class/instance/tests/testAddNonExistentFile.st R CompressionTests.package/ZipArchiveTest.class/instance/tests/testCreateWithRelativeNames.st R CompressionTests.package/ZipArchiveTest.class/instance/tests/testDate29Feb2000.st R CompressionTests.package/ZipArchiveTest.class/instance/tests/testFilePermissions.st R CompressionTests.package/ZipArchiveTest.class/instance/tests/testParseSqueakZipTimestamp.st R CompressionTests.package/ZipArchiveTest.class/instance/tests/testSetLastModification.st R CompressionTests.package/ZipArchiveTest.class/instance/tests/testZip.st R CompressionTests.package/ZipCrcTests.class/README.md R CompressionTests.package/ZipCrcTests.class/definition.st R CompressionTests.package/ZipCrcTests.class/instance/tests/testInvalidGZipCrc.st R CompressionTests.package/ZipCrcTests.class/instance/tests/testInvalidZLibCrc.st R CompressionTests.package/ZipCrcTests.class/instance/tests/testInvalidZipCrc.st R CompressionTests.package/ZipCrcTests.class/instance/tests/testMissingGZipCrc.st R CompressionTests.package/ZipCrcTests.class/instance/tests/testMissingZLibCrc.st R CompressionTests.package/ZipCrcTests.class/instance/tests/testMissingZipCrc.st R CompressionTests.package/ZipCrcTests.class/instance/tests/testValidGZipCrc.st R CompressionTests.package/ZipCrcTests.class/instance/tests/testValidZLibCrc.st R CompressionTests.package/ZipCrcTests.class/instance/tests/testValidZipCrc.st R CompressionTests.package/ZipWriteStreamTests.class/README.md R CompressionTests.package/ZipWriteStreamTests.class/definition.st R CompressionTests.package/ZipWriteStreamTests.class/instance/tests/testEmptyStrings.st A FreeType-Tests.package/FreeTypeCacheTest.class/README.md A FreeType-Tests.package/FreeTypeCacheTest.class/definition.st A FreeType-Tests.package/FreeTypeCacheTest.class/instance/private/validateCollections_.st A FreeType-Tests.package/FreeTypeCacheTest.class/instance/private/validateSizes_.st A FreeType-Tests.package/FreeTypeCacheTest.class/instance/running/setUp.st A FreeType-Tests.package/FreeTypeCacheTest.class/instance/tests/testConstants.st A FreeType-Tests.package/FreeTypeCacheTest.class/instance/tests/testEntriesRemovedFIFO.st A FreeType-Tests.package/FreeTypeCacheTest.class/instance/tests/testFailedGet.st A FreeType-Tests.package/FreeTypeCacheTest.class/instance/tests/testFreeTypeCacheEntry.st A FreeType-Tests.package/FreeTypeCacheTest.class/instance/tests/testInstanceInitialization.st A FreeType-Tests.package/FreeTypeCacheTest.class/instance/tests/testMaximumSizeRespectedOnIfAbsentPut.st A FreeType-Tests.package/FreeTypeCacheTest.class/instance/tests/testMaximumSizeRespectedOnPut.st A FreeType-Tests.package/FreeTypeCacheTest.class/instance/tests/testNormalGetIfAbsentPut.st A FreeType-Tests.package/FreeTypeCacheTest.class/instance/tests/testNormalGetIfAbsentPutTwice.st A FreeType-Tests.package/FreeTypeCacheTest.class/instance/tests/testNormalGetIfAbsentPutTwiceIntoNonEmptyCache.st A FreeType-Tests.package/FreeTypeCacheTest.class/instance/tests/testNormalPutGet.st A FreeType-Tests.package/FreeTypeCacheTest.class/instance/tests/testNormalPutGetTwice.st A FreeType-Tests.package/FreeTypeCacheTest.class/instance/tests/testNormalPutGetWidth.st A FreeType-Tests.package/FreeTypeCacheTest.class/instance/tests/testPutSameElementTwice.st A FreeType-Tests.package/FreeTypeCacheTest.class/instance/tests/testRemoveAll.st A FreeType-Tests.package/FreeTypeCacheTest.class/instance/tests/testRemoveAllForFont.st A FreeType-Tests.package/FreeTypeCacheTest.class/instance/tests/testRemoveAllForType.st A FreeType-Tests.package/FreeTypeCacheTest.class/instance/tests/testReport.st A FreeType-Tests.package/FreeTypeCacheTest.class/instance/tests/testSetMaximumSize.st A FreeType-Tests.package/FreeTypeCacheTest.class/instance/tests/testSetMaximumSizeGrow.st A FreeType-Tests.package/FreeTypeCacheTest.class/instance/tests/testSetMaximumSizeShrink.st A FreeType-Tests.package/FreeTypeCacheTest.class/instance/tests/testSetMaximumSizeUnbounded.st A FreeType-Tests.package/FreeTypeCacheTest.class/instance/tests/testSingleton.st R FreeTypeTests.package/FreeTypeCacheTest.class/README.md R FreeTypeTests.package/FreeTypeCacheTest.class/definition.st R FreeTypeTests.package/FreeTypeCacheTest.class/instance/private/validateCollections_.st R FreeTypeTests.package/FreeTypeCacheTest.class/instance/private/validateSizes_.st R FreeTypeTests.package/FreeTypeCacheTest.class/instance/running/setUp.st R FreeTypeTests.package/FreeTypeCacheTest.class/instance/tests/testConstants.st R FreeTypeTests.package/FreeTypeCacheTest.class/instance/tests/testEntriesRemovedFIFO.st R FreeTypeTests.package/FreeTypeCacheTest.class/instance/tests/testFailedGet.st R FreeTypeTests.package/FreeTypeCacheTest.class/instance/tests/testFreeTypeCacheEntry.st R FreeTypeTests.package/FreeTypeCacheTest.class/instance/tests/testInstanceInitialization.st R FreeTypeTests.package/FreeTypeCacheTest.class/instance/tests/testMaximumSizeRespectedOnIfAbsentPut.st R FreeTypeTests.package/FreeTypeCacheTest.class/instance/tests/testMaximumSizeRespectedOnPut.st R FreeTypeTests.package/FreeTypeCacheTest.class/instance/tests/testNormalGetIfAbsentPut.st R FreeTypeTests.package/FreeTypeCacheTest.class/instance/tests/testNormalGetIfAbsentPutTwice.st R FreeTypeTests.package/FreeTypeCacheTest.class/instance/tests/testNormalGetIfAbsentPutTwiceIntoNonEmptyCache.st R FreeTypeTests.package/FreeTypeCacheTest.class/instance/tests/testNormalPutGet.st R FreeTypeTests.package/FreeTypeCacheTest.class/instance/tests/testNormalPutGetTwice.st R FreeTypeTests.package/FreeTypeCacheTest.class/instance/tests/testNormalPutGetWidth.st R FreeTypeTests.package/FreeTypeCacheTest.class/instance/tests/testPutSameElementTwice.st R FreeTypeTests.package/FreeTypeCacheTest.class/instance/tests/testRemoveAll.st R FreeTypeTests.package/FreeTypeCacheTest.class/instance/tests/testRemoveAllForFont.st R FreeTypeTests.package/FreeTypeCacheTest.class/instance/tests/testRemoveAllForType.st R FreeTypeTests.package/FreeTypeCacheTest.class/instance/tests/testReport.st R FreeTypeTests.package/FreeTypeCacheTest.class/instance/tests/testSetMaximumSize.st R FreeTypeTests.package/FreeTypeCacheTest.class/instance/tests/testSetMaximumSizeGrow.st R FreeTypeTests.package/FreeTypeCacheTest.class/instance/tests/testSetMaximumSizeShrink.st R FreeTypeTests.package/FreeTypeCacheTest.class/instance/tests/testSetMaximumSizeUnbounded.st R FreeTypeTests.package/FreeTypeCacheTest.class/instance/tests/testSingleton.st A Morphic-Tests.package/CircleMorphTest.class/README.md A Morphic-Tests.package/CircleMorphTest.class/definition.st A Morphic-Tests.package/CircleMorphTest.class/instance/running/setUp.st A Morphic-Tests.package/LayoutFrameTest.class/README.md A Morphic-Tests.package/LayoutFrameTest.class/definition.st A Morphic-Tests.package/LayoutFrameTest.class/instance/tests - conversion/testAsLayoutFrame.st A Morphic-Tests.package/LayoutFrameTest.class/instance/tests/testInset.st A Morphic-Tests.package/LayoutFrameTest.class/instance/tests/testLeftTopAligned.st A Morphic-Tests.package/LayoutFrameTest.class/instance/tests/testRightBottomQuadrant.st A Morphic-Tests.package/LayoutFrameTest.class/instance/tests/testSpaceFill.st A Morphic-Tests.package/LayoutFrameTest.class/instance/tests/testTransform.st A Morphic-Tests.package/LayoutFrameTest.class/instance/tests/testTransformReturnASubArea.st A Morphic-Tests.package/LayoutFrameTest.class/instance/tests/testTransformReturnEmptyRectangleWhenNotPossibleToPlace.st A Morphic-Tests.package/MCPTest.class/README.md A Morphic-Tests.package/MCPTest.class/definition.st A Morphic-Tests.package/MCPTest.class/instance/constants/defaultBounds.st A Morphic-Tests.package/MCPTest.class/instance/constants/defaultTop.st A Morphic-Tests.package/MCPTest.class/instance/tests/testTop.st A Morphic-Tests.package/MorphTest.class/README.md A Morphic-Tests.package/MorphTest.class/definition.st A Morphic-Tests.package/MorphTest.class/instance/running/setUp.st A Morphic-Tests.package/MorphTest.class/instance/running/tearDown.st A Morphic-Tests.package/MorphTest.class/instance/testing - classification/testIsMorph.st A Morphic-Tests.package/MorphTest.class/instance/testing - geometry/testBoundingBoxOfSubmorphs.st A Morphic-Tests.package/MorphTest.class/instance/testing - geometry/testExtent.st A Morphic-Tests.package/MorphTest.class/instance/testing - initialization/testOpenInWorld.st A Morphic-Tests.package/MorphTest.class/instance/testing - into%2Foutof world/testIntoWorldCollapseOutOfWorld.st A Morphic-Tests.package/MorphTest.class/instance/testing - into%2Foutof world/testIntoWorldDeleteOutOfWorld.st A Morphic-Tests.package/MorphTest.class/instance/testing - into%2Foutof world/testIntoWorldTransferToNewGuy.st A Morphic-Tests.package/MorphTreeMorphTests.class/README.md A Morphic-Tests.package/MorphTreeMorphTests.class/definition.st A Morphic-Tests.package/MorphTreeMorphTests.class/instance/tests/testLastClickedMorphSetUponUpdateList.st A Morphic-Tests.package/MorphTreeMorphTests.class/instance/tests/testLeakingSelectionsOnUpdate.st A Morphic-Tests.package/MorphTreeMorphTests.class/instance/tests/testMaintainingSelectionsOnUpdate.st A Morphic-Tests.package/MorphTreeMorphTests.class/instance/tests/testUpdatingSelectionsOnUpdate.st A Morphic-Tests.package/MorphTreeMorphTests.class/instance/tests/testUpdatingSelectionsOnUpdateWithRemoval.st A Morphic-Tests.package/MorphicEventHandlerTest.class/README.md A Morphic-Tests.package/MorphicEventHandlerTest.class/definition.st A Morphic-Tests.package/MorphicEventHandlerTest.class/instance/running/setUp.st A Morphic-Tests.package/MorphicEventHandlerTest.class/instance/running/tearDown.st A Morphic-Tests.package/MorphicEventHandlerTest.class/instance/tests-events/testMouseEnterDraggingFromMorph.st A Morphic-Tests.package/MorphicEventHandlerTest.class/instance/tests-events/testMouseEnterFromMorph.st A Morphic-Tests.package/MorphicEventHandlerTest.class/instance/tests-events/testMouseLeaveFromMorph.st A Morphic-Tests.package/MorphicEventHandlerTest.class/instance/tests/testClickFromMorph.st A Morphic-Tests.package/MorphicEventHandlerTest.class/instance/tests/testDoubleClickFromMorph.st A Morphic-Tests.package/MorphicEventHandlerTest.class/instance/tests/testDoubleClickTimeoutFromMorph.st A Morphic-Tests.package/MorphicEventHandlerTest.class/instance/tests/testKeyStrokeFromMorph.st A Morphic-Tests.package/MorphicEventHandlerTest.class/instance/tests/testTwoEventHandlersAreAttached.st A Morphic-Tests.package/MorphicUIBugTest.class/README.md A Morphic-Tests.package/MorphicUIBugTest.class/definition.st A Morphic-Tests.package/MorphicUIBugTest.class/instance/running/setUp.st A Morphic-Tests.package/MorphicUIBugTest.class/instance/running/tearDown.st A Morphic-Tests.package/PaginatedMorphTreeMorphTests.class/README.md A Morphic-Tests.package/PaginatedMorphTreeMorphTests.class/definition.st A Morphic-Tests.package/PaginatedMorphTreeMorphTests.class/instance/tests/testPager.st A Morphic-Tests.package/PolygonMorphTest.class/README.md A Morphic-Tests.package/PolygonMorphTest.class/definition.st A Morphic-Tests.package/PolygonMorphTest.class/instance/tests/testBoundsBug1035.st A Morphic-Tests.package/RenderBugsTest.class/README.md A Morphic-Tests.package/RenderBugsTest.class/definition.st A Morphic-Tests.package/RenderBugsTest.class/instance/private/long.st A Morphic-Tests.package/RenderBugsTest.class/instance/private/shouldntTakeLong_.st A Morphic-Tests.package/RenderBugsTest.class/instance/tests/testForward.st A Morphic-Tests.package/RenderBugsTest.class/instance/tests/testHeading.st A Morphic-Tests.package/RenderBugsTest.class/instance/tests/testSetForward.st A Morphic-Tests.package/RenderBugsTest.class/instance/tests/testTestTime.st A Morphic-Tests.package/StickynessBugsTest.class/README.md A Morphic-Tests.package/StickynessBugsTest.class/definition.st A Morphic-Tests.package/StickynessBugsTest.class/instance/tests/testForTiltedStickyness.st A Morphic-Tests.package/SupplyAnswerTests.class/README.md A Morphic-Tests.package/SupplyAnswerTests.class/definition.st A Morphic-Tests.package/SupplyAnswerTests.class/instance/tests/testChooseDirectory.st A Morphic-Tests.package/SupplyAnswerTests.class/instance/tests/testFillInTheBlank.st A Morphic-Tests.package/SupplyAnswerTests.class/instance/tests/testInform.st A Morphic-Tests.package/TestInWorldMorph.class/README.md A Morphic-Tests.package/TestInWorldMorph.class/definition.st A Morphic-Tests.package/TestInWorldMorph.class/instance/accessing/intoWorldCount.st A Morphic-Tests.package/TestInWorldMorph.class/instance/accessing/intoWorld_.st A Morphic-Tests.package/TestInWorldMorph.class/instance/accessing/outOfWorldCount.st A Morphic-Tests.package/TestInWorldMorph.class/instance/accessing/outOfWorld_.st A Morphic-Tests.package/TestInWorldMorph.class/instance/initialization/initialize.st A Morphic-Tests.package/TextAnchorTest.class/README.md A Morphic-Tests.package/TextAnchorTest.class/definition.st A Morphic-Tests.package/TextAnchorTest.class/instance/running/setUp.st A Morphic-Tests.package/TextAnchorTest.class/instance/running/testMorphInline.st A Morphic-Tests.package/TextLineTest.class/README.md A Morphic-Tests.package/TextLineTest.class/definition.st A Morphic-Tests.package/TextLineTest.class/instance/running/setUp.st A Morphic-Tests.package/TextMorphTest.class/README.md A Morphic-Tests.package/TextMorphTest.class/definition.st A Morphic-Tests.package/TextMorphTest.class/instance/testing/testInitialize.st A Morphic-Tests.package/WindowAnnouncementTest.class/README.md A Morphic-Tests.package/WindowAnnouncementTest.class/definition.st A Morphic-Tests.package/WindowAnnouncementTest.class/instance/running/tearDown.st A Morphic-Tests.package/WindowAnnouncementTest.class/instance/tests - window change/testCollapsing.st A Morphic-Tests.package/WindowAnnouncementTest.class/instance/tests - window change/testMoving.st A Morphic-Tests.package/WindowAnnouncementTest.class/instance/tests - window change/testResizing.st A Morphic-Tests.package/WindowAnnouncementTest.class/instance/tests - window change/testScrolling.st A Morphic-Tests.package/WindowAnnouncementTest.class/instance/tests - window creation and deletion/testResizingClosing.st A Morphic-Tests.package/WindowAnnouncementTest.class/instance/tests - window creation and deletion/testWindowCreation.st A Morphic-Tests.package/WindowAnnouncementTest.class/instance/tests - window creation and deletion/testWindowCreationAndDeletion.st A Morphic-Tests.package/WindowAnnouncementTest.class/instance/tests - window creation and deletion/testWindowLabelling.st R MorphicTests.package/CircleMorphTest.class/README.md R MorphicTests.package/CircleMorphTest.class/definition.st R MorphicTests.package/CircleMorphTest.class/instance/running/setUp.st R MorphicTests.package/LayoutFrameTest.class/README.md R MorphicTests.package/LayoutFrameTest.class/definition.st R MorphicTests.package/LayoutFrameTest.class/instance/tests - conversion/testAsLayoutFrame.st R MorphicTests.package/LayoutFrameTest.class/instance/tests/testInset.st R MorphicTests.package/LayoutFrameTest.class/instance/tests/testLeftTopAligned.st R MorphicTests.package/LayoutFrameTest.class/instance/tests/testRightBottomQuadrant.st R MorphicTests.package/LayoutFrameTest.class/instance/tests/testSpaceFill.st R MorphicTests.package/LayoutFrameTest.class/instance/tests/testTransform.st R MorphicTests.package/LayoutFrameTest.class/instance/tests/testTransformReturnASubArea.st R MorphicTests.package/LayoutFrameTest.class/instance/tests/testTransformReturnEmptyRectangleWhenNotPossibleToPlace.st R MorphicTests.package/MCPTest.class/README.md R MorphicTests.package/MCPTest.class/definition.st R MorphicTests.package/MCPTest.class/instance/constants/defaultBounds.st R MorphicTests.package/MCPTest.class/instance/constants/defaultTop.st R MorphicTests.package/MCPTest.class/instance/tests/testTop.st R MorphicTests.package/MorphTest.class/README.md R MorphicTests.package/MorphTest.class/definition.st R MorphicTests.package/MorphTest.class/instance/running/setUp.st R MorphicTests.package/MorphTest.class/instance/running/tearDown.st R MorphicTests.package/MorphTest.class/instance/testing - classification/testIsMorph.st R MorphicTests.package/MorphTest.class/instance/testing - geometry/testBoundingBoxOfSubmorphs.st R MorphicTests.package/MorphTest.class/instance/testing - geometry/testExtent.st R MorphicTests.package/MorphTest.class/instance/testing - initialization/testOpenInWorld.st R MorphicTests.package/MorphTest.class/instance/testing - into%2Foutof world/testIntoWorldCollapseOutOfWorld.st R MorphicTests.package/MorphTest.class/instance/testing - into%2Foutof world/testIntoWorldDeleteOutOfWorld.st R MorphicTests.package/MorphTest.class/instance/testing - into%2Foutof world/testIntoWorldTransferToNewGuy.st R MorphicTests.package/MorphTreeMorphTests.class/README.md R MorphicTests.package/MorphTreeMorphTests.class/definition.st R MorphicTests.package/MorphTreeMorphTests.class/instance/tests/testLastClickedMorphSetUponUpdateList.st R MorphicTests.package/MorphTreeMorphTests.class/instance/tests/testLeakingSelectionsOnUpdate.st R MorphicTests.package/MorphTreeMorphTests.class/instance/tests/testMaintainingSelectionsOnUpdate.st R MorphicTests.package/MorphTreeMorphTests.class/instance/tests/testUpdatingSelectionsOnUpdate.st R MorphicTests.package/MorphTreeMorphTests.class/instance/tests/testUpdatingSelectionsOnUpdateWithRemoval.st R MorphicTests.package/MorphicEventHandlerTest.class/README.md R MorphicTests.package/MorphicEventHandlerTest.class/definition.st R MorphicTests.package/MorphicEventHandlerTest.class/instance/running/setUp.st R MorphicTests.package/MorphicEventHandlerTest.class/instance/running/tearDown.st R MorphicTests.package/MorphicEventHandlerTest.class/instance/tests-events/testMouseEnterDraggingFromMorph.st R MorphicTests.package/MorphicEventHandlerTest.class/instance/tests-events/testMouseEnterFromMorph.st R MorphicTests.package/MorphicEventHandlerTest.class/instance/tests-events/testMouseLeaveFromMorph.st R MorphicTests.package/MorphicEventHandlerTest.class/instance/tests/testClickFromMorph.st R MorphicTests.package/MorphicEventHandlerTest.class/instance/tests/testDoubleClickFromMorph.st R MorphicTests.package/MorphicEventHandlerTest.class/instance/tests/testDoubleClickTimeoutFromMorph.st R MorphicTests.package/MorphicEventHandlerTest.class/instance/tests/testKeyStrokeFromMorph.st R MorphicTests.package/MorphicEventHandlerTest.class/instance/tests/testTwoEventHandlersAreAttached.st R MorphicTests.package/MorphicUIBugTest.class/README.md R MorphicTests.package/MorphicUIBugTest.class/definition.st R MorphicTests.package/MorphicUIBugTest.class/instance/running/setUp.st R MorphicTests.package/MorphicUIBugTest.class/instance/running/tearDown.st R MorphicTests.package/PaginatedMorphTreeMorphTests.class/README.md R MorphicTests.package/PaginatedMorphTreeMorphTests.class/definition.st R MorphicTests.package/PaginatedMorphTreeMorphTests.class/instance/tests/testPager.st R MorphicTests.package/PolygonMorphTest.class/README.md R MorphicTests.package/PolygonMorphTest.class/definition.st R MorphicTests.package/PolygonMorphTest.class/instance/tests/testBoundsBug1035.st R MorphicTests.package/RenderBugsTest.class/README.md R MorphicTests.package/RenderBugsTest.class/definition.st R MorphicTests.package/RenderBugsTest.class/instance/private/long.st R MorphicTests.package/RenderBugsTest.class/instance/private/shouldntTakeLong_.st R MorphicTests.package/RenderBugsTest.class/instance/tests/testForward.st R MorphicTests.package/RenderBugsTest.class/instance/tests/testHeading.st R MorphicTests.package/RenderBugsTest.class/instance/tests/testSetForward.st R MorphicTests.package/RenderBugsTest.class/instance/tests/testTestTime.st R MorphicTests.package/StickynessBugsTest.class/README.md R MorphicTests.package/StickynessBugsTest.class/definition.st R MorphicTests.package/StickynessBugsTest.class/instance/tests/testForTiltedStickyness.st R MorphicTests.package/SupplyAnswerTests.class/README.md R MorphicTests.package/SupplyAnswerTests.class/definition.st R MorphicTests.package/SupplyAnswerTests.class/instance/tests/testChooseDirectory.st R MorphicTests.package/SupplyAnswerTests.class/instance/tests/testFillInTheBlank.st R MorphicTests.package/SupplyAnswerTests.class/instance/tests/testInform.st R MorphicTests.package/TestInWorldMorph.class/README.md R MorphicTests.package/TestInWorldMorph.class/definition.st R MorphicTests.package/TestInWorldMorph.class/instance/accessing/intoWorldCount.st R MorphicTests.package/TestInWorldMorph.class/instance/accessing/intoWorld_.st R MorphicTests.package/TestInWorldMorph.class/instance/accessing/outOfWorldCount.st R MorphicTests.package/TestInWorldMorph.class/instance/accessing/outOfWorld_.st R MorphicTests.package/TestInWorldMorph.class/instance/initialization/initialize.st R MorphicTests.package/TextAnchorTest.class/README.md R MorphicTests.package/TextAnchorTest.class/definition.st R MorphicTests.package/TextAnchorTest.class/instance/running/setUp.st R MorphicTests.package/TextAnchorTest.class/instance/running/testMorphInline.st R MorphicTests.package/TextLineTest.class/README.md R MorphicTests.package/TextLineTest.class/definition.st R MorphicTests.package/TextLineTest.class/instance/running/setUp.st R MorphicTests.package/TextMorphTest.class/README.md R MorphicTests.package/TextMorphTest.class/definition.st R MorphicTests.package/TextMorphTest.class/instance/testing/testInitialize.st R MorphicTests.package/WindowAnnouncementTest.class/README.md R MorphicTests.package/WindowAnnouncementTest.class/definition.st R MorphicTests.package/WindowAnnouncementTest.class/instance/running/tearDown.st R MorphicTests.package/WindowAnnouncementTest.class/instance/tests - window change/testCollapsing.st R MorphicTests.package/WindowAnnouncementTest.class/instance/tests - window change/testMoving.st R MorphicTests.package/WindowAnnouncementTest.class/instance/tests - window change/testResizing.st R MorphicTests.package/WindowAnnouncementTest.class/instance/tests - window change/testScrolling.st R MorphicTests.package/WindowAnnouncementTest.class/instance/tests - window creation and deletion/testResizingClosing.st R MorphicTests.package/WindowAnnouncementTest.class/instance/tests - window creation and deletion/testWindowCreation.st R MorphicTests.package/WindowAnnouncementTest.class/instance/tests - window creation and deletion/testWindowCreationAndDeletion.st R MorphicTests.package/WindowAnnouncementTest.class/instance/tests - window creation and deletion/testWindowLabelling.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50300.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50301.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50300.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50301.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50301 14432 FreeTypeTests package should be FreeType-Tests https://pharo.fogbugz.com/f/cases/14432 14427 CompressionTests package should be Compression-Tests https://pharo.fogbugz.com/f/cases/14427 14434 MorphicTests package should be Morphic-Tests https://pharo.fogbugz.com/f/cases/14434 http://files.pharo.org/image/50/50301.zip

Sept. 3, 2015

Re: [Pharo-dev] GitFileTree: Playing Nice with FileTree

by Peter UhnÃ¡k

Hi > (git)filetree://path/to/canonical/local/repo This is a relative path: (git)filetree:// + path/to/... it should be: (git)filetree:// + /my/absolute/path (triple slash) As for FileTree/GitFileTree, due to windows issues my colleague and I were using both. I was commiting directly through gitfiletree, and he was comitting via filetree, and then applying git on top of that manually. And if MCBrowser can't do it, maybe try it from playground... e.g. Metacello new baseline: 'Project'; "or configuration maybe for non-git" repository: 'gitfiletree:///my/abs/path/repository'; load. Peter On Thu, Sep 3, 2015 at 6:53 AM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > Hi Sean, > > Le 03/09/2015 04:29, Sean P. DeNigris a Ã©crit : > >> If I have a filetree://path/to/canonical/local/repo repository, can I >> later >> point a GitFileTree repo to that folder? From the MC Browser +Repository >> menu, I only seem to be able to set the subfolder relative to the >> #imageDirectory, not the absolute pathâ¦ >> > > Are you sure about the local path? I know I played with a few things to > try to get local paths to work if used. > > But gitfiletree://path/to/canonical/local/repo will work. > > Thierry > >

Sept. 3, 2015