- Pharo-dev - lists.pharo.org

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

Re: [Pharo-dev] Fwd: exception handling problem when running tests in Nautilus

by stepharo

Le 21/4/15 17:32, Otto Behrens a Ã©crit : > Thanks. I do <alt>jc on a method sometimes when I have changed a > method. So sometimes I so <alt>jm and then immediately <alt>jc to > check all the tests in the class. > >> Indeed, Nautilus logic to run test differs a bit from the TestRunner logic. > Does it really have to be? > >> For example, if your test fails, it is run a second time to open a debugger but it could do side effects. > This has been a problem for me for a long time. I would *love* it if > Nautilus runs a single test in debug mode (and not a second time). Me too :) > It > is especially painful when running selenium tests in our environment, > because firefox is launched on every test suite run, which makes > running a single test relatively expensive. I suppose solving the > problem of tests running a long time is first prize. > >> Why don't you just run your tests from the test runner or using MyTestClass run: #testSelector ? > Because I normally run the tests that I work on while I'm in the > Nautilus browser (using shortcut keys). Why would I want to launch a > different browser, search for the class I'm working on and run the > tests there? > > I could be missing it totally here. I'm quite interested to know how > other people work. A sort of work flow, to the point of running tests. > > To run all my tests take a long time. There are quite a few. > >> We will need to clean this kind of logic that should not be part of Nautilus. Could you open a bug entry for that? > https://pharo.fogbugz.com/f/cases/15374/exception-handling-when-running-tes… > > Is this the right place? > >> Regards, >> Christophe. >> >> Le 21 avr. 2015 Ã 15:34, Otto Behrens a Ã©crit : >> >>> I realised I may have posted this on the wrong list. Is there anyone >>> that can help with this one please? >>> >>> >>> ---------- Forwarded message ---------- >>> From: Otto Behrens <otto(a)finworks.biz> >>> Date: Sun, Apr 19, 2015 at 10:08 AM >>> Subject: exception handling problem when running tests in Nautilus >>> To: pharo-users(a)lists.pharo.org >>> >>> >>> Hi, >>> >>> Thanks everyone for the new Pharo and all the work done. I like Spotter! >>> >>> I gave Pharo 4 a try today and ran into a problem with running tests >>> in a TestCase (test class -> run tests). I just get the debugger >>> popping up with WARequestContextNotFound. >>> >>> In the setUp of our test case, we call WACurrentRequestContext value, >>> but handle the error when we do not have a context, for example: >>> >>> [ WACurrentRequestContext value. true ] >>> on: WARequestContextNotFound >>> do: [ :e | false ] >>> >>> This handler: "[ :e | false ]" is never called. What influences this >>> is the exception handling in: >>> >>> AbstractNautilusUI >> #runTestsOfClass:notifying: >>> >>> Firstly, I think that it may be slighly better to call "e pass" or "e >>> outer" in stead of "e defaultAction", as this would give another outer >>> handler a chance to do something. The defaultAction is called when >>> there are no more outer handlers anyway. >>> >>> After trying this, it did not help my cause. And I think that this is >>> because the WACurrentRequestContext is a Notification and not an >>> Error. >>> >>> I then replaced Exception with Error in the handler in >>> AbstractNautilusUI. This seem to work. What also works is to >>> completely remove the exception handling in AbstractNautilusUI >> >>> #runTestsOfClass:notifying: >>> >>> What is a bit strange is the inconsistency in this exception handling >>> when running a suite or an individual test. Perhaps this kind of code >>> could be better on the TestSuite and not in the Nautilus UI? >>> >>> Can anyone please help? Should I be doing something else? >>> >>> Cheers >>> Otto >>> >

April 24, 2015

Re: [Pharo-dev] [Pharo-users] [ANN] ArchLinux pharo-vm / pharo-launcher packages

by stepharo

Thanks Linux distributions are important especially when we will be fedup by mac :). Stef Le 20/4/15 23:38, Laurent a Ã©crit : > Fixed. > > Laurent > > Le lun. 20 avril 2015 Ã 14:25, Markus Schlager <m.slg(a)gmx.de> a Ã©crit : >> Hi Laurent, There's again a 404 file not found with >> PharoLauncher-user-stable-2015.04.18.zip. Markus >> ------------------------------------------------ ==> Erstelle Paket: >> pharo-launcher 4.0-1 (Mo 20. Apr 14:19:39 CEST 2015) ==> PrÃ¼fe >> Laufzeit-AbhÃ¤ngigkeiten... ==> PrÃ¼fe Buildtime-AbhÃ¤ngigkeiten... ==> >> Empfange Quellen... -> Lade icon-lighthouse-128x128.png herunter... % >> Total % Received % Xferd Average Speed Time Time Time Current Dload >> Upload Total Spent Left Speed 100 8219 100 8219 0 0 32276 0 --:--:-- >> --:--:-- --:--:-- 32231 -> Lade >> PharoLauncher-user-stable-2015.04.18.zip herunter... % Total % >> Received % Xferd Average Speed Time Time Time Current Dload Upload >> Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- >> 0curl: (22) The requested URL returned error: 404 Not Found ==> >> FEHLER: Fehler beim Download von >> PharoLauncher-user-stable-2015.04.18.zip Breche ab...

April 24, 2015

Re: [Pharo-dev] RPackage: 'accessing' vs 'all accessing' Protocol

by stepharo

a mistake to me. I will resume my work on the automatic classifier and we should classify the complete image. Le 23/4/15 18:31, Sean P. DeNigris a Ã©crit : > What is the distinction of 'all accessing'? > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/RPackage-accessing-vs-all-accessing-Protocol-tp482146… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

April 24, 2015

Re: [Pharo-dev] Updated WebDoc

by stepharo

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. > > 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/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/ >>> > [2] >>> 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] Updated WebDoc

by Esteban Lorenzano

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/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] Release with Dark Theme

by Esteban Lorenzano

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 stepharo

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) Le 23/4/15 17:15, Guillermo Polito a Ã©crit : > 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 <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/ > > [2] > 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