- Pharo-dev - lists.pharo.org

Re: [Pharo-project] ProfStef on steroids (was: Athens OpenGL backend - what does it mean?)

by dimitris chloupis

Very nicely done, thanks for sharing. Another class I need to take a look at, great! ________________________________ From: Stephan Eggermont <stephan(a)stack.nl> To: Pharo Development <pharo-project(a)lists.gforge.inria.fr> Sent: Tuesday, 27 November 2012, 1:16 Subject: Re: [Pharo-project] ProfStef on steroids (was: Athens OpenGL backend - what does it mean?) Sebastian Nozzi wrote: >When I read your past discussion about the help-system not being able >to show "figures" (I think Igor pointed it out) I thought: "wait a >second, why is it not possible to "embed" Morphs into the text?". I >thought I had seen something like that in the past before... (in >Squeak). Yes, you can do those things. I use that in the (Glamour based) Tutorial code. The red bullets are forms, inserted in a (non-empty) Text with Â Â Â richText addAttribute: (TextAnchor new Â Â Â Â Â Â anchoredMorph: GLMUIThemeExtraIcons glamorousRedCircle asMorph; Â Â Â Â Â Â yourself) from: richText size -1 to: richText size. (and yes, I'll look up the unicode value for bullet) Stephan

Nov. 26, 2012

Re: [Pharo-project] ProfStef on steroids (was: Athens OpenGL backend - what does it mean?)

by Stephan Eggermont

Sebastian Nozzi wrote: >When I read your past discussion about the help-system not being able >to show "figures" (I think Igor pointed it out) I thought: "wait a >second, why is it not possible to "embed" Morphs into the text?". I >thought I had seen something like that in the past before... (in >Squeak). Yes, you can do those things. I use that in the (Glamour based) Tutorial code. The red bullets are forms, inserted in a (non-empty) Text with richText addAttribute: (TextAnchor new anchoredMorph: GLMUIThemeExtraIcons glamorousRedCircle asMorph; yourself) from: richText size -1 to: richText size. (and yes, I'll look up the unicode value for bullet) Stephan

Nov. 26, 2012

Re: [Pharo-project] MongoTalk update

by Esteban Lorenzano

On Nov 26, 2012, at 10:40 PM, Yanni Chiu <yanni(a)rogers.com> wrote: > > > On 26/11/12 12:14 PM, Esteban Lorenzano wrote: >> MontoTalk does not handle it. Voyage does :) >> >> but... an "embedded collection" sounds strange to me... I don't >> really think that is correct. There is no such thing like embedded >> collection in a mongodb sense (If I'm understanding right you >> question). > > Sorry, bad choice of wording. I meant a Smalltalk collection, not a mongodb collection. The Spaceship/Pilot example was misleading as well. > > A better example could be something like a medication schedule with a list of times to have the medication. The list is an array (I think that term will work for Smalltalk and mongodb). It seems unnecessary to normalize the times into a separate collection. So the question is: would Voyage or MongoTalk rewrite the entire array of times on every add, remove, update of a time? yes, MongoTalk (and Voyage because of that) will re-write the full document (that's how the driver works: is document-atomic)

Nov. 26, 2012

[Pharo-project] [update 2.0] #20419

by Marcus Denker

20419 ----- Issue 7040: Move InvalidDirectoryError to Url package (sole user) http://code.google.com/p/pharo/issues/detail?id=7040 Issue 7050: Critics Browser http://code.google.com/p/pharo/issues/detail?id=7050 Issue 6956: Some Ring tests are dependent on Monticello http://code.google.com/p/pharo/issues/detail?id=6956 Diff information: http://ss3.gemstone.com/ss/Pharo20/Text-MarcusDenker.40.diff http://ss3.gemstone.com/ss/Pharo20/Ring-Tests-Monticello-MarcusDenker.10.di… http://ss3.gemstone.com/ss/Pharo20/Network-Url-MarcusDenker.80.diff http://ss3.gemstone.com/ss/Pharo20/Nautilus-MarcusDenker.378.diff http://ss3.gemstone.com/ss/Pharo20/Manifest-CriticBrowser-MarcusDenker.28.d… http://ss3.gemstone.com/ss/Pharo20/Manifest-Core-MarcusDenker.96.diff http://ss3.gemstone.com/ss/Pharo20/Files-MarcusDenker.ducasse.283.diff -- Marcus Denker -- denker(a)acm.org http://www.marcusdenker.de

Nov. 26, 2012

Re: [Pharo-project] Got our first pharo consortium contract :)

by Sebastian Nozzi

Congratulations! :-) 2012/11/26 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > Hi guys > > This is a great day. We got our first pharo consortium contract signed by a great > company: 2Denker :) > > Thanks for your trust! > > Soon the web site will get from the ground. > Esteban got distracted by some VM bug chasing parties but he will be back on it. > > Stef

Nov. 26, 2012

Re: [Pharo-project] MongoTalk update

by Yanni Chiu

On 26/11/12 12:14 PM, Esteban Lorenzano wrote: > MontoTalk does not handle it. Voyage does :) > > but... an "embedded collection" sounds strange to me... I don't > really think that is correct. There is no such thing like embedded > collection in a mongodb sense (If I'm understanding right you > question). Sorry, bad choice of wording. I meant a Smalltalk collection, not a mongodb collection. The Spaceship/Pilot example was misleading as well. A better example could be something like a medication schedule with a list of times to have the medication. The list is an array (I think that term will work for Smalltalk and mongodb). It seems unnecessary to normalize the times into a separate collection. So the question is: would Voyage or MongoTalk rewrite the entire array of times on every add, remove, update of a time?

Nov. 26, 2012

Re: [Pharo-project] [ANN] NativeBoost v 1.7

by Camillo Bruni

time to move to smalltalkhub... On 2012-11-26, at 18:01, Igor Stasenko <siguctua(a)gmail.com> wrote: > indeed, there's a problem.. > something broke MC in my image.. > i have > NativeBoost-Core-IgorStasenko.87 > NativeBoost-Core-IgorStasenko.88 > NativeBoost-Core-IgorStasenko.89 > > in my image, and when i "save" it does not showing any errors.. > > but then no files appear in squeaksource > and more than that, if i trying to open .mcz files in other image, > they fail with errror.. > > something got broken in version history :( > > > On 26 November 2012 21:04, Ciprian Teodorov <ciprian.teodorov(a)gmail.com> wrote: >> Thanks Igor for pushing the new version of NativeBoost. >> Though, as Guy noted the Core package seems to be missing from squeaksource >> >> -- >> Ciprian >> >> >> On Mon, Nov 26, 2012 at 7:52 PM, Guy Hylton <guygantuan(a)gmail.com> wrote: >>> >>> Igor, >>> >>> Just looking to check out your and the contributors hard work but >>> ConfigurationOf... refers to "NativeBoost-Core-IgorStasenko.88" which is not >>> found? >>> >>> Guy >>> >>> On Mon, Nov 26, 2012 at 12:41 PM, Igor Stasenko <siguctua(a)gmail.com> >>> wrote: >>>> >>>> Hi, there >>>> >>>> i'd like to announce new version of NativeBoost - 1.7. >>>> >>>> Here's an overview of changes comparing to previous version: >>>> >>>> - indirect argument in signatures. >>>> You can now use special syntax to indicate that argument to external >>>> function should be taken from n-th element of variable object (like >>>> Array) >>>> from method's argument or instance variable. >>>> >>>> Syntax: >>>> >>>> myMethod: args >>>> <primitive: .... > >>>> ^ self nbCall: #( void funFoo( int args@1 , float args@2 )) >>>> >>>> Usage: >>>> >>>> self myMethod: { 1 . 1.2 } >>>> >>>> Thanks to Ciprian Teodorov who proposed and implemented it. >>>> >>>> - Win32, features and examples: >>>> >>>> NBWin32Shell - an interface to use windows shell api >>>> (executing commands, showing control panel settings) >>>> >>>> different examples for using HDC, message box etc. >>>> >>>> Thanks to Torsten Bergmann for contribution! >>>> >>>> And last bits, from me: >>>> >>>> A public API changes to avoid use of NBFFICallout global, and instead >>>> use message(s) to denote FFI callout. >>>> >>>> Old syntax: >>>> >>>> NBFFICallout cdecl: #(...) emitCall: [ â¦ ] >>>> >>>> New syntax: >>>> >>>> self nbCallout function: #(â¦) emit: [â¦] >>>> >>>> >>>> Old syntax: >>>> >>>> NBFFICallout cdecl: #(...) module: .. >>>> >>>> New syntax: >>>> >>>> self nbCallout cdecl function: #(â¦) module: â¦ >>>> or: >>>> self nbCallout function: #(â¦) module: â¦ >>>> >>>> because cdecl is default >>>> >>>> Old syntax: >>>> >>>> NBFFICallout cdecl: #(...) module: .. options: #(â¦) >>>> >>>> New syntax: >>>> >>>> self nbCallout cdecl; >>>> options: #(â¦); >>>> function: #(â¦) module: â¦ >>>> >>>> >>>> Old syntax: >>>> >>>> NBFFICallout stdcall: #(...) module: .. options: #(â¦) >>>> >>>> New syntax: >>>> >>>> self nbCallout stdcall; >>>> options: #(â¦); >>>> function: #(â¦) module: â¦ >>>> >>>> ---- >>>> >>>> New API and syntax: >>>> >>>> self nbCallout function: <signature> address: [ address block ] >>>> >>>> generate code for calling a function located at given address with >>>> given signature. >>>> The address of function is provided by user in address block, which >>>> should return a pointer to the function (NBExternalAddress or Unsigned >>>> integer value, representing an absolute address of function). >>>> This API is useful, when you need to call some function which is not >>>> exported by via DLL symbol directly, but indirectly. >>>> >>>> The old NBFFICallout API is still there, but use of it is strongly >>>> discouraged. And it will be removed eventually. So be warned! :) >>>> >>>> >>>> -- >>>> Best regards, >>>> Igor Stasenko. >>>> >>> >> >> >> >> -- >> Dr. Ciprian TEODOROV >> IngÃ©nieur DÃ©veloppement CAO >> >> tÃ©l : 06 08 54 73 48 >> mail : ciprian.teodorov(a)gmail.com >> www.teodorov.ro > > > > -- > Best regards, > Igor Stasenko. >

Nov. 26, 2012

Re: [Pharo-project] [ANN] NativeBoost v 1.7

by Igor Stasenko

indeed, there's a problem.. something broke MC in my image.. i have NativeBoost-Core-IgorStasenko.87 NativeBoost-Core-IgorStasenko.88 NativeBoost-Core-IgorStasenko.89 in my image, and when i "save" it does not showing any errors.. but then no files appear in squeaksource and more than that, if i trying to open .mcz files in other image, they fail with errror.. something got broken in version history :( On 26 November 2012 21:04, Ciprian Teodorov <ciprian.teodorov(a)gmail.com> wrote: > Thanks Igor for pushing the new version of NativeBoost. > Though, as Guy noted the Core package seems to be missing from squeaksource > > -- > Ciprian > > > On Mon, Nov 26, 2012 at 7:52 PM, Guy Hylton <guygantuan(a)gmail.com> wrote: >> >> Igor, >> >> Just looking to check out your and the contributors hard work but >> ConfigurationOf... refers to "NativeBoost-Core-IgorStasenko.88" which is not >> found? >> >> Guy >> >> On Mon, Nov 26, 2012 at 12:41 PM, Igor Stasenko <siguctua(a)gmail.com> >> wrote: >>> >>> Hi, there >>> >>> i'd like to announce new version of NativeBoost - 1.7. >>> >>> Here's an overview of changes comparing to previous version: >>> >>> - indirect argument in signatures. >>> You can now use special syntax to indicate that argument to external >>> function should be taken from n-th element of variable object (like >>> Array) >>> from method's argument or instance variable. >>> >>> Syntax: >>> >>> myMethod: args >>> <primitive: .... > >>> ^ self nbCall: #( void funFoo( int args@1 , float args@2 )) >>> >>> Usage: >>> >>> self myMethod: { 1 . 1.2 } >>> >>> Thanks to Ciprian Teodorov who proposed and implemented it. >>> >>> - Win32, features and examples: >>> >>> NBWin32Shell - an interface to use windows shell api >>> (executing commands, showing control panel settings) >>> >>> different examples for using HDC, message box etc. >>> >>> Thanks to Torsten Bergmann for contribution! >>> >>> And last bits, from me: >>> >>> A public API changes to avoid use of NBFFICallout global, and instead >>> use message(s) to denote FFI callout. >>> >>> Old syntax: >>> >>> NBFFICallout cdecl: #(...) emitCall: [ â¦ ] >>> >>> New syntax: >>> >>> self nbCallout function: #(â¦) emit: [â¦] >>> >>> >>> Old syntax: >>> >>> NBFFICallout cdecl: #(...) module: .. >>> >>> New syntax: >>> >>> self nbCallout cdecl function: #(â¦) module: â¦ >>> or: >>> self nbCallout function: #(â¦) module: â¦ >>> >>> because cdecl is default >>> >>> Old syntax: >>> >>> NBFFICallout cdecl: #(...) module: .. options: #(â¦) >>> >>> New syntax: >>> >>> self nbCallout cdecl; >>> options: #(â¦); >>> function: #(â¦) module: â¦ >>> >>> >>> Old syntax: >>> >>> NBFFICallout stdcall: #(...) module: .. options: #(â¦) >>> >>> New syntax: >>> >>> self nbCallout stdcall; >>> options: #(â¦); >>> function: #(â¦) module: â¦ >>> >>> ---- >>> >>> New API and syntax: >>> >>> self nbCallout function: <signature> address: [ address block ] >>> >>> generate code for calling a function located at given address with >>> given signature. >>> The address of function is provided by user in address block, which >>> should return a pointer to the function (NBExternalAddress or Unsigned >>> integer value, representing an absolute address of function). >>> This API is useful, when you need to call some function which is not >>> exported by via DLL symbol directly, but indirectly. >>> >>> The old NBFFICallout API is still there, but use of it is strongly >>> discouraged. And it will be removed eventually. So be warned! :) >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko. >>> >> > > > > -- > Dr. Ciprian TEODOROV > IngÃ©nieur DÃ©veloppement CAO > > tÃ©l : 06 08 54 73 48 > mail : ciprian.teodorov(a)gmail.com > www.teodorov.ro -- Best regards, Igor Stasenko.

Nov. 26, 2012

[Pharo-project] Got our first pharo consortium contract :)

by StÃ©phane Ducasse

Hi guys This is a great day. We got our first pharo consortium contract signed by a great company: 2Denker :) Thanks for your trust! Soon the web site will get from the ground. Esteban got distracted by some VM bug chasing parties but he will be back on it. Stef

Nov. 26, 2012

Re: [Pharo-project] NativeBoost - new version new ideas ;)

by Ciprian Teodorov

and here is the fileout i have promised ;) On Mon, Nov 26, 2012 at 9:32 PM, Ciprian Teodorov < ciprian.teodorov(a)gmail.com> wrote: > Hi Igor, > > While I'm waiting impatiently for the new NB version I played around some > more and I have noted some ideas: > > First thing is related to structures and callbacks... what if I want to > have a callback as a member of a structure? > It seems to me that the way to go is to declare a MyCallback class and > then use it in the structure, which is fair enough. > But what if I have a function that initializes this structure with a user > provided callback? Then the structure is not printed correctly. > It seems that #*coerceReturnValue: is not implemented in the > NBCallbackType... * > *While this is not a big issue it made me think that I was doing > something wrong... Maybe in this case we can instantiate MyCallback class > and put the fct pointer in in trunk ivar.* > > Secondly, related to structs again... It seems that we can define > structures like: > struct { > void *a[2]; > } > only by transforming them to > struct { > void *a1; > void *a2; > } > Am I wrong... if not maybe we can extend a little bit the syntax for > defining structs to accept the first form... which will be far easier to > write if we have large index values like void *x[20]... > What do you think? > > Lastly, seeing that we are starting to have support for most of c-like > declarations, i am not really satified with the way the enums should be > handled... Maybe we can reify them as some kind of external object so that > we can say something like: > enum { > AAA = 1, > BBB = 2, > }; > MyEnum AAA (to get the item AAA of the enum) > MyEnum BBB value = 2 > and behind the enumeration is defined as a Dictionary of item->value > mappings. > Attached to this mail you will find a fileout of such an approach... > I agree that maybe this is not the most optimized way of dealing with > enums, however I like this approach because it is uniform (with structs, > external objects, external addresses, callbacks, etc). > Moreover if a beginner wants to hack his way into NB FFI I think it is > easier to cope with an enum object than with SharedPools defined in > classes, and imported. > > Cheers, > PS: I can't way to get my hand on the new version... > > -- > Dr. Ciprian TEODOROV > IngÃ©nieur DÃ©veloppement CAO > > tÃ©l : 06 08 54 73 48 > mail : ciprian.teodorov(a)gmail.com > www.teodorov.ro > -- Dr. Ciprian TEODOROV IngÃ©nieur DÃ©veloppement CAO tÃ©l : 06 08 54 73 48 mail : ciprian.teodorov(a)gmail.com www.teodorov.ro

Nov. 26, 2012