Announcement

Collapse
No announcement yet.

New freeware code generator for PBDLL60

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

  • New freeware code generator for PBDLL60

    I have just posted on both my home site and my English site, the new version
    of Prostart.Exe, version 2. It is a SDK style API code generator that builds
    startup application skeletons using CreateWindowEx style main windows. It
    has a later code design with better toolbar code and multi-pane status bar
    code.
    http://www.pbq.com.au/home/hutch/pbdll50.htm
    http://www.hutch.ukshells.co.uk/pbdll50.htm

    With a little practice, it is a 1 minute compiled user interface that has
    toolbar code, status bar code, file dialog support, client sizing code for
    any window or control that you may wish to place in the client area of the
    main window and other code options so that you can produce the project
    skeleton with the characteristics that you require.

    For PowerBASIC programmers who have yet to make the leap into true API style
    code, this code generator automates the hack API startup code so that you
    can concentrate on application design rather than the dificulties of just
    getting an application running.

    For the experienced PowerBASIC programmer, it is a tool for prototyping,
    testing code ideas without the hack work of getting a user interface going
    and a basic skeleton for building applications in.

    Code start at 8704 bytes and goes up to about 17k with all options. It will
    only run with the PBDLL60 compiler so if you have been holding back with
    your upgrade from PBDLL50, here is a good excuse to upgrade now.

    It is simple to set up and is ready to run as soon as the tools paths are
    set in the dialog box. All you need to do is create a directory for the new
    project and set it as the target directory. You can interactively build
    the skeleton and keep changing options until it has the characteristics
    you require.

    It is licenced as freeware (cannot be sold and is not for sale) and can be
    used by any PowerBASIC programmer who can use it free of any charge
    whatsoever.

    Hope it is useful to you.

    Regards,

    [email protected]
    hutch at movsd dot com
    The MASM Forum

    www.masm32.com

  • #2
    I set the paths and used target, but
    received some errors:
    unable to open include file 'include'
    fatal error rc 1015 project.rc1
    unable to locate project.res

    compiler file not found include d:\pb6\winapi.inc
    Looks like it created a project1.bas with
    include files to d:\pb6\winapi

    Thanks,
    Mike


    ------------------
    How long is an idea? Write it down.

    Comment


    • #3
      Same with me.

      Andreas


      ------------------

      Comment


      • #4
        I got those same errors too.
        Thought it was due to me putting pbdll in
        C:\program files\pbdll60
        (Just makes it easier to keep the ol' hard drive neat and tidy)
        but I guess not.

        After a few edits though, I got it to compile and away she went.

        Very nice touch of adding the inline assembly to maximize the message loop.

        Kevin

        ------------------
        mailto:[email protected][email protected]</A>
        :-)

        Comment


        • #5
          Yes, replacing any 'd:\pb6\...' did it. I also think, the assembler is well placed in the 'message pump'.

          Will you upload a new version?

          Andreas

          ------------------

          Comment


          • #6
            Thanks Hutch - another great release. I also found that even though I set the paths correct (D:\PBDLL60\Bin\Pbdll.exe etc), the generated rc and inc files persisted in showing D:\PB6\ etc. Once I edited these the exe was generated and ran well.

            Regards,

            David

            ------------------

            Comment


            • #7
              Guys,

              Thanks for the error report, I have most of it tracked down and
              will have the update posted in a few hours. Problem was I put the
              project down for a couple of months and when I finished it, I forgot
              to track down all of the original hard coded paths. Sloppy programming
              on my part but I guess we all do things like this from time to time.

              [email protected]

              ------------------
              hutch at movsd dot com
              The MASM Forum

              www.masm32.com

              Comment


              • #8
                I have just posted the update for prostart at the sam 2 addresses,
                http://www.pbq.com.au/home/hutch/pbdll50.htm http://www.hutch.ukshells.co.uk/pbdll50.htm

                I tested the update with a different installation of the PowerBASIC
                tools and it runs OK. I checked every file it generates to see if
                the correct path was added and it is writing the correct paths.

                I apologise for any inconvenience with the 1st version but most of
                the testing went into the code design over a period of about 3 months
                of use. From testing and using it for that period, it seems to build
                every option correctly so I hope it is a useful toy for starting
                projects and prototyping.

                Regards,

                [email protected]


                ------------------
                hutch at movsd dot com
                The MASM Forum

                www.masm32.com

                Comment


                • #9
                  Steve,

                  I just downloaded it and it worked fine. As we are both in Sydney, can I buy you lunch?

                  Regards,

                  David
                  9778 7121 (work)

                  ------------------

                  Comment


                  • #10
                    I'm using Prostart version 2.00a. It still seems to be having problems with the paths. I have PBDLL installed to C:\Program Files\PBDLL60\

                    When the makepb.bat file is created, I have to edit the paths to enclose the path in quotes "C:\Program Files\PBDLL60\Bin\Rc.exe" for instance.

                    Then I can run the bat file. However, then i get the following errors:

                    Error 493 in PROJECT.INC(25:14): Compiler file not found
                    Line 25: #INCLUDE "C:\Program Files\PBDLL60\Winapi\WIN32API.INC"

                    and I have to change the path to "C:\Progra~1\etc.." in order to get it to work.

                    Ive used VB for over 4 years, but i'm quite new to PB (just bought it today) and so i'm still getting used to working with include files. Should i just reinstall PB to the default directory so that I avoid all these long path name problems?

                    -Mike

                    ------------------

                    Comment


                    • #11
                      Steve

                      Thanks a million mate! I am in Canberra but will gladly dive up to Sydney to buy you lunch.

                      Siamack

                      P.S. For those who are wondering its only 500 miles to Sydney and back

                      ------------------


                      [This message has been edited by Siamack Yousofi (edited March 27, 2000).]

                      Comment


                      • #12
                        Mike, thats a 'short coming' of the compiler, not Steves code per se.

                        The actual PBDLL.EXE compiler is a 16-bit application and can only use short-filenames in any compiler directive statements. Some of the other tools like PowerGEN _may_ have problems with LFN's too. Obviously the code that the compiler creates can use LFN's but the compiler itself cannot.

                        It's easiest to reinstall into C:\PBDLL60 rather than use the "Program files" group.

                        --Lance.


                        ------------------
                        Lance
                        PowerBASIC Support
                        mailto:[email protected][email protected]</A>
                        Lance
                        mailto:[email protected]

                        Comment


                        • #13

                          Steve Hutchesson,

                          Prostart2a
                          Very Good program! Excellent Code!

                          What more could be said!

                          Thanks
                          Mike

                          ------------------
                          mwm
                          mwm

                          Comment

                          Working...
                          X