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

[Pharo-project] updating ConfigurationOfPharo

by laurent laffont

Hi, I want to update ConfigurationOfPharo to include last ProfStef. Should I update #version12beta2 or create #version12beta3 ? Laurent Laffont

Dec. 13, 2010

Re: [Pharo-project] Ring - model infrastructure for Pharo

by StÃ©phane Ducasse

>> >> > #stringVersionDefault has just one sender (#markMatchingClasses in SelectorBrowser). Do we need that? let's happily kill it. > > In general, #stringVersion in MethodReference seems to be strange... > > stringVersion: 'Class>>selector:' format > > why is there an iVar for this? Can't this just use the selector and class an build it? > > Marcus > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. >

Dec. 13, 2010

Re: [Pharo-project] About using pragma for help like in setting

by StÃ©phane Ducasse

Torsten I would like to give a try to document Soup with pragma and builder. So I will start to write some documentation and after we will need to stabilize and interface for the builder. But I imagine that we need to be able to - create a topic - create a subtopic something like that. > After the discussion in May we all agreed [2] that it is a good direction to check out the > pragma/builder approach too and see how far we can go here. I provided an example how one > can easily add this "pragma approach" to to the HelpSystem ([3] and [4] for the code) but I left > out the builder part since I dont know what Lukas expects here. > > So no real feedback/adoption so far ... at least it would help if I get an example > on how the contents should be defined in an annotated #buildHelpOn: method. > > However, the pragma approach has pros and cons: > > Maybe you like: - no dependency on a common superclass or package dependency on a class in HelpSystem > - may therefore seem "cleaner" depending on POV > > Maybe you dislike: - even with pragmas one has an implicit dependency on the builders interface > which also has to be stable very early > - by using pragmas (loose coupling) you have to deal with the problem that > your parent topic may not be there/not be loaded since it can be defined > somewhere else in the class hierarchy. > > E. After the initial release people asked on how to integrate typical "Smalltalk documentation" > to include browsable reference documentation (API doc) like class and method comments in the > HelpSystem too. This was easy to add since again I just had to write a custom help builder that does the > necessary conversion. > > If you load the "Pharo-Project-Help" you can browse the complete reference on anything that > is already documented: > > > Gofer new > squeaksource: 'HelpSystem'; > package: 'Pharo-Project-Help'; > load. > HelpBrowser open. > > In the help browser click on "Pharo" and "API Reference". This is more "reference documentation" and > only a "poor" way to easily fill up the help system ;) > > I would like to see people writing more tutorials/manuals about parts of the system so one could get the big > picture, but the idea of Stef [5] to get fully documented classes and methods is also nice. For the > reference docu: > > > Maybe you like: - no dependency on anything, just comment your classes and methods > as you may know from any other smalltalk system > > Maybe you dislike: - you dont need the help system, you can look at it in the standard browser > - its only a basic API documentation system (compared to JavaDoc and others) > > ----------------------------------------------------------------------------------------------------------------- > And now some comments on IRC/posts I've seen: > > Lukas on IRC see [6]: >> [3:14pm] renggli: HelpSystem is not useable for me and obviously not for anybody else (otherwise >> it wouldn't be empty) > > Lukas, nobody forces you to follow the "define help contents via class to book mapping" approach. > If you want a "define help content via pragmas" approach then help moving this issue forward or define > your help contents the way you like and implement a custom help builder. > > For the other point: HelpSystem is not empty - look at an updated core 1.2 and it is already > used in many external packages as Laurent already pointed out. [7] > > > Lukas wrote on [8]: >>> Couldn't you just add another loop to your script to "unload all help" just >>> like unload all tests >> Sure, but that means I have to package help text separately. This is >> the contrary to what Java, Ruby, Python, Javascript, ... are doing; >> keeping code and documention as close together as possible. > > No - you dont have to package documentation seperately. A class/method comment is still a > class/method comment and its packaged with the code. There is no dependency on HelpSystem > here - although the HelpBrowser can display it too. > > You still keep code and documentation close as in any other language. > > But if you write a "big picture" help manual or tutorial on how things interact it would > be good to package it seperately. Either using CustomHelp, pragmas, or ... > > > Lukas wrote on [8]: >> I think, the fact that there is no single external package with help >> system documentation proves this, no? > > There are quite a few. Maybe you should look more often on Squeaksource. Again I point to [7] > > > Stef wrote on [9] >> Now I was thinking that torsten would reply to this mail but in 1.3 will take a decision because I want a really better help >> and documentation inside the right class and package. > > I still think that we should in minimum have the "code" - "tests" - "help" package triade, where the code package > includes the class and method documentation as any Smalltalker is used to. The test package should include unit tests > covering the code. And the help package should give a high level overview on how to use the code or tests. > > If the dependency from "help" packages to "help system" due to the class CustomHelp is a problem then > we can easily convert them once we have a good "pragma based" approach in place. > > Removing packages or classes that are not documented is too hard ... but we should use Lint rules to check the > "completeness/basic quality" of package. > > Similar to checkstyle for Java in Eclipse - if there are problems in a package then you have a different icon for > the package and you work until it's clean because it hurts your eyes (see [10] for a screenshot) > > > Hope I could at least bring some light into the whole discussion and I would really like > the see if also the pragma approach would move forward. > > Bye > Torsten > > > [1] http://forum.world.st/Preview-Help-System-with-new-model-now-also-for-Squea… > [2] http://forum.world.st/Help-System-td2131748.html > [3] http://lists.gforge.inria.fr/pipermail/pharo-project/2010-May/026148.html > [4] http://lists.gforge.inria.fr/pipermail/pharo-project/attachments/20100505/c… > [5] http://lists.gforge.inria.fr/pipermail/pharo-project/2010-December/036952.h… > [6] http://pastebin.com/Y7MFaddK > [7] http://lists.gforge.inria.fr/pipermail/pharo-project/2010-December/037507.h… > [8] http://lists.gforge.inria.fr/pipermail/pharo-project/2010-December/037485.h… > [9] http://lists.gforge.inria.fr/pipermail/pharo-project/2010-December/037499.h… > [10] http://www.ibm.com/developerworks/java/library/j-ap01117/checkstyle-eclipse… > > > > -- > Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief! > Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail >

Dec. 13, 2010

Re: [Pharo-project] Issue 2353 in pharo: #findString:startingAt:caseSensitive: broken for WideStrings

by pharo＠googlecode.com

Comment #7 on issue 2353 by da...(a)teleport.com: #findString:startingAt:caseSensitive: broken for WideStrings http://code.google.com/p/pharo/issues/detail?id=2353 I hit this case in a Seaside/Pier image in the wild and the following expression will reproduce the problem taht I observed: | str | str := WideString new: 10 withAll: 45 asCharacter. str at: 5 put: (Character value: 8217). str findString: 'intro' startingAt: 1 caseSensitive: false. Yes ... the offending Character value was 8217. I don't know exactly how a character of that value got into the WideString, but it is there. The page where the character resides is: http://book.pharo-project.org/book/introduction/gettingstarted/ And the offending character is the $' in the phrase "if you havenât done so already"... The Pier image is running with a WAComancheAdaptor that is doing utf-8 encoding ... The takeaway is that it is very possible to create an instance of WideString with Characters whose values are larger than 256 (the size of the matchTable)....

Dec. 13, 2010

[Pharo-project] [update 1.2] #12277

by Marcus Denker

12277 ----- Issue 3398: SystemNavigation and SourcedMethodReference Issue 3402: SmalltalkEditor new raises an Error -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Dec. 13, 2010

Re: [Pharo-project] Issue 3402 in pharo: SmalltalkEditor new raises an Error

by pharo＠googlecode.com

Updates: Status: Closed Comment #4 on issue 3402 by marcus.denker: SmalltalkEditor new raises an Error http://code.google.com/p/pharo/issues/detail?id=3402 12277

Dec. 13, 2010

Re: [Pharo-project] Issue 3398 in pharo: SystemNavigation and SourcedMethodReference

by pharo＠googlecode.com

Updates: Status: Closed Comment #8 on issue 3398 by marcus.denker: SystemNavigation and SourcedMethodReference http://code.google.com/p/pharo/issues/detail?id=3398 12277

Dec. 13, 2010

[Pharo-project] TODO for 1.2...

by Marcus Denker

Open Bugs: http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2 Failing Tests: https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.2/lastCompleted… and a failing build of non-Core: https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/8/console Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Dec. 13, 2010

[Pharo-project] Play MP3s in-image

by DeNigris Sean

I extracted the mp3 support from Sophie. It works in Squeak 4.1 and Pharo 1.1.1 on Mac OS 10.6.5 Load SophiePort from http://www.squeaksource.com/SPDProjectUpdates Then try: song := StreamingMP3Sound onFileNamed: '/path/to/yourFavorite.mp3'. song play. song pause. Question: * there were checks like the following that had to be removed for Pharo 1.1.1: "WeakArray isFinalizationSupported ifFalse:[^anObject]". Is this no longer necessary? n.b. I am unclear about the license - Sophie has one license, the code itself seems to be SqueakL. Do your own investigation. Sean

Dec. 13, 2010

Re: [Pharo-project] Issue 3398 in pharo: SystemNavigation and SourcedMethodReference

by pharo＠googlecode.com

Comment #7 on issue 3398 by Benjamin.VanRyseghem.Pharo: SystemNavigation and SourcedMethodReference http://code.google.com/p/pharo/issues/detail?id=3398 @Marcus : here a little fix which is basicly the same, but I compare sourcePointer instead of sourceCode :) Yes it really need a clean up ... We have submit a fix and ask people to test it, but nobodies have tried (or at least nobodies have given feedback) ... Attachments: EqualInSourcedMethodReference.1.cs 3.5 KB

Dec. 13, 2010