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

Re: [Pharo-project] [ANN] Gofer Project Loader 1.0 (BETA)
by Dale Henrichs April 23, 2010

April 23, 2010

----- "Esteban Lorenzano" <estebanlm(a)gmail.com> wrote: | > - any idea about how we go to differentiate "stable" and "unstable" | | > universes for each Pharo version? How does the user know which version | > is the one he needs for his version of Pharo? Sorry, this is not | > directly related to the Gofer Project Loader but I think it is the next | > important step towards a working package management system! | | No clue... maybe we need to add to Metacello a new "dependence | dimension", like "minimum version of distribution"... but Dale can be | much more helpful than me in this area. I imagine that code targetted for specific Pharo versions will be treated like we treat code targeted for different Smalltalk dialects. So you would write specs like the following: spec for: #common do: [...]. spec for: #squeakCommon do: [...]. spec for: #pharo do: [...]. spec for: #'pharo1.0' do: [...]. spec for: #'pharo1.1' do: [...]. or possibly like the following, if a finer version granularity is needed: spec for: #common do: [...]. spec for: #squeakCommon do: [...]. spec for: #pharo do: [...]. spec for: #'pharo1.0' do: [...]. spec for: #'pharo1.0-10508' do: [...]. spec for: #'pharo1.0-10515' do: [...]. spec for: #'pharo1.1' do: [...]. spec for: #'pharo1.1-11508' do: [...]. spec for: #'pharo1.1-11515' do: [...]. Dale

5 13

[Pharo-project] About getting HashedCollection (another dream happening)
by stephane ducasse April 11, 2010

April 11, 2010

Hi levente and others I always wanted to have Dictionary not be a subclass of Set and you did it. Now when you introduced that in Squeak, we were busy. But now I'm so found of this change (like other Smalltalk -> SmalltalkImage current --- which we stopped in the middle because lack of momentum and mindsharing) that I would like to integrate it into Pharo. Do you have any specific recommandations (like not shooting in our own foot)? Stef

6 13

[Pharo-project] [Preview] Help System with new model
by Torsten Bergmann April 8, 2010

April 8, 2010

Hi, sorry for the delay on the help system - but time is rare these days. I know some of you are impatient - therefore I've commited my restructured code for the help system for you to look what is coming - even when it is not fully finished. But the restructured new model is now in place - I have to add more tests and adapt the "help on the help system" to document my ideas. I also want to work on compatibility with Squeak as the first version had. Currently the new stuff only work in Pharo. What is new =========== While we had 3 model classes in my initial version (and after Dannys additions even more classes) I now reduced the model to a very, very simple approach with just one model class. We now have a HelpBrowser that is "just" displaying topics. A topic (see class HelpTopic) is - providing a title and optionally an icon - able to have subtopics, - provides contents (that is displayed be the browser), - can be identified by a unique key (so we can later open the help browser on a specific topic from within other tools) You can create help topics from each and anything. To try it out just load the baseline (in Pharo 1.0 or 1.1): -------------------------------------------- Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfHelpSystem'; load. ((Smalltalk at: #ConfigurationOfHelpSystem) project version: '1.0-baseline') load -------------------------------------------- You can open the help browser from the world tool menu or via code: HelpBrowser open You can open the help browser on any object that is able to be converted into a help topic (via method #asHelpTopic). So you can write for instance: HelpBrowser openOn: Integer opening a short API help/system reference on the Integer class. The above expression is the short form for: HelpBrowser openOn: (SystemReference forClass: Integer) If you want you can include the subclasses: HelpBrowser openOn: (SystemReference hierarchyFor: Integer) or even methods HelpBrowser openOn: (SystemReference hierarchyWithMethodsFor: Integer) You can browse the whole system reference documentation using: HelpBrowser openOn: SystemReference But these are only a few examples what we can extract from the system. However - the major goal is NOT an API browser, the idea is to provide a simple architecture to provide browsable help contents depending on the context. For instance it should also be possible to use the help system to provide end user help on any commercial application that is written with Pharo. As I said you can convert any text data into topics to be displayed by the help system: the browser is able to open on anything that is convertable to a root topic using #asHelpTopic. More on this later. When you open the help browser it provides help for the whole system, so HelpBrowser open is the same as HelpBrowser openOn: SystemHelp which internally uses the class CustomHelp and subclasses to provide written text and API help to form a system wide help system. If you want you can also load "Metacello-Help" and "Squeak-Help" from the http://www.squeaksource.com/HelpSystem repository to see how the new topics are automatically used when they were just loaded. Yes, I would like to see a richer text support (using markup language) and written text documentation accessible directly from within the image. But the first step was to get a simple model, the next step would be to see if the extension mechanism is good enough (CustomHelp, HelpBuilder with own builders, ...) Some more notes on the architecture and extension ideas: ======================================================== 1. the model as I said before is now reduced to a single class (HelpTopic) 2. When you open the help browser on an object the method #asHelpTopic is sent to the object by the browser to get the root node of the displayed topic hierarchy: HelpBrowser openOn: myObject Typically the object does not convert itself to a help topic structure, usually it dispatches to a builder (see HelpBuilder and subclasses) who does all this. So the help text can be already in the image even when the help system itself is NOT YET THERE/LOADED and if you want to provide help text in whatever form you are not dependent on the help system itself!!! Later a builder can extract and convert the data. You can have builders for anything - even a builder who gets informations from the web or hard disk. But note: if you want to have your own help shown up in the standard help then you have to at least use the "CustomHelp" subclass mechanism. 3. The help browser is a simple tree view and is currently limited to ASCII text. One step in the future could be to provide a "contentType" (similar to MIME) to support other content types (for instance active morphs displayed in clean up book morphs, HTML help with scamper in the help browser, ...) 4. I dont expect the basic model to change much further - maybe Take care: all of this is still unfinished but in a usable state. The "Help on Help" is not yet updated. The tests are not reviewed, just brouht to green. So you have to rely on the implementation, all the informations in this mail or directly ask questions. Bye Torsten -- GMX DSL: Internet, Telefon und Entertainment fÃ¼r nur 19,99 EUR/mtl.! http://portal.gmx.net/de/go/dsl02

3 5

[Pharo-project] nebraska?
by Lawson English April 6, 2010

April 6, 2010

I was fooling around and noticed that Nebraska isn't in the Pharo RC image. Is it compatible at all with pharo, since it is based on Morphic? lawson

10 25

[Pharo-project] SUnit
by Adrian Kuhn April 6, 2010

April 6, 2010

Niko and me are thinking about doing some work on SUnit. Background is that we are working on Phexample, which extends SUnit with test that expand on one another [1]. We got test dependencies working with the current SUnit, but had to do some quick ugly hacks. So we thought about cleaning the internals SUnit up, and then include test dependencies in the core. Things we would possible change (we will certainly identify more as we clean up SUnit...) - store test resources in a dynamic variable rather than a static one - refactor the assert: protocol to a trait, such that they can be used in setup and teardown of test resources as well (actually I already did that, you can find a version on my squeaksource account) - apply the fixes to test resources in Niall's slide deck that Lukas showed us - add expectations matchers as used in behavior-driven testing - break testcase into two classes, and to run the test and one to store the result (no more #cleanUpInstanceVariables hack to avoid memory leaks) - add test dependencies to test results, such that one test can extend on the return value of another test - fix expected failures such that they are a first-class result (no more #shouldPass with O(n^2) or worse behavior) So you see, the idea is twofold: first to clean up what is there, and second to add test dependencies as a new feature. For those that dont know test dependencies. They had first been proposed by Markus GÃ¤lli based on an analysis of all Squeak tests years ago. He found that most tests cover a superset of another test's coverage set. A prototype in Java as been implemented later by Lea HÃ¤nsenberger and me. We published a case study at XP 2008, which lead to PHP folks to include test dependencies in the latest PHPUnit. The idea of explicit test dependencies is to shift the burden of isolating test cases from the developers to the framework. You avoid duplicate test code and you get less red test cases per failure. Please refer to Niko's blog post for more details [2]. We got some more ideas (such as API baseline testing, search in test results, etc...) but they will not likely make it into a first clean up. One thing we do not know is how many folks are out there that depend on internal representation of SUnit. I talked to some folks and identified two requirements, first that legacy tests should keep running and second that contributions to other sunit forks should keep being mergeable. The first seems feasible, the second sounds like it boils down to not cleaning anything :) What do you think? cheers, AA [1]: http://www.squeaksource.com/phexample.html [2]: http://smalltalkthoughts.blogspot.com/2009/11/phexample-because-examples-ex…

15 65

[Pharo-project] Collection
by stephane ducasse April 3, 2010

April 3, 2010

Hi guys tristan is a new student here and he would like to work on collection optimization and implementation. I would like the get some ideas from you. - are there some collections that would be cool to improve? - are there some collections that would be cool to have and that we do not have yet? If you have any idea related to optimizations let me know. Stef

13 24

[Pharo-project] squeakToUTF-8 and related?
by StÃ©phane Ducasse April 3, 2010

April 3, 2010

Hi I'm trying to remember the situation with the internal representation of string in pharo/squeak to revise http://book.seaside.st/book/in-action/serving-files/character-encodings/sea… I saw that in pharo we have this NonASCIIMap. I do not remember what have been done in pharo. Argh memory leaks.... Nicolas do you remember the situation? In this context what is the squeakToUTF8 related behavior? is squeak still using latin-1 or in the midst of changing? Stef

8 32

[Pharo-project] Registering a tool in the world menu
by HernÃ¡n Morales Durand April 1, 2010

April 1, 2010

Hi list, I'm using PharoCore 1.1 #11301. Now I want to adapt some tools to use the new menu registration mechanism. When I evaluate: menuCommandOn: aBuilder <worldMenu> (aBuilder item: #'Dependency Browser') parent: #Tools; action:[self open]; icon: UITheme current windowMenuForm. the world menu is modified including only the Dependency Browser item and all remaining items were removed. Did I miss something? Cheers, HernÃ¡n

3 5

[Pharo-project] CompiledMethod asString is a text
by Niko Schwarz April 1, 2010

April 1, 2010

Hi, I just bumped into this. Probably this is intended somehow, but it does seem weird enough to ask â¦ (Object >> #hash) asString class returns 'Text'. Cheers, Niko -- http://scg.unibe.ch/staff/Schwarz twitter.com/nes1983 Tel: +41 076 235 8683

8 21

[Pharo-project] Need screenshots
by Adrian Lienhard April 1, 2010

April 1, 2010

To prepare the website for the upcoming release, I'd like to update the page http://pharo-project.org/about/screenshots with nice new screenshots. Any takers? Cheers, Adrian ___________________ http://www.adrian-lienhard.ch/

4 6