I'd like to open disussion about cleanest directory structure in app/. Laravel provides default one, but it isn't enforced and I think that it's time to clean it up a bit.
I don't like models lying around app/. It's fine in small projects but it got mixed up with classes of many different purposes, in case of Codice. What do you think about clearly separating them under Codice\Models namespace?
PluginBase, PluginManager and MenuManager - could all of these be logically moved into single namespace? If so, what should it be? I thought about Codice\Core or just Codice\Plugins (MenuManager is API for plugin developers but it's also utilized by the core to allow changing default menus)
Reminders should became child namespace of one chosen above, IMO
What about Codice.php? (Codice\Core? Leave it as it is?)
Codice\Support\ exists only because of Codice\Support\Traits\Singleton and it's direct ripp-off from OctoberCMS. I'm not saying that it should be removed, but it just should be used - what about moving Codice\Calendar under Codice\Support?
I would be very glad if you could provide me with any tips, opinions and criticism.
I'd like to open disussion about cleanest directory structure in
app/. Laravel provides default one, but it isn't enforced and I think that it's time to clean it up a bit.app/. It's fine in small projects but it got mixed up with classes of many different purposes, in case of Codice. What do you think about clearly separating them underCodice\Modelsnamespace?PluginBase,PluginManagerandMenuManager- could all of these be logically moved into single namespace? If so, what should it be? I thought aboutCodice\Coreor justCodice\Plugins(MenuManageris API for plugin developers but it's also utilized by the core to allow changing default menus)Remindersshould became child namespace of one chosen above, IMOCodice.php? (Codice\Core? Leave it as it is?)Codice\Support\exists only because ofCodice\Support\Traits\Singletonand it's direct ripp-off from OctoberCMS. I'm not saying that it should be removed, but it just should be used - what about movingCodice\CalendarunderCodice\Support?I would be very glad if you could provide me with any tips, opinions and criticism.