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

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

Re: [Pharo-project] Issue 3777 in pharo: Bring back Mocketry

by pharo＠googlecode.com

Updates: Status: Closed Comment #2 on issue 3777 by stephane...(a)gmail.com: Bring back Mocketry http://code.google.com/p/pharo/issues/detail?id=3777 (No comment was entered for this change.)

March 12, 2011

Re: [Pharo-project] Issue 3777 in pharo: Bring back Mocketry

by pharo＠googlecode.com

Updates: Status: Closd Comment #1 on issue 3777 by stephane...(a)gmail.com: Bring back Mocketry http://code.google.com/p/pharo/issues/detail?id=3777 (No comment was entered for this change.)

March 12, 2011

Re: [Pharo-project] Issue 3469 in pharo: [Failing Test] ShoutTests.Parsing.SHParserST80Test.testCollectionHierarchy

by pharo＠googlecode.com

Updates: Status: Closed Labels: -Milestone-1.1.2-DevImage Milestone-1.2-DevImage Comment #13 on issue 3469 by stephane...(a)gmail.com: [Failing Test] ShoutTests.Parsing.SHParserST80Test.testCollectionHierarchy http://code.google.com/p/pharo/issues/detail?id=3469 (No comment was entered for this change.)

March 12, 2011

Re: [Pharo-project] [ANN] Cog issue tracker

by Tudor Girba

+1 Just to clarify: The issue tracker was created after a discussion with Elliot this week, in which he asked us to help him create a Google Code for issues related to Cog so that people can participate. Cheers, Doru On 11 Mar 2011, at 00:46, Igor Stasenko wrote: > Hello everyone. > > Without much debate we just created it at [1]. Now there is a separate > place for filing issues for Cog VM. > I think Cog deserves separate issue tracker, because currently all > reports and problems are mainly buried in vm-dev mailing list, > and it is hard to tell what is status of one or another issue, which > we lately discovered. And such approach definitely won't scale. > So, it was a main reason for making this move. > > Lets help Eliot (and others who involved in development) make > activities to be more organized and visible. > > I'd like to stress that there is nothing inside code.google in > particular, which could make its issue tracker serve our needs well. > It will work well only if we, as community, organize ourselves and pay > attention to collect and put important information there, > make it easily accessible, structured and so on.. > > > > [1] http://code.google.com/p/cog/ > > > > -- > Best regards, > Igor Stasenko AKA sig. > -- www.tudorgirba.com "Every thing should have the right to be different."

March 12, 2011