Re: [flux-dev] Flux architecture for non-IDE purposes?

[Kristian Rink <kawazu428@xxxxxxxxx>]

Hey Martin;

and first off, thanks for your feedback.

Am 09.07.2014 13:47, schrieb Martin Lippert:
> I think at the moment we are very much focused on applying the ideas
> to the IDE space and do not think beyond that space. Since the
> architecture and ideas behind Flux are very much at the beginning and
> there are more questions than answers around these days, the focus on
> building cloud-based developer tooling will help us to find the right
> answers.

I'm fully aware of that, which then again ain't a bad thing - as far as 
I can tell, most of Eclipse seems to have started out just this way, 
including the RCP. And I guess that this approach does fully make sense 
for some reasons.

However, when listening to your explanations and reading through the 
project outline, I couldn't help mentally mapping this to "my" domain. 
We're into data management for civil engineering projects, and people in 
here are right now into starting to embrace "cloud" services for 
different things. One of the more interesting problems, here: Though 
people generally would use cloud services, in some situations they're 
simply not able to do so - because, in example, working with large 
2D/3D/<n>D models and applications related to modeling, you're still 
left with working with heavy local applications requiring quite some CPU 
and graphic processing power. On the other side however, there are 
things (like computations, model validations / checkings, collaboration, 
...) that could be done very well in the cloud, maybe better than on a 
local machine.

Likewise, the idea of working in a 3D model, it would be interesting to 
leave your local application, enter the cloud UI, which by then might 
offer just a lightweight viewer but still might be able to at least 
re-open your last working perspective, specifically the 3D model you 
just were working on, and the viewpoint you had the last time you were 
working in there. So far this is pretty hypothetical as there are some 
interesting questions involved (including dealing with rather large 
model files), but it seems an interesting thing nevertheless.



> Nevertheless, if you are interested in applying the ideas (and maybe
> some code) to general application development, please feel free to
> explore that and provide feedback.

Just cloned the git repo yesterday, gonna have a look at what's in there 
the next days. Curious to see in which state this is... :)


Cheers,
Kristian