[Pharo-dev] Roassal Question

Tudor Girba tudor at tudorgirba.com
Wed Nov 27 05:34:12 EST 2013


I am glad you want to read about Roassal.

My mail was about exposing people that want to get answers to other people
that want to provide those answers. And my suggestion was based on the fact
that in the moose mailing list there are likely more people that can answer
Roassal questions than there are in the Pharo-dev mailing list.

As for PetitParser, there is not engrossment happening. It's the opposite.
The Moose team as a whole takes charge of maintaining PetitParser and makes
it even available as standalone. And I said it before that if you or
someone else wants to put the effort in maintaining packages like
PetitParser, there is no problem of moving it out of the Moose team.

Cheers,
Doru


On Wed, Nov 27, 2013 at 9:11 AM, Norbert Hartl <norbert at hartl.name> wrote:

>
> Am 27.11.2013 um 07:06 schrieb Tudor Girba <tudor at tudorgirba.com>:
>
> Perhaps it would be more useful to have these types of discussions on the
> moose-dev mailing list. You might be surprised by other things you might
> find there :)
>
> I disagree with the first sentence. I like to read Roassal stuff here in
> this list. I’m not subscribed in the moose mailing list (trying to reduce
> the mails I get) but I would like to be up to date with Roassal that has
> use case scenarios that exceed the bounds of moose. And I don’t like the
> tension that moose is engrossing standalone packages (like petit parser ;) )
>
> Norbert
>
> In case of interest, here are the coordinates:
> http://www.moosetechnology.org/about/contact
>
> Cheers,
> Doru
>
>
>
>
> On Tue, Nov 26, 2013 at 8:59 PM, Alexandre Bergel <alexandre.bergel at me.com
> > wrote:
>
>> Excellent! Let us know for any request for enhancement or bug fixes.
>>
>> Cheers,
>> Alexandre
>> --
>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> Alexandre Bergel  http://www.bergel.eu
>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>
>>
>>
>> On Nov 26, 2013, at 4:20 PM, GOUBIER Thierry <thierry.goubier at cea.fr>
>> wrote:
>>
>> > Yes! I also found there is a ROPlatform thing I can query (not sure,
>> the code is at work and I'm home).
>> >
>> > (I'm coupling a C ast + CFG + parallel task analysis displayed with
>> Roassal with interaction with the source code under analysis on a text
>> pane. I demoed it this morning to our partner)
>> >
>> > Thierry
>> > ________________________________________
>> > De : Pharo-dev [pharo-dev-bounces at lists.pharo.org] de la part de
>> Alexandre Bergel [alexandre.bergel at me.com]
>> > Date d'envoi : mardi 26 novembre 2013 17:56
>> > À : Pharo Development List
>> > Objet : Re: [Pharo-dev] Roassal Question
>> >
>> > Does the following helps?
>> > -=-=-=-=-=-=-=-=-=-=-=-=
>> > | view  shape morph |
>> > view := ROView new.
>> > 100 timesRepeat: [
>> >        shape := ROEllipse new size: 40; color: (Color green alpha: 0.5).
>> >        view add: shape element ].
>> > view elements do: [ :el | el translateTo: 500 atRandom @ 500 atRandom ].
>> >
>> >
>> > morph := ROAthensMorph on: view.
>> > morph extent: 500 @ 500.
>> > morph openInWindow
>> > -=-=-=-=-=-=-=-=-=-=-=-=
>> >
>> > If you do not use Athens, then replace “ROAthensMorph” by “ROMorph”
>> >
>> > Alexandre
>> >
>> > --
>> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> > Alexandre Bergel  http://www.bergel.eu
>> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>> >
>> >
>> >
>> > On Nov 26, 2013, at 12:51 PM, Goubier Thierry <thierry.goubier at cea.fr>
>> wrote:
>> >
>> >> Hi all,
>> >>
>> >> does anybody knows how to integrate a ROView inside a Morphic GUI ?
>> >>
>> >> Regards,
>> >>
>> >> Thierry
>> >> --
>> >> Thierry Goubier
>> >> CEA list
>> >> Laboratoire des Fondations des Systèmes Temps Réel Embarqués
>> >> 91191 Gif sur Yvette Cedex
>> >> France
>> >> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
>> >>
>> >
>> >
>> >
>>
>>
>>
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
>
>
>


-- 
www.tudorgirba.com

"Every thing has its own flow"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20131127/a9fdbf4d/attachment-0002.html>


More information about the Pharo-dev mailing list