- Pharo-dev - lists.pharo.org

[Pharo-project] [update 1.3] #13143

by Marcus Denker

13143 ----- Issue 3989: Fix the scrollToView method Issue 3800: StaticForm can be removed Issue 3960: Catch all: Remove experimental + ancient backward compatibility code -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

April 12, 2011

Re: [Pharo-project] Issue 3960 in pharo: Catch all: Remove experimental + ancient backward compatibility code

by pharo＠googlecode.com

Updates: Status: Closed Comment #6 on issue 3960 by marcus.d...(a)gmail.com: Catch all: Remove experimental + ancient backward compatibility code http://code.google.com/p/pharo/issues/detail?id=3960 in 14143

April 12, 2011

Re: [Pharo-project] Issue 3990 in pharo: 2 dependencies removed from ToolBuilder: PluggableMenuSpec & PluggableMenuItemSpec

by pharo＠googlecode.com

Updates: Status: Started Comment #2 on issue 3990 by marcus.d...(a)gmail.com: 2 dependencies removed from ToolBuilder: PluggableMenuSpec & PluggableMenuItemSpec http://code.google.com/p/pharo/issues/detail?id=3990 Nope. needs testing. (I had problems with the world menu after)

April 12, 2011

Re: [Pharo-project] Issue 3800 in pharo: StaticForm can be removed

by pharo＠googlecode.com

Updates: Status: Closed Comment #5 on issue 3800 by marcus.d...(a)gmail.com: StaticForm can be removed http://code.google.com/p/pharo/issues/detail?id=3800 in 14143

April 12, 2011

Re: [Pharo-project] Issue 3989 in pharo: Fix the scrollToView method

by pharo＠googlecode.com

Updates: Status: Closed Comment #1 on issue 3989 by marcus.d...(a)gmail.com: Fix the scrollToView method http://code.google.com/p/pharo/issues/detail?id=3989 in 14143

April 12, 2011

Re: [Pharo-project] Issue 3990 in pharo: 2 dependencies removed from ToolBuilder: PluggableMenuSpec & PluggableMenuItemSpec

by pharo＠googlecode.com

Updates: Status: Closed Comment #1 on issue 3990 by marcus.d...(a)gmail.com: 2 dependencies removed from ToolBuilder: PluggableMenuSpec & PluggableMenuItemSpec http://code.google.com/p/pharo/issues/detail?id=3990 in 14143

April 12, 2011

Re: [Pharo-project] Issue 3992 in pharo: Proposed O2 fixes for Pharo-1.2

by pharo＠googlecode.com

Updates: Cc: roeth...(a)iam.unibe.ch Labels: Type-O2 Comment #2 on issue 3992 by marcus.d...(a)gmail.com: Proposed O2 fixes for Pharo-1.2 http://code.google.com/p/pharo/issues/detail?id=3992 (No comment was entered for this change.)

April 12, 2011

Re: [Pharo-project] Using SMark

by Stefan Marr

Hi Javier: On 12 Apr 2011, at 04:52, Javier PimÃ¡s wrote: > Hi, I need to do some benchmarking on SqueakNOS and I'm exploring SMark. I downloaded the SMark and PBenchmarks packages from monticello, but now I don't know what to do to use it. The tests pass mostly OK, but, how do you run the existing benchs? To execute a benchmark suite, you can just send it the #run, or #run:withAnIntForTheNumberOfIterations messages. This will return the runner, that also has the results. The results are then processed or reported by one of the reporters, but there aren't many yet. Depending on your needs, you might also want to use another runner then the standard one. How to use them is currently probably documented best in the tests. But there are also some class comments here and there. > Is there any tool for visualizing the results? There is nothing fancy like the test runner UI. But the following should work: | runner | runner := SMarkLoops run: 10. SMarkSimpleStatisticsReporter reportFor: runner on: Transcript. Best regards Stefan > > Thanks, > Javier. > > -- > Javier PimÃ¡s > Ciudad de Buenos Aires -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

April 12, 2011

Re: [Pharo-project] Issue 3992 in pharo: Proposed O2 fixes for Pharo-1.2

by pharo＠googlecode.com

Comment #1 on issue 3992 by nicholas...(a)gmail.com: Proposed O2 fixes for Pharo-1.2 http://code.google.com/p/pharo/issues/detail?id=3992 Since this is the first time I am doing this following the instructions at <http://code.google.com/p/pharo/wiki/HowToContribute> I expect that I might have missed some steps. In that case please let me know and I can fix them. I've also attached the SLICE here just in case. Attachments: SLICE-Issue-3992-Proposed-O2-fixes-for-Pharo-12-NC.1.mcz 23.4 KB

April 12, 2011

[Pharo-project] Issue 3992 in pharo: Proposed O2 fixes for Pharo-1.2

by pharo＠googlecode.com

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.

April 12, 2011