- Pharo-dev - lists.pharo.org

[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

[Pharo-project] [ANN] update to OCompletion
by Romain Robbes May 29, 2009

May 29, 2009

new in this update: -OCompletion completes also class names! If the prefix starts with an uppercase letter, OCompletion will propose recently changed classes. Since it maintains its small list of classes, the speed problem Hernan encountered is partially solved (it still slows downs while you scroll in the extended list). Also, Henrik's concern about case sensitivity is now solved for that case (I still think it should be case- insensitive after the first letter, but we can discuss this). -OCompletion uses the default font for menus, which is indeed nicer ;-) -OCompletion only proposes matches strictly longer than what was actually typed. -Various small bug fixes (thanks Simon!). I'm looking forward to your feedback as usual, Romain -- Romain Robbes http://www.inf.unisi.ch/phd/robbes

6 8

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

May 29, 2009

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

4 3

[Pharo-project] Finding code
by Schwab,Wilhelm K May 29, 2009

May 29, 2009

I am finding that OB, Moniticello, or just plain gremlins are making life hard on me. I have code that I want to package; more specifically, I need to repackage some of it. I thought it might make sense to name something Seaside-ThisOrThat, but that turns out to get burried in the Seaside 2 category, and moving clases and methods to SeasideThisOrThat or another package frequently locks up the image. I have all of the relevant code captured in a change set. Is it safe to edit the categories in the chunks and file that into a new image? I did that (hopefully correctly) to a copy of the change set in the hopes tha a new image would see things in the correct place from the bginning. If any of this sounds like typical newbie (re Monticello) growing pains, please say so. Bill

2 2

[Pharo-project] Can't update pharo0.1-10318dev09.05.4
by Oscar Nierstrasz May 29, 2009

May 29, 2009

Hi Folks, I just downloaded the latest pharo-dev and tried to update it. I got 12 "Undefined Object>>doesNotUnderstand: #includes" messages. I don't see any issue logged for this yet. Anyone else seen this? - on

1 1

[Pharo-project] Crypt ... Libraries ...
by stepken May 29, 2009

May 29, 2009

> Pharo developers are few and limited. They are trying to do all of their > best on Pharo. We know this an important package but perhaps they have more > important things to do. Pharo is not even in a beta of first milestone. This > can be planned in a future milestone. Hmmm. How many manyears were invested in Squeak? 1000, 2000? You have removed lots of code due to "license problems". See R.A. Harmon code. What a pitty to throw away code ... Do you really think, he really cares about his former code contribution to a system, which from the beginning was free and open? Don't you think, every jugde would confirm, that such code contributions were made in the sense of "giveaways"? I think you don't have a real understanding of what you have destroyed now. Having rewritten array/colletions/streams code ... a bit shorter code now, because of traits. Who really cares? You want to build a commercial platform to make money. Supported. Yes. Didn't you all Smalltalk Developers notice, that even Dolphin was close to give up? They hat to find their new business model. And they also have a very sophisticated *free* version. GNU Smalltalk 3.0 ... fine thing, free, can run seaside, pier, .... what do i need more? Free! Do you really hope to get one cent for supporting a free smalltalk platform? I really appreciate your effords. There are things, that had to be done on Squeak. Traits, 5th implemention of closures ... But ... you haven't included the old code contributors at Viewpoint Research Institute, MIT (Scratch), HPI Berlin. Where are your plans to give back your code changes to squeak/scratch community? No. Very egoistic, IMHO. Where is the "soft refactoring" without destroying anything ...? At the moment ... i see some developments with pleasure, others are catastrophic ... Eliot writing the 10th implementation of a squeak jitter. Fine. Every profesional company uses LLVM. Apple e.g. I wanted to know, how fast a programming language with jitter could be done. It took me about 2 weeks ...LL(1) grammar, LLVM ... works like a charm on Intel, ARM, PPC ... and really fast! Other platforms to be tested. Of cause, lots of things to be done .. debugging ... profiling ... no classbrowser ... but i can run older squeak code with morphic. 80%/20% problem ;-) Or rather 90/10? Dunnow, i stopped the development. Was an experiment. Will Eliots jitter run on different processor architectures? No! 386 machine code only. So - no real portability! Who really cares that stuff then? Ever heard of the giant chinese market? They use MIPS clone 32+64Bit processors with Linux now. Everywhere. China can't officially use Intel, because of too much power consumption. I've been there several times. MIPS, everywhere. In China and Japan you find lots of people doing squeak stuff. Potential code contributors code developers for Pharo, partners! Morphic code .. from SELF Programming Language development ... then ported to squeak, then to Javascript. Fine. ETOYS on TOP. Where is my loved ETOYS? The only reason to use Squeak or Pharo! Education was and is the domain of Squeak. Nothing else. I asked Frank Lesser for EToys / Morphic on top of his Smalltalk. Matured, blindingly fast, Jitter written in Assembler. Now the base for DNG. Not a great problem, he meant, he had it once ported for testing purposes. If i really needed a sophisticated smalltalk to start new projects ... what do you think, what i would take? Smalltalk for educational purposes, e.g.? I have free choice. But no ETOYS, anywhere. Children really love EToys. It's a marvelous software package for educational purposes. Many companies are caught in their own jail of huge masses of GUI code. They can't go with other smalltalks. Will they ever change to a "supported Pharo"? I think: No. Morphic ... no MVC, no MVP. What has happened to Tweak code? ETOYS was ported to that GUI. That code was quite ok. Why haven't the code autors spent that code for Squeak/Pharo? So please ... don't tell me you haven't enough hands at the moment. Do the right things, not just some few things right, beautifying GUI, implemeting the 5th version of closures and well ... traits. Do 'crowdsourceing', invite people to contribute, learn community organizing first. Give them a reason to contribute. Give them a future, a business modell to participate. Your egoistic path to make a commercial supported free smalltalk ... good idea, but you are lightyears far from that. Leo Penta wrote a nice book about that 'crowdsourceing' stuff, or reread "Eric Raymond - Cathedral and the basaar" again and again and again. *PARTICIPATION* Bring people to participate your business model. LEARN from the mistakes, many, many good programmers did. See TWEAK bad fate. Dead development process. Good sourcecode, lost in space ... like many squeak packages. *Defective development process*. I posted that as issue, it was deleted by someone not really understanding, what i meant. thanx for understanding. cheers, Guido Stepken

7 8

[Pharo-project] SLICE-RelicensingPart1
by Alexandre Bergel May 28, 2009

May 28, 2009

I went through all the changes proposed by this slice. I am not sure how should I review the code, but here is my try: - the new version of Character class>>codePoint: anInteger seems to have a different behavior: The old (current) code is codePoint: integer "Return a character whose encoding value is integer." #Fundmntl. (0 > integer or: [255 < integer]) ifTrue: [self error: 'parameter out of range 0..255']. ^ CharacterTable at: integer + 1 The new one is: codePoint: anInteger "Just for ANSI Compliance" ^self value: anInteger value: anInteger "Answer the Character whose value is anInteger." anInteger > 255 ifTrue: [^self basicNew setValue: anInteger]. ^ CharacterTable at: anInteger + 1. At the end an error is raised, but this is not the same. Was this review useful? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

10 26

[Pharo-project] struggeling along
by Norbert Hartl May 28, 2009

May 28, 2009

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

3 3

[Pharo-project] License cleaning: 74 methods left
by Adrian Lienhard May 28, 2009

May 28, 2009

I did the check again for Pharo #10310 and now we are down at 74 dirty methods. I removed all remaining methods of Richard A. Harmon (RAH) from the list of dirty methods because, as I figured out just now, they originate from the SqueakSource package "ANSI Compatibility", which is released under SqueakL. @Gabriel: this means it would be possible to use the old versions of methods, like #codePoint, you have been working on. The up to date list can be found as usual at: http://code.google.com/p/pharo/wiki/ResultofRelicensing Further help (thanks Gabriel!) is welcome... Cheers, Adrian

2 1