September 2013 - Pharo-dev - lists.pharo.org

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=wi… 3 regressions found. SmartSuggestions.Test.SugsContextTest.testDebuggerIsAValidContext Tests.Release.ReleaseTest.testLocalMethodsOfTheClassShouldNotBeRepeatedInItsTraits ToolsTest.Debugger.DebuggerTest.testBasic

Sept. 22, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=li… 3 regressions found. SmartSuggestions.Test.SugsContextTest.testDebuggerIsAValidContext Tests.Release.ReleaseTest.testLocalMethodsOfTheClassShouldNotBeRepeatedInItsTraits ToolsTest.Debugger.DebuggerTest.testBasic

Sept. 22, 2013

[update 3.0] #30416

by Marcus Denker

30416 ----- 11645 missing visitSequence: method https://pharo.fogbugz.com/f/cases/11645 11646 Add Inspector Views / Types https://pharo.fogbugz.com/f/cases/11646 Camillo says: BAM! Inspectors just got a massive upgrade: - customizable subviews in the inspectors, by implementing #additionalInspectorClasses on the class which returns a collection of inspectors - by default: class-specific inspector + basic inspector - basic-inspector menu becomes obsolete (yet to be done) - switch between the inspector types via dropdown menu - shortcuts to navigate between the inspectors (CMD-0 .. CMD-9) - shortcut to get to the basic inspector (CMD-Shift-0) - shortcut to cycle between the inspectors (CMD-Shift-[ and CMD-Shift-]) - history is aware of selected inspector type - first basic integration of object explorer and view hierarchy (no dive support yet, should be rewritten using newer coding style) - more views on the way (namely for debugging views for AsmJit) - tree inspectors are no longer based on the tree explorer, but on the normal inspector infrastructure. Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Inspector-MarcusDenker.9… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Debugger-MarcusDenker.12… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Core-MarcusDenker.159.di… http://smalltalkhub.com/mc/Pharo/Pharo30/main/OpalCompiler-Core-MarcusDenke… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Nautilus-MarcusDenker.542.diff

Sept. 22, 2013

[update 3.0] #30415

by Marcus Denker

30415 ----- 11652 Undeclared variable in PluggableTextMorphWithLimits >> #acceptBasic https://pharo.fogbugz.com/f/cases/11652 11651 Filing testInstanceSideMethodsWithNilKeyInLastLiteral https://pharo.fogbugz.com/f/cases/11651 11629 Obsolete Class in the release: AnObsoleteKMCommandModifier https://pharo.fogbugz.com/f/cases/11629 11647 DropListModel >> #setSelectedItem: mixes up model, items and labels https://pharo.fogbugz.com/f/cases/11647 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Widgets-MarcusDenker.247… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Morphic-Base-MarcusDenker.114…

Sept. 22, 2013

Re: [Pharo-dev] About Morphic Documentation

by kilon

I agree 100% to fear the probability of image growing in size by 50 mbs is at best wishful thinking. Why ? Lets do the math. Taking a look at my word files shows me that 100kb files contains 25 pages that are 5000 words. You think 340 pages is alot ? Well if you do the math you will discover its nothing compared to 12.500 pages (for our american friends thats 12 thousands 500 pages) or 2,5 million (around 200 words per page) words of 50 mbs of documentation. And that could be even more depending on how much memory pharo consumes for regular text. Whos is going to write the first 1000 pages ? Dream on :D Plus I dont even think pharo would ever need such big documentation, at best I see 2-4 mbs growth in size for a 500-1000 pages documentation which should be more than fine and probably more than what most development enviroments out there can offer. Clearly Pharo is not far from this goal. The only problem is that we need to move this documentation inside the image (and potentially online and keeping supporting pdfs , latext etc ) and maybe polish it abit here and there and we will have accomplished a realistic goal. After that we can worry how to add up to 50 mbs of additional documentation. StÃ©phane Ducasse wrote >> Hi, >> >> Indeed. Having documentation on the web is nice for exposure, but we have >> to bring the documentation in the environment for reducing the context >> switch. >> >> As for the size, I would love to have the problem of having to remove >> 50MB of documentation from the image :) > > if only > :) > > But deep into pharo is 340 pages and Pharo for the entreprise starts to > get large already. > So if people would > - write good class comments > - tests with > testThisGuyShouldBehaveLike that > - participate to chapters > > then we have the documentation > but talking is so simpler :D > > stef > >> >> Doru >> >> >> >> On Sat, Sep 21, 2013 at 3:35 PM, Sean P. DeNigris < > sean@ > > wrote: >> ClÃ©ment Bera-4 wrote >> > the documentation would be on the web, available to anyone, >> > and each class / each package inside Pharo has a link towards its >> online >> > documentation. >> > This way the image size does not grow because of massive documentation. >> >> I agree that it would be nice for the docs to be on the web. But for me I >> would want that to be a mirror of what's available in the image. In >> general, >> I'd rather not context switch between the live, dynamic world of my image >> and a browser. Also, I don't think saving image size is enough of a >> benefit. >> Pharo is already tiny compared to other technologies, and the >> documentation >> would presumably be removed for production anyway. My 2c... >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: >> http://forum.world.st/if-Pharo-is-key-for-you-tp4708875p4709505.html >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> >> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" -- View this message in context: http://forum.world.st/if-Pharo-is-key-for-you-tp4708875p4709587.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 22, 2013

Re: [Pharo-dev] PostgresV2 overrides

by Esteban Lorenzano

yes, but in the mean time... working configuration should still be placed in: MetaRepoForPharo20 MetacelloRepository squeaksource/MetacelloRepository will not be really dead until we have a real replacement (like the catalog, who should automatize this collection) Esteban On Sep 22, 2013, at 9:06 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > We should really do something there. > > On Sep 22, 2013, at 2:42 AM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > >> >> >> >> On Sat, Sep 21, 2013 at 3:33 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >> 2013/9/21 Mariano Martinez Peck <marianopeck(a)gmail.com>: >> > >> > >> > >> > On Sat, Sep 21, 2013 at 3:03 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> >> > wrote: >> >> >> >> I loaded GlorpDBX configuration from the MetacelloRepository using: >> >> >> >> ((Smalltalk at: #ConfigurationOfGlorpDBX) >> >> project version: '2.5') load. >> >> >> >> ((Smalltalk at: #ConfigurationOfGlorpDBX) >> >> project version: '2.5') load: 'GlorpPostgresV2Native'. >> >> >> > >> > Esteban, in another thread you asked me how I was loading Native postgres >> > driver with Glorp. Like you have just figured out. But I am using last >> > version '2.8' >> >> There is no version 2.8 in the MetacelloRepository. >> >> Gofer it >> squeaksource: 'MetacelloRepository'; >> >> >> Squeaksource is dead, do not use it anymore. >> >> package: 'ConfigurationOfGlorpDBX'; >> load. >> >> Where do you get the latest ConfigurationOfGlorpDBX from? >> >> >> http://www.smalltalkhub.com/mc/DBXTalk/Configurations/main >> >> Regards, >> >> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >

Sept. 22, 2013

Re: [Pharo-dev] About Morphic Documentation

by StÃ©phane Ducasse

> Hi, > > Indeed. Having documentation on the web is nice for exposure, but we have to bring the documentation in the environment for reducing the context switch. > > As for the size, I would love to have the problem of having to remove 50MB of documentation from the image :) if only :) But deep into pharo is 340 pages and Pharo for the entreprise starts to get large already. So if people would - write good class comments - tests with testThisGuyShouldBehaveLike that - participate to chapters then we have the documentation but talking is so simpler :D stef > > Doru > > > > On Sat, Sep 21, 2013 at 3:35 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > ClÃ©ment Bera-4 wrote > > the documentation would be on the web, available to anyone, > > and each class / each package inside Pharo has a link towards its online > > documentation. > > This way the image size does not grow because of massive documentation. > > I agree that it would be nice for the docs to be on the web. But for me I > would want that to be a mirror of what's available in the image. In general, > I'd rather not context switch between the live, dynamic world of my image > and a browser. Also, I don't think saving image size is enough of a benefit. > Pharo is already tiny compared to other technologies, and the documentation > would presumably be removed for production anyway. My 2c... > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/if-Pharo-is-key-for-you-tp4708875p4709505.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Sept. 22, 2013

Re: [Pharo-dev] PostgresV2 overrides

by StÃ©phane Ducasse

We should really do something there. On Sep 22, 2013, at 2:42 AM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > > > On Sat, Sep 21, 2013 at 3:33 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > 2013/9/21 Mariano Martinez Peck <marianopeck(a)gmail.com>: > > > > > > > > On Sat, Sep 21, 2013 at 3:03 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> > > wrote: > >> > >> I loaded GlorpDBX configuration from the MetacelloRepository using: > >> > >> ((Smalltalk at: #ConfigurationOfGlorpDBX) > >> project version: '2.5') load. > >> > >> ((Smalltalk at: #ConfigurationOfGlorpDBX) > >> project version: '2.5') load: 'GlorpPostgresV2Native'. > >> > > > > Esteban, in another thread you asked me how I was loading Native postgres > > driver with Glorp. Like you have just figured out. But I am using last > > version '2.8' > > There is no version 2.8 in the MetacelloRepository. > > Gofer it > squeaksource: 'MetacelloRepository'; > > > Squeaksource is dead, do not use it anymore. > > package: 'ConfigurationOfGlorpDBX'; > load. > > Where do you get the latest ConfigurationOfGlorpDBX from? > > > http://www.smalltalkhub.com/mc/DBXTalk/Configurations/main > > Regards, > > > > > -- > Mariano > http://marianopeck.wordpress.com

Sept. 22, 2013

Re: [Pharo-dev] About Morphic Documentation

by Tudor Girba

Hi, Indeed. Having documentation on the web is nice for exposure, but we have to bring the documentation in the environment for reducing the context switch. As for the size, I would love to have the problem of having to remove 50MB of documentation from the image :) Doru On Sat, Sep 21, 2013 at 3:35 PM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > ClÃ©ment Bera-4 wrote > > the documentation would be on the web, available to anyone, > > and each class / each package inside Pharo has a link towards its online > > documentation. > > This way the image size does not grow because of massive documentation. > > I agree that it would be nice for the docs to be on the web. But for me I > would want that to be a mirror of what's available in the image. In > general, > I'd rather not context switch between the live, dynamic world of my image > and a browser. Also, I don't think saving image size is enough of a > benefit. > Pharo is already tiny compared to other technologies, and the documentation > would presumably be removed for production anyway. My 2c... > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/if-Pharo-is-key-for-you-tp4708875p4709505.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > -- www.tudorgirba.com "Every thing has its own flow"

Sept. 22, 2013

Re: [Pharo-dev] PostgresV2 overrides

by Mariano Martinez Peck

On Sat, Sep 21, 2013 at 3:33 PM, Esteban A. Maringolo <emaringolo(a)gmail.com>wrote: > 2013/9/21 Mariano Martinez Peck <marianopeck(a)gmail.com>: > > > > > > > > On Sat, Sep 21, 2013 at 3:03 PM, Esteban A. Maringolo < > emaringolo(a)gmail.com> > > wrote: > >> > >> I loaded GlorpDBX configuration from the MetacelloRepository using: > >> > >> ((Smalltalk at: #ConfigurationOfGlorpDBX) > >> project version: '2.5') load. > >> > >> ((Smalltalk at: #ConfigurationOfGlorpDBX) > >> project version: '2.5') load: 'GlorpPostgresV2Native'. > >> > > > > Esteban, in another thread you asked me how I was loading Native postgres > > driver with Glorp. Like you have just figured out. But I am using last > > version '2.8' > > There is no version 2.8 in the MetacelloRepository. > > Gofer it > squeaksource: 'MetacelloRepository'; > Squeaksource is dead, do not use it anymore. > package: 'ConfigurationOfGlorpDBX'; > load. > > Where do you get the latest ConfigurationOfGlorpDBX from? > > http://www.smalltalkhub.com/mc/DBXTalk/Configurations/main > Regards, > > -- Mariano http://marianopeck.wordpress.com

Sept. 22, 2013