folks, I was wondering (or I have missed the docs) if someone could update HowToContribute on the wiki to include the loose ideas for how to construct and manage wish lists & todos etc? Is the plan that the issue tracker is used as the master todo list? Say #186 contains a list of things to do. If I start working on one should I create a new entry so that I can show progress on it? I like the issue tracker, i'm just not entirely sure how to behave in this pre-coding / organisational phase. HowToContribute assumes pretty much you're ready with your mcz.
cheers, Mike On Mon, Sep 22, 2008 at 9:12 AM, Marcus Denker <[EMAIL PROTECTED]> wrote: > > On 21.09.2008, at 16:22, Janko Mivšek wrote: > >> Hi, >> >> Let me add few my wishes: >> >> - Inspect and Explore merging into just Inspect. By extending Explorer >> with remaining Inspector functionalities like editing objects? >> >> - Inspect always on the same place in menus, not once at the top, then on >> the middle, on the bottom... >> >> - same for senders/implementors >> >> - Integrating Monticello commands directly into code browser, in >> right-click menu over packages. This really helps with code management, I >> know that from VW. >> >> - switch off halos by default, >> >> - multi select by Ctrl-left click or Shift-left click (all other windowing >> systems have multi select, so it is a time to introduce it here too = a big >> plus for newcomers) >> > > Good ideas! I am collecting them for now in this bug-report: > > http://code.google.com/p/pharo/issues/detail?id=186 > > > Marcus > > > -- > Marcus Denker -- [EMAIL PROTECTED] > http://www.iam.unibe.ch/~denker > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
