[furcas-discussion] Where are things?

[Uhl, Axel]

Hi Stephan,

thanks for the summary.

> During refactoring in the master branch, I inspected several pieces of
> code dealing with delayed references and concluded that the scope
> handling and the dependency injection paths have to be reviewed. The
> way
> editor works does not seem to fit the interface of the model updaters /
> reference resolving infrastructure.
> 
> For example, when a model updater kicks in, it has to work on the exact
> scope of the editor and also know about transient model elements in the
> internal resource. The model updater should not source the internal
> resource of an editor that is parsed concurrently in another background
> thread.

We should discuss this in depth during your next visit. I haven't taken any time lately to work on this as I'm pretty much tied-up with the SAP Sailing Program. I was considering (as I mentioned) applying FURCAS to some particular aspects of the sailing program, but given where we stand this may be a bit too early other than for deriving a few more test cases for FURCAS.

> Yes and no. I don't think that we are mature enough. However,
> approaching usecases is the only chance we have. Without a closed
> feedback loop we are pretty much developing in the dark and might end
> nowhere.
> 
> Having concrete uses cases (e.g., runlet) seems to have served FURCAS
> really well in the past.

That was my impression too.

> Axel, have you considered re-activating the NGPM syntax? Maybe that is
> a
> good start for you to get a feel for the capabilities of the new
> infrastructure.

I haven't dared to do so and currently have other priorities that would make it hard to follow up on any non-trivial issues that pop up during this. If I get my key deliveries for the sailing program out the door I may have some more time for a more solid assessment of FURCAS again.

As you suggest, let's meet to see what can/needs to be done to not lose track of the general progress and vision. I'd still love to get FURCAS to a point where we can simply *use* it.

Best,
-- Axel