Wanted to get some input/ideas on something I have been kicking around in my brain since finding ScriptMaster and beginning the journey of learning Java/Groovy.
Can SriptMaster/Groovy be used to create an FM database that is Object-relational?
This is just strait brain spewing, but if you code your own classes and package them as jars for use with ScriptMaster could you leverage java/groovy classes in a way that would allow FileMaker tables to become more like persistent objects and thereby avoid some of the pitfalls that accompany traditional relational db data normalization?
Can we bring the concept of inheritance to FileMaker?
Example...Leads/Prospects/Customers have many similar characteristics and need to preform many of the same functions/behaviors yet each has some unique properties that cause them to be modeled in FileMaker/Relational DBs as a separate table. This leads to a lot of duplications in layouts, scripts, fields and calculations.
I have always feared that my daily use and development in FileMaker is turning me into one of the bemoaned "dataheads" who thinks in terms of tables, fields, and functions rather than in terms of real world objects. How can we use ScriptMaster to bring a little bit of object thinking to the FileMaker world?