May 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Making ASTInterpreter work with opal bindings

by Marcus Denker

On May 14, 2013, at 2:09 PM, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > Right now, in the image there exist two ways to annotate an AST: > - the Opal way > - the RB Way > > We should simplify that by having only one. So far, the only user of the RB bindings is the ASTInterpreter + the RB tests. > > So, I prepared a slice and issue [1], with the following details > > - annotate ast using opal annotator > - extended OCBindings to read and write from an AST interpreter > - not yet made a difference between arg nodes with a different class (just put an if) I think it might be a good idea to add thatâ¦ what I will do first is to cleanup the OCTemp vars a bit (there is an index variable that is used to sort them at the end, a leftover from back before the closures when there was simple temp=index mapping). > - i didnt add inst vars into the opal bindings for the binding->node relation as in RB, I send the node as a parameter We need to check this, back pointers are always interesting (but I am not sure if we have a new semantic variable or if we reuse it for multiple nodes?) > - I had to adapt the #compile: into ASTInterpreter because > - opal does not annotate other than method nodes Yes, this is because when compiling an expression we transform it do the doIt method before. Expressions can not be compiled standalone. > - undeclared variables raised warnings, not errors > Yes, the idea is that in interactive mode it does user=interaction, while in non-interactive it compiled an Undeclared. (so that the code stays loadable). Maybe the interpreter could do the same an fall back to Undeclared, that it, undeclared vars are just treated as nil. Marcus

May 16, 2013

Re: [Pharo-dev] Doubt about RING

by Marcus Denker

On May 15, 2013, at 9:43 PM, Sebastian Tleye <stleye(a)gmail.com> wrote: > Thanks Igor, i think you are right. > I am not sure what "isObsolete" does, but for Ring classes, which are created dinamically, it doesn't seem that "isObsolete" is useful. (at least is my intuition) > Obsolete classes happen if you delete a class, yet there are still instances. This is needed as classes do not model history. But a) Ring classes are not directly instantiated (they are not referenced from the header of the instances) b) They even are able to model history very nicely So the obsolete concept makes no senseâ¦ an obsolete class might even have a (Historical) Ring class associated with it and Ring would have no problem at all. Marcus

May 16, 2013

[update 3.0] #30134

by Marcus Denker

30134 ----- 7517 Spec: Document TextModel vs. TextInputFieldModel https://pharo.fogbugz.com/f/cases/7517 10629 Suggestions not working for deprecated ui icons https://pharo.fogbugz.com/f/cases/10629 10623 World is not properly updating layout https://pharo.fogbugz.com/f/cases/10623 10624 WolrdModel does not support delete https://pharo.fogbugz.com/f/cases/10624 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Widgets-MarcusDenker.167… http://smalltalkhub.com/mc/Pharo/Pharo30/main/SmartSuggestions-MarcusDenker… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Morphic-MarcusDenker.1434.diff

May 16, 2013

Re: [Pharo-dev] vm fixes

by btc＠openinworld.com

Could this be used make Pharo dual-screened ? If yes, what would be the limitations ? cheers -ben Benjamin wrote: > In the following picture, instead of doing the classical > MessageBrowser new openWithSpec, and get a Morphic window inside the os window > of Pharo > > I do > MessageBrowser openWorldWithSpec > And here the message browser window *is* the system window. > Basically, it sticks the morph on the world, do some magic around, and voilÃ . > The cool part is that the rest of the code do not change at all, and still it > opens a the good size, the title is properly updated etc > > > > Ben > > On May 14, 2013, at 10:28 PM, Tudor Girba <tudor(a)tudorgirba.com > <mailto:tudor@tudorgirba.com>> wrote: > > > This sounds intriguing. Can you be more specific? :) > > > > Doru > > > > > > On May 14, 2013, at 10:23 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com > > <mailto:benjamin.vanryseghem.pharo@gmail.com>> wrote: > > > >> Thank you :) > >> > >> This fix goes with pair with > >> https://pharo.fogbugz.com/default.asp?10619 > >> > >> Thanks to Esteban, one can now deploy a Spec widget with the os window as > >> window :) > >> > >> Ben > >> > >> On May 14, 2013, at 10:19 PM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > >> > >>> thanks esteban! > >>> > >>> On May 14, 2013, at 9:54 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >>> > >>>> Hi, > >>>> > >>>> I just pushed fix for a weird bug in cocoa cog vm. > >>>> It was crashing image when resizing using DisplayScreen>>#hostWindowSize: > >>>> but even worst, some times was crashing also when dragging a window > >>>> outside the world screen... > >>>> > >>>> The fix is there, but you will need to wait until tomorrow to have it in > >>>> zeroconf (because of weird mac jenkins slave permissions). > >>>> > >>>> This increases a bit more the VM stability, still not perfect, but we are > >>>> getting closer :) > >>>> > >>>> Esteban > >>> > >>> > >> > > > > -- > > www.tudorgirba.com <http://www.tudorgirba.com> > > > > "Presenting is storytelling." > > > > > >

May 16, 2013

Re: [Pharo-dev] TxTextLayout

by Benjamin

+1 Ben On May 15, 2013, at 10:18 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > I have a question concerning the new TxText layout. > How hard is it support inline non-text nodes (aka inline morphs) in a text layout? > > My dream is still to be able to drag and drop an "instance" from an inspector to a workspace and do some operations on it using standard smalltalk. The only difference here would be instead of using a variable or expression to get an instance of something I would have a textual/visual node directly representing an instance! > > best regard, > camillo

May 15, 2013

TxTextLayout

by Camillo Bruni

I have a question concerning the new TxText layout. How hard is it support inline non-text nodes (aka inline morphs) in a text layout? My dream is still to be able to drag and drop an "instance" from an inspector to a workspace and do some operations on it using standard smalltalk. The only difference here would be instead of using a variable or expression to get an instance of something I would have a textual/visual node directly representing an instance! best regard, camillo

May 15, 2013

Re: [Pharo-dev] Doubt about RING

by Sebastian Tleye

Thanks Igor, i think you are right. I am not sure what "isObsolete" does, but for Ring classes, which are created dinamically, it doesn't seem that "isObsolete" is useful. (at least is my intuition) 2013/5/15 Igor Stasenko <siguctua(a)gmail.com> > On 15 May 2013 11:29, Sebastian Tleye <stleye(a)gmail.com> wrote: > > Hello > > > > I am making some modifications in the smalltalk meta-model and i need > > to replace classes with Ring classes (it is supposed to be possible since > > they are polymorphic) > > But i am having a little problem, all the classes know how to answer the > > message "isObsolete" > > but Ring classes doesn't, to solve this i have defined the method > > "isObsolete" in RGBehaviorDefinition > > but i am not sure which code does it need > > > > - if i copy and paste the code from Behavior, then i obtain more > > "doesNotUnderstand" messages > > since the code from Behavior>>isObsolete is "self instanceCount = 0" but > > Ring classes doesn't know how to answer "instanceCount" neither > > so i suspect this is not the right way to do it. > > > > - if i copy the code from Class, then it seems it works, but the result > from > > for example > > "Array isObsolete" is different of the result from "Array > asRingDefinition > > isObsolete" consequently > > well.. #isObsolete for model classes doesn't makes any sense. > i would just answer false to this message. > and i would ask why this message is ever sent. because this is not > something > essential to class model. > > > next messages obtain different results and finally a a > "doesNotUnderstand" > > message again. > > > > Am i doing something wrong? Any suggestion? > > > > -- > Best regards, > Igor Stasenko. > >

May 15, 2013

Re: [Pharo-dev] About the Mailinglist debacle...

by Tudor Girba

+100 :) Doru On May 15, 2013, at 8:37 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 15 May 2013, at 20:01, Max Leske <maxleske(a)gmail.com> wrote: > >> Thanks for the effort Markus! > > +10 > > And let's hope the lists are stable now. > >> On 15.05.2013, at 19:52, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >>> Hello, >>> >>> So now that everything is workingâ¦ sorry for the mess. >>> >>> We should have left the gforge infrastructure the last time we had a multi-day problem, >>> not wait till we get it again. >>> >>> I think this will be my new principle: second real problem -> I leave. No discussions. >>> We already saw with the jenkins story just how deadly bad infrastructure is. >>> >>> So what happened was that last Tuesday, the lists (all lists of gforge) stopped delivering. >>> Why is not clear, seemingly it was not gforge itself but the upstream servers did >>> not deliver. Whatever. >>> What is clear is that it was completely unclear how long this would take, and that we >>> needed a solution after nearly a week of waiting. >>> >>> So we decided to move the lists. Of course with the old lists down, this was harder than >>> normal (even involved parsing the html to get the subscribersâ¦) but that is not important. >>> >>> Now the problem its hat Mailman does not distinguish between people that unsubscribe, >>> and those turning off delivery. So there where just a lot of people listed with "nomail (U)", >>> >>> What to do? It was clear that we can't just subscribe lots of people to a list that they *actively* >>> unsubscribed. So the only option was to skip those by >>> -> unsubscribing them from the old list >>> -> then get the list of subscribers >>> -> put that in the new list. >>> >>> The only people that will see a bad effect are those using e.g nabble to read the list. But those >>> would see the new mails, too. The only problem they have is if the want to send. So not *that* of >>> a big deal. >>> >>> It seems that we got quite some false positive subscribers anyway in the form of people who filtered >>> the mails and then with the new list the filter did not work and they suddenly saw mails of a long forgotten >>> list. We even had the case of people who where "nomail (U)", yet they did get mails delivered. How >>> that can possibly work, I have no clue *at all*. >>> >>> What else is missing (and on my TODO since Sunday/Monday, sorry for not yet acting on it): >>> >>> -> lists.pharo.org has an empty page and needs to point to the list of the lists inttead >>> -> the archive needs to be moved from the old jenkins. >>> -> the (incomplete) archive of the new lists is not working since I put it as public. >>> >>> Soâ¦ maybe it would have been better to just wait until gforge works again and then moveâ¦ but >>> it was just far too long already and not clear when it would be working again. >>> >>> Marcus >> >> > > -- www.tudorgirba.com "Problem solving efficiency grows with the abstractness level of problem understanding."

May 15, 2013

Re: [Pharo-dev] About the Mailinglist debacle...

by Sven Van Caekenberghe

On 15 May 2013, at 20:01, Max Leske <maxleske(a)gmail.com> wrote: > Thanks for the effort Markus! +10 And let's hope the lists are stable now. > On 15.05.2013, at 19:52, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> Hello, >> >> So now that everything is workingâ¦ sorry for the mess. >> >> We should have left the gforge infrastructure the last time we had a multi-day problem, >> not wait till we get it again. >> >> I think this will be my new principle: second real problem -> I leave. No discussions. >> We already saw with the jenkins story just how deadly bad infrastructure is. >> >> So what happened was that last Tuesday, the lists (all lists of gforge) stopped delivering. >> Why is not clear, seemingly it was not gforge itself but the upstream servers did >> not deliver. Whatever. >> What is clear is that it was completely unclear how long this would take, and that we >> needed a solution after nearly a week of waiting. >> >> So we decided to move the lists. Of course with the old lists down, this was harder than >> normal (even involved parsing the html to get the subscribersâ¦) but that is not important. >> >> Now the problem its hat Mailman does not distinguish between people that unsubscribe, >> and those turning off delivery. So there where just a lot of people listed with "nomail (U)", >> >> What to do? It was clear that we can't just subscribe lots of people to a list that they *actively* >> unsubscribed. So the only option was to skip those by >> -> unsubscribing them from the old list >> -> then get the list of subscribers >> -> put that in the new list. >> >> The only people that will see a bad effect are those using e.g nabble to read the list. But those >> would see the new mails, too. The only problem they have is if the want to send. So not *that* of >> a big deal. >> >> It seems that we got quite some false positive subscribers anyway in the form of people who filtered >> the mails and then with the new list the filter did not work and they suddenly saw mails of a long forgotten >> list. We even had the case of people who where "nomail (U)", yet they did get mails delivered. How >> that can possibly work, I have no clue *at all*. >> >> What else is missing (and on my TODO since Sunday/Monday, sorry for not yet acting on it): >> >> -> lists.pharo.org has an empty page and needs to point to the list of the lists inttead >> -> the archive needs to be moved from the old jenkins. >> -> the (incomplete) archive of the new lists is not working since I put it as public. >> >> Soâ¦ maybe it would have been better to just wait until gforge works again and then moveâ¦ but >> it was just far too long already and not clear when it would be working again. >> >> Marcus > >

May 15, 2013

Re: [Pharo-dev] About the Mailinglist debacle...

by Max Leske

Thanks for the effort Markus! On 15.05.2013, at 19:52, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hello, > > So now that everything is workingâ¦ sorry for the mess. > > We should have left the gforge infrastructure the last time we had a multi-day problem, > not wait till we get it again. > > I think this will be my new principle: second real problem -> I leave. No discussions. > We already saw with the jenkins story just how deadly bad infrastructure is. > > So what happened was that last Tuesday, the lists (all lists of gforge) stopped delivering. > Why is not clear, seemingly it was not gforge itself but the upstream servers did > not deliver. Whatever. > What is clear is that it was completely unclear how long this would take, and that we > needed a solution after nearly a week of waiting. > > So we decided to move the lists. Of course with the old lists down, this was harder than > normal (even involved parsing the html to get the subscribersâ¦) but that is not important. > > Now the problem its hat Mailman does not distinguish between people that unsubscribe, > and those turning off delivery. So there where just a lot of people listed with "nomail (U)", > > What to do? It was clear that we can't just subscribe lots of people to a list that they *actively* > unsubscribed. So the only option was to skip those by > -> unsubscribing them from the old list > -> then get the list of subscribers > -> put that in the new list. > > The only people that will see a bad effect are those using e.g nabble to read the list. But those > would see the new mails, too. The only problem they have is if the want to send. So not *that* of > a big deal. > > It seems that we got quite some false positive subscribers anyway in the form of people who filtered > the mails and then with the new list the filter did not work and they suddenly saw mails of a long forgotten > list. We even had the case of people who where "nomail (U)", yet they did get mails delivered. How > that can possibly work, I have no clue *at all*. > > What else is missing (and on my TODO since Sunday/Monday, sorry for not yet acting on it): > > -> lists.pharo.org has an empty page and needs to point to the list of the lists inttead > -> the archive needs to be moved from the old jenkins. > -> the (incomplete) archive of the new lists is not working since I put it as public. > > Soâ¦ maybe it would have been better to just wait until gforge works again and then moveâ¦ but > it was just far too long already and not clear when it would be working again. > > Marcus

May 15, 2013