- Pharo-dev - lists.pharo.org

Re: [Pharo-project] getting rid of these boring questions and popup

by Schwab,Wilhelm K

The answer to "is it possible to..." is almost always yes. I think it would be easier to suppress the popups add some type of analyzer/mentor pane, but I'm no expert on how the browsers work. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Andrey Larionov Sent: Friday, September 11, 2009 4:54 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] getting rid of these boring questions and popup is it possible to show with flag "Do not hastiate anymore?" and save state in current instance of editor (or some)? On Sat, Sep 12, 2009 at 01:32, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > Stef, > > Yes, the popups should go away - far away :) Â A code mentor pane with lint rule violations would be greatly appreciated, but the modal messages are too much. Â Sometimes I want to save code that I know will generate errors, with reasons ranging from "I'll let it blow up and choose to implement it from the debugger" to "don't want to lose this, so let's get it accepted before I do something stupid." > > Bill > > > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr > [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of > Michael Roberts > Sent: Friday, September 11, 2009 4:21 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] getting rid of these boring questions and > popup > > i would be quite happy if the "this variable is not used" was picked up by a lint rule. Â the "your using this variable and you haven't yet assigned a value" is sometimes nice. however, if lint/slint/slime (?) had a nice permanent UI mechanism in the browser (i haven't checked) then I would get rid the former in preference of such a framework that can point out all sorts of useful things with the code when you accept methods. could then be package / context aware etc. > > Mike > > On Fri, Sep 11, 2009 at 6:12 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> Hi guys >> >> I would like what you think of these wonderful popups that try to >> help to write cool code but just get in my way: >> Â Â Â Â "this variable is not used.... >> Â Â Â Â you did not store into it.... >> >> Could we agree that we are adults? >> and this is more a pain than anything else? >> >> Stef >> >> _______________________________________________ >> 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 > > _______________________________________________ > 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

Sept. 11, 2009

[Pharo-project] Graphics-Centric UI Capability?

by dmurphy＠infratecture.com

hello all, i have been nabbling about the list archives, trying to figure out the right class to use for providing a scrolling graph pane on which i can draw shapes. suppose i were to take UITheme(class)>>exampleWindowWithToolbars and want to turn that into a simple Paint Program. what would i put in place of the StandardWindow>>newTextEditorFor:getText:setText:getEnabled: message send? are there any simple Paint Program examples i start with? thanks for any pointers! delbert

Sept. 11, 2009

Re: [Pharo-project] getting rid of these boring questions and popup

by Andrey Larionov

is it possible to show with flag "Do not hastiate anymore?" and save state in current instance of editor (or some)? On Sat, Sep 12, 2009 at 01:32, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > Stef, > > Yes, the popups should go away - far away :) Â A code mentor pane with lint rule violations would be greatly appreciated, but the modal messages are too much. Â Sometimes I want to save code that I know will generate errors, with reasons ranging from "I'll let it blow up and choose to implement it from the debugger" to "don't want to lose this, so let's get it accepted before I do something stupid." > > Bill > > > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Michael Roberts > Sent: Friday, September 11, 2009 4:21 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] getting rid of these boring questions and popup > > i would be quite happy if the "this variable is not used" was picked up by a lint rule. Â the "your using this variable and you haven't yet assigned a value" is sometimes nice. however, if lint/slint/slime (?) had a nice permanent UI mechanism in the browser (i haven't checked) then I would get rid the former in preference of such a framework that can point out all sorts of useful things with the code when you accept methods. could then be package / context aware etc. > > Mike > > On Fri, Sep 11, 2009 at 6:12 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> Hi guys >> >> I would like what you think of these wonderful popups that try to help >> to write cool code but just get in my way: >> Â Â Â Â "this variable is not used.... >> Â Â Â Â you did not store into it.... >> >> Could we agree that we are adults? >> and this is more a pain than anything else? >> >> Stef >> >> _______________________________________________ >> 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 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Sept. 11, 2009

Re: [Pharo-project] getting rid of these boring questions and popup

by Esteban Lorenzano

+1 On 2009-09-11 18:32:18 -0300, "Schwab,Wilhelm K" <bschwab(a)anest.ufl.edu> said: > Stef, > > Yes, the popups should go away - far away :) A code mentor pane with lint > rule violations would be greatly appreciated, but the modal messages are to > o much. Sometimes I want to save code that I know will generate errors, wi > th reasons ranging from "I'll let it blow up and choose to implement it fro > m the debugger" to "don't want to lose this, so let's get it accepted befor > e I do something stupid." > > Bill > > > -----Original Message----- > From: > pharo-project-bounces(a)lists.gforge.inria.fr > [mailto:pharo-project-bou > nces(a)lists.gforge.inria.fr] On Behalf Of > Michael Roberts > Sent: Friday, September 11, 2009 4:21 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] getting rid of these boring questions and popup > > i would be quite happy if the "this variable is not used" was picked up by > a lint rule. the "your using this variable and you haven't yet assigned a > value" is sometimes nice. however, if lint/slint/slime (?) had a nice perma > nent UI mechanism in the browser (i haven't checked) then I would get rid t > he former in preference of such a framework that can point out all sorts of > useful things with the code when you accept methods. could then be package > / context aware etc. > > Mike > > On Fri, Sep 11, 2009 at 6:12 PM, StÃ©phane Ducasse <stephane.ducasse@inria > .fr> wrote: >> Hi guys >> >> I would like what you think of these wonderful popups that try to help > >> to write cool code but just get in my way: >> Â Â Â Â "this variable is not used.... >> Â Â Â Â you did not store into it.... >> >> Could we agree that we are adults? >> and this is more a pain than anything else? >> >> Stef >> >> _______________________________________________ >> 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

Sept. 11, 2009

Re: [Pharo-project] getting rid of these boring questions and popup

by Schwab,Wilhelm K

Stef, Yes, the popups should go away - far away :) A code mentor pane with lint rule violations would be greatly appreciated, but the modal messages are too much. Sometimes I want to save code that I know will generate errors, with reasons ranging from "I'll let it blow up and choose to implement it from the debugger" to "don't want to lose this, so let's get it accepted before I do something stupid." Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Michael Roberts Sent: Friday, September 11, 2009 4:21 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] getting rid of these boring questions and popup i would be quite happy if the "this variable is not used" was picked up by a lint rule. the "your using this variable and you haven't yet assigned a value" is sometimes nice. however, if lint/slint/slime (?) had a nice permanent UI mechanism in the browser (i haven't checked) then I would get rid the former in preference of such a framework that can point out all sorts of useful things with the code when you accept methods. could then be package / context aware etc. Mike On Fri, Sep 11, 2009 at 6:12 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guys > > I would like what you think of these wonderful popups that try to help > to write cool code but just get in my way: > Â Â Â Â "this variable is not used.... > Â Â Â Â you did not store into it.... > > Could we agree that we are adults? > and this is more a pain than anything else? > > Stef > > _______________________________________________ > 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

Sept. 11, 2009

[Pharo-project] New Pharo based on core 10446 - Win32 Installer

by Torsten Bergmann

see pharo download page or go directly to: http://gforge.inria.fr/frs/download.php/23175/setup_pharo1.0-10446-BETAdev0… -- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser

Sept. 11, 2009

Re: [Pharo-project] getting rid of these boring questions and popup

by Michael Roberts

i would be quite happy if the "this variable is not used" was picked up by a lint rule. the "your using this variable and you haven't yet assigned a value" is sometimes nice. however, if lint/slint/slime (?) had a nice permanent UI mechanism in the browser (i haven't checked) then I would get rid the former in preference of such a framework that can point out all sorts of useful things with the code when you accept methods. could then be package / context aware etc. Mike On Fri, Sep 11, 2009 at 6:12 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guys > > I would like what you think of these wonderful popups that try to help > to > write cool code but just get in my way: > Â Â Â Â "this variable is not used.... > Â Â Â Â you did not store into it.... > > Could we agree that we are adults? > and this is more a pain than anything else? > > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Sept. 11, 2009

Re: [Pharo-project] New Pharo based on core 10446

by Ramiro Diaz Trepat

Yes ! It's great to have the package browser working again :) On Fri, Sep 11, 2009 at 6:10 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > cool thanks! > > On Sep 11, 2009, at 4:44 PM, Damien Cassou wrote: > > > http://pharo-project.org/pharo-download > > > > with refactorings in the package browser. > > > > -- > > Damien Cassou > > http://damiencassou.seasidehosting.st > > > > "Lambdas are relegated to relative obscurity until Java makes them > > popular by not having them." James Iry > > > > _______________________________________________ > > 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 >

Sept. 11, 2009

Re: [Pharo-project] An important infrastructural question

by StÃ©phane Ducasse

yeap! the life of real project.....been backward compatible Stef On Sep 11, 2009, at 10:04 PM, Dale Henrichs wrote: > GemStone (GLASS) will be writing and reading "old-style" mcz files > for the foreseeable future, so backward compatibility is important. > > Dale > ----- "Lukas Renggli" <renggli(a)gmail.com> wrote: > > | > - idea: we keep the * notation but we hook into the > | tools to > | > create real package. In particular the user could > | either explicitly > | > add a method extension > | > to a package or use the* notation. The end result > | should be the star > | > notation in the cat > | > and the use of a real package in the background. > | > | It would be nice if old packages could be imported and new ones > | merged > | and exported without problems. If a package is named "Foo", then its > | categories would be represented in Monticello as > | "Foo-OriginalCategoryName" and its protocols as > | "*foo-OriginalProtocolName". This would allow full compatibility. > | > | > platform could be a problem. So lukas do you if VW uses the > | * > | > convention, I imagine at least when > | > saving code? > | > | Yes, they use the same convention. Categories are not really visible > | in VW, but they are the same as on the Pharo side. The package name > | could actually be cropped from the protocol, but they strangely > don't > | do that and still display the *. > | > | Cheers, > | 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 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 11, 2009

Re: [Pharo-project] An important infrastructural question

by StÃ©phane Ducasse

On Sep 11, 2009, at 9:33 PM, Lukas Renggli wrote: >> - idea: we keep the * notation but we hook into the >> tools to >> create real package. In particular the user could >> either explicitly >> add a method extension >> to a package or use the* notation. The end result >> should be the star >> notation in the cat >> and the use of a real package in the background. > > It would be nice if old packages could be imported and new ones merged > and exported without problems. If a package is named "Foo", then its > categories would be represented in Monticello as > "Foo-OriginalCategoryName" and its protocols as > "*foo-OriginalProtocolName". This would allow full compatibility. yes I believe that this is the way to go. (lot of hack in tools but necessary). If we do it well we will certainly improve the tools too. Because the notification should be a good support. >> platform could be a problem. So lukas do you if VW uses the * >> convention, I imagine at least when >> saving code? > > Yes, they use the same convention. Categories are not really visible > in VW, but they are the same as on the Pharo side. The package name > could actually be cropped from the protocol, but they strangely don't > do that and still display the *. Ok this is what I thought. We will do the same. > > Cheers, > 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

Sept. 11, 2009