- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Fwd: On the OTDebugger...

by Alexandre Bergel

Ok for me. Cheers, Alexandre On 4 Mar 2009, at 10:30, StÃ©phane Ducasse wrote: > So we should proceed that way: > - Put a big warning + the expression to switch debugger in the pharo- > dev > - then we follow what dale is saying > - I will produce a list of important features we need to have > -- copy stack > -- chase pointer > ... in OT > > Is is ok for your community? > > Stef > > > Begin forwarded message: > >> From: Dale Henrichs <dale.henrichs(a)gemstone.com> >> Date: March 3, 2009 6:57:36 PM CEST >> To: stephane.ducasse(a)inria.fr >> Subject: On the OTDebugger... >> Reply-To: dale.henrichs(a)gemstone.com >> >> Steph, >> >> This note isn't about your 'disable OB-debugger for now message', >> but it is a response, of sorts to the ensuing discussion. >> >> If you want a '120% debugger' then folks working on Pharo need to >> use the debugger and eat their own dogfood. It's the only way to >> ensure that a tool like the debugger gets enough coverage to ensure >> that it is stable. With that said, I wouldn't want to commit to >> using a tool that was broken or that I couldn't depend upon. >> >> With that in mind, I am willing to commit to the following things: >> >> 1. fix any bugs or implement any features that are deemed as show >> stoppers with the current OTDebugger - i.e., the things that are >> preventing folks from getting work done today. >> >> 2. I also promise a quick response to any show stopper bugs that >> folks come across while doing development with the OTDebugger (or >> any other of the OB-Tools). >> >> I came to maintain the OB-Tools through the 'back door'. I use a >> branch the OB-Tools in GLASS and have decided to maintain the OB- >> Tools for the Squeak/Pharo community as a way to contribute back to >> the community. What that means specifically is that next to Lukas, I >> probably know more about the OB-Tools than anyone else, however, I >> don't have a laundry list of features that need to be added to the >> debugger. >> >> I could go through the Squeak debugger and duplicate all of the >> 'missing features', but my personal sense is that some of those >> features aren't useful - I know that I have not even read all of the >> menu items in the old Squeak debugger, let alone tried to figure out >> what they do... >> >> Getting a list of important/missing features from a small group is >> important to me (at least at the start). I don't have a personal >> sense of "what's missing" from the current OTDebugger, since I have >> not used the old Squeak debugger extensively. So getting feedback >> from "old hands" is important, but I also know that I won't be able >> to respond correctly to a general query for "what's missing from the >> debugger?" >> >> For direction towards the "120% debugger", I think it makes sense >> that you and rest of the Pharo leadership team make a list of >> "debugger franchise features" - i.e., a list of features that are a >> must have for the Pharo debugger and the other OB-Tools as well >> (BTW, if that list is to "duplicate all of the 'missing features'" >> then that's fine and I'm willing to do it). >> >> The debugger along with browsers are the face of the development >> environment and I don't want to bloat the debugger without at least >> a second opinion and I trust the opinions of you and the rest of the >> Pharo leadership team. >> >> Thanks, >> >> Dale >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 4, 2009

[Pharo-project] Fwd: On the OTDebugger...

by StÃ©phane Ducasse

So we should proceed that way: - Put a big warning + the expression to switch debugger in the pharo- dev - then we follow what dale is saying - I will produce a list of important features we need to have -- copy stack -- chase pointer ... in OT Is is ok for your community? Stef Begin forwarded message: > From: Dale Henrichs <dale.henrichs(a)gemstone.com> > Date: March 3, 2009 6:57:36 PM CEST > To: stephane.ducasse(a)inria.fr > Subject: On the OTDebugger... > Reply-To: dale.henrichs(a)gemstone.com > > Steph, > > This note isn't about your 'disable OB-debugger for now message', > but it is a response, of sorts to the ensuing discussion. > > If you want a '120% debugger' then folks working on Pharo need to > use the debugger and eat their own dogfood. It's the only way to > ensure that a tool like the debugger gets enough coverage to ensure > that it is stable. With that said, I wouldn't want to commit to > using a tool that was broken or that I couldn't depend upon. > > With that in mind, I am willing to commit to the following things: > > 1. fix any bugs or implement any features that are deemed as show > stoppers with the current OTDebugger - i.e., the things that are > preventing folks from getting work done today. > > 2. I also promise a quick response to any show stopper bugs that > folks come across while doing development with the OTDebugger (or > any other of the OB-Tools). > > I came to maintain the OB-Tools through the 'back door'. I use a > branch the OB-Tools in GLASS and have decided to maintain the OB- > Tools for the Squeak/Pharo community as a way to contribute back to > the community. What that means specifically is that next to Lukas, I > probably know more about the OB-Tools than anyone else, however, I > don't have a laundry list of features that need to be added to the > debugger. > > I could go through the Squeak debugger and duplicate all of the > 'missing features', but my personal sense is that some of those > features aren't useful - I know that I have not even read all of the > menu items in the old Squeak debugger, let alone tried to figure out > what they do... > > Getting a list of important/missing features from a small group is > important to me (at least at the start). I don't have a personal > sense of "what's missing" from the current OTDebugger, since I have > not used the old Squeak debugger extensively. So getting feedback > from "old hands" is important, but I also know that I won't be able > to respond correctly to a general query for "what's missing from the > debugger?" > > For direction towards the "120% debugger", I think it makes sense > that you and rest of the Pharo leadership team make a list of > "debugger franchise features" - i.e., a list of features that are a > must have for the Pharo debugger and the other OB-Tools as well > (BTW, if that list is to "duplicate all of the 'missing features'" > then that's fine and I'm willing to do it). > > The debugger along with browsers are the face of the development > environment and I don't want to bloat the debugger without at least > a second opinion and I trust the opinions of you and the rest of the > Pharo leadership team. > > Thanks, > > Dale >

March 4, 2009

[Pharo-project] New Compiler

by Jorge Ressia

Hi, Marcus Denker and myself will be working on the New Compiler for Pharo. We have a plan draft of the steps that need to be followed in order to get it up and running in Pharo: 1.- Write good tests for each module parse, check, codeGen, execute and check if works. First simple example, and then complex ones. Test recompilation too. 2.- Performance, how long does it take compared to the old compiler. 3.- Error messages: at least like in the old compiler. 4.- Introduce Eliot's Closures. Soon we will have a more detailed and formal list of thing to be done. Cheers, Jorge Ressia

March 4, 2009

Re: [Pharo-project] Unicode test II

by Serge Stinckwich

On Tue, Mar 3, 2009 at 2:11 PM, Michael Rueger <m.rueger(a)acm.org> wrote: > Hi all, > > after some interesting adventures in Unicode land here's a second > version of the unicode test image/app: > > http://impara.de/~michael/unicode-test.zip > > Things that I think should work: > - unicode text input on all platforms including support of composing > character sequences (.eg. US international keyboards) > - unicode clipboard handling > - text editor shortcuts on non Latin1 keyboards (e.g. Russian) (thinking > about it, only tested on Windows so far) It seems to work with a french keyboard on Mac OS X. I try with a vietnamese keyboard but i think i need a vietnamese font. -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Smalltalkers do: [:it | All with: Class, (And love: it)] http://doesnotunderstand.org/

March 4, 2009

Re: [Pharo-project] Preference refactoring again

by Matthew Fulmer

On Tue, Mar 03, 2009 at 06:58:26PM +0100, Alexandre Bergel wrote: > This will probably work and seems reasonable in a general context. > However, for our situation, I feel these are on different levels. > Preferences should be defined and taken into account in Pharo-core, > meaning without Magritte. Hmm. I'd think pharo-core would not have preferences. I was just suggesting it; it seems that once you implement enough to have generic boolean, string, or enumerable preferences, you basically have a watered-down magritte anyway. And who's to say we won't want a generic timezone, email address, or url preference in the future? Magritte can do those without having to rewrite string parsing/verification into every class. -- Matthew Fulmer -- http://mtfulmer.wordpress.com/

March 4, 2009

Re: [Pharo-project] Universes question

by Dale Henrichs

March 4, 2009

Re: [Pharo-project] Unicode test II

by Michael Rueger

Igor Stasenko wrote: > 2009/3/4 Michael Rueger <m.rueger(a)acm.org>: > scanMultiCharactersCombiningFrom: startIndex to: stopIndex in: > sourceString rightX: rightX stopConditions: stops kern: kernDelta > > method near following statement: > (encoding = 0 and: [(stopConditions at: charCode + 1) ~~ nil]) ifTrue: [ hmm, could be that the encoding gets lost somewhere and so allows the code to enter the block. I think we rather need to test for charCode < 256 as the stopConditions are only of that size for any encoding AFAIK. Michael

March 4, 2009

Re: [Pharo-project] Unicode test II

by Igor Stasenko

2009/3/4 Michael Rueger <m.rueger(a)acm.org>: > Igor Stasenko wrote: >> 2009/3/4 Igor Stasenko <siguctua(a)gmail.com>: >>> Michael, i got an in MultiCompositionScanner. >> i mean error... :) >> >>> I can't mail out a bug report, because when doing it, i again get the >>> same error. > > bummer > Hmm, shouldn't there be a SqueakDebug.log file though? > > at least the method in question and a brief description of what you did > would help :-) i changed default font to Arial , to see russian letters while i typing.. then i typed some of them in transcript window.. then i tried to copy/paste text - it works well.. but then at some point it throws me an error subscript out of bounds: 1075 in scanMultiCharactersCombiningFrom: startIndex to: stopIndex in: sourceString rightX: rightX stopConditions: stops kern: kernDelta method near following statement: (encoding = 0 and: [(stopConditions at: charCode + 1) ~~ nil]) ifTrue: [ more precisely (stopConditions at: charCode + 1) okay, i closed debugger, closed transcript, opened a fresh new one, and tried again.. and was unable to reproduce the error. Then i decided to go to preferences and change the freetype hinting options.. once i clicked on it i got the same error. a transcript window contains following chars: ÑÑÐ²ÑÑ Ð²ÑÑ Ð²ÑÑ Ð²ÑÑ Ð¹Ñ ÑÑÐ¾ÑÐ¹Ð²ÑÑÑÐ¾Ð²Ñ Ð¾ÑÐ¾Ð¾ÑÐ¹Ð² Ð¹ÑÐ¾ÑÐ¾ÑÑÑÐ¾Ð²ÑÑÐ²Ð¹ÑÐ¾Ð²ÑÐ¹ÑÐ¾ÑÐ¹ÑÐ¾Ð²ÑÐ²Ð¹ÑÐ¾Ð²ÑÐ¹Ð² > - Show quoted text - > Michael > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

March 4, 2009

Re: [Pharo-project] MIMEdatabase fix?

by Michael Rueger

Giovanni Corriga wrote: > I gave a look at Micheal fix, and have integrated it into > KomHttpServer-gc.45.mcz available in the main KomHttpServer repository ( > http://www.squeaksource.com/KomHttpServer/ ). Still need to be tested > though. Thank you! :-) Michael

March 4, 2009

Re: [Pharo-project] Unicode test II

by Michael Rueger

Igor Stasenko wrote: > 2009/3/4 Igor Stasenko <siguctua(a)gmail.com>: >> Michael, i got an in MultiCompositionScanner. > i mean error... :) > >> I can't mail out a bug report, because when doing it, i again get the >> same error. bummer Hmm, shouldn't there be a SqueakDebug.log file though? at least the method in question and a brief description of what you did would help :-) Michael

March 4, 2009