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

Re: [Pharo-project] Show stopper network bug on Windows

by Schwab,Wilhelm K

I think I have it willing to keep running now. I looked for the #inform: in the process browser, and missed it the first time - I needed to ask for the full stack, and there it was, a good long way down the list :) It is now sending text to the transcript, so cross your fingers. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Schwab,Wilhelm K Sent: Tuesday, July 21, 2009 2:22 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Show stopper network bug on Windows It's trying to run on a win2k3 box. I say trying because it insists on telling me (modally) how many updates it processed - every time. Is there a way to gag that? Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse Sent: Tuesday, July 21, 2009 1:36 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Show stopper network bug on Windows Yes we do not have a windows at hand. can you let us know from which update the problem is related. > In this case the first step woud be to identify which update > introduced the problem. > > Suppose that a core #10200 image still works, you could do: > > 10200 to: 10384 do: [ :i | > Utilities updateFromServerThroughUpdateNumber: i. > NetNameResolver localHostAddress ] > > And then see after which update number the first exception is thrown. > I did not test this, but it should work. > > Adrian _______________________________________________ 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

July 21, 2009

Re: [Pharo-project] Persist a morph in a message.

by nullPointer

>Just a guess: maybe it is better to persist a morph(s) as is - as >original objects - just keep them somewhere in classvars. >Then to create a new view of it, just do a #deepCopy. Perhaps could be a combined solution. Persist the morph in a method, but only load one time, if class var is nothing. Then in the next times send #deepCopy to prototype morph . That could be a solution for the velocity :) I believe than EasyMorphicGUI works of that way too. Regards. -- View this message in context: http://n2.nabble.com/Persist-a-morph-in-a-message.-tp3292117p3295437.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

July 21, 2009

Re: [Pharo-project] VersionHistory and VersionNumber

by Damien Cassou

On Tue, Jul 21, 2009 at 7:36 PM, Adrian Lienhard<adi(a)netstyle.ch> wrote: > Does anybody use these two classes? Are they worth being kept in the > core (there are no users in the core)? when you want to know about users of a specific code, you'd better look at Pharo instead of the Pharo-core. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

July 21, 2009

Re: [Pharo-project] HostSystemMenuTest MNU

by Marcus Denker

On 21.07.2009, at 14:36, StÃ©phane Ducasse wrote: > I recognize john method > yes... don't remember what I edited... I filed those in when adding John's code fro HostMenu. Marcus > > On Jul 21, 2009, at 7:23 PM, Adrian Lienhard wrote: > >> Hi Marcus, >> >> In the test below, which has your initials, the following methods are >> not understood. >> >> calculateShouldBeFrom:using: and modifySqueakMenu: >> >> Maybe you know where to get these methods from, how to implement >> them, >> or if we should rather delete the test? >> >> Cheers, >> Adrian >> >> HostSystemMenuTest>>testCharacterChanging >> | testString item shouldBe resultingString where | >> #(';' '^' '!' '<' '/' '(' ) >> do: [:c | #('*' '* ' '* ' '**' '** ' '** ' >> ')' '*)' '* )' '* )' '**)' '** )' '** )' >> ')' '*)' '*X)' '*XX)' '**)' '**X)' '**XX)' >> '))' '*))' '*X))' '*XX))' '**))' '**X))' '**XX))' >> '(' '*(' '*X(' '*XX(' '**)' '**X(' '**XX(' >> '((' '*((' '*X((' '*XX((' '**((' '**X((' '**XX((' >> ) >> do: [:template | >> testString := template copyReplaceAll: '*' with: c. >> testString >> permutationsDo: [:mixedUp | >> item := mixedUp copy. >> shouldBe := self calculateShouldBeFrom: item using: c. >> resultingString := self modifySqueakMenu: item copy. >> self should: [shouldBe = resultingString]. >> (where := resultingString indexOf: $/) > 0 >> ifTrue: [self should: [(mixedUp at: where) = $(]. >> self should: [(mixedUp at: where+2) = $)]. >> self should: [(mixedUp at: where+1) asUppercase = >> (resultingString at: where+1)]]]]] >> >> >> _______________________________________________ >> 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

July 21, 2009

[Pharo-project] [update] #10388

by Marcus Denker

10388 ===== Issue 937: [fix] remove some unimplemented calls from BalloonEngine Issue 888: LongTestCase is unpackaged Issue 962: remove BlockArgsNode KeyWordNode Issue 894: Browser>>copyClass is lost Issue 960: unused methods in MethodDictionary Issue 898: MessageNotUnderstood: UndefinedObject>>something I closed the following OB-related reports that where put as "fixed" by David: Issue 766: UndefinedObject(Object)>>doesNotUnderstand: #itemKind Issue 905: Error with right click -> OBTextSelection(Object)>>doesNotUnderstand: #isMethodNode And those because they where not relevant anymore: Issue 586: merge MorphicExtras-Flaps with Morphic-Worlds Marcus -- Marcus Denker - http://marcusdenker.de PLEIAD Lab - Computer Science Department (DCC) - University of Chile

July 21, 2009

Re: [Pharo-project] Show stopper network bug on Windows

by Schwab,Wilhelm K

It's trying to run on a win2k3 box. I say trying because it insists on telling me (modally) how many updates it processed - every time. Is there a way to gag that? Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse Sent: Tuesday, July 21, 2009 1:36 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Show stopper network bug on Windows Yes we do not have a windows at hand. can you let us know from which update the problem is related. > In this case the first step woud be to identify which update > introduced the problem. > > Suppose that a core #10200 image still works, you could do: > > 10200 to: 10384 do: [ :i | > Utilities updateFromServerThroughUpdateNumber: i. > NetNameResolver localHostAddress ] > > And then see after which update number the first exception is thrown. > I did not test this, but it should work. > > Adrian _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 21, 2009

Re: [Pharo-project] Persist a morph in a message.

by Cameron Sanders

Thanks for the correction and full details. -Cam On Jul 21, 2009, at 3:14 PM, Torsten Bergmann wrote: > Cameron wrote: >> Torsten, >> >> Are you wanting to resolve your storage format right now, or just >> improve the I/O? > > Cameron, you must have missed something. I'm not the author of the > UI builder. The author is "nullPointer" who asked the > question regarding I/O on the mailing list and announced the video > [1]. > > The style of his message looks to me like he wants to stay anonymous > for whatever reason and the project is (so far) closed source. > Maybe it becomes a commercial or open source project. Only > "nullPointer" is able to answer this ... > > I just wanted to know what the state of the project is. > He has left a comment on my blog with some more infos (see [2]) > > Bye > Torsten > > [1] http://lists.gforge.inria.fr/pipermail/pharo-project/2009-July/011176.html > [2] http://astares.blogspot.com/2009/07/ui-builder-for-pharo.html

July 21, 2009

[Pharo-project] Persist a morph in a message.

by Torsten Bergmann

Cameron wrote: >Torsten, > >Are you wanting to resolve your storage format right now, or just >improve the I/O? Cameron, you must have missed something. I'm not the author of the UI builder. The author is "nullPointer" who asked the question regarding I/O on the mailing list and announced the video [1]. The style of his message looks to me like he wants to stay anonymous for whatever reason and the project is (so far) closed source. Maybe it becomes a commercial or open source project. Only "nullPointer" is able to answer this ... I just wanted to know what the state of the project is. He has left a comment on my blog with some more infos (see [2]) Bye Torsten [1] http://lists.gforge.inria.fr/pipermail/pharo-project/2009-July/011176.html [2] http://astares.blogspot.com/2009/07/ui-builder-for-pharo.html -- Neu: GMX Doppel-FLAT mit Internet-Flatrate + Telefon-Flatrate fÃ¼r nur 19,99 Euro/mtl.!* http://portal.gmx.net/de/go/dsl02

July 21, 2009

Re: [Pharo-project] Why Pharo?

by Travis Kay

Being a Dolphin Pro user myself, I have to agree with Esteban and Bill on all accounts. Travis Kay -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Schwab,Wilhelm K Sent: Tuesday, July 21, 2009 9:18 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Why Pharo? +100000000000000 to Esteban's comments on the Dolphin IDE - it's slick in ways that are not visually obvious. Some of it comes from speed, some from use of the good from GUI conventions, and the rest from good IDE design. -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Esteban A. Maringolo Sent: Tuesday, July 21, 2009 10:59 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: [Pharo-project] Why Pharo? Hello, Mariano's post spurred me to write my reasons of "why to use it", so I started this post. >>After many hesitations (I was reluctant to use Squeak) I decided to >>use Pharo for it and not Dolphin (my favorite Smalltalk), because of >>several reasons. >would be nice to know them hehe >sorry...in another thread. - It's mainly about getting mainstream, and not willing to develop everything from scratch once and again. - At work we've developed everything by our own on VSE/Dolphin, so every time we wanted to do something, we had to build it by ourselves (most of it). We even had a Magritte like framework (years before Magritte existed), persistence, reporting, etc. Now some of them, are very mature frameworks. But I can't borrow any of them for personal use ;-) and don't want to spend a year rewriting the frameworks I've created, contributed to or used at work. - Because what I want to build is going to be web based (and I hope to get it mobile to), anything that runs on linux is good to be considered as a server solution. - So I wanted a rich class library/frameworks, in order to be able to focus on the business logic I want to build. - I wanted to have the latest versions of such frameworks, even when it's getting easier to port them (I did port Swazoo and Seaside in the past), I'm not in the mood to do it now (yes, I'm getting lazy). - Because Dolphin future is uncertain yet, DNG seems to be the next-generation VM/Smalltalk, but I can't wait until it's ready, the conditions clear ($$$) and have the above mentioned points included. - Because I like where Pharo is going to, or seems to be going. I like its mission and how its being managed (releases, issues, patches,tests). It's a solid foundation for any reliable project. - Because nothing really new has come from other really good smalltalks like VAST/Dolphin/VW, everything is getting ported, and eventually a contribution gets back to the source. I see GLASS as an "extension" of Pharo/Squeak, because it was made very compatible, and the edges in contact work very close to each other (GLASS is useless if outdated in relation with Pharo/Squeak). - Because after all, Pharo is also Smalltalk. And I rather choose it before going to other also good stuff (like Rails), or not so good as PHP/Java/DotNet) - I want to focus on the business I'm trying to solve, and forget about everything mentioned above. The only thing that keeps me remembering the stuff above, is I'm still not comfortable as I am with Dolphin, not just because of habit. Dolphin's IDE is really neat, quick, consistent, gets the stuff done and then gets out of your way. You have to use it and do some real work to understand what I'm talking about. But I'm pretty confident Pharo will achieve such level of maturity in the not so far future. I hope it clears my reasoning behind choosing Pharo. Best regards, -- Esteban _______________________________________________ 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

July 21, 2009

Re: [Pharo-project] [Moose-dev] Re: Fwd: [SEWORLD] Call for Papers: Evaluation and Usability of Programming Languages and Tools (PLATEAU) 2009

by Alexandre Bergel

> I do not expect anything from this kind of workshop. Me neither, but this workshop can be a good alternative to many other workshop at oopsla. Moreover, a 4 pages paper does not require a lot of work. Alexandre > > On Jul 21, 2009, at 8:40 PM, Alexandre Bergel wrote: > >>> I like the topic of the workshop, because I have struggled with the >>> problem of evaluating and comparing usability a lot in the past, >>> and I >>> see that Antoine and FrÃ©dÃ©ric have similar problems with their >>> research. The only thing I hope is that this workshop is not on the >>> same day as >> >> I was thinking that having a short paper on Pharo will definitely be >> of a good move. >> >>> DLS (where we'll be presenting the RoelTyper paper, that >>> got accepted after FrÃ©dÃ©ric improved the precision; watch out for >>> this >>> new version in Squeak and Pharo one of the coming days). >> >> Congratulation! >> >>> Alex, are you going to OOPSLA ? >> >> Unfortunately not. I won't attend ESUG as well. sic... >> Next year my budget will be much larger. >> >> Alexandre >> >> >>> On Tue, Jul 21, 2009 at 3:58 PM, Alexandre >>> Bergel<alexandre(a)bergel.eu> wrote: >>>> I like the idea of this workshop. If someone is going to OOPSLA >>>> this year, >>>> this may be interesting. >>>> If someone plan to go there, let me know. >>>> >>>> Cheers, >>>> Alexandre >>>> >>>> >>>> Begin forwarded message: >>>> >>>>> From: Shane Markstrum <smarkstr(a)acm.org> >>>>> Date: 20 July 2009 16:40:22 GMT-04:00 >>>>> To: types-announce(a)lists.seas.upenn.edu, seworld(a)sigsoft.org, >>>>> announce(a)aosd.net, chi-announcements(a)LISTSERV.ACM.ORG, >>>>> hci-link(a)lists.uni-paderborn.de >>>>> Subject: [SEWORLD] Call for Papers: Evaluation and Usability of >>>>> Programming Languages and Tools (PLATEAU) 2009 >>>>> >>>>> Call for Papers >>>>> >>>>> PLATEAU 2009 >>>>> >>>>> First Workshop on >>>>> Evaluation and Usability of Programming Languages and Tools >>>>> (PLATEAU) >>>>> in conjunction with Onward!/OOPSLA 2009 >>>>> October 25-29, 2009 (Orlando, FL) >>>>> >>>>> http://ecs.victoria.ac.nz/Events/PLATEAU/WebHome >>>>> >>>>> SUBMISSION SITE >>>>> >>>>> http://www.easychair.org/conferences/?conf=plateau09 >>>>> >>>>> IMPORTANT DATES >>>>> >>>>> Submission August 31 >>>>> Notification Mid-September (before close of early registration >>>>> for >>>>> OOPSLA/Onward!) >>>>> Final version TBA >>>>> Workshop TBA, one-half or one-full day between October 25 >>>>> and 29 >>>>> >>>>> SCOPE >>>>> >>>>> Programming languages exist to enable programmers to develop >>>>> software >>>>> effectively. But how efficiently programmers can write software >>>>> depends on the usability of the languages and tools that they >>>>> develop >>>>> with. The aim of this workshop is to discuss methods, metrics and >>>>> techniques for evaluating the usability of languages and language >>>>> tools. The supposed benefits of such languages and tools cover a >>>>> large >>>>> space, including making programs easier to read, write, and >>>>> maintain; >>>>> allowing programmers to write more flexible and powerful >>>>> programs; and >>>>> restricting programs to make them more safe and secure. >>>>> >>>>> We plan to gather the intersection of researchers in the >>>>> programming >>>>> language, programming tool, and human-computer interaction >>>>> communities >>>>> to share their research and discuss the future of evaluation and >>>>> usability of programming languages and tools. We are also >>>>> interested >>>>> in the input of other members of the programming research >>>>> community >>>>> working on related areas, such as refactoring, design patterns, >>>>> program analysis, program comprehension, software visualization, >>>>> end-user programming, and other programming language paradigms. >>>>> Some >>>>> particular areas of interest are: >>>>> >>>>> - empirical studies of programming languages >>>>> - methodologies and philosophies behind language and tool >>>>> evaluation >>>>> - software design metrics and their relations to the underlying >>>>> language >>>>> - user studies of language features and software engineering tools >>>>> - visual techniques for understanding programming languages >>>>> - critical comparisons of programming paradigms, such as >>>>> object-oriented vs. functional >>>>> - tools to support evaluating programming languages >>>>> >>>>> SUBMISSIONS >>>>> >>>>> Participants are invited to submit a position paper describing >>>>> their >>>>> on going work. We will accept papers (from 4 to 6 pages) that >>>>> describe >>>>> work-in-progress or recently completed work based on the themes >>>>> and >>>>> goals of the workshop or related topics, report on experiences >>>>> gained, >>>>> question accepted wisdom, raise challenging open problems, or >>>>> propose >>>>> speculative new approaches. Longer submissions will be >>>>> considered, but >>>>> all submissions must be fewer than 10 pages. >>>>> >>>>> Submissions and final papers should be formatted using the ACM >>>>> SIGPLAN >>>>> 10 point format. Templates for Word and LaTeX are available at >>>>> http://www.acm.org/sigs/sigplan/authorInformation.htm; this site >>>>> also >>>>> contains links to useful information on how to write effective >>>>> submissions. >>>>> >>>>> Accepted submissions will be made available through this website >>>>> and >>>>> workshop participants are encouraged to have read the position >>>>> papers >>>>> before attending the workshop. Participants are also asked to >>>>> prepare >>>>> a presentation to support their position paper. >>>>> >>>>> ORGANIZERS (and members of the Committee) >>>>> >>>>> Craig Anslow - Victoria University of Wellington, New Zealand >>>>> Shane Markstrum - Bucknell University, USA >>>>> Emerson Murphy-Hill - University of British Columbia, Canada >>>>> >>>>> PROGRAM COMMITTEE >>>>> >>>>> Andrew Black - Portland State University, USA >>>>> Larry Constantine - University of Madeira, Portugal >>>>> Jeff Foster - University of Maryland, College Park, USA >>>>> Robert Fuhrer - IBM Research, USA >>>>> Donna Malayeri - EPFL, Switzerland/Carnegie Mellon University, USA >>>>> Stuart Marshall - Victoria University of Wellington, New Zealand >>>>> Todd Millstein - University of California, Los Angeles, USA >>>>> James Noble - Victoria University of Wellington, New Zealand >>>>> Ewan Tempero - University of Auckland, New Zealand >>>>> >>>>> For more information, please see the workshop website: >>>>> >>>>> http://ecs.victoria.ac.nz/Events/PLATEAU/WebHome >>>>> >>>>> ============================================================ >>>>> To contribute to SEWORLD, send your submission to >>>>> mailto:seworld@sigsoft.org >>>>> >>>>> http://www.sigsoft.org/seworld provides more >>>>> information on SEWORLD as well as a complete archive of >>>>> messages posted to the list. >>>>> ============================================================ >>>>> >>>>> >>>> >>>> -- >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>> Alexandre Bergel http://www.bergel.eu >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Moose-dev mailing list >>>> Moose-dev(a)iam.unibe.ch >>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)iam.unibe.ch >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > _______________________________________________ > 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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

July 21, 2009