- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Rome and Rome plugin

by Michael Rueger

On 4/14/2010 10:06 AM, Cyrille Delaunay wrote: > RomePlugin is present in none of listLoadedModules and listBuiltinModules that would explain the problem. You need the external plugin then. MIchael

April 14, 2010

Re: [Pharo-project] [squeak-dev] Re: [ANN] OpenGL specs parser/FFI methods generator

by Igor Stasenko

On 14 April 2010 06:58, Andreas Raab <andreas.raab(a)gmx.de> wrote: > On 4/13/2010 8:42 PM, Igor Stasenko wrote: >> >> On 14 April 2010 06:22, Andreas Raab<andreas.raab(a)gmx.de> Â wrote: >>> >>> On 4/13/2010 8:10 PM, Igor Stasenko wrote: >>>> >>>> i just submitted a code, which could help us greatly in having >>>> up-to-date and full OpenGL API coverage in Squeak. >>>> >>>> This package extracts data directly from spec files, used by OpenGL >>>> folks for generating C headers (gl.h / glext.h etc). >>> >>> Sweet! I had no idea these spec files existed. Do you know if the spec >>> files >>> cover OpenGL ES as well? Also, have you run this against the existing >>> OpenGL >>> code to see if it produces matching output? (more to verify your >>> translation >>> than anything else) >>> >> I think better would be to check with C header files, like glew >> (http://sourceforge.net/projects/glew/) > > True. Have you tried it? > well this might be a bit time consumig: GLAPIData gl functions size 2063 :) so, i think this is going to be a step by step discovery process, for the functions which i will use :) >> The FFI code generator is unfinished (if you look at it, its using an >> OpenGL-defined standard type set, like GLEnum GLShort etc..) >> So, there should be 1 more mapping step to turn them into 'long short' >> etc. >> Or, if FFI can cope with type aliases, then they could be kept as is. > > This should be straightforward. > >> There's also all constant values sitting parsed. But i haven't coded >> the fileout yet. >> The repository is open for write globally, so you can just commit your >> stuff right there. >> >> But i'd like to note, that in order to avoid dependencies, it would be >> better to use separate subpackage >> for code generation, while in original package there should be just >> classes for parsing and holding the data. > > Well, I don't really care since this would be (mostly) a one-time job unless > someone cares about special API versions ;-) > i don't know, maybe i'm too picky there is FFI and Alien, also i will use it for generating native code callouts, so to not put much mess into classes which holding a data, it would be better to keep code separated, like: FFIOpenGL-Specs AlienOpenGL-Specs NBOpenGL-Specs > OpenGL should be generated by something like: > > Â Â Â Â OpenGLApiGenerator generateFunctions: 1.4 on: OpenGL. > > which would create the equivalent to the current OpenGL function set. Then > we move on to, e.g., > > Â Â Â Â OpenGLApiGenerator generateExtFunctions: 'ARB_multisample' on: > OpenGL. > > etc. The default OpenGL would include all versions and extensions but if > you'd like to be more specific you can generate custom versions of the API > for your use (we'd do this for Teleplace for example since we're trying to > stick to 1.4 and certain extensions). > Yeah, i thought about similar approach for filtering a function set by placing them into subclasses like: OpenGL10 -> OpenGL14 -> OpenGL20 ->OpenGL30 etc For instance there is: GetFragDataLocationEXT(program, name) return Int32 param program UInt32 in value param name Char in array [COMPSIZE(name)] category EXT_gpu_shader4 dlflags notlistable version 2.0 extension soft WINSOFT glfflags ignore glxflags ignore alias GetFragDataLocation and GetFragDataLocation(program, name) return Int32 param program UInt32 in value param name Char in array [COMPSIZE(name)] category VERSION_3_0 dlflags notlistable version 3.0 extension glfflags ignore glxflags ignore so, a generator could use a clever approach, like defining a single method #glGetFragDataLocation but depending on driver version, load 'GetFragDataLocationEXT' address for gl 2.0, or 'GetFragDataLocation' for gl 3.0 > Cheers, > Â - Andreas > > -- Best regards, Igor Stasenko AKA sig.

April 14, 2010

Re: [Pharo-project] pharo on sparc solaris

by Damien Pollet

On Mon, Apr 12, 2010 at 16:42, Tudor Girba <tudor.girba(a)gmail.com> wrote: > I would need to run a Pharo RC4 image on a Sparc Solaris station. Looking on > the www.squeakvm.org/unix/, I see that there is no VM for such a station, > only for Intel Solaris. > > Unfortunately, I also do not have access to any compiling tools on this > machine (it's a server). Can anyone help me with this issue? I own a couple Ultra 5 workstations, but I doubt this will be really helpful: those are quite old machines (~300MHz CPUs) and I replaced solaris with linux... > The machine says it is: > $ uname -a > SunOS ejpdxa9017 5.10 Generic_142900-03 sun4v sparc > SUNW,SPARC-Enterprise-T5220 > > > Cheers, > Doru > > -- > www.tudorgirba.com > > "To lead is not to demand things, it is to make them happen." > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

April 14, 2010

Re: [Pharo-project] Rome and Rome plugin

by Cyrille Delaunay

RomePlugin is present in none of listLoadedModules and listBuiltinModules 2010/4/14 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Hi mike and john > > We started to play with Rome with cyrille. Alain published a version that > he started to clean in the Miro repository on squeaksource > and we got the following behavior > > When we tried the car demo with sophie dev it works > > When we tried the car demo on the latest untable on mac with 4.2.2 it does > not work > we get a RomePlugin primitive > Apparently it works with alain on linux > > Now if we take the sophie image and execute it with 4.2.2 it works. > > So do you have any idea how to fix that? > > Cyrille can you execute > > Smalltalk listLoadedModules > SmalltalkImage listBuiltinModules > > Stef > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 14, 2010

[Pharo-project] Rome and Rome plugin

by StÃ©phane Ducasse

Hi mike and john We started to play with Rome with cyrille. Alain published a version that he started to clean in the Miro repository on squeaksource and we got the following behavior When we tried the car demo with sophie dev it works When we tried the car demo on the latest untable on mac with 4.2.2 it does not work we get a RomePlugin primitive Apparently it works with alain on linux Now if we take the sophie image and execute it with 4.2.2 it works. So do you have any idea how to fix that? Cyrille can you execute Smalltalk listLoadedModules SmalltalkImage listBuiltinModules Stef

April 14, 2010

[Pharo-project] Minimum Class set ...

by James Ladd

Hi All, As I continue to translate Pharo to Java as part of the Redline project I wonder, what is the minimum set of classes and methods I need to implement? I ask this because when I go through all the methods in Object I see a lot that I don't think I need to enable the Compiler to work. Would it be ok to just include those classes and methods that are defined in the Smalltalk-80 Language and it implementation (Blue) book, and the primitives? Some have already suggested looking at little smalltalk or the mini squeak image and I am. Rgs, James. _________________________________________________________________ Browse profiles for FREE! Meet local singles online. http://clk.atdmt.com/NMN/go/150855801/direct/01/

April 14, 2010

Re: [Pharo-project] [ANN] OpenGL specs parser/FFI methods generator

by Andreas Raab

On 4/13/2010 8:42 PM, Igor Stasenko wrote: > On 14 April 2010 06:22, Andreas Raab<andreas.raab(a)gmx.de> wrote: >> On 4/13/2010 8:10 PM, Igor Stasenko wrote: >>> >>> i just submitted a code, which could help us greatly in having >>> up-to-date and full OpenGL API coverage in Squeak. >>> >>> This package extracts data directly from spec files, used by OpenGL >>> folks for generating C headers (gl.h / glext.h etc). >> >> Sweet! I had no idea these spec files existed. Do you know if the spec files >> cover OpenGL ES as well? Also, have you run this against the existing OpenGL >> code to see if it produces matching output? (more to verify your translation >> than anything else) >> > I think better would be to check with C header files, like glew > (http://sourceforge.net/projects/glew/) True. Have you tried it? > The FFI code generator is unfinished (if you look at it, its using an > OpenGL-defined standard type set, like GLEnum GLShort etc..) > So, there should be 1 more mapping step to turn them into 'long short' etc. > Or, if FFI can cope with type aliases, then they could be kept as is. This should be straightforward. > There's also all constant values sitting parsed. But i haven't coded > the fileout yet. > The repository is open for write globally, so you can just commit your > stuff right there. > > But i'd like to note, that in order to avoid dependencies, it would be > better to use separate subpackage > for code generation, while in original package there should be just > classes for parsing and holding the data. Well, I don't really care since this would be (mostly) a one-time job unless someone cares about special API versions ;-) OpenGL should be generated by something like: OpenGLApiGenerator generateFunctions: 1.4 on: OpenGL. which would create the equivalent to the current OpenGL function set. Then we move on to, e.g., OpenGLApiGenerator generateExtFunctions: 'ARB_multisample' on: OpenGL. etc. The default OpenGL would include all versions and extensions but if you'd like to be more specific you can generate custom versions of the API for your use (we'd do this for Teleplace for example since we're trying to stick to 1.4 and certain extensions). Cheers, - Andreas >> I'm definitely interested in looking at this. The original OpenGL calls were >> generated by code that I've lost in the mean time so it's great to have a >> way of recreating it from first principles! >> > Yeah. I've been looking for having this a long time :) > >> Cheers, >> - Andreas >> >> >>> So it is 100% correct. >>> Parsing these files is much easier than C headers. >>> There's also a lot of additional data , which helps to automatically >>> categorise the methods and generate correct callout code. >>> >>> The parsed data can be later used for generating an FFI/Alien OpenGL >>> callout code with full coverage of all existing extensions. >>> And you don't need to keep this package in image after you done >>> generating the code. >>> Or, it can stay, just make sure that you prune all parsed data by issuing: >>> >>> GLAPIData reset. >>> >>> The sources for parsing is located at: >>> >>> http://www.opengl.org/registry/#specfiles >>> >>> Place all *.spec and *.tm files into a single directory, and then issue: >>> >>> GLAPIData parseAll: (FileDirectory on: 'your/path'). >>> >>> >>> There is an example, how to generate an FFI callout methods. >>> >>> Use: >>> >>> GLAPIData gl generateFFIMethodsInto: (FileStream newFileNamed: >>> 'gl.st') forClass: 'OpenGL' >>> >>> Then, you can file-in the generated code right into your image: >>> >>> (FileStream oldFileNamed: 'gl.st') fileIn >>> >>> The resulting file is about 700kbytes big, having methods like: >>> >>> !OpenGL methodsFor: 'EXT_framebuffer_multisample' stamp: >>> 'Igor.Stasenko 4/14/2010 05:22'! >>> glRenderbufferStorageMultisampleEXT: target with: samples with: >>> internalformat with: width with: height >>> "This method was automatically generated from OpenGL specs" >>> "See http://squeaksource.com/OpenGLSpecs for details" >>> <apicall: void 'glRenderbufferStorageMultisampleEXT' (GLenum >>> GLsizei >>> GLenum GLsizei GLsizei)> >>> ^ self externalCallFailed >>> >>> >>> P.S. I plan to use this data directly by native code, in a way like: >>> >>> glTexCoord2hNV: s with: t >>> <primitive: 'primitiveNativeCall' module: 'NativeBoostPlugin'> >>> ^ self glAPICall: 'glTexCoord2hNV' >>> >>> since i don't need a type data placed in method. I guess, Alien could >>> use similar approach. >>> >> >> >> > > >

April 14, 2010

Re: [Pharo-project] [squeak-dev] Re: [ANN] OpenGL specs parser/FFI methods generator

by Igor Stasenko

On 14 April 2010 06:22, Andreas Raab <andreas.raab(a)gmx.de> wrote: > On 4/13/2010 8:10 PM, Igor Stasenko wrote: >> >> i just submitted a code, which could help us greatly in having >> up-to-date and full OpenGL API coverage in Squeak. >> >> This package extracts data directly from spec files, used by OpenGL >> folks for generating C headers (gl.h / glext.h etc). > > Do you know if the spec files cover OpenGL ES as well? by looking at gl.spec i see some OES stuff. But its commented out and having different format. So parser don't sees it. > > Cheers, > Â - Andreas > > >> So it is 100% correct. >> Parsing these files is much easier than C headers. >> There's also a lot of additional data , which helps to automatically >> categorise the methods and generate correct callout code. >> >> The parsed data can be later used for generating an FFI/Alien OpenGL >> callout code with full coverage of all existing extensions. >> And you don't need to keep this package in image after you done >> generating the code. >> Or, it can stay, just make sure that you prune all parsed data by issuing: >> >> GLAPIData reset. >> >> The sources for parsing is located at: >> >> http://www.opengl.org/registry/#specfiles >> >> Place all *.spec and *.tm files into a single directory, and then issue: >> >> Â GLAPIData parseAll: (FileDirectory on: 'your/path'). >> >> >> There is an example, how to generate an FFI callout methods. >> >> Use: >> >> Â GLAPIData gl generateFFIMethodsInto: (FileStream newFileNamed: >> 'gl.st') forClass: 'OpenGL' >> >> Then, you can file-in the generated code right into your image: >> >> Â (FileStream oldFileNamed: 'gl.st') fileIn >> >> The resulting file is about 700kbytes big, having methods like: >> >> !OpenGL methodsFor: 'EXT_framebuffer_multisample' stamp: >> 'Igor.Stasenko 4/14/2010 05:22'! >> glRenderbufferStorageMultisampleEXT: target with: samples with: >> internalformat with: width with: height >> Â Â Â Â "This method was automatically generated from OpenGL specs" >> Â Â Â Â "See http://squeaksource.com/OpenGLSpecs for details" >> Â Â Â Â <apicall: void 'glRenderbufferStorageMultisampleEXT' (GLenum >> GLsizei >> GLenum GLsizei GLsizei)> >> Â Â Â Â ^ self externalCallFailed >> >> >> P.S. I plan to use this data directly by native code, in a way like: >> >> glTexCoord2hNV: s with: t >> Â Â Â Â <primitive: 'primitiveNativeCall' module: 'NativeBoostPlugin'> >> Â Â Â Â ^ self glAPICall: 'glTexCoord2hNV' >> >> since i don't need a type data placed in method. I guess, Alien could >> use similar approach. >> > > > -- Best regards, Igor Stasenko AKA sig.

April 14, 2010

Re: [Pharo-project] [squeak-dev] Re: [ANN] OpenGL specs parser/FFI methods generator

by Igor Stasenko

On 14 April 2010 06:22, Andreas Raab <andreas.raab(a)gmx.de> wrote: > On 4/13/2010 8:10 PM, Igor Stasenko wrote: >> >> i just submitted a code, which could help us greatly in having >> up-to-date and full OpenGL API coverage in Squeak. >> >> This package extracts data directly from spec files, used by OpenGL >> folks for generating C headers (gl.h / glext.h etc). > > Sweet! I had no idea these spec files existed. Do you know if the spec files > cover OpenGL ES as well? Also, have you run this against the existing OpenGL > code to see if it produces matching output? (more to verify your translation > than anything else) > I think better would be to check with C header files, like glew (http://sourceforge.net/projects/glew/) The FFI code generator is unfinished (if you look at it, its using an OpenGL-defined standard type set, like GLEnum GLShort etc..) So, there should be 1 more mapping step to turn them into 'long short' etc. Or, if FFI can cope with type aliases, then they could be kept as is. There's also all constant values sitting parsed. But i haven't coded the fileout yet. The repository is open for write globally, so you can just commit your stuff right there. But i'd like to note, that in order to avoid dependencies, it would be better to use separate subpackage for code generation, while in original package there should be just classes for parsing and holding the data. > I'm definitely interested in looking at this. The original OpenGL calls were > generated by code that I've lost in the mean time so it's great to have a > way of recreating it from first principles! > Yeah. I've been looking for having this a long time :) > Cheers, > Â - Andreas > > >> So it is 100% correct. >> Parsing these files is much easier than C headers. >> There's also a lot of additional data , which helps to automatically >> categorise the methods and generate correct callout code. >> >> The parsed data can be later used for generating an FFI/Alien OpenGL >> callout code with full coverage of all existing extensions. >> And you don't need to keep this package in image after you done >> generating the code. >> Or, it can stay, just make sure that you prune all parsed data by issuing: >> >> GLAPIData reset. >> >> The sources for parsing is located at: >> >> http://www.opengl.org/registry/#specfiles >> >> Place all *.spec and *.tm files into a single directory, and then issue: >> >> Â GLAPIData parseAll: (FileDirectory on: 'your/path'). >> >> >> There is an example, how to generate an FFI callout methods. >> >> Use: >> >> Â GLAPIData gl generateFFIMethodsInto: (FileStream newFileNamed: >> 'gl.st') forClass: 'OpenGL' >> >> Then, you can file-in the generated code right into your image: >> >> Â (FileStream oldFileNamed: 'gl.st') fileIn >> >> The resulting file is about 700kbytes big, having methods like: >> >> !OpenGL methodsFor: 'EXT_framebuffer_multisample' stamp: >> 'Igor.Stasenko 4/14/2010 05:22'! >> glRenderbufferStorageMultisampleEXT: target with: samples with: >> internalformat with: width with: height >> Â Â Â Â "This method was automatically generated from OpenGL specs" >> Â Â Â Â "See http://squeaksource.com/OpenGLSpecs for details" >> Â Â Â Â <apicall: void 'glRenderbufferStorageMultisampleEXT' (GLenum >> GLsizei >> GLenum GLsizei GLsizei)> >> Â Â Â Â ^ self externalCallFailed >> >> >> P.S. I plan to use this data directly by native code, in a way like: >> >> glTexCoord2hNV: s with: t >> Â Â Â Â <primitive: 'primitiveNativeCall' module: 'NativeBoostPlugin'> >> Â Â Â Â ^ self glAPICall: 'glTexCoord2hNV' >> >> since i don't need a type data placed in method. I guess, Alien could >> use similar approach. >> > > > -- Best regards, Igor Stasenko AKA sig.

April 14, 2010

Re: [Pharo-project] Connectors minimal version into pharo

by Carla F. Griggio

Interesting! I was just about to try Connectors in Pharo too :P I'd be happy to help if you need a hand. On Mon, Apr 12, 2010 at 10:11 AM, Fernando olivero <oliverof(a)lu.unisi.ch>wrote: > Great! Once i have something working i'll post the package in squeaksource. > > I will try to remove the fsm dependency and try to avoid having so many > extensions, and have a minimal functionality. > Connectors is a full blown system, i just need to draw simple constrained > connection between morphs without the graph support. > > Fernando > > > On Apr 12, 2010, at 2:00 PM, StÃ©phane Ducasse wrote: > > > > > On Apr 12, 2010, at 12:51 AM, Fernando olivero wrote: > > > >> Hi all, i just wanted to re post the fix underscore code Lukas posted a > while ago. > >> > >> I've just imported Connectors package into pharo, (i'm trying to get a > minimal version working ), > > > > excellent! > > I'm interesting in a mini version of that ;) > > > >> and stumbled upon the problem of the underscores.. > >> but now thanks to SmallInt rules it was easy and fast to overcome this > problem! > >> > > > > > > _______________________________________________ > > 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 >

April 14, 2010