June 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] DummyUIManager

by StÃ©phane Ducasse

On Jun 21, 2010, at 12:03 PM, Pavel Krivanek wrote: > Hi Mariano, > > it is not so straightforward. You simply cannot switch from Morphic to > DummyUIManager (it requires several next steps and modifications). > This patch is only a small step to better Pharo UI Independency and > PharoKernel. It would be good to identify a roadmap of actions to step by step arrive to this point. Do you have a high level list? > When Pharo will be PharoKernel ready, we may start to > talk about benefits for the deployment. However you may add me as the > book user ;-) > > -- Pavel > > 2010/6/21 Mariano Martinez Peck <marianopeck(a)gmail.com>: >> Hi pavel. This is excellent :) >> >> Now, it would be cool to document how to use it. And even more, the >> scenarios where it can be useful. For example, suppose I deploy a headless >> PharoCore image with seaside, should I replace the UIManager with the Dummy >> ? what do I save? how can I do that? >> >> I think http://book.pharo-project.org/ is excellent for this. If you want >> to write something please let me know and I make you an user. >> >> Thanks again >> >> mariano >> >> On Thu, Jun 17, 2010 at 11:36 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com> >> wrote: >>> >>> Hi, >>> >>> I updated issue http://code.google.com/p/pharo/issues/detail?id=2069 >>> that adds DummyUIManager and makes Pharo more UIManager independent. >>> >>> Please review it, it is an important patch for better modularization. >>> >>> For the method fileInSilentlyAnnouncing: it only changes the category. >>> >>> Cheers, >>> -- Pavel >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 21, 2010

Re: [Pharo-project] [Pharo-users] Pharo book TableLayout tutorial

by laurent laffont

2010/6/21 Mariano Martinez Peck <marianopeck(a)gmail.com> > > > On Thu, Jun 10, 2010 at 10:28 PM, laurent laffont < > laurent.laffont(a)gmail.com> wrote: > >> Hi, >> >> I've added a tutorial on TableLayout >> http://book.pharo-project.org/book/GUI/PolymorphTutorial/TableLayout/which follows the one on Proportional Layout. >> >> Again, thanks for feedback and English check. >> >> > Hi Laurent. I have just watch it, it's great. I love Pharocasts. A little > feedback (not about English): the color of the subtitles. They are blue and > sometimes very similar to the background color. Mostly, to the task bar. > OK, thank you. Laurent. > > Cheers > > Mariano > > Cheers, >> >> Laurent Laffont >> >> http://pharocasts.blogspot.com/ >> http://magaloma.blogspot.com/ >> >> _______________________________________________ >> Pharo-users mailing list >> Pharo-users(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users >> >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 21, 2010

Re: [Pharo-project] Autotest (TDD), request for comments

by laurent laffont

2010/6/21 Mariano Martinez Peck <marianopeck(a)gmail.com> > > > 2010/6/17 laurent laffont <laurent.laffont(a)gmail.com> > >> Hi, >> >> Autotest is a live testing tool (similar too Ruby Autotest, but the >> Smalltalk way, more dynamic). >> >> Autotest automatically runs tests related to the methods you edit. >> Screencast to see it in action: >> http://lolgzs.free.fr/pharo/autotest3.mpeg >> >> > Hi Laurent. I have just test it and I really like it. I wasn't aware at all > what a Autotest was (I don't know Ruby). > Cool ! Personnally I really like Ruby Autotest and I use a similar script for PHP. I can't do TDD without it :) > Autotest uses the following heuritics to find the tests to run: >> - if the method is a test, runs it >> - it the method is a test setUp or tearDown, run all the tests of the >> TestCase >> - else find all senders which are tests in the same package and runs >> them (it detects different packages that are related, for example >> ProfStef-Core and ProfStef-Test) >> >> > maybe a new feature: when modifying a TestResource, run all the tests that > references it ? > Good idea. > what happens with subclasses? suppose I refactor/modify a subclass, do you > also run the tests of the superclasses? > Now there's no heuristics on the class level, only method / package. So as long as there's a sender of the method you edit, tests will run. You can have a look at AutotestFinder, heuristics protocol. > > >> To activate the Autotest dashboard >> >> > - open the settings browser >> - go under System >> - check "Show Autotest Dashboard" option >> >> > Here I am confused. This setting, just enables de dashborad or the run of > the tests? I guess one thing is to run the tests and another one is to see > them in the dashborad. > > I would love to be able to enable/disable AutoTest completly. > Closing the dashboard disables Autotest completly. AutotestDashboard sets up as a view of its Autotest instance. When you close it garbageCollect to be sure Autotest>>release is called. > In addition, I think we can add AutoTest to PharoDev 1.2 images. What you > and others think? > I would like more feedback. If you use it you notice that your workflow changes because of that instant feedback. I'm looking for people who use it on real TDD for real projects (as I'm only pharoing on my freetime). I think it can be a great tool we cannot have in Â«standardÂ» programming languages. Cheers, Laurent > > >> To load it: >> >> Gofer new >> squeaksource: 'Autotest'; >> package: 'Autotest'; >> load >> >> HelpSystem book included. >> >> >> I would like to know what needs enhancements, what to add (and to remove >> :) and whether you would use it or not (and why). >> >> Thanks for feedback. >> >> Cheers, >> >> Laurent Laffont >> >> http://pharocasts.blogspot.com/ >> http://magaloma.blogspot.com/ >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 21, 2010

Re: [Pharo-project] [Pharo-users] Pharo book TableLayout tutorial

by Mariano Martinez Peck

On Thu, Jun 10, 2010 at 10:28 PM, laurent laffont <laurent.laffont(a)gmail.com > wrote: > Hi, > > I've added a tutorial on TableLayout > http://book.pharo-project.org/book/GUI/PolymorphTutorial/TableLayout/which follows the one on Proportional Layout. > > Again, thanks for feedback and English check. > > Hi Laurent. I have just watch it, it's great. I love Pharocasts. A little feedback (not about English): the color of the subtitles. They are blue and sometimes very similar to the background color. Mostly, to the task bar. Cheers Mariano Cheers, > > Laurent Laffont > > http://pharocasts.blogspot.com/ > http://magaloma.blogspot.com/ > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > >

June 21, 2010

Re: [Pharo-project] Issue 2560 : Convenient methods from Grease for Strings

by StÃ©phane Ducasse

but do we want all grease? Stef On Jun 17, 2010, at 6:42 PM, Michael Roberts wrote: > I'm missing something. Why do we need to adopt the (copy of) methods and not just adopt the package as lukas said? I thought we wanted core to get smaller over time and better modularised anyway? We would just need to track a stable version rather than maintaining our own branch. Surely it is worse to copy the methods renamed or not but put them in a pharo specific package? > > > Cheers mike > > On 17 Jun 2010, at 14:14, Julian Fitzell <jfitzell(a)gmail.com> wrote: > >> 2010/6/17 Marcus Denker <marcus.denker(a)inria.fr>: >>> >>> On Jun 17, 2010, at 12:27 PM, Lukas Renggli wrote: >>> >>> - If included with Pharo I suggest to rename all the methods, >>> otherwise we will run into big troubles with Seaside and other >>> projects that depend on Grease. >>> >>> >>> From a philosophical standpoint, I *hate* that. this means that as a >>> plattform, we can not >>> grow and improve our libraris anymore? >>> Shouldn't be the goal that useful extensions gets adopted by the core? >> >> We will need to find a way to allow platforms to adopt Grease methods >> - I do think this is the end goal. It's a bit of a nightmare from our >> point of view because we end up having to have different Grease >> versions for different versions of the platforms, but isn't that sort >> of unavoidable in the long run anyway? Part of the reason that's so >> awful is simply due to the lack of good branching and management tools >> in our version control systems... >> >> Julian >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 21, 2010

Re: [Pharo-project] Issue 2290: window placement strategy

by Mariano Martinez Peck

Hi Jannik. I have just test them and I really like them. Regardless the particular strategy, using a strategy, and thus being able to easily swich and extend, is just great. Now, a couple of observations: - It is not completely clear for me what it is each option. What is standard? if tomorrow the standard change? I would try to avoid such names and put something better. Random ? I don't know. What is reverse stragger ?? - I think it should be also documented if possible in the settings browser, what does each option mean. - I think that for 1.2 we are quite free to change and do what we want. So, we can change the default. I think cascade is the better. What I really think is that we need something deterministic. Fixed. Not random. Not surprise. Maybe not all of you agree. I would like to hear other opinions. Cheers Mariano On Sat, Jun 12, 2010 at 9:51 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Thanks jannik I will have a look > > On Jun 12, 2010, at 9:27 PM, Laval Jannik wrote: > > > Hi all, > > > > I made a setting for placement strategy. > > By default, it is reversed stragger (which is the one by default since > Pharo exists). > > And I create one I have named "Cascade", which place the new window above > the current active window, or if there is no active window, the window is > placed at the cursor position. > > > > The change is available in SLICE-Issue-2290-windowsStrategy. > > The setting is available in the SettingBrowser in > Appearance>Morphic>Windows>Window position strategy. > > > > Now, it is possible to create new strategy positions by creating a new > strategy in RealEstateAgent (category strategy - there is also three > strategies), and by modifying the method RealEstateAgent > >>usedStrategySettingsOn: to add an entry in the menu. > > > > I hope that this change will be integrated in 1.2. > > > > Cheers, > > --- > > Jannik Laval > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 21, 2010

Re: [Pharo-project] Autotest (TDD), request for comments

by Mariano Martinez Peck

2010/6/17 laurent laffont <laurent.laffont(a)gmail.com> > Hi, > > Autotest is a live testing tool (similar too Ruby Autotest, but the > Smalltalk way, more dynamic). > > Autotest automatically runs tests related to the methods you edit. > Screencast to see it in action: http://lolgzs.free.fr/pharo/autotest3.mpeg > > Hi Laurent. I have just test it and I really like it. I wasn't aware at all what a Autotest was (I don't know Ruby). > Autotest uses the following heuritics to find the tests to run: > - if the method is a test, runs it > - it the method is a test setUp or tearDown, run all the tests of the > TestCase > - else find all senders which are tests in the same package and runs them > (it detects different packages that are related, for example ProfStef-Core > and ProfStef-Test) > > maybe a new feature: when modifying a TestResource, run all the tests that references it ? what happens with subclasses? suppose I refactor/modify a subclass, do you also run the tests of the superclasses? > To activate the Autotest dashboard > > - open the settings browser > - go under System > - check "Show Autotest Dashboard" option > > Here I am confused. This setting, just enables de dashborad or the run of the tests? I guess one thing is to run the tests and another one is to see them in the dashborad. I would love to be able to enable/disable AutoTest completly. In addition, I think we can add AutoTest to PharoDev 1.2 images. What you and others think? > To load it: > > Gofer new > squeaksource: 'Autotest'; > package: 'Autotest'; > load > > HelpSystem book included. > > > I would like to know what needs enhancements, what to add (and to remove :) > and whether you would use it or not (and why). > > Thanks for feedback. > > Cheers, > > Laurent Laffont > > http://pharocasts.blogspot.com/ > http://magaloma.blogspot.com/ > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 21, 2010

Re: [Pharo-project] [squeak-dev] Teleplace Cog VMs are now available

by Levente Uzonyi

On Sun, 20 Jun 2010, Eliot Miranda wrote: > Hi All, > > > it gives me great pleasure to announce that the Teleplace Cog VMs are now > available. Huge thanks to all at Teleplace who have given me the This is fantastic, thanks. <snip> > attempt to port it, e.g. to ARM, PowerPC and x86-64. The Cogit (excuse the > pun) is so named because it is both an interpreter and a JIT, choosing not > to generate machine code for large methods, interpreting them instead, the > default policy being not to JIT methods with more than 60 literals. I think it would be better to use an adaptive policy later. Something like: all methods will be inlined if they are evaluated enough times. Say a method with 10 literals will be inlined if it's evaluated 100 times. A method with 100 literals will need 10000 runs, etc. (note: i just made up the numbers). Levente

June 21, 2010

Re: [Pharo-project] [Pharo-users] Writing extensions

by Mariano Martinez Peck

On Mon, Jun 21, 2010 at 1:52 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > > > On Mon, Jun 21, 2010 at 12:32 PM, Bob Cowdery <bob(a)bobcowdery.plus.com>wrote: > >> Hi Mariano >> >> Thanks for the links. I managed to dig out my old code and found some of >> the links, enough for me to write the slang and convert to C. Now I need >> some header files for the build and presumable a library to link >> > > which headers? I am a vm newbie, so I cc'ed squeak-vm mailing list. They > may help you much more than me. > > Cheers > > Mariano > > >> against. I would appreciate a pointer to those as it's not obvious from >> the links where to get those from. >> >> Regards >> Bob >> >> Mariano Martinez Peck wrote: >> > Hi Bob and welcome. There are two possibiities I know to >> > write/communicate to C: >> > >> > - The FFI plugin is intended to call external libraries from Smalltalk >> > http://wiki.squeak.org/squeak/1414 >> > http://forum.world.st/FFI-Documentation-td2225148.html#a2225148 >> > >> > - Write your own VM primitives >> > http://wiki.squeak.org/squeak/356 >> > http://wiki.squeak.org/squeak/3336 >> > http://wiki.squeak.org/squeak/6102 >> > >> > Probably there are much more links, but maybe this is enough to >> > remember you what you used. >> > >> > Let us know >> > >> > Mariano >> > >> > On Mon, Jun 14, 2010 at 9:02 PM, Bob Cowdery <bob(a)bobcowdery.plus.com >> > <mailto:bob@bobcowdery.plus.com>> wrote: >> > >> > Hi all, >> > >> > I played with Squeak about 4 years ago and I built some extensions >> > in C. >> > I would like to do the same again with Pharo and I have a big lump >> > of C >> > I would like to interface to. I can't actually remember what I did >> > before and can't seem to find the tutorial I used. Could somebody >> > point >> > me in the right direction please. >> > >> > Thanks >> > Bob >> > >> > _______________________________________________ >> > Pharo-users mailing list >> > Pharo-users(a)lists.gforge.inria.fr >> > <mailto:Pharo-users@lists.gforge.inria.fr> >> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users >> > >> > >> > ------------------------------------------------------------------------ >> > >> > _______________________________________________ >> > Pharo-users mailing list >> > Pharo-users(a)lists.gforge.inria.fr >> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users >> > >> >> >> _______________________________________________ >> Pharo-users mailing list >> Pharo-users(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users >> > >

June 21, 2010

Re: [Pharo-project] [Pharo-users] Writing extensions

by Mariano Martinez Peck

On Mon, Jun 21, 2010 at 12:32 PM, Bob Cowdery <bob(a)bobcowdery.plus.com>wrote: > Hi Mariano > > Thanks for the links. I managed to dig out my old code and found some of > the links, enough for me to write the slang and convert to C. Now I need > some header files for the build and presumable a library to link > which headers? I am a vm newbie, so I cc'ed squeak-vm mailing list. They may help you much more than me. Cheers Mariano > against. I would appreciate a pointer to those as it's not obvious from > the links where to get those from. > > Regards > Bob > > Mariano Martinez Peck wrote: > > Hi Bob and welcome. There are two possibiities I know to > > write/communicate to C: > > > > - The FFI plugin is intended to call external libraries from Smalltalk > > http://wiki.squeak.org/squeak/1414 > > http://forum.world.st/FFI-Documentation-td2225148.html#a2225148 > > > > - Write your own VM primitives > > http://wiki.squeak.org/squeak/356 > > http://wiki.squeak.org/squeak/3336 > > http://wiki.squeak.org/squeak/6102 > > > > Probably there are much more links, but maybe this is enough to > > remember you what you used. > > > > Let us know > > > > Mariano > > > > On Mon, Jun 14, 2010 at 9:02 PM, Bob Cowdery <bob(a)bobcowdery.plus.com > > <mailto:bob@bobcowdery.plus.com>> wrote: > > > > Hi all, > > > > I played with Squeak about 4 years ago and I built some extensions > > in C. > > I would like to do the same again with Pharo and I have a big lump > > of C > > I would like to interface to. I can't actually remember what I did > > before and can't seem to find the tutorial I used. Could somebody > > point > > me in the right direction please. > > > > Thanks > > Bob > > > > _______________________________________________ > > Pharo-users mailing list > > Pharo-users(a)lists.gforge.inria.fr > > <mailto:Pharo-users@lists.gforge.inria.fr> > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > > > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Pharo-users mailing list > > Pharo-users(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > > > > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users >

June 21, 2010