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

Re: [Pharo-project] How get font instance programmatically?

by Schwab,Wilhelm K

Below are some fonts that I set as part of my image build process; the comment above them is "Shamelessly stolen from Lukas." They might need to be changed to take advantage of bitmap fonts?? tinyFont := LogicalFont familyName:'DejaVu Sans' fallbackFamilyNames:nil pointSize:8 stretchValue:0 weightValue:400 slantValue:0. codeFont := LogicalFont familyName:'DejaVu Sans Mono' fallbackFamilyNames:nil pointSize:9 stretchValue:0 weightValue:400 slantValue:0. baseFont := LogicalFont familyName:'DejaVu Sans' fallbackFamilyNames:nil pointSize:10 stretchValue:0 weightValue:400 slantValue:0. boldFont := LogicalFont familyName:'DejaVu Sans' fallbackFamilyNames:nil pointSize:11 stretchValue:0 weightValue:600 slantValue:0. You might try http://code.google.com/p/pharo/wiki/ImageBuildScripts ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Denis Kudriashov [dionisiydk(a)gmail.com] Sent: Thursday, June 03, 2010 11:49 AM To: Pharo-project Subject: [Pharo-project] How get font instance programmatically? Hello, My task very simple. I need set some font for TextMorph instance programmatically. I found TextStyle>>named: familyName . But it search font in TextConstants that not include my font. By my font exists in visual font chooser from halo menu in text morph. How I can get font instance that I see in FontChooser (that appears by halo menu)? P.S. I try set for my text morph default Pharo 1.0 DejavuSans font

June 3, 2010

Re: [Pharo-project] Something I don't see in ImageSegment

by Eliot Miranda

Hi Mariano, Hi All, response below. But does anyone have any tests for the image segment primitives? I'm refactoring them and would like some tests. 2010/6/3 Mariano Martinez Peck <marianopeck(a)gmail.com> > Hi. ImageSegment uses GC to compute the out pointers. Basically, to a given > array of roots (a graph) it does: > > 1) It marks the rootArray and all root objects by turning on the Garbage > Collector bit in the object header of those particular objects. > 2) Then does a mark pass over all objects. This will stop at our marked > roots leaving our segment unmarked in their shadow. > 3) Finally, it unmarks the rootArray and all root objects. > 4) Only external objects are now marked. > > The unmarked objects in the graph of objects of the arrays are those who > will be put in the WordArray (the segment) and those who are marked to the > outPointers. > > However, I don't see where step 2) is done in Interpreter >> > primitiveStoreImageSegment > > In a piece of such method it does: > > > "Then do a mark pass over all objects. This will stop at our marked roots, > thus leaving our segment unmarked in their shadow." > savedYoungStart := youngStart. > youngStart := self startOfMemory. "process all of memory" > "clear the recycled context lists" > freeContexts := NilContext. > freeLargeContexts := NilContext. > self markAndTraceInterpreterOops. "and special objects array" > youngStart := savedYoungStart. > > "Finally unmark the rootArray and all root objects." > self longAt: arrayOfRoots put: ((self longAt: arrayOfRoots) bitAnd: > AllButMarkBit). > ......continue....... > > But here I see it is only marking Interpreter oops, not all objects. And I > don't see where all objects are marked even in the code that follows this > little piece. > markInterpreterOops marks all objects accessible from the interpreter oops, including the specialObjectsArray, recursively marking any unmarked objects and their referents. i.e. it marks all objects reachable from the roots of the system. This would mark all objects in the system were it not for the fact that the primitive marks the rootArray and so markInterpreterOops does not marl objects /only/ reachable from the rootArray. So once the rootArray objects have been unmarked, only those objects that should go in the image segment are unmarked. So the primitive works by - marking the objects in rootArray, preventing marking of objects reachable from them in the next step - recursively marking all objects reachable from the roots (except those already marked) - unmarking root objects, leaving the transitive closure of objects accessible from the roots and no where else unmarked - writing the unmarked objects to an image segment HTH Eliot > You can see the comment: "Then do a mark pass over all objects" and even > without the comment it makes sense to mark all objects in order to detect > outPointers. > > Does anyone has a hint? > > Thanks > > Mariano > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 3, 2010

Re: [Pharo-project] About TDD and Pharo

by Guillermo Polito

Where should I look? :D Is something written somewhere? :P On Thu, Jun 3, 2010 at 1:22 PM, StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr>wrote: > > On Jun 2, 2010, at 10:42 PM, Guillermo Polito wrote: > > > Today's debugger (and all pharo indeed), is extremely dependant on the > mouse... I would love to do all the same with just the keyboard :( > > me too. > Now if you want to help in this direction we should check the packages for > keybindings and see what they are doing and how > we could integrate them. > The way this is done in the paragraph editor is not good. I spent hours on > it for the botsinc book long time ago. > > Stef > > > > > On Wed, Jun 2, 2010 at 4:30 PM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > > Hi all > > > > Imagine that we would like to sell pharo (+ seaside) as THE agile > platform for doing TDD. > > What would be the changes that we could do support it. > > I know that hernan did a package for that but not I would like to have a > new list of items > > to support it. > > > > Stef > > _______________________________________________ > > 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 3, 2010

Re: [Pharo-project] About TDD and Pharo

by StÃ©phane Ducasse

On Jun 2, 2010, at 10:42 PM, Guillermo Polito wrote: > Today's debugger (and all pharo indeed), is extremely dependant on the mouse... I would love to do all the same with just the keyboard :( me too. Now if you want to help in this direction we should check the packages for keybindings and see what they are doing and how we could integrate them. The way this is done in the paragraph editor is not good. I spent hours on it for the botsinc book long time ago. Stef > > On Wed, Jun 2, 2010 at 4:30 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi all > > Imagine that we would like to sell pharo (+ seaside) as THE agile platform for doing TDD. > What would be the changes that we could do support it. > I know that hernan did a package for that but not I would like to have a new list of items > to support it. > > Stef > _______________________________________________ > 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 3, 2010

Re: [Pharo-project] About TDD and Pharo

by Alexandre Bergel

The idea is excellent. Cheers, Alexandre On 3 Jun 2010, at 10:22, laurent laffont wrote: > > > On Thu, Jun 3, 2010 at 3:42 PM, Alexandre Bergel <alexandre(a)bergel.eu> wrote: > > You may have a lot of noise. > > > > I guess that Ruby uses files as a unit of development/deployment. The closest Smalltalk/Pharo has is the class and the package. > > > > I would suggest that TestCase which would use this feature use some pragma/method to identify/declare which classes/packages this test depends upon. Then the "autotest" framework would register such tests and listen for changes in the given classes/packages, launching required tests whenever a change happen. > > > > Additionally, one could declare such a pragma on a single test method, when this test should be run for a specific class. > > > > Of course, you also to take care of long running tests, which you probably want to exclude from auto-testing. > > I see autotest in Pharo in a slighly different way: When I press save in the Monticello browser, I have a popup menu which asks me whether (i) I want to run all the tests or (ii) only the tests that cover that I changed from the last version. > > Does this make sense? > > Please no popup :) What I like in ruby autotest is that I can quickly look at test results if I want (or not) without stop writing. Often you want to see your tests failing, as you type / save code. I don't have to stop writing, click a button, wait test results, go again.... testing is done in background and I just see notifications whether it's OK or not. > > So test log in a Transcript is OK for me. > > > For autotest unit of work is file: it runs the test file which has the same name as the code file, but you can customize this behavior. For autotest-rails: > "A simplified version of Autotest heuristics in this mode would be: > When changing a test file, only this file is run (e.g. test/unit/foo_test.rb âtest/unit/foo_test.rb). > When changing a model file, only associated unit test file is run (e.g.app/models/foo.rb â test/unit/foo_test.rb). > When changing a controller file, associated functional test file is run (e.g.app/controllers/foo_controller.rb âtest/functional/foo_controller_test.rb). > When changing a fixture file, associated unit test and functional test are run (e.g.app/fixtures/foos.yml â test/unit/foo_test.rb +test/functional/foo_controller_test.rb). > When changing a helper file, associated functional test file is run (e.g.app/helpers/foo_helper.rb âtest/functional/foo_controller_test.rb). > When changing application_helper.rb file all functional test files are run (e.g.application_helper.rb â test/functional/*_test.rb). > When changing a file under the config directory, all tests are run." > > Laurent > > > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > 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 -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

June 3, 2010

[Pharo-project] Something I don't see in ImageSegment

by Mariano Martinez Peck

Hi. ImageSegment uses GC to compute the out pointers. Basically, to a given array of roots (a graph) it does: 1) It marks the rootArray and all root objects by turning on the Garbage Collector bit in the object header of those particular objects. 2) Then does a mark pass over all objects. This will stop at our marked roots leaving our segment unmarked in their shadow. 3) Finally, it unmarks the rootArray and all root objects. 4) Only external objects are now marked. The unmarked objects in the graph of objects of the arrays are those who will be put in the WordArray (the segment) and those who are marked to the outPointers. However, I don't see where step 2) is done in Interpreter >> primitiveStoreImageSegment In a piece of such method it does: "Then do a mark pass over all objects. This will stop at our marked roots, thus leaving our segment unmarked in their shadow." savedYoungStart := youngStart. youngStart := self startOfMemory. "process all of memory" "clear the recycled context lists" freeContexts := NilContext. freeLargeContexts := NilContext. self markAndTraceInterpreterOops. "and special objects array" youngStart := savedYoungStart. "Finally unmark the rootArray and all root objects." self longAt: arrayOfRoots put: ((self longAt: arrayOfRoots) bitAnd: AllButMarkBit). ......continue....... But here I see it is only marking Interpreter oops, not all objects. And I don't see where all objects are marked even in the code that follows this little piece. You can see the comment: "Then do a mark pass over all objects" and even without the comment it makes sense to mark all objects in order to detect outPointers. Does anyone has a hint? Thanks Mariano

June 3, 2010

Re: [Pharo-project] The Morphic 3 project

by Brian Brown

Juan Vuletich wrote: > Yes, that would be cool. I also thought about multi user multi touch > tables, where I need to handle input form several fingers > simultaneously, that can belong or not to the same hand (user). Also > multiple standard and MIDI keyboards, continuous MIDI controllers, pen > tablets, more "special" input devices, such as the voice and various > devices designed for people with disabilities, etc... But I have done > nothing of this yet. > > Cheers, > Juan Vuletich > On a related note... when I went to your website and looked at the svg samples, there is only one link for each pair of images; for example, both lion pictures are linked to: http://www.jvuletich.org/Morphic3/lionx.svg This is the same for all pictures, so it is hard to compare in an SVG viewer ;) - Brian

June 3, 2010

[Pharo-project] How get font instance programmatically?

by Denis Kudriashov

Hello, My task very simple. I need set some font for TextMorph instance programmatically. I found TextStyle>>named: familyName . But it search font in TextConstants that not include my font. By my font exists in visual font chooser from halo menu in text morph. How I can get font instance that I see in FontChooser (that appears by halo menu)? P.S. I try set for my text morph default Pharo 1.0 DejavuSans font

June 3, 2010

Re: [Pharo-project] Can I use Projects in Pharo?

by Schwab,Wilhelm K

Lukas, I am glad that it works for you, but it strikes me as a very poor approach. I prefer to have all of my code in one place so that additions and fixes apply to and can be tested with everything of interest to me. That said, I can easily leave w/o Squeak projects, especially given how buggy Stef has found them to be. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Lukas Renggli Sent: Wednesday, June 02, 2010 1:50 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Can I use Projects in Pharo? I have my different "projects" in different images. That works perfectly. Lukas On 2 June 2010 08:46, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> +1 on missing projects. > > to do what? > >> What is our plan to replace this functionality? > which one exactly? > >> Â Is the objection to the >> idea of projects in general, or just the Squeak implementation? > > I let you guess :) > >> I found it absolutely priceless to have a world for each task at hand >> - each set up for a particular logical task, but having access to all >> the classes in the system. > > well I spent so many hours trying to work with projects for doing > demos and my botinc book that I can tell you that they can really kill you. > > Do you know for example that when you save a project, only the last > changeset is saved with it. Then what happen if in another project you change the exact same method? > since changes do not record changes themselves but just the fact that > they was a change you can be in funny situation. > > Stef > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli www.lukas-renggli.ch _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 3, 2010

Re: [Pharo-project] Can I use Projects in Pharo?

by Igor Stasenko

On 3 June 2010 10:24, Geert Claes <geert.wl.claes(a)gmail.com> wrote: > > > Jochen Riekhof wrote: >> >>> The only thing I use projects for is to separate the different tasks I am >>> working on at the same time (like spaces on the Mac), so I can have one >>> world where I'm working on a client project, and a whole other world if >>> I... >> >> Yep, thank you Sean - this more or less nails it. Squeak projects are what >> comes closest to what i need to be able to quickly change context. It is >> perfectly ok to have them just in the image without any possibility for >> load/save. >> >> ... >> >> To summarize, I would be perfectly happy with a streamlined projects >> implementation that just gives you different view to dive into without any >> need to save them outside the present image. >> > > Seems like most people agree here that the image is your project. Â Something > that "just gives you a different view" within your live image is not really > what I would call a project and calling it that only adds to the confusion. > +1 when i first run the squeak image, and found the projects, i thought, that i could write the code and break anything in one project, and then return to another one, and everything will work as if nothing happens. Bummer. As i understood, this is a 'morphic projects' - i.e. the separate morphic world where you could place the morphs and arrange them in any way you like. But the thing is, that in such form its not very userful to me , because in my understanding, the project is something more than just being able to save the position & placement of various morphs on desktop. Using a projects in a fashion like multiple morphic desktops is might be a userful, but then, its naming is too vagure/ambiguous. I think it should be renamed to MorphicProject, because as i noted before, if something having a 'Project' name, then it should provide the way how i could completely separate one project from another one :) Just my 2c. -- Best regards, Igor Stasenko AKA sig.

June 3, 2010