- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]
by GitHub Jan. 10, 2014

Jan. 10, 2014

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

1 0

[Fwd: New request to join project pharo-contribution]
by btc＠openinworld.com Jan. 10, 2014

Jan. 10, 2014

2 1

How to handle merge conflicts?
by Nicolai Hess Jan. 10, 2014

Jan. 10, 2014

How are merge conflicts handled? If you look at issue 7542 <https://pharo.fogbugz.com/default.asp?7542> there is a merge conflict with the current version and SLICE-Issue-7542-NB-system-example-IgorStasenko.2 The current version usess Smalltalk compiler new ... and igors version uses Smalltalk compiler ... Smalltalk compiler new doesn't work, as Smalltalk compiler is alread an instance of OpalCompiler nicolai

2 1

"Bootstrap" project for Seaside with separated Magritte support in a new project "BootstrapMagritte" on STHub
by Torsten Bergmann Jan. 10, 2014

Jan. 10, 2014

Hi, The bundling with magritte polluted the repo and the Bootstrap project with stuff that was not really needed for "Seaside + Bootstrap" only. Also a "Bootstrap-Demo" package appeared that was more a demo for magritte than for Bootstrap. Since there already was an "Bootstrap-Examples" package this added more confusion (at least on my side). I now took action and cleaned up the Bootstrap project again to remove the magritte stuff. If one wants to to use Bootstrap with Seaside he does not necessarily have to go the Magritte path, so IMHO this was necessary. The magritte stuff for Bootstrap is now hosted as an own separate project on STHub which would also help to see to which part code additions really belong. As a result: ============ 1. The Bootstrap project now again only contains and loads the initial three packages: - Bootstrap-Core - Bootstrap-Tests-Core - Bootstrap-Examples assembled by the known ConfigurationOfBootstrap 2. The Magritte support on top of Bootstrap is now separated in an own project to avoid too much mixin. See "BootstrapMagritte" on SmalltalkHub. The new repo "http://smalltalkhub.com/#!/~TorstenBergmann/BootstrapMagritte" has the same commiters as the old one, so feel free to continue with your work. This project includes two packages: - Bootstrap-Magritte-Core (former Bootstrap-Magritte) - Bootstrap-Magritte-Examples (former Bootstrap-Demo) assembled by a new ConfigurationOfBootstrapMagritte for this particular project 3. The Bootstrap/ConfigurationOfBootstrap is now available as - a release version 0.4.0 for Seaside 3.0.9 - a release version 0.5.0 for Seaside 3.0.10 - a release version 0.6.0 for Seaside 3.1.0 (#stable) - a development version 0.7.0 for Seaside 3.1.0 for new stuff 4. The CI for Bootstrap is green for Pharo 2.0 and now also Pharo 3.0 5. The config browser is updated for Pharo 2.0 and Pharo 3.0 with the "Bootstrap" package So you can now also open a fresh Pharo 3.0 image, open World menu -> Configuration Browser to load "Bootstrap". Then run ZnZincServerAdaptor startOn: 8080 and start coding your web application with the latest Seaside 3.1.0. Next steps: Setting up a CI for the new project "BootstrapMagritte"/ConfigurationOfBootstrapMagritte Have fun! Bye Torsten

1 0

A question about AST
by Nicolas Passerini Jan. 10, 2014

Jan. 10, 2014

I am looking at the AST of a method like this: someMethod ^ SomeClass new It was a surprise to me that the note for 'SomeClass' is an RBVariableNode instead of a RBClassReference. Which is the best way to tell if an RBVariableNode represents a global reference or an instance variable? On the other hand, there are no references to RBClassReference, so this might be a bug? Thanks, Nico

3 4

Fwd: where is hosted Grease?
by HernÃ¡n Morales Durand Jan. 10, 2014

Jan. 10, 2014

---------- Forwarded message ---------- From: HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> Date: 2014/1/9 Subject: Re: [Pharo-dev] where is hosted Grease? To: Damien Cassou <damien.cassou(a)gmail.com> Thanks Damien, For the Seaside team, you only need to merge changes from my repository http://smalltalkhub.com/#!/~hernan/Grease I hope one day you could take the time to do it, takes less energy than claiming property rights :) Cheers, HernÃ¡n 2014/1/6 Damien Cassou <damien.cassou(a)gmail.com> > On Mon, Jan 6, 2014 at 8:41 PM, HernÃ¡n Morales Durand > <hernan.morales(a)gmail.com> wrote: > > > > So I've decided to load Seaside configuration and they seem to add > > FileDirectory in FileSystem-Legacy from Seaside30LGPL. > > Then I wonder, how do you load Grease indenpendently of Seaside? > > In this job https://ci.inria.fr/pharo-contribution/job/Grease, the > configuration script contains: > > REPO=http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main > ./pharo $JOB_NAME.image config $REPO ConfigurationOf$JOB_NAME > --install=$VERSION --group='Core Tests' > ./pharo $JOB_NAME.image test --junit-xml-output "$JOB_NAME.*" > > > I don't know more than this :-). > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill >

1 0

Nautilus: Package file-outs are empty
by Nicolai Hess Jan. 9, 2014

Jan. 9, 2014

Regarding issue 12589. How should we do a file-out of a classTag from a Package? Nautilus and RPackageTag uses the RPackageTag name for display and file-outs. For example. RPackageTag "BasicObjects" in RPackage "Kernel" uses the name BasicObjects for the file-out file. The file is empty, because it uses SystemOrganization fileOutCategory: self name on: internalStream. I think it shoud use self categoryName instead of self name (Kernel-BasicObjects) What should we use for the file-out file name? self categoryName, too ? There is a problem with Packages like "AST-Core", as it includes a classTag with the same name. RPackage "AST-Core" and RPackageTag "AST-Core" should file-out to different files with different contents. Nicolai

1 0

Athens SVG Import
by J.F. Rick Jan. 9, 2014

Jan. 9, 2014

This message is mainly for Igor, who probably already curses every time he sees my name on the development list. But, perhaps others have had some experience with this as well. I'm still working on moving my touch applications to Athens. I am running into a major problem with icons. My applications tend to have quite a few icons in them. In the old BitBlt versions, I just used forms for the icons. That same approach fails with Athens as form rendering is time consuming. With just ten medium-sized forms open in my AthensWrapMorph, the system starts to crawl. My guess is that form rendering needs to be sped up before Athens can be widely adopted. Using the form as a paint, while flexible, seems pretty intense. Anyway, for most of my applications, switching over to vector-based graphics would be a better choice as it would allow for me to more easily scale to different screen sizes. So, I was excited to try the SVG import. Now that the XMLParser is working, I am running into some problems with the SVG import code. It seems that it doesn't support some of the features that an SVG export from Illustrator produces. I was wondering if I could get some help there. First, Illustrator tends to spit out SVGs that use #reflectedCubicBezier curves, which is not yet implemented. Second, I found a small bug in ASPathConverter>>readPoint The "self skipBlanks" has to be changed to "self skipBlanksAndComma" or multiple points cannot be read in sequence. Third, while ASPathConverter supports vLineTo: and hLineTo:, AthensCairoPathBuilder does not. I tried implementing these myself but they apparently don't work the way I thought they should. Here are two examples of the kind of SVG files I would like to read: button-swapShapes.svg<http://home.cc.gatech.edu/je77/uploads/1/button-swapShapes.svg> - This one fails because of vLineTo: and hLineTo: button-erase.svg <http://home.cc.gatech.edu/je77/uploads/1/button-erase.svg> - This one fails because of reflectedCubicBezier curves. Cheers, Jeff -- Jochen "Jeff" Rick, Ph.D. http://www.je77.com/ Skype ID: jochenrick

3 13

logCr in SpecDebugger
by Esteban Lorenzano Jan. 9, 2014

Jan. 9, 2014

Hi, I found this in SpecDebugger>>#updateCodeFromContext: ... self logCr: aContext receiver class. ... is there any any reason? Esteban

3 2

TDD in Core
by Sean P. DeNigris Jan. 9, 2014

Jan. 9, 2014

We should have a policy on this. I've been guilty of writing new features without tests too. It's bad enough we have to deal with untested legacy code, but to replace key parts of the system with untested code doesn't seem like such a good idea. In particular, the latest Spec refactoring broke a lot of the UI. It's a validation of how well it's been received. It has become a crucial part of much of the IDE. At various points in 3.0 the ChangeSorter, Versionner, and SliderModel have been broken, to name a few, and I get mysterious and sudden, often image wrecking, DNUs that appear, like TextModel>>#asText. It's made it very hard to work, especially when the compiler, RPackage, etc are changing (and sometimes breaking) at the same time. ----- Cheers, Sean -- View this message in context: http://forum.world.st/TDD-in-Core-tp4735378.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

4 4