Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Content Management (Extended ECM)
API, SDK, REST and Web Services
Livelink Builder How To Better Understand Development
Gil_Batac_(gbatac_-_(deleted))
Hi, I took the Livelink SDK(Builder)class and didn't really learn much. Does anyone have any advice/tip to learn more about using Builder and how to customize or create new functionality for Livelink? I wish their were "Hot To" books for Livelink. Thanks
Find more posts tagged with
Comments
Bob_DeGarmo_(WorldWideTechUser1_(Delete)_1437172)
In their defense, I'll say that the Builder class is probably the best it can be, for what it is... I know when I went through it I was "Flashing Amber" by mid-second day, warning of an imminent System Overload of my brain.Let me ask this: Did you also get the benefit of the BOBB (Building on Builder Basics) course? In that they attempt to present a "methodology" for approaching Livelink customizations. I'm not sure, really, how effective it was, since I received that class as my "Day Four" of the builder class, and I was already more than overloaded by that point.Aside from that, what I would recommend is that you work on a local play-dev box, decide something to do, and tear into it... From there probably "The School of Hard Knocks" is the best learning mechanism there is...Just keep these tips in mind:* Never, never, never, modify core code. Orphan it to your ospace instead, and override their globals to point at your objects if necessary.* For whatever you think you want to do, before going off and inventing the wheel, scrounge their code long and hard. With all they have in there, chances are you can find something close to what you want to do, and you can then either orphan their objects, or copy their code.* Don't give up! It can get frustrating at times... But once you break the "Learning Curve" you'll be surprised at what you can do...* Finally, I'll give this plug to OTSupport. They try **real** hard to support developers. Keep in mind though that they see some pretty hideous stuff, and some of it can be all but impossible to debug remotely. So be prepared to send your module in to them if need be.Good Luck!