+4
Hello out there,
I'm about to create a notation-guideline. I was wondering how you handle the notation of Controls in the K2 Designer. Do you have such a guideline or do you name them as you like for the moment?
I would like to see how you handle it to look through it and eventually adopt sth. from it.
Best regards,
Sparrow
+7
Sparrow,
I started off with the "live in the moment" mentality, however running into inconsistencies with control names not auto mapping to SmartObject variable name and issues with parameters put me into a different mind-set.
I will now build views off of the smartojects, so that my control names will match those variable names produced from the smartoject. It seems to speed up the mapping out CRUD events when I need to build them.
Between that and ensuring my parameters do not match any variable names from the SmartObject (this is a bug), those are sort of become my staples in the initial build process.
Parameter Naming - To distinguish parameters from other variables the prefix "p" should be used.
Use camel case. Example: pTypeName, pNumberOfItems
Local Variables Naming - strFirstName, dsetEmployees
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.