February 2011 - Pharo-dev - lists.pharo.org

[Pharo-project] Render a COLLADA mesh with OpenGL

by HwaJong Oh

Hi, I'm working on parsing COLLADA file and then render it with AlienOpenGL in squeaksource. (AlienOpenGL was a good example of Alien BTW) http://forum.world.st/file/n3308632/%EC%8A%A4%ED%81%AC%EB%A6%B0%EC%83%B7_20… Has anyone done this before? I've seen KMZ file successfully load on OpenCobalt. Has anyone done it with Pharo(or Squeak)? Best Regards -- View this message in context: http://forum.world.st/Render-a-COLLADA-mesh-with-OpenGL-tp3308632p3308632.h… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Feb. 16, 2011

Re: [Pharo-project] New Squeaksource ...

by Janko MivÅ¡ek

Hi Jan, On 16. 02. 2011 12:18, Jan van de Sandt wrote: > Porting CloudforkSSO to AIDA should be pretty easy. The OAuth and OpenID > base classes use WAUrl and the JSON classes of Seaside. AIDA probably > has good alternatives for these. Good to know that! Another issue could be a portability. Aida is always up-to-date on Squeak/Pharo and VisualWorks thanks to a big care that all code is portable upfront. How is CloudFork portable, do you use or plan to use libraries like Sport for socket level portability? Best regards Janko > > Jan. > > On Wed, Feb 16, 2011 at 11:22 AM, Geert Claes <geert.wl.claes(a)gmail.com > <mailto:geert.wl.claes@gmail.com>> wrote: > > > > Janko MivÅ¡ek wrote: > > > > It would be nice to rebirth back past Squeak People into something > like > > Smalltalk People on http://people.world.st and use account there for > > single sign-on on all other Smalltalk websites, what do you think? > > > > We'd need that for our GSoC site for instance, to avoid that painful > > registration process needed to differentiate real Smalltalkers from > > spammers... > > > > I'm in favor of not have all these different accounts everywhere > hence why I > was excited to see Seaside supporting OAuth/OpenID so people can sign-up > with their Google/Yahoo/Twitter/Facebook etc accounts they already have. > Maybe the sso can be ported to AIDA as well? > > -- > View this message in context: > http://forum.world.st/New-Squeaksource-tp3308305p3308534.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > -- Janko MivÅ¡ek AIDA/Web Smalltalk Web Application Server http://www.aidaweb.si

Feb. 16, 2011

Re: [Pharo-project] New Squeaksource ...

by Jan van de Sandt

Hello, Porting CloudforkSSO to AIDA should be pretty easy. The OAuth and OpenID base classes use WAUrl and the JSON classes of Seaside. AIDA probably has good alternatives for these. Jan. On Wed, Feb 16, 2011 at 11:22 AM, Geert Claes <geert.wl.claes(a)gmail.com>wrote: > > > Janko MivÅ¡ek wrote: > > > > It would be nice to rebirth back past Squeak People into something like > > Smalltalk People on http://people.world.st and use account there for > > single sign-on on all other Smalltalk websites, what do you think? > > > > We'd need that for our GSoC site for instance, to avoid that painful > > registration process needed to differentiate real Smalltalkers from > > spammers... > > > > I'm in favor of not have all these different accounts everywhere hence why > I > was excited to see Seaside supporting OAuth/OpenID so people can sign-up > with their Google/Yahoo/Twitter/Facebook etc accounts they already have. > Maybe the sso can be ported to AIDA as well? > > -- > View this message in context: > http://forum.world.st/New-Squeaksource-tp3308305p3308534.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > >

Feb. 16, 2011

Re: [Pharo-project] [squeak-dev] Smalltalk string API

by Tobias Pape

Hi, Am 2011-02-16 um 10:24 schrieb Nicolas Cellier: > I started referencing Smalltalk idioms at > http://en.wikipedia.org/wiki/Comparison_of_programming_languages_(string_fu… > I could have focused on ANSI but have chosen Squeak/Pharo. Feel free > to correct me and to complete me. > > This is a very enlighting exercize, especially for pointing when API > turns to be not that bright. > During my perigrination, I notably noticed this: > > #compare: returns 1, 2, or 3 : this is both very object oriented, very > intuitive and very standard and the rest of the world is stupid, > unless... > > #findLastOccurrenceOfString:startingAt: in its current form is stupid > to my taste, because > 1) implementation is inefficient > 2) the startingAt: only skip the beginning of the string which seems > odd for a rfind operation > I would rather expect this kind of usage: > last := aString findLastOccurrenceOfString: 'to' startingAt: aString size. > lastButOne := aString findLastOccurrenceOfString: 'to' startingAt: last - 1. > > The CamelCase is sometimes abusive like #includesSubString: While Iâm with you in the preceding part, the following is incorrect: > > There is no format. I know, purists will tell me that encoding a > format in a cryptic string is not in the Smalltalk spirit, but please > then tell me how to specify a formatting efficiently and also remove > cryptic regex encoding (a pity, it's not in trunk). see String>>format: "format the receiver with aCollection simplest example: 'foo {1} bar' format: {Date today}. complete example: '\{ \} \\ foo {1} bar {2}' format: {12. 'string'}. " as well as the String>>expandMacros* methods. The latter seem more elaborate but unused, however. So Long, -Tobias

Feb. 16, 2011

Re: [Pharo-project] A new GUI visual designer

by GÃ¶ran Krampe

On 02/14/2011 11:14 AM, Craig Latta wrote: [SNIP] > This scheme is readable, editable, easy to store, and amenable to > framework change (the four things you were after). Thinking about this a bit more I realize one interesting aspect: Your stuff is basically low level serialization support - right? So... it all boils down to what kind of object model you pick. Now... come to think of it - readable and editable? Not sure how you mean there, counting the designer tool as the editor is kinda cheating :) But that was not what I was thinking about - you say that it is "amenable to framework change", and I just wrote that serialization generally is really bad for that. Thinking more closely, as I said, it boils down to the object model. On nice way to make a GUI description to be very robust against change is to let it be the representation of "a sequence of commands aimed at a builder API". Thus, the actual UI framework can change all it wants, as long as the builder API still works. So, if your object model is such a "command sequence" then I agree, it would be as robust as the same thing in Tirade. But... if your model is the actual built UI then I don't agree that it is as robust - supporting "migration" from one object model to a new one is kinda complex. Anyway, I was not really meaning to argue against Spoon - my main point was that representing a UI as a "recipe" for constructing it is probably the most robust way to do it. And isn't VW specs actually something like that? And the corollary is that representing UIs as "snapshots" of them when they are constructed (using serialization schemes) is IMHO not at all as robust. regards, GÃ¶ran

Feb. 16, 2011

Re: [Pharo-project] Issue 3707 in pharo: Syntax highlighting looks strange

by pharo＠googlecode.com

Comment #4 on issue 3707 by Benjamin...(a)gmail.com: Syntax highlighting looks strange http://code.google.com/p/pharo/issues/detail?id=3707 I just committed a new version of Shout with no more bold. But I'm not familiar with the old styling, so maybe one of you, "old" Smalltalker could have a look ;)

Feb. 16, 2011

[Pharo-project] [update 1.3] #13057

by StÃ©phane Ducasse

13057 ----- - Issue 3705: UI Enhancements. Thanks Gary Chambers. Stef

Feb. 16, 2011

Re: [Pharo-project] New Squeaksource ...

by Geert Claes

Janko MivÅ¡ek wrote: > > It would be nice to rebirth back past Squeak People into something like > Smalltalk People on http://people.world.st and use account there for > single sign-on on all other Smalltalk websites, what do you think? > > We'd need that for our GSoC site for instance, to avoid that painful > registration process needed to differentiate real Smalltalkers from > spammers... > I'm in favor of not have all these different accounts everywhere hence why I was excited to see Seaside supporting OAuth/OpenID so people can sign-up with their Google/Yahoo/Twitter/Facebook etc accounts they already have. Maybe the sso can be ported to AIDA as well? -- View this message in context: http://forum.world.st/New-Squeaksource-tp3308305p3308534.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Feb. 16, 2011

Re: [Pharo-project] New Squeaksource ...

by Geert Claes

Nicolas Petton wrote: > > ... > The reason is that we want to wait until we have a first prototype to show > to the community. We can't ask for feedbacks if we don't have anything to > show. > ... > Excellent Nicolas! I think a lot of people are just very keen for Smalltalk to have a cool, modern online code repository. I am not sure what features will be part of the initial prototype but I wanted to clarify that I just posted the "cloudforksso" link because I have a feeling that by having support for OAuth/OpenID as part of the Smalltalk code repository would be a positive reflection of Smalltalk being modern and open :) Anyhow, looking forward to seeing Iliad in action :) -- View this message in context: http://forum.world.st/New-Squeaksource-tp3308363p3308527.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Feb. 16, 2011

Re: [Pharo-project] Issue 3697 in pharo: UI Enhancements

by pharo＠googlecode.com

Comment #2 on issue 3697 by stephane...(a)gmail.com: UI Enhancements http://code.google.com/p/pharo/issues/detail?id=3697 it was in 13053 in fact

Feb. 16, 2011