Pharo-dev
By thread
pharo-dev@lists.pharo.org
By month
Messages by month
- ----- 2026 -----
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2025 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2024 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2008 -----
- December
- November
- October
- September
- August
- July
- June
- May
- 3 participants
- 144636 messages
Re: [Pharo-dev] Updated WebDoc
by phil@highoctane.be
On Fri, Apr 24, 2015 at 9:06 AM, Esteban Lorenzano <estebanlm(a)gmail.com>
wrote:
>
> On 24 Apr 2015, at 08:56, stepharo <stepharo(a)free.fr> wrote:
>
> Ok I saw with the version 30 it is much better :)
> Because I was surprised that someone could do anything with the 40.
> Now in that case we should not just put in it in the obscure file server
> but promoted to the website.
>
>
> it is: http://pharo.org/documentation
>
> Search through pharodocs <http://files.pharo.org/doc/4.0>
>
> The reference website for documentation about Pharo.
>
Where is the 3.0 version? This is a 4.0 with the popping up hierarchy that
makes it unusable as the popup obscures the description of the class.
Phil
>
> Esteban
>
>
>
> Stef
>
>
> Le 24/4/15 09:41, Esteban Lorenzano a écrit :
>
> no, docs for pharo 4.0 are broken.
> I will regenerate it next week (it takes hours).
>
> and about if it is useful: no experienced smalltalker will ever use it.
> But newbies and google indexer will.
>
> So is good to have it and not much effort, I think.
>
> Esteban
>
> On 24 Apr 2015, at 08:37, stepharo <stepharo(a)free.fr> wrote:
>
> Is it used? Is it useful?
> I tried to browse a method during 5 min and the result was really strange
> May be my browser is broken (safari)
>
> <jcdfgjeg..png>
> Le 23/4/15 17:15, Guillermo Polito a écrit :<cbeahccf..png>
>
> 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 24, 2015
Re: [Pharo-dev] Updated WebDoc
by phil@highoctane.be
On Fri, Apr 24, 2015 at 8:56 AM, stepharo <stepharo(a)free.fr> wrote:
> Ok I saw with the version 30 it is much better :)
> Because I was surprised that someone could do anything with the 40.
> Now in that case we should not just put in it in the obscure file server
> but promoted to the website.
>
>
> Stef
>
>
> Le 24/4/15 09:41, Esteban Lorenzano a écrit :
>
> no, docs for pharo 4.0 are broken.
> I will regenerate it next week (it takes hours).
>
> and about if it is useful: no experienced smalltalker will ever use it.
> But newbies and google indexer will.
>
>
We'd be having package level comments, that would be another story.
Thus we'd be closer to JavaDoc (e.g.
https://jaxb.java.net/nonav/2.2.1/docs/api/index.html?overview-summary.html)
It is also useful to look into things without having to load them in.
Phil
>
> So is good to have it and not much effort, I think.
>
> Esteban
>
> On 24 Apr 2015, at 08:37, stepharo <stepharo(a)free.fr> wrote:
>
> Is it used? Is it useful?
> I tried to browse a method during 5 min and the result was really strange
> May be my browser is broken (safari)
>
> <jcdfgjeg..png>
> Le 23/4/15 17:15, Guillermo Polito a écrit :<cbeahccf..png>
>
> 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 24, 2015
Re: [Pharo-dev] Release with Dark Theme
by phil@highoctane.be
On Fri, Apr 24, 2015 at 8:38 AM, Esteban Lorenzano <estebanlm(a)gmail.com>
wrote:
> I disagree⦠DarkTheme is just for certain tastes, while regular one, while
> probably dated, is more âstandardâ.
> Also, DarkTheme is not ready. yeah, yeah⦠it works and works fine most of
> the time⦠but not *all* the time (take for example find string dialog⦠I
> never found the time to fix it, and nobody complained so⦠:P). Finally. we
> need to adopt SVG icons (in my TODO list since a couple of months, I will
> deliver soon, I hope), otherwise they do not look good (this is a problem
> eclipse itself had it⦠we are just inheriting it :) )
>
> But a good question would be: How can we push forward our UI, besides
> using a darker or clearer theme?
> I would like to hear some opinions here :)
>
I'd like to have some solution for that "windows popping up everywhere"
thing. AltBrowser has some good ideas.
In fact I'd like to have AltBrowser and Nautilus together (as in additional
entries in the "Browse", "Browse Scoped", ..."Alt Browse", "Alt Browse
Scoped")
Also, having a way to see a class with all the methods in a long pane.
Yeah, Smalltalk is all about short methods but it is hard to explain things
to people when looking at a ravioli at a time.
Navigating hierarchies should be made easier (switching on the "hier/flat"
button gets tiring).
I need to see how spotter will make this easier anyway. Still not using it,
need to bring all my code to 4.0 before.
Phil
>
> Esteban
>
>
> > On 24 Apr 2015, at 08:33, stepharo <stepharo(a)free.fr> wrote:
> >
> > comments about color is to be taken with care.
> >
> >
> > Le 24/4/15 02:48, Sean P. DeNigris a écrit :
> >> Why didn't/don't we make it the default for 4.0? Everyone seems to love
> it,
> >> and people are commenting that the UI looks dated.
> >>
> >>
> >>
> >> -----
> >> Cheers,
> >> Sean
> >> --
> >> View this message in context:
> http://forum.world.st/Release-with-Dark-Theme-tp4821496.html
> >> Sent from the Pharo Smalltalk Developers mailing list archive at
> Nabble.com.
> >>
> >>
> >
> >
>
>
>
April 24, 2015
Re: [Pharo-dev] Release with Dark Theme
by phil@highoctane.be
On Fri, Apr 24, 2015 at 9:45 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote:
> That's a bit harsh, the fonts are the same ;-)
> And it is of course possible that you don't like it, it is a matter of
> taste.
> The contrast thing is also taste, but for some people it solve certain
> vision problems.
>
> Exactly.
When you have floaters all day long, the last thing you want is a f*cking
white screen.
Now, I am using 3.0 with DawnTheme, which is more like SublimeText (in a
3.0).
I tried the 4.0 and it is nice. Now, icons should get a pass because the
artefacts on the edges are not nice.
If there is some little petty cash available, that's the kind of job that
can be done supercheap on something like https://en.99designs.be/. That
would be good use of consortium/association money for example.
Why bother with graphics work when you can get things done professionaly
for close to nil?
Phil
> > On 24 Apr 2015, at 09:27, Norbert Hartl <norbert(a)hartl.name> wrote:
> >
> > That's funny because I tried it two days ago the first time and I didn't
> like it. I had troubles to get anything but bitmap fonts. After setting all
> things up I was a bit disappointed that contrast wise it doesn't work for
> me. Can someone send a screenshot with one setup that he/she considers good?
> >
> > thanks,
> >
> > Norbert
> >
> >> Am 24.04.2015 um 08:38 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>:
> >>
> >> I disagree⦠DarkTheme is just for certain tastes, while regular one,
> while probably dated, is more âstandardâ.
> >> Also, DarkTheme is not ready. yeah, yeah⦠it works and works fine most
> of the time⦠but not *all* the time (take for example find string dialog⦠I
> never found the time to fix it, and nobody complained so⦠:P). Finally. we
> need to adopt SVG icons (in my TODO list since a couple of months, I will
> deliver soon, I hope), otherwise they do not look good (this is a problem
> eclipse itself had it⦠we are just inheriting it :) )
> >>
> >> But a good question would be: How can we push forward our UI, besides
> using a darker or clearer theme?
> >> I would like to hear some opinions here :)
> >>
> >> Esteban
> >>
> >>
> >>> On 24 Apr 2015, at 08:33, stepharo <stepharo(a)free.fr> wrote:
> >>>
> >>> comments about color is to be taken with care.
> >>>
> >>>
> >>> Le 24/4/15 02:48, Sean P. DeNigris a écrit :
> >>>> Why didn't/don't we make it the default for 4.0? Everyone seems to
> love it,
> >>>> and people are commenting that the UI looks dated.
> >>>>
> >>>>
> >>>>
> >>>> -----
> >>>> Cheers,
> >>>> Sean
> >>>> --
> >>>> View this message in context:
> http://forum.world.st/Release-with-Dark-Theme-tp4821496.html
> >>>> Sent from the Pharo Smalltalk Developers mailing list archive at
> Nabble.com.
> >>>>
> >>>>
> >>>
> >>>
> >>
> >>
> >
> >
>
>
>
April 24, 2015
Re: [Pharo-dev] Release with Dark Theme
by Sven Van Caekenberghe
That's a bit harsh, the fonts are the same ;-)
And it is of course possible that you don't like it, it is a matter of taste.
The contrast thing is also taste, but for some people it solve certain vision problems.
> On 24 Apr 2015, at 09:27, Norbert Hartl <norbert(a)hartl.name> wrote:
>
> That's funny because I tried it two days ago the first time and I didn't like it. I had troubles to get anything but bitmap fonts. After setting all things up I was a bit disappointed that contrast wise it doesn't work for me. Can someone send a screenshot with one setup that he/she considers good?
>
> thanks,
>
> Norbert
>
>> Am 24.04.2015 um 08:38 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>:
>>
>> I disagree⦠DarkTheme is just for certain tastes, while regular one, while probably dated, is more âstandardâ.
>> Also, DarkTheme is not ready. yeah, yeah⦠it works and works fine most of the time⦠but not *all* the time (take for example find string dialog⦠I never found the time to fix it, and nobody complained so⦠:P). Finally. we need to adopt SVG icons (in my TODO list since a couple of months, I will deliver soon, I hope), otherwise they do not look good (this is a problem eclipse itself had it⦠we are just inheriting it :) )
>>
>> But a good question would be: How can we push forward our UI, besides using a darker or clearer theme?
>> I would like to hear some opinions here :)
>>
>> Esteban
>>
>>
>>> On 24 Apr 2015, at 08:33, stepharo <stepharo(a)free.fr> wrote:
>>>
>>> comments about color is to be taken with care.
>>>
>>>
>>> Le 24/4/15 02:48, Sean P. DeNigris a écrit :
>>>> Why didn't/don't we make it the default for 4.0? Everyone seems to love it,
>>>> and people are commenting that the UI looks dated.
>>>>
>>>>
>>>>
>>>> -----
>>>> Cheers,
>>>> Sean
>>>> --
>>>> View this message in context: http://forum.world.st/Release-with-Dark-Theme-tp4821496.html
>>>> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
>>>>
>>>>
>>>
>>>
>>
>>
>
>
April 24, 2015
Re: [Pharo-dev] Release with Dark Theme
by Norbert Hartl
That's funny because I tried it two days ago the first time and I didn't like it. I had troubles to get anything but bitmap fonts. After setting all things up I was a bit disappointed that contrast wise it doesn't work for me. Can someone send a screenshot with one setup that he/she considers good?
thanks,
Norbert
> Am 24.04.2015 um 08:38 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>:
>
> I disagree⦠DarkTheme is just for certain tastes, while regular one, while probably dated, is more âstandardâ.
> Also, DarkTheme is not ready. yeah, yeah⦠it works and works fine most of the time⦠but not *all* the time (take for example find string dialog⦠I never found the time to fix it, and nobody complained so⦠:P). Finally. we need to adopt SVG icons (in my TODO list since a couple of months, I will deliver soon, I hope), otherwise they do not look good (this is a problem eclipse itself had it⦠we are just inheriting it :) )
>
> But a good question would be: How can we push forward our UI, besides using a darker or clearer theme?
> I would like to hear some opinions here :)
>
> Esteban
>
>
>> On 24 Apr 2015, at 08:33, stepharo <stepharo(a)free.fr> wrote:
>>
>> comments about color is to be taken with care.
>>
>>
>> Le 24/4/15 02:48, Sean P. DeNigris a écrit :
>>> Why didn't/don't we make it the default for 4.0? Everyone seems to love it,
>>> and people are commenting that the UI looks dated.
>>>
>>>
>>>
>>> -----
>>> Cheers,
>>> Sean
>>> --
>>> View this message in context: http://forum.world.st/Release-with-Dark-Theme-tp4821496.html
>>> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
>>>
>>>
>>
>>
>
>
April 24, 2015
Re: [Pharo-dev] Updated WebDoc
by Luc Fabresse
2015-04-24 9:18 GMT+02:00 Max Leske <maxleske(a)gmail.com>:
>
> On 24 Apr 2015, at 08:41, Esteban Lorenzano <estebanlm(a)gmail.com> wrote:
>
> no, docs for pharo 4.0 are broken.
> I will regenerate it next week (it takes hours).
>
> and about if it is useful: no experienced smalltalker will ever use it.
> But newbies and google indexer will.
>
>
> When I took Oscar's programming language class and we used Pharo, that was
> one of the first questions: is there a doc? My reaction at first was to
> tell them to look at the source code. But it takes a while to getting used
> to that idea. If you come from other languages you just expect a doc. And
> if there isnât one âthen something must be wrong with that Pharo languageâ
> is the common reaction.
>
+1
Fully agree.
Luc
>
> So yes, as Esteban says, we need it for promotional purposes.
>
>
> So is good to have it and not much effort, I think.
>
> Esteban
>
> On 24 Apr 2015, at 08:37, stepharo <stepharo(a)free.fr> wrote:
>
> Is it used? Is it useful?
> I tried to browse a method during 5 min and the result was really strange
> May be my browser is broken (safari)
>
> <jcdfgjeg..png>
> Le 23/4/15 17:15, Guillermo Polito a écrit :<cbeahccf..png>
>
> 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 24, 2015
Re: [Pharo-dev] Updated WebDoc
by Max Leske
> On 24 Apr 2015, at 08:41, Esteban Lorenzano <estebanlm(a)gmail.com> wrote:
>
> no, docs for pharo 4.0 are broken.
> I will regenerate it next week (it takes hours).
>
> and about if it is useful: no experienced smalltalker will ever use it.
> But newbies and google indexer will.
When I took Oscar's programming language class and we used Pharo, that was one of the first questions: is there a doc? My reaction at first was to tell them to look at the source code. But it takes a while to getting used to that idea. If you come from other languages you just expect a doc. And if there isnât one âthen something must be wrong with that Pharo languageâ is the common reaction.
So yes, as Esteban says, we need it for promotional purposes.
>
> So is good to have it and not much effort, I think.
>
> Esteban
>
>> On 24 Apr 2015, at 08:37, stepharo <stepharo(a)free.fr <mailto:stepharo@free.fr>> wrote:
>>
>> Is it used? Is it useful?
>> I tried to browse a method during 5 min and the result was really strange
>> May be my browser is broken (safari)
>>
>> <jcdfgjeg..png>
>> Le 23/4/15 17:15, Guillermo Polito a écrit :<cbeahccf..png>
>>> 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/#%21/%7EPharoExtras/WebDoc>
>>>
>>>
>>
>
April 24, 2015
Re: [Pharo-dev] Fwd: exception handling problem when running tests in Nautilus
by stepharo
Hi otto
we really want that the infrastructure of Pharo tools lets you define
such process.
So this is important that you
- notify us
- potentially contribute with code.
Remember pharo is not just an external tool, this is your system.
Le 21/4/15 18:29, Otto Behrens a écrit :
>> We miss a functionality in Pharo to easily run (a shorcut) a set of selected tests (ex: your project tests). This way, you can have a quick feedback on your updates.
>> As it is not so easy, I often fallback to run tests from Nautilus (a test class or sometimes only a test method).
> This may be an idea: I once wrote a bit of Smalltalk code inspired by this:
>
> http://www.junitmax.com/
>
> We ran it in our dev environment for about 2 years, and took it out
> when we upgraded to Pharo 3.0. I still miss it. Other members on the
> project do not, generally.
>
> When accepting a method, we ran some tests:
> 1. lint (on the method)
Now we should have that. I always wanted to have that :)
> 2. if the changed method is a test method, run it (debug)
> 3. if not, run at most 5 tests in the vicinity of the changed method
> (look for some appropriate senders)
Cool :)
>
> What we got for this:
> 1. TDD really beautiful. Accept a test method -> debugger pops up ->
> write the code in the debugger -> restart -> rinse and repeat.
> 2. Lint complained instantly. Very useful. As and when.
> 3. Change domain code: breaking test pops up -> edit code in the debugger!
:)
It would be really nice to have a package with a setup like that.
The tools should be open and customizable for such process.
If you want to push this we will really help.
>
> Problems we had:
> 1. Monkey patching OmniBrowser to do stuff when accepting a method.
> Work to figure out how in Nautilus :-(
We should do a pass on nautilus but normally there should be an
event for that.
> 2. Lint became slow. Lots of work to optimise and perhaps exclude some.
We have false positive support and we can filter the rules. So with
the work on uko if should be getting better and better.
> 3. The responsiveness on accepting a method was just a slight bit slow
> which put people off
did you check recently because we did some bench like running all
the rules on a method and it was under a second.
> 4. Editing in the debugger and lists of methods: no refactoring, no
> auto-formatting; pain
We started to add refactorings in all the senders/implementors and
others.
Now if you see a place where there are missing, again send us the
code.
>
> Solutions:
> 1. Make it run in the background (continuously). Protect from running too often.
> 2. Get the method list browser and debugger editors to behave the same
> as Nautilus (at a method level)
> 3. Record information about failing tests, and run the ones that tend
> to fail more often
> 4. Use changes to help with "run tests for stuff that I am working on"
>
>
April 24, 2015
Re: [Pharo-dev] Updated WebDoc
by Esteban Lorenzano
> On 24 Apr 2015, at 08:56, stepharo <stepharo(a)free.fr> wrote:
>
> Ok I saw with the version 30 it is much better :)
> Because I was surprised that someone could do anything with the 40.
> Now in that case we should not just put in it in the obscure file server but promoted to the website.
it is: http://pharo.org/documentation <http://pharo.org/documentation>
Search through pharodocs <http://files.pharo.org/doc/4.0>
The reference website for documentation about Pharo.
Esteban
>
>
> Stef
>
>
> Le 24/4/15 09:41, Esteban Lorenzano a écrit :
>> no, docs for pharo 4.0 are broken.
>> I will regenerate it next week (it takes hours).
>>
>> and about if it is useful: no experienced smalltalker will ever use it.
>> But newbies and google indexer will.
>>
>> So is good to have it and not much effort, I think.
>>
>> Esteban
>>
>>> On 24 Apr 2015, at 08:37, stepharo <stepharo(a)free.fr <mailto:stepharo@free.fr>> wrote:
>>>
>>> Is it used? Is it useful?
>>> I tried to browse a method during 5 min and the result was really strange
>>> May be my browser is broken (safari)
>>>
>>> <jcdfgjeg..png>
>>> Le 23/4/15 17:15, Guillermo Polito a écrit :<cbeahccf..png>
>>>> 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/#%21/%7EPharoExtras/WebDoc>
>>>>
>>>>
>>>
>>
>
April 24, 2015