https://github.com/tamerescrl/libusb-pharo

This will be a meta guide

Like pages for JSON and XML

Hello,
I would like to add a small guide about DataFrame.
Where should I put it?

I don't think it fits into External projects > Data exchange.
Perhaps External projects > Data structures?

The baseline management guide is cool but we should have a more high level guide around project management.

A guide we could send to this discussion: http://forum.world.st/What-is-the-actual-way-of-managing-code-in-Pharo-td5089943.html

• https://github.com/pharo-contributions/OSSubprocess
• OSProcess ?

This merges #6 and #7

Could be great to add a guide on Pharo convensions.

• Instance var begins with a lower case
• Class var begins with an upper case
• Classes begins with an upper case
• methods begins with a lower case
• A test package is in the form MyPackage-Tests
• A test class name is MyClassTest
• Explain conventions on some protocols
  ...

On this page, it's sometimes "Dynamic variables" and sometime "dynamic variables".
Which one should it be?

Explain how one can define and load dependencies and Metacello like Maven (for dependency management without external repositories) using just baseline: and load.

Metacello new
    baseline: #TinyBlog;
    load.

https://github.com/pharo-open-documentation/pharo-wiki/blob/master/General/Baselines.md

• PetitParser https://github.com/moosetechnology/PetitParser
• Smacc

https://github.com/svenvc/ston/blob/master/ston-spec.md

• Binary
• Buffered
• Encoding
• Newline
• Fast line reader ((ZnFastLineReader on: aStream) linesDo: [ :line | line doSomething ])
• ...

https://github.com/Metacello/metacello/blob/master/repository/Metacello-Platform.pharo60.package/MetacelloPharoPlatform.class/instance/downloadZipArchive.to..st

In cool snippets

We should add links to the Deep into pharo metacello chapter and to Metacello documentation.

They are not necessarily complete but they go deeper into some subjects.

Smalltalk ui icons inspect

1. For this repository - if you look at the pages that we already have, these are not tips and tricks.
2. For organization - GitHub organization that hosts this repository also has two awesome lists. And none of the three repositories contain actual tips and tricks.

Explain some methods to share Smalltalk code.

• VCS
• Fileout
• .st files to execute via command line
• remote workspace (via the playground)

It seems a cool project.
But I'll need help because I do not now anything about it yet ;D

Based on the comments on reddit for the 7.0 release, I think it would be good to have a "How to get started" documentation that's up to date and really simple. I had a look at Pharo by Example and it's pretty out of date (Pharo Launcher is very different now). It would be nice to have:

• Installing Pharo with Pharo Launcher (the curl/bash approaches are technical and set off alarms for people who are rightly paranoid of running scripts to install things).
• Up-to-date explanation of Pharo Launcher
• Explaining simply what is a Pharo environment: Image, VM, Package, File, Git repo. I'm not sure beginners will need the .changes files or more details. They're in the other docs anyway.
  Here's a diagram (I can attach the PlantUML source if you need) to give an idea:
  

It is currently missing the part on VM profiling.

https://hal.archives-ouvertes.fr/hal-01585754/document

https://www.youtube.com/watch?v=N-nwf9eFCTA

1 directory per theme ?

Will require to update links in README.md

For Pharo 7: https://github.com/pavel-krivanek/pharoMaterials/blob/master/Filestreams.MD

This page should go in Pharo Projects I guess

Profiling

Profiling a program is the act of measuring, for example, the time or space it takes to execute.

• Time Profiling
  • Method 1
  • Method 2
  • Method 3
• Space Profiling

Time Profiling

Method 1

If SimpleGridExample new open is the program you want to profile, run:

TimeProfiler spyOn: [ SimpleGridExample new open ]

Result: a breakdown of the methods in which the program spent time.

Method 2

If SimpleGridExample new open is the program you want to profile, inspect:

[ SimpleGridExample new open ] bench.

Result: the number of times the profiler was able to run the program per second.

Method 3

You can access a UI for the time profiler tool via the menu.

Result: type your code in the top box and click "Profile it".

Space Profiling

Imagine you want to know how much instances of the classes Point and TextMorph there are in the system, and how much space they occupy. Inspect:

((SpaceTally new spaceTally: (Array with: TextMorph with: Point)) 
	asSortedCollection: [:a :b | a spaceForInstances > b spaceForInstances])

Result:

From Philippe Back.

WorldState MinCycleLapse: 5 or 16 makes the UI more responsive.

• #streamContents:
• #do:separatedBy:
• #joinUsing: and #join:
• #splitOn: and #split:
• #format:

Master branch should only have finished and reviewed pages

We need a Manifest file that clearly explains what this repository is and what it isn't.
Is it a wiki?
Is it documentation?
Is it a place for tutorials?
Good practices?
Personal advices?
Should it copy existing books, booklets, docs?
How do we reference them?

• <script> and <script: '1 inspect'>
• <example>

others?

Hi Dario,

if you look at the end of the PharoDebug.log you will see:

Most recent primitives
doesNotUnderstand:
doesNotUnderstand:
doesNotUnderstand:
doesNotUnderstand:
doesNotUnderstand:
doesNotUnderstand:
doesNotUnderstand:
doesNotUnderstand:
doesNotUnderstand:
.......
......
doesNotUnderstand:
doesNotUnderstand:
doesNotUnderstand:
doesNotUnderstand:
doesNotUnderstand:
doesNotUnderstand:
doesNotUnderstand:
doesNotUnderstand:
doesNotUnderstand:
doesNotUnderstand:
doesNotUnderstand:

So you have a recursive doesNotUnderstand: error and the system is running
out of memory. The questions are where and why? You can try and debug
this further by running the VM with --trace=259, e.g.

pharo-vm/pharo --trace=259 my image.image

This will produce lots of output, eventually ending in an endless stream of
doesNotUnderstand:'s. So capture the first few megabytes of output (see
e.g. head(1) ($ man head))

FYI
"traceFlags is a set of flags.
1 => print trace (if something below is selected)
2 => trace sends
4 => trace block activations
8 => trace interpreter primitives
16 => trace events (context switches, GCs, etc)
32 => trace stack overflow
64 => send breakpoint on implicit receiver (Newspeak VM only)
128 => check stack depth on send (simulation only)
256 => trace linked sends "

Alternatively you could use a debugger such as gdb and I can tell you how
to put a breakpoint on doesNotUnderstand:

• How to clean the image
• How to block the acces to code
• How to change the logo of the application
• How to change the name of the application
• How to deploy a seaside application with nginx?
• How to sign the application on OSX and Windows
• ...