- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] TClassDescription: Why #comment:?

by Sean P. DeNigris

Marcus Denker-4 wrote > Yes, we had in the past the problem that comments lost the stamps oftenâ¦ > I wanted to remove all cases where it puts > <historical> Okay, I created Issue 15389 "Class Comments: Never Create <historical> Stamps" Marcus Denker-4 wrote > Hmm.. strange. Maybe the notification is not done correctly? I'm having trouble reproducing it. Let's assume it was a fluke for now... ----- Cheers, Sean -- View this message in context: http://forum.world.st/TClassDescription-Why-comment-tp4821441p4821461.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 23, 2015

Re: [Pharo-dev] TClassDescription: Why #comment:?

by Marcus Denker

> On 23 Apr 2015, at 16:45, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Sean P. DeNigris wrote >> When would we want that? > > And, AFAICT there are senders (out of the 24 total) who should be using the > stamp version - FileContentsBrowser>>#contents:notifying:, this will soon go away thankfullyâ¦ > AbstractNautilusUI>>#openCommentEditor:... > a comment: that sets a good default stamp should be good here, too, or not? Marcus

April 23, 2015

Re: [Pharo-dev] TClassDescription: Why #comment:?

by Marcus Denker

> On 23 Apr 2015, at 16:30, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > There is already #comment:stamp:. #comment: makes the stamp <historical>. > When would we want that? Or if it's a convenience method, maybe it should > pass `... stamp: Author changeStamp`? > Yes, we had in the past the problem that comments lost the stamps oftenâ¦ I wanted to remove all cases where it puts <historical> > Also, it seems that the result of neither of these messages shows up in MC > changes browser, even though they do go into the changes file and are > committed by MC... > Hmm.. strange. Maybe the notification is not done correctly? Marcus

April 23, 2015

Re: [Pharo-dev] TClassDescription: Why #comment:?

by Sean P. DeNigris

Sean P. DeNigris wrote > When would we want that? And, AFAICT there are senders (out of the 24 total) who should be using the stamp version - FileContentsBrowser>>#contents:notifying:, AbstractNautilusUI>>#openCommentEditor:... ----- Cheers, Sean -- View this message in context: http://forum.world.st/TClassDescription-Why-comment-tp4821441p4821442.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 23, 2015

TClassDescription: Why #comment:?

by Sean P. DeNigris

There is already #comment:stamp:. #comment: makes the stamp <historical>. When would we want that? Or if it's a convenience method, maybe it should pass `... stamp: Author changeStamp`? Also, it seems that the result of neither of these messages shows up in MC changes browser, even though they do go into the changes file and are committed by MC... ----- Cheers, Sean -- View this message in context: http://forum.world.st/TClassDescription-Why-comment-tp4821441.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 23, 2015

Re: [Pharo-dev] Updated WebDoc

by Esteban Lorenzano

orâ¦ with better naming: http://files.pharo.org/doc/4.0 <http://files.pharo.org/doc/4.0> http://files.pharo.org/doc/3.0 <http://files.pharo.org/doc/3.0> Esteban > On 23 Apr 2015, at 16:15, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > Quick answer, no. > > More elaborate one: > > The exports of the full pharo release (versions 3.0 and 4.0) exist and were created by Esteban manually before each release. These, are hosted here > > http://file-pharo.inria.fr/doc/4.0 <http://file-pharo.inria.fr/doc/4.0> > http://file-pharo.inria.fr/doc/3.0 <http://file-pharo.inria.fr/doc/3.0> > > We could run it automatically every day with latest pharo to avoid the manual steps. I'll add that into my todo and check it later ^^. > > > El jue., 23 de abr. de 2015 a la(s) 4:09 p. m., Sven Van Caekenberghe <sven(a)stfx.eu <mailto:sven@stfx.eu>> escribiÃ³: > Great! Thank you. > > And the full image export, is that somewhere (done automatically) ? > > > On 23 Apr 2015, at 15:56, Guillermo Polito <guillermopolito(a)gmail.com <mailto:guillermopolito@gmail.com>> wrote: > > > > Hi guys, > > > > I started yesterday to update WebDoc to work on latest Pharo. I share with you my progress since yesterday: > > > > - Now it loads in latest pharo4 :) > > - fixed javascript errors and render issues > > - a little of love to the css styles > > - removed unused/not working features > > - made it work well when exporting not the full image > > - ci job is again green [1] > > > > you can see the result of applying webdoc to webdoc as the result of the ci job here [2]. If you use it further, you'll see there are still of course some problems, but I feel it is better than before :). > > > > If you want to check it out, instructions in [3]. > > Download: > > > > Gofer it > > smalltalkhubUser: 'PharoExtras' project: 'WebDoc'; > > package:'ConfigurationOfWebDoc'; > > load. > > > > (#ConfigurationOfWebDoc asClass project version: #development) load. > > > > Export: > > (WebDocExporter packages: {RPackageOrganizer default packageNamed: 'YourProject'}) > > title: 'YourProject'; > > exportTo: './doc' asFileReference. > > > > > > Guille > > > > [1] https://ci.inria.fr/pharo-contribution/job/WebDoc/ <https://ci.inria.fr/pharo-contribution/job/WebDoc/> > > [2] https://ci.inria.fr/pharo-contribution/job/WebDoc/PHARO=40,VERSION=developm… <https://ci.inria.fr/pharo-contribution/job/WebDoc/PHARO=40,VERSION=developm…> > > [3]http://www.smalltalkhub.com/#!/~PharoExtras/WebDoc <http://www.smalltalkhub.com/#!/~PharoExtras/WebDoc> > >

April 23, 2015

Re: [Pharo-dev] Updated WebDoc

by Guillermo Polito

Quick answer, no. More elaborate one: The exports of the full pharo release (versions 3.0 and 4.0) exist and were created by Esteban manually before each release. These, are hosted here http://file-pharo.inria.fr/doc/4.0 http://file-pharo.inria.fr/doc/3.0 We could run it automatically every day with latest pharo to avoid the manual steps. I'll add that into my todo and check it later ^^. El jue., 23 de abr. de 2015 a la(s) 4:09 p. m., Sven Van Caekenberghe < sven(a)stfx.eu> escribiÃ³: > Great! Thank you. > > And the full image export, is that somewhere (done automatically) ? > > > On 23 Apr 2015, at 15:56, Guillermo Polito <guillermopolito(a)gmail.com> > wrote: > > > > Hi guys, > > > > I started yesterday to update WebDoc to work on latest Pharo. I share > with you my progress since yesterday: > > > > - Now it loads in latest pharo4 :) > > - fixed javascript errors and render issues > > - a little of love to the css styles > > - removed unused/not working features > > - made it work well when exporting not the full image > > - ci job is again green [1] > > > > you can see the result of applying webdoc to webdoc as the result of the > ci job here [2]. If you use it further, you'll see there are still of > course some problems, but I feel it is better than before :). > > > > If you want to check it out, instructions in [3]. > > Download: > > > > Gofer it > > smalltalkhubUser: 'PharoExtras' project: 'WebDoc'; > > package:'ConfigurationOfWebDoc'; > > load. > > > > (#ConfigurationOfWebDoc asClass project version: #development) load. > > > > Export: > > (WebDocExporter packages: {RPackageOrganizer default packageNamed: > 'YourProject'}) > > title: 'YourProject'; > > exportTo: './doc' asFileReference. > > > > > > Guille > > > > [1] https://ci.inria.fr/pharo-contribution/job/WebDoc/ > > [2] > https://ci.inria.fr/pharo-contribution/job/WebDoc/PHARO=40,VERSION=developm… > > [3]http://www.smalltalkhub.com/#!/~PharoExtras/WebDoc > > >

April 23, 2015

Re: [Pharo-dev] Updated WebDoc

by Sven Van Caekenberghe

Great! Thank you. And the full image export, is that somewhere (done automatically) ? > On 23 Apr 2015, at 15:56, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > Hi guys, > > I started yesterday to update WebDoc to work on latest Pharo. I share with you my progress since yesterday: > > - Now it loads in latest pharo4 :) > - fixed javascript errors and render issues > - a little of love to the css styles > - removed unused/not working features > - made it work well when exporting not the full image > - ci job is again green [1] > > you can see the result of applying webdoc to webdoc as the result of the ci job here [2]. If you use it further, you'll see there are still of course some problems, but I feel it is better than before :). > > If you want to check it out, instructions in [3]. > Download: > > Gofer it > smalltalkhubUser: 'PharoExtras' project: 'WebDoc'; > package:'ConfigurationOfWebDoc'; > load. > > (#ConfigurationOfWebDoc asClass project version: #development) load. > > Export: > (WebDocExporter packages: {RPackageOrganizer default packageNamed: 'YourProject'}) > title: 'YourProject'; > exportTo: './doc' asFileReference. > > > Guille > > [1] https://ci.inria.fr/pharo-contribution/job/WebDoc/ > [2] https://ci.inria.fr/pharo-contribution/job/WebDoc/PHARO=40,VERSION=developm… > [3]http://www.smalltalkhub.com/#!/~PharoExtras/WebDoc

April 23, 2015

Updated WebDoc

by Guillermo Polito

Hi guys, I started yesterday to update WebDoc to work on latest Pharo. I share with you my progress since yesterday: - Now it loads in latest pharo4 :) - fixed javascript errors and render issues - a little of love to the css styles - removed unused/not working features - made it work well when exporting not the full image - ci job is again green [1] you can see the result of applying webdoc to webdoc as the result of the ci job here [2]. If you use it further, you'll see there are still of course some problems, but I feel it is better than before :). If you want to check it out, instructions in [3]. Download: Gofer it smalltalkhubUser: 'PharoExtras' project: 'WebDoc'; package:'ConfigurationOfWebDoc'; load. (#ConfigurationOfWebDoc asClass project version: #development) load. Export: (WebDocExporter packages: {RPackageOrganizer default packageNamed: 'YourProject'}) title: 'YourProject'; exportTo: './doc' asFileReference. Guille [1] https://ci.inria.fr/pharo-contribution/job/WebDoc/ [2] https://ci.inria.fr/pharo-contribution/job/WebDoc/PHARO=40,VERSION=developm… [3]http://www.smalltalkhub.com/#!/~PharoExtras/WebDoc

April 23, 2015

Re: [Pharo-dev] Why is ZeroConf Repo moved?

by Esteban Lorenzano

zeroconf is in github since ever (more than 1.5yrs at least). you can contribute using filetree and pull request, which is a common way of doing it. cheers, Esteban > On 23 Apr 2015, at 15:35, stephan <stephan(a)stack.nl> wrote: > > AFAIK, we still don't have a working git workflow, so why is development > moved to github? I'm fine with duplication, less with making it impossible > to contribute. > > Stephan >

April 23, 2015