Architecting InnateMC

[heftymouse]

As this app becomes larger, it becomes important to define a standardized architecture so that it remains easy to maintain in the future. This is dependent on opinions and peoples' conventions so it'd be good to discuss it in, well, this discussion.

[heftymouse]

Here's what I had so far:

• It's unlikely that we ever move away from macOS or SwiftUI so it's unnecessary to excessively decouple functionality and implementation.
• SwiftUI has built-in support for two-way data binding so having a separate viewmodel is unnecessary.
• Body and event/completion handlers should be in separate parts of the view.
  - Global 'services' should be passed in through a singleton EnvironmentObject
• 'Services' should be separate singleton classes.

[BoogieMonster1O1]

What would be the advantage over utilizing an Environment object with published fields?

[heftymouse]

It removes one object from the heap I suppose

[BoogieMonster1O1]

It removes one object from the heap I suppose

At the cost of five more, the environment keys

[heftymouse]

The environment object will have those five as members anyways

[BoogieMonster1O1]

The environment object will have those five as members anyways

Environment Object - 1 encapsulating class + 5 members
Environment - 5 environment keys + 5 members

Removing an object from the heap isn't a valid argument lol

[BoogieMonster1O1]

InnateKit is starting to sound like over-engineering. It has a couple of abstractions for things that we could remove. The advantages of InnateKit are as follows.

• Easier testing (counter - test driven development is a bad idea)
• Possibility to create a CUI launcher (counter - not on InnateMC's plans for the foreseeable future)

InnateKit and InnateMC are also starting to have some blurred lines, namely preferences, as it is not known in which module they should be stored.

The merger of InnateKit and InnateMC would signal the end of a hybrid development architecture and the beginning of a monolithic architecture.

[heftymouse]

I agree, having them as separate targets is pointless given the direction we're going in.

[BoogieMonster1O1]

#27 addresses this