Browse by Tags

Re: PBL naming and object grouping

Thanks Grismare, and welcome to the forums =) Your insight will be very helpful since you have a lot of experience with adaptation of Kodigo. So as long as we group the libraries allowing developers to pick how much of the framework they will use, and keep the object names away from common PB/PFC conventions...

Posted to Futures Discussion (Forum) by yeyi on 03-16-2008
Re: Constants/Enumerations

OK, please correct me if I'm wrong. Let's assume we have a variable named FirstName Scope: Local: lFirstName Instance: iFirstName Shared: sFirstName Global: gFirstName Argument: aFirstName This is OK, but how about access to instance level (protected, private)? I was thinking of using underscores...

Posted to Futures Discussion (Forum) by yeyi on 03-14-2008
Re: Common, lightweight services changed to overloaded global functions

Function has been added (w/ overload for ignoreCase). Incidentally, this function is also present in StringService class but I will keep the function in the service and probably point it to the global one.

Posted to Futures Discussion (Forum) by yeyi on 03-13-2008
Re: PBL naming and object grouping

The consensus now is to retain the name Kodigo. Due credit will be given to any ideas, design, coding, etc. for anything that will be part of the project, big or small. Roland, any help coming from your experience I seriously consider. TopwizProgramming has been in my bookmarks since forever. I agree...

Posted to Futures Discussion (Forum) by yeyi on 03-13-2008
Constants/Enumerations

There is no support to create our own Enumerations in PB. Fortunately there is the workaround of creating a nonvisualobject and declaring public instance varables as constants. This approach enables us to get the value without having to instantiate the nvo. In the previous Kodigo, i prefixed all enumerations...

Posted to Futures Discussion (Forum) by yeyi on 03-12-2008
Common, lightweight services changed to overloaded global functions

I decided to change some of the most common services into global functions with overloads. The topic can be found here . As long as it is only edited and saved in source view, it should be OK. Opening it via painter will only show you one function. Here are some of the functions: SizeOf - get's the...

Posted to Futures Discussion (Forum) by yeyi on 03-12-2008
Controls

I have been playing a lot with control authoring in .NET and also in PB. I also tried the external vuo route and although it is a little more difficult, it was very doable. But it wasn't unitl PBNI that things started to get easier. The biggest hurdle for me before was translating all the GDI+ code...

Posted to Futures Discussion (Forum) by yeyi on 03-07-2008
Kodigo toolkit

In order gain traction, a good framework is not enough. It also has to have a set of tools to help in the use of it. Here is a shortlist: Unit Testing - in line with PBUnit xRef and impact analysis Comment generator and Code documentation - in line with PBDoc/PBPaste, but maybe not as robust DAL and...

Posted to Futures Discussion (Forum) by yeyi on 03-07-2008
PBL naming and object grouping

For the next Kodigo, I have been playing around on how to name the libraries and what goes into them. Here is my current list: kodigo.pb.base.pbl - contains all inherited objects from powerbuilder. Serves as an insulation layer. kodigo.core.pbl - contains core kodigo classes kodigo.services.pbl - contains...

Posted to Futures Discussion (Forum) by yeyi on 03-05-2008
Naming conventions

Many of us have been conditioned in Powerbuilder to name our classes/object with prefix identifiers (n_cst_xxx, u_xx, etc). In the new Kodigo, I have been playing around with how to name objects saved in the PBL. Here are my requirements: It should not clash with naming conventions of PFC and other popular...

Posted to Futures Discussion (Forum) by yeyi on 03-05-2008

Page 4 of 5 (45 items) < Previous 1 2 3 4 5 Next >

Kodigo

Browse by Tags