- Pharo-dev - lists.pharo.org

Re: [Pharo-project] OB 10231: search bar does not work

by David RÃ¶thlisberger

> Using the latest pharo dev 10231dev09.02.1, I cant use the search bar > anymore. I got a OBEnhancementMetaNode(Object)>>doesNotUnderstand: #fan: > > Latest I check (10211), it works. Is it a known bug? yeah, I'm aware of that one and will fix it soon. David

Feb. 11, 2009

Re: [Pharo-project] Workspace API

by Keith Hodges

StÃ©phane Ducasse wrote: > Where? When? > Keith > in the long run it would be nice that yu do not bash us systematically. > Yes we have a different way of working but normally this is often by > pure lack of time or information > that we do not check what exist. > > Stef > I was concerned to find code in Pier that did not seem to be compatible with squeak, while I thought that the Workspace issue had come up before. Your different way of working..... as I see it: You want more tests, you develop more tests, you add more tests to the image. Are those tests useful to the rest of the squeak community? No. Should they be? YES. If there was a way of marking those tests that are pharo only tests, as such, and also marking those tests that should work in squeak. Then the squeak/pharo communities could use one testing package for all squeak images, and pharo. So to enable this to happen you need to think about testing in a broader sense and you need improved tools to handle it, and you need to develop or assess those tools FIRST. hmm, so August 2006, I thought this through, that to support diversity in the squeak community we needed something like that, and SUnit-improved was the result. That was its purpose, to support forks of squeak, I believe in forking squeak.... All the tools I have worked on for 2 years are to enable working with diverse images, and to facilitate packages to work in different images. Thus reducing the dependency upon a specific kernel-image and thus releasing the kernel-image to be improved. What I don't believe in was the pharo approach of going your own way WITHOUT considering anyone else, to the extent that you ignore all of the extensive work that has been carried out to provide tools that would enable you to participate. The main goal of the 3.11 effort hasn't been a particular image, but a tool set, and a process, that would enable folks to work on diverse projects, while considering each other. And you are ignoring those tools, because you dont see them as important. I cant work out why you dont see them as important is because you have sucessfully harnessed a lot of enthusiasm for improving squeak. YET you dont have a process for using that enthusiam effectively. You still have the same old bottlenecked controlled process where there is no actual plan (you do what you feel like when you get up in the morning), and two people get to hack at the image day and night and everyone else is contributing to a moving target. regards Keith

Feb. 11, 2009

Re: [Pharo-project] Workspace API

by Keith Hodges

Alexandre Bergel wrote: > I was wondering, how many people saved their workspace content in a > file? > > Cheers, > Alexandre > MC1.5 supports files so if you want to manage scripts and readmes having a workspace that knows its file, is a good idea. Also Bob wants a way to (optionally) show you the script that it used to build the image. http://bugs.squeak.org/view.php?id=5669 Keith

Feb. 11, 2009

Re: [Pharo-project] LogicalFont deepCopy infinite loop with Arial font

by Gary Chambers

Good luck! Regards, Gary ----- Original Message ----- From: "Alain Plantec" <alain.plantec(a)free.fr> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Wednesday, February 11, 2009 5:02 PM Subject: Re: [Pharo-project] LogicalFont deepCopy infinite loop with Arial font Gary Chambers a Ã©crit : > Saved preferences seems broken in other ways... it seems to lead to > odd obsoletions of the PBPreferenceView subclasses... probably due to > the deepcopy. I'm not sure deep copying is really wanted here, there's > probably a better way. ok, I will try to repare and improve it. alain > > Regards, Gary > > ----- Original Message ----- From: "Alain Plantec" > <alain.plantec(a)free.fr> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Wednesday, February 11, 2009 3:22 PM > Subject: [Pharo-project] LogicalFont deepCopy infinite loop with Arial > font > > >> Hi all, >> I would like to improve the PreferencesBrowser so that it includes >> standard Fonts preferences (see joined snapshot). >> It's almost done except that, if a preference font is set to Arial, >> clicking on Save button leads to an infinite loop. >> >> To reproduce it, set button font to Arial-12 and >> Preferences standardButtonFont deepCopy. >> >> Cheers >> alain >> > > > -------------------------------------------------------------------------------- > > > >> _______________________________________________ >> 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

Feb. 11, 2009

Re: [Pharo-project] Workspace API

by Gary Chambers

Around the same... usually when I rebuild my image. Loading from file happens more often (preference and appearance settings mostly). Regards, Gary ----- Original Message ----- From: Chris Cunningham To: Pharo-project(a)lists.gforge.inria.fr Sent: Wednesday, February 11, 2009 4:41 PM Subject: Re: [Pharo-project] Workspace API I average about once a year (saving contents to a file). However, I regularly open a workspace on strings. ------------------------------------------------------------------------------ _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Feb. 11, 2009

Re: [Pharo-project] LogicalFont deepCopy infinite loop with Arial font

by Alain Plantec

Gary Chambers a Ã©crit : > Saved preferences seems broken in other ways... it seems to lead to > odd obsoletions of the PBPreferenceView subclasses... probably due to > the deepcopy. I'm not sure deep copying is really wanted here, there's > probably a better way. ok, I will try to repare and improve it. alain > > Regards, Gary > > ----- Original Message ----- From: "Alain Plantec" > <alain.plantec(a)free.fr> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Wednesday, February 11, 2009 3:22 PM > Subject: [Pharo-project] LogicalFont deepCopy infinite loop with Arial > font > > >> Hi all, >> I would like to improve the PreferencesBrowser so that it includes >> standard Fonts preferences (see joined snapshot). >> It's almost done except that, if a preference font is set to Arial, >> clicking on Save button leads to an infinite loop. >> >> To reproduce it, set button font to Arial-12 and >> Preferences standardButtonFont deepCopy. >> >> Cheers >> alain >> > > > -------------------------------------------------------------------------------- > > > >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > >

Feb. 11, 2009

Re: [Pharo-project] Call for UI gripes

by Gary Chambers

The next version (Polymorph-Widgets-gvc.45) will support adaptive layout insets for buttons in the Watery2 theme dependent upon the corners that are rounded. For square buttons this will save 8 pixels horizontally per button. I'll put on SqueakSource once enough other changes are made to Polymorph to justify the effort of releasing ;-) Regards, Gary >> >> Space to sides of the buttons?? Perhaps unrelated, but I have been >> thinking of something similar while poking at Damien's recent dev image. >> > > Because Watery2 has more-rounded-than-usual buttons some extra space is > required to avoid the text/morph apearing outside the button image. >

Feb. 11, 2009

Re: [Pharo-project] looking for Unicode testers

by John M McIntosh

No, it's just more smalltalk coding, the utf8-plain-text bytes need to be translated into bytes according to "Normalizes the string into the specified form as described in Unicode Technical Report #15." and ensure we return the bytes as UTF8. The FFI calls let the macintosh operating system deal with the messy details. http://unicode.org/unicode/standard/reports/tr15/tr15-18.html also see http://developer.apple.com/qa/qa2001/qa1235.html Say is that a precomposed and decomposed Unicode you have there, really what does squeak want? want does the operating system want. Choices choices. PS beware the utf8 to macroman or macroman to utf8 text converts in squeak, I don't think the one that came from etoys does the right thing can't remember, it's named wrong, does utf8 to ascii or something... On 11-Feb-09, at 7:29 AM, Michael Rueger wrote: > Michael Rueger wrote: > >>> Well that *is* the extended clipboard support. Just need the >>> smalltalk code to make the proper primitive calls to the extended >>> clipboard plugin. >>> You need the ClipboardExtendedPlugin.bundle > > Hmm, you still need FFI despite the plugin: > > readUTF8StringClipboardData > | bytes | > "utf8" > > bytes := self readClipboardData: 'public.utf8-plain-text'. > bytes := MacCFString callMakeUTF8NormalizedStringViaByteString: > bytes asString. > ^bytes ifNil: [bytes] ifNotNil: > [bytes asString convertFromWithConverter: (UTF8TextConverter new)] > > > > Michael -- = = = ======================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================

Feb. 11, 2009

Re: [Pharo-project] Workspace API

by Chris Cunningham

I average about once a year (saving contents to a file). However, I regularly open a workspace on strings.

Feb. 11, 2009

Re: [Pharo-project] looking for Unicode testers

by John M McIntosh

On 11-Feb-09, at 6:39 AM, Michael Rueger wrote: > > alt/ctrl > so if you hit alt-c (apple-c) slot six is nil Well you have 3 different events that occur on tapping that key(s) This follows the rules set by the windows VM. on the down stroke, we give you EventTypeKeyboard->EventKeyDown, the macintosh keycode (some virtual magic number), and zero for the unicode value After the operating system determines what that plastic or rubber key was, we send EventTypeKeyboard-> EventKeyChar, the macintosh macRoman character (if possible, may be zero), and the unicode value Once the key is released, we send EventTypeKeyboard> EventKeyUp , the macintosh keycode (some virtual magic number), and zero for the unicode value If the key is held down it repeats, and according to windows rules it doesn't send the keyup (I believe check the archives), just key down, key char I had offered to return the unicode value for keydown/keyup but was told it was too hard for the windows VM to provide that data at the point where key down/up occurs http://lists.squeakfoundation.org/pipermail/squeak-dev/2003-December/071701… As you know some flavours of the Squeak UI look for character input on keyChar or keyUp... So is this on key up/down or key char? > > >>> Oh, I thought the new Mac VMs supported Unicode in the clipboard >>> logic as the other VMs now do. >>> How much effort would that be to add UTF-x support to the current >>> clipboard logic? >> Well that *is* the extended clipboard support. Just need the >> smalltalk code to make the proper primitive calls to the extended >> clipboard plugin. >> You need the ClipboardExtendedPlugin.bundle > > OK, will do for now. > Guess in future versions we should remove the clipboard support from > the core VM and replace it by the (extended) clipboard plugin. > > Michael > -- = = = ======================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================

Feb. 11, 2009