Issue 6144 in pharo: Port 2.0 bug fixes to 1.4 for summer release

Status: Accepted
Owner: [hidden email]
Labels: Type-Bug Milestone-1.4

New issue 6144 by [hidden email]: Port 2.0 bug fixes to 1.4 for  
summer release
http://code.google.com/p/pharo/issues/detail?id=6144

Make a list of integrated fixes to 2.0 [1] that conform to these guidelines  
[2]:
   - No new features.
   - No cleanups
   - If a bug was there in Pharo 1.1 already and we lived with it for years,  
fixing it in the current dev version is (in many cases) enough. (There are  
exceptions, but is does not happen often).

[1]  
http://code.google.com/p/pharo/issues/list?can=1&q=status%3AIntegrated+Milestone%3D2.0+Type%3DBug
[2] http://forum.world.st/Backporting-fixes-tp4633625p4633635.html


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #1 on issue 6144 by [hidden email]: Port 2.0 bug fixes to  
1.4 for summer release
http://code.google.com/p/pharo/issues/detail?id=6144

Issue 6135: Code completion in all tools
http://code.google.com/p/pharo/issues/detail?id=6135

Fix in inbox: SLICE-Issue-6135-Code-completion-in-all-tools-SeanDeNigris.4

* Add code completion to Inspector and ObjectExplorer
* Syntax highlighting
        - Add to ObjectExplorer
        - Fix for Inspector


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #2 on issue 6144 by [hidden email]: Port 2.0 bug fixes to  
1.4 for summer release
http://code.google.com/p/pharo/issues/detail?id=6144

Issue 6083: Mouse down events are being processed twice
http://code.google.com/p/pharo/issues/detail?id=6083

Morph>>#handleMouseDown: is calling #mouseDown:, which calls  
#mouseDown:fromMorph:, and then calling #mouseDown:fromMorph: explicitly

Fix in inbox:
   - for 1.4:  
SLICE-Issue-6083-Mouse-down-events-are-being-processed-twice-SeanDeNigris.1

* Fix Morph>>#handleMouseDown: to have #mouseDown:fromMorph: called only  
once, via #mouseDown:


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #3 on issue 6144 by [hidden email]: Port 2.0 bug fixes to  
1.4 for summer release
http://code.google.com/p/pharo/issues/detail?id=6144

Port to Pharo 1.4 the fix for "Issue 5818: Put back the correct order in  
#asert:equals:", which was actually integrated in "Issue 6069: Test guard  
for 20132" (don't know how the original change got lost)

Fix in inbox:  
SLICE-Issue-6144-Port-Fix-5818-to-14-Put-back-the-correct-order-in-asertequals-SeanDeNigris.1

* Fix the order of #assert:equals:
* Add Mariano's test, which now passes


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #4 on issue 6144 by [hidden email]: Port 2.0 bug fixes to  
1.4 for summer release
http://code.google.com/p/pharo/issues/detail?id=6144

Port to Pharo 1.4 the fix for "Issue 5800: stdin hangs until EOF"

Fix in inbox:  
SLICE-Issue-6144-Port-Fix-5800-to-14-stdin-hangs-until-EOF-SeanDeNigris.1

Changes:
* disable read buffering on stdin, to avoid hanging image when reading


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #5 on issue 6144 by [hidden email]: Port 2.0 bug fixes to  
1.4 for summer release
http://code.google.com/p/pharo/issues/detail?id=6144

The rest will be separate issues tagged 1.4. I think it will be easier to  
manage.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #6 on issue 6144 by [hidden email]: Port 2.0 bug fixes to  
1.4 for summer release
http://code.google.com/p/pharo/issues/detail?id=6144

I removed the issues from the comments here because it was getting two  
confusing. There are now separate issues for each tagged 1.4.

Here's a link to the list of 1.4 bugs with fixes:  
http://code.google.com/p/pharo/issues/list?can=2&q=Milestone%3D1.4+is%3Aopen+Type%3DBug+status%3AFixReviewNeeded%2CFixToInclude


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: Closed

Comment #7 on issue 6144 by [hidden email]: Port 2.0 bug fixes to  
1.4 for summer release
http://code.google.com/p/pharo/issues/detail?id=6144

yes, one  issue per thing to do is the way to go.

Issue entries need to be actionable


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker