Announcement

Collapse
No announcement yet.

PDS to PBCC White Paper???

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Doug Ingram
    replied
    Fred,

    Well done - another great piece to the puzzle.

    Thanks - that's very helpful.

    Doug

    Leave a comment:


  • Fred Buffington
    replied
    Doug, several years ago i wrote an htm / text as a possible inclusion in
    several books on PB that were proposed but never came to fuition.

    I am not sure if the inclusions of the new features of pbcc4+/pbwin8+ are
    referenced but the htm file is still on my web site.
    http://oasys.rain.prohosting.com/APPENDIXA.htm
    hope it can help.

    Leave a comment:


  • Doug Ingram
    replied
    Bob,
    I guess that has all the stuff I was looking for.
    I made my own White Paper by printing it out.
    Thanks!!!
    Doug

    Leave a comment:


  • Bob Zale
    replied
    Hi Doug!

    In the PBCC Help File, GoTo the INDEX, then select "Upgrading from DOS"

    Best regards,

    Bob Zale
    PowerBASIC Inc.

    Leave a comment:


  • Doug Ingram
    replied
    Thanks Chris -good advice I'm sure.

    Leave a comment:


  • Chris Boss
    replied
    One other thing before doing the above,

    Separate the routines which are non-UI to one source file and all the routines which are UI related to another. You can write a parser to help here, by scanning routines to find ones which include common UI commands (ie. Clear, locate, print, inkey, input, color). Parse out the routines which have such commands into one file and the others into another.

    The more you automate the task (by parsing) the faster the conversion will be.

    The PB string commands and parse commands are great for writing parsers.

    Leave a comment:


  • Chris Boss
    replied
    One way to start is to find out how much of the app is not compatible with PBCC.

    Break up the source code into multiple BAS files.

    Then create a simply test program with just a PBMain in it and one messagebox and then one by one include the other source files.

    The idea is to see how much compiles without error.

    Find the problem areas which will pose the greatest problems in converting and separate the routines which need no modification into a separate source file and the uncompilable ones into another.

    Now if the modifications needed are quite logical, write a parser to read the problem source code and make as many changes that are reasonable using a parser.

    Lastly, it will be "crunch" time where you have to manually make changes.

    Leave a comment:


  • Doug Ingram
    replied
    Originally posted by Chris Boss View Post
    Are you porting an entire existing app from QBX to PBCC ?

    Or just portions of code ?

    Doesn't PBCC support the standard screen commands of QB ? (ie. locate, print, input, inkey)
    A huge application with numerous modules and subroutines.
    Where to start is the problem. I thought there was a paper on the main things to look out for - to save time starting up.

    Leave a comment:


  • Chris Boss
    replied
    Just a comment:

    If one is porting a commercial (?) application from DOS to Windows, it really makes sense to skip converting it to a console app and to try to create a real GUI application.

    One trick which is useful, is to run the DOS version (as a window, not full screen) and to take screen shots of all the screens (use PRINT SCREEN key and copy from clipboard).

    Next using a Visual Designer which supports Bitmap backgrounds, load the screenshots as backgrounds to forms and then use them as templates to design your GUI (with controls).

    I used a technique like this years ago when I converted a PDS (DOS) Basic app to VB 1.0.

    This allows you to design a real windows app which looks similiar to the DOS one, but have the benefits of a real windows app.

    Convert all the DOS menus to Windows menus.

    If you need low level keyboard control (ie. inkey$), try using either keyboard accelerators or you can trap keyboard messages in the apps message loop before they get sent to the windows.

    You will find that much of the non-GUI code will convert relatively easily with little change.

    Leave a comment:


  • Chris Boss
    replied
    Are you porting an entire existing app from QBX to PBCC ?

    Or just portions of code ?

    Doesn't PBCC support the standard screen commands of QB ? (ie. locate, print, input, inkey)

    Leave a comment:


  • Doug Ingram
    started a topic PDS to PBCC White Paper???

    PDS to PBCC White Paper???

    I know - I know ... the 147th thread on PDS/QBX to PBCC.

    However, I've got a huge project to start and it seems like I remember seeing a comprehensive White Paper on the major things to look out for. I searched and couldn't find it. If anyone has it - or could just tell me it does or doesn't exist, I can move on. Just trying to save a little time! TIA
    Last edited by Doug Ingram; 12 Jan 2008, 02:13 AM.
Working...
X