- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Call for test: Dark Theme now ready (?) for integration

by phil＠highoctane.be

Did you fix the DiffMorph colors? The colorForType: thing. Le 15 mai 2014 18:20, "Esteban Lorenzano" <estebanlm(a)gmail.com> a Ã©crit : > no, noâ¦ is the same. You still need to merge :) > But if we have a âgood to goâ the idea is to integrate it. > > Esteban > > On 15 May 2014, at 18:15, kilon alios <kilon.alios(a)gmail.com> wrote: > > is the installation procedure exactly the same ? Do we still need to merge > ? > > this is what I use for installation > > â1. You need this because otherwise Gofer merge becomes dumb :P" > MCRepositoryGroup default > addRepository: (MCSmalltalkhubRepository > owner: 'estebanlm' > project: 'Pharo3DarkTheme'). > â2. Now we can actually MERGE the project" > Gofer it > smalltalkhubUser: 'estebanlm' project: 'Pharo3DarkTheme'; > package: 'Pharo3DarkTheme'; > merge. > â3. And then install it" > Pharo3DarkTheme installFullTheme. > > > On Thu, May 15, 2014 at 7:07 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > >> Hi, >> >> So I made a pass on the dark theme and I ensured it does not contains >> hacks and still works. And you can switch between themes without braking >> anything (but you need to restart all windows). >> How it works now? >> >> - I removed tons and tons of hardcoded colors all around image >> - I redirected defaults to values in theme >> - I fixed some buggy places >> >> So now it should be clean to include it in debut pharo4 (and maybe >> backport to pharo3, right now is not a problem). >> But I would want you to test it to be sure that is not breaking anything. >> >> thanks, >> Esteban >> > > >

May 15, 2014

Re: [Pharo-dev] Call for test: Dark Theme now ready (?) for integration

by Clara Allende

2014-05-15 18:13 GMT+02:00 Esteban A. Maringolo <emaringolo(a)gmail.com>: > So I load as I loaded the previous on Pharo 3, but this time no merge > will be required? > This time there weren't merge conflicts, if that's what you mean for "no merge required" Esteban, is that part of the fix? (Thanks if it is :D ) > > Regards! > Esteban A. Maringolo > > > 2014-05-15 13:07 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > > Hi, > > > > So I made a pass on the dark theme and I ensured it does not contains > hacks and still works. And you can switch between themes without braking > anything (but you need to restart all windows). > > How it works now? > > > > - I removed tons and tons of hardcoded colors all around image > > - I redirected defaults to values in theme > > - I fixed some buggy places > > > > So now it should be clean to include it in debut pharo4 (and maybe > backport to pharo3, right now is not a problem). > > But I would want you to test it to be sure that is not breaking anything. > > > > thanks, > > Esteban > >

May 15, 2014

Re: [Pharo-dev] 32 bits and 64 bits VM

by Esteban Lorenzano

so yesâ¦ I integrated the fix, created a pull request, waited until validationâ¦ and then I forget to merge :S it should be in process to build now. Esteban On 15 May 2014, at 10:44, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > damnâ¦ I was sure. I need to check now :) > > Esteban > > On 15 May 2014, at 09:21, Hilaire Fernandes <hilaire.fernandes(a)gmail.com> wrote: > >> Are you sure? >> Because VM fetched with "curl get.pharo.org/vmLatest | bash" has no >> working keypad. >> >> Hilaire >> >> Le 15/05/2014 00:46, Esteban Lorenzano a Ã©crit : >>> and is integrated but still not promoted to stable (I think it will be >>> next week). In the mean time, vmLatest will work. >>> >> >> -- >> Dr. Geo http://drgeo.eu >> >> >

May 15, 2014

Re: [Pharo-dev] Call for test: Dark Theme now ready (?) for integration

by Esteban Lorenzano

no, noâ¦ is the same. You still need to merge :) But if we have a âgood to goâ the idea is to integrate it. Esteban On 15 May 2014, at 18:15, kilon alios <kilon.alios(a)gmail.com> wrote: > is the installation procedure exactly the same ? Do we still need to merge ? > > this is what I use for installation > > â1. You need this because otherwise Gofer merge becomes dumb :P" > MCRepositoryGroup default > addRepository: (MCSmalltalkhubRepository > owner: 'estebanlm' > project: 'Pharo3DarkTheme'). > â2. Now we can actually MERGE the project" > Gofer it > smalltalkhubUser: 'estebanlm' project: 'Pharo3DarkTheme'; > package: 'Pharo3DarkTheme'; > merge. > â3. And then install it" > Pharo3DarkTheme installFullTheme. > > > On Thu, May 15, 2014 at 7:07 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi, > > So I made a pass on the dark theme and I ensured it does not contains hacks and still works. And you can switch between themes without braking anything (but you need to restart all windows). > How it works now? > > - I removed tons and tons of hardcoded colors all around image > - I redirected defaults to values in theme > - I fixed some buggy places > > So now it should be clean to include it in debut pharo4 (and maybe backport to pharo3, right now is not a problem). > But I would want you to test it to be sure that is not breaking anything. > > thanks, > Esteban >

May 15, 2014

Re: [Pharo-dev] Call for test: Dark Theme now ready (?) for integration

by kilon alios

is the installation procedure exactly the same ? Do we still need to merge ? this is what I use for installation â1. You need this because otherwise Gofer merge becomes dumb :P" MCRepositoryGroup default addRepository: (MCSmalltalkhubRepository owner: 'estebanlm' project: 'Pharo3DarkTheme'). â2. Now we can actually MERGE the project" Gofer it smalltalkhubUser: 'estebanlm' project: 'Pharo3DarkTheme'; package: 'Pharo3DarkTheme'; merge. â3. And then install it" Pharo3DarkTheme installFullTheme. On Thu, May 15, 2014 at 7:07 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > Hi, > > So I made a pass on the dark theme and I ensured it does not contains > hacks and still works. And you can switch between themes without braking > anything (but you need to restart all windows). > How it works now? > > - I removed tons and tons of hardcoded colors all around image > - I redirected defaults to values in theme > - I fixed some buggy places > > So now it should be clean to include it in debut pharo4 (and maybe > backport to pharo3, right now is not a problem). > But I would want you to test it to be sure that is not breaking anything. > > thanks, > Esteban >

May 15, 2014

Re: [Pharo-dev] Call for test: Dark Theme now ready (?) for integration

by Esteban A. Maringolo

So I load as I loaded the previous on Pharo 3, but this time no merge will be required? Regards! Esteban A. Maringolo 2014-05-15 13:07 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > Hi, > > So I made a pass on the dark theme and I ensured it does not contains hacks and still works. And you can switch between themes without braking anything (but you need to restart all windows). > How it works now? > > - I removed tons and tons of hardcoded colors all around image > - I redirected defaults to values in theme > - I fixed some buggy places > > So now it should be clean to include it in debut pharo4 (and maybe backport to pharo3, right now is not a problem). > But I would want you to test it to be sure that is not breaking anything. > > thanks, > Esteban

May 15, 2014

Call for test: Dark Theme now ready (?) for integration

by Esteban Lorenzano

Hi, So I made a pass on the dark theme and I ensured it does not contains hacks and still works. And you can switch between themes without braking anything (but you need to restart all windows). How it works now? - I removed tons and tons of hardcoded colors all around image - I redirected defaults to values in theme - I fixed some buggy places So now it should be clean to include it in debut pharo4 (and maybe backport to pharo3, right now is not a problem). But I would want you to test it to be sure that is not breaking anything. thanks, Esteban

May 15, 2014

Re: [Pharo-dev] Pharo Docs Generation

by Esteban Lorenzano

well.. current configuration is taking filetreeâ¦ we should do one using github. I do not have time right now, but feel free to implement :) Esteban On 15 May 2014, at 14:29, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Is there a configuration for it? If no, can we create one and put on meta repo? > > Uko > > On 15 May 2014, at 14:13, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> once installed, you can export doing something like this: >> >> (WebDocExporter packages: RPackageOrganizer default packages) exportTo: './doc' asFileReference. >> >> (that exports everything, you will need to select your own packages) >> >> Esteban >> >> On 15 May 2014, at 14:10, phil(a)highoctane.be wrote: >> >>> Awesome, I wondered how that was done in order to use it for my own things. >>> >>> >>> >>> >>> >>> On Thu, May 15, 2014 at 1:54 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> yes, >>> >>> https://github.com/estebanlm/pharo-webdoc >>> >>> is a filetree project so you need to clone repo into ./repository to make it work. >>> >>> cheers, >>> Esteban >>> >>> On 15 May 2014, at 13:41, Gabriel Cotelli <g.cotelli(a)gmail.com> wrote: >>> >>>> Hi, >>>> anybody knows how it's generated the online docs in pharodocs ?. >>>> >>>> Is there a package or script that can be applied to an specific set of packages? >>>> >>>> Thanks, Gabriel. >>> >>> >> >

May 15, 2014

Re: [Pharo-dev] SmalltalkHub username/password in environment variable?

by Yuriy Tymchuk

Thanks Mircea for improvement. Now there is indexible important piece of knowledge :) Uko On 15 May 2014, at 14:28, Mircea Filip Lungu <lungu(a)iam.unibe.ch> wrote: > Thanks Yuriy for the fast response! > > Your solution works, but only for the repos which are in the image. MCHTTPRepository>>userAndPasswordFromSettingsDo: already has machinery for using credentials. I posted an alternative solution that uses that machinery here: > > http://stackoverflow.com/a/23677314/1200070 > > @Phil: the code of Sean that you mentioned is maybe this: MCHTTPRepository>>userAndPasswordFromSettingsDo: > > M. > > > > 2014-05-15 11:50 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > Hi > > http://stackoverflow.com/questions/23673986/how-to-publish-to-smalltalkhub-… > > Uko > > On 14 May 2014, at 11:56, Mircea Filip Lungu <lungu(a)iam.unibe.ch> wrote: > >> Hi folks, >> >> Is there a way of setting the SmalltalkHub username and password in an environment variable or an external configuration file as opposed to setting them in every repository in every image? >> >> It gets old introducing them always :) >> >> Cheers, >> M. >> >> >> -- >> Mircea Lungu, PhD. >> Researcher >> Software Composition Group >> University of Bern >> > > > > > -- > Mircea Lungu, PhD. > Researcher > Software Composition Group > University of Bern >

May 15, 2014

Re: [Pharo-dev] Pharo Docs Generation

by Yuriy Tymchuk

Is there a configuration for it? If no, can we create one and put on meta repo? Uko On 15 May 2014, at 14:13, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > once installed, you can export doing something like this: > > (WebDocExporter packages: RPackageOrganizer default packages) exportTo: './doc' asFileReference. > > (that exports everything, you will need to select your own packages) > > Esteban > > On 15 May 2014, at 14:10, phil(a)highoctane.be wrote: > >> Awesome, I wondered how that was done in order to use it for my own things. >> >> >> >> >> >> On Thu, May 15, 2014 at 1:54 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> yes, >> >> https://github.com/estebanlm/pharo-webdoc >> >> is a filetree project so you need to clone repo into ./repository to make it work. >> >> cheers, >> Esteban >> >> On 15 May 2014, at 13:41, Gabriel Cotelli <g.cotelli(a)gmail.com> wrote: >> >>> Hi, >>> anybody knows how it's generated the online docs in pharodocs ?. >>> >>> Is there a package or script that can be applied to an specific set of packages? >>> >>> Thanks, Gabriel. >> >> >

May 15, 2014