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

[Pharo-project] Please clarify which versions to report issues on
by DougEdmunds April 12, 2011

April 12, 2011

If you start to open a new issue on http://code.google.com/p/pharo/issues/list this is what appears: "We are currently working on version 1.2, so please verify your issue with the latest 1.2 Unstable version before reporting it - we improved a lot the system." But on http://www.pharo-project.org/pharo-download, the 'unstable' version is listed as Pharo 1.3 image (unstable), with a link to PharoCore 1.3 (just core). Is there another place to go to for 1.2 Unstable? Or should everything be reported against 1.3? If it is 1.3, can someone update the default text new issue info on code.google.com? -- View this message in context: http://forum.world.st/Please-clarify-which-versions-to-report-issues-on-tp3… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

1 0

Re: [Pharo-project] [Seaside] [ANN] Seaside Tutorial Ready for 3.0
by Mariano Martinez Peck April 12, 2011

April 12, 2011

This was the first tutorial I read and it was really nice. Thanks a lot for this. Mariano ---------- Forwarded message ---------- From: Michael Perscheid <michaelperscheid(a)googlemail.com> Date: Tue, Apr 12, 2011 at 3:21 PM Subject: [Seaside] [ANN] Seaside Tutorial Ready for 3.0 To: seaside(a)lists.squeakfoundation.org Hi all, I would like to announce that we have updated the Seaside tutorial of the Software Architecture Group ( http://www.hpi.uni-potsdam.de/hirschfeld/seaside/tutorial) Now it can be applied with the current Seaside 3.0 version without any problems. Besides a revision of all chapters, we have especially changed the persistence chapter and added new sections about SandstoneDB, PostgreSQL, and GemStone. Most of the update was done by Lauritz Thamsen and Tobias Pape. Thank you very much. If you have any feedback, please let us know. Best regards, Michael Perscheid _______________________________________________ seaside mailing list seaside(a)lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside -- Mariano http://marianopeck.wordpress.com

1 0

[Pharo-project] Issue 3992 in pharo: Proposed O2 fixes for Pharo-1.2
by pharo＠googlecode.com April 12, 2011

April 12, 2011

Status: New Owner: ---- New issue 3992 by nicholas...(a)gmail.com: Proposed O2 fixes for Pharo-1.2 http://code.google.com/p/pharo/issues/detail?id=3992 Pharo Metainfo ------------- Pharo image: dev Pharo core version: Pharo1.2.1 Virtual machine used: Cog VM.r2378 Description ---------- Follow the full discussion at <http://forum.world.st/Code-Navigation-Navigation-History-in-System-Browser-…>. I completely agree with StÃ©phane Ducasse's comments about O2 being outdated and how it will be replaced soon. But since I've ported it, I might as well share it with the community in case someone else is interested. These are the fixes to make it possible to load O2 into a Pharo-1.2 Dev image. It is based off the latest version of the code from the O2 repository (http://www.squeaksource.com/O2) made by David Roethlisberger. Notable changes: * Removed all references to Preferences (deprecated in Pharo 1.2) * Removed most preferences that I could not find any references to. * Made test cases pass (mostly adapting the tests to the new TestCase hierarchy that it was testing for) Remaining problems: * Undo/redo does not work in the editor. This is probably because Pharo-1.2 changed the TextEditor components (i.e. uses EditingState). * Lots of duplication between O2 and OB. Not sure whether to merge/eliminate duplication since these browsers seem to be quite independent and I don't enough of their ecosystem to say if we should merge.

1 3

[Pharo-project] Updated O2 for Pharo 1.2 [WAS] Re: [Pharo-users] Code Navigation: Navigation History in System Browser?
by Mariano Martinez Peck April 12, 2011

April 12, 2011

> > Agreed. I've invested just a few hours already so I decided to just finish > it > up. I've made the proposed fix available at > http://code.google.com/p/pharo/issues/detail?id=3992. Perhaps some other > people > might find it useful. Perhaps not, but that's OK too. :-) > > Sure. > -- > Nick > > -- > View this message in context: > http://forum.world.st/Code-Navigation-Navigation-History-in-System-Browser-… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > -- Mariano http://marianopeck.wordpress.com

1 0

[Pharo-project] [Guillermo Polito, Benjamin Van Ryseghem] Issue 3088: MNU Text>>withBlanksTrimmed
by Bernardo Ezequiel Contreras April 12, 2011

April 12, 2011

Guillermo Polito and Benjamin Van Ryseghem, Could you check your changes made to ProtocolBrowser>>initListFrom: selectorCollection highlighting: aClass ? It's related to http://code.google.com/p/pharo/issues/detail?id=3088 Basically, Guillermo added the line stringVersion: item asString and then Benjamin replaced it with stringVersion: item So, now the Protocol Browser is creating SourceMethodReferences with Texts as stringVersion. you can view those instances if you follow the steps and then execute SourcedMethodReference allInstances select: [:each | each stringVersion class == Text ] And it leads to http://code.google.com/p/pharo/issues/detail?id=3088 For what i saw, the fix will be to add Guillermo's line again but im not sure. its confusing. What do you think? Thanks

3 2

[Pharo-project] Issue 3999 in pharo: Add More Explicit Error Classes for Collections
by pharo＠googlecode.com April 12, 2011

April 12, 2011

Status: New Owner: ---- New issue 3999 by camillob...(a)gmail.com: Add More Explicit Error Classes for Collections http://code.google.com/p/pharo/issues/detail?id=3999 Added OutOfBounds and some more explicit Error Messages Kernel-CamilloBruni.863 Collections-Sequenceable-CamilloBruni.87 Collections-Unordered-CamilloBruni.110

1 0

[Pharo-project] Issue 3393 in pharo: Better support of configuration dependencies in Monticello Browser
by pharo＠googlecode.com April 12, 2011

April 12, 2011

Status: Accepted Owner: alexandre.bergel CC: da...(a)teleport.com, stephane.ducasse Labels: Difficulty-Easy New issue 3393 by alexandre.bergel: Better support of configuration dependencies in Monticello Browser http://code.google.com/p/pharo/issues/detail?id=3393 Configurations are better handled now. If the configuration you're editing depends on another configuration, then it is correctly defined in the baseline. MonticelloGUI-AlexandreBergel.83 in the inbox

1 2

[Pharo-project] Fix to be included
by Damien Cassou April 12, 2011

April 12, 2011

http://code.google.com/p/pharo/issues/detail?id=3497 -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

1 0

[Pharo-project] Issue 3996 in pharo: alt+k opens a StringHolder and not a workspace
by pharo＠googlecode.com April 12, 2011

April 12, 2011

Status: Started Owner: damien.c...(a)gmail.com Labels: Type-ReportDefect Milestone-1.2.2-DevImage Difficulty-Easy New issue 3996 by damien.c...(a)gmail.com: alt+k opens a StringHolder and not a workspace http://code.google.com/p/pharo/issues/detail?id=3996 alt+k shortcut is defined in PasteUpMorph>>defaultDesktopCommandKeyTriplets { $k. StringHolder. #open. 'Open a new, blank Workspace'}. Then, alt+k opens a StringHolder and not a plain Workspace. This prevents the user from accessing all features of workspaces (syntax highlighting, old content management, line ending handling...). It would be better to open a workspace. The correct way to do that is probably to ask the default ToolSet: ToolSet default openWorkspace However, the syntax of the table in #defaultDesktopCommandKeyTriplets prevents sending 2 messages to ToolSet. Doing { $k. ToolSet default. #openWorkspace. 'Open a new, blank Workspace'}. is fragile because it fixes the toolset upon initialization of the World. I propose to add #openWorkspace to the ToolSet class (along with a lot of other useful utilities) which would look like: ToolSet class>>openWorkspace ^ self default openWorkspace and then update #defaultDesktopCommandKeyTriplets: { $k. ToolSet. #openWorkspace. 'Open a new, blank Workspace'}.

1 2

[Pharo-project] Fix to be included
by Damien Cassou April 12, 2011

April 12, 2011

http://code.google.com/p/pharo/issues/detail?id=3996 -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

1 0