Posts

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 Forms, is only a few mi
Post a Comment
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
Post a Comment
Read more

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

 So now we are down to just the SolarSystem Code Sheet. This is NOT a rubberstamp of the Galaxy. The MAIN reason is that the Galaxy Records are Sourced directly from the Database, As you will recall our SolarSystem is Sourced from the Galaxy Record's Solar System Collection NOT the Database. This makes for a VERY Significant difference between in the code. Our Procedure are the save ALL the Steps are the same, the differences are in the details. Starting once again at the top, we have our declares: Define quitfrmSolarSystem Declare SolarSystemCustom() Declare SolarSystemSetScreen() Declare SolarSystemCreate() Declare SolarSystemModify() Declare SolarSystemDelete() Declare SolarSystemSetData() Declare SolarSystemSave() Declare SolarSystemClose() And then, as before the SetScreen Procedure, and Control-Loop. Procedure SolarSystemSetScreen() Protected String$, x, y, w, h, i, ID Shared WorkSolarSystem Protected EventID, MenuID, GadgetID, WindowID, Index Shared quitfrm
Post a Comment
Read more

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

 Here is the entire Galaxy Code Sheet: Define quitfrmGalaxy Declare GalaxyCustom() Declare GalaxySetScreen() Declare GalaxyCreate() Declare GalaxyModify(GalaxyID.i) Declare GalaxyDelete(GalaxyID.i) Declare GalaxySetData() Declare GalaxySave() Declare GalaxyClose() Procedure GalaxySetScreen() Protected String$, x, y, w, h, ID Shared WorkGalaxy Protected EventID, MenuID, GadgetID, WindowID, Index Shared quitfrmGalaxy quitfrmGalaxy = #False If Window_frmGalaxy() DisableWindow(#Window_frmMain, #True) SetActiveWindow(#Window_frmGalaxy) GalaxyCustom() SetGadgetText(#Gadget_frmGalaxy_txtName, WorkGalaxy\Name) SetActiveGadget(#Gadget_frmGalaxy_txtName) ;Set Screen Data GALAXY::LoadListIcon(#Gadget_frmGalaxy_liSolarsystems) If ListEx::CountItems(#Gadget_frmGalaxy_liSolarsystems) > 0 ListEx::SetState(#Gadget_frmGalaxy_liSolarsystems, 0) EndIf Repeat EventID =WaitWindowEvent() MenuID =EventMenu() GadgetI
Post a Comment
Read more

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

 Now Let's look at The Galaxy View Code. I'll take it from the Top Down. the the next post will be it in its entirety. Beginning at the top we Have: Define quitfrmGalaxy Declare GalaxyCustom() Declare GalaxySetScreen() Declare GalaxyCreate() Declare GalaxyModify(GalaxyID.i) Declare GalaxyDelete(GalaxyID.i) Declare GalaxySetData() Declare GalaxySave() Declare GalaxyClose() These are nothing more than the declaration of the aforementioned Procedures. First Procedure is the "SetScreen", as I always put the Form Custom at the bottom. You will remember this Procedure's job is to Display the Form, and load information from the DataLayer to the Screen. After this the procedure contains the Control-Loop for the form.  Procedure GalaxySetScreen() Protected String$, Index, ID Shared WorkGalaxy Protected EventID, MenuID, GadgetID, WindowID, Index Shared quitfrmGalaxy quitfrmGalaxy = #False If Window_frmList() DisableWindow(#Window_frmMain, #True)
Post a Comment
Read more

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

 This is the whole Desktop Code Sheet ;/ Created with PureVision64 v6.01 x64 ;/ Thu, 05 Oct 2023 18:19:52 ;/ by Peter Hollyer XIncludeFile "Blog_Constants.pb" XIncludeFile "Blog_Windows.pb" XIncludeFile "Utils/ComboBoxExModule.pbi" XIncludeFile "Utils/ListExModule.pbi" XIncludeFile "Models/DB.pbi" XIncludeFile "Models/SolarSystem.pbi" XIncludeFile "Models/Galaxy.pbi" Global WorkGalaxy.GALAXY::Galaxy Global WorkSolarSystem.SOLARSYSTEM::SolarSystem XIncludeFile "Views/frmSolarSystem.pbi" XIncludeFile "Views/frmGalaxy.pbi" Declare frmMainCustom() ;- Main Loop If Window_frmMain() frmMainCustom() Define Index, ID ;This Loads the ListIcon with all Galaxies in the Database GALAXY::LoadListIcon(#Gadget_frmMain_liList) ;If there ARE Records select the First If ListEx::CountItems(#Gadget_frmMain_liList) > 0 ListEx::SetState(#Gadget_frmMain_liList, 0) EndI
Post a Comment
Read more

Connecting Forms to Data-Layer (part 4)

 Now we will finish out our frmMain or our Application Desk Top  Scrolling down our Control loop we get to the section with out List of Galaxies, and our Create, Modify, Delete Buttons. Our first change will be to the List, specifically we want the default behavior of Double-Clicking an Item in our list to be "Modify". To accomplish this, we insert a PostEvent command which will Left-Click the the Modify Button for us. Case #Gadget_frmMain_liList Select EventType() Case #PB_EventType_LeftDoubleClick PostEvent(#PB_Event_Gadget, #Window_frmMain, #Gadget_frmMain_btModify, #PB_EventType_LeftClick) Default EndSelect Next we Come to the Create Button, Here we want to call our GalaxyCreate Method. Case #Gadget_frmMain_btCreate Select EventType() Case #PB_EventType_LeftClick GalaxyCreate() Default EndSelect Here is our FIRST
Post a Comment
Read more