For ConfigurationOfRoelTyper it is safe to use #stable.
The configurationOfOrderPreservingDictionary had a broken baseline
with a numbered version in it. I removed the broken baseline and
changed the reference to it. It is now safe to use stable
Stephan
Hi!
I am slowly integrating feature of the GraphBuilder into the (new) Mondrian builder. Normalizer and the partition are supported by RTMondrian now.
Here is a small example:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
classes := RTLayout withAllSubclasses, RTBuilder withAllSubclasses, RTShape withAllSubclasses.
b := RTMondrian new.
b shape circle size: 5.
b nodes: classes.
b edges connectFrom: #superclass.
b normalizer
objects: classes;
normalizeSize: #numberOfMethods min: 5 max: 30;
normalizeColor: #numberOfLinesOfCode using: { Color green . Color red } using: #sqrt.
b layout
for: [ :c | c includesBehavior: RTLayout ] use: RTForceBasedLayout new;
for: [ :c | c includesBehavior: RTBuilder ] use: RTForceBasedLayout new;
for: [ :c | c includesBehavior: RTShape ] use: RTForceBasedLayout new;
flow.
b
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Christophe wrote
>Once Versionner has this baseline version, it resolves all kind of symbolic versions to the numbered versions for the release
>(but still keep the symbolic version in the baseline to use for dev version and next releases).
You don't want numbered versions for the parts you don't control. There you want patches to be possible.
Dependent projects always need to be referred to by symbolic name. Dependent project are volatile
information.
https://www.cs.utexas.edu/users/EWD/ewd07xx/EWD719.PDF
In Moose, there are at any time a few sub projects that are very active and are very likely to break very
soon after (or even at) release. At the moment, that could be PetitParser and Roassal2. As we'll move
to Pharo4 straight after this release, the development version is going to be fragile for a while.
If we want to be able to patch active projects, we need symbolic versions to make sure that patch
versions don't need to propagate to the configurations using them.
Stephan
I've checked and changed to have stable versions:
ConfigurationOfFame
ConfigurationOfMetanool
ConfigurationOfGlamour now uses a release version of Magritte3
but has no stable yet.
Stephan
>No. We will create a stable version of each configuration that will be versioned based on the numbering of each configurations.
Last time I was not so happy with the results of using numbered configurations. The release version stopped being usable about
a week after the release date. With a symbolic name we can fix critical bugs that stop newcomers from using Moose.
Last time we had a development version that didn't work because of significant Pharo3 surgery and a stable version that
couldn't be build because of numbered configurations. If possible I would like to avoid that this time.
Stephan
Christophe wrote:
>Maybe you could use Versionner for that.
>If your configuration depends on a #stable version, Versionner can resolve this (check box activated by default) when releasing a new version.
>Versioner do not have a deep release functionality but it should not be difficult to do if needed; At a time, I created the VSConfigurationGeneratorCommand (in Versionner repo in SH) that follows all the >dependencies of a project.
For that we'd need Versionner to support groups and platforms.
We have dependencies on Grease and Magritte3
Stephan
Hi Doru,
I'd like to make transparant what needs to be done
to release Moose 5.0, so I'll write down the steps I
take.
First step is deciding which configurations need to be
changed, and what needs to be done with them.
In Moose we have the following 34 configurations:
ConfigurationOfAnnouncerCentricDebugger
ConfigurationOfBitmapCharacterSet
ConfigurationOfCommandShell
ConfigurationOfDeepTraverser
ConfigurationOfFame
ConfigurationOfGTDebugger
ConfigurationOfGTInspector
ConfigurationOfGTInspectorCore
ConfigurationOfGTPlayground
ConfigurationOfGTPlaygroundCore
ConfigurationOfGTSpotter
ConfigurationOfGToolkit
ConfigurationOfGlamour
ConfigurationOfGlamourCore
ConfigurationOfGrease
ConfigurationOfHashTable
ConfigurationOfMagritte3
ConfigurationOfMerlin
ConfigurationOfMetanool
ConfigurationOfMoose
ConfigurationOfMooseAlgos
ConfigurationOfNewDebugger
ConfigurationOfOSProcess
ConfigurationOfOrderPreservingDictionary
ConfigurationOfPastell
ConfigurationOfPetitParser
ConfigurationOfPetitSQLParser
ConfigurationOfPhexample
ConfigurationOfRoassal2
ConfigurationOfRoelTyper
ConfigurationOfRubric
ConfigurationOfSmallDude
ConfigurationOfXMLParser
ConfigurationOfXMLWriter
In Pharo3 30860 there are no configurations.
Of those, the maintained ones I know not under Moose control are:
ConfigurationOfCommandShell
ConfigurationOfGrease
ConfigurationOfMagritte3
ConfigurationOfOSProcess
ConfigurationOfXMLParser
ConfigurationOfXMLWriter
I assume there are a few more. Which ones?
In those I'd suggest to not add the #'moose5.0' but pick the met fitting
current version.
Grease and Magritte3 already have named versions, so we can simply refer to
Magritte3 #'release3.2'
Grease #'release1.1'
that contains the same packages as #development=version3.1.5
CommandShell loads version469 which has a numbered OSProcess version 4.5.12
the #stable version refers to 469 so can be used.
The baseline of CommandShell looks broken.
to be continued
Stephan
Hi,
I need help with creating the stable 5.0 version in the configurations.
I wanted to get to extend the Spanshotcello, but unfortunately, I did not
manage to do it and the time is since long up. So, we should just do it
manually, but for that I need help.
Who can provide it?
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
Hi to all,
Try the next piece of code:
RTHTML5ExporterExample new exportAll.
Wait.
Wait again (maybe you can drink a cup of coffe)
Then open the generated file index.html to see the exported examples, this
is only the beginning, there are a lot of work on this exporter.
This exporter aims recreate the visualization of Pharo in HTML with all
their interactions.
Cheers,
Milton
