My suggestion is write tests and after try to build a Spec adapter. The spec adpater will be a really good client. Because with Boc the adapter should not exist at runtime. It should just be there for the registration but not a middle man like now.
Stef On Thu, Sep 28, 2017 at 11:44 PM, stephan <[email protected]> wrote: > On 28-09-17 21:03, Stephane Ducasse wrote: >> >> Now how do you validate the API of your widgets. > > > Good question. In Morphic I had everything centralized in the Morph. > The advantage is that it is clear what influences what, the disadvantage is > that it easily results in very complex code. Here I have event handling > spread over multiple objects. That gives here a better separation of > concerns. The pane itself handles clicking, the dragInteraction object the > drag and drop. Separating these two works, but in a more complex application > there could be e.g. multiple drag and drop relationships. > >> I think that write test is a really because in that it will force us >> to have fully scriptable widgets. > > > Indeed. At the moment I am still trying to find out how I want to distribute > responsibilities. I welcome ideas on how to improve this. > > And of course I would like the dropping to also work on the last position. > > Stephan > > >
