- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Stadistics about Pharo 1.0 ?

by Serge Stinckwich

What is really important is the number of new people in the mailing-list ! On Tue, Apr 20, 2010 at 1:51 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > so 2098 downloads of 1.0 one click :) > > Stef > > > On Apr 20, 2010, at 5:22 AM, Mariano Martinez Peck wrote: > >> Hi Marcus/Adrian. Can you tell us more or less stadistics from the Pharo 1.0 release ? Â people entering the website, downloading the image, the one click, PBE, etc ? >> >> thanks >> >> mariano >> _______________________________________________ >> 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 > -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/

April 20, 2010

Re: [Pharo-project] FFI in 1.1

by StÃ©phane Ducasse

The question is what we call core. I think that core should contain less and less but pharo should contain infrastructure and FFI or Alien are infrastructure. If you look at my answer to German on "Re: [Pharo-project] Really Important message (tm)" April 16 You can see that with a fast loading package mechanism then we could really introduce in "Pharo-Core" (= what we have now) infrastructure package to produce Pharo and works on making a real core. FFI does not belong to this core=mini but to Pharo from my point of view Mini Mini + FFI + Tools + IDE + Compiler ....= PharoCore Pharo + Sounds + Morphic examples + archiview.... = Pharo Note that the belonging of one package to group is not automatically clear. This is why metacello is key and a metacelloRepository. Steg >> I wouldn't include neither FFI or Alien FFI in neither PharoCore or PharoDev >> image. > > +1 > >> That's only my opinion. > > Maybe Stef should tell us more about why he thinks it should be included. > > Bye > T. > > -- > GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 20, 2010

Re: [Pharo-project] Wish List for Tests

by StÃ©phane Ducasse

http://code.google.com/p/pharo/issues/detail?id=2331 ;) On Apr 20, 2010, at 5:50 AM, Mariano Martinez Peck wrote: > > > On Fri, Apr 16, 2010 at 11:08 AM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > >> 2. When deleting all test cases using > >> > >> TestCase allSubclasses do: [:each | each removeFromSystem ] > >> > > > would be great to move all this stuff > > "unload all test packages" > #(Tests CollectionsTests CompilerTests FreeTypeTests GraphicsTests KernelTests MorphicTests MultilingualTests NetworkTests ToolsTest 'Gofer-Tests') > do: [ :each | (MCPackage named: each) unload ]. > > "unload SUnit" > Smalltalk at: #TestCase ifPresent: [ :class | > SystemChangeNotifier uniqueInstance noMoreNotificationsFor: class ]. > #(SUnitGUI SUnit) do: [ :each | (MCPackage named: each) unload ]. > AppRegistry removeObsolete. > TheWorldMenu removeObsolete. > > > to a method called unloadAllTestsAndSUnit > > so that it can be reused and not only in cleanUpForProduction > > cheers > > mariano > > >> I have also Monticello packages changed that are not in test > >> packages. > >> > >> Hope we find the time to clearly separate the tests from > >> the "core" package to clean unload the tests and continue > >> the modularization efforts. > > We have that already. I modularized the tests in PharoCore to make them cleanly unloadable. Do the following for unloading all tests from PharoCore (in ScriptLoader new>>cleanUpForProduction): > > #(Tests CollectionsTests CompilerTests FreeTypeTests GraphicsTests KernelTests MorphicTests MultilingualTests NetworkTests ToolsTest 'Gofer-Tests') do: [ :each | (MCPackage named: each) unload ]. > > If you run this in a Pharo image, it also does not leave any dirty packages, but obviously it does not remove the tests from external packages. To achieve this, the maintainers of external packages would need to separate the tests from the rest of their code. I don't think this is very important, though, because unloading tests is most important in PharoCore (that is, to strip down an image, you probably don't start from Pharo but PharoCore anyway). > > Cheers, > Adrian > _______________________________________________ > 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

April 20, 2010

Re: [Pharo-project] Stadistics about Pharo 1.0 ?

by StÃ©phane Ducasse

so 2098 downloads of 1.0 one click :) Stef On Apr 20, 2010, at 5:22 AM, Mariano Martinez Peck wrote: > Hi Marcus/Adrian. Can you tell us more or less stadistics from the Pharo 1.0 release ? people entering the website, downloading the image, the one click, PBE, etc ? > > thanks > > mariano > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 20, 2010

Re: [Pharo-project] FEATURE: User chooses preferred location for MC directory repositories

by StÃ©phane Ducasse

On Apr 20, 2010, at 1:00 AM, Sean P. DeNigris wrote: > > http://code.google.com/p/pharo/issues/detail?id=2329 > > Pharo image: Pharo 1.0 > > In Monticello Browser, when I click "+Repository" and select "directory," > I'd love to be taken right to the directory where I keep my local > repositories, instead of having to click to the same place over and over. > > I changed the following method: > MCDirectoryRepository class>>morphicConfigure > ^ (UIManager default chooseDirectoryFrom: (FileDirectory on: > '/path/to/my/Repositories')) ifNotNil: > [:directory | > self new directory: directory] > > How should I store the default repository directory? Would anyone else find > this helpful? it would be good to be able to either choose to have one local cache on the side of the image or one shared among image - this implies a way to store and set it up => probably a class variable + a setting in 1.1 > > Sean DeNigris > -- > View this message in context: http://n4.nabble.com/FEATURE-User-chooses-preferred-location-for-MC-directo… > 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

April 20, 2010

Re: [Pharo-project] Zoomable UI

by StÃ©phane Ducasse

This is strange that Juan does not mention that ESUG is sponsoring him. He will certainly fix that. I could not see ESUG mentioned on his web page. Stef On Apr 20, 2010, at 3:44 AM, David T. Lewis wrote: > On Mon, Apr 19, 2010 at 08:32:31PM +0300, Igor Stasenko wrote: >> This is where, i think we should be heading: >> >> http://ahead.com >> >> And this is why i think, a graphics frameworks should be vector based, >> not a pixel based one. > > Of course you know of Juan's work in this direction: > > http://www.jvuletich.org/Morphic3/Index.html > > Dave > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 20, 2010

[Pharo-project] FFI in 1.1

by Torsten Bergmann

>I wouldn't include neither FFI or Alien FFI in neither PharoCore or PharoDev >image. +1 >That's only my opinion. Maybe Stef should tell us more about why he thinks it should be included. Bye T. -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

April 20, 2010

Re: [Pharo-project] Issue 2330: BUG: After undo-ing all changes to code shown in OBrowser, it should not be marked as dirty

by Lukas Renggli

I don't think this has anything to do with OB, but with the ParagraphEditor. I guess this is solved with the new editors in Pharo 1.1. On 20 April 2010 01:11, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > http://code.google.com/p/pharo/issues/detail?id=2330 > > Pharo image: Pharo-1.0 #10517 > Virtual machine used: Squeak 4.2.4beta1U (Mac) > Class browser used (if applicable): Â OBSystemBrowserAdaptor > > Steps to reproduce: > 1. Â In code pane of OBSystemBrowser: > Â Â a. make a change to the code > Â Â b. undo the change > > The code pane is still marked dirty, even though it has now reverted the > original. > -- > View this message in context: http://n4.nabble.com/Issue-2330-BUG-After-undo-ing-all-changes-to-code-show… > 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 > -- Lukas Renggli www.lukas-renggli.ch

April 20, 2010

Re: [Pharo-project] Zoomable UI

by Douglas Brebner

On 19/04/2010 18:32, Igor Stasenko wrote: > This is where, i think we should be heading: > > http://ahead.com > > And this is why i think, a graphics frameworks should be vector based, > not a pixel based one. > > You may want to look at the papers on Pad++ which had a fair bit of information on ZUIs, including optimisation and navigation techniques, though I haven't looked at it for a long time. (I mention navigation because a ZUI desktop can be immense and easy to get lost in :)

April 20, 2010

Re: [Pharo-project] Minor GUI glitch with Pharo 1.0 on Mac

by Mariano Martinez Peck

http://code.google.com/p/pharo/issues/detail?id=1882 On Tue, Apr 20, 2010 at 4:53 AM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > It is already reported...sorry no time to search it in the bug tracker > > > On Thu, Apr 15, 2010 at 9:22 PM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > >> this is not a problem but reporting is the first step. >> Now I imagine that we should get a resize window event and react to it. >> On Apr 15, 2010, at 9:19 PM, Lawson English wrote: >> >> > StÃ©phane Ducasse wrote: >> >> Simple. >> >> - Enter a bug entry. >> >> - Say it in the mailing-list. >> >> - Send fix. >> >> >> >> Consider that Pharo is not our stuff but OUR stuff. >> >> >> >> Stef >> >> >> >> >> > >> > Sorry. Definitely did NOT want to seem like a critical non-contributor >> (though I am both, I'm afraid). >> > >> > At this point, I have no idea how to figure out what is wrong, letalone >> how to fix it. >> > >> > Lawson >> > >> > _______________________________________________ >> > 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 >> > >

April 20, 2010