- Pharo-dev - lists.pharo.org

[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

[Pharo-project] [update 2.0] #20432
by stephane ducasse Dec. 7, 2012

Dec. 7, 2012

20432 ----- Issue 7103: Job should use normalize progress [0.0 - 1.0] PART 1 http://code.google.com/p/pharo/issues/detail?id=7103 Diff information: http://ss3.gemstone.com/ss/Pharo20/Polymorph-Widgets-StephaneDucasse.742.di… http://ss3.gemstone.com/ss/Pharo20/Morphic-StephaneDucasse.1300.diff http://ss3.gemstone.com/ss/Pharo20/KernelTests-StephaneDucasse.458.diff http://ss3.gemstone.com/ss/Pharo20/Kernel-StephaneDucasse.1265.diff http://ss3.gemstone.com/ss/Pharo20/Deprecated20-StephaneDucasse.27.diff I will raise a debugger at the end. Just close it :). Stef

4 3

[Pharo-project] [update 2.0] #20433
by StÃ©phane Ducasse Dec. 7, 2012

Dec. 7, 2012

20433 ----- Issue 7110: FIx Refresh of ProgressBar http://code.google.com/p/pharo/issues/detail?id=7110 Diff information: http://ss3.gemstone.com/ss/Pharo20/Morphic-StephaneDucasse.1301.diff Stef

1 0

[Pharo-project] Delay bug
by Guillermo Polito Dec. 7, 2012

Dec. 7, 2012

Hi, When using a Delay and saving the image, the delay becomes stupidly broken. Look at this: With the following code Object subclass: #DelayBug instanceVariableNames: 'delay process' classVariableNames: '' poolDictionaries: 'private' category: 'DelayBug' start delay := Delay forMilliseconds: 300. process := [ [ Transcript logCr: 'test'. delay wait . false ] whileFalse: [ ] ] fork. - Then evaluate. *db := DelayBug new.* *db start.* - inspect *db instVarAt: 'delay'.* * * The delay seems ok. - save the image The delay has a stupid time to be finished :/ Guille

4 15

[Pharo-project] [update 2.0] #20432
by Marcus Denker Dec. 7, 2012

Dec. 7, 2012

20432 ----- Issue 6923: Missing Method in SocketStream http://code.google.com/p/pharo/issues/detail?id=6923 Diff information: http://ss3.gemstone.com/ss/Pharo20/Network-Kernel-MarcusDenker.76.diff

1 0

[Pharo-project] Pharo 2.0 BETA, Configs and Seaside
by Torsten Bergmann Dec. 7, 2012

Dec. 7, 2012

1. Since NativeBoost is now integrated I removed the config from the ConfigurationBrowser - because it makes no sense to install when it is already in the image :) 2. Please help to test external packages and if they are known to work on Pharo 2.0 please put a copy of ConfigurationOf... also into https://ss3.gemstone.com/ss/MetaRepoForPharo20.html Do not forget to put a symbolic version for #stable into the metacello config. This way they will show up in and will be loadable from the ConfigurationBrowser. 3. I would like to see a config with a recent Seaside for Pharo 2.0 showing up and putting it into ConfigurationBrowser too so Seaside is easily loadable right from Pharo 2.0. It loads well on the BETA when one uses: https://github.com/renggli/builder/blob/master/scripts/seaside31-pharo2.st and Gofer new squeaksource: 'ZincHTTPComponents'; "package: 'Zinc-HTTP';" package: 'Zinc-Seaside'; load. The only thing I've hit was some deprecation stuff #includesSubString: vs. includesSubstring: but I did not check all seaside tests. @Dale: whats the state of a Seaside config for Pharo 2.0? Thanks T.

5 4

[Pharo-project] [Fuel] Materialization error, #DoIt Not found
by Vanessa PeÃ±a Araya Dec. 7, 2012

Dec. 7, 2012

Hi, I was working with Fuel to save and load a Roassal view (serialize and materialize), and everything works perfect (so far) except for one thing: if I have an Anouncer which its registry has an announcementSubscription with a nil subscriber, it does not work is gives me this error: Standard Roassal interactions are OK, but if I do: aRoElement on: ROMouseClick do: [something] in a Wokspace materialization does not work. If I execute the same code in a method send as message to an object I have not this error and materialization works perfectly. This means I can not save some visualizations created in the Workspace. Have anyone experience something like this? Thanks, Vanessa.

2 4