- Pharo-dev - lists.pharo.org

[Pharo-project] Fwd: preferences to settings refactoring: #colorWhenPrettyPrinting case
by StÃ©phane Ducasse June 1, 2009

June 1, 2009

>> StÃ©phane Ducasse a Ã©crit : >>> alain >>> >> This slice removes the preference from the core, so it has nothing >> to do with Shout. >> As noticed in the issue comment, because colorWhenPrettyPretting >> has already no effect when set this slice consists more in a clean- >> up. >>> do you always color? >> so, never in core >>> or do you rely on shout? >> and color in pharo (aka pharo-dev) relies on shout as always. > > ok this is what I wanted to know. > > Stef >> >> >> alain >>> >>> Stef >>> >>> On May 29, 2009, at 9:39 AM, Alain Plantec wrote: >>> >>>> Hi, >>>> A slice is upload in pharoInbox. >>>> Cheers >>>> Alain >>>> >>>> Name: SLICE-colorWhenPrettyPrintingRemoval-alain_plantec.2 >>>> Dependencies: Compiler-alain_plantec.104, >>>> Kernel-alain_plantec.renggli.335, KernelTests-alain_plantec.109, >>>> Polymorph-Tools-Diff-alain_plantec.21, >>>> System-FilePackage-alain_plantec.6, System-Support-alain_plantec. >>>> 27, >>>> Tools-alain_plantec.154, Traits-alain_plantec.279 >>>> >>>> Remove the #colorWhenPrettyPrinting preference. >>>> As a consequence, some code formatting methods are refactored >>>> (The major remodelling is the >>>> Compiler>>#format:in:notifying:decorated: >>>> removal, replaced by Compiler>>#format:in:notifying:) >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >>> >>> >> >> > > > >

4 6

[Pharo-project] Problem with keyboard shortcuts
by Mariano Martinez Peck June 1, 2009

June 1, 2009

Hi folks. I am facing problems with keyboard shortcuts in Windows. "Inspect" and "explore" shortcuts seem to be wrong. Look at this example: 1) With this: Preferences enable: #swapControlAndAltKeys. Preferences enable: #swapCOntrolAndAltKeys. Preferences disable: #duplicateAllControlAndAltKeys. Preferences disable: #duplicateControlAndAltKeys. I get this results: browse -> alt + b inspect -> alt + i print -> alt + p explore -> ctrl + i 2) With this: Preferences disable: #swapControlAndAltKeys. Preferences disable: #swapCOntrolAndAltKeys. Preferences disable: #duplicateAllControlAndAltKeys. Preferences disable: #duplicateControlAndAltKeys. I get this results: browse -> alt + b inspect -> alt + i print -> alt + p explore -> ctrl + i 3) With this: Preferences disable: #swapControlAndAltKeys. Preferences disable: #swapCOntrolAndAltKeys. Preferences enable: #duplicateAllControlAndAltKeys. Preferences disable: #duplicateControlAndAltKeys. I get this results: browse -> ctrl + b inspect -> alt + i print -> ctrl + p explore -> ctrl + shift + i Conclusions: 1) We have TWO preferences for the same purpose: swapControlAndAltKeys and swapCOntrolAndAltKeys. I think only has to be swapControlAndAltKeys. 2) Enabling or disabling swapControlAndAltKeys has no effect. 3) When duplicateAllControlAndAltKeys "inspect" should be ctrl + i but it is alt + i. In addition, is ok explore to be ctre + shift + i ? 4) If I don't enable duplicateAllControlAndAltKeys world menu is wrong because it says the shortcut is (I) when it actually is (i). It is only (I) if you have enable duplicateAllControlAndAltKeys. Some time ago, I created the ticket http://code.google.com/p/pharo/issues/detail?id=829 But now it seems to be a bit bigger than that. I can create another ticket if needed. Best, Mariano

1 0

[Pharo-project] roadmap for beta
by StÃ©phane Ducasse May 31, 2009

May 31, 2009

Hi I will harvest later today the fix of gabriel for license cleaning. I would like that we continue this effort and check the tests. I saw that some traits tests are yellow now. I will try to harvest the speed up of multibytestream proposed by nicolas. Stef

1 0

[Pharo-project] loading ecompletion and ocompletion
by Tudor Girba May 31, 2009

May 31, 2009

Hi, I am trying to load ECompletion and OCompletion in a core image, but I do not seem to manage. I first do: ScriptLoader loadOBAlpha. I then tried to do "ScriptLoader loadEcompletion" but I get error in OB. I tried "ScriptLoader loadShout" but I still get an error in OB due to ECompletion. I hoped that maybe "Installer squeaksource project: 'OCompletion'; install: 'OCLoader' would load all the needed dependencies, but it does not seem to work. What am I doing wrong? Cheers, Doru -- www.tudorgirba.com "Sometimes the best solution is not the best solution."

1 0

[Pharo-project] [ANN] 10322 color preference removal
by StÃ©phane Ducasse May 31, 2009

May 31, 2009

Remove the #colorWhenPrettyPrinting preference. As a consequence, some code formatting methods are refactored (The major remodelling is the Compiler>>#format:in:notifying:decorated: removal, replaced by Compiler>>#format:in:notifying:) http://code.google.com/p/pharo/issues/detail?id=824 Stef

1 0

[Pharo-project] XML query engine
by Alexandre Bergel May 30, 2009

May 30, 2009

Dear List, I have been using Michael's XML Parser. It makes me happy. However, a Xpath like query engine is currently missing so far. Any of you had to query XML engine? What are the tools you used? Hard to find its way among the 1500+ projects on squeaksource. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

1 0

[Pharo-project] java has yet another strike against it now
by Steve Wirts May 29, 2009

May 29, 2009

http://tech.slashdot.org/story/09/05/29/1711203/Java-Gets-New-Garbage-Colle…

2 1

[Pharo-project] preferences to settings refactoring: #colorWhenPrettyPrinting case
by Alain Plantec May 29, 2009

May 29, 2009

Hi, A slice is upload in pharoInbox. Cheers Alain Name: SLICE-colorWhenPrettyPrintingRemoval-alain_plantec.2 Dependencies: Compiler-alain_plantec.104, Kernel-alain_plantec.renggli.335, KernelTests-alain_plantec.109, Polymorph-Tools-Diff-alain_plantec.21, System-FilePackage-alain_plantec.6, System-Support-alain_plantec.27, Tools-alain_plantec.154, Traits-alain_plantec.279 Remove the #colorWhenPrettyPrinting preference. As a consequence, some code formatting methods are refactored (The major remodelling is the Compiler>>#format:in:notifying:decorated: removal, replaced by Compiler>>#format:in:notifying:)

2 2

[Pharo-project] Minor test runner bug?
by Mariano Martinez Peck May 29, 2009

May 29, 2009

This is a very low priority bug I think. 1) Go to Test Runner. 2) Select more than 1 or 2 Tests 3) right button -> "select none" After this, you will see that the last selected Test is in blue (or something like violet) color when (I think) should have no color. Is this a bug ? If someone confirm it I will create a ticket. cheers, Mariano

3 3

Re: [Pharo-project] struggeling along
by Dale Henrichs May 29, 2009

May 29, 2009

The 2.3.1 preview one-click is based on the dev image for 10243 and I use 10259 at work, both work fine for GemTools usage. Dale ----- "Reg Krock" <rkrock(a)locksleycreeksoftware.com> wrote: | Which version of Pharo would you recommend? | | Reg | | On 28-May-09, at 5:15 PM, Dale Henrichs wrote: | | > Norbert, | > | > I would recommend using an older version of Pharo for GemTools - the | | > one-click GemTools 2.3.1 preview (based on an earlier version of | > Pharo) is the best option, in my opinion. | > | > I am waiting for the rate of change to slow down a bit, before | > trying GemTools on the latest version of Pharo. | > | > On the other hand if you get GemTools running, let me know and I'll | | > take it for a whirl:) | > | > Dale | > | > ----- "Norbert Hartl" <norbert(a)hartl.name> wrote: | > | > | Hi, | > | | > | I can't really follow the mailing list so some of these might | > | already known and fixed. I just tried to install a gemtools | > | client from universe. I'm using the latest pharo-dev. | > | | > | Installing FFI brought up an syntax error because there is | > | an attempt writing to a temp. Did this change with the | > | closures? I think this is fixed by the version some can load | > | via the ScriptLoader. | > | | > | Next I encountered a problem with MIMEDocument. I think it | > | is Issue-631. There is an incorrect usage of the MIMEDocument | > | interface. I changed it but wanted to store it in PharoInbox | > | but my image crashes if I try to. | > | | > | It is: | > | | > | Segmentation fault | > | | > | -1178673304 UUID>initialize | > | -1178673420 Behavior>new: | > | -1178673512 >new | > | | > | I updated my vm to exupery-0.15.1 but still has the same | behaviour. | > | | > | I attached a patch for the MIMEDocument issue on Issue-631. | > | | > | Than I met InputSensor. InputSensor default returns an instance | > | of InputEventSensor. This looks just strange to me. Is this | right? | > | | > | Norbert | > | | > | | > | _______________________________________________ | > | 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 | > | | Reg Krock | rkrock(a)locksleycreeksoftware.com

2 2