October 2014 - Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

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

Oct. 7, 2014

[pharo-project/pharo-core] 540247: 40287

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 540247e6a0a41db6b7409810838453d45c3e4995 https://github.com/pharo-project/pharo-core/commit/540247e6a0a41db6b7409810… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-10-07 (Tue, 07 Oct 2014) Changed paths: A Deprecated40.package/extension/MorphicUIManager/instance/request_initialAnswer_centerAt_.st A Deprecated40.package/extension/NonInteractiveUIManager/instance/request_initialAnswer_centerAt_.st A Deprecated40.package/extension/UIManager/instance/displayProgress_at_from_to_during_.st A Deprecated40.package/extension/UIManager/instance/request_initialAnswer_centerAt_.st M Morphic-Widgets-Tree.package/MorphTreeModel.class/instance/announcing/on_send_to_.st M Morphic-Widgets-Tree.package/MorphTreeMorph.class/instance/announce requests/registerRequestHandlers.st M OpalCompiler-Core.package/AbstractCompiler.class/class/settings/compilerSettingsOn_.st R OpalCompiler-Core.package/CCompilationContext.class/class/accessing/allowBlockArgumentAssignment.st R OpalCompiler-Core.package/CCompilationContext.class/instance/accessing/allowBlockArgumentAssignment.st R OpalCompiler-Core.package/CompilationContext.class/class/accessing/allowBlockArgumentAssignment.st R OpalCompiler-Core.package/CompilationContext.class/class/accessing/allowBlockArgumentAssignment_.st M OpalCompiler-Core.package/CompilationContext.class/definition.st R OpalCompiler-Core.package/CompilationContext.class/instance/accessing/allowBlockArgumentAssignment.st R OpalCompiler-Core.package/OCASTSemanticAnalyzer.class/instance/variables/checkVariableIsWritable_.st M OpalCompiler-Core.package/OCASTSemanticAnalyzer.class/instance/variables/lookupVariableForWrite_.st R Polymorph-Widgets.package/MorphicUIManager.class/instance/ui requests/request_initialAnswer_centerAt_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script287.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40287.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st R UIManager.package/NonInteractiveUIManager.class/instance/ui requests/request_initialAnswer_centerAt_.st R UIManager.package/UIManager.class/instance/deprecated/displayProgress_at_from_to_during_.st R UIManager.package/UIManager.class/instance/deprecated/request_initialAnswer_centerAt_.st Log Message: ----------- 40287 14179 deprecate the method in UIManager "deprecated" category https://pharo.fogbugz.com/f/cases/14179 14162 Replace Announcer>>#on:send:to:s senders in Morphic-Widgets-Tree https://pharo.fogbugz.com/f/cases/14162 14173 remove #allowBlockArgumentAssignment preference https://pharo.fogbugz.com/f/cases/14173 http://files.pharo.org/image/40/40287.zip

Oct. 7, 2014

Re: [Pharo-dev] WhatsUp from: 2014-10-06 until: 2014-10-19

by Tudor Girba

I mean, thank you for comparing the two. The work on Tide belongs to Esteban and Nicolas :) Cheers, Doru On Tue, Oct 7, 2014 at 11:46 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Thank you! > > Please let us know what you find. > > Doru > > > On Tue, Oct 7, 2014 at 11:42 AM, S Krish < > krishnamachari.sudhakar(a)gmail.com> wrote: > >> >> >> Tide is quite complete.. !!.. Didnt notice it at all. >> >> Will try it out / perhaps compare it too to Flow. >> >> >> >> On Mon, Oct 6, 2014 at 11:23 PM, Tudor Girba <tudor(a)tudorgirba.com> >> wrote: >> >>> Nice. Still, my question remains: how does it compare with Tide? Or >>> better yet, would you not be interested in collaborating around Tide? >>> >>> Cheers, >>> Doru >>> >>> On Mon, Oct 6, 2014 at 5:56 PM, Sebastian Sastre < >>> sebastian(a)flowingconcept.com> wrote: >>> >>>> >>>> - Iâve realized that this email was a social media done with email, >>>> cool :) BTW I think feeding a blog with this thread would be interesting, >>>> what do you think? >>>> - presented flow <https://github.com/flow-stack/flow> at >>>> CampSmalltalkVI2014, good reception, mostly offline but also slides have >>>> ~360 views already >>>> - added a couple of cool and very needed features to it (related to >>>> double data-binding in the frontend) >>>> - preparing to add some real-time features to it (in its Pharo backend) >>>> >>>> >>>> >>>> >>>> On Oct 6, 2014, at 2:00 AM, seaside(a)rmod.lille.inria.fr wrote: >>>> >>>> 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: >>>> >>>> - >>>> $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS >>>> >>>> ### What's next, until 2014-10-19 (*): >>>> >>>> - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION >>>> >>>> (*) we'll be expecting results by then ;) >>>> >>>> >>>> >>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Every thing has its own flow" >>> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > -- www.tudorgirba.com "Every thing has its own flow"

Oct. 7, 2014

Re: [Pharo-dev] WhatsUp from: 2014-10-06 until: 2014-10-19

by Tudor Girba

Thank you! Please let us know what you find. Doru On Tue, Oct 7, 2014 at 11:42 AM, S Krish <krishnamachari.sudhakar(a)gmail.com> wrote: > > > Tide is quite complete.. !!.. Didnt notice it at all. > > Will try it out / perhaps compare it too to Flow. > > > > On Mon, Oct 6, 2014 at 11:23 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> Nice. Still, my question remains: how does it compare with Tide? Or >> better yet, would you not be interested in collaborating around Tide? >> >> Cheers, >> Doru >> >> On Mon, Oct 6, 2014 at 5:56 PM, Sebastian Sastre < >> sebastian(a)flowingconcept.com> wrote: >> >>> >>> - Iâve realized that this email was a social media done with email, cool >>> :) BTW I think feeding a blog with this thread would be interesting, what >>> do you think? >>> - presented flow <https://github.com/flow-stack/flow> at >>> CampSmalltalkVI2014, good reception, mostly offline but also slides have >>> ~360 views already >>> - added a couple of cool and very needed features to it (related to >>> double data-binding in the frontend) >>> - preparing to add some real-time features to it (in its Pharo backend) >>> >>> >>> >>> >>> On Oct 6, 2014, at 2:00 AM, seaside(a)rmod.lille.inria.fr wrote: >>> >>> 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: >>> >>> - >>> $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS >>> >>> ### What's next, until 2014-10-19 (*): >>> >>> - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION >>> >>> (*) we'll be expecting results by then ;) >>> >>> >>> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> > > -- www.tudorgirba.com "Every thing has its own flow"

Oct. 7, 2014

Re: [Pharo-dev] WhatsUp from: 2014-10-06 until: 2014-10-19

by S Krish

Tide is quite complete.. !!.. Didnt notice it at all. Will try it out / perhaps compare it too to Flow. On Mon, Oct 6, 2014 at 11:23 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Nice. Still, my question remains: how does it compare with Tide? Or better > yet, would you not be interested in collaborating around Tide? > > Cheers, > Doru > > On Mon, Oct 6, 2014 at 5:56 PM, Sebastian Sastre < > sebastian(a)flowingconcept.com> wrote: > >> >> - Iâve realized that this email was a social media done with email, cool >> :) BTW I think feeding a blog with this thread would be interesting, what >> do you think? >> - presented flow <https://github.com/flow-stack/flow> at >> CampSmalltalkVI2014, good reception, mostly offline but also slides have >> ~360 views already >> - added a couple of cool and very needed features to it (related to >> double data-binding in the frontend) >> - preparing to add some real-time features to it (in its Pharo backend) >> >> >> >> >> On Oct 6, 2014, at 2:00 AM, seaside(a)rmod.lille.inria.fr wrote: >> >> 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: >> >> - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS >> >> ### What's next, until 2014-10-19 (*): >> >> - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION >> >> (*) we'll be expecting results by then ;) >> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Oct. 7, 2014

Re: [Pharo-dev] gt issues

by Christophe Demarey

Hi Doru, Le 6 oct. 2014 Ã 23:33, Tudor Girba a Ã©crit : > Hi Christophe, > > We will start with adding the possibility of closing the last pane. It is unlikely that we will add closing of random panes in the inspector because the main purpose of those panes is to preserve the navigation path. > > For preserving inspectors on independent objects, we need another solution. I believe for this case, we could simply use a kind of a clipboard for objects that can be inspected at a later time. It may be an idea. I was just thinking on another possibility: if you want to keep the navigation history, just get a way to quickly identify valuable tabs and be able to navigate quickly between them. Maybe something like the star/unstar feature of GitHub. Anyway, the important thing to remember is that there is a need for a way to keep some objects that we would to inspect later, whatever the implementation is. Regards, Christophe.

Oct. 7, 2014

Re: [Pharo-dev] DNUs in the styler

by Marcus Denker

> On 07 Oct 2014, at 08:02, stepharo <stepharo(a)free.fr> wrote: > > Marcus can you open a roadmap file on github so that we know and can take action. > This is a nice way to share knowledge and possible actions. Ok, I will write something. > Stef > >>> I had the setting on "use AST styler" which explains the DNUs. I turned it off so that's solved. >>> >> Yes, this is not completely working yetâ¦ we need to do the move and fix all the bugsâ¦ >> >>> The sequence above shows that the RBParserErrorNode thing [1] works in some cases and not all. >>> >>> Are you planning something in that area? >>> >> >> Planning yesâ¦ but not started yetâ¦ I need to finish other things before. So every contribution is welcome... >> >>> Thierry >>> >>> [1] encapsulating a syntax error in a RBParserErrorNode so that: styling can happen on a correct part of the code; and that (maybe) parsing can continue. >>> >>> >> > >

Oct. 7, 2014

Re: [Pharo-dev] ANNC: QR Code (v.2)

by stepharo

this is cool I want discussing with olivier and do you think that it would be easy to produce pdf (beside cropping the morph and saving it as png) On 6/10/14 17:49, J.F. Rick wrote: > I've got a new version of the QR Code generator: > http://smalltalkhub.com/#!/~JochenRick/QRCode > <http://smalltalkhub.com/#%21/%7EJochenRick/QRCode> > > This one includes support for MicroQR, for UTF-8 encoding and other > aspects of the latest QR standard (e.g., mirroring). I've also written > a small Zinc web app which makes it easy to try out. > > Enjoy! > > Jeff > > -- > Jochen "Jeff" Rick, Ph.D. > http://www.je77.com/ > Skype ID: jochenrick

Oct. 7, 2014

Re: [Pharo-dev] WhatsUp from: 2014-10-06 until: 2014-10-19

by stepharo

On 6/10/14 07:00, seaside(a)rmod.lille.inria.fr wrote: > 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: > - translating to english artefact - started to work on EntreprisePharo book with Sven and Damien. - cleaning cleaning cleaning... > > ### What's next, until 2014-10-19 (*): > - Organizing Pharo Days -

Oct. 7, 2014

Re: [Pharo-dev] GT-Inspector silly titles

by Tudor Girba

Hi, It is like that. Only I added it with gtDisplayString because GT was external. We can now introduce it in the base system and remove gtDisplayString. In the meantime, Sven fixed the title problem. Cheers, Doru On Tue, Oct 7, 2014 at 8:17 AM, stepharo <stepharo(a)free.fr> wrote: > doru > > why we do not introduce displayString as suggested long time ago and > default displayString to printString? > > Stef > > On 6/10/14 13:33, Tudor Girba wrote: > > Hi, > > Yes, the label does introduce redundancy in some cases, but that is > because the use of printString has to be rethought :) > > printString was used for a long time as a primary inspection tool. > Because of that it tries to do too much (like adding the class name), and > it is certainly not suitable for a label. > > gtDisplayString is meant for labeling the content of the object. It is > used also for things like a list. As soon as you will do something with > your objects, you will want to have something smaller. There is no need to > have the class part of that string. Relying on that convention is brittle, > as it is easy for people to not have the class name in there. But, for an > inspector, having the class at all times is a prerequisite, so that will be > displayed always separately (to ensure that the right information is > offered). > > gtDisplayString relies on printString by default, so people can provide > the labels at their convenience. > > Cheers, > Doru > > > On Mon, Oct 6, 2014 at 1:20 PM, Sven Van Caekenberghe <sven(a)stfx.eu> > wrote: > >> I think the titles of GT-Inspector windows/panes are a bit silly: >> >> >> Notice the 'a ZnClient(a ZnClient)' and 'a Dictionary(a >> Dictionary(...))' where the class name is repeated. >> >> I think it is very important to honour the standard/general Smalltalk >> approach and assume the #printString already contains the class name. If >> not, you are basically punishing everybody who went through the trouble of >> writing custom #printString implementation (like me, I do this for most >> classes). >> >> I saw the whole #display thing, but you can't force everybody to >> rewrite #printString to #gtDisplayString or whatever. >> >> Sven >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > -- www.tudorgirba.com "Every thing has its own flow"

Oct. 7, 2014