search

90301 / Crescent-CRM-V

the vaadian version of Crescent CRM.
2 stars 0 forks source link

Custom field Mono-Class #232

Open 90301 opened 7 years ago

90301 commented 7 years ago

Consolidate custom Field Classes into fewer classes (single class if possible).

231

FfGingaNinja commented 7 years ago

Sounds like a plan. I'll try to work on this some today after my classes.

FfGingaNinja commented 7 years ago

I'll make sure to keep you up to date on what I move to the single class. What should be the name of the class? It's in UiElements, but should it be called Custom Fields? Or maybe AllThingsCustomField? haha

90301 commented 7 years ago

I agree, this is certainly the predicament. The best thing I can think of is to make it 1 class that handles all the data (in client info package). The actual visual elements may need to be a separate class. This is partially why we need a diagram. To store the info, we need a class that extends a max object. you can't extend two classes. Some of this might just be consolidation. and it might turn out that we can't really simplify the class structure. if we can't, we can still make helper methods that pull and link information much better.