Naming objects

[Ray]

Hi everyone
I am new to Alpha Five but I would like to no if I should
use naming prefixes like putting

lbl for labels
tbl for tables
fld for fields
txt for text boxes
btn for buttons

I have done some studies with Microsoft VB and that is what
I learned for naming objects

Any help
Ray

[JerryBrightbill]

RE: Naming objects

Ray,

I think everyone has their own conventions for naming objects. Normally, I leave field objects named the same as the field itself. It seems easier to keep track of them. I usually rename buttons with something more descriptive than "button1, button2". I normally use something like "Button_save". I do the same for other objects like text boxes, browses, etc. Maybe it's just me, but using short cryptic names is occasionally confusing. I prefer a short name that I can identify immediately.

I will deviate on some objects where I may need to use values in an array to address them. An example would be an instance where I want to change the text in a series of text boxes or buttons. Then I will use a name with a number ("button1, button2" for example). Then I can use the array pointer to identify the object. The following is an example for a calendar that fills in numbers on buttons for each day in the month

for i = day_wk to day_wk+num_days-1
block = obj(":Pop Calendar:Button"+alltrim(str(i,2)))
block.text = str((i - day_wk +1),2)
next

In this case, day_wk is the day of the week for the first of the month and num_days is the numberr of days in the month. The button naming method makes it easy to change the text using the variable.

Others may have different ideas, but this works for me.

Jerry

[Ray]

RE: Naming objects

Hi Jerry

Thank you
Ray

[Geoffrey Hollander]

RE: Naming objects

Ray,

I've been learning XBasic for a couple of years. Simutaneously, I have also been trying to learn VBA & VB. I have spent much more time with Alpha Five since most of what I do involves data management and "conditioning" and, as any Access user has experienced, the Jet Database Engine (used by Access and VB) is slow, bloated and ungainly.

One of the things that impressed me about the VB world was that a lot of it was standardized -- vis a vis its naming conventions. I've found that VB's naming works fine in Alpha Five, and is especially useful to me when I either have a LOT of objects in a project or when looking at a list of object names.

Not only does a naming convention help long after you've begun a project but, as you have probably discovered, the longer a project goes on, the more often you have to revise object names and be increasingly creative about the new ones you add.

I have a client who insists that I work in Access/VBA for our project. In the course of working with Access, I found a cool addin which will search and replace text ANYWHERE in the project; so renaming things is easy.

Say that you have created several saved queries upon which several sub reports and reports are based. Some of these titles and objects also appear in the code used to manipulate them. With this utility, I can change the name of a report in the database window, in the report itself, in any code that refers to that report and throughout any queries that interact with it, all in a single pass.

I hope that Alpha FIve incorporates someting like this one day.

Anywho, Welcome aboard!

Best regards,

Geoff HOllander

[CALocklin]

RE: Naming objects

Personally, I've started using a naming convention (sporadically) simply because it seems like "good form" and it seems to be the accepted standard now. On the other hand, I find it to be just unnecessary typing in A5. The Xbasic explorer uses icons/structure which makes it obvious what you are working with and the context of Xbasic script usually makes it obvious as well. But, that's just my opinion.

I think the key here is that any naming convention, at least in A5, is for your benefit. Do what works for you.

[Ray]

RE: Naming objects

Hi Geoffrey
Thank you very much

Ray

[Ray]

RE: Naming objects

Hi Cal

Thank you very much
Ray