- Pharo-dev - lists.pharo.org

[Pharo-project] Need your opinion: What is most appealing form for GL function bindings?
by Igor Stasenko May 21, 2010

May 21, 2010

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) A Croquet/FFI bindings translates it to a following selector: 1. glVertex3f: x with: y with: z An Alien bindings using following form: 2. glVertex3fX: x y: y z: z Since my bindings will definitely use underscores, its not a problem to use a following one: 3. glVertex3f_x: x y: y z: z Currently i using this one: 4. glVertex3f: x y: y z: z In private mail with Andreas, he proposed a following: --- The one thing I'd consider is to use #comma: as the 'standard' keyword instead of #with: for example: 5. glVertex3f: x comma: y comma: z The reason should be obvious; you're replacing the comma so it should be a little more clear than using #with:. --- 6. this option actually not about positional arguments, but about omitting the 'gl' prefix for each function name. It is because, you already typing gl at each invocation: gl glVertex3f: x with: y with: z so, maybe it worth to omit gl prefix, so, a code will look like: gl Vertex3f: x with: y with: z (sure thing, one may use different name for api interface object, not 'gl'.. but i think that in 99.9% cases, 'gl' is a natural choice). --- My own choice is [3]. As to me, it helps greatly when you coding, so, once you autocomplete the selector, you know what parameter you need at each position, unlike anonymous keywords, like with: or comma: , which don't telling you anything about arguments you end up browsing docs each time. Oh, and btw, each time you need to change something, you again may need to refer to docs, since it still may be not clear, what argument types a function expects even if you look at already working code. The pro for picking [1] is mainly be compatible with lots of Croquet code which using GL. Except that, in NB bindings, i taking a constant names as is , i.e. GL_LINES, while croquet uses GLLines. So, its still will require porting. P.S. i'm already having some stuff working (see attachment).. But i little bit hesistant to do more, because then , if i reconsider about selector names, it will require a lot of fixes all around places. It generating all these methods automatically, so i can change a form at any moment. NBOpenGL methodDict size 2063 NBWgl methodDict size 132 NBGlx methodDict size 121 -- Best regards, Igor Stasenko AKA sig.

4 7

Re: [Pharo-project] Pier Book tool
by Tudor Girba May 21, 2010

May 21, 2010

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."

2 3

[Pharo-project] Wrong password with Monticello repository [WAS] Re: [BetaTesting] [ANN] Pharo-1.1-11367-Beta1dev10.05.1
by Mariano Martinez Peck May 21, 2010

May 21, 2010

On Fri, May 21, 2010 at 10:35 AM, Serge Stinckwich < serge.stinckwich(a)gmail.com> wrote: > 2010/5/21 Mariano Martinez Peck <marianopeck(a)gmail.com>: > > > > > > On Fri, May 21, 2010 at 6:35 AM, Serge Stinckwich > > <serge.stinckwich(a)gmail.com> wrote: > >> > >> 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. > >> > > > > This this is wrong from my point of view. > > > > Anyway, wasn't it like that also in 1.0 ? can you check ? > > > > Yes same behavior with 1.0 > Ok...which should be the correct behavior ? I guess to throw an error saying that the user and password are incorrect. The problem is that I don't know if we can get that information from Monticello. Lukas do you know? Cheers Mariano > > -- > Serge Stinckwich > UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam > Every DSL ends up being Smalltalk > http://doesnotunderstand.org/ > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

1 0

[Pharo-project] Community Development (a suggestion)
by Sean P. DeNigris May 21, 2010

May 21, 2010

Since there is a major push in both Squeak and Pharo to be clear about what's loading where, and get more and more projects loadable; and the community is fixing projects that we don't own... I propose: 1. Everyone make your SqS repos globally writable unless you have a reason not to. 2. SqS admins, send an email to all the repo admins requesting this. Motivation: I've been fixing many projects as I try to load them, as a service to the community, but I am not necessarily taking on being responsible for their long-term maintenance. Right now, the process seems to be: 1. Upload fixes to my own repo 2. Email the project admin (if they are even still findable) 3. Post to the mailing lists with the new link 4. Wait for a response Not only is this more complicated than it has to be, but creates confusion. For example, I fixed ExternalWebBrowser to work in Pharo, but couldn't upload it to the project repo. Now I fixed the ConfigurationOf. Where do I put it? If I put it in the usual places, it will now point to my personal repository. It doesn't seem right to hijack someone else's project this way. And it's confusing for users - why are there two ExternalWebBrowsers and ConfigurationOfs on squeaksource? Thanks. Sean -- View this message in context: http://forum.world.st/Community-Development-a-suggestion-tp2224670p2224670.… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

3 6

[Pharo-project] MetaSource demo app working again
by Torsten Bergmann May 21, 2010

May 21, 2010

>I had fixed this and made a new ConfigurationOf, but I don't have write >access to the EWB repo, so they are both here: Hi Sean, The confusion came mostly from the fact that you also "rehosted" the config itself instead of just the code package. 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... Bye T. -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

2 1

[Pharo-project] FFI Documentation
by Torsten Bergmann May 21, 2010

May 21, 2010

>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 We can then also add it to the ConfigurationOfFFI. Thx T. -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

2 1

[Pharo-project] Fwd: [squeak-dev] Finalization enhancement for 4.2
by StÃ©phane Ducasse May 20, 2010

May 20, 2010

igor I have a question about your new finalization. Can we add it to Pharo? Should we replace something else (I mean it is something to replace an existing solution). How does it interact with existing code? You see I will learn a lot again :) Stef > From: "David T. Lewis" <lewis(a)mail.msen.com> > Date: May 20, 2010 5:59:07 PM GMT+02:00 > To: ma.chris.m(a)gmail.com, The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org> > Cc: vm-dev(a)lists.squeakfoundation.org > Subject: Re: [squeak-dev] Finalization enhancement for 4.2 > Reply-To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org> > > CC to vm-dev list, follow up on technical issues should go to vm-dev. > > Chris, Igor, this sounds very encouraging. Yes, I'll help on the > VM side, with guidance from Andreas and others (I am not technically > competent on this issue). I'll probably be off list for a few days, > but will catch up on this next week. > > Andreas, Eliot, others - any advice or guidance? > > Dave > > On Thu, May 20, 2010 at 10:14:00AM -0500, Chris Muller wrote: >> I have packaged up Igor's change-sets for the finalization fix: >> >> http://bugs.squeak.org/view.php?id=7525 >> http://bugs.squeak.org/view.php?id=7473 >> >> into their respective MC packages and uploaded them to the Inbox. >> >> Recall the original discussion: >> >> http://lists.squeakfoundation.org/pipermail/vm-dev/2010-March/003958.html >> >> I have been running with Igor's enhanced VM and image-side >> finalization patches for a few weeks now. The results are striking. >> Squeak applications using large Weak-collections deteriorate to a >> point of unusability without this fix because Squeak spends 95% of its >> time in the finalization process, leaving no time for application >> processing. With this fix installed, CPU utilization is 0% when the >> application is idle, providing excellent responsiveness. >> >> This is a big, big, win for any application that uses Weak >> collections, and a win for Squeak overall because it's own use of >> weak-collections is enhanced. >> >> While it seems to be backward compatible, e.g. I am able to run the >> enhanced VM on older images (including 3.9), and I am able to run with >> these image changes on an older VM, both are required to take >> advantage of the enhanced finalization. >> >> I would like to push this into the trunk, but will need help from the >> VMMaker developers for that piece. David? >> >> For Magma, this wil be the most exciting and important fix since >> #becomeForward:copyHash: introduced back in 2004. >> >> - Chris >

2 1

[Pharo-project] Where to host Help packages?
by Mariano Martinez Peck May 20, 2010

May 20, 2010

Hi Torsten. 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. So....where should I host them ? or what is the convention? in their own repositories or in HelpSystem ? Cheers Mariano

1 0

[Pharo-project] [BetaTesting] [ANN] Pharo-1.1-11367-Beta1dev10.05.1
by Torsten Bergmann May 20, 2010

May 20, 2010

Maybe you should include "Pharo-Project-Help" MCZ package from squeaksource.com/HelpSystem into the ConfigurationOfPharo. While the core image only has the basic help support and only one topic ("Help on Help) the dev image would then have some basic infos on Pharo itself as well as the browsable API for Pharo accessible from the help browser (if this is loaded). Do we have a ghostwriter who wants to help on this package? Thx T. -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

2 1

May 20, 2010

Begin forwarded message: > From: Joachim Geidel <joachim.geidel(a)onlinehome.de> > Date: May 20, 2010 6:31:51 PM GMT+02:00 > To: <pharo-users(a)lists.gforge.inria.fr> > Subject: [Pharo-users] Flushing the VM method cache? > Reply-To: A friendly place where any question about pharo is welcome <pharo-users(a)lists.gforge.inria.fr> > > Hello all, > > The software I am working on generates classes on the fly, and discards > those classes when they are no longer needed. The class library is > cross-platform, i.e. it exists for Dolphin and VisualWorks, and I am > currently porting it to Pharo. > > In Dolphin, it is necessary to flush the VM's method cache after discarding > all the dynamically generated classes, because the method cache holds > references to the classes which prevent them from being garbage collected. > For VisualWorks, I have adopted this, although I am not quite sure if it's > actually needed there. > > In the Pharo 1.0 image, I haven't found a method for flushing the VM's > method cache in one go, there only seems to be Behavior>>flushCache. > > What I would like to know is: > - Does the VM method cache of the Squeak VM hold references to classes which > prevent an obsolete class from being garbage collected? If this is not the > case, I don't need to flush anything. > - If flushing the cache is advisable, is Behavior>>flushCache the only way > to do this? I would have to pick up all the obsolete classes and iterate > over them in that case. > > Thanks in advance! > Joachim Geidel > > > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users

2 2