Separate the component specification from the component implementations

While searching for a suitable class hierarchy for my components in patternfly-fritz2, I came across the classes, interfaces, mixins and functions defined in components.kt.

These definitions are very well done and most of them would perfectly fit also as the base for my components. Would it be possible to factor them out into its own module? That way I could add a dependency on it w/o depending on the actual fritz2 component implementations.

I’d like to ask for moving everything but the following elements into an own module:

• dev.fritz2.components.CloseButtonProperty
• dev.fritz2.components.CloseButtonMixin

WDYT?

[hpehl]

At the moment I don’t have a good answer to this issue either. Maybe I’ll come up with a solution as I continue to work on my PatternFly components. If so I’ll comment here…

[jamowei]

In my opinion there is a possibility to integrate our styling approach into our core later after we stabilized it enough. Then we are able to move the basic interfaces on, which our components rely on, to the core either. But for now I think it is to early to do that move and we should keep focus on stabilizing our projects. Anyway it is good to have this issue and to keep this idea in mind! And maybe we can find a way in between this two scenarios we can achieve earlier.