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

[Pharo-project] FFI and underscores in 1.1 (RC2)

by Schwab,Wilhelm K

I just had an underwhelming response to my latest adventure into FFI, specifically wrapping the Acces IO USB API. Specifically, very few functions survived from description to actually being compiled. AFAICT, the compiler does not like underscores in method names for external functions. I'm not even sure how to describe it other than to give an example. This works: dIOWrite8:deviceIndex byteIndex:byteIndex data:data "unsigned long DIO_Write8(unsigned long DeviceIndex, unsigned long ByteIndex, unsigned char Data)" < cdecl: ulong 'DIO_Write8' ( ulong ulong byte ) > ^self invalidCall. This should compile, but it complains about a mismatch in the number of arguments: DIO_Write8:deviceIndex byteIndex:byteIndex data:data "unsigned long DIO_Write8(unsigned long DeviceIndex, unsigned long ByteIndex, unsigned char Data)" < cdecl: ulong 'DIO_Write8' ( ulong ulong byte ) > ^self invalidCall. The less Pharo forces us to change names as given from the outside, the better off we will be. I am using a 1.1 RC2 image, just in case this has been fixed since then?? I really need to build a new image soon. Bill

Aug. 21, 2010

Re: [Pharo-project] some important fixes we should focus on for 1.2

by GermÃ¡n Arduino

Hi Stef: I am with very little free time, but I'm still dealing with the Issue 2770. As fas as I can understand and fix it, can try with some of the issues you commented. Cheers. 2010/8/21 stephane ducasse <stephane.ducasse(a)free.fr>: > Hi guys > > here is a list of issue I would like to work and get some help. > > Stef > > http://code.google.com/p/pharo/issues/detail?id=2570 Issue 2570: > Removed implicit conversion of DateAndTime equality-testing argument. > > http://code.google.com/p/pharo/issues/detail?id=2579 > http://code.google.com/p/pharo/issues/detail?id=2698 > Â Â Issue 2698: Â Â Â Â Smalltalk registration to SystemChangeNotifier should be handle in startup > http://code.google.com/p/pharo/issues/detail?id=2177 Issue 2177: Â Â Â Â Generalize stream protocol #readInto:startingAt:count: > Issue 1981: Â Â Raising DuplicateError Exception in class builder > http://code.google.com/p/pharo/issues/detail?id=1981 > http://code.google.com/p/pharo/issues/detail?id=2146 Issue 2146: Â Â Â Â Fix SystemChangeNotification for traits. > > http://code.google.com/p/pharo/issues/detail?id=1899 Issue 1899: Â Â Â Â MethodDictionary improvement > http://code.google.com/p/pharo/issues/detail?id=2315 Method Dictionary Compact protocol to investigate > > http://code.google.com/p/pharo/issues/list?cursor=2313 Â Issue 2313: Â Â HashedCollectionIntegrityTest > > http://code.google.com/p/pharo/issues/detail?id=2583 Issue 2583: Â Â Â Â COG - MessageTally > Â Issue 2619: Â Â ignore vm parameters with nil value in MessageTally, so it can be used in Cog > > http://code.google.com/p/pharo/issues/detail?id=2584 COG- COG- LargeNegativeInteger to be compact at 5 > > http://code.google.com/p/pharo/issues/detail?id=2567 > Â Issue 2567: Â Â evaluate the finalizers outside the protected block in WeakRegistry > > http://code.google.com/p/pharo/issues/detail?id=2564 > Â Issue 2564: Â Â WeakKeyDictionary finalizeValue tests > > http://code.google.com/p/pharo/issues/detail?id=2769 > Issue 2769: Â Â Fixes for broken SocketStream behavior. > > http://code.google.com/p/pharo/issues/list?cursor=2551 weakstructure > > http://code.google.com/p/pharo/issues/detail?can=2&q=2244 > Issue 2244: Â Â Socket support for #next:putAll:startingAt: and #readInto:startingAt:count: > > http://code.google.com/p/pharo/issues/detail?id=2825 > Issue 2825: Â Â [[true] whileTrue] fork cannot be interrupted > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- ================================================= GermÃ¡n S. ArduinoÂ <gsa @ arsol.net>Â Â Twitter: garduino Arduino Software & Web HostingÂ Â http://www.arduinosoftware.com PasswordsProÂ http://www.passwordspro.com =================================================

Aug. 21, 2010

Re: [Pharo-project] Trying to install Rio file handling package

by Lawson English

Thanks. Lawson On 8/20/10 2:46 PM, Schwab,Wilhelm K wrote: > Rio was a thorn in my side for several (sub)releases, but it was apparently because something was loading an old version of it?? You might try loading it in Linux, as there was a bug that would prevent it loading on Windows at one point, but it could load on Linux (and probably a mac too), after which it would have to fixed for the image to load on Windows. Good luck. > > Bill > > >

Aug. 21, 2010

[Pharo-project] some important fixes we should focus on for 1.2

by stephane ducasse

Hi guys here is a list of issue I would like to work and get some help. Stef http://code.google.com/p/pharo/issues/detail?id=2570 Issue 2570: Removed implicit conversion of DateAndTime equality-testing argument. http://code.google.com/p/pharo/issues/detail?id=2579 http://code.google.com/p/pharo/issues/detail?id=2698 Issue 2698: Smalltalk registration to SystemChangeNotifier should be handle in startup http://code.google.com/p/pharo/issues/detail?id=2177 Issue 2177: Generalize stream protocol #readInto:startingAt:count: Issue 1981: Raising DuplicateError Exception in class builder http://code.google.com/p/pharo/issues/detail?id=1981 http://code.google.com/p/pharo/issues/detail?id=2146 Issue 2146: Fix SystemChangeNotification for traits. http://code.google.com/p/pharo/issues/detail?id=1899 Issue 1899: MethodDictionary improvement http://code.google.com/p/pharo/issues/detail?id=2315 Method Dictionary Compact protocol to investigate http://code.google.com/p/pharo/issues/list?cursor=2313 Issue 2313: HashedCollectionIntegrityTest http://code.google.com/p/pharo/issues/detail?id=2583 Issue 2583: COG - MessageTally Issue 2619: ignore vm parameters with nil value in MessageTally, so it can be used in Cog http://code.google.com/p/pharo/issues/detail?id=2584 COG- COG- LargeNegativeInteger to be compact at 5 http://code.google.com/p/pharo/issues/detail?id=2567 Issue 2567: evaluate the finalizers outside the protected block in WeakRegistry http://code.google.com/p/pharo/issues/detail?id=2564 Issue 2564: WeakKeyDictionary finalizeValue tests http://code.google.com/p/pharo/issues/detail?id=2769 Issue 2769: Fixes for broken SocketStream behavior. http://code.google.com/p/pharo/issues/list?cursor=2551 weakstructure http://code.google.com/p/pharo/issues/detail?can=2&q=2244 Issue 2244: Socket support for #next:putAll:startingAt: and #readInto:startingAt:count: http://code.google.com/p/pharo/issues/detail?id=2825 Issue 2825: [[true] whileTrue] fork cannot be interrupted

Aug. 21, 2010

[Pharo-project] How to redraw a PluggableTreeMorph when its contents change

by Rob Rothwell

Thanks to the TreeMorph Pharocast (thank you!) and some digging, I have added a context menu to a PluggableTreeMorph that lets me add a child to a selected node (I am just using the idea of nested "accounts"): addAccount | isExpanded | aTreeMorph selectedMorph complexContents item addAccount: (Account new accountName: (UIManager default request: 'Enter a new account name:')). isExpanded := aTreeMorph selectedMorph isExpanded. aTreeMorph toggleExpandedState: aTreeMorph selectedMorph. isExpanded ifTrue: [aTreeMorph toggleExpandedState: aTreeMorph selectedMorph.] But as you can see I can only figure out how to show new nodes by toggling the expanded state, which is really not helpful if you want to rename, delete, etc... Is there a way to somehow just inform the PluggableTreeMorph to redraw itself after changing its contents? Thank you, Rob

Aug. 21, 2010

Re: [Pharo-project] Something wrong with changes?

by Schwab,Wilhelm K

I was able to get a very recent image from the Windows box and it seems to work correctly after re-saving on Linux. I am not sure exactly what I would lose by stopping at this point, hence my next question. Not knowing whether the change log from the broken image is at fault, I hesitate to use it as the basis for future work. If I understand how to recover lost changes, that is exactly what I would do: use it as the change log for the working image and recover changes into it. Is there another, perhaps safer, way to do that? Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Schwab,Wilhelm K [bschwab(a)anest.ufl.edu] Sent: Friday, August 20, 2010 3:24 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: [Pharo-project] Something wrong with changes? I might have a corrupt change log. It is not particularly large, so I doubt it is size related. The problem is that I am not getting temporary names (lots of t1, t2, ... where there should be meaningful names). I recently copied the image from Linux to Windows and back; the timing is interesting. I also sometimes find that Ubuntu takes a LONG time to complete writes to flash sticks and wonder whether that might be an accident waiting to happen?? I have a backup from not quite a week ago and will check the image on the Windows box. Between the two of them and some recovery, I can probably be back in action quickly. It is also time for me to move from 1.1 RC2 to release anyway. Does any of this (possible changes woes and/or problems moving between Linux and Windows) sound familiar? Bill _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 20, 2010

Re: [Pharo-project] Trying to install Rio file handling package

by Schwab,Wilhelm K

Rio was a thorn in my side for several (sub)releases, but it was apparently because something was loading an old version of it?? You might try loading it in Linux, as there was a bug that would prevent it loading on Windows at one point, but it could load on Linux (and probably a mac too), after which it would have to fixed for the image to load on Windows. Good luck. Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Lawson English [lenglish5(a)cox.net] Sent: Friday, August 20, 2010 5:36 PM To: The general-purpose Squeak developers list; Pharo-project(a)lists.gforge.inria.fr Subject: [Pharo-project] Trying to install Rio file handling package The Gallery addon for pier first requires that Rio be installed. http://www.squeaksource.com/@7zePIlRlfoA0dT1I/VwzOlsoy However, rio won't install due to errors: FileMacOSXExectuive class as yet unclassified getenv: getenv: varString " self getenv: 'HOME' " " self getenv: 'ZYZZYX' " <> expected ->cdecl: char* 'getenv' ( char* ) module: 'libc.dylib'> ^self externalCallFailed Happens in both the latest Pharo and the latest Squeak. Not sure how to fix this... thanks for any advice. Lawson _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 20, 2010

[Pharo-project] Trying to install Rio file handling package

by Lawson English

The Gallery addon for pier first requires that Rio be installed. http://www.squeaksource.com/@7zePIlRlfoA0dT1I/VwzOlsoy However, rio won't install due to errors: FileMacOSXExectuive class as yet unclassified getenv: getenv: varString " self getenv: 'HOME' " " self getenv: 'ZYZZYX' " <> expected ->cdecl: char* 'getenv' ( char* ) module: 'libc.dylib'> ^self externalCallFailed Happens in both the latest Pharo and the latest Squeak. Not sure how to fix this... thanks for any advice. Lawson

Aug. 20, 2010

Re: [Pharo-project] How can I load metacello without OB

by Mariano Martinez Peck

On Fri, Aug 20, 2010 at 4:19 PM, Tudor Girba <tudor.girba(a)gmail.com> wrote: > Indeed, now we could add this method in Gofer. > > I didn't understand. Which method ? why in Gofer? > Cheers, > Doru > > > > On 20 Aug 2010, at 16:01, Mariano Martinez Peck wrote: > > >> >> On Fri, Aug 20, 2010 at 3:54 PM, StÃ©phane Ducasse < >> stephane.ducasse(a)inria.fr> wrote: >> > >> > The problem is in ConfigurationOfRPackage as in #ensureMetacello is >> like this: >> > >> > ensureMetacello >> > Smalltalk at: #MetacelloProject ifAbsent: [ >> > Gofer new >> > disableRepositoryErrors; >> > url: 'http://seaside.gemstone.com/ss/metacello'; >> > package: 'ConfigurationOfMetacello'; >> > load. >> > (Smalltalk at: #ConfigurationOfMetacello) project latestVersion >> load: #('default' 'UI') ] >> >> I hate the fact that we should copy all the code around.... >> what a crap. >> >> This was discussed several, severaaaaal times. As I remember the problem >> was that otherwise you class depends on a base class that should be included >> in the image you are working on. >> But I guess we don't have problem to add such base class in PharoCore...if >> we have Gofer.. >> >> >> > >> > >> > If you see, it is loading #('default' 'UI') of metacello..... UI -> OB. >> > >> > change that to #('default') and wala >> > >> > BTW, I would use the latest recommended #ensureMetacello: >> > >> > http://code.google.com/p/metacello/wiki/EnsureMetacello >> > >> > cheers >> > >> > mariano >> > >> > >> > And stuck because OB does not load in 1.2 so I lost one hour...... >> boring. >> > >> > 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 >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > -- > www.tudorgirba.com > > "Live like you mean it." > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 20, 2010

Re: [Pharo-project] Introducing smallUML: a little project to help us document :)

by StÃ©phane Ducasse

On Aug 20, 2010, at 9:57 PM, Adrian Lienhard wrote: > Hi Carla, > > Nice! Here a few random comments: > > - I really like that I can ship the diagrams with the code Thanks :) > - if I understand correctly, the method names are hardcoded in the spec. Hence, when I document my software with a diagram and then I change the code, my diagram gets out of date. If you already have the diagram with the code, I think you miss an opportunity here. For now we make it static but working. > - I don't understand why, when I drag a box, there are suddenly two arrows shown (I guess the second arrow should be its shadow, but it does not really work) > > - I suggest to simplify menu labels like "Add new class box" to "New class". "New" implies that it gets added, and you don't need to say "box" because its clear from the context that this will be a box. It also avoids confusion about classboxes (for those who know classboxes). > > - One feature of the class diagram that would be very nice to have is associations. > > - I couldn't figure out how to create relationships > > - I suggest, instead of adding new type of diagrams, to first make the class diagram really good. You have a much larger impact if you do just one small thing but really well. I told her :) > > > Cheers, > Adrian > > > On Aug 19, 2010, at 16:56 , Carla F. Griggio wrote: > >> Hi everyone! >> Well, here I am announcing the resulting project of my GSoC experience during the [your] summer: smallUML, a project to help us building diagrams and sharing them with any package of code. >> My mentor was Stephane Ducasse and my co-mentor Geert Claes, so thanks to them for the guidance up to now, and also to Fernando Olivero who helped me a lot (hope to do some coding with you at ESUG! :P). >> >> You can gofer it: >> >> Gofer it >> squeaksource: 'smallUML'; >> package: 'ConfigurationOfSmallUML'; >> load. >> (Smalltalk at: #ConfigurationOfSmallUML) project latestVersion load. >> >> And then open the Diagram Browser of the current little examples evaluating: >> >> DiagramDrawingDocumentation openDiagramBrowser . >> >> This is beta and I'm still working on it, my work will continue after GSoC's deadline, so of course your welcome to give some feedback and think about what features would you like it to have and if you're confortable with the current features. It would be really nice if this helped to get all Pharo projects more documented, with visual diagrams that help understanding them at a glance. >> >> Talking about that... the current features are: >> â¢ Open a Diagram Browser for an existing Category Diagrams Holder (this is a class ment to hold the created diagrams and there should be one per category, for now; you can browse DiagramDrawingDocumentation to see an example) >> â¢ Create and edit diagrams programatically describing them with "diagram code" (the diagram code it's just a protocol of methods meant to describe diagrams, you can see some diagram code browsing DiagramDrawingDocumentation methods or each Class Box in the Diagram Browser) >> â¢ Every diagram you build through the Diagram Browser it's saved as "diagram code", so you can share it as code that will reproduce your diagram :) That means that diagrams can 'travel' along it's package when you commit your changes with Monticello! And then they can be edited by anybody, they're not just a pretty picture. >> â¢ You can export your diagram as a PNG picture or you can export it's "diagram code" as a workspace. >> â¢ Only Class Diagrams can be built for now. >> â¢ Class Boxes of a class diagram can be dragged to be easily positioned. >> Some details that are missing: >> â¢ It's funny, but I can't center the class boxes title! :P >> â¢ I tried adding some scrollbars to the "whiteboard" where you can view your diagrams in the Diagram Browser, but if I did that the drag & drop of the class boxes worked funny :( I'll ask about that to you later. >> On the way: >> â¢ Tests and documentation, and a screencast showing every feature. >> â¢ Lots of refactors: as I'm adding more kind of diagrams right now, so I'm doing a lot of refactors to make everything more flexible and improving all the messy code there. >> â¢ A version of Minimal Connectors for anybody to use if they feel like connecting morphs for another project. >> â¢ Some usability improvements. >> â¢ Object diagrams >> â¢ Sequence diagrams >> â¢ Your feedback :D >> >> So I'd really appreciate if you can give it a try and tell me how you feel about it, I'd like it to be very usable. >> >> Cheers! >> >> Carla >> >> _______________________________________________ >> 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

Aug. 20, 2010