- Pharo-dev - lists.pharo.org

Pharo 60 need help white-theme-color-for-button-is-not-good

by Stephane Ducasse

https://pharo.fogbugz.com/f/cases/19657/white-theme-color-for-button-is-not… If we compare the selection color for the dark theme, the blue is stronger and much better to see. This is particularly true for class/instance side button, I would be good to have a better white theme with stronger selection colors.

Feb. 6, 2017

Pharo 60 needs help on Broken-syntax-highlithing

by Stephane Ducasse

I'm giving some lectures to siemens engineers and .... we found glitches. (bad impression). https://pharo.fogbugz.com/f/cases/19656/Broken-syntax-highlithing

Feb. 6, 2017

Re: [Pharo-dev] Seamless Error in GT-Inspector

by Sean P. DeNigris

Denis Kudriashov wrote > I fixed it. Thanks! Denis Kudriashov wrote > So old RemoteDebuggingTools project is also work on Pharo 5. > But remember that PharmIDE is only target Pharo 6 or later. No problem. I don't /need/ it to work in Pharo 5, but read that it was working, so I figured I'd let you know about the problem. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Seamless-Error-in-GT-Inspector-tp4933050p4933193.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Feb. 6, 2017

Pharo 60 needs help on shortcuts-are-wrongly-displayed

by Stephane Ducasse

https://pharo.fogbugz.com/f/cases/19660/shortcuts-are-wrongly-displayed The system should display Ctrl + s and not Ctrl + S Because people are pressing Shift to get S and this is not working. We should distinguish between uppercase and lowercase. The reader cannot guess that S is not the same as s + shift. There is no way that a user can know that they should NOT press shift when looking at Ctrl + S (because there is no noshiftPressed). Ctrl + S means press Shift.

Feb. 6, 2017

Pharo 60 need help on Red-in-Dark-Theme-is-plain-bad

by Stephane Ducasse

https://pharo.fogbugz.com/f/cases/19658/Red-in-Dark-Theme-is-plain-bad The black theme is not usable on certain screen because the red color cannot be distinguished. So when the white theme does not work for other reasons people cannot do much. They cannot read the errors. In addition since the hilighter is broken!!! bingo you cannot see anything. Super cool system.

Feb. 6, 2017

Pharo 60 need help on When-coding-in-the-debugger-I-get-an-error-sourceNodeExecuted

by Stephane Ducasse

https://pharo.fogbugz.com/f/cases/19661/When-coding-in-the-debugger-I-get-a… Then I got a really strange problem when I was doing the counter execise using the debugger. create a Test Case TestCase subclass: #CounterTest instanceVariableNames: '' classVariableNames: '' package: 'Counter' - add testValueAtCreation self assert: (Counter new count: 10) count equals: 10 - ok to define classes - define count: in the class Counter - count: anInteger count := anInteger - Declare instance variable count NOW problem Instance of class did not understand count - ok to define it => Instance of IRMethod do not understand sourceNodeExecuted HAnging around instances ========== Then if I remove the Counter class and relaunch the tests I get Instance of anObsoleteCounter did not understandâ¦.

Feb. 6, 2017

Re: [Pharo-dev] Seamless Error in GT-Inspector

by Denis Kudriashov

I fixed it. Now Seamless is compatible with old Pharo (5 at least). Try new stable version. It was just little problem with one method. So old RemoteDebuggingTools project is also work on Pharo 5. But remember that PharmIDE is only target Pharo 6 or later. Thank's for feedback 2017-02-06 16:59 GMT+01:00 Sean P. DeNigris <sean(a)clipperadams.com>: > Denis Kudriashov wrote > > Just check in latest Pharo 6. It works > > Thanks, I was in Pharo 5 > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Seamless-Error-in-GT- > Inspector-tp4933050p4933167.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

Feb. 6, 2017

Re: [Pharo-dev] Pharo 6 update catalog entries

by Sean P. DeNigris

kilon.alios wrote > I see little reason to support individual pharo versions because I focus > always on the latest version. I'm not suggesting that you maintain compatibility ongoingly with various versions, but if you mark compatible versions as such in the catalog, users won't get an unnecessary warning. Either way, thanks for the tool! I happily use it daily :) ----- Cheers, Sean -- View this message in context: http://forum.world.st/Pharo-6-update-catalog-entries-tp4932354p4933169.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Feb. 6, 2017

Re: [Pharo-dev] Seamless Error in GT-Inspector

by Sean P. DeNigris

Denis Kudriashov wrote > Just check in latest Pharo 6. It works Thanks, I was in Pharo 5 ----- Cheers, Sean -- View this message in context: http://forum.world.st/Seamless-Error-in-GT-Inspector-tp4933050p4933167.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Feb. 6, 2017

Re: [Pharo-dev] [QA] quality assurance

by Sean P. DeNigris

Ben Coman wrote > That seems appropriate. > A separate list makes it hard to draw new people in to help. +1 ----- Cheers, Sean -- View this message in context: http://forum.world.st/QA-quality-assurance-tp4933067p4933166.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Feb. 6, 2017