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

[Pharo-project] Unable to run pharo on Ubuntu 12.10
by dimitris chloupis Dec. 10, 2012

Dec. 10, 2012

I try to double click the Pharo-1.4-one-click.sh , even after going to properties and enabling allow excuting file as programm does nothing. And running from terminal prints the following exloupis@ephestos:~/Downloads/Pharo-1.4-one-click.app$ sudo ./Pharo-1.4-one-click.sh ./Pharo-1.4-one-click.sh: line 26: /home/exloupis/Downloads/Pharo-1.4-one-click.app/Contents/Linux/pharo: Permission denied ./Pharo-1.4-one-click.sh: line 26: exec: /home/exloupis/Downloads/Pharo-1.4-one-click.app/Contents/Linux/pharo: cannot execute: Permission denied Any idea why ?

2 1

[Pharo-project] strange == behavior
by Ciprian Teodorov Dec. 10, 2012

Dec. 10, 2012

Hi guys, Playing with some recursive data-structure I have found some strange piece of behavior in Pharo. If in an workspace we try to evaluate: a := Association new. a key: 3. a value: a. a == a value. the first time we get "true", the second we get an infinite loop... A simple workaround is to declare "a": |a| a := Association new. a key: 3. a value: a. a == a value. My question now is: Is this a bug or a feature ? By the way the same thing happens in 1.4 and 2.0 equally. By the way, in Pharo 2.0 doing cmd + . erases the lines selected in the workspace replacing them by "." Cheers, -- Dr. Ciprian TEODOROV IngÃ©nieur DÃ©veloppement CAO tÃ©l : 06 08 54 73 48 mail : ciprian.teodorov(a)gmail.com www.teodorov.ro

9 18

[Pharo-project] eating some obsolete dog food
by Nicolas Cellier Dec. 9, 2012

Dec. 9, 2012

This is a long time since I did not contribute to Pharo, so I tried with something easy... http://code.google.com/p/pharo/issues/detail?id=7108 I downloaded latest successful build, Pharo2.0a Latest update: #20433 Then I updated the 5 methods from a MC merge, and... Err... I cannot type my initials ^H^H^H^H^H^H^H^H full name The dialog insists on selecting any letter I type and next letter will override the previous one. I finally published anonymously, that does not matter... But you know the impact of a first bad UI impression... It would ruin tons of efforts I know you spent cleaning the infrastructure. I believe such cleaning is very ambitious and rarely rewarding in the short term... But I'd really like to be more supportive, it's so essential for building the future. So before ranting loud, I digged a bit further: could it be this warning I had at startup about obsolete VM, yes that was it! So if you are episodic user like me : ******** DON'T FORGET TO DOWNLOAD A PHARO SPECIFIC VM ************* I already spent way more time on this than I wished, hope my mistake helps someone else. ( over-estimating pharo planned obsolescence period is indeed a mistake ;) why would the VM be handled differently ? ) Last thing, maybe you should insist on the download page that 2.0 REQUIRES a pharo specific VM. Not sure I would have read it, but then it would be entirely my fault. Nicolas

7 9

[Pharo-project] Errors after force quit on Windows
by Sean P. DeNigris Dec. 8, 2012

Dec. 8, 2012

My image hung waiting on data from a socket, so I aborted via "End Task" in Windows 7. When I restarted it, I got "CannotDeleteFileException: Could not delete the old version of file Z:\Pharo-2.0-one-click.app\Contents\Resources\stdout" Then, when I went to save the image, it was complaining about the changes file: MultiByteFileStream(Object)>>primitiveFailed: MultiByteFileStream(Object)>>primitiveFailed MultiByteFileStream(StandardFileStream)>>primSize: MultiByteFileStream(StandardFileStream)>>size MultiByteFileStream(StandardFileStream)>>setToEnd ChangesLog>>assureStartupStampLogged Any ideas? Thanks, Sean -- View this message in context: http://forum.world.st/Errors-after-force-quit-on-Windows-tp4658575.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

2 2

[Pharo-project] Please use 20431 I rollback 20432 and 20433
by StÃ©phane Ducasse Dec. 8, 2012

Dec. 8, 2012

Hi guys Sorry for my mistake. I rollbacked 20432 and 20433 since the changes are too intrusive. Stef

2 2

[Pharo-project] Progress Update
by Camillo Bruni Dec. 8, 2012

Dec. 8, 2012

I promised to fix my partial refactoring for the ProgressBar. Finally this evening I hacked on the whole progress mess :), now I am almost done with one little bug left. - the progress bar is always responsive - all processes showing a progress with priority <60 can be interrupted - refreshes periodically 16 times per second - only forces a manual refresh when blocking the UI - no more out of bounds progress bars - no more ugly display buffer pattern when resizing the screen during a running progress this is a massive improvement for me :) For instance now you can simply interrupt the test runner with a click on the progress bar. I have one bug left, that is when I run the test runner, the UI event handling gets somehow disturbed. Windows no longer receive events, but everything is directly forwarded to the World. Opening the World menu is the only thing you can do :/ Anyone has a clue? The slice is in the inbox, see issue http://code.google.com/p/pharo/issues/detail?id=7103 best cami

4 6

[Pharo-project] [ANN] Pharo 2.0 enters BETA
by Esteban Lorenzano Dec. 7, 2012

Dec. 7, 2012

Hi, Today I finished the pending integrations for move to Pharo 2.0. There is still a problem with the VMs (for NB), but that's not a stopper for moving on. What does this means? Starting now, no new changes of API will be allowed, just bug fixes and minor enhancements that does not change the system behavior. We still have a long stabilization path until we can release, but we hope a couple of months will put us in shape :) Esteban

4 4

[Pharo-project] NBFFICallback fnSpec
by Jimmie Houchin Dec. 7, 2012

Dec. 7, 2012

Hello, I am working through implementing NativeBoost interface to a C wrapper dll. I have 8 callback functions to call in this interface. I am subclassing NBFFICallback as stated in the documentation. I am also implementing the fnSpec method based on the code in the header file. fnSpec ^#( void (NBExternalString rowID, Row rowData)) This is the code in the header: typedef void (*TABLE_ROW_CALLBACK)(const char *rowID, FXCHandle rowData); Should I leave the return type as void or should I use NBVoid? I do not know C at all. Is the NBExternalString suitable for the const char *rowID? The documentation says you can use it for char*, but I don't know what difference const makes. Thanks for any help. Jimmie

3 6

[Pharo-project] [RFC] Zinc-Resources
by Sven Van Caekenberghe Dec. 7, 2012

Dec. 7, 2012

Hi, This is request for comment on an idea, as suggested by Pavel because he needs it for his kernel building/packaging work, but also in line with several existing issues related to URL, URI and mime types. The idea would be to create a new package called 'Zinc-Resources' or maybe 'Zinc-Resource-Description' to contain just ZnUrl and ZnMimeType (and their supporting clases if any). The packaging requirement would be that the new package can only depend on core Smalltalk and not on any IO related packages such as File, Network or HTTP (Zn). Afterwards, File, Network or HTTP (Zn) could then add extensions, like #retrieveContents. After the separation I would like to extend ZnUrl to at least support file URIs (file://) since these are very useful. I am not sure that extending ZnUrl to be more general and to satisfy all users will be easy, I fear some conflicting goals, but we'll see. The end goal is of course to replace the old classes and simply Pharo. Any comments ? Sven PS: Of course, there would be a unit tests package as well. Actually, any changes should be test driven. -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

3 2

[Pharo-project] [NativeBoost] New kid on the block: NBExternalTypeArray + future plans
by Igor Stasenko Dec. 7, 2012

Dec. 7, 2012

Hi there, i just uploaded new version of config - 1.8 (development), where i introduced the new public core classs: NBExternalTypeArray. The class provides a generic functionality for working with arrays which elements is of foreign (C) type. And since it is a subclass of ArrayedCollection, you can use them naturally as any other Array(s)/Collection(s) in smalltalk. Here the class comment: -------------- I am abstract class which provides a convenient interface to work with arrays which elements are values of some external (C) type. In order to use me with concrete element type, you must create a subclass of me and initialize element type properly. Subclassing using public subclass: - if you want to create a public subclass of me, then you should make sure that in class-side #initialize method, you add self-send #initElementType: and specify the element type name to use. (And of course, initialize the class before attempting to create any instances). Subclassing with anonymous subclass: To create an anonymous subclass of me, use #ofType: protocol, i.e.: floatArrayClass := NBExternalTypeArray ofType: 'float'. Please note that separate #at: / #at:put: methods will be automatically added in each and every subclass. Never remove them, despite they looking identical to superclass methods! !!CAUTION!! Currently those methods do not perform any range checking for index. So, please make sure you using sane index values (1<= index <= size). Also, note, that class instance variables: elementType and elementSize, once initialized, is considered read-only. Changing them, once you created at least a single instance of your class may lead to funny consequences. Arrays in external memory vs object memory: My instances can work either with data held in object memory or in external memory. The difference is only at instantiation time: To create a new array in object memory, just use #new: protocol: myArray := floatArrayClass new: 10. "create a new array with 10 floats". To allocate a new array in external memory, use #externalNew: protocol: myArray := floatArrayClass externalNew: 10. .. myArray free. "and sure thing, do not forget to free external memory after use". To check whether array uses object memory or external memory , use #isExternal protocol. Also, you can convert any external address into NBExternalTypeArray subclass instance, i.e. suppose some external function returns a pointer (instance of NBExternalAddress): pointer := self callSomeFunc: 1. So, in order to access memory at given address as array of 100 elements of type 'int', you can use following: myArray := (NBExternalTypeArray ofType: 'int') onAddress: pointer size: 100. myArray at: 1. "read first element" myArray at: 2 put: 50. "write second element" myArray do: [:each | ... ] ... etc (sure thing, in the above example, the "NBExternalTypeArray ofType: 'int' " expression is just to demonstrate the intent. It should be replaced with some variable, which you initialize only once and use many times, because creating an anonymous subclass each time would be highly ineffective ) Supported protocols: Since NBExternalTypeArray inherits from ArrayedCollection, you're free to use any protocols defined there as well as in its superclasses. There's only few additions comparing to ArrayedCollection, like #isExternal and #free . Copying: a #copy behavior is special for external arrays: A copy will always use object memory, even if original used external memory. ----------------- Now, i would really appreciate if someone could do some more serious testing (how well it works as Collection etc), and of course do a review and feedback :) My nearest plans concerning NB: - review the callbacks interface (to make it more convenient to use , as we discussed on this list some time ago) - by seeing how nicely NBExternalTypeArray deals with external/internal duality, i am now inclined to do the same for NBExternalStructure. (Yes.. nice and simple things are not often so obvious :) Like that, NBExternalStructure will be just a regular class (instead of var-byte one) which will keep 'data' object which is ByteArray for object memory allocated struct, and NBExternalAddress for indirect reference to structure data somewhere beyond our safe harbor ;)) - also, if time allows, i'd like to get threaded calls working. The prototype was started by Javier almost a year ago, and we need to finish it. Also, we want to work together with Esteban for making Objective-C bridge functional. This will bring us one step closer to multiple different goals: - native window management - allow us to avoid extra blitting Athens -> Display -> ObjC view.. but just Athens ->Obj-C :) - direct use of Obj-C runtime - .. reimplement VM features in image + adding new stuff (and sure thing, Esteban has own) And, of course, besides of that, soon we will start working on unified FFI interface for Pharo. So, people will no longer need to choose between old FFI/Alien/NB, since it will be ONE in the core functionality of a system. P.S. i'd like to thank everyone, who helping me with development of NB. In last couple months, i really see how your contribution helps bringing NB to better quality levels. Even though, not all of you risking to practice dark-assembly magic, ditching some nuances and polishing rough corners etc is really helpful.. because i wouldn't say that i'm in a mood of polishing project right now, because i more focused on adding missing features. :) -- Best regards, Igor Stasenko.

5 10