23 Jul
2012
23 Jul
'12
11:40 p.m.
I will soon bump into this problem. Roassal for VisualWorks and Pharo is and will remain
open source.
We will soon release the Amber version, which will then be available to the whole
JavaScript World. Should Roassal for Amber stay open source? Well... It is not clear. It
will naturally be to the Amber community, but I am not sure outside.
It would be cool to hear some experience on that topic. Maybe a "lite" version
for the whole World, and a full-fledged one as soon as you pay. This is the model
frequently used in the Mobile App.
Stef, why the INRIA guys did not come with a solution yet? I guess they have seen this
situation many times haven't they?
Cheers,
Alexandre
On Jul 23, 2012, at 5:22 PM, Stéphane Ducasse wrote:
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
+1
Now what should I use ? InMoose that I do not control, or VerveineJ.... that is not open
source ?
This is stupid but maybe, I should write mine :)
give a try to see :)
again we were planning to have a license so that verveineJ is usable for close friends.
I'm sorry but we do not want to give everything for free all the time.
Stef
Jannik
On Jul 23, 2012, at 1:28 PM, Tudor Girba wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev Sure. But, you see, even Jannik who is an Moose
insider misunderstood
the status of VerveineJ. This means we have to be more clear somehow.
I added now explicitly a line saying that there is a commercial license.
Should I remove the pointer of how to checkout the source as well?
Doru
On Mon, Jul 23, 2012 at 1:04 PM, Stéphane Ducasse
<stephane.ducasse(a)inria.fr> wrote:
---
Jannik Laval
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev For us we will continue to work on verveineJ and
the license will stay like that for a while until we know were we go.
So for us verveineJ is important because we can control it, fix it…
Stef
> Hi Jannik,
>
>>> Some questions:
>>> - is there any reason to support vervainJ instead of InFamix ? Would it make
sense to support both ?
>>
>> This is a long discussion. I know that VerveinJ works fine. It is open-soure and
well-maintained.
>> Maybe Nicolas Anquetil has already done a comparison between the two importers.
>
> Unfortunately, VerveineJ is not open-source. It is at the moment
> available to be used, but as it stands, the license is not specified
> at all. This is why the page says that you should contact Stef for
> getting information about the license. It would be great to clarify
> this point to avoid confusion in the future :).
>
>
> Cheers,
> Doru
> _______________________________________________
> 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
--
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