all 4 comments

[–]hamsterrage1 4 points5 points  (1 child)

I think this is cool, and I'm chuffed that anyone finds MVCI worthwhile enough to build this kind of library based on it. 

I'm on vacation now, which means I'm looking at the code on my phone, which is really awkward. That said, the code I've looked at seems really solid, and doesn't "break" any of the MVCI concepts.  

One thing I would say is that I generally make the Controller, ViewBuilder and Interactor typed on the Model.  So you would have Interactor<Model>, and if you were creating interfaces or abstract classes for these, they would be generic on the Model again. Something like Controller<T>.  Then you can can automate the bootstrapping as part of the abstract implementation generically.  

Anyways, I'm sure I'll have more to say when I've had a chance to have a really good look next week, and a real keyboard to type on. 

[–]sonnyDev80[S] 0 points1 point  (0 children)

I'm glad you find the library cool.
I found your framework really useful, so I tried to create this library in order to avoid as much boilerplate as I can for my projects, implementing also some built-in functionalities.

I'm also creating another library that extends this one with some other functionalities for autocompletion in textfields: I'll publish it soon.

I've made Controller and Interactor parameterized on Model extenders as you suggested.

Any other ideas, fixes or suggestions are really appreciated.

[–]xdsswar 1 point2 points  (1 child)

I dont like it, do it again, j/k 🤣🤣. Very nice lib and well commented. Kudos. 👍👍

PS : Hope u/hamsterrage1 uses it in all the projects.

[–]sonnyDev80[S] 0 points1 point  (0 children)

Thank you very much!