Yes, the issues Andrea reported are all from 1.2.2. That's the version we are currently using besides 1.1.2.
Unfortunately, its not an option for us to move to new versions of Pharo too frequently. New Pharo versions can have unforeseen effects in production and hence can cause a lot of work for us and pain for our users (just an example is the semantic change of String>>asNumber). On the other hand, we are working 8 hours a day with Pharo and hence a good IDE is very important. If things like the debugger do not reliably work, this is not fun. Are other people just living with the issues? Are there any patches that could be backported? Cheers, Adrian On Aug 23, 2011, at 10:54 , Alexandre Bergel wrote: > These issues are for 1.2.2. Who is maintaining it by the way? > > Pharo 1.4 presents a significant number of improvements over Pharo 1.3. > Whereas I found Pharo 1.3 almost unusable, I am quite happy with 1.4 > > Cheers, > Alexandre > > > On 23 Aug 2011, at 08:54, Andrea Brühlmann wrote: > >> Hello, >> >> I reported some bugs on the issue tracker and hope you can help me with them! >> >> >> 4681: Accepting with the enter key does not work >> http://code.google.com/p/pharo/issues/detail?id=4681 >> >> 4682: Code completion makes strange cursor placements and too many spaces >> http://code.google.com/p/pharo/issues/detail?id=4682 >> >> 4683: Code completion breaks some search fields (errors during typing) >> http://code.google.com/p/pharo/issues/detail?id=4683 >> >> 4684: Missing ctrl+w (methodNamesContainingIt:) >> http://code.google.com/p/pharo/issues/detail?id=4684 >> >> 4685: Merge dialog: cannot resolve conflict with removed method >> http://code.google.com/p/pharo/issues/detail?id=4685 >> >> 4686: Method category change creates no new version >> http://code.google.com/p/pharo/issues/detail?id=4686 >> >> 4687: Errors during coding (MessageNotUnderstood: receiver of "morph" is nil) >> http://code.google.com/p/pharo/issues/detail?id=4687 >> >> 4688: Progress bar disappears on image save >> http://code.google.com/p/pharo/issues/detail?id=4688 >> >> 4689: MessageTally bug >> http://code.google.com/p/pharo/issues/detail?id=4689 >> >> 4690: Progress bar position >> http://code.google.com/p/pharo/issues/detail?id=4690 >> >> 4691: Bad line breaks in code until window is resized (because of bold text?) >> http://code.google.com/p/pharo/issues/detail?id=4691 >> >> 4692: Drop downs should select the default entry (topmost) instead of a >> middle one >> http://code.google.com/p/pharo/issues/detail?id=4692 >> >> 4693: Line breaks in tooltips are wrong >> http://code.google.com/p/pharo/issues/detail?id=4693 >> >> 4694: Debugger: stepping over an error can not open a new debugger until I >> hit cmd+. >> http://code.google.com/p/pharo/issues/detail?id=4694 >> >> 4695: Time asString prints nanos unrounded >> http://code.google.com/p/pharo/issues/detail?id=4695 >> >> >> -- >> Andrea Brühlmann >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > >
