Variable Naming Convention - Discussion
March 19, 2008 12:00 AM
I would just like to open a discussion about how developers name their variables in a Lectora project. Coming from VBA, I have become accustomed to preceding variable names with an abbreviated variable type. For example, intValue is an integer, blnSuccess is a boolean, and strName is a text string. This works quite well in programming environments when you type out the variables. It seems to create more work for me in Lectora's form-driven environment. When I have a Jeopardy-style game show with 25 different spaces that may or may not be visible, it becomes tedious to press B 17 times just to get to blnPotpourri200. Instead, I could have reduced the number of keystrokes by pressing P twice to get Potpourri 200. Such an informal naming of variables disturbs me, though. I try to define my objects appropriately, so I have a Potpourri 200 Text and a Potpourri 200 Blank Text and so forth. What options should I consider for naming the boolean associated with Potpourri 200?After having a little chat with an associate, I'm leaning more toward a hierarchical method where the "object" comes first followed by type. So, all of my related words begin with Potpourri, but they are divided up into:Potpourri Visible TextPotpourri Hidden TextPotpourri Image BoxPotpourri VAR blnPotpourri VAR strAnd so forth. How do you name your variables? I'm looking for some inspiration.Kevin
Discussions have been disabled for this post