gemtalk / pharogs Goto Github PK

@nrgiii @Ducasse @martinmcclure @jgfoster @AllenOtis @guillep To get things rolling for the PharoGS project, I've put together a 4 phase strawman proposal for progressing towards our goal of 100% source code sharing between Pharo and PharoGs:

• PharoGs Stawman 1 Phase 1: convert current PharoGs bootstrap process to use Rowan
• PharoGs Strawman 1 Phase 2: bootstrap from Minimal PharoGs Image packages directly
• PharoGs Strawman 1 Phase 3: produce PharoGs image for Pharo and GemStone
• PharoGs Strawman 1 Phase 4: continued expansion of Pharo functionality ported to PharoGs

Please feel free to discuss/criticize/question details in each of the phase issues ... and use this issue for more general discussions/questions.

I am currently working on the initial task in Phase1 which I had promised to start working on in Cologne.

This phase of work would involve continually expanding the level of functionality that can be shared between Pharo and PharoGs. Once the Pharo Minimal Image has been ported to PharoGs, we should continue to move towards adding headful functionality to PharoGs and begin approaching the overall goal of 100% compatibility between Pharo and PharoGs

The goal of this phase is to release a pharo image that matches the functionality available in PharoGs. Ideally this would be identical to the Pharo Minimal Image, however, the expectation is that there will be some functionality in the Pharo Minimal Image that cannot/will not be implemented in PharoGs. Once a sufficient amount of functionality from the Pharo Minimal Image is functional in PharoGs, the PharoGs image can be released and developers would be expected to start developing applications against PharoGs image.

The goal of this phase is to get to the point where PharoGs can be bootstrapped from https://github.com/pharo-project/pharo packages directly. This implies that the PharoMods be converted to common code in some form or moved into PharoGs specific packages.

• merge/reconcile PharoMods into https://github.com/pharo-project/pharo
• update PharoGs bootstrap scripts to load from https://github.com/pharo-project/pharo

Convert @jgfoster work to Tonel-based packages and Rowan loading, paving the way for eventually loading from Pharo repositories directly into PharoGs.

• convert PharoMods to Tonel
• specify PharoGs method environment in Rowan
• convert the ./exportFromPharo.sh; ./importToGemStone.sh to directly load pharo minimal image packages from https://github.com/pharo-project/pharo

The Pharo folks want to analyze the pharo mods made by @jgfoster and the best way to do that is to convert the .gs files to tonel packages.

The plan is to adapt GsFileIn (a .gs file reader) to convert methods to Rowan extension method definitions and then write out the packages. I plan to follow the approach used by @AllenOtis to convert the GemStone bootstraping .gs files to Rowan packages for GemStone 3.6.

• rowanize AnalyzeFileIn.gs
• refactor to meet PharoMods .gs conversion needs (just extension methods and single target package)
• generate PharoMods package

PharMods package can be found here: utilities/src/PharoMods-Core