- Pharo-dev - lists.pharo.org

Re: [Pharo-project] TalkFFI: automatic FFI generation for Pharo

by StÃ©phane Ducasse

Thanks Ciprian. It is a nice extension :). we should write a little tutorial :) Stef > Happy new year everybody! > > I am pleased to announce today the initial release of TalkFFI. > > TalkFFI enables automatic FFI generation for Smalltalk. > It uses libclang to parse unmodified C header files and generate FFI bindings to c libraries. > For now it supports the generation of NativeBoost FFI bindings. > > The project is released under MIT license, and you can find it on the smalltalkhub site. > http://smalltalkhub.com/#!/~CipT/TalkFFI > > Please do not hesitate send me your comments/critics/ideas. > > Best regards, > -- > Dr. Ciprian TEODOROV > IngÃ©nieur DÃ©veloppement CAO > > tÃ©l : 06 08 54 73 48 > mail : ciprian.teodorov(a)gmail.com > www.teodorov.ro

Jan. 6, 2013

Re: [Pharo-project] TalkFFI: automatic FFI generation for Pharo

by Ciprian Teodorov

Hi guys, I have just uploaded a short presentation video on youtube (generation of LLVM mapping), so that you can get the taste of it. http://youtu.be/y_zfgUh27m0 On Sun, Jan 6, 2013 at 7:18 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > On Jan 6, 2013, at 7:07 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> > wrote: > > That's super awesome. Thanks!! > And the documentation answer that I was just going to ask you :) > *"The libclang bindings themselves were also generated using TalkFFI > (using minimal hand-written binding for bootstrapping)."* > > sweet :) > > Yes, that looks very interesting! > > Marcus > > > -- Dr. Ciprian TEODOROV IngÃ©nieur DÃ©veloppement CAO tÃ©l : 06 08 54 73 48 mail : ciprian.teodorov(a)gmail.com www.teodorov.ro

Jan. 6, 2013

Re: [Pharo-project] TalkFFI: automatic FFI generation for Pharo

by Marcus Denker

On Jan 6, 2013, at 7:07 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > That's super awesome. Thanks!! > And the documentation answer that I was just going to ask you :) > "The libclang bindings themselves were also generated using TalkFFI (using minimal hand-written binding for bootstrapping)." > > sweet :) > Yes, that looks very interesting! Marcus

Jan. 6, 2013

Re: [Pharo-project] TalkFFI: automatic FFI generation for Pharo

by Mariano Martinez Peck

That's super awesome. Thanks!! And the documentation answer that I was just going to ask you :) *"The libclang bindings themselves were also generated using TalkFFI (using minimal hand-written binding for bootstrapping)."* sweet :) On Sun, Jan 6, 2013 at 1:22 PM, Ciprian Teodorov <ciprian.teodorov(a)gmail.com > wrote: > Happy new year everybody! > > I am pleased to announce today the initial release of TalkFFI. > > TalkFFI enables *automatic* FFI generation for Smalltalk. > It uses libclang <http://clang.llvm.org> to parse *unmodified* C header > files and generate FFI bindings to c libraries. > For now it supports the generation of NativeBoost FFI bindings. > > The project is released under MIT license, and you can find it on the > smalltalkhub site. > http://smalltalkhub.com/#!/~CipT/TalkFFI > > Please do not hesitate send me your comments/critics/ideas. > > Best regards, > -- > Dr. Ciprian TEODOROV > IngÃ©nieur DÃ©veloppement CAO > > tÃ©l : 06 08 54 73 48 > mail : ciprian.teodorov(a)gmail.com > www.teodorov.ro > -- Mariano http://marianopeck.wordpress.com

Jan. 6, 2013

[Pharo-project] TalkFFI: automatic FFI generation for Pharo

by Ciprian Teodorov

Happy new year everybody! I am pleased to announce today the initial release of TalkFFI. TalkFFI enables *automatic* FFI generation for Smalltalk. It uses libclang <http://clang.llvm.org> to parse *unmodified* C header files and generate FFI bindings to c libraries. For now it supports the generation of NativeBoost FFI bindings. The project is released under MIT license, and you can find it on the smalltalkhub site. http://smalltalkhub.com/#!/~CipT/TalkFFI Please do not hesitate send me your comments/critics/ideas. Best regards, -- Dr. Ciprian TEODOROV IngÃ©nieur DÃ©veloppement CAO tÃ©l : 06 08 54 73 48 mail : ciprian.teodorov(a)gmail.com www.teodorov.ro

Jan. 6, 2013

Re: [Pharo-project] zero conf scripts location

by Camillo Bruni

On 2013-01-06, at 10:23, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Jan 4, 2013, at 9:59 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > >> I plan to move the ci-zero conf scripts to a new subdirectory >> >> http://pharo.gforge.inria.fr/ci/script/* >> >> instead of >> >> http://pharo.gforge.inria.fr/ci/* >> >> >> is anyone besides our ci servers using theses scripts? >> > Only people that use it to download new imagesâ¦ who are all > on the list. so consider them moved ;)

Jan. 6, 2013

Re: [Pharo-project] zero conf scripts location

by Marcus Denker

On Jan 4, 2013, at 9:59 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > I plan to move the ci-zero conf scripts to a new subdirectory > > http://pharo.gforge.inria.fr/ci/script/* > > instead of > > http://pharo.gforge.inria.fr/ci/* > > > is anyone besides our ci servers using theses scripts? > Only people that use it to download new imagesâ¦ who are all on the list. Marcus

Jan. 6, 2013

Re: [Pharo-project] [ANN] NBOpenGL update

by Dan Corneanu

thx, for the help. I finally got it working after I have updated my display driver. On Sat, Jan 5, 2013 at 11:17 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 5 January 2013 21:41, Dan Corneanu <dan.corneanu(a)gmail.com> wrote: > > Ok, I have fixed those problems but now I stumbled on other problems. > > If I load the latest version > > ConfigurationOfNBOpenGL project lastVersion load. > > When I try to run the demo I get a SubscriptOutOfBounds:2083 exception at > > NBOpenGLAPIBase>>emitCall: generator: > > > this looks strange. there should be no out of bound indexes by > construction, > since during automatic code generation, every unique GL function has > assigned number and NBOpenGLAPIBase creates > a variable-size object to hold all of them. > > > If I load version 1.0.2 > > (ConfigurationOfNBOpenGL project version: '1.0.2') load. > > and try the demo I get > > 'Error: Frame buffer is incomplete: GL_FRAMEBUFFER_UNSUPPORTED' > > in > > this message says for itself. > sounds like your video driver does not supports the framebuffer in > configuration which > i intended to use. > > > NBGLFrameBuffer>>checkStatus > > > > By the way, I am on a windows machine. > > > > > > On Sat, Jan 5, 2013 at 9:34 PM, Igor Stasenko <siguctua(a)gmail.com> > wrote: > >> > >> On 5 January 2013 11:29, Dan Corneanu <dan.corneanu(a)gmail.com> wrote: > >> > Hello, > >> > I have loaded the latest NBOpenGL into Pharo 1.4 but when I try > >> > GLTTRenderingDemo new openInWorld. > >> > I get a > >> > SmallInteger(Object)>>doesNotUnderstand: #| > >> > > >> > What am I missing/doing wrong? > >> > > >> this is an extension method, which looks like i missed when splitting > >> package.. > >> it is synonym for #bitOr: > >> > >> > Best regards, > >> > Dan. > >> > > >> > P.S. > >> > There is also a typo in: > >> > NBMacGLContextDriver >> supportsCurrentPlatform > >> > "NativeBoostConstants mac32PlaformId" I think it should be > >> > "NativeBoostConstants mac32PlatformId" > >> > > >> yes. > >> Should fix it :) > >> > >> > > >> > > >> > On Fri, Apr 6, 2012 at 3:31 PM, Igor Stasenko <siguctua(a)gmail.com> > >> > wrote: > >> >> > >> >> Hi there, > >> >> > >> >> for those, who interested, i updated a NBOpenGL configuration. > >> >> > >> >> Changes are: > >> >> > >> >> - updated GL API to most recent available (taken directly from > opengl > >> >> specs). Now there is about 300 more methods to explore :) > >> >> - finally dealt with win32 support code and made it working again > >> >> - fixed the GLX function prefix , which should be 'glX' not 'glx' > >> >> > >> >> To load it in 1.4 use: > >> >> > >> >> Gofer new > >> >> squeaksource: 'NBOpenGL'; > >> >> package: 'ConfigurationOfNBOpenGL'; > >> >> load. > >> >> > >> >> > >> >> and then > >> >> > >> >> (ConfigurationOfNBOpenGL project version: '1.0.2') load > >> >> > >> >> I did not tested the update thoroughly.. so i would appreciate if > >> >> people will try it out and tell how it goes. > >> >> > >> >> > >> >> -- > >> >> Best regards, > >> >> Igor Stasenko. > >> >> > >> > > >> > >> > >> > >> -- > >> Best regards, > >> Igor Stasenko. > >> > > > > > > -- > Best regards, > Igor Stasenko. > >

Jan. 6, 2013

[Pharo-project] Slides for a talk on "Why I Still Use Smalltalk" for comments

by Stephen Travis Pope

Hello all, I've put together a set of slides for a 90-minute lecture/demo on "Why I Still Use Smalltalk" to be given to a colloquium of graduate media arts and technology students at UCSB (where I taught from 1996-2010). I up-loaded the slides for your comments; there's a 19-page PDF file (6 slides per page) at, http://HeavenEverywhere.com/STP_ST80_Talk_Slides.pdf Your comments/questions are welcome... (The demo at the start will be using VisualWorks to build the canonical up/down counter.) (Slide 12 is me and the head of the composition department at UCSB, both in 1984, for context.) stp -- Stephen Travis Pope Santa Barbara, California, USA http://HeavenEverywhere.com Begin forwarded message: > From: Stephen Travis Pope <stephen(a)heaveneverywhere.com> > Date: October 26, 2012 12:47:55 PM PDT > To: vwnc <vwnc(a)cs.uiuc.edu> > Cc: Stephen Travis Pope <stephen(a)heaveneverywhere.com> > Subject: Outline of a talk on "Why I Still Use Smalltalk" for comments > > > Hello all, > > I'm planning to give a colloquium called "Why I Still Use Smalltalk" for the graduate students at UCSB, and wanted to solicit your comments on the outline. > > stp > > -------------------- > > Why I Still Use Smalltalk > > Graduate Colloquium > UCSB Graduate Program in Media Arts and Technology > November, 2012 > Stephen Travis Pope, stephen(a)FASTLabInc.com > > -------------------- > > Proposal > > Title: Why I Still Use Smalltalk > > Abstract > > The Smalltalk-80 programming system is celebrating its 30th birthday this year (Smalltalk-80 version 2 was released and documented in a series of books in 1982). The system was the first popular software development tool that incorporated a number of features we take for granted today, including an object-oriented programming language, a comprehensive open-source class library, an integrated window-based development environment, and a cross-platform virtual-machine-based delivery system. Nevertheless, Smalltalk has nowhere near the installed base or the mindshare of lesser peers such as C++ or Java, or more modern descendants such as Python or Ruby. This talk will introduce the Smalltalk system's language, libraries and tools, outline its history, and discuss the reasons why it is not more widely used. Several aspects of the Smalltalk system make it especially good for developing multimedia applications, and these will be introduced with examples from the last 30 years. The presenter was among the very first to use Smalltalk for real-world applications, and worked on the Smalltalk team at Xerox PARC and their spin-off ParcPlace Systems from 1986-94. He still uses Smalltalk (now available in both commercial and free versions) for his day-to-day work. > > Presenter > > Stephen Travis Pope is a software engineer and composer based in Santa Barbara. He taught at UCSB (in the departments of Music and Computer Science, and the Graduate Program in Media Arts and Technology) from 1996-2010, and is now known as FASTLabInc.com (for multimedia software) and HeavenEverywhere.com (for music and film). > > ---------------------------- > > Outline > Introduction > Demo > What Is Smalltalk? > The Language > The Libraries > The Environment > A Brief History > Smalltalk Leaves PARC > C++, ObjectiveC and Java > Smalltalk Today > Why I Still Use Smalltalk > > Introduction > Overview > My background in 1981 > > Demo > Counter Example with GUI > > What Is Smalltalk? > Language > Libraries > Tools, IDE > Methodology > Note: "OO is not Enough!" > > The Language > Terse, expressive, readable > Everything is an Object (really, everything) > All activity is message-passing > Trivial syntax, no reserved words > true, false, nil, self, super, thisContext > Control structures written in Smalltalk > Messages to Booleans, Blocks, etc. > Means they're extensible (!) > aCollection do: [ :item | Transcript show: item printString] > Keyword syntax - messages with > 1 argument alternate keyword/argumentâ¦ > anArray at: 1 (getter) > anArray at: 1 put: 'hello' (setter) > r := Rectangle top: 1 left: 1 width: 10 height: 10 > Fully Reflective > (isKindOf:, understands:, â¦) > Compiles to a virtual machine language (normally) > > The Libraries > Everything is an Object > Polymorphism (heavily used) > E.g., many implementations of at:put: or + > OO Design Patterns > Composite, Adaptor, Singleton, MVC, Visitor, â¦ > Magnitudes, Collections and Streams > Graphics and Windows > All classes are extensible (!) > Example: aString asPath: sepChar > Try this in C++ or ObjC... > > The Methodology > OO A/D Methods (OBA) > OO Design Patterns > Domain-specific Languages > > The Tools > Window-based GUI and Tools > Multi-desktop (Projects) > Browsers, Inspectors and Editors > Rules of Reuse (Programmer as Reader project) > Pluggable look-and-feel > Code-sharing tools: change-lists, Envy > Open-source Tools (!!) > > Tool Demo > Browsers > Code in DB package, class, category, method > Compile 1 method at a time > "Programmer as Reader" facilities > Senders, implementors, class/variable references > Flavors of browsers: protocol, hierarchy, namespace, etc. > Debugger > Just like the browser(!!!) > Fix and continue > CASE Tools > Change lists, packages, projects > > The Environment > VI/VM Architecture > VI like APL workspaces, LISP core files > Snapshot/restart (relation to BOSS files) > VM - "cheat but don't get caught" > Thinks it's an operating system > "The OS is only there for all the things you forgot to put in the language" > Scheduler, file system, network drivers, etc. in Smalltalk > Light-weight processes and scheduler in Smalltalk > Simple VM: Byte-code interpreter > High-performance VM: JIT Optimizing > Native code caches > Polymorphic inline caches > > Other Novel Aspects > Other languages in Smalltalk (Lisp, Prolog, etc.) > Compiler frameworks > Smalltalk-as-OS (running on naked hardware) > OOP and AI > Frames/objects, rules, logic, etc. > Early "block diagram compilers" > > Smalltalk and Multimedia > Early Computer Graphics > BitBLT pixel graphics > SPIM and graphics contexts > Music with Smalltalk > Real-time FM on the Alto > Real-time scheduling for MIDI > Music notations in Smalltalk > > Early (1980s) Applications > ThingLab > ThinkerToy > Graphical programming > Analyst > AI, Multimedia, Graphical Programming > Chinese Temple Design ToolKit > Models of process > MOBY, DoubleTalk > Petri Nets > ObjectWorks/C++ > ST-like IDE for C++ > > Early (1980s) Music Applications > HyperScore ToolKit/MODE > Music composition and notations > SoundKit > Music signal processing > Kyma > Cross-compilation for a DSP > Harmonic Analysis Tool > Chord/Harmony analysis expert system > Smoke > Flexible music representation language > > The Risks > Breaking the system (really easy) > Also easy to recover > VI Bloat > Strippers, Whittlers > Incompatible changes > Tools for merging packages > > A Brief History > Flex and Smalltalk-72 > Simula, Sketchpad, Augment and other precursors > PARC Learning Research Group > Smalltalk-76 and the Xerox Alto > Mostly ASCII > Personal Dynamic Media Paper in "Computer" 3/1977 > Smalltalk-78 > Browser, NoteTaker project > Smalltalk-80 V1 > 3rd complete rewrite before they had an installed user base > LRG now Systems Concepts Lab > 1981 Byte Magazine Special Issue > Context: Xerox Alto, MIT LISP Machines > Smalltalk-80 V2 > Incorporated feedback from first-round users > MVC used for all GUIs > Late-80s changes > Exceptions and I/O > Host window system interface > DLLCC > Compiler Framework > Namespaces, Packages > ANSI Smalltalk (1993-98) > > Smalltalk Leaves PARC > Getting Smalltalk to Users > (Porting to non-Xerox hardware) > Early licensees: Apple, H-P, Tektronix > Tex 44404 demo - http://www.youtube.com/watch?v=8yxCJfayW-8 > Berkeley SOAR and SPARC design > XSIS and the Analyst > ParcPlace Systems (spun off in 1988) > Digitalk's Smalltalk/V on early PCs (1984) > These merge in 1995 > GNU Smalltalk (free) > > C++, ObjectiveC and Java > C with Classes - hybrid language; class is like a struct > ObjectiveC - C + Smalltalk in 1 program > Java ("what a shame they didn't copy everything.") > > Why it failed (in the 1990s) > Price (relative to what?) > Perception of compute demands (requires graphics and mouse, lots of RAM, â¦) > Performance Issues > VM performance and optimization > GC overhead and generation scavenging > Performance much better on Xerox machines > VM in microcode > Tagged architecture > Not upward compatible with anything > "Everything you know is wrong" > C hybrids appeared to get you most of the way thereâ¦ > > Smalltalk Implementations > Cincom Smalltalk (commercial) > ObjectStudio (commercial) > Squeak (free, based on Apple V1) > Pharo (stripped Squeak) > > Coral (for scripting) > Amber (runs on JavaScript VM) > Bistro (runs on JavaScript VM) > S# (runs with .NET) > > Smalltalk/X > VisualAge > Dolphin > > Smalltalk Today > DLLCC and Slang > Seaside (for web apps) > Gemstone (scalable OODB) > > STIC/ESUG > Smalltalk.org > Squeak community > > Relatives/Derivatives > ObjectiveC > Self (no classes, VM advances) > Lively (JavaScript libraries and tools) > F-Script > Strongtalk > SuperCollider > > Reasons Why I Still Use Smalltalk > 3 top reasons: Productivity, productivity and productivity > Language features > Simplicity, scalability, stability > Keyword syntax (!!) > Library features > Comprehensive, consistent, stable, extensible (!!) > All source close at hand > Pluggable L&F > Development Environment > Open tools (!!!) > Integrated, cross-platform > Fix/restart in debugger (!!!) > VI/VM architecture > Code lives in DB, easy change management, publication, crash recovery, etc. (!) > > Why I complain about other languages > "Object-Oriented is not Enough" (Goldberg & Pope 1989 article) > âThe Computer Revolution Hasnât Happened Yetâ (A Kay quote) > Issues center on libraries and tools rather than the languages themselves > Lively for JavaScript > ?? for Python > > What I do use (other than Smalltalk) > C++ > Standard, fast > XCode > Python > Hybrid language > Good libraries (inconsistent, non-OO) > Poor tools > Good integration with C/C++ via ctypes > Curse of version 3 > Octave/MATLAB > Terse, good matrix support > Extensive code base > > -- > > Stephen Travis Pope Santa Barbara, California, USA http://HeavenEverywhere.com > >

Jan. 6, 2013

Re: [Pharo-project] [ANN] NBOpenGL update

by Igor Stasenko

On 5 January 2013 21:41, Dan Corneanu <dan.corneanu(a)gmail.com> wrote: > Ok, I have fixed those problems but now I stumbled on other problems. > If I load the latest version > ConfigurationOfNBOpenGL project lastVersion load. > When I try to run the demo I get a SubscriptOutOfBounds:2083 exception at > NBOpenGLAPIBase>>emitCall: generator: > this looks strange. there should be no out of bound indexes by construction, since during automatic code generation, every unique GL function has assigned number and NBOpenGLAPIBase creates a variable-size object to hold all of them. > If I load version 1.0.2 > (ConfigurationOfNBOpenGL project version: '1.0.2') load. > and try the demo I get > 'Error: Frame buffer is incomplete: GL_FRAMEBUFFER_UNSUPPORTED' > in this message says for itself. sounds like your video driver does not supports the framebuffer in configuration which i intended to use. > NBGLFrameBuffer>>checkStatus > > By the way, I am on a windows machine. > > > On Sat, Jan 5, 2013 at 9:34 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: >> >> On 5 January 2013 11:29, Dan Corneanu <dan.corneanu(a)gmail.com> wrote: >> > Hello, >> > I have loaded the latest NBOpenGL into Pharo 1.4 but when I try >> > GLTTRenderingDemo new openInWorld. >> > I get a >> > SmallInteger(Object)>>doesNotUnderstand: #| >> > >> > What am I missing/doing wrong? >> > >> this is an extension method, which looks like i missed when splitting >> package.. >> it is synonym for #bitOr: >> >> > Best regards, >> > Dan. >> > >> > P.S. >> > There is also a typo in: >> > NBMacGLContextDriver >> supportsCurrentPlatform >> > "NativeBoostConstants mac32PlaformId" I think it should be >> > "NativeBoostConstants mac32PlatformId" >> > >> yes. >> Should fix it :) >> >> > >> > >> > On Fri, Apr 6, 2012 at 3:31 PM, Igor Stasenko <siguctua(a)gmail.com> >> > wrote: >> >> >> >> Hi there, >> >> >> >> for those, who interested, i updated a NBOpenGL configuration. >> >> >> >> Changes are: >> >> >> >> - updated GL API to most recent available (taken directly from opengl >> >> specs). Now there is about 300 more methods to explore :) >> >> - finally dealt with win32 support code and made it working again >> >> - fixed the GLX function prefix , which should be 'glX' not 'glx' >> >> >> >> To load it in 1.4 use: >> >> >> >> Gofer new >> >> squeaksource: 'NBOpenGL'; >> >> package: 'ConfigurationOfNBOpenGL'; >> >> load. >> >> >> >> >> >> and then >> >> >> >> (ConfigurationOfNBOpenGL project version: '1.0.2') load >> >> >> >> I did not tested the update thoroughly.. so i would appreciate if >> >> people will try it out and tell how it goes. >> >> >> >> >> >> -- >> >> Best regards, >> >> Igor Stasenko. >> >> >> > >> >> >> >> -- >> Best regards, >> Igor Stasenko. >> > -- Best regards, Igor Stasenko.

Jan. 5, 2013