Improving Pharo By Example
Locked
12345
12345
 
|
On 06 May 2014, at 21:26, Damien Cassou <[hidden email]> wrote: > Yuriy, maybe the script could check if pdflatex is present and if not, > ignore the pdf generation? The pdf will be generated by the build > server so we don't really care. Moreover, one of the goals doing > pillar was to avoid asking everyone to install LaTeX which is quite > large. What do you think? I completely agree. I’ll try to take a look as soon as I have some time. Uko > > > On Sat, May 3, 2014 at 10:53 AM, kilon alios <[hidden email]> wrote: >> Ok Nicolas I followed its advice and it looks like you are correct.Wget get >> error on make but make install seemed to worked. >> >> But >> >> I am getting an error connecting to the servers is Inria servers down today >> ? >> >> this is the error >> >> kilon-imac:UpdatedPharoByExample kilon$ ./download.sh >> >> --2014-05-03 11:49:15-- >> https://ci.inria.fr/pharo-contribution/job/Pier3BookOnPharo20/lastSuccessfulBuild/artifact/Pier3BookOnPharo20.zip >> >> Resolving ci.inria.fr... 193.51.193.223 >> >> Connecting to ci.inria.fr|193.51.193.223|:443... connected. >> >> HTTP request sent, awaiting response... 404 Not Found >> >> 2014-05-03 11:49:16 ERROR 404: Not Found. >> >> >> Yuriy thanks for the advice I have command line tools because I am building >> Blender the 3d open source app on my iMac. I tried before installing wget >> with homebrew it failed too. >> >> >> >> On Fri, May 2, 2014 at 3:25 PM, Yuriy Tymchuk <[hidden email]> wrote: >>> >>> There is some black magic with wget. I think you have to install command >>> line tools which get uninstalled on every update. Also if I remember >>> correctly, I've installed it with home-brew. >>> >>> Uko >>> >>> On 02 May 2014, at 13:15, kilon alios <[hidden email]> wrote: >>> >>> Thank you Yuriy >>> >>> I have tried to follow the installation instructions before on my iMAC but >>> I was not successful installing wget. I tried building wget myself and it >>> failed with errors, I tried using a binary of wget that I found online that >>> failed too. >>> >>> But I will give it another try today when I get home where my macs are and >>> share with you the exact errors I am experiencing. >>> >>> >>> On Fri, May 2, 2014 at 1:29 PM, Yuriy Tymchuk <[hidden email]> >>> wrote: >>>> >>>> Hi. >>>> >>>> Here is a repo for updated version of Pharo by example >>>> https://github.com/SquareBracketAssociates/UpdatedPharoByExample and it >>>> should be done in Pillar. >>>> >>>> I've added you to the team, so feel free to contribute. >>>> >>>> Uko >>>> >>>> >>>> On 02 May 2014, at 12:22, kilon alios <[hidden email]> wrote: >>>> >>>>> How I can help improve Pharo by Example , add chapters and update >>>>> current ones for Pharo 3 ? >>>>> >>>>> What is the process ? >>>> >>>> >>> >>> >> > > > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > |
|
Thanks for the help Uko just for your information emacs pillar mode gives me errors on make && make install "In end of data:
package-build.el:1197:1:Warning: the following functions are not known to be defined: package-desc-extras, package-desc-name, package-desc-summary, package-desc-version Wrote /Users/kilon/.emacs.d/.cask/24.3.1/bootstrap/package-build-20140427.357/package-build.elc Done (Total of 3 files compiled, 1 skipped) Cannot open load file: subst-ksc make: *** [pillar.elc] Error 255" I opened a pillar file it says its opened on Git-master (LaTex W) On Tue, May 6, 2014 at 11:30 PM, Yuriy Tymchuk <[hidden email]> wrote:
|
|
|
ok I made my first commit just now I added the Preface chapter, looks ok. Just the first page. It asked me to merge my commit, dont know why, I hope I did not mess anything up, I am not very experienced with git so bare with me.
I have 2 questions a) The page I am porting from PBE has a footnote, does Pier have a syntax for footnotes ? b) Why Pier does not wrap text ? On Tue, May 6, 2014 at 11:49 PM, kilon alios <[hidden email]> wrote:
|
|
|
On 06 May 2014, at 23:45, kilon alios <[hidden email]> wrote:
Everything is fine. I’ve made some big changes, that’s why it asked for merge.
As far as I know, for now it’s not supported.
What do you mean by this? Uko
|
|
|
Wraping text is basically aligning text to the edges of the window. Text remains aligned even when the window gets resized.If you look at PBE pdf you will see its wraped. It definetly makes text look better. Wraped text is also known as justified text. Στις 7 Μαϊ 2014 1:24 π.μ., ο χρήστης "Yuriy Tymchuk" <[hidden email]> έγραψε:
|
|
|
For me it is like that: https://space.zeo.net/g/d639
On 07 May 2014, at 00:32, kilon alios <[hidden email]> wrote:
|
|
|
What the ..... Στις 7 Μαϊ 2014 1:39 π.μ., ο χρήστης "Yuriy Tymchuk" <[hidden email]> έγραψε:
|
|
|
By the way is your link the pdf or the html version ? Cause I was talking about html version. What the ..... Στις 7 Μαϊ 2014 1:39 π.μ., ο χρήστης "Yuriy Tymchuk" <[hidden email]> έγραψε:
|
|
|
On 07 May 2014, at 00:48, kilon alios <[hidden email]> wrote:
True. Will put on ToDo list.
|
|
|
In reply to this post by kilon.alios
On Wed, May 7, 2014 at 12:48 AM, kilon alios <[hidden email]> wrote:
> By the way is your link the pdf or the html version ? Cause I was talking > about html version. that's just a CSS thing then. I guess each author has to choose whether they want justification or not. By default, Pillar uses bootstrap to format the HTML document. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill |
|
|
In reply to this post by kilon.alios
On Tue, May 6, 2014 at 10:49 PM, kilon alios <[hidden email]> wrote:
> just for your information emacs pillar mode gives me errors on make && make > install in Emacs, you don't have to execute make at all. Just do M-x package-install and select Pillar. If Pillar is not in the list, you need to read http://melpa.milkbox.net/#/getting-started -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill |
|
|
ok here is my latest commit log "finished the Preface chapter, looks ok , but I may make corrections later on. I removed a dead link and also removed tooltip icon from original PBE cause it display it in seperate space from the text so it does not work as it should. Please note also that I found a bug with todo annotation @@ it keeps outputing to html though it should not. Another thing to note as I have informed people in irc is that paragraphs do not intend as they should(space in front of them) in html output. I have also add additional info for the Pharo community like irc, and stackoverflow. I have replaced the reference to squeak source with smalltalkhub and I did some other minor corrections here and there that should be evident by the commit log."
so Preface chapter is finished, moving on to next chapter. Will keep an eye on this one to make sure it has no errors inside.
On Wed, May 7, 2014 at 12:06 PM, Damien Cassou <[hidden email]> wrote:
|
|
|
also please note that link you provide in Github readme in "This book is continuously built on an Inria Jenkins server." is dead it would be nice to have access to the build and the pdf version :)
On Wed, May 7, 2014 at 6:26 PM, kilon alios <[hidden email]> wrote:
|
|
|
I don’t think that it’s being built now. That’s one more thing on TODO list.
Uko
On 07 May 2014, at 17:39, kilon alios <[hidden email]> wrote:
|
|
|
In reply to this post by stepharo
Yes I think reducing screenshots makes sense, especially the ones that do not directly explain the tools. Reducing them will make it easier to update PBE in the future. I am also very interested in automating the screenshot process as has been suggested in another thread, if we able to do this that will reduce the time to update PBE in future massively. I will try to simplify PBE so its much easier to update without sacrificing quality for the viewer. Obviously screenshots are essential. I am also viewing your TODO you have linked on the Readme.
I have updated the Readme so that links to Damien's Documentation of Pillar and also to Pharo for the Enterprise , obviously anyone who wants to contribute must be aware of both of these things.
I also added Chapter 1 - Quick Tour in Pharo. Just the first part , the chapter is of course still a WIP. I am not so sure what you mean about automated tests, are they for the example code ?
I am all for automation. On Mon, May 5, 2014 at 11:08 PM, stepharo <[hidden email]> wrote: This is really cool that people want to update the Pharo by Example book. |
|
|
Ok, so for now updated PBE should not complain about absence of pdflatex
Uko On 07 May 2014, at 21:10, kilon alios <[hidden email]> wrote:
|
|
|
indeed it does not. Tried it no mention of pdflatex. however I am getting loads of warnings , even before your commit I assume you guys are aware of this, but just in case
"./compile.sh
Generating files for all chapters The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete *** Warning: Deprecation: The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete *** Warning: Deprecation: The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete *** Warning: Deprecation: The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete *** Warning: Deprecation: The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete *** Warning: Deprecation: The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete *** Warning: Deprecation: The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete *** Warning: Deprecation: The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete *** Warning: Deprecation: The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete *** Warning: Deprecation: The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete *** Warning: Deprecation: The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete Done kilon-imac:UpdatedPharoByExample kilon$ ./compile.sh Generating files for all chapters The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete *** Warning: Deprecation: The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete *** Warning: Deprecation: The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete *** Warning: Deprecation: The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete *** Warning: Deprecation: The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete *** Warning: Deprecation: The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete *** Warning: Deprecation: The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete *** Warning: Deprecation: The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete *** Warning: Deprecation: The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete *** Warning: Deprecation: The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete *** Warning: Deprecation: The method AbstractFileReference>>ensureDeleted has been deprecated. Use ensureDelete Done kilon-imac:UpdatedPharoByExample kilon$ " On Wed, May 7, 2014 at 10:50 PM, Yuriy Tymchuk <[hidden email]> wrote:
|
|
|
In reply to this post by kilon.alios
if you see in the tex when we have example we also have a tag that indicates that the code can be extracted and run. I do not remember but oscar did a script and we where able to automatically verify that all the simple examples were correctly working with a version of Pharo. Now in Pillar we should introduce the notion of tag to support at the word level. - index - comment - citation
|
|
|
I found a bug in Pillar syntax when I type 3 + 4 , it seems like it takes + as part of the pillar syntax and uses latex syntax and when it tries to generate the pdf it fails so I am forced now to type it as raw text like this : {{{3+4}}}
also I would like the ability to have a dark background for text like we do with smalltalk syntax . Pharo Tour chapters proceeds well, I compile to both latex html and pdf , I see no problems so far with my text, I copy my text directly from the latex files of the original PBE in github.
I also improved the Readme. On Thu, May 8, 2014 at 9:16 AM, stepharo <[hidden email]> wrote:
|
|
|
On 10 May 2014, at 17:01, kilon alios <[hidden email]> wrote:
It’s not a bug, it’s a feature :). I’d suggest you to use something like ==inline code== for wrapping of ‘’italic’'.
I don’t really understand what you need. If you need to style the result, it should be done outside of pillar.
|
«
Return to Pharo Smalltalk Developers
|
1 view|%1 views
| Free forum by Nabble | Edit this page |