All Projects → SquareBracketAssociates → Updatedpharobyexample

SquareBracketAssociates / Updatedpharobyexample

Licence: other
A version of Pharo by Example for Pharo 50.

Projects that are alternatives of or similar to Updatedpharobyexample

Everything Curl
The book documenting the curl project, the curl tool, libcurl and everything related to this.
Stars: ✭ 885 (+254%)
Mutual labels:  documentation, book
Learn Vim
Learning Vim and Vimscript doesn't have to be hard. This is the guide that you're looking for.
Stars: ✭ 7,221 (+2788.4%)
Mutual labels:  book, beginner
Easybook
Book publishing as easy as it should be (built with Symfony components)
Stars: ✭ 744 (+197.6%)
Mutual labels:  documentation, book
Learn Vim
Vim 实操教程(Learning Vim)Vim practical tutorial.
Stars: ✭ 1,166 (+366.4%)
Mutual labels:  book, beginner
Rx Book
xgrommx.github.io/rx-book
Stars: ✭ 1,660 (+564%)
Mutual labels:  documentation, book
Http2 Explained
A detailed document explaining and documenting HTTP/2, the successor to the widely popular HTTP/1.1 protocol
Stars: ✭ 2,060 (+724%)
Mutual labels:  documentation, book
Ebook Template
Template to create PDF, ePub and Kindle books with Asciidoctor
Stars: ✭ 150 (-40%)
Mutual labels:  documentation, book
Book
文言陰符 An Introduction to Programming in Wenyan Language
Stars: ✭ 194 (-22.4%)
Mutual labels:  documentation, book
Create Your Own Lang With Rust
Create your own programming language with Rust (WIP)
Stars: ✭ 236 (-5.6%)
Mutual labels:  book
Vue Examples
Collection of Vue examples for beginner front end developers
Stars: ✭ 244 (-2.4%)
Mutual labels:  beginner
Go Doc Zh
Go标准库学习笔记
Stars: ✭ 238 (-4.8%)
Mutual labels:  documentation
Greenboard
📖 Gatsby theme for api documentation
Stars: ✭ 240 (-4%)
Mutual labels:  documentation
Apitome
Apitome: /iˈpitəmē/ An API documentation presentation layer for RSpec API Documentation output.
Stars: ✭ 244 (-2.4%)
Mutual labels:  documentation
Generator
Use your AsyncAPI definition to generate literally anything. Markdown documentation, Node.js code, HTML documentation, anything!
Stars: ✭ 237 (-5.2%)
Mutual labels:  documentation
Interrogate
Explain yourself! Interrogate a codebase for docstring coverage.
Stars: ✭ 245 (-2%)
Mutual labels:  documentation
Api on rails
Learn best practices to build an API using Ruby on Rails 5/6
Stars: ✭ 236 (-5.6%)
Mutual labels:  book
Docfx
Tools for building and publishing API documentation for .NET projects
Stars: ✭ 2,873 (+1049.2%)
Mutual labels:  documentation
Shins
Shins development continues at
Stars: ✭ 250 (+0%)
Mutual labels:  documentation
Awesome Algorithm Books
📚 awesome algorithm books I've collected 【不定期更新】 搜集整理的算法书籍(经典算法、ML/DL算法、面试算法、比赛算法等)
Stars: ✭ 245 (-2%)
Mutual labels:  book
Regex For Regular Folk
🔍💪 Regular Expressions for Regular Folk — A visual, example-based introduction to RegEx [BETA]
Stars: ✭ 242 (-3.2%)
Mutual labels:  book

Build Status

Introduction

Pharo by Example (vol 1) is a practical introduction for Pharo, a Smalltalk-inspired programming language, IDE and live coding enviroment. This book is an updated version of Pharo By Example for Pharo 1.4.

This version focuses on the latest stable version of Pharo (Pharo 5.0, at the time of writing).

You can find more info and documentation about Pharo at Pharo.org.

Latest Builds

The latest versions of Updated Pharo by Example can be found at the following sites:

Chapter Progress

Chapter Status Latest Link reference
1 - Preface Revised, copyedited html pdf
2 - Pharo Tour Revised, copyedited html pdf Chapter *: A Quick Tour of Pharo>../PharoTour/[email protected]:tour*
3 - A First Application Revised, copyedited html pdf Chapter *: A First Application>../FirstApplication/[email protected]:firstApp*
4- Syntax in a Nutshell Revised, copyedited html pdf Chapter *: Syntax in a Nutshell>../SyntaxNutshell/[email protected]:syntax*
5 - Understanding Messages Revised, copyedited html pdf Chapter *: Understanding Message Syntax>../UnderstandingMessage/[email protected]:messages*
6 - The Pharo Object Model Revised, copyedited html pdf Chapter *: The Pharo Object Model>../PharoObjectModel/[email protected]:model*
7 - Environment Revised, copyedited html pdf Chapter *: The Pharo Environment>../Environment/[email protected]:env*
8 - Sharing Code and Source Control Revised, copyedited html pdf Chapter *: Sharing Code and Source Control>./SharingCode/[email protected]:sharingCode*
9 - SUnit Revised, copyedited html pdf Chapter *: SUnit>../SUnit/[email protected]:sunit*
10 - Basic Classes Revised, copyedited html pdf Chapter *: Basic Classes>../BasicClasses/[email protected]:basicClasses*
11 - Collections Revised, copyedited html pdf Chapter *: Collections>../Collections/[email protected]:collections*
12 - Streams Revised, copyedited html pdf Chapter *: Streams>../Streams/[email protected]:streams*
13 - Morphic Revised, copyedited html pdf Chapter *: Morphic>../Morphic/[email protected]:morphic*
14 - Seaside By Example Needs revision html pdf Chapter *: Seaside By Example>../Seaside/[email protected]:seaside*
15 - Classes and Metaclasses Revised, copyedited html pdf Chapter *: Classes and Metaclasses>../Metaclasses/[email protected]:metaclasses*
16 - Reflection Needs revision html pdf Chapter *: Reflection>../Reflexion/[email protected]:reflection*
17 - Regular Expressions in Pharo Needs revision html pdf Chapter *: Regular Expressions in Pharo>../Regex/[email protected]:regex*

Contributing to Updated Pharo By Example (vol 1)

This book follows the fork-and-pull GitHub workflow for contributions:

  1. Fork the repository

  2. For each modification, create a quick topic branch named in the form of...

    • initials_ChapterName_my_topic_description

    example: git checkout -b dz_PharoTour_update_screen_snapshots

  3. Make commits to that branch. When you're ready, make a Pull Request

  4. The request will receive comments/corrections, and will be merged into the main repo.

More info about contributing to this book (including Pillar syntax, setting up LaTeX, etc) can be found in the CONTRIBUTING.md file.

Please send any comments, suggestions, or questions to the pharo-dev mailing list (see also the Get Help section of Pharo.org).

Style Guide

This book is written in Pillar markup. If you are not familiar with it please check the pillar-documentation. See also:

Images

Images (screenshots and diagrams) use Pillar image syntax:

+Image caption>file://figures/filename.png|width=80|label=fig:label+

For example:

+A stream positioned at its beginning.>file://figures/abcde.png|width=100|label=fig:abcde+
  • The width parameter is required (percentage of the screen).
  • Place the files in the figures directory of the chapter they are in.
  • The label should begin with fig:
  • When taking screenshots (PNG format), please compress them (you can use TinyPNG for easy and lossless compression)

To reference an image: Figure *@fig:abcde* (renders to Figure 3.8, for example).

Scripts and Code Blocks

For scripts, method definitions and other code blocks:

[[[language=smalltalk|caption=Hello World in a Transcript|label=src:helloWorld
	Transcript show: 'hello world'; cr.
]]]

Note that the label starts with src:.

To reference code blocks, use Script *@scr:helloWorld* (similar to Figures).

Chapter and Section Reference Links

Whenever you refer to other chapters of the book, please use the Pillar internal link syntax and the chapter name. (The cha: in the id is to denote that it's a chapter, to differentiate from a section id.) For example:

Chapter *: A Quick Tour of Pharo>../PharoTour/[email protected]:tour*

A list of chapter ref link code is provided, to easily copy and paste, in the Chapter Progress / table of contents above.

General Style Guidelines

Please keep in mind the following:

  • When possible, hard-wrap lines at 80 characters (e.g. Meta-Q in Emacs, Cmd-Alt-Q in Atom). This is a common open-source documentation convention, and helps with viewing GitHub-generated diffs. However, due to Pillar limitations, ordered and unordered list elements must be on a single line to be correctly parsed. Those can be left un-wrapped.
  • Only one space between sentences.
  • Avoid periods in section titles. (For example, this section is titled "Style Guide" and not "Style Guide.")
  • All inline code mentions (objects, messages, variables, packages) should use the Pillar monospace notation: ==Object==.

License

This book is licensed under a Creative Commons Attribution-ShareAlike 3.0 license.

Other Books

Deep Into Pharo (Pharo By Example vol 2)

Deep into Pharo (source code) is the second volume of a series of books covering Pharo. Whereas the first volume is intended for newcomers, this second volume covers deeper topics.

Enterprise Pharo: A Web Perspective

Enterprise Pharo: A Web Perspective (latest PDF, source code) is the third volume of the series. It covers enterprise libraries and frameworks, and in particular those useful for doing web development.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].