- Pharo-dev - lists.pharo.org

[Pharo-project] petit parser help
by Esteban Lorenzano April 26, 2011

April 26, 2011

Hi Lukas, all I'm finally working on a HTML petit parser (a very basic one, based on XML petit parser) and I have a serious problem (well... besides my complete ignorance about petit parser, he...) I need to match this pattern: openTag, contents, closeTag (that will be something like "<html> ... </html>") inlineTag (that will be something like "<br/>") openTag (that will be something like "<link ...>" or "<img src='anUrl'>") so, after try some variants... I came with this construct: element "[39] element ::= EmptyElemTag | STag content ETag" ^(self inlineTag / (self openTag, content, self closeTag) / self openTag) ==> [ :nodes | ]. openTag ^ $< asParser, qualified, whitespace optional, attributes, whitespace optional, $> asParser inlineTag ^ $< asParser, qualified, whitespace optional, attributes, whitespace optional, '/>' asParser closeTag ^'</' asParser , qualified , whitespace optional , $> asParser so... the problem here is that the statement self openTag, contents, self closeTag matchs with ... <link ...> </html> and for that reason, the resulting tree is invalid. So, I need a way to ensure the openTag name is equal to the closeTag name. How can I do that? Cheers, Esteban

4 4

[Pharo-project] Online Pharo Documentation
by Camillo Bruni April 26, 2011

April 26, 2011

Hi everyone, During the last month I worked a bit on my pharo web documentation tool. It's a derivate of ruby's http://yardoc.org/ running on top of seaside. A test image is available here: http://dl.dropbox.com/u/18184943/WebDoc.zip Open the image then access the documentation in your browser http://localhost:8080/doc There are still some glitches due to the javascript fancyness around. Features: - browse and filter packages - browse and filter classes of packages - Class overview with markdown enabled comments - fully annotated source code with popups for known types and selectors Missing: - fully functional and slightly more intelligent search for methods, classes and packages - hierarchical display of packages - bookmarkable links don't work yet. Please feel free to add your own wishes, I hope to slowly improve this webdoc to make it really usable. v(^_^)v camillo

4 5

[Pharo-project] removing versions from configurations
by Tudor Girba April 26, 2011

April 26, 2011

Hi, The Moose build broke because the 'default' version was removed from ConfigurationOfRPackage. I fixed it now by using #stable, but that is not the issue. I understand the need for cleaning, but we should be aware that removing versions from configurations can have far reaching ripple effects. Cheers, Doru -- www.tudorgirba.com "From an abstract enough point of view, any two things are similar."

3 8

[Pharo-project] new template for class empty comments for OB
by StÃ©phane Ducasse April 26, 2011

April 26, 2011

Hi lukas could you add the following in OB for missing template http://code.google.com/p/pharo/issues/detail?id=4090 templateOn: aStream aStream nextPutAll: theClass name; nextPutAll: ' has not been documented yet. The class comment should describe the purpose of the class, its collaborations and its variables. '. aStream nextPutAll: 'We encourage you to fill up the following template.'; cr;cr. aStream nextPutAll: 'Class intention';cr ; tab. aStream nextPutAll: 'I''m doing the following ...';cr;cr. aStream nextPutAll: 'Class collaborations'; cr;tab. aStream nextPutAll: 'I usually do not work in isolation but with the help of ...'; cr ;cr . aStream nextPutAll: 'Class main API'; cr; tab. aStream nextPutAll: 'My main public API is ...'. aStream nextPutAll: 'My subclasses may want to override such specific hooks ...'; cr. aStream nextPutAll: 'Implementation notes';cr. self templateLabel: 'Instance Variables:' class: theClass variables: theClass instVarNames on: aStream. self templateLabel: 'Class Instance Variables:' class: theClass class variables: theClass class instVarNames on: aStream I did the same for the default browser. Stef

4 8

[Pharo-project] [ANN] SqueakSource3 Beta.1 "Easter Fire"
by Tobias Pape April 26, 2011

April 26, 2011

Dear Smalltalkers, gladly I would like to announce the first Beta of SqueakSource3 âEaster Fireâ. To try it, take your favorite Monticello-API and install the Metacello configuration. N.B.: The SqueakSource-Configuration has a dependency on Seaside3, however, if you happen to not have Seaside installed previously there will be no adaptor chosen for you. So, it is preferable to install Seaside3 with the settings you like before installing SqueakSource. "===" "GemStone. N.B.: You probably need an almostOutOfMemory-guard." Gofer project load: 'SqueakSource' version: #easterFire group: #( 'Full' ). "--" "Squeak" Installer squeaksource project: 'MetacelloRepository' install: 'ConfigurationOfSqueakSource'. ((Smalltalk globals at: #ConfigurationOfSqueakSource) project version: #easterFire) load. "--" "Pharo" Gofer new squeaksource: MetacelloRepository; package: 'ConfigurationOfSqueakSource'; load. ((Smalltalk at: #ConfigurationOfSqueakSource) project version: #easterFire) load. "===" SqueakSource3 is a port of SqueakSource to Seaside 3 and Magritte 2. It is based on the original SqueakSource by Lukas Renggli, Adrian Lienhard, and Avi Bryant; moreover recent changes to several SqueakSource-forks are incorporated, too. Some features like access to diffs in a browser as done by Bert Freudenberg for source.squeak.org have been integrated into SqueakSource3. SqueakSource3 incorporates a basic issue tracker done by Dale Henrichs. SqueakSource3 is expected to run on GemStone/GLASS as well as on squeakish Smalltalks, ie, Pharo and Squeak. âeaster fireâ has been tested on GemStone 2.4.4.x/GLASS 1.0-beta.8 and Squeak4.2 both with Seaside 3.0.4. Pharo-tests are pending. The agenda for SqueakSource3 in random order is: â¢ Have it running on GemStone, esp. GemStone 3 beta â¢ Provide a cleaner external API (may be REST or XMLRPC) â¢ Provide a more clear modularization and extension api (example: the Issue component by Dale Henrichs) â¢ Name itâ¦suggestions are welcome. â¢ Stability. Philippe Marschal, Dale Henrichs, and Gerhard Obermann have contributed much to SqueakSource3. All feedback is appreciated. So Long, -Tobias

1 0

[Pharo-project] Pharo 1.2.1 to Pharo 1.2.2
by Miguel CobÃ¡ April 26, 2011

April 26, 2011

How will this upgrade path will be handled? In some email of previous week this is mentioned: SystemVersion newVersion: 'Pharo1.2.2a'. But evaluated in a Pharo 1.2.1 update 12345 starts updating from 12342 and stops on 12345, so I think that is wrong. Evaluating SystemVersion newVersion: 'Pharo1.2.2a' begin the update from 12346 and stops on 12350 so I think that is the correct one, right? Or should users begin with: https://gforge.inria.fr/frs/download.php/28436/PharoCore-1.2.2a-12345.zip and update from there? (This implies migrate to a new image, not so much a update from 1.2.1 to 1.2.2 but a migration). Thanks in advance. -- Miguel CobÃ¡ http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx

1 1

[Pharo-project] Glamour theme
by Alexandre Bergel April 25, 2011

April 25, 2011

Hi Doru, Just wondering whether you have tried to remove the black border of each windows. I indeed like to not have it around button, scrollbar. Why not windows? I have the impression what the window color has to slightly change when not in foreground. I like the theme, even if I am more rounded than squared :-) Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

2 2

[Pharo-project] Suggestion: rename some methods for consistency
by DougEdmunds April 25, 2011

April 25, 2011

The vast majority of example methods follow a consistent naming pattern where the word 'example' starts the method name. There's a handful that don't. The advantage of this approach is that all the examples appear together in the browser list of methods. I suggest that these methods be renamed: BorderedMorph class >> gradientExample --> exampleGradient SimpleHierarchicalListMorph class >> submorphsExample --> exampleSubmorphs PluggableMenuSpec class >> withOneSingleItemExample --> exampleWithOneSingleItem PluggableMenuSpec class >> withSubMenuExample --> exampleWithSubMenu PluggableMenuSpec class >> withTwoSimpleItemsExample --> exampleWithTwoSimpleItems DigitalSignatureAlgorith >> writeExamplesToDisk --> exampleWriteToDisk UITheme class >> textEntryWithCompletionDialog --> exampletextEntryWithCompletionDialog UITheme class >> closeExampleDialogs --> exampleCloseDialogs (I've excluded test and testcase examples from this list). -- View this message in context: http://forum.world.st/Suggestion-rename-some-methods-for-consistency-tp3473… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

1 0

Re: [Pharo-project] [Metacello] Re: Metacellobrowser feedback
by Alexandre Bergel April 25, 2011

April 25, 2011

> I understand the point you are making. I never intended my mails to be of the 'do this now' kind. I am just sharing my experiences and points of view. I have always had strong opinions about UI elements and lately even more since I have been reading up on the topic (because of my work on AspectMaps ). If my comments can be of any use and may be taken into account at some point, great, if not, no problem. I get that this is a work in progress and I am sure you have a lot of other things on your plate, as do we all :-/ > > (assuming you are replying to both my mails of last saturday, btw) No problem Johan. Thanks for sharing your experience and using your time to comment on our work. Cheers, Alexandre > > On 24 Apr 2011, at 11:52, Dale Henrichs wrote: > >> Johan, >> >> Just one point ... the ui for MetacelloBrowser is not expected to be complete at this point ... I think there are still a number of commands that need to be added before we can start considering what the final ui will look like ... once we have a feel for the set of commands that should be included and the type of work flow we are supporting (neither of which has been decided upon) we will be able to fine tune the ui and there is a lot of work that needs to be done ... >> >> You're comments about the fact that you had difficulty figuring out how to call your #loadDefault method are where we need to be focussing our efforts ... this is a missing piece of functionality that needs to be addressed. >> >> Spiffing up a ui _before_ you've decided on the final set of commands to be supported is the same type of mistake you make when making a premature optimization of an algorithm ... >> >> For me the biggest problem that I struggle with is the number of times that I must break out of the MetacelloBrowser to do work with Monticello Browser windows...I have included a number of commands in the MetacelloBrowser that allow you to perform many of the MonticelloBrowser functions and I see the need to add more ... So I begin thinking that maybe these functions should be incorporated into the MetacelloBrowser ... allow the direct viewing of the repository/history .... I'm also not happy with having to go the browser to see certain bits of information from the Metacello spec (like the description) .... I think we need to incorporate that as well ... We need major improvement in the ui for creating a configuration ... major work needs to be done there ... >> >> ... and more ... >> >> Dale >> On Apr 23, 2011, at 12:57 PM, Johan Fabry wrote: >> >>> >>> My 2 cents on this topic: user interface consistency cannot be underestimated. I called these 'leds' unit-test icons because thats what they are (in my mind and I guess also for a lot of other people). So using them for anything else is not a good idea at all. Alex' proposal seems (to me) a much better idea. > > > -- > Johan Fabry > jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry > PLEIAD Lab - Computer Science Department (DCC) - University of Chile > > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

1 0

[Pharo-project] Which packages should we include of metacello for Pharo 1.3?
by Mariano Martinez Peck April 25, 2011

April 25, 2011

Hi Dale and the rest. In Pharo 1.2 we used to include these packages/groups from Metacello: #('Metacello-Core' 'Tutorial' 'UI' 'Metacello-ProfStef' 'Metacello-Help'); and #('Tests') Is this still valid? because I decided them a couple of months ago...so maybe they are not valid anymore. For example, do we want the MetacelloBrowser or things like that ? and the MetacelloToolbox ? Thanks -- Mariano http://marianopeck.wordpress.com

3 6