- Pharo-dev - lists.pharo.org

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

Re: [Pharo-dev] Spec Examples

by Benjamin

Yes, something like this :) Ben On Sep 21, 2013, at 9:17 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > > On 2013-09-21, at 16:11, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > >> What should be done is to first create some methods on ComposableModel like instantiateListModel, instantiateTextModel, etc so you hide at maximum the implementation details, and then you can do a more generic "self instantiate: MethodBrowser." >> >> The first version of Spec was like this: >>> listModel := self instantiate: ListComposableModel. >>> methodModel := self instantiate: MethodBrowser. >> >> But then you find out there is always the same pattern, so Johan and I decided to introduce a way to encapsulate this. >> >> Then of course, do whatever you want :P > > actually true, something short like newButton / newList / newText ?

Sept. 21, 2013

Re: [Pharo-dev] Spec Examples

by Camillo Bruni

On 2013-09-21, at 16:11, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > What should be done is to first create some methods on ComposableModel like instantiateListModel, instantiateTextModel, etc so you hide at maximum the implementation details, and then you can do a more generic "self instantiate: MethodBrowser." > > The first version of Spec was like this: >> listModel := self instantiate: ListComposableModel. >> methodModel := self instantiate: MethodBrowser. > > But then you find out there is always the same pattern, so Johan and I decided to introduce a way to encapsulate this. > > Then of course, do whatever you want :P actually true, something short like newButton / newList / newText ?

Sept. 21, 2013

Re: [Pharo-dev] Spec Examples

by Benjamin

On Sep 21, 2013, at 7:35 PM, Erwan Douaille <douailleerwan(a)gmail.com> wrote: > Since UIPainter, example aren't needed :p euhhhhhhhh :P Ben > > Another way, than i like, is create a method for a model. > > Class>>listModel > listModel ifNil: [ listModel := self instantiate: ListModel. and options ]. > ^ listModel > > And do nothing in initializeWidgets > > > 2013/9/21 Camillo Bruni <camillobruni(a)gmail.com> > Can I rewrite all spec examples from > > self instantiateModels: #( > listModel ListComposableModel > methodModel MethodBrowser ). > > to the more explicit form: > > listModel := self instantiate: ListComposableModel. > methodModel := self instantiate: MethodBrowser. > > > > > > -- > Best regards, > > Douaille Erwan <douaille.erwan(a)gmail.com>

Sept. 21, 2013

Re: [Pharo-dev] Spec Examples

by Benjamin

What should be done is to first create some methods on ComposableModel like instantiateListModel, instantiateTextModel, etc so you hide at maximum the implementation details, and then you can do a more generic "self instantiate: MethodBrowser." The first version of Spec was like this: > listModel := self instantiate: ListComposableModel. > methodModel := self instantiate: MethodBrowser. But then you find out there is always the same pattern, so Johan and I decided to introduce a way to encapsulate this. Then of course, do whatever you want :P Ben On Sep 21, 2013, at 7:29 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > Can I rewrite all spec examples from > > self instantiateModels: #( > listModel ListComposableModel > methodModel MethodBrowser ). > > to the more explicit form: > > listModel := self instantiate: ListComposableModel. > methodModel := self instantiate: MethodBrowser. > >

Sept. 21, 2013

Re: [Pharo-dev] PostgresV2 overrides

by Esteban A. Maringolo

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'; package: 'ConfigurationOfGlorpDBX'; load. Where do you get the latest ConfigurationOfGlorpDBX from? Regards,

Sept. 21, 2013

Re: [Pharo-dev] PostgresV2 overrides

by Mariano Martinez Peck

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' > But the PostgresV2 package basically f*cks up the DateAndTime class > overriding #julianDayNumber and #offset: > > Is this normal behavior? I'm loading a vanilla 2.0 image to see if > this also happens there. > > Try version 2.8 and check if it happens the same. > > > > Esteban A. Maringolo > > -- Mariano http://marianopeck.wordpress.com

Sept. 21, 2013

Re: [Pharo-dev] Spec Examples

by Camillo Bruni

On 2013-09-21, at 14:35, Erwan Douaille <douailleerwan(a)gmail.com> wrote: > Since UIPainter, example aren't needed :p > > Another way, than i like, is create a method for a model. > > Class>>listModel > listModel ifNil: [ listModel := self instantiate: ListModel. and options > ]. > ^ listModel > > And do nothing in initializeWidgets yeah I saw that you did that for the InspectorToolbar and I like this approach since you group all the settings for a specific widget in a single method. I remember vaguely that the UI framework under NetBeans did these kind of methods in Java...

Sept. 21, 2013

PostgresV2 overrides

by Esteban A. Maringolo

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'. But the PostgresV2 package basically f*cks up the DateAndTime class overriding #julianDayNumber and #offset: Is this normal behavior? I'm loading a vanilla 2.0 image to see if this also happens there. Esteban A. Maringolo

Sept. 21, 2013