February 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] #new version #basicNew when materializing (SIXX/Fuel difference)

by Eliot Miranda

On Thu, Feb 27, 2014 at 5:29 AM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > Hi guys, > > I found this a bit strange and arguable. Upon materialization, for normal > classes, Fuel uses #basicNew to instantiate objects and then sets its > instances variables values getting them from the stream.... > > Today I found that SIXX sends #new first (*and hence #initialize is sent*) > and after, if fails, it tries, #basicNew. > > This 2 approaches have different results. > > Which one would you expect? > Yours. SIXX's approach is doing unnecessary work. Answer it another way. Have you found any cases where using basicNew[:] leads to errors? If not, then it is the better approach because it is more efficient. -- best, Eliot

Feb. 28, 2014

Re: [Pharo-dev] ws vs st extensions

by Esteban A. Maringolo

2014-02-28 18:26 GMT-03:00 Chris Cunningham <cunningham.cb(a)gmail.com>: > On Fri, Feb 28, 2014 at 6:07 AM, Esteban A. Maringolo <emaringolo(a)gmail.com> > wrote: >> >> I have a naive question... >> >> Why if the BasicCodeLoader handler looks for .st files does the >> Workpace offer .ws as the default extension? > > Well, the workspace doesn't just use chuck format - in fact, you rarely put > in chunk format into a workspace (or do you? I certainly don't). Also, > workspaces allow for dynamic local variables - which normal chunk loaders > don't. The two things behave differently. .st is explicitly for runnable > code - workspaces are for more than just code - more of a scratch pad. I know, but the cmd line handler isn't a chunk reader. It compiles the content of the file and evaluate it all at once. And explicitly expects for files with .st extension (I don't understand such restriction). I don't put chunk in a workspace either (actually I don't know how to properly read a chunk file in Pharo). tl;dr Frankly I don't like the .ws extension at all. It's a matter of habit. :) Regards! Esteban A. Maringolo

Feb. 28, 2014

Re: [Pharo-dev] ws vs st extensions

by Chris Cunningham

On Fri, Feb 28, 2014 at 6:07 AM, Esteban A. Maringolo <emaringolo(a)gmail.com>wrote: > I have a naive question... > > Why if the BasicCodeLoader handler looks for .st files does the > Workpace offer .ws as the default extension? > Well, the workspace doesn't just use chuck format - in fact, you rarely put in chunk format into a workspace (or do you? I certainly don't). Also, workspaces allow for dynamic local variables - which normal chunk loaders don't. The two things behave differently. .st is explicitly for runnable code - workspaces are for more than just code - more of a scratch pad. -cbc > > Why not a single extension for Smalltalk files? (.st) and other for > chunked content (changesets?) > > :) > > > Esteban A. Maringolo > >

Feb. 28, 2014

Re: [Pharo-dev] Gettext broken in Pharo 3.0

by Pharo4Stef

thanks usman do you have the expression to load gettext in pharo 3.0 On 28 Feb 2014, at 15:36, Usman Bhatti <usman.bhatti(a)gmail.com> wrote: > Hello, > > I encountered a problem when trying to export the Gettext file in Pharo 3.0. > In a Pharo 3.0 image, load Gettext and then do the following: > > TextDomainManager > registerCategoryPrefix: 'Fuel' > domain: 'Fuel'. > > GetTextExporter exportTemplate. > > Apparently, there are some deprecations and doing proceed on them shows a DNU: > "RBMethodNode does not understand isMessageNode" > > I can report the bug somewhere to later find some time to correct it but Pharo bug tracker might not be the right place. Any ideas where this bug should be reported? > > If someone knowledgeable about RB related stuff can have a look at it, it would be great. > > tx, > usman

Feb. 28, 2014

Re: [Pharo-dev] ws vs st extensions

by Esteban A. Maringolo

I thought so. Esteban A. Maringolo 2014-02-28 18:09 GMT-03:00 Pharo4Stef <pharo4Stef(a)free.fr>: > > On 28 Feb 2014, at 15:07, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > >> I have a naive question... >> >> Why if the BasicCodeLoader handler looks for .st files does the >> Workpace offer .ws as the default extension? >> >> Why not a single extension for Smalltalk files? (.st) and other for >> chunked content (changesets?) > > legacy :) > >> >> :) >> >> >> Esteban A. Maringolo >> > >

Feb. 28, 2014

Re: [Pharo-dev] ws vs st extensions

by Pharo4Stef

On 28 Feb 2014, at 15:07, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > I have a naive question... > > Why if the BasicCodeLoader handler looks for .st files does the > Workpace offer .ws as the default extension? > > Why not a single extension for Smalltalk files? (.st) and other for > chunked content (changesets?) legacy :) > > :) > > > Esteban A. Maringolo >

Feb. 28, 2014

Help needed! ClassTest>>#testRenaming

by Nicolai Hess

Hope we can sort this out, more and more fixes suffer from the wrong testing failures and nothing new gets integrated. 12996 <https://pharo.fogbugz.com/default.asp?12996>ClassTest>>#testRenaming leaves dirty package Dummy-Tests-Class behind 12995 <https://pharo.fogbugz.com/default.asp?12995> CI ClassTest>>#testRenaming is failing available options: 1. skip test 2. test for nil in RPackageOrganizer>>#systemClassRenamedActionFrom: before rPackage updateDefinedClassNamed: oldName withNewName: newName. 3. review changes for issue 12601 (fix RPackageOrganizer>>#systemCategoryRemovedActionFrom: ann, to unregister packages even if there are MCPackages (don't know about the side effects) best solution would be number 3, but the recent submissions for issue 12601 are quite complex, so I don't know. Nicolai

Feb. 28, 2014

Re: [Pharo-dev] Pharo 3 shortcuts

by Hernan Wilkinson

On Fri, Feb 28, 2014 at 1:06 PM, Sergi Reyner <sergi.reyner(a)gmail.com>wrote: > El 28/02/2014 16:00, "Hernan Wilkinson" <hernan.wilkinson(a)10pines.com> > escribiÃ³: > > > > > For example, looking for senders on the code panel is alt+n but if you > are on the method list it is different, it is alt+b+n which is really > difficult to press because three fingers has to be used and the b and n are > close one to the other. The one impossible to press is when looking for > class references because it is alt+b+N, that is lowercase b and uppercase N > at the same time, which is impossible so there is no other solution that to > use the menu > > Try pressing alt+b, then alt+n. Why would you assume that both letters > have to be pressed at the same time? :) > cool, that worked but it is really awkward and slow compared to the previous one, why not just alt+n? I assume that is to get more possibilities, more shortcuts but is it really necessary? -- *HernÃ¡n Wilkinson Agile Software Development, Teaching & Coaching* *Phone: +54 - 011 - *6091 - 3125 * Mobile: +54 - 911 - 4470 - 7207email: hernan.wilkinson(a)10Pines.comsite: http://www.10Pines.com <http://www.10pines.com/>* Address: Alem 693, Floor 5 B, Buenos Aires, Argentina

Feb. 28, 2014

Re: [Pharo-dev] Pharo 3 shortcuts

by Sergi Reyner

El 28/02/2014 16:00, "Hernan Wilkinson" <hernan.wilkinson(a)10pines.com> escribiÃ³: > > For example, looking for senders on the code panel is alt+n but if you are on the method list it is different, it is alt+b+n which is really difficult to press because three fingers has to be used and the b and n are close one to the other. The one impossible to press is when looking for class references because it is alt+b+N, that is lowercase b and uppercase N at the same time, which is impossible so there is no other solution that to use the menu Try pressing alt+b, then alt+n. Why would you assume that both letters have to be pressed at the same time? :)

Feb. 28, 2014

Pharo 3 shortcuts

by Hernan Wilkinson

Hi, I been using pharo 3 during this week and I'd like to say that it is working great!, it runs faster, looks stable, etc. So, congratulations for the excellent work you are doing. At the same time, I'd like to comment that I feel uncomfortable with the browser's shortcuts and some of them are impossible to use or not consistent. For example, looking for senders on the code panel is alt+n but if you are on the method list it is different, it is alt+b+n which is really difficult to press because three fingers has to be used and the b and n are close one to the other. The one impossible to press is when looking for class references because it is alt+b+N, that is lowercase b and uppercase N at the same time, which is impossible so there is no other solution that to use the menu, but looking for class references is not a first option on the menu but one that is almost the last option on the Analyze menu so you have to navigate a lot with the mouse to get there... For sure there is a reason for these shortcuts... can somebody explain them or point me to where to read them? Thanks -- *HernÃ¡n Wilkinson Agile Software Development, Teaching & Coaching* *Phone: +54 - 011 - *6091 - 3125 * Mobile: +54 - 911 - 4470 - 7207email: hernan.wilkinson(a)10Pines.comsite: http://www.10Pines.com <http://www.10pines.com/>* Address: Alem 693, Floor 5 B, Buenos Aires, Argentina

Feb. 28, 2014