Hi Stef,
I do understand (at least partially) the value behind it and I tried to
play with it more, and there were things that I really liked...
However I feel like many of those concepts should've been introduced
directly as part (or an extension) of Roassal, instead of top of it,
because that seriously limits its (re)usability without fully committing to
Telescope.
In any case from my experiments and considering all other things (like
serious lack of documentation, even smaller user-base, different API, ...),
I think that it would be currently too much work for too little added value
for me,
because I already had to solve some of the problems you guys had on my own,
so I would be basically spend a lot of time rewriting code and at the end I
would be where I started... and then Roassal 3 would come and I would have
to rewrite again.
Also another important part is the overall user experience, so this
definitely means that I will need to dive deep into Roassal (and even
Morphic) to make things work (as I've already done and continue to do). And
since you decided that you want yet another layer between Telescope and
Roassal (to be able have another rendering libraries (although from the
Telescope code I've seen it's not exactly separated)).
So this would mean for me that I would have to write a lot of stuff twice
(or three times (Roassal+Telescope+adapter)); and again, with little added
benefit for me (and since I'm not payed for what I do; what I want is my
primary concern).
So to summarize...
I think that currently best scenario is to postpone it and look at it again
when Roassal 3 starts rolling around, because I will be migrating to
Roassal 3 for sure also because of Bloc.
This will also give me more time to familiarize myself more with Telescope
and make the transition less painful.
Peter
On Sat, Jul 25, 2015 at 12:41 PM, stepharo <stepharo(a)free.fr> wrote:
Peter
telescope idea is that you can define visualization (model) where you can
define advanced behavior and reuse it.
We presented last year the model to alex and this year again and
he saw that there is a real added value.
Scripts does not let us reuse and build more complex model.
Telescope has a visualziation model (not a canvas on which you write)
+ composite + advanced interaction.
telescope model should be taken and used in future version of Roassal.
We do not take it personally if alex takes synectique's code/ideas.
For us we will continue to build around and if telescope is fusioned into
Roassal 3
then even better.
I dream about
Roassal 3 = Bloc + Telescope + some part of Roassal 2 (layout....)
And roassal 3 does not have to be compatible to Roassal2. And people do
not have
to migrate to Roassal 3.
Stef
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev