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

Re: [Pharo-project] Pharo on Apple App Store

by StÃ©phane Ducasse

tx for the precision. >>> I'm not sure anyone really answered the question. >>> >>> (a) Yes you can build squeak/pharo VM based applications for the iOS platform and distribute in the App Store. This assumes you adhere to the rules. >>> >>> (b) Yes you can build Squeak/pharo VM based applications for the OS-X platform and distribute in the OS-X App Store. This assumes someone wants to take the time to port the file dialog logic from Sophie to Pharo since you will be rejected if you present a Squeak file open/save dialog. >>> >>> Thanks John. >>> >>> Is the licence of Sophie file dialog code MIT ? >> >> Yes but we do not really want to have the copyright of a university in pharo. This is why alain rewrote from scratch the undo. >> > Actually, the problem was that it is BSD... which is not the faullt of Sophie, this was what was thought as being good at that point > in time. Later people understood that MIT is even better... > > Wikepedia says: > > The MIT License is similar to the 3-clause "modified" BSD license, except that the BSD license contains a notice prohibiting the use of the name of the > copyright holder in promotion. This is sometimes present in versions of the MIT License, as noted above. > The original BSD license also includes a clause requiring all advertising of the software to display a notice crediting its authors. > This "advertising clause" (since disavowed by UC Berkeley[7]) is present in the modified MIT License used by XFree86. > > The MIT License states more explicitly the rights given to the end-user, including the right to use, copy, modify, merge, publish, distribute, sublicense, and/or > sell the software. > > For the Undo it was nor really worth to think about what it means to add BSD (and which of the BSD?) licensed code to an MIT licensed system... > > Marcus > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > >

March 5, 2011

Re: [Pharo-project] Monticello diff between 2 version

by StÃ©phane Ducasse

you click on open the repository select the package version press history use the menu select the version you want spawn select the latest something like that. Stef On Mar 5, 2011, at 7:55 PM, Miguel CobÃ¡ wrote: > Maybe I am not seeing it but: > > How do you see the changes between 2 version in a given repository in > Monticello? > > And then, how do you export it to a simple fileout or record them in a > change set. > > More specifically how can I extract the changes introduced by > > Collections-cmm.405.mcz > Collections-cmm.404.mcz > > in source.squeak.org/trunk > > Thanks > -- > Miguel CobÃ¡ > http://twitter.com/MiguelCobaMtz > http://miguel.leugim.com.mx > > > >

March 5, 2011

Re: [Pharo-project] Pharo on Apple App Store

by Marcus Denker

On Mar 5, 2011, at 7:53 PM, StÃ©phane Ducasse wrote: > > On Mar 5, 2011, at 12:14 PM, laurent laffont wrote: > >> On Sat, Mar 5, 2011 at 11:19 AM, John McIntosh <johnmci(a)smalltalkconsulting.com> wrote: >> I'm not sure anyone really answered the question. >> >> (a) Yes you can build squeak/pharo VM based applications for the iOS platform and distribute in the App Store. This assumes you adhere to the rules. >> >> (b) Yes you can build Squeak/pharo VM based applications for the OS-X platform and distribute in the OS-X App Store. This assumes someone wants to take the time to port the file dialog logic from Sophie to Pharo since you will be rejected if you present a Squeak file open/save dialog. >> >> Thanks John. >> >> Is the licence of Sophie file dialog code MIT ? > > Yes but we do not really want to have the copyright of a university in pharo. This is why alain rewrote from scratch the undo. > Actually, the problem was that it is BSD... which is not the faullt of Sophie, this was what was thought as being good at that point in time. Later people understood that MIT is even better... Wikepedia says: The MIT License is similar to the 3-clause "modified" BSD license, except that the BSD license contains a notice prohibiting the use of the name of the copyright holder in promotion. This is sometimes present in versions of the MIT License, as noted above. The original BSD license also includes a clause requiring all advertising of the software to display a notice crediting its authors. This "advertising clause" (since disavowed by UC Berkeley[7]) is present in the modified MIT License used by XFree86. The MIT License states more explicitly the rights given to the end-user, including the right to use, copy, modify, merge, publish, distribute, sublicense, and/or sell the software. For the Undo it was nor really worth to think about what it means to add BSD (and which of the BSD?) licensed code to an MIT licensed system... Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

March 5, 2011

Re: [Pharo-project] Kernel

by StÃ©phane Ducasse

On Mar 5, 2011, at 5:15 PM, Eliot Miranda wrote: > > > On Sat, Mar 5, 2011 at 12:12 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > Woot!!!!! Is this still a tracer or does it create a new kernel from source? If it's still a tracer when do you think you'll have a creator and what are you calling it? > > From source may be a way to go but only for the smallest core. > > Of course. From source one produces the smallest thing that can bring up the rest of the system. IMO, collections, numbers, compiler, files & a stdi/o read-eval-print loop. > > But form source is /vital/ to be able to produce a new object representation and that's absolutely necessary to improve performance. Using the tracer makes things like changing the bytecode set or replacing characters with immediate characters more difficult. There's also value in having a declarative definition of the core system. Yes. now our problem is not really to have a source code bootstrap for a smalltalk. Gwenael did that in 3 days for his smalltalk but he was controlling all the details (all his object have named and variable size) and only one kind. With Pharo we are reverse engineering format and other hardcoded knowledge with bitAnd: and bitshift: when it would have been so much simpler to have better names. So we will go there but first we should extract the knowledge from the mud. Stef > > > I would like to play with a source bootstrap. > For now we use a tracer and we should learn also how to build dynamically cores (like aljandro nurturing) > > Stef > > >

March 5, 2011

Re: [Pharo-project] [COTDC] - 24 DockingBarMorph

by StÃ©phane Ducasse

On Mar 5, 2011, at 3:55 PM, Tudor Girba wrote: > Until it gets obsolete :) indeed but better than nothing. > > Doru > > > On 5 Mar 2011, at 08:54, StÃ©phane Ducasse wrote: > >> I love the example in the comment >> >> On Mar 4, 2011, at 9:00 AM, laurent laffont wrote: >> >>> I'm a kind of container which adhere to one edge of the screen. See me in action with: >>> >>> >>> DockingBarMorph new >>> addMorph: (SimpleButtonMorph new >>> label: 'Say hello'; >>> target: [UIManager inform: 'Hello']; >>> actionSelector: #value); >>> addMorph: (SimpleButtonMorph new >>> label: 'Say bonjour'; >>> target: [UIManager inform: 'Bonjour']; >>> actionSelector: #value); >>> addMorph: (SimpleButtonMorph new >>> label: 'Close'; >>> target: [DockingBarMorph allInstances last delete]; >>> actionSelector: #value); >>> adhereToBottom; >>> openInWorld. >>> >>> >>> Laurent Laffont - @lolgzs >>> >>> Pharo Smalltalk Screencasts: http://www.pharocasts.com/ >>> Blog: http://magaloma.blogspot.com/ >>> >>> >>> On Thu, Mar 3, 2011 at 6:28 PM, laurent laffont <laurent.laffont(a)gmail.com> wrote: >>> Today: DockingBarMorph >>> >>> >>> Comment Of The Day Contest - One Day One Comment >>> Rules: >>> #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). >>> #2: If you cannot comment it, deprecate it. >>> Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest >>> >>> Laurent >>> >> >> > > -- > www.tudorgirba.com > > "Every successful trip needs a suitable vehicle." > > > > >

March 5, 2011

Re: [Pharo-project] Coral?

by StÃ©phane Ducasse

> What is coral all about? There seems to be no documentation except a little tutorial. But the tutorial does not make much sense to me. It explains the installation of coral and the result is that you can run a script from the commandline. Well, that is possible anyway. So where is coral located. Between positioning it as a shell replacement in the mailing list and the "just runs a shell script" is a huge space where it could be actually located. Any hints are appreciated. We want a scripting syntax to be able to builds script with pharo so we have coral. In coral you write Point >> mydistance [ ^ x * x ] Point class>>myNewPointWithx: anInt withY: another [ ] With OSProcess we access os behavior and yes I should fix the configurationOf... We have a more compact class creation syntax [ Object <| MyPoint iv: 'myx' "not sure that this is like that I'm watching a movie so not pharo " ] Stef > > Norbert > > > On 05.03.2011, at 08:58, StÃ©phane Ducasse wrote: > >> >> On Mar 4, 2011, at 2:17 PM, Alexandre Bergel wrote: >> >>> Hi! >>> >>> After I've tried Hazel, I was wondering what is the status of Coral. I would love to move away from Bash. >> >> me tooo. >> >>> I am just wondering. >> >> Use coral it is working. >> We should get more and more user. >> I'm waiting for after next week to introduce a better way to handle file.st, file.cor..... >> When hazel will be working we will use it but this is orhtogonal to Coral. >> >> We have documenting FS and we should improve it too. >> >> Luc told me that he remove the icon to get the start up faster >> Stef >> >>> >>> Cheers, >>> Alexandre >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >>> >>> >> >> > >

March 5, 2011

[Pharo-project] Monticello diff between 2 version

by Miguel CobÃ¡

Maybe I am not seeing it but: How do you see the changes between 2 version in a given repository in Monticello? And then, how do you export it to a simple fileout or record them in a change set. More specifically how can I extract the changes introduced by Collections-cmm.405.mcz Collections-cmm.404.mcz in source.squeak.org/trunk Thanks -- Miguel CobÃ¡ http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx

March 5, 2011

Re: [Pharo-project] Pharo on Apple App Store

by StÃ©phane Ducasse

On Mar 5, 2011, at 12:14 PM, laurent laffont wrote: > On Sat, Mar 5, 2011 at 11:19 AM, John McIntosh <johnmci(a)smalltalkconsulting.com> wrote: > I'm not sure anyone really answered the question. > > (a) Yes you can build squeak/pharo VM based applications for the iOS platform and distribute in the App Store. This assumes you adhere to the rules. > > (b) Yes you can build Squeak/pharo VM based applications for the OS-X platform and distribute in the OS-X App Store. This assumes someone wants to take the time to port the file dialog logic from Sophie to Pharo since you will be rejected if you present a Squeak file open/save dialog. > > Thanks John. > > Is the licence of Sophie file dialog code MIT ? Yes but we do not really want to have the copyright of a university in pharo. This is why alain rewrote from scratch the undo. Stef > > Laurent > > > Lastly you can't download MC packages to the app for doing on the fly updates, any updates have to go thru the app store. An example of alternate technology is Sparkle and Apple has rejected apps that use that technology to provide an update path. > > PS No I can't say I've actually attempted getting a squeak based app into the OS-X store, perhaps this summer, still that is my tea leaf reading of the situation. > > > On Fri, Mar 4, 2011 at 12:53 AM, laurent laffont <laurent.laffont(a)gmail.com> wrote: > Hi, > > is it possible today to distribute Pharo apps through Apple App Store (OSX) ? If no, why ? Can I hope it will be possible or should I learn objective-C ? > > > Laurent > > > > -- > =========================================================================== > John M. McIntosh <johnmci(a)smalltalkconsulting.com> > Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com > =========================================================================== > > > >

March 5, 2011

Re: [Pharo-project] LDAPlayer tutorial

by StÃ©phane Ducasse

I will read it and give you feedback On Mar 5, 2011, at 11:52 AM, Olivier Auverlot wrote: > Hi, > > I just published a little tutorial about LDAPlayer on my web site. It's a first draft in french. Translaters are welcome for english, binary or interstellar languages ;-) > > http://www.auverlot.fr/index.php?z=21 > > Best regards > Olivier

March 5, 2011

Re: [Pharo-project] Kernel

by Eliot Miranda

On Sat, Mar 5, 2011 at 12:12 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > > Woot!!!!! Is this still a tracer or does it create a new kernel from > source? If it's still a tracer when do you think you'll have a creator and > what are you calling it? > > From source may be a way to go but only for the smallest core. Of course. From source one produces the smallest thing that can bring up the rest of the system. IMO, collections, numbers, compiler, files & a stdi/o read-eval-print loop. But form source is /vital/ to be able to produce a new object representation and that's absolutely necessary to improve performance. Using the tracer makes things like changing the bytecode set or replacing characters with immediate characters more difficult. There's also value in having a declarative definition of the core system. > I would like to play with a source bootstrap. > For now we use a tracer and we should learn also how to build dynamically > cores (like aljandro nurturing) > > Stef > > >

March 5, 2011