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
Hi, all
I have a little ruby_test.rb file whit this content.
=begin
hey this
is a
block comment.
=end
# Ruby knows what you
# mean, even if you
# want to do math on
# an entire Array
cities = %w[ London
Oslo
Paris
Amsterdam
Berlin ]
visited = %w[Berlin Oslo]
puts "Hey #{cities.first}"
puts "I still need " +
"to visit the " +
"following cities:",
cities - visited
the output is:
nelson@LinuxDev:~/projects/smalltalk/pharo3.0/shared$ ruby ruby_test.rb
Hey London
I still need to visit the following cities:
London
Paris
Amsterdam
-------------------
in Pharo:
result := RubyGrammar parseFile:'ruby_test.rb'.
the output is:
'%w[ London Oslo Paris Amsterdam Berlin ]'
'%w[Berlin Oslo]'
'""Hey #{cities.first}""'
'""I still need ""'
'""to visit the ""'
'""following cities:""'
but the last instruction doesn't appear "cities - visited"
2014-12-02 9:56 GMT-04:00 Juraj Kubelka <juraj.kubelka(a)gmail.com>:
> Great! Let us know about your progress and thoughts :-)
>
> Juraj
>
> On Dec 2, 2014, at 10:55 AM, Nelson Garcia <nelsongarcia.info(a)gmail.com>
> wrote:
>
> thanks Juraj, now I can explore the code.
>
> On 12/02/2014 06:09 AM, Juraj Kubelka wrote:
>
> Hi Nelson,
>
> check this page: http://smalltalkhub.com/#!/~radi/RubyParser
>
> There is:
> <Mail Attachment.png>
> This code you can copy and in Pharo, you can use Monticello tool which
> have a button “+Repository”, here you chose smalltalkhub from the menu and
> paste the code from the page.
>
> I think there is a chapter in the book about Monticello. Here you can
> find more details.
>
> Cheers,
> Juraj
>
>
> On Dec 1, 2014, at 11:47 PM, Nelson Garcia <nelsongarcia.info(a)gmail.com>
> wrote:
>
> Hi, all
>
> How can I check the code of this repository
> http://smalltalkhub.com/mc/radi/RubyParser/main?
>
> do I need some permission?
>
> On 12/01/2014 02:27 PM, Juraj Kubelka wrote:
>
> Sí, no dudas de preguntar!
>
> Que estás bien,
> Juraj
>
> On Dec 1, 2014, at 12:50 PM, Alexandre Bergel <alexandre.bergel(a)me.com>
> wrote:
>
> Cualquier duda, pregunta!
>
> Alexandre
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
> On Dec 1, 2014, at 12:19 PM, Nelson Garcia <nelsongarcia.info(a)gmail.com>
> wrote:
>
> Hola Alexandre,
>
> gracias por incluirme en este proyecto. continuare leyendo el libro de
> moose y probaré el código de Jan Kurs y Oscar.
>
>
> On 12/01/2014 10:25 AM, Alexandre Bergel wrote:
>
> Hola Nelson,
>
> Jan Kurs and Oscar son de Suiza, en una buena unversidad. Es importante
> que colaboras con ellos. La cosa que puedes hacer por ahora, es probar el
> código que ellos han hecho.
>
> Avisanos como va. Es importante
>
> Saludos,
> Alexandre
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
> Begin forwarded message:
>
> *Date: *December 1, 2014 at 10:35:01 AM GMT-3
> *From: *Jan Kurš <kurs(a)iam.unibe.ch>
> *To: *Jan Kurš <kurs(a)iam.unibe.ch>
> *Cc: *Moose-related development <moose-dev(a)iam.unibe.ch>, Nelson Garcia <
> nelsongarcia.info(a)gmail.com>, Rathesan Iyadurai <
> rathesan(a)students.unibe.ch>
> *Subject: **[Moose-dev] Re: Analyzing Ruby*
> *Reply-To: *Moose-related development <moose-dev(a)iam.unibe.ch>
>
> Hey All,
>
> Indeed, we have a student working on extracting class names and method
> names from Ruby code using PetitParser. So far, you can find the project
> here:
>
> http://smalltalkhub.com/#!/~radi/RubyParser
>
> Do you plan to use PetitParser, hand written parser or some other
> framework?
>
> Cheers,
> Jan
>
> On 1 December 2014 at 14:29, Jan Kurš <kurs(a)iam.unibe.ch> wrote:
>
>> Hey All,
>>
>> Indeed, we have a student working on extracting class names and method
>> names from a ruby code. So far, you can find the project here:
>>
>>
>> On 1 December 2014 at 10:12, Oscar Nierstrasz <oscar.nierstrasz(a)gmail.com
>> > wrote:
>>
>>>
>>> Hi Folks,
>>>
>>> Please talk to Jan Kurs (in CC). We have a student now exploring how to
>>> use island grammars to define an exporter. Our goal is not to produce a
>>> finished product, but to evaluate our island parser tech, but still it may
>>> be useful to sync.
>>>
>>> Cheers,
>>> Oscar
>>>
>>>
>>> > On 30 Nov 2014, at 14:09 , Tudor Girba <tudor(a)tudorgirba.com> wrote:
>>> >
>>> > Hi Nelson,
>>> >
>>> > Welcome!
>>> >
>>> > Thanks for taking this project up. Indeed, this would be a very
>>> valuable addition to the Moose ecosystem. Please ask questions and we will
>>> support you.
>>> >
>>> > Cheers,
>>> > Doru
>>> >
>>> >
>>> >
>>> > On Sun, Nov 30, 2014 at 2:06 PM, Alexandre Bergel <
>>> alexandre.bergel(a)me.com> wrote:
>>> > Hi!
>>> >
>>> > Nelson is an excellent student from Bolivia. We met Nelson at the
>>> summer school (sponsored by ESUG) that we organized.
>>> > Nelson would like to write an MSE exporter for Ruby. Analyzing Ruby
>>> applications in Moose is indeed important.
>>> >
>>> > Nelson, as a starting point how how to produce MSE file, you can have
>>> a look at
>>> > - http://www.themoosebook.org/book
>>> http://www.themoosebook.org/book/externals/import-export/mse
>>> > - Try out with .mse file example. You can easily generate one
>>> by importing Pharo code in Moose (
>>> http://www.themoosebook.org/book/externals/import-export/smalltalk) and
>>> export it by right clicking on a model
>>> >
>>> > Ask for help in the mailing list. People are waiting for your tool :-)
>>> >
>>> > Cheers,
>>> > Alexandre
>>> > --
>>> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>>> > Alexandre Bergel http://www.bergel.eu
>>> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>> >
>>> >
>>> >
>>> >
>>> > _______________________________________________
>>> > Moose-dev mailing list
>>> > Moose-dev(a)iam.unibe.ch
>>> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>> >
>>> >
>>> >
>>> > --
>>> > www.tudorgirba.com
>>> >
>>> > "Every thing has its own flow"
>>> > _______________________________________________
>>> > Moose-dev mailing list
>>> > Moose-dev(a)iam.unibe.ch
>>> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>
>>>
>>
> _______________________________________________
> Moose-dev mailing list
> Moose-dev(a)iam.unibe.ch
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
>
>
>
>
>
>
>
>
Hi,
I’ve just downloaded roassal2 image from https://ci.inria.fr/moose/job/roassal2/ <https://ci.inria.fr/moose/job/roassal2/>. Problem is next.
On the CI server Roassal2 is loaded into Pharo3 image. But if you open it, there are some problems, as GT inspector is not present there. I could just make it to load into pharo 4 image, or make a matrix job. But I want to rise attention, because this is a sign that roassal conf. loads broken things…
Uko
Hi!
I played a bit this morning. This is the whole Pharo:
A detail of this picture:
There are over 100 000 methods and over 65 000 edges.
Each circle is a method. Color of the method indicates its class. Edges are self-call between methods (e.g., a method "foo ^ self bar” will creates a link between #foo and #bar.
The very short script to produce it and a large version of the pictures are available on: https://www.facebook.com/ObjectProfile/posts/742756179144315
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi,
I am executing disharmony codecity example with the properties #isGodClass,
#isBrainClass and #isDataClass. However, the properties return Nil and in
the documentation we have: return nil if the property does not exist. I have
some questions:
1- Where these properties are calculated? I have not found!
2- Where can I find the list badsmells implemented in codecity?
3- I would like implement new properties for disharmony codecity, Where to
start?
My test code is this:
Thanks!
--
View this message in context: http://forum.world.st/Disharmony-codecity-example-The-properties-return-Nil…
Sent from the Moose mailing list archive at Nabble.com.
Hi,
Despite of my advances studying Glamorous Toolkit and making some
advances on "apps" and interfaces, I really don't understand well the
concept of ports and auto-update of values. So I started with a small
excercise from the transcript example as proposed in the GT blog[1]. Its
working as expected, so try to extend the example with a code that shows
my incomplete understanding at [2]. My idea was to create a two panels
browser showing an array. Left panel show a list, and right one was a
text with the selected value of the list. When the values at the right
were updated the list at the left was updated also. Because this was not
working I create a Transcript trying to show if changes on the right
where captured. I have seen the three inter-dependant panes example,
but still I don't get it right. So my questions are:
[1] http://ws.stfx.eu/L277ESMZYIF3
[2] http://ws.stfx.eu/1FOA0OWJ8PWA
a) How can I send the changes in values from the right panel to the one
of the left?
Thanks,
Offray
