Re: [Pharo-dev] Embeddable/scalable Smalltalk VM needs funding for release (repost/update from squeak-dev)

[S Krish]

Great Work..!!

On Mon, May 15, 2017 at 1:01 PM, Zak Fenton  wrote:

> Hi folks. I posted earlier in squeak-dev about a Smalltalk implementation
> I've been working on. The first post was a bit unwieldy, but there was at
> least some interest so I'm posting an update to vm-dev and pharo-dev.
>
>
> Main strong points are that it's embeddable (like Lua or SQLite) and
> scalable (like Erlang). There are weak points too, of course (e.g. hot loop
> performance will be much worse than Squeak/Pharo at this point).
>
>
> The VM itself is pure C and has no dependencies apart from libc and libm.
> It doesn't require a filesystem (you can pipe VM images through custom
> stream implementations or arrays) and it should run well in tight (~1MB)
> memory situations.
>
>
> The extension system is similar to the Unix system call and virtual
> filesystem APIs, so it's kind-of object oriented but in a very "C" way. All
> extension resources are managed properly (so the system can clean up safely
> and/or warn you if you allocate memory and don't deallocate it, for
> example).
>
>
> Extensions are available for cells (threads/individual VMs), shared memory
> (so different cells can communicate efficiently - but also with memory
> protection and calling features for implementing domain-specific JIT
> compilers), windowing and event handling (based on SDL2) and 2D graphics
> rendering (based on Cairo). There are some higher-level libraries (stylable
> GUI system, tight OS integration, 3D modelling, etc.).
>
>
> It's polished in some ways (there's a test suite, an integrated help
> system, colour shell, etc.), but it needs a lot more refinement in others
> (the current GUI style is terrible, it needs more documentation, there's
> only minimal support for keyboard entry, no networking library, etc.).
>
>
> I'd like to release it (ideally as 100% public domain/CC0), but I don't
> want to do so without some way of funding development. The project promises
> a lot and I want to actually deliver with some ongoing updates and support
> (and being able to pay rent next week would also be a plus), so I'm not
> interested in just dumping it on GitHub and calling it a day.
>
>
> So I'm open to any suggestions as to how to fund this project at least in
> the short term and how it might fit into the wider Squeak/Pharo/Smalltalk
> ecosystems, as well as any technical criticism relating to the
> implementation itself.
>
>
> I've put together a basic website describing the implementation in a bit
> more detail (sorry, no downloads yet): http://a4vm.info/
>
>
> -Zak.
>

[Pharo-dev] Calypso technology preview.

[Ben Coman]

It is probably much too late to suggest this, but if Calypso is a candidate
for our next browser, perhaps it could be included in Pharo 6 as a
technology preview?
Or maybe in a half-year point release Pharo 6.x ?

cheers -ben

Re: [Pharo-dev] Launcher and Pharo 6 Errors on Mac

[Ben Coman]

On Sat, May 20, 2017 at 2:02 AM, Sean P. DeNigris 
wrote:

> Ben Coman wrote
> > What do you get installing from the Catalogue into a fresh Image and
> > manually updating?
>
> When you say "fresh image", what do you have in mind because I got the same
> error with a Pharo 6 from the CI, so it doesn't seem to be a launcher
> issue.
>

Just that.  Isolating the problem between Launcher or Pharo


> Sorry if I was not clear...
>
>
cool.
cheers -ben

[Pharo-dev] Re : QualityImprovements assured by tests

[Benoit St-Jean via Pharo-dev]

--- Begin Message ---
How about a sprint? I surely am not the most qualified person to comment a 
class I did not create but we can all remove crap ! 

Envoyé à partir de Yahoo Courriel sur Android 
 
  Le ven., mai 19 2017 à 18:26, Torsten Bergmann a écrit :   Hi,

One year later we are close to a final release for Pharo 6 and either with 
Pharo 6 or upcoming Pharo 7 
I would really like to see some checks that ensure a quality image and tests 
who keep us all more 
disciplined in the future. 

Because:

  1. We should not have undocumented classes:

        (Object allSubclasses select: [:cls| cls hasComment not ]) 

    but we have a lot in Pharo 6 now since we introduced new packages in this 
release iteration

  2. We should not have class instance variables in uppercase but:

    (Object allSubclasses select: [:cls| cls isMeta]) select: [:cls| cls  
      instVarNames anySatisfy: [:n | n first isUppercase]]

    is not empty - although this was already discussed back in 2008 (!), see
    
http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2008-November/003366.html

  3. We should not have uncategorized methods but:

    (Object allSubclasses select: [:cls| (cls selectorsInProtocol: Protocol 
unclassified) notEmpty ]) 

    we still have them. 

  4. I've seen methods with unused temporary variables. Dont know about unused 
ivars or other.
 
  5. add you own here ...

I know this is often boring to comment or categorize - but we should do our 
homework as we wanted to
better compared to the past. Also if the base image is not following rules how 
should we expect others
to provide quality packages on top of it? 

IMHO we should raise the bar. Either in Pharo 6 or in early Pharo 7. We can fix 
these once and for 
all AND assure with unit tests that we keep the standard image on this quality 
level.

Thx
T.




  
--- End Message ---

[Pharo-dev] QualityImprovements assured by tests

[Torsten Bergmann]

Hi,

One year later we are close to a final release for Pharo 6 and either with 
Pharo 6 or upcoming Pharo 7 
I would really like to see some checks that ensure a quality image and tests 
who keep us all more 
disciplined in the future. 

Because:

  1. We should not have undocumented classes:

(Object allSubclasses select: [:cls| cls hasComment not ]) 

 but we have a lot in Pharo 6 now since we introduced new packages in this 
release iteration

  2. We should not have class instance variables in uppercase but:

 (Object allSubclasses select: [:cls| cls isMeta]) select: [:cls| cls  
   instVarNames anySatisfy: [:n | n first isUppercase]]

 is not empty - although this was already discussed back in 2008 (!), see
 
http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2008-November/003366.html

  3. We should not have uncategorized methods but:

 (Object allSubclasses select: [:cls| (cls selectorsInProtocol: Protocol 
unclassified) notEmpty ]) 

 we still have them. 

  4. I've seen methods with unused temporary variables. Dont know about unused 
ivars or other.
 
  5. add you own here ...

I know this is often boring to comment or categorize - but we should do our 
homework as we wanted to
better compared to the past. Also if the base image is not following rules how 
should we expect others
to provide quality packages on top of it? 

IMHO we should raise the bar. Either in Pharo 6 or in early Pharo 7. We can fix 
these once and for 
all AND assure with unit tests that we keep the standard image on this quality 
level.

Thx
T.

Re: [Pharo-dev] Chrome DevTools Protocol and Pharo

[Alistair Grant]

Hi Torsten,

On Fri, May 19, 2017 at 10:50:41PM +0200, Torsten Bergmann wrote:
> Hi Alistair,
> 
> cant look right now but two things:
> 
>   - there are also events in the protocol - if we could hook Pharo into them
> this would solve the problem without abusing delay (because then you will 
> get informed when the page loading is finished)

That would be great.  It will be a while before I get a chance to look
at this (I want to finish some proposed changes to the FileSystem
packages first), but I'll try and include it then.


>   - you can write "5 seconds wait" in Pharo

Thanks for the tip (I'm still transitioning from VW 2.5 :-)).


> 
> Bye
> T. 
> 
> 
> > Gesendet: Freitag, 19. Mai 2017 um 17:51 Uhr
> > Von: "Alistair Grant" 
> > An: pharo-dev@lists.pharo.org
> > Betreff: Re: [Pharo-dev] Chrome DevTools Protocol and Pharo
> >
> > On Fri, May 19, 2017 at 01:50:28PM +0200, Torsten Bergmann wrote:
> > > Alistair Grant wrote
> > > 
> > > > This looks really interesting, thanks for making it available.  I'm on
> > > > linux, so I guess it will need some porting.
> > > 
> > > I added support for Linux and tried on Ubuntu with Chromium. Works - see 
> > > screenshot
> > 
> > Fantastic, thanks!
> > 
> > I did have to change your script for it to work on my laptop:
> > 
> > 1. isInDebugMode is false by default, which meant that chrome wasn't
> > launched with remote debugging enabled.
> > 
> > 2. Retrieving the remotes in GoogleChrome class>>tabPages failed because
> > the browser hadn't had time to start up.  I'll submit a pull request
> > which adds a retry with delay.

I've submitted the PR to ping the browser while it starts up, and add
/opt/google/chrome/chrome as a known location.

Thanks again,
Alistair


> > 3. I initially got a white image.  This appears to be because the script
> > doesn't wait for the navigation to complete before taking the
> > screenshot.  I just added an ugly delay, but I'm not yet sure what the best
> > solution here is.
> > 
> > 
> > | chrome page |
> > 
> > chrome := GoogleChrome new
> > debugOn;
> > open;
> > yourself.
> > page := chrome tabPages first.
> > page navigateTo: 'http://www.pharo.org'.
> > (Delay forSeconds: 5) wait.
> > page captureScreenshot scaledToSize: 200@300.
> > 
> > 
> > > You need to load my OSLinux package (instead of OSOSX) from catalog. Or 
> > > start 
> > > Chrom manually in debug mode.
> > > 
> > > In the Pharo settings browser you can set the path to the chrome 
> > > executable
> > > and the debug port to use.
> > 
> > I doubt that the chrome executable is in that many different places.
> > Would you be open accepting a pull request which adds (what I assume is)
> > the Ubuntu 16.04 default location?
> > 
> > 
> > > Will add Windows support as well (using my OSWindows package)
> > > 
> > > > Do you know how the DevTools protocol relates to headless chome, which
> > > > will be available in Chrome 59?
> > > > See https://developers.google.com/web/updates/2017/04/headless-chrome
> > > 
> > > Dont know - just try it.
> > > 
> > > > In particular, is it possible to dump the DOM with your package?
> > > 
> > > I've seen that Brackets editor as well as Netbeans open Chrome to
> > > display webpages when editing and refresh when typing. Wanted
> > > to find out how it was done.
> > > 
> > > I have not implemented the full protocol. Only what was needed to show
> > > that it is possible and to do things like grabbing screenshots from 
> > > websites
> > > using Pharo.
> > 
> > I've found a page that describes accessing the DOM, so it looks like it
> > should be possible.  I'll see what I can do...
> > 
> > > There is a DOM domain that one could wrap - basically it is just
> > > sending JSON around, see
> > > https://chromedevtools.github.io/devtools-protocol
> > > 
> > > With 
> > > 
> > >  chrome := GoogleChrome open.
> > >  chrome jsProtocolJSON.
> > >  chrome browseProtocolJSON
> > > 
> > > you can now even retrieve the Protocol as JSON for the specific browser. 
> > > With a little bit more work it should be possible to even generate 
> > > the wrapper classes/methods from such a protocol spec.

Re: [Pharo-dev] Chrome DevTools Protocol and Pharo

[Torsten Bergmann]

Hi Alistair,

cant look right now but two things:

  - there are also events in the protocol - if we could hook Pharo into them
this would solve the problem without abusing delay (because then you will 
get informed when the page loading is finished)

  - you can write "5 seconds wait" in Pharo

Bye
T. 


> Gesendet: Freitag, 19. Mai 2017 um 17:51 Uhr
> Von: "Alistair Grant" 
> An: pharo-dev@lists.pharo.org
> Betreff: Re: [Pharo-dev] Chrome DevTools Protocol and Pharo
>
> On Fri, May 19, 2017 at 01:50:28PM +0200, Torsten Bergmann wrote:
> > Alistair Grant wrote
> > 
> > > This looks really interesting, thanks for making it available.  I'm on
> > > linux, so I guess it will need some porting.
> > 
> > I added support for Linux and tried on Ubuntu with Chromium. Works - see 
> > screenshot
> 
> Fantastic, thanks!
> 
> I did have to change your script for it to work on my laptop:
> 
> 1. isInDebugMode is false by default, which meant that chrome wasn't
> launched with remote debugging enabled.
> 
> 2. Retrieving the remotes in GoogleChrome class>>tabPages failed because
> the browser hadn't had time to start up.  I'll submit a pull request
> which adds a retry with delay.
> 
> 3. I initially got a white image.  This appears to be because the script
> doesn't wait for the navigation to complete before taking the
> screenshot.  I just added an ugly delay, but I'm not yet sure what the best
> solution here is.
> 
> 
> | chrome page |
> 
> chrome := GoogleChrome new
>   debugOn;
>   open;
>   yourself.
> page := chrome tabPages first.
> page navigateTo: 'http://www.pharo.org'.
> (Delay forSeconds: 5) wait.
> page captureScreenshot scaledToSize: 200@300.
> 
> 
> > You need to load my OSLinux package (instead of OSOSX) from catalog. Or 
> > start 
> > Chrom manually in debug mode.
> > 
> > In the Pharo settings browser you can set the path to the chrome executable
> > and the debug port to use.
> 
> I doubt that the chrome executable is in that many different places.
> Would you be open accepting a pull request which adds (what I assume is)
> the Ubuntu 16.04 default location?
> 
> 
> > Will add Windows support as well (using my OSWindows package)
> > 
> > > Do you know how the DevTools protocol relates to headless chome, which
> > > will be available in Chrome 59?
> > > See https://developers.google.com/web/updates/2017/04/headless-chrome
> > 
> > Dont know - just try it.
> > 
> > > In particular, is it possible to dump the DOM with your package?
> > 
> > I've seen that Brackets editor as well as Netbeans open Chrome to
> > display webpages when editing and refresh when typing. Wanted
> > to find out how it was done.
> > 
> > I have not implemented the full protocol. Only what was needed to show
> > that it is possible and to do things like grabbing screenshots from websites
> > using Pharo.
> 
> I've found a page that describes accessing the DOM, so it looks like it
> should be possible.  I'll see what I can do...
> 
> > There is a DOM domain that one could wrap - basically it is just
> > sending JSON around, see
> > https://chromedevtools.github.io/devtools-protocol
> > 
> > With 
> > 
> >  chrome := GoogleChrome open.
> >  chrome jsProtocolJSON.
> >  chrome browseProtocolJSON
> > 
> > you can now even retrieve the Protocol as JSON for the specific browser. 
> > With a little bit more work it should be possible to even generate 
> > the wrapper classes/methods from such a protocol spec.
> 
> Thanks again,
> Alistair
> 
> 
> 
> 

[Pharo-dev] Epicea and #name in #behaviorAffectedName

[Torsten Bergmann]

Hi,

in latest Pharo 6 image 60494 I run into some trouble today where the 
deprecation warning dialog popped up and repeated itself unstoppable
due to Epicea.

It is hard to reproduce but what I found out was that I had a class
modification (represented by EpClassModification) which run into a state 
where "newClass" was nil and therefore in 
EpClassModification>>#behaviorAffectedName 
the message #name was sent to nil.

So #name was found in Object and as we all know we deprecated it now
which lead to the deprecation dialog, leading to the deprecation dialog, 
leading to the deprecation dialog, ... 

Nearly all implementors of Epiceas #behaviorAffectedName send #name
which is ok if there is a valid object it is sent to.

I do not know if we should protect them somehow in case something
goes wrong (like having nil in newClass) or if we should keep this 
untouched.

At least I wanted to inform because I do not know if this later
gets others into trouble too and losing their changes because Epicea
does not record.

Thanks
T.

Re: [Pharo-dev] Launcher and Pharo 6 Errors on Mac

[Sean P. DeNigris]

Ben Coman wrote
> What do you get installing from the Catalogue into a fresh Image and
> manually updating?

When you say "fresh image", what do you have in mind because I got the same
error with a Pharo 6 from the CI, so it doesn't seem to be a launcher issue.
Sorry if I was not clear...



-
Cheers,
Sean
--
View this message in context: 
http://forum.world.st/Launcher-and-Pharo-6-Errors-on-Mac-tp4947652p4947665.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Re: [Pharo-dev] Chrome DevTools Protocol and Pharo

[Ben Coman]

Would you be interested in trying it with BSD Licensed Chromium...
https://chromium.googlesource.com/chromium/src/+/lkgr/headless/README.md
which could be packaged with a Pharo distribution.

cheers -ben

P.S. on the idea of an in-Image browser, this looks interesting...
https://en.wikipedia.org/wiki/Chromium_Embedded_Framework


On Fri, May 19, 2017 at 3:20 AM, Torsten Bergmann  wrote:

> Hi,
>
> I played around with remote controlling Google Chrome from
> Pharo using Chrome DevTools Protocol [1] (based on WebSockets).
>
> The video shows an example using latest Pharo 6 on Mac:
> https://www.youtube.com/watch?v=9F5FrQTEJWY
>
> Initial Code is on GitHub [2] if someone is interested,
> requires OSOSX and Zinc Websockets to be loaded.
>
> Have fun
> T.
>
> [1] https://chromedevtools.github.io/devtools-protocol
> [2] https://github.com/astares/Pharo-Chrome
>
>

Re: [Pharo-dev] Launcher and Pharo 6 Errors on Mac

[Ben Coman]

What do you get installing from the Catalogue into a fresh Image and
manually updating?
cheers -ben

On Fri, May 19, 2017 at 10:48 PM, Sean P. DeNigris 
wrote:

> On image start, I get "PrimitiveFailed: primitive #createDirectory: in
> MacStore failed" for
> /private/var/folders/fv/8j408sn92bb59k5ggw8cd3kcgn
> /T/AppTranslocation/4EF86F92-66D6-4944-8B30-FBCD96118FCC/d/
> Pharo.app/Contents/Resources/pharo-local
>
> When I try to Quit, I get "PrimitiveFailed: primitive #primSize: in
> MultiByteFileStream failed" from `SourceFiles changesFileStream size`
>
> FYI I got the same results when I downloaded:
> - the latest Launcher from
> https://ci.inria.fr/pharo/view/Launcher/job/Launcher/
> PHARO=60,VERSION=stable,VM=vm,label=linux/lastSuccessfulBuild/artifact/
> Pharo-mac.zip
> - Pharo 6 from http://files.pharo.org/platform/Pharo6.0-mac.zip
>
> Mac Sierra 10.12.3
>
> From the Pharo 6 download:
>
> Image
> -
> /private/var/folders/fv/8j408sn92bb59k5ggw8cd3kcgn
> /T/AppTranslocation/C2941508-46E0-4CEC-8573-CBC4488351B0/d/
> Pharo6.0.app/Contents/Resources/Pharo6.0.image
> Pharo6.0
> Latest update: #60494
> Unnamed
>
> Virtual Machine
> ---
> /private/var/folders/fv/8j408sn92bb59k5ggw8cd3kcgn
> /T/AppTranslocation/C2941508-46E0-4CEC-8573-CBC4488351B0/d/
> Pharo6.0.app/Contents/MacOS/Pharo
> CoInterpreter VMMaker.oscog-eem.2203 uuid:
> 12d4afae-8498-4e76-8efe-60eba6ef4db2 May  2 2017
> StackToRegisterMappingCogit VMMaker.oscog-eem.2203 uuid:
> 12d4afae-8498-4e76-8efe-60eba6ef4db2 May  2 2017
> VM: 201705021552 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $
> Date: Tue May 2 08:52:41 2017 -0700 $ Plugins: 201705021552
> https://github.com/OpenSmalltalk/opensmalltalk-vm.git $
>
> Mac OS X built on May  2 2017 17:03:29 UTC Compiler: 4.2.1 Compatible Apple
> LLVM 6.1.0 (clang-602.0.53)
> VMMaker versionString VM: 201705021552
> https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: Tue May 2
> 08:52:41 2017 -0700 $ Plugins: 201705021552
> https://github.com/OpenSmalltalk/opensmalltalk-vm.git $
> CoInterpreter VMMaker.oscog-eem.2203 uuid:
> 12d4afae-8498-4e76-8efe-60eba6ef4db2 May  2 2017
> StackToRegisterMappingCogit VMMaker.oscog-eem.2203 uuid:
> 12d4afae-8498-4e76-8efe-60eba6ef4db2 May  2 2017
>
>
>
> -
> Cheers,
> Sean
> --
> View this message in context: http://forum.world.st/
> Launcher-and-Pharo-6-Errors-on-Mac-tp4947652.html
> Sent from the Pharo Smalltalk Developers mailing list archive at
> Nabble.com.
>
>

Re: [Pharo-dev] [Pharo-users] Need help with Pillar

[Alexandre Bergel]

Okay, will check!

Alexandre
-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.



> On May 19, 2017, at 10:35 AM, Damien Pollet  
> wrote:
> 
> I think it would have updated stuff. Hopefully.
> 
> As an alternative, to run in docker :
> - delete pharo-vm (because if it's a mac VM it will not work in the linux 
> container)
> - docker run --rm -tiv $PWD:/work dpollet/texlive:pillar make pdfbook
> 
> Docker is what the travis builds use, you can check the config file in books 
> that I have recently updated, e.g. 
> https://github.com/SquareBracketAssociates/Booklet-Glorp/blob/master/.travis.yml
>  
> 
> 
> 
> On 19 May 2017 at 16:27, Alexandre Bergel  > wrote:
> I get the following:
> 
> ~/Dropbox/Pillar> tlmgr update --self --all
> TeX Live 2016 is frozen forever and will no
> longer be updated.  This happens in preparation for a new release.
> 
> If you're interested in helping to pretest the new release (when
> pretests are available), please read http://tug.org/texlive/pretest.html 
> .
> Otherwise, just wait, and the new release will be ready in due time.
> tlmgr: package repository 
> http://ftp.inf.utfsm.cl/pub/tex-archive/systems/texlive/tlnet 
>  (not 
> verified: gnupg not available)
> You don't have permission to change the installation in any way,
> specifically, the directory /usr/local/texlive/2016/tlpkg/ is not writable.
> Please run this program as administrator, or contact your local admin.
> tlmgr: An error has occurred. See above messages. Exiting.
> ~/Dropbox/Pillar> 
> 
> I use the installation of TeXlive on my machine since I have no idea who to 
> make the docker image use my local files.
>  
> Alexandre
> -- 
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu 
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> 
> 
> 
>> On May 19, 2017, at 10:06 AM, Damien Pollet > > wrote:
>> 
>> I think you still have a TeXlive snapshot from earlier this year. Try this :
>> tlmgr update --self --all
>> 
>> On 19 May 2017 at 15:19, Alexandre Bergel > > wrote:
>> Hi Damien!
>> 
>> Apparently the INRIA CI is getting better. I could get the archetype. I have 
>> another error when compiling the book. I get:
>> Sidefoothsep and sidefootwidth: 2.46019mm and 44.98633mm
>> Sidefootvsep and sidefootheight: 4.21747mm and 192.73828mm
>> **
>> 
>> (/usr/local/texlive/2016/texmf-dist/tex/latex/datetime2/datetime2.sty
>> (/usr/local/texlive/2016/texmf-dist/tex/latex/tracklang/tracklang.sty
>> (/usr/local/texlive/2016/texmf-dist/tex/generic/tracklang/tracklang.tex)))
>> Runaway argument?
>> \pdffeedback creationdate\@dtm@endparsepdfdatetime \let \@dtm@currentyear 
>> \ETC.
>> 
>> ./root/support/latex/common.tex:5: File ended while scanning use of 
>> \@dtm@parse
>> pdfdatetime.
>>  
>> \par 
>> l.5 
>>   
>>  1217 words of node memory still in use:
>>2 hlist, 1 rule, 1 dir, 34 glue, 9 attribute, 167 glue_spec, 9 
>> attribute_lis
>> t, 3 write, 1 pdf_colorstack nodes
>>avail lists: 2:24,3:1,5:2,6:4,7:1,8:1,9:2
>> ./root/support/latex/common.tex:5:  ==> Fatal error occurred, no output PDF 
>> fil
>> e produced!
>> Transcript written on book.log.
>> Latexmk: Errors, so I did not complete making targets
>> Collected error summary (may duplicate other messages):
>>   pdflatex: Command for 'pdflatex' gave return code 256
>> Latexmk: Use the -f option to force complete processing,
>>  unless error was exceeding maximum runs of latex/pdflatex.
>> make[1]: *** [book.pdf] Error 12
>> make: *** [build/book.pdf] Error 2
>> ~/Dropbox/Pillar> 
>> 
>> Is it because of some missing Latex .cls? If yes, which one? How can I 
>> install them?
>> 
>> Thanks for your help! 
>> 
>> Cheers,
>> Alexandre
>> -- 
>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> Alexandre Bergel  http://www.bergel.eu 
>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>> 
>> 
>> 
>>> On May 18, 2017, at 7:43 AM, Damien Pollet >> > wrote:
>>> 
>>> On 18 May 2017 at 01:34, Alexandre Bergel >> > wrote:
>>> curl 
>>> https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh 
>>>  
>>> | bash
>>> 
>>> I had to copy PharoV50.sources in the folder pharo-vm/ apparently.
>>> 
>>> Hmm strange I got that this morning as well with 

Re: [Pharo-dev] Chrome DevTools Protocol and Pharo

[Alistair Grant]

On Fri, May 19, 2017 at 01:50:28PM +0200, Torsten Bergmann wrote:
> Alistair Grant wrote
> 
> > This looks really interesting, thanks for making it available.  I'm on
> > linux, so I guess it will need some porting.
> 
> I added support for Linux and tried on Ubuntu with Chromium. Works - see 
> screenshot

Fantastic, thanks!

I did have to change your script for it to work on my laptop:

1. isInDebugMode is false by default, which meant that chrome wasn't
launched with remote debugging enabled.

2. Retrieving the remotes in GoogleChrome class>>tabPages failed because
the browser hadn't had time to start up.  I'll submit a pull request
which adds a retry with delay.

3. I initially got a white image.  This appears to be because the script
doesn't wait for the navigation to complete before taking the
screenshot.  I just added an ugly delay, but I'm not yet sure what the best
solution here is.


| chrome page |

chrome := GoogleChrome new
debugOn;
open;
yourself.
page := chrome tabPages first.
page navigateTo: 'http://www.pharo.org'.
(Delay forSeconds: 5) wait.
page captureScreenshot scaledToSize: 200@300.


> You need to load my OSLinux package (instead of OSOSX) from catalog. Or start 
> Chrom manually in debug mode.
> 
> In the Pharo settings browser you can set the path to the chrome executable
> and the debug port to use.

I doubt that the chrome executable is in that many different places.
Would you be open accepting a pull request which adds (what I assume is)
the Ubuntu 16.04 default location?


> Will add Windows support as well (using my OSWindows package)
> 
> > Do you know how the DevTools protocol relates to headless chome, which
> > will be available in Chrome 59?
> > See https://developers.google.com/web/updates/2017/04/headless-chrome
> 
> Dont know - just try it.
> 
> > In particular, is it possible to dump the DOM with your package?
> 
> I've seen that Brackets editor as well as Netbeans open Chrome to
> display webpages when editing and refresh when typing. Wanted
> to find out how it was done.
> 
> I have not implemented the full protocol. Only what was needed to show
> that it is possible and to do things like grabbing screenshots from websites
> using Pharo.

I've found a page that describes accessing the DOM, so it looks like it
should be possible.  I'll see what I can do...

> There is a DOM domain that one could wrap - basically it is just
> sending JSON around, see
> https://chromedevtools.github.io/devtools-protocol
> 
> With 
> 
>  chrome := GoogleChrome open.
>  chrome jsProtocolJSON.
>  chrome browseProtocolJSON
> 
> you can now even retrieve the Protocol as JSON for the specific browser. 
> With a little bit more work it should be possible to even generate 
> the wrapper classes/methods from such a protocol spec.

Thanks again,
Alistair

Re: [Pharo-dev] bug in command line handler

[K K Subbu]

On Friday 19 May 2017 05:40 PM, Damien Pollet wrote:

I wouldn't want to sound sarcastic, but I'm not sure there is such a
concept as "correct" in the context of ANSI escape sequences.
Still, according to the legends, 97 is supposed to be high intensity
white (for some subset of existing implementations).


;-). My context was command line usage in linux terminals.

Anyway, attached is a patch for the annoying bug which fixed the problem 
for me. I would appreciate if anyone else using the command line can 
confirm if the patch works for them. E.g.



$ ./pharo Pharo.image eval 'ProtoObject methodDict size\;^MProtoObject 
methodDict keys'

Syntax Error on line 1: 'Variable or expression expected'
=
1: ProtoObject methodDict size\;
  _^_
2: ProtoObject methodDict keys
$ ./pharo Pharo.image eval 'ProtoObject methodDict size.^MProtoObject 
methodDict keys;'

Syntax Error on line 2: 'Message expected'
==
1: ProtoObject methodDict size.
2: ProtoObject methodDict keys;
  _^_
$


Thanks .. Subbu


'From Pharo6.0 of 13 May 2016 [Latest update: #60473] on 19 May 2017 at 8:03:31.630191 pm'!
"Change Set:		resetcolor
Date:			19 May 2017
Author:			kks

reset colors after printing error messages while parsing"!


!STCommandLineHandler class methodsFor: 'printing' stamp: 'kks 5/19/2017 20:01'!
printCompilerWarning: aSyntaxErrorNotification
	| stderr position contents errorLine errorMessage maxLineNumberSize lineNumber |
	
	"format the error"
	position := aSyntaxErrorNotification location.
	contents := aSyntaxErrorNotification errorCode.
	errorLine := contents lineNumberCorrespondingToIndex: position.
	stderr := VTermOutputDriver stderr.
		
	"first gather the error title to be able to underline it properly"
	errorMessage := String streamContents: [ :s|
		s nextPutAll: 'Syntax Error on line '; 
			print: errorLine; nextPutAll: ': '; 
			print: aSyntaxErrorNotification errorMessage].
	
	 stderr red;
		nextPutAll: errorMessage; lf;
		nextPutAll: ('' padLeftTo: errorMessage size with: $=); lf;
		clear.
	
	"print each source line and mark the found syntax error"
	maxLineNumberSize := contents lines size asString size.
	lineNumber := 0.
	contents lineIndicesDo: [:start :endWithoutDelimiters :end |
		lineNumber := lineNumber + 1.
		lineNumber == errorLine ifTrue: [ stderr errorColor ].
		"0 pad the line numbers to the same size"
		stderr 
			nextPutAll: (lineNumber asString padLeftTo: maxLineNumberSize with: $0);
			nextPutAll: ': ';
			nextPutAll: (contents copyFrom: start to: endWithoutDelimiters);
			lf.
			"print the marker under the error line"
		(lineNumber == errorLine)
			ifTrue: [
	stderr nextPutAll:( '_^_' padLeftTo: position - start + maxLineNumberSize + 4);
			 lf;
			 clear]
	]! !


!VTermOutputDriver methodsFor: 'coloring' stamp: 'kks 5/19/2017 19:58'!
errorColor 
	self red! !

[Pharo-dev] Launcher and Pharo 6 Errors on Mac

[Sean P. DeNigris]

On image start, I get "PrimitiveFailed: primitive #createDirectory: in
MacStore failed" for
/private/var/folders/fv/8j408sn92bb59k5ggw8cd3kcgn/T/AppTranslocation/4EF86F92-66D6-4944-8B30-FBCD96118FCC/d/Pharo.app/Contents/Resources/pharo-local

When I try to Quit, I get "PrimitiveFailed: primitive #primSize: in
MultiByteFileStream failed" from `SourceFiles changesFileStream size`

FYI I got the same results when I downloaded:
- the latest Launcher from
https://ci.inria.fr/pharo/view/Launcher/job/Launcher/PHARO=60,VERSION=stable,VM=vm,label=linux/lastSuccessfulBuild/artifact/Pharo-mac.zip
- Pharo 6 from http://files.pharo.org/platform/Pharo6.0-mac.zip

Mac Sierra 10.12.3

>From the Pharo 6 download:

Image
-
/private/var/folders/fv/8j408sn92bb59k5ggw8cd3kcgn/T/AppTranslocation/C2941508-46E0-4CEC-8573-CBC4488351B0/d/Pharo6.0.app/Contents/Resources/Pharo6.0.image
Pharo6.0
Latest update: #60494
Unnamed

Virtual Machine
---
/private/var/folders/fv/8j408sn92bb59k5ggw8cd3kcgn/T/AppTranslocation/C2941508-46E0-4CEC-8573-CBC4488351B0/d/Pharo6.0.app/Contents/MacOS/Pharo
CoInterpreter VMMaker.oscog-eem.2203 uuid:
12d4afae-8498-4e76-8efe-60eba6ef4db2 May  2 2017
StackToRegisterMappingCogit VMMaker.oscog-eem.2203 uuid:
12d4afae-8498-4e76-8efe-60eba6ef4db2 May  2 2017
VM: 201705021552 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $
Date: Tue May 2 08:52:41 2017 -0700 $ Plugins: 201705021552
https://github.com/OpenSmalltalk/opensmalltalk-vm.git $

Mac OS X built on May  2 2017 17:03:29 UTC Compiler: 4.2.1 Compatible Apple
LLVM 6.1.0 (clang-602.0.53)
VMMaker versionString VM: 201705021552
https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: Tue May 2
08:52:41 2017 -0700 $ Plugins: 201705021552
https://github.com/OpenSmalltalk/opensmalltalk-vm.git $
CoInterpreter VMMaker.oscog-eem.2203 uuid:
12d4afae-8498-4e76-8efe-60eba6ef4db2 May  2 2017
StackToRegisterMappingCogit VMMaker.oscog-eem.2203 uuid:
12d4afae-8498-4e76-8efe-60eba6ef4db2 May  2 2017



-
Cheers,
Sean
--
View this message in context: 
http://forum.world.st/Launcher-and-Pharo-6-Errors-on-Mac-tp4947652.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Re: [Pharo-dev] [Pharo-users] Need help with Pillar

[Damien Pollet]

I think it would have updated stuff. Hopefully.

As an alternative, to run in docker :
- delete pharo-vm (because if it's a mac VM it will not work in the linux
container)
- docker run --rm -tiv $PWD:/work dpollet/texlive:pillar make pdfbook

Docker is what the travis builds use, you can check the config file in
books that I have recently updated, e.g.
https://github.com/SquareBracketAssociates/Booklet-Glorp/blob/master/.travis.yml


On 19 May 2017 at 16:27, Alexandre Bergel  wrote:

> I get the following:
>
> ~/Dropbox/Pillar> tlmgr update --self --all
> TeX Live 2016 is frozen forever and will no
> longer be updated.  This happens in preparation for a new release.
>
> If you're interested in helping to pretest the new release (when
> pretests are available), please read http://tug.org/texlive/pretest.html.
> Otherwise, just wait, and the new release will be ready in due time.
> tlmgr: package repository http://ftp.inf.utfsm.cl/pub/
> tex-archive/systems/texlive/tlnet (not verified: gnupg not available)
> You don't have permission to change the installation in any way,
> specifically, the directory /usr/local/texlive/2016/tlpkg/ is not writable.
> Please run this program as administrator, or contact your local admin.
> tlmgr: An error has occurred. See above messages. Exiting.
> ~/Dropbox/Pillar>
>
> I use the installation of TeXlive on my machine since I have no idea who
> to make the docker image use my local files.
>
> Alexandre
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
> On May 19, 2017, at 10:06 AM, Damien Pollet 
> wrote:
>
> I think you still have a TeXlive snapshot from earlier this year. Try this
> :
> tlmgr update --self --all
>
> On 19 May 2017 at 15:19, Alexandre Bergel  wrote:
>
>> Hi Damien!
>>
>> Apparently the INRIA CI is getting better. I could get the archetype. I
>> have another error when compiling the book. I get:
>> Sidefoothsep and sidefootwidth: 2.46019mm and 44.98633mm
>> Sidefootvsep and sidefootheight: 4.21747mm and 192.73828mm
>> **
>>
>> (/usr/local/texlive/2016/texmf-dist/tex/latex/datetime2/datetime2.sty
>> (/usr/local/texlive/2016/texmf-dist/tex/latex/tracklang/tracklang.sty
>> (/usr/local/texlive/2016/texmf-dist/tex/generic/tracklang/
>> tracklang.tex)))
>> Runaway argument?
>> \pdffeedback creationdate\@dtm@endparsepdfdatetime \let \@dtm@currentyear
>> \ETC.
>>
>> ./root/support/latex/common.tex:5: File ended while scanning use of
>> \@dtm@parse
>> pdfdatetime.
>> 
>> \par
>> l.5
>>
>>  1217 words of node memory still in use:
>>2 hlist, 1 rule, 1 dir, 34 glue, 9 attribute, 167 glue_spec, 9
>> attribute_lis
>> t, 3 write, 1 pdf_colorstack nodes
>>avail lists: 2:24,3:1,5:2,6:4,7:1,8:1,9:2
>> ./root/support/latex/common.tex:5:  ==> Fatal error occurred, no output
>> PDF fil
>> e produced!
>> Transcript written on book.log.
>> Latexmk: Errors, so I did not complete making targets
>> Collected error summary (may duplicate other messages):
>>   pdflatex: Command for 'pdflatex' gave return code 256
>> Latexmk: Use the -f option to force complete processing,
>>  unless error was exceeding maximum runs of latex/pdflatex.
>> make[1]: *** [book.pdf] Error 12
>> make: *** [build/book.pdf] Error 2
>> ~/Dropbox/Pillar>
>>
>> Is it because of some missing Latex .cls? If yes, which one? How can I
>> install them?
>>
>> Thanks for your help!
>>
>> Cheers,
>> Alexandre
>> --
>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> Alexandre Bergel  http://www.bergel.eu
>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>
>>
>>
>> On May 18, 2017, at 7:43 AM, Damien Pollet 
>> wrote:
>>
>> On 18 May 2017 at 01:34, Alexandre Bergel 
>> wrote:
>>
>>> curl https://raw.githubusercontent.com/pillar-markup/pillar/maste
>>> r/download.sh | bash
>>>
>>> I had to copy PharoV50.sources in the folder pharo-vm/ apparently.
>>>
>>
>> Hmm strange I got that this morning as well with Clément's book.
>> The script installs a PharoV60.sources so most probably it installs the
>> latest VM; might be a problem if Pillar really relies on Pharo 5…
>>
>>
>>> Getting the archetype book gives me an error:
>>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>>> /tmp/pillar> ./pillar archetype book
>>>
>>> Which website is it trying to get access to?
>>>
>>
>> That would be Inria CI, they're having problems with CloudStack currently
>>
>>
>> --
>> Damien Pollet
>> type less, do more [ | ] http://people.untyped.org/damien.pollet
>>
>>
>>
>
>
> --
> Damien Pollet
> type less, do more [ | ] http://people.untyped.org/damien.pollet
>
>
>

Re: [Pharo-dev] [Pharo-users] Need help with Pillar

[Alexandre Bergel]

I get the following:

~/Dropbox/Pillar> tlmgr update --self --all
TeX Live 2016 is frozen forever and will no
longer be updated.  This happens in preparation for a new release.

If you're interested in helping to pretest the new release (when
pretests are available), please read http://tug.org/texlive/pretest.html.
Otherwise, just wait, and the new release will be ready in due time.
tlmgr: package repository 
http://ftp.inf.utfsm.cl/pub/tex-archive/systems/texlive/tlnet (not verified: 
gnupg not available)
You don't have permission to change the installation in any way,
specifically, the directory /usr/local/texlive/2016/tlpkg/ is not writable.
Please run this program as administrator, or contact your local admin.
tlmgr: An error has occurred. See above messages. Exiting.
~/Dropbox/Pillar> 

I use the installation of TeXlive on my machine since I have no idea who to 
make the docker image use my local files.
 
Alexandre
-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.



> On May 19, 2017, at 10:06 AM, Damien Pollet  wrote:
> 
> I think you still have a TeXlive snapshot from earlier this year. Try this :
> tlmgr update --self --all
> 
> On 19 May 2017 at 15:19, Alexandre Bergel  > wrote:
> Hi Damien!
> 
> Apparently the INRIA CI is getting better. I could get the archetype. I have 
> another error when compiling the book. I get:
> Sidefoothsep and sidefootwidth: 2.46019mm and 44.98633mm
> Sidefootvsep and sidefootheight: 4.21747mm and 192.73828mm
> **
> 
> (/usr/local/texlive/2016/texmf-dist/tex/latex/datetime2/datetime2.sty
> (/usr/local/texlive/2016/texmf-dist/tex/latex/tracklang/tracklang.sty
> (/usr/local/texlive/2016/texmf-dist/tex/generic/tracklang/tracklang.tex)))
> Runaway argument?
> \pdffeedback creationdate\@dtm@endparsepdfdatetime \let \@dtm@currentyear 
> \ETC.
> 
> ./root/support/latex/common.tex:5: File ended while scanning use of 
> \@dtm@parse
> pdfdatetime.
>  
> \par 
> l.5 
>   
>  1217 words of node memory still in use:
>2 hlist, 1 rule, 1 dir, 34 glue, 9 attribute, 167 glue_spec, 9 
> attribute_lis
> t, 3 write, 1 pdf_colorstack nodes
>avail lists: 2:24,3:1,5:2,6:4,7:1,8:1,9:2
> ./root/support/latex/common.tex:5:  ==> Fatal error occurred, no output PDF 
> fil
> e produced!
> Transcript written on book.log.
> Latexmk: Errors, so I did not complete making targets
> Collected error summary (may duplicate other messages):
>   pdflatex: Command for 'pdflatex' gave return code 256
> Latexmk: Use the -f option to force complete processing,
>  unless error was exceeding maximum runs of latex/pdflatex.
> make[1]: *** [book.pdf] Error 12
> make: *** [build/book.pdf] Error 2
> ~/Dropbox/Pillar> 
> 
> Is it because of some missing Latex .cls? If yes, which one? How can I 
> install them?
> 
> Thanks for your help! 
> 
> Cheers,
> Alexandre
> -- 
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu 
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> 
> 
> 
>> On May 18, 2017, at 7:43 AM, Damien Pollet > > wrote:
>> 
>> On 18 May 2017 at 01:34, Alexandre Bergel > > wrote:
>> curl 
>> https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh 
>>  
>> | bash
>> 
>> I had to copy PharoV50.sources in the folder pharo-vm/ apparently.
>> 
>> Hmm strange I got that this morning as well with Clément's book.
>> The script installs a PharoV60.sources so most probably it installs the 
>> latest VM; might be a problem if Pillar really relies on Pharo 5…
>>  
>> Getting the archetype book gives me an error:
>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>> /tmp/pillar> ./pillar archetype book
>> 
>> Which website is it trying to get access to?
>> 
>> That would be Inria CI, they're having problems with CloudStack currently
>> 
>> 
>> -- 
>> Damien Pollet
>> type less, do more [ | ] http://people.untyped.org/damien.pollet 
>> 
> 
> 
> 
> 
> -- 
> Damien Pollet
> type less, do more [ | ] http://people.untyped.org/damien.pollet 
> 

Re: [Pharo-dev] [Pharo-users] Need help with Pillar

[Damien Pollet]

I think you still have a TeXlive snapshot from earlier this year. Try this :
tlmgr update --self --all

On 19 May 2017 at 15:19, Alexandre Bergel  wrote:

> Hi Damien!
>
> Apparently the INRIA CI is getting better. I could get the archetype. I
> have another error when compiling the book. I get:
> Sidefoothsep and sidefootwidth: 2.46019mm and 44.98633mm
> Sidefootvsep and sidefootheight: 4.21747mm and 192.73828mm
> **
>
> (/usr/local/texlive/2016/texmf-dist/tex/latex/datetime2/datetime2.sty
> (/usr/local/texlive/2016/texmf-dist/tex/latex/tracklang/tracklang.sty
> (/usr/local/texlive/2016/texmf-dist/tex/generic/tracklang/tracklang.tex)))
> Runaway argument?
> \pdffeedback creationdate\@dtm@endparsepdfdatetime \let \@dtm@currentyear
> \ETC.
>
> ./root/support/latex/common.tex:5: File ended while scanning use of
> \@dtm@parse
> pdfdatetime.
> 
> \par
> l.5
>
>
>  1217 words of node memory still in use:
>2 hlist, 1 rule, 1 dir, 34 glue, 9 attribute, 167 glue_spec, 9
> attribute_lis
> t, 3 write, 1 pdf_colorstack nodes
>avail lists: 2:24,3:1,5:2,6:4,7:1,8:1,9:2
> ./root/support/latex/common.tex:5:  ==> Fatal error occurred, no output
> PDF fil
> e produced!
> Transcript written on book.log.
> Latexmk: Errors, so I did not complete making targets
> Collected error summary (may duplicate other messages):
>   pdflatex: Command for 'pdflatex' gave return code 256
> Latexmk: Use the -f option to force complete processing,
>  unless error was exceeding maximum runs of latex/pdflatex.
> make[1]: *** [book.pdf] Error 12
> make: *** [build/book.pdf] Error 2
> ~/Dropbox/Pillar>
>
> Is it because of some missing Latex .cls? If yes, which one? How can I
> install them?
>
> Thanks for your help!
>
> Cheers,
> Alexandre
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
> On May 18, 2017, at 7:43 AM, Damien Pollet 
> wrote:
>
> On 18 May 2017 at 01:34, Alexandre Bergel  wrote:
>
>> curl https://raw.githubusercontent.com/pillar-markup/pillar/maste
>> r/download.sh | bash
>>
>> I had to copy PharoV50.sources in the folder pharo-vm/ apparently.
>>
>
> Hmm strange I got that this morning as well with Clément's book.
> The script installs a PharoV60.sources so most probably it installs the
> latest VM; might be a problem if Pillar really relies on Pharo 5…
>
>
>> Getting the archetype book gives me an error:
>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>> /tmp/pillar> ./pillar archetype book
>>
>> Which website is it trying to get access to?
>>
>
> That would be Inria CI, they're having problems with CloudStack currently
>
>
> --
> Damien Pollet
> type less, do more [ | ] http://people.untyped.org/damien.pollet
>
>
>


-- 
Damien Pollet
type less, do more [ | ] http://people.untyped.org/damien.pollet

Re: [Pharo-dev] [Pharo-users] Anyone knows how to get the list of available archetype with Pillar?

[Damien Pollet]

There is one archtype for each directory under
https://github.com/pillar-markup/Pillar-Archetype

On 19 May 2017 at 15:50, Alexandre Bergel  wrote:

> Hello!
>
> Still on my quest to use Pillar :-)
>
> What are the different Archetypes available for Pillar?
> It would be great to have: ./pillar archetype
> to obtain the list of available archetype :-)
>
> Cheers,
> Alexandre
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>

[Pharo-dev] Anyone knows how to get the list of available archetype with Pillar?

[Alexandre Bergel]

Hello!

Still on my quest to use Pillar :-)

What are the different Archetypes available for Pillar?
It would be great to have: ./pillar archetype
to obtain the list of available archetype :-)

Cheers,
Alexandre
-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Re: [Pharo-dev] [Pharo-users] Need help with Pillar

[Alexandre Bergel]

Hi Damien!

Apparently the INRIA CI is getting better. I could get the archetype. I have 
another error when compiling the book. I get:
Sidefoothsep and sidefootwidth: 2.46019mm and 44.98633mm
Sidefootvsep and sidefootheight: 4.21747mm and 192.73828mm
**

(/usr/local/texlive/2016/texmf-dist/tex/latex/datetime2/datetime2.sty
(/usr/local/texlive/2016/texmf-dist/tex/latex/tracklang/tracklang.sty
(/usr/local/texlive/2016/texmf-dist/tex/generic/tracklang/tracklang.tex)))
Runaway argument?
\pdffeedback creationdate\@dtm@endparsepdfdatetime \let \@dtm@currentyear \ETC.

./root/support/latex/common.tex:5: File ended while scanning use of \@dtm@parse
pdfdatetime.
 
\par 
l.5 
  
 1217 words of node memory still in use:
   2 hlist, 1 rule, 1 dir, 34 glue, 9 attribute, 167 glue_spec, 9 attribute_lis
t, 3 write, 1 pdf_colorstack nodes
   avail lists: 2:24,3:1,5:2,6:4,7:1,8:1,9:2
./root/support/latex/common.tex:5:  ==> Fatal error occurred, no output PDF fil
e produced!
Transcript written on book.log.
Latexmk: Errors, so I did not complete making targets
Collected error summary (may duplicate other messages):
  pdflatex: Command for 'pdflatex' gave return code 256
Latexmk: Use the -f option to force complete processing,
 unless error was exceeding maximum runs of latex/pdflatex.
make[1]: *** [book.pdf] Error 12
make: *** [build/book.pdf] Error 2
~/Dropbox/Pillar> 

Is it because of some missing Latex .cls? If yes, which one? How can I install 
them?

Thanks for your help! 

Cheers,
Alexandre
-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.



> On May 18, 2017, at 7:43 AM, Damien Pollet  wrote:
> 
> On 18 May 2017 at 01:34, Alexandre Bergel  > wrote:
> curl 
> https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh 
>  | 
> bash
> 
> I had to copy PharoV50.sources in the folder pharo-vm/ apparently.
> 
> Hmm strange I got that this morning as well with Clément's book.
> The script installs a PharoV60.sources so most probably it installs the 
> latest VM; might be a problem if Pillar really relies on Pharo 5…
>  
> Getting the archetype book gives me an error:
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> /tmp/pillar> ./pillar archetype book
> 
> Which website is it trying to get access to?
> 
> That would be Inria CI, they're having problems with CloudStack currently
> 
> 
> -- 
> Damien Pollet
> type less, do more [ | ] http://people.untyped.org/damien.pollet 
> 

Re: [Pharo-dev] Chrome DevTools Protocol and Pharo

[Reg Krock via Pharo-dev]

--- Begin Message ---
Willow Lucas-Smith worked on the WithStyle project.

She is now working at Cincom.


> On 19 May2017, at 8:03 AM, Torsten Bergmann  wrote:
> 
> If you are up to a Smalltalk internet browser then check the old
> Scamper from Squeak and H. Hirzels post + screenshot on squeak-dev from this 
> month:
> 
>   http://lists.squeakfoundation.org/pipermail/squeak-dev/2017-May/194481.html
> 
> If you want a simple morphic based internet browser I guess this could 
> be ported to Pharo.
> 
> There was also "WithStyle" in VisualWorks Smalltalk, an XML based
> UI browser built back in the days by an (australian?) company. I guess
> it is still included in the commercial VisualWorks distribution.
> Dont know about the license 
> http://forum.world.st/VW-7-5-and-WithStyle-td1408557.html
> 
> Building a webbrowser in Smalltalk would be cool - but lots of work
> (HTML + CSS parsing, JavaScript layer, drawing, ...) that would require time.
> 
> Thx
> T.
> 
> 
>> Gesendet: Freitag, 19. Mai 2017 um 03:30 Uhr
>> Von: askoh 
>> An: pharo-dev@lists.pharo.org
>> Betreff: Re: [Pharo-dev] Chrome DevTools Protocol and Pharo
>> 
>> Torsten:
>> 
>> Excellent. This is a great start towards the Smalltalk Internet Browser I
>> had envisioned. Hopefully, this integration can be made standard in Pharo
>> and other Smalltalks in many platforms. Perhaps, someone can connect all
>> Smalltalk IDEs to a cloud where the different dialects can really work
>> together in synergy - share and pool code from all sources, minimize
>> duplications, integrate local and external search, etc. Smalltalk has
>> pioneered many things in the past and there is no reason for it to stop.
>> Smalltalk makes it easier to do so and we can live up to the quote by Bob
>> Martin "Smalltalkers will, eventually, win. So says this old C++
>> programmer".
>> 
>> Thanks,
>> Aik-Siong Koh
>> 
>> 
>> 
>> --
>> View this message in context: 
>> http://forum.world.st/Chrome-DevTools-Protocol-and-Pharo-tp4947589p4947609.html
>> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
>> 
>> 
> 


--- End Message ---

Re: [Pharo-dev] bug in command line handler

[Damien Pollet]

I wouldn't want to sound sarcastic, but I'm not sure there is such a
concept as "correct" in the context of ANSI escape sequences.
Still, according to the legends, 97 is supposed to be high intensity white
(for some subset of existing implementations).

On 19 May 2017 at 12:52, K K Subbu  wrote:

> All,
>
> I found an annoying bug with Pharo's eval command line handler. When it
> encounters a syntax error, the foreground color is set to red while
> printing error message, but not restored after (see attachment). I have to
> reset it every time using "echo -e \e[0m" :-(.
>
> I found
> 
> STCommandLineHandler>>#printCompilerWarning: aSyntaxErrorNotification
> ...
> "print the marker under the error line"
>  (lineNumber == errorLine) ifTrue: [
> stderr red
> nextPutAll:( '_^_' padLeftTo: position -
> start + maxLineNumberSize + 4);
> lf ]]
> 
> The above code will leave the red color if the error happens on the last
> line (as in eval handler), then the color is never restored. Can someone
> confirm if this is indeed what is happening? I will file a case and post a
> fix, if so.
>
> I also found VTermOutputDriver uses incorrect ANSI color codes (e.g. white
> is 37 instead of 97). If the current terminal bg color happens to be
> "stderr white", then the error text is unreadable.
>
> Regards .. Subbu
>



-- 
Damien Pollet
type less, do more [ | ] http://people.untyped.org/damien.pollet

Re: [Pharo-dev] Chrome DevTools Protocol and Pharo

[Torsten Bergmann]

Yes - we should just redo what others do and show that if one uses Pharo for it
it is easier, cleaner and usually done with less effort
 

Gesendet: Freitag, 19. Mai 2017 um 03:48 Uhr
Von: "Ben Coman" 
An: "Pharo Development List" 
Betreff: Re: [Pharo-dev] Chrome DevTools Protocol and Pharo

 
 
On Fri, May 19, 2017 at 3:20 AM, Torsten Bergmann 
 wrote:Hi,

I played around with remote controlling Google Chrome from
Pharo using Chrome DevTools Protocol [1] (based on WebSockets).

The video shows an example using latest Pharo 6 on Mac:
https://www.youtube.com/watch?v=9F5FrQTEJWY[https://www.youtube.com/watch?v=9F5FrQTEJWY]

Initial Code is on GitHub [2] if someone is interested,
requires OSOSX and Zinc Websockets to be loaded.

Have fun
T.

[1] 
https://chromedevtools.github.io/devtools-protocol[https://chromedevtools.github.io/devtools-protocol]
[2] 
https://github.com/astares/Pharo-Chrome[https://github.com/astares/Pharo-Chrome]
 
This is great Torsten.  Such videos have high potential to be marketable 
outside the Pharo community.
cheers -ben 

[Pharo-dev] bug in command line handler

[K K Subbu]

All,

I found an annoying bug with Pharo's eval command line handler. When it 
encounters a syntax error, the foreground color is set to red while 
printing error message, but not restored after (see attachment). I have 
to reset it every time using "echo -e \e[0m" :-(.


I found

STCommandLineHandler>>#printCompilerWarning: aSyntaxErrorNotification
...
"print the marker under the error line"
 (lineNumber == errorLine) ifTrue: [
stderr red
nextPutAll:( '_^_' padLeftTo: position - start 
+ maxLineNumberSize + 4);
lf ]]

The above code will leave the red color if the error happens on the last 
line (as in eval handler), then the color is never restored. Can someone 
confirm if this is indeed what is happening? I will file a case and post 
a fix, if so.


I also found VTermOutputDriver uses incorrect ANSI color codes (e.g. 
white is 37 instead of 97). If the current terminal bg color happens to 
be "stderr white", then the error text is unreadable.


Regards .. Subbu

Re: [Pharo-dev] PrimitiveFailed: primitive #primLocalAddress in NetNameResolver class failed [FreeBSD]

[Petr Fischer]

It's not jail, just core FreeBSD system (I will test jails later).

Networking is still the same, Pharo 5 is OK.

/etc/hosts: 
::1ilocalhost localhost.my.domain
127.0.0.1   localhost localhost.my.domain
127.0.0.1   pf-bsd pf-bsd.localdomain pf-bsd.local

ifconfig:
em0: flags=8c02 metric 0 mtu 1500

options=4019b
ether b8:6b:23:38:f8:7d
nd6 options=29
media: Ethernet autoselect
status: no carrier
lo0: flags=8049 metric 0 mtu 16384
options=63
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
inet 127.0.0.1 netmask 0xff00
nd6 options=21
groups: lo
wlan0: flags=8843 metric 0 mtu 1500
ether 30:10:b3:77:b8:58
inet 192.168.1.3 netmask 0xff00 broadcast 192.168.1.255 
nd6 options=29
media: IEEE 802.11 Wireless Ethernet MCS mode 11ng
status: associated
ssid "pf's Network" channel 1 (2412 MHz 11g ht/20) bssid 
f0:79:59:d2:7a:00
regdomain 106 indoor ecm authmode WPA2/802.11i privacy ON
deftxkey UNDEF AES-CCM 2:128-bit AES-CCM 3:128-bit txpower 20 bmiss 7
scanvalid 60 protmode CTS ampdulimit 64k ampdudensity 4 shortgi wme
burst roaming MANUAL
groups: wlan



> 
> > On 19. May 2017, at 03:27, Petr Fischer  wrote:
> > 
> > Hello,
> 
> 
> 
> > But, this exception occurs often:
> > PrimitiveFailed: primitive #primLocalAddress in NetNameResolver class failed
> > details: https://pastebin.com/raw/bdjDW6YR
> 
> 
> How does the networking look in your jail? Which interfaces and IP addresses 
> do you have?
> 
> holger
> 
> 

Re: [Pharo-dev] Chrome DevTools Protocol and Pharo

[Graham McLeod]

Very cool. Thanks for sharing.

Graham

Torsten Bergmann wrote:

Hi,

I played around with remote controlling Google Chrome from
Pharo using Chrome DevTools Protocol [1] (based on WebSockets).

The video shows an example using latest Pharo 6 on Mac:
https://www.youtube.com/watch?v=9F5FrQTEJWY

Initial Code is on GitHub [2] if someone is interested,
requires OSOSX and Zinc Websockets to be loaded.

Have fun
T.

[1] https://chromedevtools.github.io/devtools-protocol
[2] https://github.com/astares/Pharo-Chrome




<>