Hi Sean, Thanks a lot for the valuable feedback!
On Apr 9, 2010, at 05:57 , Sean P. DeNigris wrote: > > I love the clean look with all the great developer features pre-installed > (shout, OCompletion, etc.). It's been a pleasure to work with. > > And, a few things stood out that didn't seem to work as well. I'm sharing > them here because I wonder what your opinions are. Also, what is the policy > about contributing "good ideas" i.e. new/altered features that are not bug > fixes? Is it best to discuss them on the list like this, or submit a > changeset right off the bat per > http://code.google.com/p/pharo/wiki/HowToContribute? Normally I would do both. If you have code, commit it and create a ticket (not only for bugs but also for features). Then announce it in the mailing list. Since many people are busy, sometimes you don't get a response immediately, especially if it requires somebody loading the code and trying it out. In this case just send a reminder and explicitly ask people for feedback. For the list of suggestions you gave, you may want to wait for other feedback and then create single issues in the tracker for those that other people feel should be changed. Cheers, Adrian [...] _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
