December 2011 - Pharo-dev - lists.pharo.org

[Pharo-project] [update 1.4] #14241
by Marcus Denker Dec. 2, 2011

Dec. 2, 2011

14241 ----- Issue 5028: failing MCPackageManager initialization http://code.google.com/p/pharo/issues/detail?id=5028 Issue 4914: #14196 VM crash on #cleanUpForRelease http://code.google.com/p/pharo/issues/detail?id=4914 Issue 1817: [etoy] Should remove project (Part I) http://code.google.com/p/pharo/issues/detail?id=1817 -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] [COTDC] 87 - TextStream
by Sean P. DeNigris Dec. 2, 2011

Dec. 2, 2011

Continuing in Collections... Today: TextStream Comment Of The Day Contest - One Day One Comment Rules: #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). #2: If you cannot comment it, deprecate it. Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest -- View this message in context: http://forum.world.st/COTDC-87-TextStream-tp4128886p4128886.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

3 4

Re: [Pharo-project] TestNewParagraphFix
by Marcus Denker Dec. 2, 2011

Dec. 2, 2011

On Dec 2, 2011, at 3:20 PM, Sean P. DeNigris wrote: > NewParagraph is deprecated in 1.4. TestNewParagraphFix doesn't actually > mention NewParagraph directly. The class comment says "This class tests the > same things as its superclass, but for NewParagraph which is used in the > Morphic environment." but its superclass is TestCase. > > Is TestNewParagraphFix still relevant? What was the original motivation i.e. > why is it called XxxFix? It's a test for a bug of years ago... we can just delete the test. -- Marcus Denker -- http://marcusdenker.de

2 1

[Pharo-project] The SmalltalkHub demo is online!
by Nicolas Petton Dec. 2, 2011

Dec. 2, 2011

Hi guys, I'm glad to tell you that the demo of SmalltalkHub is online. http://www.smalltalkhub.com Note that this is a demo only (all projects will be deleted at some point). You can follow the SmalltalkHub project here: http://smalltalkhub.com/user/NicolasPetton/SmalltalkHub You can report bugs you encounter on the issue tracker there. This demo is running on Pharo (the next one will be on GemStone). The changelog is quite big, but here's some important changes: - The clone feature has been removed in favor of an inbox per project. (later the inbox repository url will be visible in the project overview) - RSS feeds for project timelines and user activity - Persistency is now pluggable (the current demo uses Fuel to serialize the repository) - New help system - New chronological view of packages - More useful commit view - The issue tracker has received some love some bugs has been fixed - new statistics view - Email notifications - And of course, many bug and UX fixes Some features that will appear soon (in random order): - Scripting engine to perform actions on projects - A diff browser - the ability to accept/decline packages committed to the inbox, and move/delete packages/versions. Cheers, Nicolas

9 16

[Pharo-project] SystemNavigation vs. SystemOrganizer
by Sean P. DeNigris Dec. 2, 2011

Dec. 2, 2011

SystemNavigation default. -> an object that let's you navigate the current system SystemOrganizer default. -> ??? To get what I would expect from above, it seems I need to access the global SystemOrganization. Does anyone else find this confusing? Sean -- View this message in context: http://forum.world.st/SystemNavigation-vs-SystemOrganizer-tp4131010p4131010… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

3 4

[Pharo-project] Test Categories
by Sean P. DeNigris Dec. 2, 2011

Dec. 2, 2011

There's Tests-System - tests for various sub-categories of System Tests-SystemSupport - notice no second dash Tests-Polymorph-Widgets - with second dash I was going to change the first two to be like the last one (which is most like the category under test). But I know there are weird dash issues because of Monticello, so I wanted to ask first... Sean -- View this message in context: http://forum.world.st/Test-Categories-tp4147171p4147171.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

1 0

Re: [Pharo-project] Athens work in progress: couple screenshots
by Fernando Olivero Dec. 2, 2011

Dec. 2, 2011

I've implied using meta-programming,in order to have a uniform protocol in the abstract Canvas. AthensCanvas>>transformDescribedBy: aName self perform: ( aName , 'Transform' ) asSymbol . But i see that your approach is simpler, there's no need for a uniform protocol because when you are using a particular AthensCanvas you are fully aware of that! Regarding the build, after a lonnnngg series of errors, i also managed to build universal binaries of Cairo, using MacPorts (brew just doesn't ease the task of creating 32 bit libraries). sudo port cairo +universal, worked for me, taking at least 30 min to build. ATTENTION: Before entering the port cairo install command, I've had to manually install appleGcc4.2, found @ [1] (file name gcc-42-5666.3-darwin11.pkg. Given that i have Lion, XCode4.2, and if you just allow macports to build appleGcc4.2, it will run a process that consumes resources and finally stalls your computer! I've attached a screen shot that may help somebody else, for setting up the examples. Using NativeBoost Cog VM for Mac, downloadable from NativeBoost site or Jenkins. Great work Javier, and Igor! I'm looking forward to implement a Text editor using Cairo+Pango + "my new morphic". Fernando [1] http://r.research.att.com/tools/ On Tue, Nov 29, 2011 at 5:02 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 29 November 2011 16:12, Fernando Olivero <fernando.olivero(a)usi.ch> wrote: >> I get the point now, something like the brushes in seaside. >> Thanks for the explanation. >> >> Regarding the protocol, did you consider reusing the same idea, but >> one step before, as in the following: >> >> pathTransform := canvas transformDescribedBy: 'path'. >> pathTransform scaleBy: 0.5. >> >> imageTransform := canvas transformDescribedBy: 'image'. >> imageTransform scaleBy: 0.5. >> >> Maybe add the following for documentation: >> >> AthensCairo>>availableTransforms >> Â Â Â Â Â Â Â ^ #('path'. 'image'. ) >> >> AthensOpenGL>>availableTransforms >> Â Â Â Â Â Â Â ^ #('modelView'. 'projection'. ) >> >> This would unify the canvas protocol, for all the available rendering engines. >> > > This sounds more complicated. We can map different matrices in > different engines to Athens. > So, it is not necessary for client code to know which of them are > there, because then code will be > filled with tons of Â #ifTrue: branches ... . > > > > -- > Best regards, > Igor Stasenko.

3 2

[Pharo-project] [update 1.4] #14240
by Marcus Denker Dec. 2, 2011

Dec. 2, 2011

14240 ----- Issue 5037: Remove the failing CompiledMethodTest>>testAuthor http://code.google.com/p/pharo/issues/detail?id=5037 Issue 3529: TextMorph>>releaseCachedState creates a paragraph which causes a Subscript out of bounds in an internal RunArray http://code.google.com/p/pharo/issues/detail?id=3529 Issue 3621: The S in fullscreen should not be capitalized http://code.google.com/p/pharo/issues/detail?id=3621 -- Marcus Denker -- http://marcusdenker.de

1 0

Dec. 2, 2011

hi may be I'm wrong but I have the impression that we have around three different kinds of event system in the system - actionMap - announcement - changed: Could we simplify that? Stef

7 10

Re: [Pharo-project] Call for your input on questions you ask yourselves during merge
by Marcus Denker Dec. 1, 2011

Dec. 1, 2011

On Nov 29, 2011, at 4:25 PM, StÃ©phane Ducasse wrote: > Hi guys > > We are writing some articles on the work of veronica to support merging > activities. We need your input great smalltalk community :) > What are the questions that you ask yourselves when you are/want to merge > some code in your project? > We would like to do a compilation of questions and also evaluate how the > solution of veronica solves them or part of them. > > Here are some typical questions we asked ourselves. > - What other changes did this change require? > - Can I integrate this change right now? > - How large it is? > - Who made it? > - Is it still valid (when I'm working on an old change)? > - Is this change impacted by a change that happened in another > branch of my software? > - Which Packages are touched by the change? - Are the tests green after? - How stable is the code that is changed by this patch (that is: Was the code changed a lot recently?) - Is the changed code actually used? How is is used? --> in the sense of is that code "hot", e.g. is is used to render the current desktop? Is is needed when starting the image? Is is executed when merging changes? - What is the status of the commiter? Did he commit a lot good code or did his/her past changes lead to corrections all the time? - are there other bugs reported that are related to the change? - are there failing tests related to this change? Marcus -- Marcus Denker -- http://marcusdenker.de

2 1