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

Re: [Pharo-project] [update 1.1] #11097

by Mariano Martinez Peck

On Sun, Dec 13, 2009 at 4:31 PM, Marcus Denker <denker(a)acm.org> wrote: > > > IMHO we should also check senders in Pharo and Pharo Web. Pharo core in > itself is nothing. Pharo is the platform for other tools. We have the dev > and web image. We should take care about the packages that are loadable in > Pharo. I am not saying not to remove the method, but at least, to check in > dev and web images and if there are senders, send an email to the > developers/maintainers notifying about this change. Even if the messages > shouldn't be part of the API. With this we avoid possible DNU at runtime. > Not all the external packages covers a good percent of tested code in their > unit tests. > > > > Yes... but there is really stuff that nobody needs. > > Yes, of course. But for example, the other day ifNil:ifNotNilDo: and ifNotNilDo:ifNil: were removed. And maybe are packages that use them, for example O2. Cheers, Mariano > For the other, we should just put removals on the bugtracker and make sure > that we check with the main image before removal... > > In general, I hope to revisit the idea of supporting software evolution in > the language... see e.g. the paper > http://scg.unibe.ch/scgbib?query=Nier08b&display=abstract for some > thoughts of what is needed. > > Marcus > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Dec. 13, 2009

Re: [Pharo-project] [update 1.1] #11097

by Marcus Denker

> IMHO we should also check senders in Pharo and Pharo Web. Pharo core in itself is nothing. Pharo is the platform for other tools. We have the dev and web image. We should take care about the packages that are loadable in Pharo. I am not saying not to remove the method, but at least, to check in dev and web images and if there are senders, send an email to the developers/maintainers notifying about this change. Even if the messages shouldn't be part of the API. With this we avoid possible DNU at runtime. Not all the external packages covers a good percent of tested code in their unit tests. > Yes... but there is really stuff that nobody needs. For the other, we should just put removals on the bugtracker and make sure that we check with the main image before removal... In general, I hope to revisit the idea of supporting software evolution in the language... see e.g. the paper http://scg.unibe.ch/scgbib?query=Nier08b&display=abstract for some thoughts of what is needed. Marcus

Dec. 13, 2009

Re: [Pharo-project] Keyboard Shortcuts in Pharo?

by Mariano Martinez Peck

I forgot to say that there are still some pending problems like the one I reported here: http://code.google.com/p/pharo/issues/detail?id=1064 Cheers, Mariano On Sun, Dec 13, 2009 at 1:26 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > > > 2009/12/13 Bart Gauquie <bart.gauquie(a)gmail.com> > > All, >> >> Looking at all the responses, it looks to me we should do the following >> things: >> >> - Check at the list ( >> http://lists.gforge.inria.fr/pipermail/pharo-project/2009-December/017196.h…) >> of shortcuts Mariano Martinez Peck already provided. Put it on the wiki as a >> WorkInProgress. See which ones are still valid, see which ones can be >> removed, ... >> - Create a wiki document which outlines the changes we want to make to >> the window changing, code selecting, refactoring behaviour I suggested. I >> take the liberty to humbly suggest my initial list of behaviour as a >> starting point for this? >> - Point out who is doing what ... >> >> I'm not sure how new enhancements are discussed on this list. My >> suggestion is to create a wiki document which serves as a working document, >> and so always displays the latest up to date info. Discussions about it are >> done on the mailing list and decisions 'committed' to this doc. >> > > Yes, this could be a good little first step. > > > >> I'll be happy to create this pages, but don't seem to have the rights to >> create a new page on the wiki. >> >> Kind Regards, >> >> Bart >> -- >> imagination is more important than knowledge - Albert Einstein >> Logic will get you from A to B. Imagination will take you everywhere - >> Albert Einstein >> Learn from yesterday, live for today, hope for tomorrow. The important >> thing is not to stop questioning. - Albert Einstein >> The true sign of intelligence is not knowledge but imagination. - Albert >> Einstein >> Gravitation is not responsible for people falling in love. - Albert >> Einstein >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > >

Dec. 13, 2009

Re: [Pharo-project] Keyboard Shortcuts in Pharo?

by Mariano Martinez Peck

2009/12/13 Bart Gauquie <bart.gauquie(a)gmail.com> > All, > > Looking at all the responses, it looks to me we should do the following > things: > > - Check at the list ( > http://lists.gforge.inria.fr/pipermail/pharo-project/2009-December/017196.h…) > of shortcuts Mariano Martinez Peck already provided. Put it on the wiki as a > WorkInProgress. See which ones are still valid, see which ones can be > removed, ... > - Create a wiki document which outlines the changes we want to make to > the window changing, code selecting, refactoring behaviour I suggested. I > take the liberty to humbly suggest my initial list of behaviour as a > starting point for this? > - Point out who is doing what ... > > I'm not sure how new enhancements are discussed on this list. My suggestion > is to create a wiki document which serves as a working document, and so > always displays the latest up to date info. Discussions about it are done on > the mailing list and decisions 'committed' to this doc. > Yes, this could be a good little first step. > I'll be happy to create this pages, but don't seem to have the rights to > create a new page on the wiki. > > Kind Regards, > > Bart > -- > imagination is more important than knowledge - Albert Einstein > Logic will get you from A to B. Imagination will take you everywhere - > Albert Einstein > Learn from yesterday, live for today, hope for tomorrow. The important > thing is not to stop questioning. - Albert Einstein > The true sign of intelligence is not knowledge but imagination. - Albert > Einstein > Gravitation is not responsible for people falling in love. - Albert > Einstein > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Dec. 13, 2009

Re: [Pharo-project] Ugly disabled buttons

by Tudor Girba

I would also vote for dimming :) Cheers, Doru On 13 Dec 2009, at 12:55, Lukas Renggli wrote: > That's the fuzzy label of Polymorph. It sort of works with true-type > fonts, but makes the bitmap fonts unreadable. I don't like it in any > case, have never seen a user-interface using something like that. Why > not just dim the color? > > Lukas > > 2009/12/13 Adrian Lienhard <adi(a)netstyle.ch>: >> The disabled buttons look ugly with the new strike fonts. Does >> somebody know >> what the reason is and how to fix it? We cannot ship Pharo like >> this... >> >> Cheers, >> Adrian >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com "Speaking louder won't make the point worthier."

Dec. 13, 2009

Re: [Pharo-project] Ugly disabled buttons

by Lukas Renggli

That's the fuzzy label of Polymorph. It sort of works with true-type fonts, but makes the bitmap fonts unreadable. I don't like it in any case, have never seen a user-interface using something like that. Why not just dim the color? Lukas 2009/12/13 Adrian Lienhard <adi(a)netstyle.ch>: > The disabled buttons look ugly with the new strike fonts. Does somebody know > what the reason is and how to fix it? We cannot ship Pharo like this... > > Cheers, > Adrian > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli http://www.lukas-renggli.ch

Dec. 13, 2009

[Pharo-project] Ugly disabled buttons

by Adrian Lienhard

The disabled buttons look ugly with the new strike fonts. Does somebody know what the reason is and how to fix it? We cannot ship Pharo like this... Cheers, Adrian

Dec. 13, 2009

Re: [Pharo-project] Keyboard Shortcuts in Pharo?

by Adrian Lienhard

Hi Bart, This sounds like a good plan! I added you as a project committer, which should give you write access to the wiki. Cheers, Adrian On Dec 13, 2009, at 04:58 , Bart Gauquie wrote: > All, > > Looking at all the responses, it looks to me we should do the > following > things: > > - Check at the list ( > http://lists.gforge.inria.fr/pipermail/pharo-project/2009-December/017196.h…) > of shortcuts Mariano Martinez Peck already provided. Put it on the > wiki as a > WorkInProgress. See which ones are still valid, see which ones can > be > removed, ... > - Create a wiki document which outlines the changes we want to > make to > the window changing, code selecting, refactoring behaviour I > suggested. I > take the liberty to humbly suggest my initial list of behaviour as a > starting point for this? > - Point out who is doing what ... > > I'm not sure how new enhancements are discussed on this list. My > suggestion > is to create a wiki document which serves as a working document, and > so > always displays the latest up to date info. Discussions about it are > done on > the mailing list and decisions 'committed' to this doc. > I'll be happy to create this pages, but don't seem to have the > rights to > create a new page on the wiki. > > Kind Regards, > > Bart > -- > imagination is more important than knowledge - Albert Einstein > Logic will get you from A to B. Imagination will take you everywhere - > Albert Einstein > Learn from yesterday, live for today, hope for tomorrow. The > important thing > is not to stop questioning. - Albert Einstein > The true sign of intelligence is not knowledge but imagination. - > Albert > Einstein > Gravitation is not responsible for people falling in love. - Albert > Einstein > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 13, 2009

Re: [Pharo-project] SqueakMap code into Pharo?

by Adrian Lienhard

I added this to the FAQ of our web site: http://www.pharo-project.org/documentation/faq Adrian On Dec 13, 2009, at 04:40 , Bart Gauquie wrote: > Hi, > > That is very handy information. I've searched on the pharo wiki, but > did not > find any info about SqueakMap, except that: 'Remove SqueakMap and > Installer > from core'. > > Would it not be a good idea to provide a wiki page for users that know > Squeak and 'miss' certain features in Pharo, explaining a work > around for > Pharo; this info you gave as a first example? > > Kind Regards, > > Bart > > On Sat, Dec 12, 2009 at 11:47 PM, Lukas Renggli <renggli(a)gmail.com> > wrote: > >>> How do I load code that is in SqueakMap into a Pharo Image? >> >> You go to the SqueakMap website (http://map1.squeakfoundation.org/) >> navigate to the project, download the release and drag&drop it into >> the Pharo image. >> >>> Specifically I'm interested in Sixx and SoapCore but it would be >>> good to >>> know if there is a general way to load code from SqueakMap into a >>> Pharo >>> image. >> >> Presumably the code from SqueakMap outdated, you might also want to >> search on SqueakSource. >> >> Lukas >> >> -- >> Lukas Renggli >> http://www.lukas-renggli.ch >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > imagination is more important than knowledge - Albert Einstein > Logic will get you from A to B. Imagination will take you everywhere - > Albert Einstein > Learn from yesterday, live for today, hope for tomorrow. The > important thing > is not to stop questioning. - Albert Einstein > The true sign of intelligence is not knowledge but imagination. - > Albert > Einstein > Gravitation is not responsible for people falling in love. - Albert > Einstein > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 13, 2009

[Pharo-project] stream nile fixes?

by StÃ©phane Ducasse

Damien or cyrille could you check if the following is working in Nile? http://code.google.com/p/pharo/issues/detail?id=1595 Stef

Dec. 13, 2009