- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3732 in pharo: default omni browser size bigger

by pharo＠googlecode.com

Comment #4 on issue 3732 by stephane...(a)gmail.com: default omni browser size bigger http://code.google.com/p/pharo/issues/detail?id=3732 in 1.2 Name: OmniBrowser-StephaneDucasse.504 Author: StephaneDucasse Time: 12 March 2011, 10:55:41 am UUID: de859fef-729d-45ef-91d9-4fa0371747de Ancestors: OmniBrowser-lr.503 Issue 3732: default omni browser size bigger

March 12, 2011

Re: [Pharo-project] Issue 1959 in pharo: Replace isSomething by is: #

by pharo＠googlecode.com

Comment #10 on issue 1959 by stephane...(a)gmail.com: Replace isSomething by is: # http://code.google.com/p/pharo/issues/detail?id=1959 We should probably revert this is: because this is a bad idiom.

March 12, 2011

Re: [Pharo-project] Issue 2058 in pharo: Code styling to Workspace

by pharo＠googlecode.com

Comment #6 on issue 2058 by stephane...(a)gmail.com: Code styling to Workspace http://code.google.com/p/pharo/issues/detail?id=2058 Probably not needed anymore.

March 12, 2011

Re: [Pharo-project] Issue 3706 in pharo: In OB: Text in comment pane of Browser uses syntax highlighting

by pharo＠googlecode.com

Updates: Cc: guillermopolito Comment #3 on issue 3706 by stephane...(a)gmail.com: In OB: Text in comment pane of Browser uses syntax highlighting http://code.google.com/p/pharo/issues/detail?id=3706 Sorry guys but I will not spend my time trying to understand how to fix OB. I looked at the fixes lukas published in his repository and I do not understand why this is not in PharoOB and in addition I do not have the time to understand all the changes. So may be we should remove OB from Pharo.

March 12, 2011

Re: [Pharo-project] [Moose-dev] the glamorous toolkit project

by Mariano Martinez Peck

Tudor, thanks a lot for such a big beast :) I saw some of the tools the other day with you and they were really cool. What do you think about cut a bit some functionalities and propose it as GSoC ? On Sat, Mar 12, 2011 at 8:25 AM, Tudor Girba <tudor.girba(a)gmail.com> wrote: > Hi, > > I would like to promote the idea of projects in Pharo. The concept is > simple: we should build new infrastructures that go beyond small fixes and > that require the concerted work of multiple people over a longer period of > time. > > A project has a clear goal, and is led by someone. That someone is not > necessarily the one that writes all the code (like we might tend to do it), > but simply one that ensures that the project advances, that the different > contributions are integrated, and that things are not left at 90%. > > I would like to announce the Glamorous Tool project. The goal of this > project is to provide a new set of tools for developing with Pharo. It is to > be developed on top of Glamour, and it should address at least the > followings: > - Coder (ex-System Browser) > - Debugger > - Inspector > - Playground (ex-Workspace - it's not called Workspace anymore because I > would like to encourage people not to "work" there) > - Chaser (senders, implementors and references) > > The project spans several topics. For example: > - Glamour support > - Morphic enhancements: > --- Proper TextMorph with keybindings and context sensitiveness > --- Collapsable Panes > --- Scalable tabs > --- Parallel rendering > - Suitable models > --- RPackage > --- Code introspection > --- Debugger model > - Testing > --- Because these tools are so critical, they should be robust > --- OB is a good example for the testing part > - Usability > --- Principle: Spawning a window might be easy, but it is not effective > --- Principle: Uniformity > --- Principle: Less concepts are better than many > - Graphic design of skins and icons > - Weak announcements > - Performance > > > I will lead it, and you are welcome to participate. The today sprint is a > good occasion to take a look. The current code can be found at: > > Gofer new > squeaksource: 'glamoroust'; > package: 'ConfigurationOfGlamoroust'; > load. > (Smalltalk at: #ConfigurationOfGlamoroust) perform: #loadDefault. > > > Cheers, > Doru > > -- > www.tudorgirba.com > > "Sometimes the best solution is not the best solution." > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev >

March 12, 2011

Re: [Pharo-project] Issue 3620 in pharo: Settings: OCompletion settings appear twice

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.2-DevImage Milestone-1.3 Comment #15 on issue 3620 by stephane...(a)gmail.com: Settings: OCompletion settings appear twice http://code.google.com/p/pharo/issues/detail?id=3620 (No comment was entered for this change.)

March 12, 2011

Re: [Pharo-project] Issue 3581 in pharo: [Failing test] 1.1.1 Full: MethodWrappers.Tests.ObjectAsOneTimeMethodWrapperTest.testInstallOnClassCategory

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.2-DevImage Comment #6 on issue 3581 by luc.fabr...(a)gmail.com: [Failing test] 1.1.1 Full: MethodWrappers.Tests.ObjectAsOneTimeMethodWrapperTest.testInstallOnClassCategory http://code.google.com/p/pharo/issues/detail?id=3581 Not failing in 1.2

March 12, 2011

Re: [Pharo-project] Issue 3685 in pharo: #createUserSubclass:instVarNames:categoryName: no longer accepts an inst var array

by pharo＠googlecode.com

Updates: Status: Fixed Comment #2 on issue 3685 by stephane...(a)gmail.com: #createUserSubclass:instVarNames:categoryName: no longer accepts an inst var array http://code.google.com/p/pharo/issues/detail?id=3685 (No comment was entered for this change.)

March 12, 2011

Re: [Pharo-project] Issue 674 in pharo: Registration for PasteUpMorph menu needed

by pharo＠googlecode.com

Updates: Summary: Registration for PasteUpMorph menu needed Comment #7 on issue 674 by stephane...(a)gmail.com: Registration for PasteUpMorph menu needed http://code.google.com/p/pharo/issues/detail?id=674 (No comment was entered for this change.)

March 12, 2011

Re: [Pharo-project] Issue 3645 in pharo: Update Hudson One-Click build files for 1.2

by pharo＠googlecode.com

Updates: Labels: Type-ToDo Comment #4 on issue 3645 by luc.fabr...(a)gmail.com: Update Hudson One-Click build files for 1.2 http://code.google.com/p/pharo/issues/detail?id=3645 (No comment was entered for this change.)

March 12, 2011