May 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] FW: [OT] RIS vs. BibTeX

by Damien Pollet

On Thu, May 21, 2009 at 06:07, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > Any thoughts on this? Â Bibus is looking less and less like a short-term solution to my needs, so I'd like to get Citezen loaded and see what it can do. [...] > It was running along fine and then hit a walkback in > > RioLocalExecutive class>>initialize. > > Does not like Current initializeDefault (DNU). That's Rio code. You should look at what's in Current (it's a class variable, so select it in the the class declaration for RioLocalExecutive). It should contain an instance of RioLocalExecutive or one of its subclasses, depending on your OS. If it's nil, then either it was reset somehow, or your platform was incorrectly detected ? To put a correct value back in, I guess you could just doit the two lines that initialize it in RioLocalExecutive class >> performStartupMigration. -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

May 22, 2009

Re: [Pharo-project] can you give feedabck to alain on preference cleaning

by Adrian Lienhard

I also never use the annotations. On May 22, 2009, at 03:05 , Igor Stasenko wrote: > 2009/5/22 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> fun this is the first thing I remove. > the most annoyng for me, that when i use "show all categories" in > method's categories then for currently selected method i can't see to > which category it belongs to. If I need to know this, I do a "Command-shift-c" > Not saying that method's change record information sometimes is > useful as well. For this I browse the versions with "Command-v" Adrian > > >> >> Stef >> >> On May 21, 2009, at 8:55 PM, Igor Stasenko wrote: >> >>> annotation pane is very useful thing. This is first thing i turning >>> on, when start using new image. >>> >>> 2009/5/21 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>>> >>>> http://code.google.com/p/pharo/issues/detail?id=810 >>>> Especially for the annotation panes in the old browser. >>>> >>>> Stef >>>> >>>> _______________________________________________ >>>> 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. >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> >> _______________________________________________ >> 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. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 22, 2009

Re: [Pharo-project] call for hypercool fonts configuration

by Adrian Lienhard

Hm, they look perfect on my machine. I just took a 10310 Pharo core and run the script I posted. Do you have the BitBlt plugin added to the VM? Are the DejaVu fonts blurry as well? Can you post a screenshot? Adrian On May 21, 2009, at 23:30 , StÃ©phane Ducasse wrote: > this is strange because I get a blurry result. > Should I have a specific package loaded: I tried with the 10309dev and > the VM has the FT2plugin > > Stef > > > On May 21, 2009, at 10:50 PM, Adrian Lienhard wrote: > >> On Mac, I like the following "special" configuration with Lucida >> Grande and Monaco: >> >> font := LogicalFont familyName: 'Lucida Grande' pointSize: 10. >> codeFont := LogicalFont familyName: 'Monaco' pointSize: 9. >> codeFont realFont instVarNamed: 'cachedAscent' put: 12. >> codeFont realFont instVarNamed: 'cachedHeight' put: 15. >> titleFont := LogicalFont familyName: 'Lucida Grande' pointSize: 10. >> >> Preferences setListFontTo: font. >> Preferences setMenuFontTo: font. >> Preferences setCodeFontTo: codeFont. >> Preferences setButtonFontTo: font. >> Preferences setSystemFontTo: font. >> Preferences setWindowTitleFontTo: titleFont. >> >> Note, I manually tweak the font description of Monaco to decrease the >> line height (don't know why it is that high by default). With the >> above, it looks more like in TextMate for example. >> >> Adrian >> >> On May 21, 2009, at 10:55 , Hilaire Fernandes wrote: >> >>> Yes, anythinks related to look'nd feel and overal design in Pharo >>> could help a lot to make people to LOVE Pharo or to RUN AWAY. >>> >>> Regarding fonts, I found myself sharing the point previously >>> expressed there: >>> -Dejavu Sans for all but code >>> -Code with Dedavu mono >>> >>> The issue about Freetype efficiency, related to submorph damage code >>> related previsouly, is of equal importance. >>> >>> If the user experience is ungood -- slowness -- people will RUN >>> AWAY. >>> >>> >>> >>> >>> 2009/5/21 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>>> Hi guys >>>> >>>> on one hand we should have a good default for fonts - default means >>>> ok >>>> for license and >>>> work on platforms.... >>>> >>>> Now I would LOVE to get a list of cool combination of fonts even if >>>> they are proprietary. >>>> >>>> So I hope that I woke the designer in you :) >>>> Send snippets in the following forms that we can impress girls :) >>>> >>>> >>>> font := LogicalFont familyName: 'DejaVu Sans' pointSize: 10. >>>> codeFont := LogicalFont familyName: 'DejaVu Sans Mono' pointSize: >>>> 9. >>>> titleFont := LogicalFont familyName: 'DejaVu Serif' pointSize: 11. >>>> >>>> Preferences setListFontTo: font. >>>> Preferences setMenuFontTo: font. >>>> Preferences setCodeFontTo: codeFont. >>>> Preferences setButtonFontTo: font. >>>> Preferences setSystemFontTo: font. >>>> Preferences setWindowTitleFontTo: titleFont. >>>> >>>> >>>> Stef >>>> >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >>> >>> >>> -- >>> http://blog.ofset.org/hilaire >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 22, 2009

Re: [Pharo-project] can you give feedabck to alain on preference cleaning

by Alain Plantec

Igor Stasenko a Ã©crit : > annotation pane is very useful thing. This is first thing i turning > on, when start using new image. > Hi Igor, how do you makes it work on old browser. It is never updated. However, It is well implemented by OB, and works very well with it. So the question is can I remove it from old browser (from the core). We can keep OB implementation and introduce an OB specific setting for it. Regarding the old browser, It is very badly implemented and introduces very dirty dependences. See pieces of code below. We hare removing etoy or bookmorph for the same reasons. CodeHolder>>refreshAnnotation "If the receiver has an annotation pane that does not bear unaccepted edits, refresh it" (aPane := self dependents detect: [:m | (m inheritsFromAnyIn: #('PluggableTextView' 'PluggableTextMorph' )) and: [m getTextSelector == #annotation]] ifNone: []) ifNotNil: [:aPane | aPane hasUnacceptedEdits ifFalse: [aPane update: #annotation]] other "cool" pieces of code: PluggableTextMorph>>accept .... ok := self acceptTextInModel. ok == true ifTrue: [self setText: self getText. self hasUnacceptedEdits: false. (model dependents detect: [:dep | (dep isKindOf: PluggableTextMorph) and: [dep getTextSelector == #annotation]] ifNone: []) ifNotNilDo: [:aPane | model changed: #annotation]]. ... PluggableTextMorph>>cancel self setText: self getText. self setSelection: self getSelection. getTextSelector == #annotation ifFalse: [(aPane := model dependents detect: [:dep | (dep isKindOf: PluggableTextMorph) and: [dep getTextSelector == #annotation]] ifNone: []) ifNotNil: [:aPane | model changed: #annotation]] Cheers Alain > 2009/5/21 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > >> http://code.google.com/p/pharo/issues/detail?id=810 >> Especially for the annotation panes in the old browser. >> >> Stef >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> > > > >

May 22, 2009

Re: [Pharo-project] call for hypercool fonts configuration

by Benjamin Pollack

On Thu, May 21, 2009 at 5:30 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > this is strange because I get a blurry result. > Should I have a specific package loaded: I tried with the 10309dev and > the VM has the FT2plugin > > Stef > This is actually confusing me, too. My favorite coding font by far is Consolas, a proprietary Microsoft font that ships with Vista and newer versions of Office. (Hey, give me a break; once every 30 years, they're allowed to get something right.) I therefore gave the following configuration a shot: font := LogicalFont familyName: 'Lucida Grande' pointSize: 10. codeFont := LogicalFont familyName: 'Consolas' pointSize: 9. titleFont := LogicalFont familyName: 'Lucida Grande' pointSize: 11. Preferences setListFontTo: font. Preferences setMenuFontTo: font. Preferences setCodeFontTo: codeFont. Preferences setButtonFontTo: font. Preferences setSystemFontTo: font. Preferences setWindowTitleFontTo: titleFont. Unfortunately, under Pharo, the result's so bad, I feel as if I'm trying to code through beer goggles. The Lucida Grande looks fine, but the Consolas looks as if it has been heavily smeared. Oddly, the problem mostly goes away if I change Consolas' size to 8 points, rather than 9. To me, without any knowledge of what Pharo does for fonts, that screams that the FreeType plugin is built without the bytecode interpreter. If so, I think it can safely be enabled on both OS X and Windows, since the patent holders are Apple and Microsoft. --Benjamin

May 22, 2009

Re: [Pharo-project] Port of Cryptography to Pharo

by Schwab,Wilhelm K

The most recent post on the crytography mailing list starts out as follows: Since the Cryptography Team doesn't exists anymore, the Cryptography package is not maintained by anyone. The SSL implementation doesn't allow easy debugging, you can't just turn on logging to see what's happening. Following the state machine transitions should give you the answer why the handshake isn't succeding. It might be related to certificates or TLS->SSL3 fallback. If I were you, I would go with curl. I think it is time to write a wrapper around open SSL in addition to looking at the curl plugin. Trying to write cryptography code from scratch and get and keep it right is a huge effort, and pretty avoidable, and IMHO, better avoided by letting others do the job. Ever read Sun Tzu? Bill ________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Mariano Martinez Peck Sent: Thursday, May 21, 2009 8:51 PM To: Pharo Development Subject: [Pharo-project] Port of Cryptography to Pharo I don't know if there is anyone of the developers of the package Cryptography but is someone is willing to do the port of it to Pharo? Most tests are break and it seems not to work because lots of Cryptography methods where in classes like SmallInteger and these methods were removed in Pharo. Regards, Mariano

May 22, 2009

Re: [Pharo-project] ThirtyTwoBitRegister methods removed

by Mariano Martinez Peck

Just forget this topic. These methods actually are needed by the Cryptography package. Glorp port to Squeak only can be used with Postgres. So, I was doing the test with the native postgres driver. But, if you have configured your postgres database with MD5 (as I have), the package Cryptography is needed. I will configure my postgres without md5. When someone has time and do a port of Cryptography I can go on with this. Sorry for the noise. Mariano On Thu, May 21, 2009 at 2:19 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > > On May 21, 2009, at 3:10 PM, Mariano Martinez Peck wrote: > > > > > > > On Thu, May 21, 2009 at 6:51 AM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr > > > wrote: > > If you need them for glorp copy them from Squeak and publish a new > > package version working for Glorp in PharoInbox > > I will push it in pharo > > > > Ok, I will do that. I am trying to see how the fax the license signed. > > > > However, it is not that I NEED it for Glorp. I mean, I can put it in > > Glorp as an method extension with *Glorp and will work. But for me, > > these two methods are ok to be in Pharo. > > sounds like so push them > > > > > > > Cheers, > > > > Mariano > > > > > > On May 21, 2009, at 3:07 AM, Mariano Martinez Peck wrote: > > > > > I searched in Monticello for the package System-Digital Signatures > > > and in the Pharo repository I only see two commits and even in the > > > first one, these two methods are not there. But, they are in Squeak. > > > So, know I guess where this commit should be? where I can search ? > > > > > > Thanks! > > > > > > Mariano > > > > > > On Mon, May 18, 2009 at 9:27 PM, Mariano Martinez Peck < > marianopeck(a)gmail.com > > > > wrote: > > > Hi folks. I noticed that this two methods were removed from > > > ThirtyTwoBitRegister: > > > > > > asByteArray > > > ^ ByteArray with: (low bitAnd: 16rFF) with: (low bitShift: > > > -8) with: (hi bitAnd: 16rFF) with: (hi bitShift: -8) > > > > > > > > > > > > reverseLoadFrom: aByteArray at: index > > > "Load my 32-bit value from the four bytes of the given > > > ByteArraystarting at the given index. Consider the first byte to > > > contain the mostsignificant bits of the word (i.e., use big-endian > > > byte ordering)." > > > > > > hi := ((aByteArray at: index + 3) bitShift: 8) + > > > ( aByteArray at: index + 2). > > > low := ((aByteArray at: index + 1) bitShift: 8) + > > > ( aByteArray at: index). > > > > > > > > > > > > I need them for Glorp. I looked but I didn't found a similar message > > > for them. I don't think adding them as an extension is a good > > > solution here since this seems to be very "internal". is there a > > > reason of the removing? If not, could them be added again? If there > > > are reason, which should be the best approach to fix this in mi > > case? > > > > > > I have no problem in commit them if you want. > > > > > > Thanks! > > > > > > Mariano > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > Pharo-project mailing list > > > Pharo-project(a)lists.gforge.inria.fr > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 22, 2009

[Pharo-project] Port of Cryptography to Pharo

by Mariano Martinez Peck

I don't know if there is anyone of the developers of the package Cryptography but is someone is willing to do the port of it to Pharo? Most tests are break and it seems not to work because lots of Cryptography methods where in classes like SmallInteger and these methods were removed in Pharo. Regards, Mariano

May 22, 2009

Re: [Pharo-project] can you give feedabck to alain on preference cleaning

by Igor Stasenko

2009/5/22 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > fun this is the first thing I remove. the most annoyng for me, that when i use "show all categories" in method's categories then for currently selected method i can't see to which category it belongs to. Not saying that method's change record information sometimes is useful as well. > > Stef > > On May 21, 2009, at 8:55 PM, Igor Stasenko wrote: > >> annotation pane is very useful thing. This is first thing i turning >> on, when start using new image. >> >> 2009/5/21 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>> >>> http://code.google.com/p/pharo/issues/detail?id=810 >>> Especially for the annotation panes in the old browser. >>> >>> Stef >>> >>> _______________________________________________ >>> 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. >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > 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.

May 22, 2009

Re: [Pharo-project] call for hypercool fonts configuration

by StÃ©phane Ducasse

this is strange because I get a blurry result. Should I have a specific package loaded: I tried with the 10309dev and the VM has the FT2plugin Stef On May 21, 2009, at 10:50 PM, Adrian Lienhard wrote: > On Mac, I like the following "special" configuration with Lucida > Grande and Monaco: > > font := LogicalFont familyName: 'Lucida Grande' pointSize: 10. > codeFont := LogicalFont familyName: 'Monaco' pointSize: 9. > codeFont realFont instVarNamed: 'cachedAscent' put: 12. > codeFont realFont instVarNamed: 'cachedHeight' put: 15. > titleFont := LogicalFont familyName: 'Lucida Grande' pointSize: 10. > > Preferences setListFontTo: font. > Preferences setMenuFontTo: font. > Preferences setCodeFontTo: codeFont. > Preferences setButtonFontTo: font. > Preferences setSystemFontTo: font. > Preferences setWindowTitleFontTo: titleFont. > > Note, I manually tweak the font description of Monaco to decrease the > line height (don't know why it is that high by default). With the > above, it looks more like in TextMate for example. > > Adrian > > On May 21, 2009, at 10:55 , Hilaire Fernandes wrote: > >> Yes, anythinks related to look'nd feel and overal design in Pharo >> could help a lot to make people to LOVE Pharo or to RUN AWAY. >> >> Regarding fonts, I found myself sharing the point previously >> expressed there: >> -Dejavu Sans for all but code >> -Code with Dedavu mono >> >> The issue about Freetype efficiency, related to submorph damage code >> related previsouly, is of equal importance. >> >> If the user experience is ungood -- slowness -- people will RUN AWAY. >> >> >> >> >> 2009/5/21 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>> Hi guys >>> >>> on one hand we should have a good default for fonts - default means >>> ok >>> for license and >>> work on platforms.... >>> >>> Now I would LOVE to get a list of cool combination of fonts even if >>> they are proprietary. >>> >>> So I hope that I woke the designer in you :) >>> Send snippets in the following forms that we can impress girls :) >>> >>> >>> font := LogicalFont familyName: 'DejaVu Sans' pointSize: 10. >>> codeFont := LogicalFont familyName: 'DejaVu Sans Mono' pointSize: 9. >>> titleFont := LogicalFont familyName: 'DejaVu Serif' pointSize: 11. >>> >>> Preferences setListFontTo: font. >>> Preferences setMenuFontTo: font. >>> Preferences setCodeFontTo: codeFont. >>> Preferences setButtonFontTo: font. >>> Preferences setSystemFontTo: font. >>> Preferences setWindowTitleFontTo: titleFont. >>> >>> >>> Stef >>> >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> >> >> -- >> http://blog.ofset.org/hilaire >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 21, 2009