Modular/Package Structure

[larry-tx]

When looking into CrudBooster, I became interested in it because it seemed to understand the kind of modular/package architecture that are essential to virtually ever modern web application. You can imagine my horror when I discovered that your cb-model package simply slings all models into a non-standard directory called app\CBModels. Horrors!!!!!!!!!!!!!!!!!! My application, which is not fully developed at this time has 217 tables most of which have at least three or four relationships to other tables.. Do you expect me to sling, willy-nilly, 217++++ models into one directory? How would I ever manage that?

Do you have any plans to incorporate module support into this package? I tried making the models for my smallest, almost trivial module. (I'm currently using nwidart/laravel-modules for my modular architecture. It's great.You should build CrudBooster and CB-Models to accommodate such packages.) Anyway, this smallest of my 26 modules has five tables and models in it. I can't believe that your package would dump these models in the same directory with over twenty entirely unrelated modules and their models. This application that I'm working on is very much like the complexity of what my colleagues are developing, although it is somewhat smaller than theirs.

Do you plan to develop this CBModel package into a mature, workable package? If so, when? I'm working on my application right now and hope to push it into production status in the next month or two. If not, will CrudBooster work with any models that conform to Laravel specifications?