Has anyone out there created their own library from scratch?
Here's some background info, skip to the questions if you want a short read.
In our current production setup we use a heavily modified version of the Beta Foundation library. I love the library and I do just fine working in it, but training our employees to use our modified version has been.......well...... difficult. The formulas I have implemented are so long they have no idea what's really going on, and don't want to take the time to find out. Which I can understand. Most of our cabs are made from the masters cabs because I've modified so much. Every product has hundreds of prompts that aren't usually necessary. And that's mostly my fault for designing it that way I suppose.
Anyway, I'm toying with a new library development. I want to build a library from scratch. For us to use for many years to come. It would be able to match our workflows and completely integrate with our tracking and production software.
My goals are to keep the library concise as possible, making only prompts available that actually work and we provide to our customers. I want TO LOCK THIS THING DOWN. I want all the prompts to work together, Never break each other, and be correct 100% of the time. If we need anything more than those prompts, then it is considered custom and, will require an adjustment in the spreadsheet, which is what we are doing now anyway. Every edit seems to be a little different than the last, so it's hard to bake that into the library
I know all this is possible in the FL, but also getting a inexperienced user to understand what's happening behind the scenes is daunting when there's 100s of prompts. We are such a custom shop, and we do dozens of custom designed cabinets for our larger projects. So being able to work in the spreadsheet and understand our prompts is a must.
So here are my actual questions for discussion
Has anyone else out there attempted to create their own library from scratch?
Is there template library I can start from that is blank? Like an empty library I can add to?
What are some useful library creation tips? Such as....
1. What is the best way to get thicknesses of material? is using the pointer like M!Base_Bottom_Thickness still up to date as the most effecient way to call that?
2. What sort of prompt organization have you developed or imagined would work well?
3. How many prompts are too many prompts?
4. Does it make sense to have every polyline token developed in a table in the prompts page?
5. Have you developed a system for changing material thicknesses on the fly for a project? Currently we copy materials to project level, and change the thicknesses and then change all the pointers to those materials. Is formula materials more efficient for this? We have stayed away from FM because I couldn't decide how a project with many different colors would be managed with that route. What if we wanted to run this color on a different core. which then is different board size. I need to look into this more.
I've created my own blank library, but now I get errors and object reference errors galore because I went and hacked things up in the Explorer. I will have to export my new library into a cleaner configuration at some point.
I know this is a lot of information, but wanted to post this here to see what others are doing out there, and be able to discuss best practices when designing a library from scratch. I feel like a knowledge base article for this type of thing WOULD BE AWESOME.
If only I could have Mr. Lenny's experience for something like this.