Roassal on Bloc on not Pharo

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

Roassal on Bloc on not Pharo

Peter Uhnak
Hi,

I am wondering... how will moving Roassal to Bloc affect other platforms such as VisualWorks? Because it seems it would be unportable with Bloc, no?

Peter

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Roassal on Bloc on not Pharo

Tudor Girba-2
The right direction is to make things work on Bloc and commit to this platform 100%. This will make things simpler and will take advantage of what Bloc offers.

Doru

On Fri, Jul 31, 2015 at 1:50 PM, Peter Uhnák <[hidden email]> wrote:
Hi,

I am wondering... how will moving Roassal to Bloc affect other platforms such as VisualWorks? Because it seems it would be unportable with Bloc, no?

Peter

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev




--

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Roassal on Bloc on not Pharo

Peter Uhnak
So Roassal3 will only be supported on Pharo?

(This is not a question about the benefits of a single platform or benefits of Bloc, which are both known to me, but about other platforms.)

On Fri, Jul 31, 2015 at 1:56 PM, Tudor Girba <[hidden email]> wrote:
The right direction is to make things work on Bloc and commit to this platform 100%. This will make things simpler and will take advantage of what Bloc offers.

Doru

On Fri, Jul 31, 2015 at 1:50 PM, Peter Uhnák <[hidden email]> wrote:
Hi,

I am wondering... how will moving Roassal to Bloc affect other platforms such as VisualWorks? Because it seems it would be unportable with Bloc, no?

Peter

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev




--

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Roassal on Bloc on not Pharo

Stephan Eggermont-3
In reply to this post by Peter Uhnak


On 31-07-15 13:50, Peter Uhnák wrote:
>
> I am wondering... how will moving Roassal to Bloc affect other
> platforms such as VisualWorks? Because it seems it would be unportable
> with Bloc, no?
>
>

There is an abstraction layer. There is no technical reason it can't be
kept up to date.
Advanced features get lost/are only supported on one platform/need a lot
of work

Stephan
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Roassal on Bloc on not Pharo

abergel
In reply to this post by Peter Uhnak
Frankly, I have no idea yet. 
A couple of months ago I thought to completely drop the VisualWorks port. Roassal3 on Pharo exist because we get funds from companies that are using VisualWorks. So, nothing is clear for now. 

Alexandre
-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.



On Jul 31, 2015, at 8:50 AM, Peter Uhnák <[hidden email]> wrote:

Hi,

I am wondering... how will moving Roassal to Bloc affect other platforms such as VisualWorks? Because it seems it would be unportable with Bloc, no?

Peter
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Roassal on Bloc on not Pharo

stepharo
In reply to this post by Peter Uhnak
If Roassal's future is not on Bloc then it will be difficult because Bloc is far better than Trachel.

Bloc is the foundation for Pharo and the feedback we got from experts who did an equivalent of Bloc
during 5 years on top of VW, first bloc is better done, second they plan to migrate).
I think that the path for Alex is
    - maintain Roassal 2 for VW and Mooser (and ask user to pay for extension like in normal life when you buy your bread)
    - work calmly and secretly on Roassal 3 or whatever name  on Bloc.
        -- make it really really sexy
        -- learn from telescope model

Stef

Le 31/7/15 13:50, Peter Uhnák a écrit :
Hi,

I am wondering... how will moving Roassal to Bloc affect other platforms such as VisualWorks? Because it seems it would be unportable with Bloc, no?

Peter


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Roassal on Bloc on not Pharo

stepharo
In reply to this post by abergel


Le 31/7/15 15:20, Alexandre Bergel a écrit :
Frankly, I have no idea yet. 
A couple of months ago I thought to completely drop the VisualWorks port. Roassal3 on Pharo exist because we get funds from companies that are using VisualWorks. So, nothing is clear for now.
Alex

if you offer a platform to analyse network package to chris in Pharo + GT he will be more than happy.
This is why I asked him.
After you can still "maintained Roassal2" in VW but the future is not in VW that I can tell you :)

Stef

Alexandre
-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.



On Jul 31, 2015, at 8:50 AM, Peter Uhnák <[hidden email]> wrote:

Hi,

I am wondering... how will moving Roassal to Bloc affect other platforms such as VisualWorks? Because it seems it would be unportable with Bloc, no?

Peter
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Roassal on Bloc on not Pharo

Tudor Girba-2
+1 :)

Doru

On Sat, Aug 1, 2015 at 11:36 AM, stepharo <[hidden email]> wrote:


Le 31/7/15 15:20, Alexandre Bergel a écrit :
Frankly, I have no idea yet. 
A couple of months ago I thought to completely drop the VisualWorks port. Roassal3 on Pharo exist because we get funds from companies that are using VisualWorks. So, nothing is clear for now.
Alex

if you offer a platform to analyse network package to chris in Pharo + GT he will be more than happy.
This is why I asked him.
After you can still "maintained Roassal2" in VW but the future is not in VW that I can tell you :)

Stef

Alexandre
-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.



On Jul 31, 2015, at 8:50 AM, Peter Uhnák <[hidden email]> wrote:

Hi,

I am wondering... how will moving Roassal to Bloc affect other platforms such as VisualWorks? Because it seems it would be unportable with Bloc, no?

Peter
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev




--

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Roassal on Bloc on not Pharo

kilon.alios
In reply to this post by stepharo
Bloc does indeed seem like a very well designed library and a good replacement for Morphic. I also the fact that it comes with a ton of examples :)

On Sat, Aug 1, 2015 at 12:35 PM stepharo <[hidden email]> wrote:
If Roassal's future is not on Bloc then it will be difficult because Bloc is far better than Trachel.

Bloc is the foundation for Pharo and the feedback we got from experts who did an equivalent of Bloc
during 5 years on top of VW, first bloc is better done, second they plan to migrate).
I think that the path for Alex is
    - maintain Roassal 2 for VW and Mooser (and ask user to pay for extension like in normal life when you buy your bread)
    - work calmly and secretly on Roassal 3 or whatever name  on Bloc.
        -- make it really really sexy
        -- learn from telescope model

Stef

Le 31/7/15 13:50, Peter Uhnák a écrit :
Hi,

I am wondering... how will moving Roassal to Bloc affect other platforms such as VisualWorks? Because it seems it would be unportable with Bloc, no?

Peter


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Roassal on Bloc on not Pharo

abergel
In reply to this post by stepharo
Yes, it looks like to be

Alexandre


> On Aug 1, 2015, at 6:34 AM, stepharo <[hidden email]> wrote:
>
> I think that the path for Alex is
>     - maintain Roassal 2 for VW and Mooser (and ask user to pay for extension like in normal life when you buy your bread)
>     - work calmly and secretly on Roassal 3 or whatever name  on Bloc.
>         -- make it really really sexy
>         -- learn from telescope model

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev