May 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Pier Book tool

by Tudor Girba

Hi, Indeed, the Sitemap was only accessible for admins. It was my mistake. I fixed it. Now, when you are logged in as an editor, you should see the tree in the footer, with the children of the current structure expanded. Cheers, Doru On 20 May 2010, at 13:44, Lukas Renggli wrote: >>>>> The toolbar icon above the edit area lists the embeddable items. >>>> >>>> Listing the embeddable items would be good, how do you list the >>>> embeddable >>>> items? The link or embed buttons above the edit area don't do >>>> anything? >>> >>> Any structure (page, figure, component, ...) is embeddable. I guess >>> that when you log-in you get some kind of a navigation tree that >>> shows >>> the structure, no? >> >> There the TOC, and the TOC has a Table of Figures showing the >> images and >> their title but no way to find out the name, which you need to >> embed the >> image no? I would also like to remove images but I have no idea >> where I can >> do that. > > That has nothing to do with the TOC and TOF. There should be a tree > with the complete structure of the book after you login. Maybe you > don't see it because you don't have the access rights, I don't know. > Please ask your administrator. > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- www.tudorgirba.com "Every successful trip needs a suitable vehicle."

May 21, 2010

Re: [Pharo-project] Where should I put ConfigurationOfGLMorphic

by Igor Stasenko

2010/5/21 Javier PimÃ¡s <elpochodelagente(a)gmail.com>: > Hi, I made a very basic ConfigurationOfGLMorphic that manages it's > dependency on FFI. Where should I upload this configuration now? > Feel free to upload it into GLMorphic repository. > Regards, > Â Â Â Â Â Â Â Â Â Â Javier. > > -- > Javier PimÃ¡s > Ciudad de Buenos Aires > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

May 21, 2010

[Pharo-project] [BetaTesting] [ANN] Pharo-1.1-11367-Beta1dev10.05.1

by Torsten Bergmann

>Thanks Torsten. I wasn't aware of such package. So..for next release I will >add a project reference from ConfigurationOfPharo to >ConfigurationOfHelpSystem No, please just add the package I've mentioned since the ConfigurationOfHelpSystem was before the integration into Squeak/Pharo and would load old code. Meanwhile we had adaptions (we dont have the Squeak support code in Pharo for instance and vice versa). Maybe we should remove ConfigurationOfHelpSystem since it now adds more confusion. >It is not clear for me where Help packages should be hosted. For >example, ScriptManager host its own Help package in its own repository. >But Metacello is in the HelpSystem repository. The book for Metacello was just a demo - typically I would expect them to be in the same repo as the code. I dont want a "docu only" repo - if it is close to the code it will be easier to know and maintain it. Thx T. -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

May 21, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo-1.1-11367-Beta1dev10.05.1

by Serge Stinckwich

There is no warning when you try to access a monticello repository with a password and you enter the wrong password. The repository just look empty. 2010/5/21 Mariano Martinez Peck <marianopeck(a)gmail.com>: > Hi Pharaoers. I am pleased to announce the first Pharo 1.1 beta based on > PharoCore-1.1-11367-Beta. It is the first time we build a Pharo 1.1 dev > image with PharoCore 1.1 so the image may be not 100% stable. However, we > think it is good to release it so that people can start to test it, load > their own packages, adapt them, etc. We would like to receive feedback about > it. It (yet) has failing and error tests. > > The main changes with Pharo 1.0 is that of course, it is based on a > PharoCore 1.1 with all that it means. We started to write down some of the > actions done in PharoCore 1.1. The list so far can be found here: > http://code.google.com/p/pharo/wiki/ActionsInPharoOneDotOne > Of course, for the stable releae of Pharo 1.1 we will do a clear list in the > website as we did for 1.0. > > Regarding the included packages in 1.1 we added ScriptManager (a tool to > manage and persist workspaces), ProfStefBrowser, ArchiveViewer, > MethodWrappers and ObjectMetaTools (which includes things like > ProtocolCatcher, ObjectTracer, ObjectViewer, etc). > > Another difference is the font. In Pharo 1.0 we used TrueType fonts by > default. In Pharo 1.1 we use StrikeFonts (no need of TrueType plugin, > netiher to have the fonts). However, of course, you can disable StrikeFonts > and put TrueType like in 1.0. > > That's all. We would really appreciate you use it, test it, report issues, > provide fixes, etc. It is important also that you start to use your own > packages/applications. There have been several changes in 1.1 that may > require change in your code. > > Ahh if you want to create the image yourself, check as usually the > installScript.st file to see how to do it. Actually, you can just take a > PharoCore-1.1-11367-Beta image and evaluate (the same procedure as 1.0): > > Gofer new > Â Â Â squeaksource: 'MetacelloRepository'; > Â Â Â package: 'ConfigurationOfPharo'; > Â Â Â load. > > ((Smalltalk at: #ConfigurationOfPharo) project version: '1.1-beta1.10517') > load. > > Here is the link to the image: > > https://gforge.inria.fr/frs/download.php/27025/Pharo-1.1-11367-Betadev10.05… > > Cheers > > Mariano > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/

May 21, 2010

Re: [Pharo-project] MetaSource demo app working again

by Sean P. DeNigris

Torsten Bergmann wrote: > > It should be no problem when you put the ExternalBrowser code > package into another repo until you can copy it to the > original repo. > > But the ConfigurationOfXXX should be continued on > squeaksource/MetacelloRepository which is read/write. > > So the configuration can point to the temporary location until the > package moves to the original one - but others can still > use the newer versions in ConfigurationOfXXX since they dont > care where the loaded packages are hosted... > Perfect, that's what I wanted to know. Sean -- View this message in context: http://forum.world.st/MetaSource-demo-app-working-again-tp2225100p2225586.h… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

May 21, 2010

Re: [Pharo-project] FFI Documentation

by Sean P. DeNigris

Igor Stasenko wrote: > > NB Pros: > * as well as for plugin, you can create new > functionality that doesn't exist in any library > * no need to recompile plugin/VM when you making a changes > * all your code is distributed with the Smalltalk code, > but there can be > complications with platforms > * fast - faster than any FFI implementation written in > C, and as fast as plugin primitive or even faster > > Cons: > * ?unsafe? - you have to provide a safety layers > (But hey, you have to deal with same sorts of stuff, > when writing plugin. No magician workers there) > > * harder to write > Yes, its harder than plain smalltalk - true. > But i can't say, that writing an assembler is harder than writing a > plugin's slang code. > If you writing a plugin, you should have an expertise, in VM internals > and how to build VM , etc etc > and if you writing an native code, you should have an expertise in > assembler as well as VM internals. > > So, they are different, and definitely much harder comparing to plain > smalltalk code, > but which one is easier is hard to tell. > Cool, I'm glad you wrote that. I've been following your posts about NB, and from that quick summary, I already have a much better understanding of where it fits into the "external code" picture. Sean -- View this message in context: http://forum.world.st/FFI-Documentation-tp2225148p2225585.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

May 21, 2010

[Pharo-project] Where should I put ConfigurationOfGLMorphic

by Javier PimÃ¡s

Hi, I made a very basic ConfigurationOfGLMorphic that manages it's dependency on FFI. Where should I upload this configuration now? Regards, Javier. -- Javier PimÃ¡s Ciudad de Buenos Aires

May 21, 2010

Re: [Pharo-project] FFI Documentation

by Andreas Raab

On 5/20/2010 1:11 PM, Torsten Bergmann wrote: >> I want to get this info into the help system and/or collaborative book, as >> similar questions pop up regularly on the lists. > > Hi Sean, > > Here is the compiled book - see the attached MCZ. Just file it in. > If you continue with it it would be good to upload it > to the FFI repository at http://source.squeakfoundation.org/FFI Please do! Cheers, - Andreas

May 21, 2010

Re: [Pharo-project] FFI Documentation

by Igor Stasenko

Very nice topic coverage. I hope, eventually NB will also have something like this :) But it having a little different pros/cons table: NB Pros: * as well as for plugin, you can create new functionality that doesn't exist in any library * no need to recompile plugin/VM when you making a changes * all your code is distributed with the Smalltalk code, but there can be complications with platforms * fast - faster than any FFI implementation written in C, and as fast as plugin primitive or even faster Cons: * ?unsafe? - you have to provide a safety layers (But hey, you have to deal with same sorts of stuff, when writing plugin. No magician workers there) * harder to write Yes, its harder than plain smalltalk - true. But i can't say, that writing an assembler is harder than writing a plugin's slang code. If you writing a plugin, you should have an expertise, in VM internals and how to build VM , etc etc and if you writing an native code, you should have an expertise in assembler as well as VM internals. So, they are different, and definitely much harder comparing to plain smalltalk code, but which one is easier is hard to tell. On 20 May 2010 22:25, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > thanks sean > this is cool to see such kind of documentation emerging. > > Stef > > On May 20, 2010, at 9:16 PM, Sean P. DeNigris wrote: > >> >> I want to get this info into the help system and/or collaborative book, as >> similar questions pop up regularly on the lists. >> >> I compiled every piece of info I could find. Â The focus in on FFI, with >> stubs for other strategies. Â Please read this *very* rough outline for >> missing info and inaccuracies: >> >> FFI >> >> What is FFI and what is it used for? Â Calling functions in libraries outside >> of the image... >> >> FFI, the Squeak Foreign Function Interface, is used to call functions >> located in shared libraries that are not part of the Squeak VM nor its >> plugins. It also provides means to read and write memory structures that are >> associated with the use of those shared libraries. A typical use is to >> directly invoke operating system APIs. As such, applications that use FFI >> can only be used on the platform(s) that support the particular API being >> used. C conventions are used throughout, though the external function could >> have been written by any language capable of generating object code that >> follows C conventions. Â FFI is probably the easiest way to do the things it >> does. FFI is pretty fast too. Croquet uses FFI calls to OpenGL for all it's >> drawing routines.[1] >> >> How does FFI work? >> Technically what happens is: >> * you define what the interface is - the parameters, types etc. >> * when you make the call, the FFI logic assembles the data from the Squeak >> Objects into the proper structures according to the routine calling >> conventions for your architecture, and of course manages the return values. >> So no magic but perhaps just a little assembler in the plugin to properly >> deal with all the registers and condition flags. >> >> How do I use it? >> >> 1. make a method (whose structure is similar to a named primitive method) >> >> Example: >> system: aString "name (by convention is apiXxx: e.g. apiSystem:)" >> >> Â Â Â <apicall: long 'system' (char*) module: 'libSystem.dylib'> "first line >> should be the external function specification" >> Â Â Â ^self externalCallFailed. >> >> Let's take it piece by piece: >> >> Â Â Â system: aString >> Â Â Â Â Â Â Â Method name - by convention named 'apiXxx' >> >> Â Â Â <apicall: long 'system' (char*) module: 'libSystem.dylib'> >> Â Â Â Â Â Â Â Function specification >> Â Â Â Â Â Â Â Â Â Â Â - should be the first line >> Â Â Â Â Â Â Â Â Â Â Â - enclosed in angle brackets: < > containing: >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â 1. Calling Convention, either apicall: (Pascal convention) or cdecl: (C >> convention) >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â - Mac - use either one >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â - Unix - use cdecl >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â - Windows - use apical >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â 2. Return Type (see types) >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â 3. External Function Name (literal string) >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â 4. Argument Types (a literal array) >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â 5. Module - "module: " + [filename of the external library (literal >> string)] (see below). >> >> Â Â Â self externalCallFailed. >> Â Â Â Â Â Â Â Failure handler >> Â Â Â Â Â Â Â Â Â Â Â - normal smalltalk code >> Â Â Â Â Â Â Â Â Â Â Â - executed if the linking to or calling the external function fails >> Â Â Â Â Â Â Â Â Â Â Â - API calls don't know how to communicate failure like Squeak primitives >> do, so: >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â - it does not tell you whether the external function succeeded >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â - the most common code is simply '^self externalCallFailed.' >> >> Argument Types >> Â Â Â - must be names of ExternalTypes, either: >> Â Â Â Â Â Â Â - atomic types (see ExternalType class>>initializeFFIConstants and >> ExternalType class>>initializeAtomicTypes): >> Â Â Â Â Â Â Â Â Â Â Â void >> Â Â Â Â Â Â Â Â Â Â Â bool >> Â Â Â Â Â Â Â Â Â Â Â byte (unsigned) >> Â Â Â Â Â Â Â Â Â Â Â sbyte (signed) >> Â Â Â Â Â Â Â Â Â Â Â ushort (16-bit unsigned) >> Â Â Â Â Â Â Â Â Â Â Â short (16-bit signed) >> Â Â Â Â Â Â Â Â Â Â Â ulong (32-bit unsigned) >> Â Â Â Â Â Â Â Â Â Â Â long (32-bit signed) >> Â Â Â Â Â Â Â Â Â Â Â ulonglong (64-bit unsigned) >> Â Â Â Â Â Â Â Â Â Â Â longlong (64-bit signed) >> Â Â Â Â Â Â Â Â Â Â Â char (unsigned) >> Â Â Â Â Â Â Â Â Â Â Â schar (signed) >> Â Â Â Â Â Â Â Â Â Â Â float (single-precision float) >> Â Â Â Â Â Â Â Â Â Â Â double (double-precision float) >> >> Structure Types [4] >> Â Â Â - subclass of ExternalStructure >> Â Â Â Â Â Â Â - class>>fields that returns an array of field descriptions (see below) >> Â Â Â Â Â Â Â Â Â Â Â - Example: >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â fields >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â ^#((red Â 'byte')(green 'byte')(blue Â 'byte')) >> Â Â Â Â Â Â Â - class>>initialize which includes "self defineFields" (which must be >> called before using the class) >> Â Â Â - refer to as MyExternalStructure* (to indicate that the argument or return >> is a pointer to that structure) >> >> Field description [4] >> Â Â Â - 2-element array (or three but that does something else, I'm not sure >> what): >> Â Â Â Â Â Â Â - first element is the field name >> Â Â Â Â Â Â Â - second is the type >> >> Mac Memory Allocation Issues [4] (not sure about this) >> >> If you allocate external structures, those with memory outside the Squeak >> process space, you may need to increase the amount of memory that is >> reserved outside the object heap for such use. The Mac OS (9 and previous) >> needs this, other platforms may be able to dynamically get more memory from >> the OS. To see how much memory is currently reserved printIt 'Smalltalk >> extraVMMemory'. To change it, execute 'Smalltalk extraVMMemory: >> someNumberofBytes' Then save your image and quit. When you next start up, >> the amount of memory you requested will be reserved. (JMM) Note the OSX >> versions of the VM ignore extraVMMemory because the memory model for >> OS-X/unix applications is quite different. >> >> Module Name >> - depends on the platform >> Â Â Â - Mac >> Â Â Â Â Â Â Â - pre Snow Leopard: flexible, can eliminate leading lib or extension e.g. >> 'libc.dylib' becomes 'libc', 'c.dylib', or 'c' >> Â Â Â Â Â Â Â - Snow Leopard >> Â Â Â Â Â Â Â Â Â Â Â - file name must be exact including extension (unless Info.plist is >> altered as in 'Library Location' below) >> Â Â Â Â Â Â Â - With pre-mach-o VMs >> Â Â Â Â Â Â Â Â Â Â Â - For Classic applications, use 'InterfaceLib' >> Â Â Â Â Â Â Â Â Â Â Â - For Carbon libs, use 'CarbonLib' >> >> Module Location - where the external library file lives >> Â Â Â - depends on the platform >> Â Â Â Â Â Â Â - Mac >> Â Â Â Â Â Â Â Â Â Â Â - pre Snow Leopard >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â - checks VM path and common library paths >> Â Â Â Â Â Â Â Â Â Â Â - Snow Leopard >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â - only looks in VM bundle's Resources file, you must either [5]: >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â - store all external libraries there >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â - ln -s path/to/library path/to/VM/Resources/library_name >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â - Change the VM's Info.plist "SqueakPluginsBuiltInOrLocalOnly" key from >> "true" to "false." >> Caveats >> Â Â Â - security >> Â Â Â Â Â Â Â - malicious users could call arbitrary functions in the OS e.g. Â "format >> c:" from "system.dll" [7] >> Â Â Â Â Â Â Â - VMs do not protect against buffer overflow from bad parameters [8]: >> Â Â Â Â Â Â Â Â Â Â Â "this would require an attacker to execute arbitrary Smalltalk >> Â Â Â Â Â Â Â Â Â Â Â code on your server. Of course if they can do that they own you >> Â Â Â Â Â Â Â Â Â Â Â anyway, especially if you allow FFi or use the OSProcess plugin" - John >> McIntosh >> >> * difficulty >> Â Â Â - if you make a mistake you'll not drop into the debugger but Squeak will >> just crash [2] >> Â Â Â - If you crash Squeak when it is running the garbage collector, then you >> know your FFI code is leaking bits into object memory [2] >> >> What do I need to use FFI with Squeak? >> >> You need the FFI plugin, which is included with most VM's as of Squeak 3.6 >> or so. >> >> You can also build the plugin yourself. See VMMaker. >> >> References: >> [1] http://wiki.squeak.org/squeak/1414 >> [2] http://wiki.squeak.org/squeak/2424 >> [3] http://wiki.squeak.org/squeak/5716 >> [4] http://wiki.squeak.org/squeak/2426 >> [5] >> http://forum.world.st/squeak-dev-Alien-Squeak-FFI-issues-on-Snow-Leopard-td… >> [6] http://wiki.squeak.org/squeak/5846 >> [7] http://forum.world.st/FFI-Callbacks-td54056.html#a54073 >> [8] http://forum.world.st/Security-td99624.html#a99635: >> >> Other choices: >> In the fall of 2008, Alien the FFI interface (written by Cadence Design >> Systems, Inc.) was put into squeaksource: >> http://www.squeaksource.com/Alien.html. This API allows the primitive to >> call back to Smalltalk Code, and return error code information, and >> apparently is much faster due to a less complex call sequence. >> Â Â Â * if you need callbacks >> Â Â Â * mac-only? >> >> Plugins - write external code and dynamically link it to the VM >> Â Â Â Pros: >> Â Â Â Â Â Â Â * safest - users are limited to using the functionality you provide and >> can not call other external functions e.g. system rm / >> Â Â Â Â Â Â Â * fast - faster than FFI >> Â Â Â Â Â Â Â * you can create new functionality that doesn't exist in any library >> Â Â Â Cons: >> Â Â Â Â Â Â Â * harder to write >> Â Â Â Â Â Â Â * plugin must be distributed with the Smalltalk code - there can be >> complications with platforms >> >> Primitive method - invokes behavior in the VM or a plugin [3] >> >> Questions: >> * why would you want to build the FFI plugin yourself? >> * api prefix or no for method names? >> * not sure about pre Snow Leopard library search >> * OSProcess - how does this fit into the bigger picture? >> * "^self externalCallFailed." or "self externalCallFailed." i.e. return self >> or return the result, or doesn't matter? >> * why would a field description have three elements? >> * Mac Memory Allocation Issues? >> -- >> View this message in context: http://forum.world.st/FFI-Documentation-tp2225148p2225148.html >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> >> _______________________________________________ >> 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 > -- Best regards, Igor Stasenko AKA sig.

May 21, 2010

Re: [Pharo-project] Need your opinion: What is most appealing form for GL function bindings?

by Igor Stasenko

On 20 May 2010 21:51, Henrik Sperre Johansen <henrik.s.johansen(a)veloxit.no> wrote: > Â On 20.05.2010 17:47, Igor Stasenko wrote: >> >> There are multiple GL bindings exists by now >> - one that used by Croquet (FFI) >> - another one that using Alien >> >> and i doing one more, which using NativeBoost for callouts. >> >> And the question, what form of selectors you like most, >> pros/cons .. i need to know, because i can pick any of them, >> but i hope, that i will not be only one who using this stuff, so i >> need your opinion. >> >> Lets take a usual OpenGL function: >> >> void glVertex3f(GLfloat x, GLfloat y, GLfloat z) >> > For me, 3 + 6 seems the nicest, for the reasons you mentioned. > (method names starting in lower case though, so gl vertex3f_x: x y: y z: z). > Ok, with one exception, i think. For funtions which taking just a single argument, like: void glMatrixMode ( GLenum mode ) i think it would be better to not append an argument name i.e. gl matrixMode: foo instead of gl matrixMode_mode: foo Because in most cases, there is enough information about it from a function name itself, and argument name in selector just adds a noise: void glColor3fv ( GLfloat* v ) gl color3fv: foo instead of gl color3fv_v: foo > Cheers, > Henry > > PS. That particular method was deprecated in 3.0 and removed in 3.1 though, > right? ;) > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

May 20, 2010