September 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] chunk file format (unrecoverable changes)

by John Brant

On 9/8/2015 8:48 AM, Eliot Miranda wrote: > Forgive me, I don't mean to complain, but... It's rather sad now I look > at it that the specification misses a very cool thing about the format. > Glenn Krasner invented it and he's no dummy. What the specs miss out is > that the syntax for a protocol is actually a general escape mechanism. > For example in > > !Object methodsFor: 'testing'! > isUnderstood > ^false! ! > > the fileIn parser evaluates > > Object methodsFor: 'testing' > > and then asks that object to scanFrom: the stream. And the above > answers a ClassCategoryReader that reads chunks, compiling them and > adding them to the relevant category, until it finds an empty chunk > (hence ! ! is not special syntax, but actually a chunk followed by an > empty chunk). > > So one /could/, if one wanted, add another kind of reader, for example > > !Preferences loadSavedPreferences! > beCool true! > beKnowledgeable true! > rememberOnersHistorytLestOneWishesToRepeatIt true! ! > > and have this not file in, but store preferences. I think that's neat, > and it's very sad that the ANSI standard did;t define this but reduced > the mechanism to support only protocols, and thence cause people to > wonder why the syntax was so weird, when in fact it was very simple and > wonderfully extensible. Dolphin uses it to define class and method categories: !MyClass categoriesFor: #myMethod!accessing!public! ! > Now I'm not blaming the standards process; the real problem here is that > the scheme wasn't documented other than by its implementation and so the > flexibility was never made apparent to the standardizers, I think the flexibility was likely known as most (all?) other implementations at the time did it the same way and Glenn Krasner was the Vice-Chairman of the committee. However, I think some on the committee wanted a purely declarative Smalltalk so you couldn't have anything in the file that evaluated code. >and anyway > they wanted an interchange format, which is not what Squeak and Pharo > chunk readers provide; they provide an extensible format. Pharo no longer provides an extensible format. I tried to file in some Dolphin code and instead of defining a few different methods that returned chunk readers (i.e., methodsFor, categoriesForClass, categoriesFor:), I had to modify the ChunkFileFormatParser>>parseNextDeclaration method. This method has hard coded the different chunk types it accepts. John Brant

Sept. 8, 2015

Re: [Pharo-dev] when:send:to: vs. subscribe:send:to:

by Ferlicot D. Cyril

Le 08/09/2015 10:13, Stephan Eggermont a Ã©crit : > When looking at the implementation, it looks as if we should > replace all #when:send:to: by #subscribe:when:do:, not the other way > around. > > Where is this all coming from? > > Stephan > > > I think that #when:send:to: is more explicit and more understandable, but this is a personal opinion. -- Cheers Cyril

Sept. 8, 2015

Re: [Pharo-dev] WhatsUp from: 2015-09-07 until: 2015-09-20

by Damien Cassou

seaside(a)rmod.lille.inria.fr writes: > ### Here's what I've been up to since the last WhatsUp: - Misc - improve Pharo flyer - Launcher - write a student project proposal to get an intern - start mocking a new GUI - Starter kit - videos - exercices - slides - finish preparing it - send it to the usb stick creator - Mooc (new course on Pharo) - clean the build - make the build pass (fix unicode characters) - improve beamer template (for PDF slides) - new lecture with screencast (create a contact book with web interface) - Pillar - progress on PetitPillar with Cyril - rewrite the default configurations implementation - helped a bit Cyril move Pillar issues to github.com/pillar-markup/pillar - fix job - proof read changes to the documentation by Cyril - fix Pillar bash script (add missing --baseDirectory because Pharo does not know its PWD) - Books - use new Travis infrastructure (sudo: false) - proof-read of an UPBE pull request - fix jobs regarding new Pillar - redo some figures to increase print quality (300dpi) - update latex installation on a slave > ### What's next, until 2015-09-20 (*): - Pillar - release new version - some bug fixing - little enhancements -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

Sept. 8, 2015

Re: [Pharo-dev] garbage on transcript

by Marcus Denker

> On 08 Sep 2015, at 15:53, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > Hi Marcus, > > On Tue, Sep 8, 2015 at 6:28 AM, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: > >> On 08 Sep 2015, at 15:19, Eliot Miranda <eliot.miranda(a)gmail.com <mailto:eliot.miranda@gmail.com>> wrote: >> >> >> >> On Tue, Sep 8, 2015 at 5:13 AM, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: >> Yes, we do name analysis on the AST before coloring itâ¦ >> >> Even worse than the transcript output are >> >> -> it adds everything into Undeclared >> -> Playground colors variables wrong that the playground knows as the name analysis does >> not setup the requestorscope correctly. >> >> I will add issue tracker entriesâ¦ >> >> Alternatively one could simply use Shout, a specialized parser for syntax highlighting that is simple, efficient, mature and customizable. >> > > The idea was to reduce the amount of Parsers (and models of methods) in the systemâ¦ > > I understand that. But parsing for code generation is very different from the quick and simple parsing for syntax highlighting that Shout provides, and if one ends up complicating the former to make it encompass the latter then maybe that's not such a good idea. I'd rather have a number of smaller simpler parsers than one great big complex difficult to understand and full of special cases parser (think... Morphic). Just a thought. Yesâ¦ but the Shout parser is actually not that simple. SHParserST80 package linesOfCode â2581â And if you then see how much work the completion system has to do to get structural information out of the token stream it that is already in a normal AST by defaultâ¦ Until now the only real change to the RB Parser is the feature to generate an error node for syntactically wrong input. (#parseFaultyExpression/#parseFaultyMethod). Everything else was ok as is. The AST is unchanged (and we therefore use the same AST for the RB Engine, the Compiler and the syntax highlighter). Marcus

Sept. 8, 2015

Re: [Pharo-dev] garbage on transcript

by Eliot Miranda

Hi Marcus, On Tue, Sep 8, 2015 at 6:28 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 08 Sep 2015, at 15:19, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > > > On Tue, Sep 8, 2015 at 5:13 AM, Marcus Denker <marcus.denker(a)inria.fr> > wrote: > >> Yes, we do name analysis on the AST before coloring itâ¦ >> >> Even worse than the transcript output are >> >> -> it adds everything into Undeclared >> -> Playground colors variables wrong that the playground knows as the >> name analysis does >> not setup the requestorscope correctly. >> >> I will add issue tracker entriesâ¦ >> > > Alternatively one could simply use Shout, a specialized parser for syntax > highlighting that is simple, efficient, mature and customizable. > > > > The idea was to reduce the amount of Parsers (and models of methods) in > the systemâ¦ > I understand that. But parsing for code generation is very different from the quick and simple parsing for syntax highlighting that Shout provides, and if one ends up complicating the former to make it encompass the latter then maybe that's not such a good idea. I'd rather have a number of smaller simpler parsers than one great big complex difficult to understand and full of special cases parser (think... Morphic). Just a thought. Marcus > _,,,^..^,,,_ best, Eliot

Sept. 8, 2015

Re: [Pharo-dev] chunk file format (unrecoverable changes)

by Eliot Miranda

Hi Nicolai, On Mon, Sep 7, 2015 at 1:21 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > 2015-09-07 20:10 GMT+02:00 Eliot Miranda <eliot.miranda(a)gmail.com>: > >> >> >> On Sun, Sep 6, 2015 at 12:56 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: >> >>> Do we have a documentation about the format of >>> - class definitions >>> - methods >>> - class comments >>> for the changes file ? >>> >> >> >> Google "specification of smalltalk chunk format" and you will see: >> >> Overviews: Chunk File Format >> <https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uac…> >> Smalltalk Interchange Format - Draft Smalltalk Standard v1.9 >> <https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=2&cad=rja&uac…> >> The Smalltalk fileOut format - 1 >> <https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=3&cad=rja&uac…> >> >> and more. >> > > > Thank you eliot > (should have google that myself !) > > >> >> >>> >>> I am asking because some entries are using two separator >>> "! !" >>> and some only one >>> "!" >>> >> >> Indeed. It's in the spec. ! ! ends a run of methods in the same >> protocol. ! ends a method or a doit, etc. Read the spec. >> > > ah! grouping multiple methods for one protocol. > Forgive me, I don't mean to complain, but... It's rather sad now I look at it that the specification misses a very cool thing about the format. Glenn Krasner invented it and he's no dummy. What the specs miss out is that the syntax for a protocol is actually a general escape mechanism. For example in !Object methodsFor: 'testing'! isUnderstood ^false! ! the fileIn parser evaluates Object methodsFor: 'testing' and then asks that object to scanFrom: the stream. And the above answers a ClassCategoryReader that reads chunks, compiling them and adding them to the relevant category, until it finds an empty chunk (hence ! ! is not special syntax, but actually a chunk followed by an empty chunk). So one /could/, if one wanted, add another kind of reader, for example !Preferences loadSavedPreferences! beCool true! beKnowledgeable true! rememberOnersHistorytLestOneWishesToRepeatIt true! ! and have this not file in, but store preferences. I think that's neat, and it's very sad that the ANSI standard did;t define this but reduced the mechanism to support only protocols, and thence cause people to wonder why the syntax was so weird, when in fact it was very simple and wonderfully extensible. Now I'm not blaming the standards process; the real problem here is that the scheme wasn't documented other than by its implementation and so the flexibility was never made apparent to the standardizers, and anyway they wanted an interchange format, which is not what Squeak and Pharo chunk readers provide; they provide an extensible format. The ANSI standard /could/ however have specified that the syntax is indeed extensible as described, but that conforming implementations are only expected to provide ClassCategoryReaders, and are expected to raise an error if given expressions they don't recognize, or some such. Also, given this history you can see why a single ! following a method definition isn't seen anymore; we've put the stamp information in the ClassCategoryreader so it can only parse a single method. If we'd done something like this (and I'm not suggesting that's a good idea) !Object methodsFor: 'testing'! [stamp: 'mad 01/04/2015 12:00'] isUnderstood ^#barely! [stamp: 'mad 01/04/2015 12:01'] isMisunderstood ^#almostCertainly! ! we'd still see the single !'s after methods. Two key points for me are - specify carefully and visibly - extensible standards are better than fixed standards And we have a problem with the "Recover lost changes" browser >>> (https://pharo.fogbugz.com/f/cases/16498/unrecoverable-changes) >>> and I am not sure if this is a bug on the code importer >>> or if it is a bug on how we write changes to the changes file. >>> >> _,,,^..^,,,_ best, Eliot

Sept. 8, 2015

Re: [Pharo-dev] garbage on transcript

by Marcus Denker

> On 08 Sep 2015, at 15:19, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > > > On Tue, Sep 8, 2015 at 5:13 AM, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: > Yes, we do name analysis on the AST before coloring itâ¦ > > Even worse than the transcript output are > > -> it adds everything into Undeclared > -> Playground colors variables wrong that the playground knows as the name analysis does > not setup the requestorscope correctly. > > I will add issue tracker entriesâ¦ > > Alternatively one could simply use Shout, a specialized parser for syntax highlighting that is simple, efficient, mature and customizable. > The idea was to reduce the amount of Parsers (and models of methods) in the systemâ¦ Marcus

Sept. 8, 2015

Re: [Pharo-dev] garbage on transcript

by Eliot Miranda

On Tue, Sep 8, 2015 at 5:13 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Yes, we do name analysis on the AST before coloring itâ¦ > > Even worse than the transcript output are > > -> it adds everything into Undeclared > -> Playground colors variables wrong that the playground knows as the name > analysis does > not setup the requestorscope correctly. > > I will add issue tracker entriesâ¦ > Alternatively one could simply use Shout, a specialized parser for syntax highlighting that is simple, efficient, mature and customizable. > > Marcus > > On 08 Sep 2015, at 08:09, stepharo <stepharo(a)free.fr> wrote: > > > > Hi > > > > when I define methods and the Transcript is open I get such kind of > trace and I do not get where it comes from. > > I think that this is the syntactical coloring. > > Would be good to avoid because this is annoying. > > > > StoreImporter>>messageSelectorAndArgumentNames (statements is Undeclared) > > > > UndefinedObject>>noMethod (messageSelectorAndArgumentNames is Undeclared) > > > > Stef > > > > > -- _,,,^..^,,,_ best, Eliot

Sept. 8, 2015

Re: [Pharo-dev] garbage on transcript

by Marcus Denker

Yes, we do name analysis on the AST before coloring itâ¦ Even worse than the transcript output are -> it adds everything into Undeclared -> Playground colors variables wrong that the playground knows as the name analysis does not setup the requestorscope correctly. I will add issue tracker entriesâ¦ Marcus > On 08 Sep 2015, at 08:09, stepharo <stepharo(a)free.fr> wrote: > > Hi > > when I define methods and the Transcript is open I get such kind of trace and I do not get where it comes from. > I think that this is the syntactical coloring. > Would be good to avoid because this is annoying. > > StoreImporter>>messageSelectorAndArgumentNames (statements is Undeclared) > > UndefinedObject>>noMethod (messageSelectorAndArgumentNames is Undeclared) > > Stef >

Sept. 8, 2015

Re: [Pharo-dev] TextAttributes in source code or class comment?

by Henrik Johansen

> On 08 Sep 2015, at 11:03 , Martin Dias <tinchodias(a)gmail.com> wrote: > > On Sat, Sep 5, 2015 at 1:10 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: >> The same for the ]lang[ tag (see issue 15750) > > Ok. But I still don't know how to add a url to a method's source code > or comment from the UI. > > I mean, people with a non-English keyboard can produce source code > with ]lang[, but how can I produce a ]style[ ? > > MartÃn The whole mechanism is quite broken in Pharo4 upwards:

Sept. 8, 2015

Re: [Pharo-dev] TextAttributes in source code or class comment?

by Nicolai Hess

2015-09-08 11:03 GMT+02:00 Martin Dias <tinchodias(a)gmail.com>: > On Sat, Sep 5, 2015 at 1:10 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > > The same for the ]lang[ tag (see issue 15750) > > Ok. But I still don't know how to add a url to a method's source code > or comment from the UI. > > I mean, people with a non-English keyboard can produce source code > with ]lang[, but how can I produce a ]style[ ? > Hi Martin, In squeak, you can open a "choose style" dialog (select some text and use shortcut cmd+6). This lets you choose a text color or text links. For example, this is working in the class comment editor too, you can open the comment for class Morph, select a word like "Rectangle" and put a link to that class definition. This style attributes are first only a part of the Text instance, but saving or file out the class definition will include this style attributes with the ]style[ tag. Writing the style code text is not supported in pharo anymore. Changing the style (color and text links) with cmd+6 does not work in Rubrics text components anymore. It is working with the old PluggableTextMorph (but only color attributes - no links). Reading Text with style attributes is still working in Pharo (only color and emphasis, no text links). For example, put this "styled" text in a Workspace and inspect it: 'Red Gree Blue! ]style[(3 1 4 1 4)f1cred;b,f1b,f1cgreen;b,f1b,f1cblue;b!' readStream nextChunkText > > MartÃn > > > > > 2015-09-05 12:06 GMT+02:00 Martin Dias <tinchodias(a)gmail.com>: > >> > >> Hi all > >> > >> On Sat, Sep 5, 2015 at 3:44 AM, Ben Coman <btc(a)openinworld.com> wrote: > >> > On Sat, Sep 5, 2015 at 4:43 AM, Eliot Miranda < > eliot.miranda(a)gmail.com> > >> > wrote: > >> >> > >> >> On Sep 4, 2015, at 1:33 PM, stepharo <stepharo(a)free.fr> wrote: > >> >> > >> >> Nobody defines urls in method comment anymore. > >> >> > >> >> I do. Several places in the Cog JIT contain irks to specification > >> >> documents. I don't care how its implemented (providing it's > preserved > >> >> in > >> >> text, or maybe have the pretty-printer scan comments for http://. > But > >> >> it is > >> >> sad that we can't have hyperlinks in text. > >> >> > >> >> Look I know the implementation stinks, but it can be fixed. But if > the > >> >> functionality is lost the system is weakened. Instead of asking what > >> >> you > >> >> can get rid if why not ask what you can reimplement or enhance more > >> >> elegantly. > >> > > >> > Its a reasonable strategy to start the discussion at the extreme end > >> > and work back from there :) But if its being used we should think > >> > harder about it. What alternatives/workarounds are there? > >> > > >> > First just to clarify, the aim is to remove Text from the image for > >> > the boot-strap? > >> > >> Yes :) I heard that we want to do cut the dependency to Text-Core, so > >> I browsed how to do it. > >> > >> Ben, there is an explanation about ]style[ in the class comment of > >> RemoteString. > >> > >> Eliot, I didn't thought that somebody was using Text. In fact, I don't > >> know how to do it in Pharo... how do you do? > >> I found that ChangeRecord>>fileIn uses #newTextChunk to parse, but I > >> just tested filing-in the attached .st file and it doesn't work. I > >> guess the new CodeImporter replaced the ChangeRecord implementation, > >> and it raises an error when ]style[. > >> > >> MartÃn > >> > >> > >> > > >> > 1. Save the text internally as a string in the stream format and > >> > up-convert to Text only when its being displayed? But I guess these > >> > styles aren't restricted to just occurring in comments and maybe cause > >> > problem for compilation ?? > >> > > >> > 2. As a stepping stone, introduce a TextPlaceholder class within > >> > minimal interface required by compilation which simply strips out all > >> > styles when Text is missing from the Image. When Text is present it > >> > #becomes back to it. Maybe risks loosing styles editing is done on > >> > the raw-stream-format. Maybe any editor would show the raw ]style[ > >> > and the compiler asks for #source which strips styles out. > >> > > >> > 3. Introduce Pillar and convert across. What are the requirements? > >> > a. URLs > >> > b. Class/method links > >> > c. Would you expect that Pillar can only appear in comments? Or > >> > in-line with code? > >> > d. Colouring? > >> > ...? > >> > > >> > btw, I haven't come across this before. Can someone point me to some > >> > url & styled code where I can have a look at it > >> > > >> > cheers -ben > >> > > >> >> Christ you're even using minis paced fonts. It's like the dark > >> >> ages in there ;-) > >> >> > >> >> In addition would prefer to have an explicit syntax as in Pillar or > >> >> html to > >> >> represent > >> >> an hyperlink. We could have > >> >> *Class>>#method* when pillar is not loaded and else a nicer > >> >> representation. > >> >> ctrl-click on a class should jump on it already and we could map it > to > >> >> *Class>>#method* > >> >> > >> >> In class comments we should use pillar and get a real text renderer. > >> >> > >> >> > >> >> Hi Martin, > >> >> > >> >> On Fri, Sep 4, 2015 at 8:13 AM, Martin Dias <tinchodias(a)gmail.com> > >> >> wrote: > >> >>> > >> >>> Hi all, > >> >>> > >> >>> The source code of a method could be a Text, with TextAttributes. In > >> >>> such > >> >>> case, it will be written down to a stream with a "]style[" suffix. > >> >>> Through a > >> >>> special parsing, the system can reconstruct the original Text. I > think > >> >>> the > >> >>> use of Text in source code or class comments is discouraged, but I > >> >>> understand we kept support for some backward compatibility. Now, may > >> >>> be it's > >> >>> time to remove this feature. > >> >>> > >> >>> With Pablo, we looked for uses of ]style[ in the .sources and > .changes > >> >>> files of a new Pharo 5.0, and there are no real uses. It appears in > >> >>> some > >> >>> comments only, as examples. > >> >>> > >> >>> We tried to find past discussions about this feature, because we're > >> >>> sure > >> >>> there were, but we couldn't. > >> >>> > >> >>> So, the questions is: > >> >>> > >> >>> Can we remove support for text in source code or class comments > in > >> >>> Pharo 5.0? > >> >> > >> >> > >> >> IIUC, ]style[ also supports things like embedding URL links and > method > >> >> references in class comments. So I would request that it /not/ be > >> >> removed. > >> >> It is very useful to put clickable links in class comments. > >> >> > >> >>> > >> >>> > >> >>> I think I can propose a slice. > >> >>> > >> >>> Regards, > >> >>> MartÃn > >> >>> PS: I was trying to cut dependencies of Text-Core with > System-Changes > >> >>> and > >> >>> System-Changes. > >> >> > >> >> > >> >> > >> >> > >> >> -- > >> >> _,,,^..^,,,_ > >> >> best, Eliot > >> >> > >> >> > >> > > > > > >

Sept. 8, 2015

Re: [Pharo-dev] ANSICompatibility package

by Jan Vrany

Hi, On Tue, 2015-09-08 at 12:04 +0200, H. Hirzel wrote: > Jan, > > have a look at > > http://wiki.squeak.org/squeak/3172 > > ca 2800 tests Thanks for this, I'll make a note... > > First thing to do would be to do an quick analysis of the porting > effort. > > The question is why do not need a ANSI compatibility package. > > Grease > http://www.smalltalkhub.com/#!/~Seaside/Grease11 > is also an issue to look into for creating portable code. > Well: "Grease enhances the ANSI Smalltalk standard. With only a few exceptions, we assume platforms are fully ANSI-compliant." So on Pharo, Grease would not help as, IIUC, Pharo is not and does now want to be, ANSI compliant. This means that ANSICompatibility is (will be) needed for Grease if Pharo keeps removing ANSI methods, right? > In the end the incompatible methods in Pharo are often not all that > many. > This means that what you mention as 'quick and dirty' is actually > quite a good approach: You test the Smalltalk platform you are using > for the availability of certain methods and act accordingly. Except it makes the code a lot less comprehensible... Anyway, problem solved :-) Jan > > > --Hannes > > On 9/8/15, Jan Vrany <jan.vrany(a)fit.cvut.cz> wrote: > > On Tue, 2015-09-08 at 12:04 +0800, Ben Coman wrote: > > > On Tue, Sep 8, 2015 at 9:21 AM, Jan Vrany <jan.vrany(a)fit.cvut.cz> > > > wrote: > > > > Hi, > > > > > > > > is there actually such a thing like ANSICompatibility package? > > > > (it has been mentioned here lately, but I cannot find it) > > > > > > > > Thanks, Jan > > > > > > > > > > I made it up for the purpose of discussion to see what interest > > > it > > > generated. > > > Should we start one ? > > > > Well, let's put it this way: if there would be one, I'd use it and > > even > > contribute adding missing stuff. But I certainly have no time to > > start > > yet another project, having way too much on my plate already. > > > > So `(passes respondsTo: #removeAtIndex:) ifTrue:[...]` would do it. > > Quick and dirty, but no time and desire to fight Pharo :-) > > > > Cheers, Jan > > > > > cheers -ben > > > > > > > >

Sept. 8, 2015

Re: [Pharo-dev] when:send:to: vs. subscribe:send:to:

by Henrik Johansen

> On 08 Sep 2015, at 10:13 , Stephan Eggermont <stephan(a)stack.nl> wrote: > > On 06-09-15 10:37, stepharo wrote: >> >> >> Le 5/9/15 22:42, Tudor Girba a Ã©crit : >>> +1. >>> >>> We already deprecated on:send:to:/on:do: and I think we should do the >>> same for the subscribe:send:to:. >> Thanks Doru. I thought the same. Because each time I read subscribe: my >> mind stops for about half or a second until I remember that this is >> the same as when: send: to: > > When looking at the implementation, it looks as if we should > replace all #when:send:to: by #subscribe:when:do:, not the other way > around. > > Where is this all coming from? > > Stephan > > > An attempt at compatibility. IIRC; the original VW Announcements use when:send:to: (polymorphic with the old event system), while Lukas' implementation from Seaside use(d/s) subscribe:when:do: My 2c; If you need to pick one over the other, choose when:send:to. Cheers, Henry

Sept. 8, 2015

Re: [Pharo-dev] ANSICompatibility package

by H. Hirzel

Jan, have a look at http://wiki.squeak.org/squeak/3172 ca 2800 tests First thing to do would be to do an quick analysis of the porting effort. The question is why do not need a ANSI compatibility package. Grease http://www.smalltalkhub.com/#!/~Seaside/Grease11 is also an issue to look into for creating portable code. In the end the incompatible methods in Pharo are often not all that many. This means that what you mention as 'quick and dirty' is actually quite a good approach: You test the Smalltalk platform you are using for the availability of certain methods and act accordingly. --Hannes On 9/8/15, Jan Vrany <jan.vrany(a)fit.cvut.cz> wrote: > On Tue, 2015-09-08 at 12:04 +0800, Ben Coman wrote: >> On Tue, Sep 8, 2015 at 9:21 AM, Jan Vrany <jan.vrany(a)fit.cvut.cz> >> wrote: >> > Hi, >> > >> > is there actually such a thing like ANSICompatibility package? >> > (it has been mentioned here lately, but I cannot find it) >> > >> > Thanks, Jan >> > >> >> I made it up for the purpose of discussion to see what interest it >> generated. >> Should we start one ? > > Well, let's put it this way: if there would be one, I'd use it and even > contribute adding missing stuff. But I certainly have no time to start > yet another project, having way too much on my plate already. > > So `(passes respondsTo: #removeAtIndex:) ifTrue:[...]` would do it. > Quick and dirty, but no time and desire to fight Pharo :-) > > Cheers, Jan > >> cheers -ben >> > >

Sept. 8, 2015

Re: [Pharo-dev] TextAttributes in source code or class comment?

by Eliot Miranda

Hi Martin, Sent from my iPhone > On Sep 5, 2015, at 3:06 AM, Martin Dias <tinchodias(a)gmail.com> wrote: > > Hi all > >> On Sat, Sep 5, 2015 at 3:44 AM, Ben Coman <btc(a)openinworld.com> wrote: >>> On Sat, Sep 5, 2015 at 4:43 AM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >>> >>> On Sep 4, 2015, at 1:33 PM, stepharo <stepharo(a)free.fr> wrote: >>> >>> Nobody defines urls in method comment anymore. >>> >>> I do. Several places in the Cog JIT contain irks to specification >>> documents. I don't care how its implemented (providing it's preserved in >>> text, or maybe have the pretty-printer scan comments for http://. But it is >>> sad that we can't have hyperlinks in text. >>> >>> Look I know the implementation stinks, but it can be fixed. But if the >>> functionality is lost the system is weakened. Instead of asking what you >>> can get rid if why not ask what you can reimplement or enhance more >>> elegantly. >> >> Its a reasonable strategy to start the discussion at the extreme end >> and work back from there :) But if its being used we should think >> harder about it. What alternatives/workarounds are there? >> >> First just to clarify, the aim is to remove Text from the image for >> the boot-strap? > > Yes :) I heard that we want to do cut the dependency to Text-Core, so > I browsed how to do it. > > Ben, there is an explanation about ]style[ in the class comment of RemoteString. > > Eliot, I didn't thought that somebody was using Text. In fact, I don't > know how to do it in Pharo... how do you do? I develop the VM in Squeak. There's a menu pick in the squeak text editor that lets you do it. In the hierarchy of emphasis types there's a class called something like TextURL. I'll take a look soon and check. > I found that ChangeRecord>>fileIn uses #newTextChunk to parse, but I > just tested filing-in the attached .st file and it doesn't work. I > guess the new CodeImporter replaced the ChangeRecord implementation, > and it raises an error when ]style[. > > MartÃn > > >> >> 1. Save the text internally as a string in the stream format and >> up-convert to Text only when its being displayed? But I guess these >> styles aren't restricted to just occurring in comments and maybe cause >> problem for compilation ?? >> >> 2. As a stepping stone, introduce a TextPlaceholder class within >> minimal interface required by compilation which simply strips out all >> styles when Text is missing from the Image. When Text is present it >> #becomes back to it. Maybe risks loosing styles editing is done on >> the raw-stream-format. Maybe any editor would show the raw ]style[ >> and the compiler asks for #source which strips styles out. >> >> 3. Introduce Pillar and convert across. What are the requirements? >> a. URLs >> b. Class/method links >> c. Would you expect that Pillar can only appear in comments? Or >> in-line with code? >> d. Colouring? >> ...? >> >> btw, I haven't come across this before. Can someone point me to some >> url & styled code where I can have a look at it >> >> cheers -ben >> >>> Christ you're even using minis paced fonts. It's like the dark >>> ages in there ;-) >>> >>> In addition would prefer to have an explicit syntax as in Pillar or html to >>> represent >>> an hyperlink. We could have >>> *Class>>#method* when pillar is not loaded and else a nicer >>> representation. >>> ctrl-click on a class should jump on it already and we could map it to >>> *Class>>#method* >>> >>> In class comments we should use pillar and get a real text renderer. >>> >>> >>> Hi Martin, >>> >>>> On Fri, Sep 4, 2015 at 8:13 AM, Martin Dias <tinchodias(a)gmail.com> wrote: >>>> >>>> Hi all, >>>> >>>> The source code of a method could be a Text, with TextAttributes. In such >>>> case, it will be written down to a stream with a "]style[" suffix. Through a >>>> special parsing, the system can reconstruct the original Text. I think the >>>> use of Text in source code or class comments is discouraged, but I >>>> understand we kept support for some backward compatibility. Now, may be it's >>>> time to remove this feature. >>>> >>>> With Pablo, we looked for uses of ]style[ in the .sources and .changes >>>> files of a new Pharo 5.0, and there are no real uses. It appears in some >>>> comments only, as examples. >>>> >>>> We tried to find past discussions about this feature, because we're sure >>>> there were, but we couldn't. >>>> >>>> So, the questions is: >>>> >>>> Can we remove support for text in source code or class comments in >>>> Pharo 5.0? >>> >>> >>> IIUC, ]style[ also supports things like embedding URL links and method >>> references in class comments. So I would request that it /not/ be removed. >>> It is very useful to put clickable links in class comments. >>> >>>> >>>> >>>> I think I can propose a slice. >>>> >>>> Regards, >>>> MartÃn >>>> PS: I was trying to cut dependencies of Text-Core with System-Changes and >>>> System-Changes. >>> >>> >>> >>> >>> -- >>> _,,,^..^,,,_ >>> best, Eliot > <HelpOnHelp class-example.st>

Sept. 8, 2015

Re: [Pharo-dev] TextAttributes in source code or class comment?

by Martin Dias

On Sat, Sep 5, 2015 at 1:10 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > The same for the ]lang[ tag (see issue 15750) Ok. But I still don't know how to add a url to a method's source code or comment from the UI. I mean, people with a non-English keyboard can produce source code with ]lang[, but how can I produce a ]style[ ? MartÃn > > 2015-09-05 12:06 GMT+02:00 Martin Dias <tinchodias(a)gmail.com>: >> >> Hi all >> >> On Sat, Sep 5, 2015 at 3:44 AM, Ben Coman <btc(a)openinworld.com> wrote: >> > On Sat, Sep 5, 2015 at 4:43 AM, Eliot Miranda <eliot.miranda(a)gmail.com> >> > wrote: >> >> >> >> On Sep 4, 2015, at 1:33 PM, stepharo <stepharo(a)free.fr> wrote: >> >> >> >> Nobody defines urls in method comment anymore. >> >> >> >> I do. Several places in the Cog JIT contain irks to specification >> >> documents. I don't care how its implemented (providing it's preserved >> >> in >> >> text, or maybe have the pretty-printer scan comments for http://. But >> >> it is >> >> sad that we can't have hyperlinks in text. >> >> >> >> Look I know the implementation stinks, but it can be fixed. But if the >> >> functionality is lost the system is weakened. Instead of asking what >> >> you >> >> can get rid if why not ask what you can reimplement or enhance more >> >> elegantly. >> > >> > Its a reasonable strategy to start the discussion at the extreme end >> > and work back from there :) But if its being used we should think >> > harder about it. What alternatives/workarounds are there? >> > >> > First just to clarify, the aim is to remove Text from the image for >> > the boot-strap? >> >> Yes :) I heard that we want to do cut the dependency to Text-Core, so >> I browsed how to do it. >> >> Ben, there is an explanation about ]style[ in the class comment of >> RemoteString. >> >> Eliot, I didn't thought that somebody was using Text. In fact, I don't >> know how to do it in Pharo... how do you do? >> I found that ChangeRecord>>fileIn uses #newTextChunk to parse, but I >> just tested filing-in the attached .st file and it doesn't work. I >> guess the new CodeImporter replaced the ChangeRecord implementation, >> and it raises an error when ]style[. >> >> MartÃn >> >> >> > >> > 1. Save the text internally as a string in the stream format and >> > up-convert to Text only when its being displayed? But I guess these >> > styles aren't restricted to just occurring in comments and maybe cause >> > problem for compilation ?? >> > >> > 2. As a stepping stone, introduce a TextPlaceholder class within >> > minimal interface required by compilation which simply strips out all >> > styles when Text is missing from the Image. When Text is present it >> > #becomes back to it. Maybe risks loosing styles editing is done on >> > the raw-stream-format. Maybe any editor would show the raw ]style[ >> > and the compiler asks for #source which strips styles out. >> > >> > 3. Introduce Pillar and convert across. What are the requirements? >> > a. URLs >> > b. Class/method links >> > c. Would you expect that Pillar can only appear in comments? Or >> > in-line with code? >> > d. Colouring? >> > ...? >> > >> > btw, I haven't come across this before. Can someone point me to some >> > url & styled code where I can have a look at it >> > >> > cheers -ben >> > >> >> Christ you're even using minis paced fonts. It's like the dark >> >> ages in there ;-) >> >> >> >> In addition would prefer to have an explicit syntax as in Pillar or >> >> html to >> >> represent >> >> an hyperlink. We could have >> >> *Class>>#method* when pillar is not loaded and else a nicer >> >> representation. >> >> ctrl-click on a class should jump on it already and we could map it to >> >> *Class>>#method* >> >> >> >> In class comments we should use pillar and get a real text renderer. >> >> >> >> >> >> Hi Martin, >> >> >> >> On Fri, Sep 4, 2015 at 8:13 AM, Martin Dias <tinchodias(a)gmail.com> >> >> wrote: >> >>> >> >>> Hi all, >> >>> >> >>> The source code of a method could be a Text, with TextAttributes. In >> >>> such >> >>> case, it will be written down to a stream with a "]style[" suffix. >> >>> Through a >> >>> special parsing, the system can reconstruct the original Text. I think >> >>> the >> >>> use of Text in source code or class comments is discouraged, but I >> >>> understand we kept support for some backward compatibility. Now, may >> >>> be it's >> >>> time to remove this feature. >> >>> >> >>> With Pablo, we looked for uses of ]style[ in the .sources and .changes >> >>> files of a new Pharo 5.0, and there are no real uses. It appears in >> >>> some >> >>> comments only, as examples. >> >>> >> >>> We tried to find past discussions about this feature, because we're >> >>> sure >> >>> there were, but we couldn't. >> >>> >> >>> So, the questions is: >> >>> >> >>> Can we remove support for text in source code or class comments in >> >>> Pharo 5.0? >> >> >> >> >> >> IIUC, ]style[ also supports things like embedding URL links and method >> >> references in class comments. So I would request that it /not/ be >> >> removed. >> >> It is very useful to put clickable links in class comments. >> >> >> >>> >> >>> >> >>> I think I can propose a slice. >> >>> >> >>> Regards, >> >>> MartÃn >> >>> PS: I was trying to cut dependencies of Text-Core with System-Changes >> >>> and >> >>> System-Changes. >> >> >> >> >> >> >> >> >> >> -- >> >> _,,,^..^,,,_ >> >> best, Eliot >> >> >> >> >> > > >

Sept. 8, 2015

Re: [Pharo-dev] ANSICompatibility package

by Jan Vrany

On Tue, 2015-09-08 at 12:04 +0800, Ben Coman wrote: > On Tue, Sep 8, 2015 at 9:21 AM, Jan Vrany <jan.vrany(a)fit.cvut.cz> > wrote: > > Hi, > > > > is there actually such a thing like ANSICompatibility package? > > (it has been mentioned here lately, but I cannot find it) > > > > Thanks, Jan > > > > I made it up for the purpose of discussion to see what interest it > generated. > Should we start one ? Well, let's put it this way: if there would be one, I'd use it and even contribute adding missing stuff. But I certainly have no time to start yet another project, having way too much on my plate already. So `(passes respondsTo: #removeAtIndex:) ifTrue:[...]` would do it. Quick and dirty, but no time and desire to fight Pharo :-) Cheers, Jan > cheers -ben >

Sept. 8, 2015

Re: [Pharo-dev] when:send:to: vs. subscribe:send:to:

by Stephan Eggermont

On 06-09-15 10:37, stepharo wrote: > > > Le 5/9/15 22:42, Tudor Girba a Ã©crit : >> +1. >> >> We already deprecated on:send:to:/on:do: and I think we should do the >> same for the subscribe:send:to:. > Thanks Doru. I thought the same. Because each time I read subscribe: my > mind stops for about half or a second until I remember that this is > the same as when: send: to: When looking at the implementation, it looks as if we should replace all #when:send:to: by #subscribe:when:do:, not the other way around. Where is this all coming from? Stephan

Sept. 8, 2015

Re: [Pharo-dev] garbage on transcript

by Thierry Goubier

Hi Stef, yes, this is annoying. Thierry Le 08/09/2015 08:09, stepharo a Ã©crit : > Hi > > when I define methods and the Transcript is open I get such kind of > trace and I do not get where it comes from. > I think that this is the syntactical coloring. > Would be good to avoid because this is annoying. > > StoreImporter>>messageSelectorAndArgumentNames (statements is Undeclared) > > UndefinedObject>>noMethod (messageSelectorAndArgumentNames is Undeclared) > > Stef > >

Sept. 8, 2015

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50312 Home: https://github.com/pharo-project/pharo-core

Sept. 8, 2015

[pharo-project/pharo-core] cb6342: 50312

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: cb634202202449e568ea5a8ee049fa49b43dcaed https://github.com/pharo-project/pharo-core/commit/cb634202202449e568ea5a8e… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-09-08 (Tue, 08 Sep 2015) Changed paths: M ConfigurationOfCatalog.package/ConfigurationOfCatalog.class/instance/symbolic versions/stable_.st A ConfigurationOfCatalog.package/ConfigurationOfCatalog.class/instance/versions/version08_.st M Morphic-Core.package/WorldState.class/class/world menu items/saveAs.st M Nautilus.package/AbstractNautilusUI.class/instance/private/runClassTests_notifying_.st M Nautilus.package/AbstractNautilusUI.class/instance/private/runTestsOfClass_notifying_.st A Polymorph-Widgets.package/TEasilyThemed.class/instance/services/fileSave_initialAnswer_extensions_path_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50311.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50312.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50311.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50312.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Tool-Catalog.package/CatalogBrowser.class/README.md A Tool-Catalog.package/CatalogBrowser.class/instance/actions/defineAllRepositoriesInMCBrowser.st A Tool-Catalog.package/CatalogBrowser.class/instance/actions/defineCurrentVersionRepositoryInMCBrowser.st R Tool-Catalog.package/CatalogBrowser.class/instance/building/installStableVersionButton_.st R Tool-Catalog.package/CatalogBrowser.class/instance/building/installStableVersionMenuItem_.st R Tool-Catalog.package/CatalogBrowser.class/instance/building/loadConfigurationButton_.st R Tool-Catalog.package/CatalogBrowser.class/instance/building/loadConfigurationMenuItem_.st A Tool-Catalog.package/CatalogBrowser.class/instance/menu/defineAllRepositoriesInMCBrowserButton_.st A Tool-Catalog.package/CatalogBrowser.class/instance/menu/defineCurrentVersionRepositoryButton_.st A Tool-Catalog.package/CatalogBrowser.class/instance/menu/installStableVersionButton_.st A Tool-Catalog.package/CatalogBrowser.class/instance/menu/installStableVersionMenuItem_.st A Tool-Catalog.package/CatalogBrowser.class/instance/menu/loadConfigurationButton_.st A Tool-Catalog.package/CatalogBrowser.class/instance/menu/loadConfigurationMenuItem_.st A Tool-Catalog.package/CatalogBrowser.class/instance/private - utilities/availableRepositoryURLStrings.st M Tool-Catalog.package/CatalogBrowser.class/instance/private - utilities/buildContextMenuOn_.st A Tool-Catalog.package/CatalogBrowser.class/instance/private - utilities/repositoryObjectFromURLString_.st M Tool-Catalog.package/CatalogProject.class/README.md R Tool-Catalog.package/CatalogProject.class/class/accessing/repositoryNames.st A Tool-Catalog.package/CatalogProject.class/class/accessing/repositoryURLToNameMappings.st A Tool-Catalog.package/CatalogProject.class/class/private/availableRepositoryURLStrings.st R Tool-Catalog.package/CatalogProject.class/class/private/createRepositoryNames.st A Tool-Catalog.package/CatalogProject.class/class/private/createRepositoryURLtoNameMappings.st A Tool-Catalog.package/CatalogProject.class/class/private/pharoCurrentDottedName.st A Tool-Catalog.package/CatalogProject.class/class/private/pharoCurrentMajorName.st A Tool-Catalog.package/CatalogProject.class/class/private/pharoDistributionRepository.st M Tool-Catalog.package/CatalogProject.class/instance/accessing/allKeywords.st R Tool-Catalog.package/CatalogProject.class/instance/accessing/repository.st A Tool-Catalog.package/CatalogProject.class/instance/accessing/repositoryName.st M Tool-Catalog.package/CatalogProject.class/instance/testing/isAvailableForCurrentPharo.st M Tool-Catalog.package/CatalogProvider.class/README.md Log Message: ----------- 50312 16496 Provide context menu icons in Catalog browser https://pharo.fogbugz.com/f/cases/16496 15374 exception handling when running tests in Nautilus https://pharo.fogbugz.com/f/cases/15374 16511 Smalltalk saveAs should include the current image name as the initial text in the file dialogue https://pharo.fogbugz.com/f/cases/16511 http://files.pharo.org/image/50/50312.zip

Sept. 8, 2015

garbage on transcript

by stepharo

Hi when I define methods and the Transcript is open I get such kind of trace and I do not get where it comes from. I think that this is the syntactical coloring. Would be good to avoid because this is annoying. StoreImporter>>messageSelectorAndArgumentNames (statements is Undeclared) UndefinedObject>>noMethod (messageSelectorAndArgumentNames is Undeclared) Stef

Sept. 8, 2015

Re: [Pharo-dev] ANSICompatibility package

by Ben Coman

On Tue, Sep 8, 2015 at 9:21 AM, Jan Vrany <jan.vrany(a)fit.cvut.cz> wrote: > Hi, > > is there actually such a thing like ANSICompatibility package? > (it has been mentioned here lately, but I cannot find it) > > Thanks, Jan > I made it up for the purpose of discussion to see what interest it generated. Should we start one ? cheers -ben

Sept. 8, 2015

ANSICompatibility package

by Jan Vrany

Hi, is there actually such a thing like ANSICompatibility package? (it has been mentioned here lately, but I cannot find it) Thanks, Jan

Sept. 8, 2015

Re: [Pharo-dev] ensure: and assignments RB Rule

by Eliot Miranda

Sent from my iPhone > On Sep 7, 2015, at 2:16 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > > *Now* I understand this rule. Hi Nicolai, points to the need for some very good doc for these rules :-) > > 2015-09-02 3:40 GMT+02:00 Eliot Miranda <eliot.miranda(a)gmail.com>: >> >> >>> On Tue, Sep 1, 2015 at 1:29 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: >>> Thank you all for your response, >>> now the interesting question is, what should this rule recommend to use instead? First assign to a block local variable and >>> add a nil check in the unwind block? >> >> No. I think the pattern modifies this: >> >> | t | >> ... >> [t := initExpr. >> exprs] >> ensure: [t msg] >> >> to this >> >> | t | >> ... >> t := initExpr. >> [exprs] >> ensure: [t msg] >> >> Control never reaches the block [exprs] isf there is an error in initExpr so there's no issue with t being unassigned; control won't get to the ensure block, so no need to test for nil. >> >>> >>> And maybe we should improve that rule, because in Pharo 5.0 there are 5 methods catched by >>> this rule: >>> 3 have an explicit ifnonil check before accessing the variable - their implementation actually behaves correctly. >>> The other two are just "testdata" used in the unit test for this rule >>> >>> >>> >>> 2015-08-31 15:30 GMT+02:00 Eliot Miranda <eliot.miranda(a)gmail.com>: >>>> If there's an error in the expression that is assigned to file, and the stack unwound, file won't have been assigned and the close will get sent to nil. The assignment to file should precede the block. >>>> >>>> Sent from my iPhone >>>> >>>>> On Aug 31, 2015, at 5:03 AM, Nicolai Hess <nicolaihess(a)web.de> wrote: >>>>> >>>>> Anyone? We may remove this rule if no one understands for what this is good for. >>>>> (if anyone knows, please comment that class). >>>>> >>>>> >>>>> >>>>> 2014-12-14 11:22 GMT+01:00 Nicolai Hess <nicolaihess(a)web.de>: >>>>>> >>>>>> 2014-11-30 20:54 GMT+01:00 stepharo <stepharo(a)free.fr>: >>>>>>> >>>>>>> thanks we should open a bug entry to improve the class comment of this rule. >>>>>>> Any taker? >>>>>>> >>>>>>> Stef >>>>>>> >>>>>>> Le 30/11/14 12:10, Thierry Goubier a Ã©crit : >>>>>> >>>>>> done >>>>>> 14618 >>>>>> Add a comment describing RBFileBlocksRule >>>>>> >>>>>> now I just need to have a good description for this rule. Please, can >>>>>> someone outline the discussion on this thread: >>>>>> - describe why code matching this rule is considered back practice >>>>>> - describe how the code could be rewritten. >>>>>> >>>>>> nicolai >>>>>> >>>>>> >>>>>>> >>>>>>>> Le 30/11/2014 12:01, Max Leske a Ã©crit : >>>>>>>>> >>>>>>>>>> On 30.11.2014, at 11:18, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: >>>>>>>>>> >>>>>>>>>> Le 30/11/2014 11:06, Max Leske a Ã©crit : >>>>>>>>>>> The code would look like this: >>>>>>>>>>> >>>>>>>>>>> [ | file | >>>>>>>>>>> file := StandardFileStream forceNewFileNamed: âfooâ. >>>>>>>>>>> file nextPutAll: âbarâ ] >>>>>>>>>>> ensure: [ file close ]. >>>>>>>>>>> >>>>>>>>>>> Why that is considered bad practice however, I canât tell. >>>>>>>>>> >>>>>>>>>> This one would fail because file is a temp to the block (and not visible to the ensure block). >>>>>>>>> >>>>>>>>> If it werenât visible, wouldnât the compiler raise an exception? >>>>>>>> >>>>>>>> In your example, yes. >>>>>>>> >>>>>>>> But the rule matched: >>>>>>>> >>>>>>>> | file | >>>>>>>> [ >>>>>>>> file := StandardFileStream forceNewFileNamed: âfooâ. >>>>>>>> file nextPutAll: âbarâ ] >>>>>>>> ensure: [ file close ]. >>>>>>>> >>>>>>>> (Hum: wouldn't the compiler complain of file might be nil in the ensure block?) >>>>>>>> >>>>>>>>>> Another problem is that, if you have a failure in forceNewFileNamed:, file is nil and the ensure: fail as well. >>>>>>>>> >>>>>>>>> True, but thatâs a problem this rule doesnât really cover I guess. That oneâs up to the developer. >>>>>>>> >>>>>>>> I would expect that rule to flag bad coding practices, and I think it does ;) >>>>>>>> >>>>>>>> Thierry >> >> >> >> -- >> _,,,^..^,,,_ >> best, Eliot >

Sept. 8, 2015

Re: [Pharo-dev] Nautilus strange pattern

by Ben Coman

On Tue, Sep 8, 2015 at 5:32 AM, Nicolai Hess <nicolaihess(a)web.de> wrote: > We should make sure to unregister to all announcement when the window is > closed. +1. Nautilus seems to leak announcements. Sorry I forgot to log an issue already for this... https://www.mail-archive.com/pharo-dev@lists.pharo.org/msg31953.html So should I log a new issue now, or do you want to pick it up under existing work? cheers -ben > (Or is there any reason or situation in which nautilus can properly work > after the window is closed?) > > 2015-09-06 10:41 GMT+02:00 stepharo <stepharo(a)free.fr>: >> >> Hi >> >> I'm trying to understand what there is a need for this window ifNil: [^ >> self ] >> And I wonder is this is not problem due to a global announcer that would >> keep announcer even when the nautilus widget >> has been deleted. >> Any other suggestions? >> >> Stef >> >> classRemoved: anAnnouncement >> | class oldPackage | >> window ifNil: [ ^ self ]. >> window isDisplayed >> ifFalse: [ ^ self ]. >> class := anAnnouncement classRemoved. >> (self classWidget getClassesList includes: class) >> ifTrue: >> [ >> >> classRecategorized: anAnnouncement >> >> window ifNil: [ ^ self ]. >> window isDisplayed ifFalse: [ ^ self ]. >> self selectedPackage ifNotNil:[:selection | >> ({ anAnnouncement oldCategory. anAnnouncement newCategory } >> anySatisfy: [ :each | selection includesCategory: each ]) >> ifTrue: [ self updatePackageGroupAndClassList ]] >> >> >> classRemoved: anAnnouncement >> | class oldPackage | >> window ifNil: [ ^ self ]. >> window isDisplayed >> ifFalse: [ ^ self ]. >> class := anAnnouncement classRemoved. >> (self classWidget getClassesList includes: cla >> >

Sept. 7, 2015

Re: [Pharo-dev] Nautilus strange pattern

by Nicolai Hess

We should make sure to unregister to all announcement when the window is closed. (Or is there any reason or situation in which nautilus can properly work after the window is closed?) 2015-09-06 10:41 GMT+02:00 stepharo <stepharo(a)free.fr>: > Hi > > I'm trying to understand what there is a need for this window ifNil: [^ > self ] > And I wonder is this is not problem due to a global announcer that would > keep announcer even when the nautilus widget > has been deleted. > Any other suggestions? > > Stef > > classRemoved: anAnnouncement > | class oldPackage | > window ifNil: [ ^ self ]. > window isDisplayed > ifFalse: [ ^ self ]. > class := anAnnouncement classRemoved. > (self classWidget getClassesList includes: class) > ifTrue: > [ > > classRecategorized: anAnnouncement > > window ifNil: [ ^ self ]. > window isDisplayed ifFalse: [ ^ self ]. > self selectedPackage ifNotNil:[:selection | > ({ anAnnouncement oldCategory. anAnnouncement newCategory } > anySatisfy: [ :each | selection includesCategory: each ]) > ifTrue: [ self updatePackageGroupAndClassList ]] > > > classRemoved: anAnnouncement > | class oldPackage | > window ifNil: [ ^ self ]. > window isDisplayed > ifFalse: [ ^ self ]. > class := anAnnouncement classRemoved. > (self classWidget getClassesList includes: cla > >

Sept. 7, 2015

Re: [Pharo-dev] ensure: and assignments RB Rule

by Nicolai Hess

*Now* I understand this rule. 2015-09-02 3:40 GMT+02:00 Eliot Miranda <eliot.miranda(a)gmail.com>: > > > On Tue, Sep 1, 2015 at 1:29 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > >> Thank you all for your response, >> now the interesting question is, what should this rule recommend to use >> instead? First assign to a block local variable and >> add a nil check in the unwind block? >> > > No. I think the pattern modifies this: > > | t | > ... > [t := initExpr. > exprs] > ensure: [t msg] > > to this > > | t | > ... > t := initExpr. > [exprs] > ensure: [t msg] > > Control never reaches the block [exprs] isf there is an error in initExpr > so there's no issue with t being unassigned; control won't get to the > ensure block, so no need to test for nil. > > >> And maybe we should improve that rule, because in Pharo 5.0 there are 5 >> methods catched by >> this rule: >> 3 have an explicit ifnonil check before accessing the variable - their >> implementation actually behaves correctly. >> The other two are just "testdata" used in the unit test for this rule >> >> >> >> 2015-08-31 15:30 GMT+02:00 Eliot Miranda <eliot.miranda(a)gmail.com>: >> >>> If there's an error in the expression that is assigned to file, and the >>> stack unwound, file won't have been assigned and the close will get sent to >>> nil. The assignment to file should precede the block. >>> >>> Sent from my iPhone >>> >>> On Aug 31, 2015, at 5:03 AM, Nicolai Hess <nicolaihess(a)web.de> wrote: >>> >>> Anyone? We may remove this rule if no one understands for what this is >>> good for. >>> (if anyone knows, please comment that class). >>> >>> >>> >>> 2014-12-14 11:22 GMT+01:00 Nicolai Hess <nicolaihess(a)web.de>: >>> >>>> >>>> 2014-11-30 20:54 GMT+01:00 stepharo <stepharo(a)free.fr>: >>>>> >>>>> thanks we should open a bug entry to improve the class comment of this >>>>> rule. >>>>> Any taker? >>>>> >>>>> Stef >>>>> >>>>> Le 30/11/14 12:10, Thierry Goubier a Ã©crit : >>>> >>>> >>>> done >>>> 14618 <https://pharo.fogbugz.com/default.asp?14618> >>>> Add a comment describing RBFileBlocksRule >>>> >>>> now I just need to have a good description for this rule. Please, can >>>> someone outline the discussion on this thread: >>>> - describe why code matching this rule is considered back practice >>>> - describe how the code could be rewritten. >>>> >>>> nicolai >>>> >>>> >>>> >>>>> >>>>> Le 30/11/2014 12:01, Max Leske a Ã©crit : >>>>>> >>>>>>> >>>>>>> On 30.11.2014, at 11:18, Thierry Goubier <thierry.goubier(a)gmail.com> >>>>>>>> wrote: >>>>>>>> >>>>>>>> Le 30/11/2014 11:06, Max Leske a Ã©crit : >>>>>>>> >>>>>>>>> The code would look like this: >>>>>>>>> >>>>>>>>> [ | file | >>>>>>>>> file := StandardFileStream forceNewFileNamed: âfooâ. >>>>>>>>> file nextPutAll: âbarâ ] >>>>>>>>> ensure: [ file close ]. >>>>>>>>> >>>>>>>>> Why that is considered bad practice however, I canât tell. >>>>>>>>> >>>>>>>> >>>>>>>> This one would fail because file is a temp to the block (and not >>>>>>>> visible to the ensure block). >>>>>>>> >>>>>>> >>>>>>> If it werenât visible, wouldnât the compiler raise an exception? >>>>>>> >>>>>> >>>>>> In your example, yes. >>>>>> >>>>>> But the rule matched: >>>>>> >>>>>> | file | >>>>>> [ >>>>>> file := StandardFileStream forceNewFileNamed: âfooâ. >>>>>> file nextPutAll: âbarâ ] >>>>>> ensure: [ file close ]. >>>>>> >>>>>> (Hum: wouldn't the compiler complain of file might be nil in the >>>>>> ensure block?) >>>>>> >>>>>> Another problem is that, if you have a failure in forceNewFileNamed:, >>>>>>>> file is nil and the ensure: fail as well. >>>>>>>> >>>>>>> >>>>>>> True, but thatâs a problem this rule doesnât really cover I guess. >>>>>>> That oneâs up to the developer. >>>>>>> >>>>>> >>>>>> I would expect that rule to flag bad coding practices, and I think it >>>>>> does ;) >>>>>> >>>>>> Thierry >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>> >> > > > -- > _,,,^..^,,,_ > best, Eliot >

Sept. 7, 2015

Re: [Pharo-dev] GitFileTree with Project Template from GitHub

by Thierry Goubier

Le 07/09/2015 20:58, Peter UhnÃ¡k a Ã©crit : > MCFileTreeGitRemoteRepository > > > I was under the impression that Remote is read only because you cannot > commit directly to github; this is DCVS. No, remote works just like a normal gitfiletree repository, and it becomes read only if you use https as a protocol. MCFileTreeGitRemoteRepository is only there because: - you add the clone and branch to download the repository - and MC only allows one creation method per repository class. > What I do is that I have local copy of the git repo which is then loaded > into Pharo... But it is even easier to do something like: Metacello new baseline: 'SmaCC'; repository: 'gitfiletree://github.com/ThierryGoubier/SmaCC'; load Thierry > > ~~~~~~~~~~~~~~~~~~~~~~~~~~ > Metacello new > baseline: 'BaslineOfMyProject'; > repository: 'gitfiletree:///path/to/my/git/repo'; > load. > ~~~~~~~~~~~~~~~~~~~~~ > > > On Mon, Sep 7, 2015 at 7:59 PM, Sean P. DeNigris <sean(a)clipperadams.com > <mailto:sean@clipperadams.com>> wrote: > > Let's say you decide to port a repo from StHub to GitHub. Here's a > logical > workflow: > 1. Create a repo via the GitHub we interface so you get a nice > license file > and readme > 2. Create a MCFileTreeGitRemoteRepository as the destination for the > port. > For example: > (cloneFolder / 'repository') ensureCreateDirectory. > destination := MCFileTreeGitRemoteRepository > location: 'git@github.com:seandenigris/Superuser.git' > name: cloneFolder > subdirectory: 'repository' > branch: ''. > > Oops! I couldn't find a magic incantation to get #2 to work. Here is > what > seems to be the problem: If you specify the 'repository' > subdirectory, you > get an error that it doesn't exist (because there's no way to > autogenerate > empty directories from the GitHub web interface), but if you create it > before the clone, you get an error that the pre-existing cloneFolder > is not > a git repo. Catch 22! > > It would be nice if GitFileTree cloned the repo and then created the > subdirectory if needed. I hacked around a bit, but didn't get very > far :/ > > I ended up manually cloning and then creating a vanilla GitFileTree repo > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/GitFileTree-with-Project-Template-from-GitHub-tp48486… > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

Sept. 7, 2015

Re: [Pharo-dev] GitFileTree with Project Template from GitHub

by Thierry Goubier

Le 07/09/2015 19:59, Sean P. DeNigris a Ã©crit : > Let's say you decide to port a repo from StHub to GitHub. Here's a logical > workflow: > 1. Create a repo via the GitHub we interface so you get a nice license file > and readme > 2. Create a MCFileTreeGitRemoteRepository as the destination for the port. > For example: > (cloneFolder / 'repository') ensureCreateDirectory. > destination := MCFileTreeGitRemoteRepository > location: 'git@github.com:seandenigris/Superuser.git' > name: cloneFolder > subdirectory: 'repository' > branch: ''. > > Oops! I couldn't find a magic incantation to get #2 to work. Here is what > seems to be the problem: If you specify the 'repository' subdirectory, you > get an error that it doesn't exist (because there's no way to autogenerate > empty directories from the GitHub web interface), but if you create it > before the clone, you get an error that the pre-existing cloneFolder is not > a git repo. Catch 22! > > It would be nice if GitFileTree cloned the repo and then created the > subdirectory if needed. I hacked around a bit, but didn't get very far :/ Good point. It is doable with probably a single line (when opening the repository, ensure the target directory is created if it doesn't exist) > I ended up manually cloning and then creating a vanilla GitFileTree repo This work-around allways exist ;) I'll try and add an auto-creation if the target repository is missing. Thierry > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/GitFileTree-with-Project-Template-from-GitHub-tp48486… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

Sept. 7, 2015

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50311 Home: https://github.com/pharo-project/pharo-core

Sept. 7, 2015

[pharo-project/pharo-core] 0acdab: 50311

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 0acdab79aac87eca75f566c14f77b99cd2ca2ff3 https://github.com/pharo-project/pharo-core/commit/0acdab79aac87eca75f566c1… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-09-07 (Mon, 07 Sep 2015) Changed paths: M Nautilus.package/ClassWidget.class/instance/private list model/dropInClass_inARow_.st M Nautilus.package/NautilusUI.class/instance/drag and drop/dropMethod_inARow_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50310.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50311.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50310.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50311.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Tools.package/NewVersionBrowser.class/instance/instance creation/browseVersionsOf_.st M Spec-Tools.package/NewVersionBrowser.class/instance/instance creation/browseVersionsOf_class_meta_category_selector_.st M Spec-Tools.package/NewVersionBrowser.class/instance/instance creation/revert_.st A Spec-Tools.package/NewVersionBrowser.class/instance/private/setRGMethodFrom_.st M Tool-Catalog.package/CatalogBrowser.class/README.md R Tool-Catalog.package/CatalogBrowser.class/instance/actions/defineAllRepositoriesInMCBrowser.st R Tool-Catalog.package/CatalogBrowser.class/instance/actions/defineCurrentVersionRepositoryInMCBrowser.st A Tool-Catalog.package/CatalogBrowser.class/instance/building/installStableVersionButton_.st A Tool-Catalog.package/CatalogBrowser.class/instance/building/installStableVersionMenuItem_.st A Tool-Catalog.package/CatalogBrowser.class/instance/building/loadConfigurationButton_.st A Tool-Catalog.package/CatalogBrowser.class/instance/building/loadConfigurationMenuItem_.st R Tool-Catalog.package/CatalogBrowser.class/instance/menu/defineAllRepositoriesInMCBrowserButton_.st R Tool-Catalog.package/CatalogBrowser.class/instance/menu/defineCurrentVersionRepositoryButton_.st R Tool-Catalog.package/CatalogBrowser.class/instance/menu/installStableVersionButton_.st R Tool-Catalog.package/CatalogBrowser.class/instance/menu/installStableVersionMenuItem_.st R Tool-Catalog.package/CatalogBrowser.class/instance/menu/loadConfigurationButton_.st R Tool-Catalog.package/CatalogBrowser.class/instance/menu/loadConfigurationMenuItem_.st R Tool-Catalog.package/CatalogBrowser.class/instance/private - utilities/availableRepositoryURLStrings.st M Tool-Catalog.package/CatalogBrowser.class/instance/private - utilities/buildContextMenuOn_.st R Tool-Catalog.package/CatalogBrowser.class/instance/private - utilities/repositoryObjectFromURLString_.st M Tool-Catalog.package/CatalogProject.class/README.md A Tool-Catalog.package/CatalogProject.class/class/accessing/repositoryNames.st R Tool-Catalog.package/CatalogProject.class/class/accessing/repositoryURLToNameMappings.st R Tool-Catalog.package/CatalogProject.class/class/private/availableRepositoryURLStrings.st A Tool-Catalog.package/CatalogProject.class/class/private/createRepositoryNames.st R Tool-Catalog.package/CatalogProject.class/class/private/createRepositoryURLtoNameMappings.st R Tool-Catalog.package/CatalogProject.class/class/private/pharoCurrentDottedName.st R Tool-Catalog.package/CatalogProject.class/class/private/pharoCurrentMajorName.st R Tool-Catalog.package/CatalogProject.class/class/private/pharoDistributionRepository.st M Tool-Catalog.package/CatalogProject.class/instance/accessing/allKeywords.st A Tool-Catalog.package/CatalogProject.class/instance/accessing/repository.st R Tool-Catalog.package/CatalogProject.class/instance/accessing/repositoryName.st M Tool-Catalog.package/CatalogProject.class/instance/testing/isAvailableForCurrentPharo.st M Tool-Catalog.package/CatalogProvider.class/README.md Log Message: ----------- 50311 16504 NewVersionBrowser and RGMethodDefinition vs. CompiledMethod https://pharo.fogbugz.com/f/cases/16504 16496 Provide context menu icons in Catalog browser https://pharo.fogbugz.com/f/cases/16496 16487 Dropping methods on empty areas of class/method category pane raises SubscriptOutOfBounds https://pharo.fogbugz.com/f/cases/16487 http://files.pharo.org/image/50/50311.zip

Sept. 7, 2015

Re: [Pharo-dev] Did no find yet a way to reproduce QA concurrent access

by Marcus Denker

> On 07 Sep 2015, at 22:07, stepharo <stepharo(a)free.fr> wrote: > > I'm not complaining. I know that there is a good chance that we break the system when improving it. > I have no problem with that and I prefer a living system with some bugs for a while than a dead system with no bug :) exactly. For me, Pharo was exactly that: Imagine instead of ânot doing anything because we could do betterâ we would just do, as trivial and wrong as it our limits allow, but then learn from the mistakes and repeatâ¦ and, important, this in a way that the improvement âfeeds backâ into the system to have a direct impact on the next iteration. There are multiple feedback loops: - you only learn when you do. And most when you do it wrong. When you do the next thing it will be with more understanding and knowledge. If you do nothing because what you can do might be not perfect, you will just end with nothing. - As we improve the system we use, every tiny improvement has an impact on the next improvement. The âThis is just a 2% boring improvementâ is part of an exponential growth process if it happens in such a feedback loop. - The artefact that you see is not the goal. Itâs just a stepping stone towards. It will be ugly and imperfect, it will contain parts that are even not meant to be ever âniceâ as they are just scaffolding. They are there to help us build something else. â¦.. Marcus

Sept. 7, 2015

Re: [Pharo-dev] chunk file format (unrecoverable changes)

by Nicolai Hess

2015-09-07 20:10 GMT+02:00 Eliot Miranda <eliot.miranda(a)gmail.com>: > > > On Sun, Sep 6, 2015 at 12:56 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > >> Do we have a documentation about the format of >> - class definitions >> - methods >> - class comments >> for the changes file ? >> > > > Google "specification of smalltalk chunk format" and you will see: > > Overviews: Chunk File Format > <https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uac…> > Smalltalk Interchange Format - Draft Smalltalk Standard v1.9 > <https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=2&cad=rja&uac…> > The Smalltalk fileOut format - 1 > <https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=3&cad=rja&uac…> > > and more. > Thank you eliot (should have google that myself !) > > >> >> I am asking because some entries are using two separator >> "! !" >> and some only one >> "!" >> > > Indeed. It's in the spec. ! ! ends a run of methods in the same > protocol. ! ends a method or a doit, etc. Read the spec. > ah! grouping multiple methods for one protocol. > > > >> And we have a problem with the "Recover lost changes" browser >> (https://pharo.fogbugz.com/f/cases/16498/unrecoverable-changes) >> and I am not sure if this is a bug on the code importer >> or if it is a bug on how we write changes to the changes file. >> >> >> nicolai >> >> > > > -- > _,,,^..^,,,_ > best, Eliot >

Sept. 7, 2015

Re: [Pharo-dev] Did no find yet a way to reproduce QA concurrent access

by stepharo

may be this is the same. Le 7/9/15 12:32, Yuriy Tymchuk a Ã©crit : > Yes, I know, but Stef was referring to deleting a method. > > Also I donât really know how I can fix the stuff with instance > variable. I need to have a separate process in order not to slow down > the browsing in Nautilus. I have the impression that we see that the reflective should be thread safe :) No? May be you could check what is used and have a threadsafe wrapper (not since the rules can use many different infromation I guess that this is not practical to do it. In any case this is a really interested case. Food for thoughts as they say.

Sept. 7, 2015

Re: [Pharo-dev] Did no find yet a way to reproduce QA concurrent access

by stepharo

I'm not complaining. I know that there is a good chance that we break the system when improving it. I have no problem with that and I prefer a living system with some bugs for a while than a dead system with no bug :) I'm just trying to help handling this problem. This is alpha with all the risks. Stef Le 7/9/15 00:46, Yuriy Tymchuk a Ã©crit : > I think that it is related to how I was working with Nautilus announcements. Now as announcements are changed, I can improve that. Just give me a bit of time :) > > Uko > >> On 06 Sep 2015, at 22:17, stepharo <stepharo(a)free.fr> wrote: >> >> I thought that I could reproduce the QA concurrent access raising a DNU when we remove a method >> but I failed. >> I got again this bug. >> What I did was selecting a method in Nautilus and removing this method after an implementors and from the message list browser. >> But I cannot reproduce it. >> >> Stef >> > >

Sept. 7, 2015

Re: [Pharo-dev] Did no find yet a way to reproduce QA concurrent access

by stepharo

Ok I will do it. Le 7/9/15 00:56, Yuriy Tymchuk a Ã©crit : > Also, when if this kind of error happens again, can you please fuel it out and sent it to me? Having a stack can be helpful in understanding. > > Uko > >> On 06 Sep 2015, at 22:17, stepharo <stepharo(a)free.fr> wrote: >> >> I thought that I could reproduce the QA concurrent access raising a DNU when we remove a method >> but I failed. >> I got again this bug. >> What I did was selecting a method in Nautilus and removing this method after an implementors and from the message list browser. >> But I cannot reproduce it. >> >> Stef >> > >

Sept. 7, 2015

Re: [Pharo-dev] WhatsUp from: 2015-09-07 until: 2015-09-20

by stepharo

Le 7/9/15 07:00, seaside(a)rmod.lille.inria.fr a Ã©crit : > Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! > > ### Here's what I've been up to since the last WhatsUp: - Finished a first version of the Pharo Starter Kit (to be released and announced soon). - Collection of YouTube pharo related videos (to be announced soon too). - Many many little microscopical uninteresting cleans, with the hope and probably conviction that at the end it will make a HUGE difference :) > > ### What's next, until 2015-09-20 (*): > > - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION > > (*) we'll be expecting results by then ;) > >

Sept. 7, 2015

Re: [Pharo-dev] GitFileTree with Project Template from GitHub

by Peter UhnÃ¡k

> > MCFileTreeGitRemoteRepository I was under the impression that Remote is read only because you cannot commit directly to github; this is DCVS. What I do is that I have local copy of the git repo which is then loaded into Pharo... ~~~~~~~~~~~~~~~~~~~~~~~~~~ Metacello new baseline: 'BaslineOfMyProject'; repository: 'gitfiletree:///path/to/my/git/repo'; load. ~~~~~~~~~~~~~~~~~~~~~ On Mon, Sep 7, 2015 at 7:59 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Let's say you decide to port a repo from StHub to GitHub. Here's a logical > workflow: > 1. Create a repo via the GitHub we interface so you get a nice license file > and readme > 2. Create a MCFileTreeGitRemoteRepository as the destination for the port. > For example: > (cloneFolder / 'repository') ensureCreateDirectory. > destination := MCFileTreeGitRemoteRepository > location: 'git@github.com:seandenigris/Superuser.git' > name: cloneFolder > subdirectory: 'repository' > branch: ''. > > Oops! I couldn't find a magic incantation to get #2 to work. Here is what > seems to be the problem: If you specify the 'repository' subdirectory, you > get an error that it doesn't exist (because there's no way to autogenerate > empty directories from the GitHub web interface), but if you create it > before the clone, you get an error that the pre-existing cloneFolder is not > a git repo. Catch 22! > > It would be nice if GitFileTree cloned the repo and then created the > subdirectory if needed. I hacked around a bit, but didn't get very far :/ > > I ended up manually cloning and then creating a vanilla GitFileTree repo > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/GitFileTree-with-Project-Template-from-GitHub-tp48486… > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

Sept. 7, 2015

Re: [Pharo-dev] chunk file format (unrecoverable changes)

by Eliot Miranda

On Sun, Sep 6, 2015 at 12:56 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > Do we have a documentation about the format of > - class definitions > - methods > - class comments > for the changes file ? > Google "specification of smalltalk chunk format" and you will see: Overviews: Chunk File Format <https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uac…> Smalltalk Interchange Format - Draft Smalltalk Standard v1.9 <https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=2&cad=rja&uac…> The Smalltalk fileOut format - 1 <https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=3&cad=rja&uac…> and more. > > I am asking because some entries are using two separator > "! !" > and some only one > "!" > Indeed. It's in the spec. ! ! ends a run of methods in the same protocol. ! ends a method or a doit, etc. Read the spec. > And we have a problem with the "Recover lost changes" browser > (https://pharo.fogbugz.com/f/cases/16498/unrecoverable-changes) > and I am not sure if this is a bug on the code importer > or if it is a bug on how we write changes to the changes file. > > > nicolai > > -- _,,,^..^,,,_ best, Eliot

Sept. 7, 2015

GitFileTree with Project Template from GitHub

by Sean P. DeNigris

Let's say you decide to port a repo from StHub to GitHub. Here's a logical workflow: 1. Create a repo via the GitHub we interface so you get a nice license file and readme 2. Create a MCFileTreeGitRemoteRepository as the destination for the port. For example: (cloneFolder / 'repository') ensureCreateDirectory. destination := MCFileTreeGitRemoteRepository location: 'git@github.com:seandenigris/Superuser.git' name: cloneFolder subdirectory: 'repository' branch: ''. Oops! I couldn't find a magic incantation to get #2 to work. Here is what seems to be the problem: If you specify the 'repository' subdirectory, you get an error that it doesn't exist (because there's no way to autogenerate empty directories from the GitHub web interface), but if you create it before the clone, you get an error that the pre-existing cloneFolder is not a git repo. Catch 22! It would be nice if GitFileTree cloned the repo and then created the subdirectory if needed. I hacked around a bit, but didn't get very far :/ I ended up manually cloning and then creating a vanilla GitFileTree repo ----- Cheers, Sean -- View this message in context: http://forum.world.st/GitFileTree-with-Project-Template-from-GitHub-tp48486… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 7, 2015

Re: [Pharo-dev] System announcements fixed?

by Stephan Eggermont

On 05-09-15 15:50, stepharo wrote: > > > Le 5/9/15 14:10, Stephan Eggermont a Ã©crit : >> On 05-09-15 08:52, stepharo wrote: > Are the fixes of yuriy addressing the nautilus one? >> >> And there is a more difficult case where changing code in the debugger >> does not get to (all) nautilus browsers. I had two browsers open and >> changed code that was in the selected class but not visible in the >> browsers. One browser was correctly updated, the other was not. >> >> This has happened for a few weeks now, and I thought this was known >> and related to the current Nautilus refactorings. > No Pharo is a complex system and we do not have enough tests. Issue 16508 Nautilus loses track of changes when using the debugger (restart) 50310 Linux Open a nautilus browser Add a new package Added Add a new class SomeCase Add a new method SomeCase>>one ^1+self two Save Enter author name Click on --all-- to get the method to show up (different bug) Open a Playground DoIt SomeCase new one Create method two in debugger SomeCase>>two ^2 + self three Save Restart (cursor is not correctly updated) Proceed Create a method three in debugger SomeCase>>three ^3 Save Proceed Now, method three in the nautilus window is SomeCase>>three self shouldBeImplemented. Open a new nautilus browser and verify that it has the correct method three SomeCase>>three ^3

Sept. 7, 2015

[pharo-project/pharo-core] d9bb19: 50310

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: d9bb19202f1c607107a3a1b7d6ba3c9d5b8c4b0a https://github.com/pharo-project/pharo-core/commit/d9bb19202f1c607107a3a1b7… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-09-07 (Mon, 07 Sep 2015) Changed paths: M Nautilus.package/AbstractNautilusUI.class/instance/accessing/classifier.st M Nautilus.package/AbstractNautilusUI.class/instance/accessing/groupsManager.st M Nautilus.package/AbstractNautilusUI.class/instance/accessing/model_.st R Nautilus.package/AbstractNautilusUI.class/instance/accessing/noMethodsString.st M Nautilus.package/AbstractNautilusUI.class/instance/accessing/selectedClass.st M Nautilus.package/AbstractNautilusUI.class/instance/accessing/selectedGroup.st M Nautilus.package/AbstractNautilusUI.class/instance/accessing/selectedPackageWithoutChangingSelection_.st M Nautilus.package/AbstractNautilusUI.class/instance/accessing/selectedPackage_.st M Nautilus.package/AbstractNautilusUI.class/instance/accessing/sourceCodeContainer.st M Nautilus.package/AbstractNautilusUI.class/instance/accessing/sourceCodePanel.st R Nautilus.package/AbstractNautilusUI.class/instance/accessing/updateCodePanel.st M Nautilus.package/AbstractNautilusUI.class/instance/accessing/window.st M Nautilus.package/AbstractNautilusUI.class/instance/accessing/window_.st M Nautilus.package/AbstractNautilusUI.class/instance/announcement registration/registerToAnnouncements.st M Nautilus.package/AbstractNautilusUI.class/instance/class comment pane/whenExtendCommentSwitch_.st A Nautilus.package/AbstractNautilusUI.class/instance/code panel/updateCodePanel.st A Nautilus.package/AbstractNautilusUI.class/instance/default/noMethodsString.st M Nautilus.package/AbstractNautilusUI.class/instance/displaying/close.st M Nautilus.package/AbstractNautilusUI.class/instance/menus behavior/renameClass.st M Nautilus.package/AbstractPackageWidget.class/instance/protocol/buildContents.st M Nautilus.package/ClassOrMethodDefinitionAcceptor.class/README.md M Nautilus.package/ClassOrMethodDefinitionAcceptor.class/instance/protocol/acceptInstanceSide_notifying_.st M Nautilus.package/CodeRewritingAcceptor.class/instance/protocol/accept_notifying_.st M Nautilus.package/CodeSearchingAcceptor.class/instance/protocol/accept_notifying_.st M Nautilus.package/Nautilus.class/README.md A Nautilus.package/Nautilus.class/class/testing/isNoCategoryAndNoMethodSelected.st R Nautilus.package/NautilusHelp.class/README.md R Nautilus.package/NautilusHelp.class/class/accessing/bookName.st R Nautilus.package/NautilusHelp.class/class/accessing/pages.st R Nautilus.package/NautilusHelp.class/class/menus/contextMenus.st R Nautilus.package/NautilusHelp.class/definition.st R Nautilus.package/NautilusUI.class/instance/debugging actions/buildTestSuiteFor_.st M Nautilus.package/NautilusUI.class/instance/debugging actions/debugTest.st R Nautilus.package/NautilusUI.class/instance/displaying/open.st M Nautilus.package/NautilusUI.class/instance/drag and drop/dropMethod_inARow_.st M Nautilus.package/NautilusUI.class/instance/focus/giveFocusToClass.st M Nautilus.package/NautilusUI.class/instance/focus/giveFocusToMethod.st M Nautilus.package/NautilusUI.class/instance/focus/giveFocusToProtocol.st M Nautilus.package/NautilusUI.class/instance/history behavior/currentHistoryIndex.st M Nautilus.package/NautilusUI.class/instance/history behavior/getHistoryList.st M Nautilus.package/NautilusUI.class/instance/history behavior/historyChanged.st M Nautilus.package/NautilusUI.class/instance/history behavior/setHistory_.st M Nautilus.package/NautilusUI.class/instance/history behavior/wrapHistory_.st M Nautilus.package/NautilusUI.class/instance/menu-packages/demoteSelectedPackageAsPackageWithTag.st R Nautilus.package/NautilusUI.class/instance/menus behavior/runTestForAMethodWithAnHalt_.st M Nautilus.package/NautilusUI.class/instance/menus behavior/runTestForAMethod_notifying_priority_.st A Nautilus.package/NautilusUI.class/instance/open/open.st M Reflectivity-Tests.package/ReflectivityControlTest.class/instance/tests - after/testAfterMethod.st M Reflectivity.package/RFASTTranslator.class/instance/visitor-double dispatching/visitMethodNode_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50309.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50310.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50309.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50310.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Shout.package/SHRBTextStyler.class/instance/formatting/literalStyleSymbol_.st Log Message: ----------- 50310 16493 Syntax highlighting in Rubric need to highlight characters https://pharo.fogbugz.com/f/cases/16493 16507 Simplify test running of Nautilus https://pharo.fogbugz.com/f/cases/16507 16506 Ensure wrapping #after for MethodNode https://pharo.fogbugz.com/f/cases/16506 16502 simple nautilus cleans https://pharo.fogbugz.com/f/cases/16502 http://files.pharo.org/image/50/50310.zip

Sept. 7, 2015

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50310 Home: https://github.com/pharo-project/pharo-core

Sept. 7, 2015

Re: [Pharo-dev] Nautilus ;D

by Esteban Lorenzano

> On 07 Sep 2015, at 15:13, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > >> On 07 Sep 2015, at 14:20, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: >> >> Hi >> >> In Pharo 50308 Nautilus has strange behaviour. >> >> Select "--- all ---" and then press "select all" cmd+A shortcut => duplicated methods. >> <Screen Shot 2015-09-07 at 14.11.11.png>â >> >> Also drag and drop of methods is strange now. If I don't have any selected method I can't drag any method. As soon as I select one => drag and drop works for any method. As soon as deselect - doesn't work. > > I had the same problem. When nothing is selected and you just start to drag something it gets the secondary selection, and so is not dragged. But when you explicitly klick on it, to give it primary selection, you can drag it. yes, that is reported. I will tackle them as soon as I find 5â â¦ now if someone wants to take overâ¦ I wouldnât mind :) Esteban > > Uko > >> >> Cheers, >> Alex >> > >

Sept. 7, 2015

Re: [Pharo-dev] Nautilus ;D

by Yuriy Tymchuk

> On 07 Sep 2015, at 14:20, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > > Hi > > In Pharo 50308 Nautilus has strange behaviour. > > Select "--- all ---" and then press "select all" cmd+A shortcut => duplicated methods. > <Screen Shot 2015-09-07 at 14.11.11.png>â > > Also drag and drop of methods is strange now. If I don't have any selected method I can't drag any method. As soon as I select one => drag and drop works for any method. As soon as deselect - doesn't work. I had the same problem. When nothing is selected and you just start to drag something it gets the secondary selection, and so is not dragged. But when you explicitly klick on it, to give it primary selection, you can drag it. Uko > > Cheers, > Alex >

Sept. 7, 2015

Re: [Pharo-dev] Nautilus ;D

by Esteban Lorenzano

I think thatâs related to FasTable. can you report a bug? Esteban > On 07 Sep 2015, at 14:20, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > > Hi > > In Pharo 50308 Nautilus has strange behaviour. > > Select "--- all ---" and then press "select all" cmd+A shortcut => duplicated methods. > <Screen Shot 2015-09-07 at 14.11.11.png>â > > Also drag and drop of methods is strange now. If I don't have any selected method I can't drag any method. As soon as I select one => drag and drop works for any method. As soon as deselect - doesn't work. > > Cheers, > Alex >

Sept. 7, 2015

Re: [Pharo-dev] [Pharo-users] Low traffic [ANN] only list

by Marcus Denker

> On 07 Sep 2015, at 14:52, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > Would be nice to have all the major update of libraries, Pharo, and documentation. > I guess this is the idea of this list right? > No, the idea is to have something even more low traffic. The idea is to have something for people who are interested in Pharo but who are not users. I want this to be at 1 mail per month max. > Will it be browsable online? I am not sure.. I already put hours into this yesterday, I canât invest even more now. Marcus

Sept. 7, 2015

Re: [Pharo-dev] [Pharo-users] Low traffic [ANN] only list

by Alexandre Bergel

Would be nice to have all the major update of libraries, Pharo, and documentation. I guess this is the idea of this list right? Will it be browsable online? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Sep 6, 2015, at 11:32 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hello, > > We have set up a low traffic announce-only list: > > http://eepurl.com/byhgL9 <http://eepurl.com/byhgL9> > > > The idea is that this is max one mail per month. > > Marcus

Sept. 7, 2015

Nautilus ;D

by Aliaksei Syrel

Hi In Pharo 50308 Nautilus has strange behaviour. Select "--- all ---" and then press "select all" cmd+A shortcut => duplicated methods. â Also drag and drop of methods is strange now. If I don't have any selected method I can't drag any method. As soon as I select one => drag and drop works for any method. As soon as deselect - doesn't work. Cheers, Alex

Sept. 7, 2015