- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Please review DrGeo

by Phil (list)

As far as I know, that's never been the policy (at least nothing I've read as a developer in the U.S. would indicate that... if you're elsewhere and are seeing a different policy that would be good to know.) If it were, developers also on the Amazon app store for example would have a problem. I agree that it may not be worth the effort since you could also put an apk download link on a website that would let the majority of the users who for whatever reason can't or don't want to use the Play Store use DrGeo (assuming you're not concerned about collecting revenue). I'll let others speak to the pros and cons of alternate markets and mainly wanted to pass along that you're not limited should one or more of them make sense for you or your users. Phil On Nov 13, 2012, at 3:42 PM, Hilaire Fernandes wrote: > I remember reading I can't distribute outside GooglePlay once published > there. Did Google change their policy? Need to be checked. > Anyway I am not sure it is worth the effort. I was fun to do but there > are too many rough edges. > > Hilaire > > Le 12/11/2012 05:32, Phil (list) a Ã©crit : >> Are you bound by agreements other than the Google Play TOS? The standard terms of service don't limit you regarding other distribution options: http://support.google.com/googleplay/android-developer/bin/answer.py?hl=en&… > > >

Nov. 16, 2012

[Pharo-project] [update 2.0] #20401

by Marcus Denker

20401 ----- Issue 6985: SytemWindow unused iVar allowReframeHandles http://code.google.com/p/pharo/issues/detail?id=6985 Issue 6984: DebuggerMethodMap should be defined by the Compiler... http://code.google.com/p/pharo/issues/detail?id=6984 Issue 6981: move ThreadSafeTranscript Morphic dependent methods to Polymorph http://code.google.com/p/pharo/issues/detail?id=6981 Diff information: http://ss3.gemstone.com/ss/Pharo20/Transcript-MarcusDenker.6.diff http://ss3.gemstone.com/ss/Pharo20/Polymorph-Widgets-MarcusDenker.728.diff http://ss3.gemstone.com/ss/Pharo20/Morphic-MarcusDenker.1282.diff http://ss3.gemstone.com/ss/Pharo20/Kernel-MarcusDenker.1250.diff http://ss3.gemstone.com/ss/Pharo20/Compiler-MarcusDenker.358.diff -- Marcus Denker -- http://marcusdenker.de

Nov. 16, 2012

Re: [Pharo-project] [update 2.0] #20400

by Marcus Denker

On Nov 16, 2012, at 2:01 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > I like the update number :P > :-) And Issue number 7000 is just 15 Issues away... Marcus > On 2012-11-16, at 16:03, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> 20400 >> ----- >> >> Issue 6975: move some RGMethodDefinition to Ring-Monticello package >> http://code.google.com/p/pharo/issues/detail?id=6975 >> >> Issue 6973: two ClassDescription>> #correspondingForTest issues >> http://code.google.com/p/pharo/issues/detail?id=6973 >> >> Issue 6970: Morphic dependency in checkBasicClasses >> http://code.google.com/p/pharo/issues/detail?id=6970 >> >> >> >> Diff information: >> http://ss3.gemstone.com/ss/Pharo20/Ring-Monticello-MarcusDenker.10.diff >> http://ss3.gemstone.com/ss/Pharo20/Ring-Core-Kernel-MarcusDenker.86.diff >> http://ss3.gemstone.com/ss/Pharo20/NautilusCommon-MarcusDenker.103.diff >> http://ss3.gemstone.com/ss/Pharo20/Nautilus-MarcusDenker.376.diff >> http://ss3.gemstone.com/ss/Pharo20/Kernel-MarcusDenker.1248.diff >> >> -- >> Marcus Denker -- http://marcusdenker.de >> >> > > -- Marcus Denker -- http://marcusdenker.de

Nov. 16, 2012

Re: [Pharo-project] [update 2.0] #20400

by Camillo Bruni

I like the update number :P On 2012-11-16, at 16:03, Marcus Denker <marcus.denker(a)inria.fr> wrote: > 20400 > ----- > > Issue 6975: move some RGMethodDefinition to Ring-Monticello package > http://code.google.com/p/pharo/issues/detail?id=6975 > > Issue 6973: two ClassDescription>> #correspondingForTest issues > http://code.google.com/p/pharo/issues/detail?id=6973 > > Issue 6970: Morphic dependency in checkBasicClasses > http://code.google.com/p/pharo/issues/detail?id=6970 > > > > Diff information: > http://ss3.gemstone.com/ss/Pharo20/Ring-Monticello-MarcusDenker.10.diff > http://ss3.gemstone.com/ss/Pharo20/Ring-Core-Kernel-MarcusDenker.86.diff > http://ss3.gemstone.com/ss/Pharo20/NautilusCommon-MarcusDenker.103.diff > http://ss3.gemstone.com/ss/Pharo20/Nautilus-MarcusDenker.376.diff > http://ss3.gemstone.com/ss/Pharo20/Kernel-MarcusDenker.1248.diff > > -- > Marcus Denker -- http://marcusdenker.de > >

Nov. 16, 2012

[Pharo-project] [^ 1] and ifCurtailed:

by StÃ©phane Ducasse

Hi guys I'm updating the exception chapter to show the interplay between exception and ensure/ifcurtailed: [[ ^ 1 ] ifCurtailed: [ Transcript show: 'show only curtailed'; cr. ]] on: Error do: [ :e | Transcript show: 'error'; cr. "do not show it" e return: 4 ]. normally shows that only the ifCurtailed: argument is executed. Now I do not get why when I select [^ 1] value and execute it I do not get an error telling me that there is no context to return to. May be because the evaluation itself creates a context. Stef

Nov. 16, 2012

[Pharo-project] [ANN] LZ4 Compressor binding for Pharo

by Mariano Martinez Peck

I better change the subject ;) On Fri, Nov 16, 2012 at 5:16 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > Hi guys. I wrote a Pharo binding for the LZ4 compressor. > If you are interested read here: > http://marianopeck.wordpress.com/2012/11/16/lz4-binding-for-pharo/ > And here: http://smalltalkhub.com/#!/~marianopeck/LZ4/ > > Cheers, > > -- > Mariano > http://marianopeck.wordpress.com > > -- Mariano http://marianopeck.wordpress.com

Nov. 16, 2012

[Pharo-project] LZ4 Compressor binding for Pharo

by Mariano Martinez Peck

Hi guys. I wrote a Pharo binding for the LZ4 compressor. If you are interested read here: http://marianopeck.wordpress.com/2012/11/16/lz4-binding-for-pharo/ And here: http://smalltalkhub.com/#!/~marianopeck/LZ4/ Cheers, -- Mariano http://marianopeck.wordpress.com

Nov. 16, 2012

[Pharo-project] Nautilus does not run test from superclass?

by Mariano Martinez Peck

Hi. I have a class XX that have some test methods. I have a subclass YYY that have some others. If I run the tests of YYY, the tests of XX are not run.... Even if YYY shouldInheritSelectors -> true Do I open an issue? -- Mariano http://marianopeck.wordpress.com

Nov. 16, 2012

[Pharo-project] [update 2.0] #20400

by Marcus Denker

20400 ----- Issue 6975: move some RGMethodDefinition to Ring-Monticello package http://code.google.com/p/pharo/issues/detail?id=6975 Issue 6973: two ClassDescription>> #correspondingForTest issues http://code.google.com/p/pharo/issues/detail?id=6973 Issue 6970: Morphic dependency in checkBasicClasses http://code.google.com/p/pharo/issues/detail?id=6970 Diff information: http://ss3.gemstone.com/ss/Pharo20/Ring-Monticello-MarcusDenker.10.diff http://ss3.gemstone.com/ss/Pharo20/Ring-Core-Kernel-MarcusDenker.86.diff http://ss3.gemstone.com/ss/Pharo20/NautilusCommon-MarcusDenker.103.diff http://ss3.gemstone.com/ss/Pharo20/Nautilus-MarcusDenker.376.diff http://ss3.gemstone.com/ss/Pharo20/Kernel-MarcusDenker.1248.diff -- Marcus Denker -- http://marcusdenker.de

Nov. 16, 2012

Re: [Pharo-project] [Pharo-users] CategorySaver

by Mariano Martinez Peck

On Mon, Nov 12, 2012 at 10:14 PM, Sebastian Nozzi <sebnozzi(a)gmail.com>wrote: > 2012/11/12 Fernando Olivero <fernando.olivero(a)usi.ch>: > > Sebastian, thanks for sharing your code and thoughts. > > Hey, you're welcome. > > > Maybe what Mariano was implying is that you already have the data for the > > backup in the changes, and having yet another mechanism for that adds > > complexity to the system. > > As I said, I think I should not have posted on "pharo project". No, it was perfect to publish here, so that we can discuss :) > I > didn't mean this as a contribution to the project per se, but to the > community (as a user, to the users). I am not suggesting for a second > that it should be part of the system. It's something I coded for me, > and wanted to share. > > And of course, everyone is free *not* to use it ;-) > But it is the opposite, I was asking to do the other way around: analyze whether we should include it in Pharo :) > > > I think is a good idea, but too focused on the categories you choose up > > front..and not on those actual changes you perform on the system. > > I would like to know how to ask the system what classes did I change. > But the only things I found took minutes to execute (asking every > class for its authors, or something like that). Very brute-fore. I'm > sure there is a better approach I am not aware of. > > > Which is why the recovering from the changes file is better. > > I don't see it as "which one is better". I am honoured that this was > interpreted as a serious theoretical "inclusion" as a Pharo feature, > with shortcomings or not :-) > :) Again, thanks for sharing this. I just wanted to know whether it makes sense to include it in Pharo. -- Mariano http://marianopeck.wordpress.com

Nov. 16, 2012