PAHLabs Blog goes Live

 Welcome All!

Today with this post the PAHLabs Blog goes Live.

It is a goal of mine to share with others my passion in Software Development, Coding and Application Design.  I plan to use this blog to reach out to those of like minds, and especially those wanting to learn.

Though in my 40+ year career in software development I have written many, many software languages, this blog is mostly going to focus on PureBasic.  I have an accompanying website (https://www.PAHLabs.com) where I have both free and licensed software products, developed using the PureBasic Language.  You can find out more about PureBasic at PureBasic

Here in my blog, I will begin explaining how these applications were written, and to share with you how I develop software.  

The first thing about software development I wish to share with you is that software development is all about solving problems. A software program is nothing more than a solution to a problem.  As with ALL solutions there are many ways to solve any problem, the trick it to solve the problem in an elegant manner that is both efficient and pleasing to the eye, but above all else it must SOLVE the problem.  If this solution can be done in an organized logical, repetitive manner than maintenance of this solution will be far easier. After all most programs take several weeks to months to write, test, and move into a production status, but they "live" in maintenance for years. If every application you wrote was a 100% unique solution, and you re-invent the wheel anew with each and every program you write then your development time will be much longer, and maintenance will be a nightmare! 

Taking a measured standardized approach will make your development times shorter, far more reliable, and maintenance a breeze.

This is first of MANY posts to come.  

Comments

Post a Comment

Popular posts from this blog

How to build this without writing Code

I'm not sure if I should do this now, because I have not explained a number of additional aspects to the code, but for those of you who are interested.  The foundation of what I shown you here, IS the foundation of code my PBXClassBuilder-Standard generates for you.  And I truly mean generates  for you. You can have all this code generated for you without writing a single line of it yourself. Now PBXClassBuilder-Standard is not perfect, it is approximately 90=95% accurate. And I am constantly tweaking it edging this number ever higher. To use PBXClassBuilder-Standard, You should start with Forms already laid out and built.  Within PBXClassBuilder-Standard you use intuitive screens to define your table structure, while linking the Table Fields to their intended form Fields.  Then link the Tables together as Parent Child, and finally you simply click buttons to generate the code, Including the SQL Code to create the tables. The Whole development process, post For...
Read more

Connecting the Forms to the Data-Layer (part 9)

Here is the whole View Code Sheet Define quitfrmSolarSystem Declare SolarSystemCustom() Declare SolarSystemSetScreen() Declare SolarSystemCreate() Declare SolarSystemModify() Declare SolarSystemDelete() Declare SolarSystemSetData() Declare SolarSystemSave() Declare SolarSystemClose() Procedure SolarSystemSetScreen() Protected String$, x, y, w, h, i, ID Shared WorkSolarSystem Protected EventID, MenuID, GadgetID, WindowID, Index Shared quitfrmSolarSystem quitfrmSolarSystem = #False If Window_frmSolarSystem() SolarSystemCustom() SetActiveWindow(#Window_frmSolarSystem) ;Set Screen Data SetGadgetText(#Gadget_frmSolarSystem_txtName, WorkSolarSystem\Name) SetGadgetText(#Gadget_frmSolarSystem_txtGrow, Str(WorkSolarSystem\GRow)) SetGadgetText(#Gadget_frmSolarSystem_txtGCol, Str(WorkSolarSystem\GCol)) SetActiveGadget(#Gadget_frmSolarSystem_txtName) Repeat EventID =WaitWindowEvent() MenuID =EventMenu() GadgetID =EventG...
Read more