- Pharo-dev - lists.pharo.org

Re: [Pharo-project] [update 3.0] #30022

by stephane ducasse

Hi igor since you were at the meeting where we built the list of actions, you could also have edited the entry and add more information. Camille was nice to take notes for everbody and to open issues. I added contents. Now we can also use a bad and private wiki to store information that is clear for the core team but it will not be nice. Stef > On 5 April 2013 17:29, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> There does not seem to be any description in the issue tracker either, or maybe I missed it. >> > indeed, the record on issue tracker looks very informative. (in the attached). > >>> On Fri, Apr 5, 2013 at 1:51 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> 30022 >>> ----- >>> >>> 10032 Integrate new debugger >>> https://pharo.fogbugz.com/f/cases/10032 >>> >>> Diff information: >>> http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/DebuggerModel-EstebanLorenza… >>> http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Spec-Debugger-EstebanLorenza… >> > > > > -- > Best regards, > Igor Stasenko. > <Screen Shot 2013-04-05 at 9.23.06 PM.png>

April 6, 2013

Re: [Pharo-project] [update 3.0] #30022

by stephane ducasse

>> > > Indeed, sounds very promising but what does it mean ? > There does not seem to be any description in the issue tracker either, or maybe I missed it. What we integrated is a model (two classes) that andrei wrote based on the old debugger. The old debugger does not make the distinction cleanly between a model and the view. So the logic is mixed with the display. When andrei came at lille he wrote with ben a Spec interface. We should rethink it by the way because I prefer the glamourst one much more :). So this model is good because we can build tools on top. What we plan in the future is to have - to get a new UI based on the model and that this ui via this model still use the old logic (bytecode interpretation and the bugs we get with it) - an AST interpreter and plug it with this model so get a really new debugger execution logic (not a bytecode mapping range to text one) So Pharo30 will have at least two debuggers for a while - the old one but we are rewamped ui and using the model of andrei - the one based on AST interpretation using the rewamped ui and using the model of andrei Stef > >> On Fri, Apr 5, 2013 at 1:51 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> 30022 >> ----- >> >> 10032 Integrate new debugger >> https://pharo.fogbugz.com/f/cases/10032 >> >> Diff information: >> http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/DebuggerModel-EstebanLorenza… >> http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Spec-Debugger-EstebanLorenza… >

April 6, 2013

Re: [Pharo-project] Issue 10219: Completion: enter on accept awkwardness

by Johan Brichau

fwiw, I changed the implementation of NECController to: - accept both <enter> and <tab> for code completion - still use <tab> to first complete the common prefixes, but a subsequent <tab> will select the suggestion i.e. this is the behavior in XCode, which imho is a very good one. _and_ I do not have to disable the completion of common prefixes if I want to disable <enter> for selection. Maybe people should give this a try and see? cheers Johan On 06 Apr 2013, at 02:18, Ben Coman <btc(a)openInWorld.com> wrote: > Alexandre Bergel wrote: >> +1 >> >> Alexandre >> >> >> On Apr 3, 2013, at 8:57 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> >>> +1 >>> >>> Doru >>> >>> >>> On Apr 4, 2013, at 2:19 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: >>> >>> >>>> On 3 April 2013 22:45, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>>> >>>>> theres a setting to: >>>>> >>>>> - disable ENTER to accept the completion >>>>> - to increase the popup delay >>>>> >>>>> so I think that is invalid bug report then... >>>>> >>>>> >>>> i tend to disagree. >>>> The defaults which we have now in 2.0 for autocompletion >>>> is breaking my workflow badly too. >>>> >>>> Yes, i can go to settings and disable/reconfigure stuff but that doesn't >>>> nullifying the fact, that my workflow is broken with ambiguous and inconsistent >>>> reaction(s) to my keystrokes by UI if i keep defaults. >>>> >>>> For instance i am still clueless, why 'enter' is default for autocompletion, >>>> and disabling it and enabling 'tab' simply doesn't works. >>>> That leaves me with the only option: keep using 'enter' for >>>> autocompletion, if i ever want to use it. >>>> We have to fix that. >>>> >>>> >>>> >>>>> On 2013-04-03, at 22:23, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: >>>>> >>>>> >>>>>> From >>>>>> https://pharo.fogbugz.com/f/cases/10219/Completion-enter-on-accept-awkwardn… >>>>>> : >>>>>> >>>>>> >>>>>>> The combination of enter on accept, with the current behavior to select >>>>>>> the first completion suggestion by default = trouble. For example: >>>>>>> >>>>>>> 1. Type "printOn: aStream"... pretty common method start >>>>>>> 2. Hit enter to go to the next line >>>>>>> >>>>>>> You will now have "printOn: MCDataStream" WTF!! I get burned by this >>>>>>> pretty regularly and it's annoying. I'm not sure what the fix should be... >>>>>>> probably no default selection in the suggestion menu, but possibly only >>>>>>> when enter on accept is enabled (t would require an extra key press to >>>>>>> complete and when do you ever type a tab in the middle of a line?) >>>>>>> >>>>>> > I haven't used the 2.0 auto compeltion yet so I don't know if this is relevant, but just a passing thought... When Microsoft Word muck up using smart characters, one small saving grace is that it first enters my original typing before "smart-ifying" it, such that ctrl-z undoes back to my original typing. > > cheers -ben >

April 6, 2013

Re: [Pharo-project] Big thanks for the organization of the Pharo Conf and MooseDay

by stephane ducasse

yes and we should kick athens out. Because I want to see athens based demo at ESUG :) Stef > On 5 April 2013 11:59, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> Thanks again to Doru and SCG >> because the pharo conf was really nice and the moose day too. >> >> Stef >> > > +1 > > this event forced me to make Athens tutorial. And i thank you for that. :) > Hope you liked it. > > -- > Best regards, > Igor Stasenko. >

April 6, 2013

Re: [Pharo-project] Pharo Theming: does anyone have some doc?

by stephane ducasse

> > > Also, the STHStyler80 class coloring schemes are nice and well, but without an editor, good luck w/ the colors. That's an area where spec would come in handy. About that, I read that some paper would surface explaining spec a bit more. I updated the SVN but didn't saw anything conclusive. Is there something? We did not work on the spec tutorial there is only the old spec techreport available for now. Stef

April 6, 2013

Re: [Pharo-project] Fwd: Game prototype with Amber deployed

by S Krish

Impressive..! On Fri, Apr 5, 2013 at 5:46 PM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > I forward this to Pharo project it might interest some of you too. > > ---------- Forwarded message ---------- > From: ClÃ©ment Bera <bera.clement(a)gmail.com> > Date: 2013/4/5 > Subject: Game prototype with Amber deployed > To: amber-lang(a)googlegroups.com > > > Hello amber community, > > Eight months ago I met Nicolas Petton, discovered Amber and developed a > game prototype with it. Recently Nicolas Petton asked me if I could deploy > it to show examples of what you can do with Amber. So* I spent several > hours reading / updating my old code, updating to latest amber version and > I deployed a beta version here :* > > http://clementbera.github.com/amber/projects/easnoth/fight2players.html?map… > > According to my tests on Mac OS X, on : > - Firefox it works fine > - Google Chrome it works fine the first time (cache problem) with the *best > animation experience* but there is a problem when you refresh the page > - Safari it works fine the first time but there is a huge cache problem, > so you need to close safari and reopen it to reopen the page. > > There is no AI, so you have to play two player on the same computer for > now. Unfortunately I disabled a lot of functionality in this deployed > version because most of them were not stable but only prototypes. Also, I > developed that when I was a student and I am ashamed of the bad quality of > the code ... *I'm going to refactor and work on it in the next two months > to go to a true release* *at the end of May*. And I'll fix this cache > problem on Safari and Chrome :). I let on purpose amber in non deploy mode > so you can browse the bad code if you want to (and to show it is open > source). > > This is my first use of git (I used monticello and svn only before) and > the repo seems to be not correct. I will change that so the beta version > link might be obselete in a few days. > > By the way *congratulations for Amber it is really cool.* > > Are the workspace DoIt working the same way in helios that in the previous > browser ? Like you need to declare temp variables in the contrary of all > the other smalltalk systems ? If so I'd like to hack in your compiler Nico > to change that. > > > > > >

April 6, 2013

Re: [Pharo-project] Issue 10219: Completion: enter on accept awkwardness

by Ben Coman

Alexandre Bergel wrote: > +1 > > Alexandre > > > On Apr 3, 2013, at 8:57 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > >> +1 >> >> Doru >> >> >> On Apr 4, 2013, at 2:19 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: >> >> >>> On 3 April 2013 22:45, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>> >>>> theres a setting to: >>>> >>>> - disable ENTER to accept the completion >>>> - to increase the popup delay >>>> >>>> so I think that is invalid bug report then... >>>> >>>> >>> i tend to disagree. >>> The defaults which we have now in 2.0 for autocompletion >>> is breaking my workflow badly too. >>> >>> Yes, i can go to settings and disable/reconfigure stuff but that doesn't >>> nullifying the fact, that my workflow is broken with ambiguous and inconsistent >>> reaction(s) to my keystrokes by UI if i keep defaults. >>> >>> For instance i am still clueless, why 'enter' is default for autocompletion, >>> and disabling it and enabling 'tab' simply doesn't works. >>> That leaves me with the only option: keep using 'enter' for >>> autocompletion, if i ever want to use it. >>> We have to fix that. >>> >>> >>> >>>> On 2013-04-03, at 22:23, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: >>>> >>>> >>>>> From >>>>> https://pharo.fogbugz.com/f/cases/10219/Completion-enter-on-accept-awkwardn… >>>>> : >>>>> >>>>> >>>>>> The combination of enter on accept, with the current behavior to select >>>>>> the first completion suggestion by default = trouble. For example: >>>>>> >>>>>> 1. Type "printOn: aStream"... pretty common method start >>>>>> 2. Hit enter to go to the next line >>>>>> >>>>>> You will now have "printOn: MCDataStream" WTF!! I get burned by this >>>>>> pretty regularly and it's annoying. I'm not sure what the fix should be... >>>>>> probably no default selection in the suggestion menu, but possibly only >>>>>> when enter on accept is enabled (t would require an extra key press to >>>>>> complete and when do you ever type a tab in the middle of a line?) >>>>>> >>>>> I haven't used the 2.0 auto compeltion yet so I don't know if this is relevant, but just a passing thought... When Microsoft Word muck up using smart characters, one small saving grace is that it first enters my original typing before "smart-ifying" it, such that ctrl-z undoes back to my original typing. cheers -ben

April 6, 2013

Re: [Pharo-project] Issue 10219: Completion: enter on accept awkwardness

by Alexandre Bergel

+1 Alexandre On Apr 3, 2013, at 8:57 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > +1 > > Doru > > > On Apr 4, 2013, at 2:19 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > >> On 3 April 2013 22:45, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>> theres a setting to: >>> >>> - disable ENTER to accept the completion >>> - to increase the popup delay >>> >>> so I think that is invalid bug report then... >>> >> >> i tend to disagree. >> The defaults which we have now in 2.0 for autocompletion >> is breaking my workflow badly too. >> >> Yes, i can go to settings and disable/reconfigure stuff but that doesn't >> nullifying the fact, that my workflow is broken with ambiguous and inconsistent >> reaction(s) to my keystrokes by UI if i keep defaults. >> >> For instance i am still clueless, why 'enter' is default for autocompletion, >> and disabling it and enabling 'tab' simply doesn't works. >> That leaves me with the only option: keep using 'enter' for >> autocompletion, if i ever want to use it. >> We have to fix that. >> >> >>> On 2013-04-03, at 22:23, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: >>> >>>> From >>>> https://pharo.fogbugz.com/f/cases/10219/Completion-enter-on-accept-awkwardn… >>>> : >>>> >>>>> The combination of enter on accept, with the current behavior to select >>>>> the first completion suggestion by default = trouble. For example: >>>>> >>>>> 1. Type "printOn: aStream"... pretty common method start >>>>> 2. Hit enter to go to the next line >>>>> >>>>> You will now have "printOn: MCDataStream" WTF!! I get burned by this >>>>> pretty regularly and it's annoying. I'm not sure what the fix should be... >>>>> probably no default selection in the suggestion menu, but possibly only >>>>> when enter on accept is enabled (t would require an extra key press to >>>>> complete and when do you ever type a tab in the middle of a line?) >>>> >>>> >>>> >>>> >>>> >>>> ----- >>>> Cheers, >>>> Sean >>>> -- >>>> View this message in context: http://forum.world.st/Issue-10219-Completion-enter-on-accept-awkwardness-tp… >>>> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >>>> >>> >>> >> >> >> >> -- >> Best regards, >> Igor Stasenko. >> > > -- > www.tudorgirba.com > > "Not knowing how to do something is not an argument for how it cannot be done." > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 5, 2013

[Pharo-project] [ANN] Physical Etoys 2.1 released!

by Ricardo Moran

Hi everybody (and sorry if you receive multiple copies), It's been a while since our last version but we're proud to announce a new release of Physical Etoys. You can download it from here: http://tecnodacta.com.ar/gira/projects/physical-etoys/ This new version includes: * Full support for the DuinoBot kit ( http://www.kickstarter.com/projects/1689254125/multiplo-create-your-own-rob… ). * New objects such as the Timer and the IR receiver. * More example projects to help you get started. * And of course, lots of bug fixes and minor UI enhancements. All in all, this version is much better than the previous and we hope you would enjoy it as much as we do :). Thanks! Richo

April 5, 2013

Re: [Pharo-project] How to define a ConfigurationOf with a #development version that depends on a baseline?

by Alexandre Bergel

Just a question: Is there any plan for a Metacello 2? We have learnt a lot and we have a clear idea on a number of versioning scenarios. What do we want the future of packaging in Pharo to look like? Alexandre On Apr 2, 2013, at 7:15 AM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > http://stackoverflow.com/questions/15762706/how-to-define-a-configurationof… > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 5, 2013