June 2012 - Pharo-dev - lists.pharo.org

[Pharo-project] [update 2.0] #20123

by StÃ©phane Ducasse

20123 ----- - Issue 6043: Unused ivs in SystemNavigation. Thanks Camille Teruel. http://code.google.com/p/pharo/issues/detail?id=6043. - Issue 6033: RPackageOrganizer should use the private announcer and not the public one. http://code.google.com/p/pharo/issues/detail?id=6033. - Issue 6016: privateAnnouncer is not used and this is not good. http://code.google.com/p/pharo/issues/detail?id=6016 Stef

June 10, 2012

Re: [Pharo-project] Look and font competition

by Pavel Krivanek

What about slightly warmer base color that plain gray. baseColor ^ Color r: 199 g: 192 b: 181 range: 255 I'm confident with DejaVu font. I tried several others but in case I found some font that looked prettier, it was hardly usable for the code (e.g. URW Ghotic L). -- Pavel On Sun, Jun 10, 2012 at 10:27 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guys > > this morning Igor shows me all his work around dynlib loading of third party plugins. > And yes now we get all the third party plugins downloaded and compiled (yes with only one copy of FT2)â¦.Great stuff! > > Now we would like to organize a little competition for the official look of Pharo 2.0. So if you feel that you are a little > bit designer inside, please send us proposals. > We propose this one :) based on Curlz MT (welcome to the world of the pink little ponies) :) > >

June 10, 2012

Re: [Pharo-project] Look and font competition

by Igor Stasenko

ah.. sorry it looks like google's viewer using crappy rendering quality.. if i download it and look using preview , the image quality is preserved On 10 June 2012 16:44, Igor Stasenko <siguctua(a)gmail.com> wrote: > Stef, don't use pdf for image transfer.. it turns a beautiful, nicely > antialiased png picture into horrible back-to-80's patches. > > On 10 June 2012 10:27, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> Hi guys >> >> this morning Igor shows me all his work around dynlib loading of third party plugins. >> And yes now we get all the third party plugins downloaded and compiled (yes with only one copy of FT2)â¦.Great stuff! >> >> Now we would like to organize a little competition for the official look of Pharo 2.0. So if you feel that you are a little >> bit designer inside, please send us proposals. >> We propose this one :) based on Curlz MT (welcome to the world of the pink little ponies) :) >> >> > > > > -- > Best regards, > Igor Stasenko. -- Best regards, Igor Stasenko.

June 10, 2012

Re: [Pharo-project] Look and font competition

by Igor Stasenko

Stef, don't use pdf for image transfer.. it turns a beautiful, nicely antialiased png picture into horrible back-to-80's patches. On 10 June 2012 10:27, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guys > > this morning Igor shows me all his work around dynlib loading of third party plugins. > And yes now we get all the third party plugins downloaded and compiled (yes with only one copy of FT2)â¦.Great stuff! > > Now we would like to organize a little competition for the official look of Pharo 2.0. So if you feel that you are a little > bit designer inside, please send us proposals. > We propose this one :) based on Curlz MT (welcome to the world of the pink little ponies) :) > > -- Best regards, Igor Stasenko.

June 10, 2012

[Pharo-project] Look and font competition

by StÃ©phane Ducasse

Hi guys this morning Igor shows me all his work around dynlib loading of third party plugins. And yes now we get all the third party plugins downloaded and compiled (yes with only one copy of FT2)â¦.Great stuff! Now we would like to organize a little competition for the official look of Pharo 2.0. So if you feel that you are a little bit designer inside, please send us proposals. We propose this one :) based on Curlz MT (welcome to the world of the pink little ponies) :)

June 10, 2012

[Pharo-project] Nautilus & Trats

by Igor Stasenko

Hi, i have many DNU's when working with Nautilus and coding traits.. - browsing trait's class side -> DNU - changing/adding new methods -> DNU please check that -- Best regards, Igor Stasenko.

June 10, 2012

[Pharo-project] Enhancement - version history to include class and method renames

by Ben Coman

Since <Versions> shows both the class name and method name, it would be useful to have class and method renames to have that show up in the version history. Use case: 1. PersonA creates a ClassA and methodA. <Versions> shows the author of ClassA>methodA as PersonA. 2. PersonB renames classA to classB. <Versions> shows the author of ClassB>methodA as PersonA. Where as I think the guilty party should show as PersonB. cheers -ben

June 10, 2012

Re: [Pharo-project] DBXTalk code changes / band-aides

by Cam S

After yet another search of the forums, this time I think I struck gold: I found this tidbit... Gofer new renggli: 'magritte3'; package: 'Magritte-Model'; package: 'Magritte-Pharo-Model'; package: 'Magritte-Seaside'; package: 'Magritte-Pharo-Seaside'; package: 'Magritte-Morph'; package: 'Magritte-Tests-Model'; package: 'Magritte-Tests-Pharo-Model'; load. Doing that, it looks like there is sanity in the asComponent method. I am testing it now. (It as a March posting...) -cam

June 10, 2012

[Pharo-project] DBXTalk code changes / band-aides

by Cam S

> > >>> > >> I have a few fixes for DBXTalk: the Magritte descriptions generation (I >>> switched Array output code-generation to the {...} format instead of #( >>> ...) which was not allowing #conditions: to be properly formatted, which >>> may be a problem for other smalltalk environments), and other trivial fixes. >>> >> > Excellent!!! :) Thanks. Can you send us the changes or directly commit? > Band-aide approach... DBXMagritteWriterVisitor>>writeDescription: aMADescription onClass: aClass | properties descriptionMethod classes | properties := '; ' join: (aMADescription properties associations collect: [ :assoc | '{1}: {2}' format: {(assoc key). "assoc value printString" ((assoc value isKindOf: Array) ifTrue: ['{', ('. ' join: assoc value ), '}' ] ifFalse: [ assoc value printString ])} ]). ... - <clipped> Mine is a horrible solution. Given that there are blocks in the conditions loops, the traditional array notation, #( ... ), will not work anyway, so the curly-brace approach is fine. I played around with #respondsTo: and tried to generalize, but hit problems because the value is often a symbol or string. so in the end, to get my classes generated, I just did the above quick-n-dirty patch. The only other changes I have gone ahead and made were to make certain that more methods of DBXEntity return the newly created attribute/entity, so that I could say something like the following: (e hasOne: #DpAddress as: #mailingAddress) label: 'Mailing Address'; priority: 400. So all of the #hasOne:as:, #hasMany:as:, etc. .... Oops... looks like late last night, when I was updating packages to see if i was missing anything, I lost my changes to those methods! There were only 4 or 5 such changes, and they were trivial. Cheers. I like the DBXTalk approach. And Magritte too. In the two major projects I worked on over the years, and even on a couple of small side projects, I/we ended up using meta-language tools to add runtime behavior; and the starting code for new objects, at least in the one big project, was generated from a short-hand table of the meta-language specs. Very powerful. And lazy people like me are drawn to such things. Nice work guys! Cam

June 10, 2012

Re: [Pharo-project] [Pharo-users] loading order for seaside / DBXTalk + Magritte / Pharo 1.4 / configuration

by Cam S

> > I keep having problems with configurations. The documentation for each >>>> particular tool looks so simple, and seems to work all by itself, but for >>>> some reason, I keep failing at having one 1.4 (or 1.3) image where >>>> everything works (e.g. Glorp AND seaside AND DBXTalk); though I do have 3 >>>> different images where 2-out of three work, so by revolving my dev process >>>> through the images, >>>> >>> >> > what is *exactly* what does not work? otherwise we cannot guess. >> > Like Object instance>>#description, which prevents asComponent from working, in the currently configured 1.4 image I am working with. If I change the behavior there, I run into other problems. Other problems in other images with different load orders. I was not expecting anyone to guess. I was just wondering whether anyone has actually made them all work together or not. If not, then I do not have time to be the one to battle through it. Same old story: I simply do not have time. - I will go through the load process again, keeping it minimal, and provide the scripts (workspace contents) back on this list. I have a few fixes for DBXTalk: the Magritte descriptions generation (I >>>> switched Array output code-generation to the {...} format instead of #( >>>> ...) which was not allowing #conditions: to be properly formatted, which >>>> may be a problem for other smalltalk environments), and other trivial fixes. >>>> >>> >> Excellent!!! :) Thanks. Can you send us the changes or directly commit? >> > Sure, I would rather not commit them without someone else reviewing them. Does the {} array notation work in any flavors of smalltalk other than Pharo? Thanks, I will get back to you... after I go through this process again. -Cam

June 9, 2012