I'm fairly new to components also, and what you describe below is pretty much how I'm doing it. Anything reusable goes in one component library. But I want to use different subsets of this for different projects. I have "build methods" which specify which methods (modules) should be shared for the compiled component. So this allows different compiled components to be created with different sets of features from the same source structure. I have a parser almost done. I will eventually remove all unused code from the component before compilation rather than just hiding methods by making them unshared.
John DeSoi, Ph.D. > On Apr 20, 2017, at 6:32 PM, David Adams via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > I might give components one more try by putting everything into an > OmniJumble component and having the host call it all of the time. Not > really a sensible way to organize libraries, but it may be as good as I can > get. My main goal, in this case, is to hide a lot of the plumbing on a > large body of code. I'm not trying to hide the code per se (if I give out > the component, I'd give out the code), but to make the calls easier to work > with. Your idea about colored method names would help here too. ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
