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

Re: [Pharo-dev] The funny side of Pharo : Message Definitely Not Understood

by kilon alios

what if updater becomes a separate application that operates on an image without loading it. So in an update Pharo would save the image, close itself, open the updater application which will perform the update and the updater reopen Pharo loading the same image ? On Wed, May 21, 2014 at 3:59 PM, Guillermo Polito <guillermopolito(a)gmail.com > wrote: > But not also... Because right now the way changes are integrated is using > the same update mechanism if I'm not mistaken. > > The very challenge of the update is that you are updating your image, > which has your objects, and your changes! > > So, what if you made some changes in the core classes? update may fail on > merge or even remove your changes. If you keep your method you may lose a > bugfix > If there was a rename of that method you changed? what should the update > do? > If you configured some shortcuts? the update may reset them > The changesets? they may be reset > And the list goes on... > > > On Wed, May 21, 2014 at 2:49 PM, Esteban A. Maringolo < > emaringolo(a)gmail.com> wrote: > >> 2014-05-21 7:11 GMT-03:00 stepharo <stepharo(a)free.fr>: >> > So we should probably remove the software update button. >> >> +1 >> >> >> > Stef >> > PS: the last time I updated my iPhone it blocked and I had to fully >> > reinstall everything. >> > And once when I updated my mac my mouse got blocked forever on the left >> top >> > corner. >> >> You might be one of the lots of unlucky persons that got issues while >> updating iOS/MacOS, but sill you probably represent less than the 1% >> of the total userbase (of which the rest updated with no issues). >> >> The hard thing here is Pharo tries to update itself while running, it >> is like trying to modify a plane while flying. >> >> >> >> Esteban A. Maringolo >> >> >

May 21, 2014

Re: [Pharo-dev] The funny side of Pharo : Message Definitely Not Understood

by Guillermo Polito

But not also... Because right now the way changes are integrated is using the same update mechanism if I'm not mistaken. The very challenge of the update is that you are updating your image, which has your objects, and your changes! So, what if you made some changes in the core classes? update may fail on merge or even remove your changes. If you keep your method you may lose a bugfix If there was a rename of that method you changed? what should the update do? If you configured some shortcuts? the update may reset them The changesets? they may be reset And the list goes on... On Wed, May 21, 2014 at 2:49 PM, Esteban A. Maringolo <emaringolo(a)gmail.com>wrote: > 2014-05-21 7:11 GMT-03:00 stepharo <stepharo(a)free.fr>: > > So we should probably remove the software update button. > > +1 > > > > Stef > > PS: the last time I updated my iPhone it blocked and I had to fully > > reinstall everything. > > And once when I updated my mac my mouse got blocked forever on the left > top > > corner. > > You might be one of the lots of unlucky persons that got issues while > updating iOS/MacOS, but sill you probably represent less than the 1% > of the total userbase (of which the rest updated with no issues). > > The hard thing here is Pharo tries to update itself while running, it > is like trying to modify a plane while flying. > > > > Esteban A. Maringolo > >

May 21, 2014

Re: [Pharo-dev] Call for co-coders

by Norbert Hartl

Am 21.05.2014 um 09:05 schrieb stepharo <stepharo(a)free.fr>: > >>>> >>>> As a general matter, I would be interested in: >>>> - unifying with the ZnLogEvent >>> > SystemLogger is infrastructure low level. So I do not see why Zn and SystemLogger should be unified. > yep >> If this means talking to Sven this is a definite yes. I donât think we need to unify with the current ZnLogEvent. Syncing with zinc is probably not the way to go anyway. Zinc is still an external framework (hence the namespace prefix). I did a zinc bridge which operates an a single event bridging from zinc to SystemLogger. This is not clever performance wise. A better approach is to plug into zincs LogSupport. We should hook into there so we just get the invocations from zinc and we can emit the proper SystemLogger events into the Log framework. >> Sven will come up with something announcement based. And that is still a task for us, too. To look where functionality of SystemLogger is doubled with announcements. > > We should pay attention that it stays small and simple. > It is and will be an extra anyway. You load zinc, you load SystemLogger, you load the glue code between them. Nothing to bloat the core. > >>> first we should integrate it and make sure that all the Transcript show are funnelled to the Log frameworks. >> >> Yes. Maybe we need to sync our understanding of log levels first. The exchange adds a log level and adding a tag would be good, too. > > I do not get it but this is not a problem. No need to reply. The Log as it is at the moment contains log level and a tag. Going from a simple logCr: you have to add a log level. Not everything will be debug/trace. With the tag I meant the tag of the Log class. This is a first-class citizen for categorizing and should be something like âimageâ or even better the name of the sub-system that emitted the message. Clear now? Norbert > >>>> - Split the Log class >>> >>> we will not split it because we iterated over the design since 8 months with norbert :) >> >> I cannot find the proposals of Doru. But Iâm interested. I splitted the Log class already into BasicLog and Log. Iâm not fully satisfied with it so â¦ My concern about the Log class is more how get it right supporting different kind of Log classes and still have a working filtering in the Logger. But that we can discuss in the groups that form I guess > I would like to stop iterating. And again we should keep the system small. > I studied all the logger framework available and I think that we can look for the graal forever or get done and I want to get done > because there are other many many topics that can get fixed. > Right now we went from 0% to 80% and this is a good ratio. We iterated with you. Now I do not want to pass time to go to an hypothetical 85%. > > >>>> - Possibly support Fuel serialization for each log entry >>> Please go ahead. >> >> Yes. I donât even understand what it means :) > Send code! > >

May 21, 2014

Re: [Pharo-dev] Understanding Workspace

by Tudor Girba

Indeed, I just noticed that we are also loading the Rubric package directly in Glamour. This is not good :) Doru On Wed, May 21, 2014 at 2:25 PM, kilon alios <kilon.alios(a)gmail.com> wrote: > I tried ConfigurationOfRubic load, loadDefault and loadDevelopment , they > all fail with an error so I am loading each package manually now. > > > On Wed, May 21, 2014 at 3:17 PM, kilon alios <kilon.alios(a)gmail.com>wrote: > >> Thank you Tudor, thats looks definitely very useful . >> >> I am downloading it now and studying it :) >> >> >> On Wed, May 21, 2014 at 3:10 PM, Tudor Girba <tudor(a)tudorgirba.com>wrote: >> >>> The first suggestion is to not invest in the PluggableTextMorph :) >>> >>> Ideally, we should get the new text widget soon, but in the meantime, >>> you would be better with using Rubric. It is a pragmatic solution developed >>> by Alain Plantec and that works now. This is where we are going with the >>> Glamorous Toolkit at the moment. You find it already in the Moose image, or >>> you can download it from here: >>> http://smalltalkhub.com/#!/~AlainPlantec/Rubric >>> >>> Cheers, >>> Doru >>> >>> >>> On Wed, May 21, 2014 at 12:44 PM, kilon alios <kilon.alios(a)gmail.com>wrote: >>> >>>> Hello guys, I have started a new experiment of mine, a tool I call >>>> "Talos". I want Talos to become workspace on steroids. >>>> >>>> The first thing I want to implement is emacs like navigation. With that >>>> I mean keyboard shortcuts for moving inside the text like you can do with >>>> arrow keys already and the ability to move to the next word , the first >>>> character of next word, the last character of next word , previous world, >>>> quickly rename variables and all the great things one can do with emacs and >>>> vim. >>>> >>>> Of course I don't want to do all that at once, one step at a time. >>>> >>>> Now I have take a look at Workspace and it seems that it uses >>>> PlaggableTextMorph , it also looks like I can get the contents via >>>> PluggableTextMorph>>text instance side. The source code returned is also >>>> send to RBParser using the parseBlock method , I think for syntax >>>> highlighting. >>>> >>>> However because the PluggableTextMorph is very big and it does not even >>>> have a class comment, though quite a lot of methods are commented, I am >>>> really open to advice and suggestions on to how to parse the contents and >>>> manipulate the cursor position. >>>> >>>> I know I could use PettitParser but I dont know if there are better >>>> options out there, or maybe I am doing the whole thing wrong. >>>> >>>> So any advice and suggestion is more than welcomed. >>>> >>> >>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Every thing has its own flow" >>> >> >> > -- www.tudorgirba.com "Every thing has its own flow"

May 21, 2014

Re: [Pharo-dev] The funny side of Pharo : Message Definitely Not Understood

by Esteban A. Maringolo

2014-05-21 7:11 GMT-03:00 stepharo <stepharo(a)free.fr>: > So we should probably remove the software update button. +1 > Stef > PS: the last time I updated my iPhone it blocked and I had to fully > reinstall everything. > And once when I updated my mac my mouse got blocked forever on the left top > corner. You might be one of the lots of unlucky persons that got issues while updating iOS/MacOS, but sill you probably represent less than the 1% of the total userbase (of which the rest updated with no issues). The hard thing here is Pharo tries to update itself while running, it is like trying to modify a plane while flying. Esteban A. Maringolo

May 21, 2014

Fixing configurations: XML-Parser

by Stephan Eggermont

XML-Parser did have breaking tests in Pharo 2, due to the use of selectorsInCategory:. This method is defined on TClassDescription. We added a package XML-Pharo2-Parser containing a copy in an extension method on TClassAndTraitDescription. It might be useful to add to Pharo 2. Diego & Stephan

May 21, 2014

Re: [Pharo-dev] Call for co-coders

by Norbert Hartl

Am 21.05.2014 um 14:24 schrieb Tudor Girba <tudor(a)tudorgirba.com>: > As it is now, when I execute: > Log critical: 'message' > > I get an instance of Log. This is confusing, and not needed. We can nicely get an instance of LogEvent. This will not complicate things at all. > Please take Object>>#asLog into account when doing it. Norbert

May 21, 2014

[REMINDER] CFP - IWST 2014 - Deadline June, 15

by jannik laval

[Please accept our apologies if you receive multiple copies of this call] [Please send to interested colleagues / mailing-lists] ************************************************************************************************************ CALL FOR PAPERS IWST14 â International Workshop on Smalltalk Technologies Cambridge, England; August 19, 2014 http://www.esug.org/Conferences/2014/IWST14 ************************************************************************************************************ ------------------- Goals and scopes ------------------- The goals of the workshop is to create a forum around advances or experience in Smalltalk and to trigger discussions and exchanges of ideas. The topics of your paper can be on all aspect of Smalltalk, theoretical as well as practical. Participants are invited to submit research articles or industrial papers. This year we want to open two different tracks: one research track and one industrial track with less scientific constraints. We expect papers of three kinds: Short position papers describing emerging ideas Long research papers with deeper description of experiments and of research results. Industrial papers with presentation of real and innovative Smalltalk applications; this kind of paper should enlighten why Smalltalk is really appropriate for your application. We will not enforce any length restriction. -------------------- Important Dates -------------------- Submission deadline: June 15, 2014 Notification deadline: July 15, 2014 Workshop : August 19, 2014 All accepted papers will be published in ACM DL (To be confirmed) ------------------- Topics ------------------- We welcome contributions on all aspects, theoretical as well as practical, of Smalltalk related topics such as: Aspect-oriented programming, Design patterns, Experience reports, Frameworks, Implementation, new dialects or languages implemented in Smalltalk, Interaction with other languages, Meta-programming and Meta-modeling, Tools ------------------- Best Paper Award ------------------- To encourage the submission of high-quality papers, the IWST organizing committee is very proud to announce a Best Paper Award for this edition of IWST. We thank Lam Research Corporation for its financial contribution that makes it possible a price for the three best papers: 1000 USD for first place, 600 USD for second place and 400 USD for third place. The ranking will be decided by the program committee during the review process. The awards will be given during the ESUG conference social event. The Best Paper Award will take place only with a minimum of six submissions. Notice also that to be illegible, a paper must be presented at the workshop by one of the author and that the presenting author must be registered at the ESUG conference. ------------------- Publication ------------------- Both submissions and final papers must be prepared using the ACM SIGPLAN 10 point format. Templates for Word and LaTeX are available at http://www.acm.org/sigs/sigplan/authorInformation.htm. This site also contains links to useful informations on how to write effective submissions. ------------------- Submission ------------------- All submissions must be sent via easychair: https://www.easychair.org/conferences/?conf=iwst2014 ------------------- Program chairs ------------------- Alain Plantec (UMR 6265 Lab-STICC, University of Brest, France) Jannik Laval (Ecole des Mines de Douai, France) -- ~~Jannik Laval~~ Ãcole des Mines de Douai Enseignant-chercheur http://www.jannik-laval.eu http://www.phratch.com http://car.mines-douai.fr/

May 21, 2014

[REMINDER] CFP - IWST 2014 - Deadline June, 15

by jannik laval

[Please accept our apologies if you receive multiple copies of this call] [Please send to interested colleagues / mailing-lists] ************************************************************************************************************ CALL FOR PAPERS IWST14 â International Workshop on Smalltalk Technologies Cambridge, England; August 19, 2014 http://www.esug.org/Conferences/2014/IWST14 ************************************************************************************************************ ------------------- Goals and scopes ------------------- The goals of the workshop is to create a forum around advances or experience in Smalltalk and to trigger discussions and exchanges of ideas. The topics of your paper can be on all aspect of Smalltalk, theoretical as well as practical. Participants are invited to submit research articles or industrial papers. This year we want to open two different tracks: one research track and one industrial track with less scientific constraints. We expect papers of three kinds: Short position papers describing emerging ideas Long research papers with deeper description of experiments and of research results. Industrial papers with presentation of real and innovative Smalltalk applications; this kind of paper should enlighten why Smalltalk is really appropriate for your application. We will not enforce any length restriction. -------------------- Important Dates -------------------- Submission deadline: June 15, 2014 Notification deadline: July 15, 2014 Workshop : August 19, 2014 All accepted papers will be published in ACM DL (To be confirmed) ------------------- Topics ------------------- We welcome contributions on all aspects, theoretical as well as practical, of Smalltalk related topics such as: Aspect-oriented programming, Design patterns, Experience reports, Frameworks, Implementation, new dialects or languages implemented in Smalltalk, Interaction with other languages, Meta-programming and Meta-modeling, Tools ------------------- Best Paper Award ------------------- To encourage the submission of high-quality papers, the IWST organizing committee is very proud to announce a Best Paper Award for this edition of IWST. We thank Lam Research Corporation for its financial contribution that makes it possible a price for the three best papers: 1000 USD for first place, 600 USD for second place and 400 USD for third place. The ranking will be decided by the program committee during the review process. The awards will be given during the ESUG conference social event. The Best Paper Award will take place only with a minimum of six submissions. Notice also that to be illegible, a paper must be presented at the workshop by one of the author and that the presenting author must be registered at the ESUG conference. ------------------- Publication ------------------- Both submissions and final papers must be prepared using the ACM SIGPLAN 10 point format. Templates for Word and LaTeX are available at http://www.acm.org/sigs/sigplan/authorInformation.htm. This site also contains links to useful informations on how to write effective submissions. ------------------- Submission ------------------- All submissions must be sent via easychair: https://www.easychair.org/conferences/?conf=iwst2014 ------------------- Program chairs ------------------- Alain Plantec (UMR 6265 Lab-STICC, University of Brest, France) Jannik Laval (Ecole des Mines de Douai, France) -- ~~Jannik Laval~~ Ãcole des Mines de Douai Enseignant-chercheur http://www.jannik-laval.eu http://www.phratch.com http://car.mines-douai.fr/

May 21, 2014

Re: [Pharo-dev] Understanding Workspace

by kilon alios

I tried ConfigurationOfRubic load, loadDefault and loadDevelopment , they all fail with an error so I am loading each package manually now. On Wed, May 21, 2014 at 3:17 PM, kilon alios <kilon.alios(a)gmail.com> wrote: > Thank you Tudor, thats looks definitely very useful . > > I am downloading it now and studying it :) > > > On Wed, May 21, 2014 at 3:10 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> The first suggestion is to not invest in the PluggableTextMorph :) >> >> Ideally, we should get the new text widget soon, but in the meantime, you >> would be better with using Rubric. It is a pragmatic solution developed by >> Alain Plantec and that works now. This is where we are going with the >> Glamorous Toolkit at the moment. You find it already in the Moose image, or >> you can download it from here: >> http://smalltalkhub.com/#!/~AlainPlantec/Rubric >> >> Cheers, >> Doru >> >> >> On Wed, May 21, 2014 at 12:44 PM, kilon alios <kilon.alios(a)gmail.com>wrote: >> >>> Hello guys, I have started a new experiment of mine, a tool I call >>> "Talos". I want Talos to become workspace on steroids. >>> >>> The first thing I want to implement is emacs like navigation. With that >>> I mean keyboard shortcuts for moving inside the text like you can do with >>> arrow keys already and the ability to move to the next word , the first >>> character of next word, the last character of next word , previous world, >>> quickly rename variables and all the great things one can do with emacs and >>> vim. >>> >>> Of course I don't want to do all that at once, one step at a time. >>> >>> Now I have take a look at Workspace and it seems that it uses >>> PlaggableTextMorph , it also looks like I can get the contents via >>> PluggableTextMorph>>text instance side. The source code returned is also >>> send to RBParser using the parseBlock method , I think for syntax >>> highlighting. >>> >>> However because the PluggableTextMorph is very big and it does not even >>> have a class comment, though quite a lot of methods are commented, I am >>> really open to advice and suggestions on to how to parse the contents and >>> manipulate the cursor position. >>> >>> I know I could use PettitParser but I dont know if there are better >>> options out there, or maybe I am doing the whole thing wrong. >>> >>> So any advice and suggestion is more than welcomed. >>> >> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> > >

May 21, 2014