- Pharo-users - lists.pharo.org

Re: [Pharo-users] OpenGL project

by Dimitris Chloupis

Better name it "Pharo OpenGL ES" so people don't get confused why some of their OpenGL code does not work. You won't finds docs about it , the guy that made it rarely frequents this forums anymore and his code is based on a api that is no longer included and supported by Pharo because it was doing a lot of machine code stuff that was very hard to maintain. My advise is don't worry about backward compatibility , make it easy, make it simple. Don't be afraid to code some of it in C if you have to. Sometimes it's far easier to use C than Pharo. Pharo is no magic wand. And foremost ask a ton of questions. We love questions. On Fri, 25 Mar 2016 at 11:38, Thibault Raffaillac < thibault.raffaillac(a)inria.fr> wrote: > > Can you include a proper build script? > > Yep sorry, here are the steps I used to make it run on OSX: > $ brew install glfw3 > $ cc demo.c -lglfw3 -framework OpenGL > > For other systems the doc is hopefully detailed enough ( > http://www.glfw.org/docs/latest/build.html) > > > Why do you say ?porting NBOpenGL?? Is it just a matter of rewriting the > > native calls with the new FFI system? > NBOpenGL functions were generated automatically from NBGLGenerator, so I > need to get used to the tool beforehand. It looks like a lot of work was > put into this, can I find a paper about it? > Also, IMO this all looks too complex. My point in limiting to ES 2 is not > just removing functions, I want to make it look simple like the C demo! > > Thibault > >

March 25, 2016

Re: [Pharo-users] OpenGL project

by Thibault Raffaillac

> Can you include a proper build script? Yep sorry, here are the steps I used to make it run on OSX: $ brew install glfw3 $ cc demo.c -lglfw3 -framework OpenGL For other systems the doc is hopefully detailed enough (http://www.glfw.org/docs/latest/build.html) > Why do you say ?porting NBOpenGL?? Is it just a matter of rewriting the > native calls with the new FFI system? NBOpenGL functions were generated automatically from NBGLGenerator, so I need to get used to the tool beforehand. It looks like a lot of work was put into this, can I find a paper about it? Also, IMO this all looks too complex. My point in limiting to ES 2 is not just removing functions, I want to make it look simple like the C demo! Thibault

March 25, 2016

Re: [Pharo-users] [ANN] Simple FogBugz Search tool in Pharo

by Ben Coman

Looks cool. Now to ask for more ;) Something like this would be nice to have integrated into Pharo, plus listing and filtering on For Review status, and showing and loading slices. cheers -ben On Fri, Mar 25, 2016 at 8:08 AM, Torsten Bergmann <astares(a)gmx.de> wrote: > Hi, > > played with the JSON API of Pharo FogBugz issue tracker with the outcome of > another little Pharo tool that lets you: > > - login to FogBugz from Pharo > - enter a string and search for according issues > - open a browser on a selected issue in the result list (works on Linux and Win so far) > > The project repo is at: > > http://www.smalltalkhub.com/#!/~TorstenBergmann/FogBugz > > One can use the client also directly: > > |client| > client := FogBugzClient loginUser: 'abc(a)def.com' password: 'secret'. > (client query: 'UFFI') inspect. > client logout > > You can download the tool in latest Pharo 5 (50660 or later) from catalog > or by opening the Spotter and entering "FogBugz", wait and hitting ENTER. > > Attached is a screenshot. > > Enjoy > T.

March 25, 2016

[ANN] Simple FogBugz Search tool in Pharo

by Torsten Bergmann

Hi, played with the JSON API of Pharo FogBugz issue tracker with the outcome of another little Pharo tool that lets you: - login to FogBugz from Pharo - enter a string and search for according issues - open a browser on a selected issue in the result list (works on Linux and Win so far) The project repo is at: http://www.smalltalkhub.com/#!/~TorstenBergmann/FogBugz One can use the client also directly: |client| client := FogBugzClient loginUser: 'abc(a)def.com' password: 'secret'. (client query: 'UFFI') inspect. client logout You can download the tool in latest Pharo 5 (50660 or later) from catalog or by opening the Spotter and entering "FogBugz", wait and hitting ENTER. Attached is a screenshot. Enjoy T.

March 25, 2016

Re: [Pharo-users] left-pad.io

by phil＠highoctane.be

The network is the computer. ... and the planet is now overheating. Internet, the great CO2 production device. http://www.internetlivestats.com/watch/co2-emissions/ Phil On Thu, Mar 24, 2016 at 8:58 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > This is a really great joke: > > > http://left-pad.io/ <http://left-pad.io/> > > But should you feel the need to implement this extremely valuable web > service yourself, here is how you could do it in Pharo (error handling is > not 100% bullet proof, this is just a quick demo, but you get the idea): > > 'paddin'' oswalt' padLeftTo: 68 with: $@. > > (ZnServer startDefaultOn: 8080) > onRequestRespond: [ :req | > | str len ch | > str := req uri queryAt: #str ifAbsent: [ '' ]. > len := req uri queryAt: #len ifAbsent: [ '' ]. > len := Integer readFrom: len ifFail: [ 0 ]. > ch := (req uri queryAt: #ch ifAbsent: [ ' ' ]) first. > ZnResponse ok: (ZnEntity text: (str padLeftTo: len with: ch)) ]. > > ZnClient new > host: #localhost; > port: 8080; > queryAt: #str put: 'paddin'' oswalt'; > queryAt: #len put: 68; > queryAt: #ch put: $@; > get. > > $ curl 'http://localhost:8080/?str=paddin%27%20oswalt&len=68&ch=@' > > Of course, if you are really going this into production, you'll have to > pay me and Pharo the necessary royalties ;-) > > Sven > > PS: Returning a JSON (which does not really make sense here) is left as an > exercise. > > > >

March 24, 2016

left-pad.io

by Sven Van Caekenberghe

This is a really great joke: > http://left-pad.io/ <http://left-pad.io/> But should you feel the need to implement this extremely valuable web service yourself, here is how you could do it in Pharo (error handling is not 100% bullet proof, this is just a quick demo, but you get the idea): 'paddin'' oswalt' padLeftTo: 68 with: $@. (ZnServer startDefaultOn: 8080) onRequestRespond: [ :req | | str len ch | str := req uri queryAt: #str ifAbsent: [ '' ]. len := req uri queryAt: #len ifAbsent: [ '' ]. len := Integer readFrom: len ifFail: [ 0 ]. ch := (req uri queryAt: #ch ifAbsent: [ ' ' ]) first. ZnResponse ok: (ZnEntity text: (str padLeftTo: len with: ch)) ]. ZnClient new host: #localhost; port: 8080; queryAt: #str put: 'paddin'' oswalt'; queryAt: #len put: 68; queryAt: #ch put: $@; get. $ curl 'http://localhost:8080/?str=paddin%27%20oswalt&len=68&ch=@' Of course, if you are really going this into production, you'll have to pay me and Pharo the necessary royalties ;-) Sven PS: Returning a JSON (which does not really make sense here) is left as an exercise.

March 24, 2016

Re: [Pharo-users] OpenGL project

by Alexandre Bergel

Hi Thibault, I put Ronie in copy because he is interested very much on having 3d stuff working. Why do you say âporting NBOpenGLâ? Is it just a matter of rewriting the native calls with the new FFI system? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Mar 24, 2016, at 1:59 PM, Thibault Raffaillac <thibault.raffaillac(a)inria.fr> wrote: > > _ Anybody else working on porting NBOpenGL? I am rather slow, so if we can sync work would be perfect :)

March 24, 2016

Re: [Pharo-users] OpenGL project

by Damien Pollet

Can you include a proper build script? cc --std=c99 -Wall --pedantic -I/opt/homebrew/Cellar/glfw3/3.1.2/include -L/opt/homebrew/Cellar/glfw3/3.1.2/lib -lglfw3 minimal-glfw.c -o minimal-glfw minimal-glfw.c:15:5: warning: suggest braces around initialization of subobject [-Wmissing-braces] 256, 0, // top point ^~~~~~~~ { } minimal-glfw.c:16:5: warning: suggest braces around initialization of subobject [-Wmissing-braces] 512, 256, // right point ^~~~~~~~ { } minimal-glfw.c:17:5: warning: suggest braces around initialization of subobject [-Wmissing-braces] 256, 512, // bottom point ^~~~~~~~ { } minimal-glfw.c:18:7: warning: suggest braces around initialization of subobject [-Wmissing-braces] 0, 256}; // left point ^~~~~~ { } 4 warnings generated. Undefined symbols for architecture x86_64: "_glAttachShader", referenced from: _main in minimal-glfw-368070.o "_glBindBuffer", referenced from: _main in minimal-glfw-368070.o "_glBufferData", referenced from: _main in minimal-glfw-368070.o "_glClear", referenced from: _main in minimal-glfw-368070.o "_glClearColor", referenced from: _main in minimal-glfw-368070.o "_glCompileShader", referenced from: _main in minimal-glfw-368070.o "_glCreateProgram", referenced from: _main in minimal-glfw-368070.o "_glCreateShader", referenced from: _main in minimal-glfw-368070.o "_glDrawArrays", referenced from: _main in minimal-glfw-368070.o "_glEnableVertexAttribArray", referenced from: _main in minimal-glfw-368070.o "_glGenBuffers", referenced from: _main in minimal-glfw-368070.o "_glGetAttribLocation", referenced from: _main in minimal-glfw-368070.o "_glLinkProgram", referenced from: _main in minimal-glfw-368070.o "_glShaderSource", referenced from: _main in minimal-glfw-368070.o "_glUseProgram", referenced from: _main in minimal-glfw-368070.o "_glVertexAttribPointer", referenced from: _main in minimal-glfw-368070.o ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) make: *** [minimal-glfw] Error 1 On 24 March 2016 at 17:59, Thibault Raffaillac <thibault.raffaillac(a)inria.fr > wrote: > Hi, > > Some progress on the OpenGL project: > _ I read much of the sources around NBOpenGL, the architecture looks nice > to me, so will keep it, but am actually considering to strip it to OpenGL > ES 2! This is a subset of OpenGL, but is supported on more platforms > (Android, iOS, RPi), and will be easier to maintain in the long term. > _ A working minimal demo in C ( > https://drive.google.com/file/d/0B6Y_O5MtrUaEbXFjTGhUcTZwY3M/view?usp=shari… > ) > _ SDL2 gave me some headaches (2~3 seconds to start & open a window, could > not properly display the title bar, displays big ugly pixels on retina > screen, could not test it in Pharo since it did not find library file). So > I tried GLFW and LOVE IT (starts fast, handles the pixel density problem > nicely, amazing documentation). I will work to bind it with FFI. > _ Anybody else working on porting NBOpenGL? I am rather slow, so if we can > sync work would be perfect :) > > Cheers, > Thibault > > > ------------------------------ > > > > Message: 2 > > Date: Sat, 12 Mar 2016 09:06:36 +0100 > > From: stepharo <stepharo(a)free.fr> > > To: pharo-users(a)lists.pharo.org > > Subject: Re: [Pharo-users] OpenGL project > > Message-ID: <56E3CE0C.1010907(a)free.fr> > > Content-Type: text/plain; charset=windows-1252; format=flowed > > > > Check bloc under Moose in the CI > > there is a little class with the binding. > > > > Stef > > > > Le 11/3/16 13:22, Thibault Raffaillac a ?crit : > > > Hi, > > > > > > I would like to do a bit of OpenGL in Pharo, but it does not seem to > work > > > at the moment. > > > > > > Tried NBOpenGL with a spur image (50560): > > > _ fails at installation from configuration browser (need to click > again on > > > installing to get all classes) > > > _ demo "GLTTRenderingDemo new openInWorld" fails at NBGLContextDriver > with > > > error "No suitable implementation found for initializing OpenGL context > > > for your platform" (running on a Mac) > > > > > > Tried with a pre-spur image (50496): > > > _ same weirdness at installation > > > _ demo fails at NBGLCurveRenderer with "MessageNotUnderstood: receiver > of > > > on: is nil" > > > > > > Is there a working demo available out there? I have worked a lot with > > > OpenGL ES 2.0 and could definitely provide work on the topic. > > > > > > Cheers, > > > Thibault > > > > >

March 24, 2016

Re: [Pharo-users] OpenGL project

by Thibault Raffaillac

Hi, Some progress on the OpenGL project: _ I read much of the sources around NBOpenGL, the architecture looks nice to me, so will keep it, but am actually considering to strip it to OpenGL ES 2! This is a subset of OpenGL, but is supported on more platforms (Android, iOS, RPi), and will be easier to maintain in the long term. _ A working minimal demo in C (https://drive.google.com/file/d/0B6Y_O5MtrUaEbXFjTGhUcTZwY3M/view?usp=shari…) _ SDL2 gave me some headaches (2~3 seconds to start & open a window, could not properly display the title bar, displays big ugly pixels on retina screen, could not test it in Pharo since it did not find library file). So I tried GLFW and LOVE IT (starts fast, handles the pixel density problem nicely, amazing documentation). I will work to bind it with FFI. _ Anybody else working on porting NBOpenGL? I am rather slow, so if we can sync work would be perfect :) Cheers, Thibault > ------------------------------ > > Message: 2 > Date: Sat, 12 Mar 2016 09:06:36 +0100 > From: stepharo <stepharo(a)free.fr> > To: pharo-users(a)lists.pharo.org > Subject: Re: [Pharo-users] OpenGL project > Message-ID: <56E3CE0C.1010907(a)free.fr> > Content-Type: text/plain; charset=windows-1252; format=flowed > > Check bloc under Moose in the CI > there is a little class with the binding. > > Stef > > Le 11/3/16 13:22, Thibault Raffaillac a ?crit : > > Hi, > > > > I would like to do a bit of OpenGL in Pharo, but it does not seem to work > > at the moment. > > > > Tried NBOpenGL with a spur image (50560): > > _ fails at installation from configuration browser (need to click again on > > installing to get all classes) > > _ demo "GLTTRenderingDemo new openInWorld" fails at NBGLContextDriver with > > error "No suitable implementation found for initializing OpenGL context > > for your platform" (running on a Mac) > > > > Tried with a pre-spur image (50496): > > _ same weirdness at installation > > _ demo fails at NBGLCurveRenderer with "MessageNotUnderstood: receiver of > > on: is nil" > > > > Is there a working demo available out there? I have worked a lot with > > OpenGL ES 2.0 and could definitely provide work on the topic. > > > > Cheers, > > Thibault > >

March 24, 2016

unsubscribe

by Alex Schenkman

March 24, 2016