- Pharo-dev - lists.pharo.org

[Pharo-project] [update 1.1] #11314 : textEditor from CUIS
by StÃ©phane Ducasse April 15, 2010

April 15, 2010

11314 ----- - Merge gofer - Issue 1225: Harvest textEditor from Squeak. Thanks Fernando. Now we should debug it. So please use them and we will find and fix the bugs. Stef

6 8

[Pharo-project] [ANN] 1.0 One-Click image
by Marcus Denker April 15, 2010

April 15, 2010

https://gforge.inria.fr/frs/download.php/26828/Pharo-1.0-OneClick.zip -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

9 16

[Pharo-project] [update 1.1] #11314 : textEditor from CUIS
by Torsten Bergmann April 15, 2010

April 15, 2010

Interesting, it says "0 new updates installed" afterwards ... I'm also not able to open the world menu on the "logo" area, looks like the morph gets all the events. Bye T. -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

7 13

[Pharo-project] Issue 2308 is fixed
by Torsten Bergmann April 14, 2010

April 14, 2010

http://code.google.com/p/pharo/issues/detail?id=2308 -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

2 1

[Pharo-project] Minimum Class set ...
by James Ladd April 14, 2010

April 14, 2010

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/

3 2

[Pharo-project] pharo on sparc solaris
by Tudor Girba April 14, 2010

April 14, 2010

Hi, 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? 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."

5 5

[Pharo-project] Open Pharo debugger from a Seaside wallback
by Facundo Vozzi April 14, 2010

April 14, 2010

Hi people, I'm using Pharo RC2 with Seaside 2.8.4 version and it's very slow when I trying to debugging a seaside application. In other words, I press the debug link on the seaside application walback and it take to Pharo over 40 seconds to open de imagen debugger. I tried with Seaside 3 developer image and it was the same situation. I'm using pharo on 32 bits Windows 7 in a Core 2 Duo and 2 GB ram memory. Has anybody experimented the same problem or behavior? Tranks, Facundo ps: Please, excuse my poor english.

7 23

[Pharo-project] CLFramework/UIBuilder
by Torsten Bergmann April 14, 2010

April 14, 2010

What's the state of the UI builder for Pharo? http://www.squeaksource.com/CLFramework.html seems to be gone. Thx T. -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

4 3

[Pharo-project] CLFramework/UIBuilder
by Torsten Bergmann April 14, 2010

April 14, 2010

>IÂ´m continue working on that,but does not have sense publish versions if >the development is not ended. >... >When the development be totally ended and exists a first version I update >the CLFramework project To me this really looks like a step in the wrong direction and I dont know what lead to this decision. Especially since it was a great addition to Pharo. Even when the framework was not finished I was able to look at your code from time to time. Did't have the time to help but it was good that it was there. I was able to learn more about using Polymorph and I could follow your progress. And it was already usable since I tried to build a small GUI without any problems. There are also now many postings out there pointing to the project on Squeaksource - but it is gone. Why completely remove it? If you care about people then: - make it available - create a ConfigurationOfCLFramework where you mark it as "alpha" until you are ready to provide a first version (can help you here if you want) - if someone complains tell him it is still "alpha" and if he uses it it is on his own risk, others should wait for the first usable release version You can also use the Metacello config to mark working milestone versions and continue to work on a baseline with new features. It is your decision but I would really like to see it republished. Thx Torsten -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

1 0

[Pharo-project] [ANN] OpenGL specs parser/FFI methods generator
by Igor Stasenko April 14, 2010

April 14, 2010

Hello, 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). 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.

2 5