Hi all,
I’m fairly new to the game of using constants and user defined classes in LotusScript and have found that the one script library have been writing all of my classes and constants in for a database I have been developing has grown quite large (over 1300 lines) and i was wondering if anyone had any suggestions that could help me pare it down a bit. i have almost 300 constants in this script and if it weren’t for TeamStudio’s object browser for the Designer, i’d be totally screwed.
anyway, if anyone has any suggestions, i’d be glad to hear them. thanks.
brandt
Subject: Can anyone suggest best practices for LS Constants and Script Libraries with numerous classes?
I’m a one class per library man, myself, when it comes to OO, using a Class naming scheme. It makes 'em almost weildy. For constants, I wouldn’t worry about splitting them up unless you can break them down into easily identifiable “functional groups”.
Subject: RE: Can anyone suggest best practices for LS Constants and Script Libraries with numerous classes?
Hey Stan,
question about your one class per script library philosophy…do you create a script library that simply references all of your classes in your Options section and then reference that library in all of your design elements, etc. or do you do it on a case by case basis?
brandt
Subject: RE: Can anyone suggest best practices for LS Constants and Script Libraries with numerous classes?
Case by case – but the cases are lowest-level and simplest. That is, any class that extends another class uses the library containing the class it’s extending, so there are usually a very small number of references to manage in the final code.
(These days, I’m in “protect the IP mode”, so there’s a lot of LSS including rather than library using. That gets rid of the “use” chain problems, but there is the unfortunate side effect of having no maintainable source code in the database.)