- Pharo-dev - lists.pharo.org

[Pharo-project] Pharo brainstorming workshop to produce Request For Improvements

by StÃ©phane Ducasse

Hi guys we often meet to hack together and I would really like to take the time that as a group we think about the improvements we want for the system. For example luc and noury told me that the finalization for socket was brittle or combersome to use and I imagine many other cases. I would like that we collect them so that we can address such points. So it would be good if we could organize a workshop where we do not code but produce Documented Requests for Improvement. Name Description: one line description Problem: Solution: What do you think? Stef

Feb. 21, 2013

Re: [Pharo-project] [squeak-dev] code coverage

by Frank Shearar

On 21 February 2013 19:52, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > Hi All, > > anyone have any bytecode-to-bytecode transformation tools for > doing basic-block resolution coverage? Is it possible that Jejak [1] might vaguely fit this bill? It's a tracing tool, but maybe one could hack something on the side to turn it into a coverage tool? Certainly I've wanted a fine resolution (branch/block level) coverage tool for a long time. frank [1] http://lists.gforge.inria.fr/pipermail/pharo-project/2012-July/067679.html

Feb. 21, 2013

Re: [Pharo-project] A matter with Delays

by Eliot Miranda

On Thu, Feb 21, 2013 at 3:28 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > Hi. > > There is one thing which is IMO an over-engineering artifact: > - when system goes down (image shutdown), all currently scheduled > delays are "saved" > and then when image starting up they are rescheduled again to keep > waiting what time is left for delay.. Right now one says Delay forMilliseconds: n etc. That's clearly a duration. An API which said Delay until: aTime is different, and could be added to the current API easily. One good reason for keeping the current behaviour is profiling image shutdown and startup. The current MessageTally is slightly broken in this regard but I fixed it at Cadence to profile our start-up slowness. So please consider carefully throwing this behaviour away. I at least find it quite useful. > > But the problem is that it does not takes into account the total time > an image was frozen, and the requirement is quite ambiguous: > > - if you put a process on a delay for 5 minutes, then immediately > save image, and then restart it 10 minutes (or 1 year) after, > should this delay keep waiting for 4 +x seconds which is left? Or > should we consider this delay as utterly expired? > (and as you can see, the answer is different, if we counting time > using real, physical time, or just image uptime). > > And why counting image uptime? Consider use cases, like connection > timeout.. it is all about > real time , right here , right now.. will it matter to get socket > connection timeout error when you restart some image 1 year after? > Please, give me a scenario, which will illustrate that we cannot live > without it and should count image uptime for delays, because i can't > find one. > > If not, then to my opinion, and to simplify all logic inside delay > code, i would go straight and declare following: > - when new image session starts, all delays, no matter for how long > they are scheduled to wait are considered expired (and therefore all > waiting processes > is automatically resumed). > > Because as tried to demonstrate, the meaning of delay which spans over > multiple image sessions is really fuzzy and i would be really > surprised to find a code > which relies on such behavior. > > This change will also can be helpful with terminating all processes > which were put on wait for too long (6304550344559763 milliseconds) by > mistake or such. > > > -- > Best regards, > Igor Stasenko. > -- best, Eliot

Feb. 21, 2013

[Pharo-project] code coverage

by Eliot Miranda

Hi All, anyone have any bytecode-to-bytecode transformation tools for doing basic-block resolution coverage? -- best, Eliot

Feb. 21, 2013

[Pharo-project] PharoConf Tutorial

by Benjamin

Hi guys, if I do a Spec tutorial at Bern for the PharoConf, what would you like to be the tutorial about ? :) Ben

Feb. 21, 2013

Re: [Pharo-project] [update 2.0] #20562

by Helene Bilbo

EstebanLM wrote > 20562 > ----- > Issue 5638: Line wrap is breaking lines within words instead of between > words in text views > http://code.google.com/p/pharo/issues/detail?id=5638 Beautiful :) -- View this message in context: http://forum.world.st/update-2-0-20562-tp4671345p4671357.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Feb. 21, 2013

Re: [Pharo-project] TxTextMorph based on new text model

by Denis Kudriashov

Hello 2013/2/15 Sean P. DeNigris <sean(a)clipperadams.com> > I don't know how efficient it would be, but how much text do we really > layout at once? If it makes the code simpler and more beautiful, then it > would be my starting point. Doing otherwise is premature optimization. > I talk about amount of memory which required for text model where each character is separated "big" object. For example, I have small screen laptop and It contains nearly 8000 characters with single 9'pt font which filled full screen. For big monitors I think it will be ~ 32000 characters. For my daily usage I have nearly 20 opened windows with some text (browser pages, articles). And I have nearly 50 saved latest closed windows at history pane. So such text model required significant amount of objects to cover my example. But I don't know is it really bad or not. Actually I agree with your point: > If it makes the code simpler and more beautiful, then it > would be my starting point > And that's why I like what guys implemented. Good experiment. In any case TxText is attempt to get clean object implementation of "text stuff" based on tests. So with little steps we can extend it and add new features. Now TxText can be used instead labels (not editable text morphs). Soon we will have cursor navigation, text selection and editing. I work on cursor now. (I mean visual part of TxText project). Best regards, Denis

Feb. 21, 2013

[Pharo-project] [update 2.0] #20562

by Esteban Lorenzano

20562 ----- Issue 7566: Source code not saved http://code.google.com/p/pharo/issues/detail?id=7566 Issue 6164: Starting the image twice gives CannotDeleteFileException on Windows http://code.google.com/p/pharo/issues/detail?id=6164 Issue 5638: Line wrap is breaking lines within words instead of between words in text views http://code.google.com/p/pharo/issues/detail?id=5638 Diff information: http://ss3.gemstone.com/ss/Pharo20/Traits-EstebanLorenzano.460.diff http://ss3.gemstone.com/ss/Pharo20/Text-EstebanLorenzano.52.diff http://ss3.gemstone.com/ss/Pharo20/Morphic-EstebanLorenzano.1357.diff http://ss3.gemstone.com/ss/Pharo20/Kernel-EstebanLorenzano.1316.diff http://ss3.gemstone.com/ss/Pharo20/Files-EstebanLorenzano.ducasse.294.diff http://ss3.gemstone.com/ss/Pharo20/Compiler-EstebanLorenzano.379.diff

Feb. 21, 2013

Re: [Pharo-project] TxTextMorph based on new text model

by Denis Kudriashov

2013/2/15 Fernando Olivero <fernando.olivero(a)usi.ch> > I recall Safara, in squeaksource. Lukas and a student worked on a nice > text model. Worth checking it out. Thank's for link. I will look at code. Igor and Camillo, do you see this project?

Feb. 21, 2013

Re: [Pharo-project] Problems with SmalltalkHub

by Camillo Bruni

perfect ;) On 2013-02-21, at 18:03, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > ok done for this one : > > http://code.google.com/p/smalltalk-hub/issues/detail?id=13 > > On Thu, Feb 21, 2013 at 5:56 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> can you open an issue on http://code.google.com/p/smalltalk-hub/? >> >> >> On 2013-02-21, at 17:48, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: >> >>> Yes I think so ... >>> >>> Another strange stuff with SmalltalkHub, when you delete a project and >>> recreate a project with the same name, you have access >>> to the history of commits of the previous project. But this one is >>> not a big issue. >>> >>> >>> On Thu, Feb 21, 2013 at 5:40 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>> Yes, it seems something goes wrong inside StHub, we'll have to wait for Nicolas Petton to have a look I guess. >>>> >>>> On 21 Feb 2013, at 17:33, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: >>>> >>>>> In fact, when i try to access to >>>>> http://smalltalkhub.com/mc/UMMISCO/Kendrick/main/Kendrick-SergeStinckwich.1… >>>>> for exemple, I have the following error: >>>>> >>>>> Internal Server Error >>>>> Error: only integers should be used as indices >>>>> >>>>> There is no error with another project : >>>>> http://smalltalkhub.com/mc/Pharo/Opal/main/OpalCompiler-Core-MarcusDenker.1… >>>>> >>>>> So this is a problem with my repo I guess ... >>>>> >>>>> >>>>> >>>>> On Thu, Feb 21, 2013 at 5:05 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>>>> it is a StHub problem, open http://smalltalkhub.com/mc/UMMISCO/Kendrick/main in a browser and try downloading any package, they all failâ¦ >>>>>> >>>>>> On 21 Feb 2013, at 17:03, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>>>> >>>>>>> It fails on 2.0 #561 as well â¦ (not opening the repository, downloading a package). >>>>>>> >>>>>>> On 21 Feb 2013, at 16:10, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: >>>>>>> >>>>>>>> Hi all, >>>>>>>> >>>>>>>> I have some annoying problems with SmalltalkHub. >>>>>>>> >>>>>>>> I have made a project inside a team here: >>>>>>>> http://smalltalkhub.com/#!/~UMMISCO/Kendrick/ >>>>>>>> >>>>>>>> Everytime I try to browse on Pharo 1.4 this repository, I have the >>>>>>>> following errors: >>>>>>>> ZnHttpSuccessful: 500 Internal Server Error >>>>>>>> >>>>>>>> but not for other projects on SmalltalkHub ... >>>>>>>> >>>>>>>> Regards, >>>>>>>> -- >>>>>>>> Serge Stinckwich >>>>>>>> UCBN & UMI UMMISCO 209 (IRD/UPMC) >>>>>>>> Every DSL ends up being Smalltalk >>>>>>>> http://doesnotunderstand.org/ >>>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Serge Stinckwich >>>>> UCBN & UMI UMMISCO 209 (IRD/UPMC) >>>>> Every DSL ends up being Smalltalk >>>>> http://doesnotunderstand.org/ >>>>> >>>> >>>> >>> >>> >>> >>> -- >>> Serge Stinckwich >>> UCBN & UMI UMMISCO 209 (IRD/UPMC) >>> Every DSL ends up being Smalltalk >>> http://doesnotunderstand.org/ >>> >> >> > > > > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://doesnotunderstand.org/ >

Feb. 21, 2013