This document discusses the key challenges for Pharo 70 including cleaning and stabilizing the codebase, supporting 64-bit systems, adopting Iceberg for version control, managing Pharo on GitHub, retiring the Nautilus browser in favor of Calypso and Commander, improving the class definition system, and developing Opal and PharoPro services. It proposes a new "ClassParser" node-based system to handle class definitions and avoid combinatorial explosions, and notes that Pharo 70 is an exciting release with many possibilities for contributions.

1. Pharo 70
The key challenges
S. Ducasse for the RMoD Team

2. Points
• Cleaning and stabilising
• 64 bits windows/large images
• Iceberg in production
• Pharo managed on github
• Bootstrap in production
• Retirement of Nautilus -> Calypso + Commander
• New class definition
• Cargo

3. Nautilus

4. Calypso
• Thanks alain for giving us the name

5. Calypso & its submarines

6. Calypso
• Basis for Remote Browsing
• Fully extensible
• No ifs
• Developed by D. Kudriashov
• Thanks alain for giving us the name

7. Calypso
• multiple panes
• multiple method definitions
• incomplete method definitions
• scoping…

8. Calypso
• mulitple panes
• multiple method definitions
• incomplete method definitions
• scoping…

9. New Message Browser

10. Iceberg
• Paid by the consortium
• libgit2

11. Iceberg
• Potentially for
• Fossil
• Mercurial

13. Pharo on github

14. About classes

15. Class definition explosion
• subclass:, variableSubclass:, variableByte.. variableWord, weak:
• uses:
• layout:
• tag:
• immediate:, ephemeron
• category:
• package:
• slot:
• instanceVariableNames:, classVariableNames:

16. Need a fluid API
• Only specify what is used!
• No empty classVariableNames: ‘’
• Handling combinatorial explosion
Class <<< #Box
vars: { #width . #height };
package: #MyPackage.

17. Possible Designs
Class {
superclass: #MySuperclass;
uses: #MyTrait;
vars: { #a. #b };
classVars: { #A. #B };
package: #MyPackage;
tags: #(Core).
}
Class <<< #MyClass
superclass: #MySuperclas;
uses: #MyTrait;
vars: { #a. #b };
classVars: { #A. #B };
package: #MyPackage;
tags: #(Core)

18. Need a class **definition**
• a.k.a. AST
• traits, slots, kinds….
• Can be manipulated
• Support for Smart Suggestions
• Need to be able to have **undefined** classes
• Important for modules!

19. Working on a “ClassParser”
+ Nodes
• Can handle variations, backward compatibles….
• Support for smart suggestion in class definition
• Avoid ‘*subclass:*’ matches: str

20. Opal
• Warnings into real objects
• Another pass on the API

21. PharoPro
More services around the consortium
• Long Term Support (LTS)
• Platform Support: CentOS, NetBSD, FreeBSD
• Pharo Hotline
• Custom Development

22. Pharo 70 is exciting
We are excited by the possibilities
You can help, contribute and have fun with us