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

[Pharo-project] chasing the double copy and paste

by StÃ©phane Ducasse

mike asked in the bugtracker "After a double paste, is the undo undoing the double paste as well? That would indicate that not to paste commands come through but rather the paste string gets duplicated." please pay attention and let us know. Stef

Dec. 3, 2009

Re: [Pharo-project] file encodings

by Michael Rueger

...and of course you should read the classic on this: http://www.joelonsoftware.com/articles/Unicode.html "There Ain't No Such Thing As Plain Text." ;-) Michael

Dec. 3, 2009

Re: [Pharo-project] file encodings

by Michael Rueger

Philippe Marschall wrote: > Tudor Girba wrote: >> Or more general, how can I find out what kind of converter I need for >> a given file? ... > You can pretend the problem doesn't exist and just use a random encoding > aka the platform default encoding. That would work if all your files > were are created on your computer and all your programs used the At least for those files it will work in almost all cases. > platform default encoding. E.g. you don't download stuff from the > internet or copy stuff off storage media (USB sticks, CDs, DVDs, ...). Well, there are some heuristics, but nothing failsafe... If the file has cr-lf, it is probably a windows file http://en.wikipedia.org/wiki/ISO/IEC_8859-1#ISO-8859-1_and_Windows-1252_con… You can check for a Unicode BOM. .html should be UTF-8 these days. Try reading UTF-8, if it fails try re-reading with platform encoding. > > The funny thing is that XML partially solves the problem because the > encoding can be put into the preamble. In fact it should if the file is > not ASCII. You can make a guess whether Yaxo supports binary input and > detecting the encoding either from the BOM or the preamble. Hmm, to be honest I'm not sure myself, but I think I (with help from others) did some work a while ago to make it read files according to the encoding entry. But maybe my memory has the wrong encoding ;-) Michael

Dec. 3, 2009

Re: [Pharo-project] ParserTreeSearcher problem (lukas can you check)

by laurent laffont

On Thu, Dec 3, 2009 at 5:07 PM, Lukas Renggli <renggli(a)gmail.com> wrote: > I think that I fixed that a long time ago. No? > > Well, if you download current pharo-web image on pharo-project.org and run code critics, it fails. Slime package loaded is Slime-lr.24. And now that your server is up again (hurrah !!), it seems to me that there's no update available. Sorry ;) (I also found bug about ParseTreeRewriter renamed to RBParserTreeRewriter) Laurent

Dec. 3, 2009

Re: [Pharo-project] Slime at work

by Lukas Renggli

Indeed the screenshots and explanation is outdated. I've added your comment to the book. That should help you go through in the latest Pharo: 1. In the browser select an item from the package you want to check, for example a class. 2. In the context menu of that item select 'browse package (p)' or 'refactoring scope > package' which both do the same. 3. In the new (yellow) browser that is scoped and should only show the code of your package browser select 'refactor > code critics'. 4. In the new browser wait until the package has finished searching. This might take a while. A progress indicator should appear after a while in the window title. 5. After completion the bold items display problems. Select one and click on 'browse' to open a view on the problems. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Dec. 3, 2009

Re: [Pharo-project] class comment displayed

by StÃ©phane Ducasse

On Dec 3, 2009, at 5:35 PM, Lukas Renggli wrote: > Hi Stef > >> I hope that the trip was good. > > Yep, just arrived home. Reboot :) > >> this was to get the comment below the class definition >> This is in the preferences at least on my image (rc1.0). > > That split class-definition/class-comment view is only available in > the ST-80 browser. I think that would be difficult to implement in OB. ok too bad because nicolas made me think that we are doing a poor job at pushing people to write comments since nobody can easily read them. > > 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

Dec. 3, 2009

Re: [Pharo-project] Why some packages are rejected from Test Coverage?

by Lukas Renggli

> :(Â Â What a pity. I have already coded itÂ :( > > And there is no way to test coverage only sub categories of a package? > Suppose I want to test the category "System-Object Storage" of the package > System. Can I do it ? if true, how? This is a test runner, not a tool to solve all possible problems. It provides an absolutely minimal implementation of method wrappers that does exactly one thing, and one thing only: calculating coverage on a per-package bases. If you want something more sophisticated you should look at the original implementation of MethodWrappers and their integration in OmniBrowser. Using these two you can conveniently select any set of methods in the image, wrap them with a custom wrapper, perform a custom action, etc. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Dec. 3, 2009

[Pharo-project] [update 1.1] #11069

by StÃ©phane Ducasse

11069 ----- Issue 1541: Settings integration part3 *added a menu entry in the world menu for the new setting browser. * added double-click handling in MorphTreeMorph * SystemSettingBrowser, double clicking on a row open a class browser on the method which declares the selected setting * do not update a SystemSettingBrowser if it is not viewed by an opened window (prevents updating of a closed but not yet garbaged window) * improved gradient background rendering (radial direction) * added System-Support-SystemSettings, Network-SystemSettings, Polymorph-SystemSettings and Monticello-SystemSettings packages * migrate all preferences from the old Browsing * migrate existing http proxy preferences * migrate existing media preferences * add settings for network user name, password, blab email, author fullname * deprecation of some old preference methods Thanks a lot alain!!!!!!

Dec. 3, 2009

Re: [Pharo-project] class comment displayed

by Lukas Renggli

Hi Stef > I hope that the trip was good. Yep, just arrived home. > this was to get the comment below the class definition > This is in the preferences at least on my image (rc1.0). That split class-definition/class-comment view is only available in the ST-80 browser. I think that would be difficult to implement in OB. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Dec. 3, 2009

Re: [Pharo-project] [Moose-dev] Re: duplication between default: and version40beta2:?

by Simon Denier

On 3 dÃ©c. 2009, at 09:40, Laval Jannik wrote: > Yeh, > > Now, I understand the process... (I am slow :) ) > > But, in this process we must specify versions and maintain it. > Is there a solution (in monticello maybe) to say a version of a > package is stable. > So in this case, we can say "I want last stable version of my > package" and we do not need to maintain ConfigurationOf. The way to do it with Metacello: ConfigurationOfXXX project latestVersion load It takes the latest stable version, i.e. one which is not marked as baseline, broken, or development. > > Maybe this discussion is more global than moose community, > So I copy it in pharo mailing list. > > Jannik > > On Dec 3, 2009, at 13:15 , Tudor Girba wrote: > >> Hi Stef, >> >> As I mentioned before, default represents the work in progress. It >> can happen that the work in progress is the same as the previously >> released version, and that is why you will see duplication. >> >> Another possibility would be to reuse the previous configuration >> and just mention the delta (of adding new packages), but I am not >> sure this would scale in the long run. >> >> So, the current process is: >> - work on default >> - when we release, we copy the method in a new baselineXXX >> - we create a hardcoded version in versionXXX >> >> Cheers, >> Doru >> >> >> -- >> www.tudorgirba.com >> >> "We cannot reach the flow of things unless we let go." >> >> >> >> _______________________________________________ >> 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 -- Simon

Dec. 3, 2009