I think most people either use OrcaScript or PowerGen.

I also have a PB Bootstrap product available:

http://www.topwizprogramming.com/bootstrap.html

Hi Yuri;

    The only ways to import PB object source files is to either: a) use the IDE, b) ORCA API, or ORCAScript. PB does have a LibraryImport () function but Sybase purposely  handicapped it to only work on DataWindow objects. Mainly because they wanted revenue from selling (Licensing) ORCA. This limitation has never been lifted on the LibraryImport() command. If it were, you could easily write  SCM (Source Code Management) utilities of your own - all in PB. Feel free to open a support ticket to see if Engineering can lift this restriction on the command.

Regards ... Chris

Hi Chris, Hi All,
I'm looking for an orca script sample to export an object from a pbl, modify it to change a value, then reimport it into the pbl and finally compile all the app.

It would be a great help if you have some :)

Thanks in advance
S.

I find myself wondering how the PBG file would get out of sync, since out pbg's are under source control along with everything else, but...

You could write a script to create your PBG file and then use AutoCompile (PBC170.exe) to build your target.  The PBG file syntax is pretty simple, as is the target (.PBT) syntax.  With the .pbt, .pbg's, and .sr*'s, you can build your PBL's with PBC170.

There are two ways to make this easy.
1. This simple answer is bad for source control:  keep all of your PBLs in a single folder. Then compiling the code is simple and there's no risk of losing a PBL.

2. The other method is to use a BATCH file to copy all of your files from their various folders into a COMPILE folder. It works like this:
    a) first delete all of the old files from c:\compile (or wherever you put your compile folder)

   b) copy the PBLs, PBRs, DLLs, images, and whatever else you need from the various development folders into the COMPILE folder.

       Alternately, you can keep the DLLs and images in separate folders and have the PATH environment valiable include those folders.

   c) Run the batch file.

   d) Change the TARGET file in the PB IDE to point to the code in the COMPILE folder

   e) Deploy the code in the COMPILE folder

Later -

Olan

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Sample batch file:

@echo off
color e2

;rem    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
;rem    Update the yourAPP files in C:\Build12
;rem    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
;rem
;rem    Author:     Olan Knight
;rem    Date:       17-JUL-2012
;rem    Version:    1.01
;rem    
;rem    The purpose of this batch file is to copy the current PBLs
;rem    from the C:\Apps12 folder into your C:\Apps12\Build12 folder.
;rem    
;rem    Note that everyone needs to have the exact same directory
;rem    structure in order for us to implement source control software.
;rem    Do NOT change the structure of the C:\Apps12 directory.
;rem      
;rem    KEEP YOUR WORKSPACE AND TARGETS AT THE "C:\Apps12\Build12" LEVEL!!!
;rem   
;rem    Note: Remember that the RESOURCES file is still on the M drive
;rem        so your PATH variable must include the Resources folder.
;rem    ----------------------------------------------------------------

echo.
echo.
echo "Press enter to continue or c to quit"
echo.
pause " "

set DeleteFlags=/s /f /q
set CopyFlags=/s /k /r /y

;rem  =======================================================================
;rem  =======================================================================

echo.
echo.
echo.
echo.
echo  Copying the yourAPP libraries....
echo.
echo.

set   sourcepath=C:\Apps12\yourAPP
set   targetpath=C:\Apps12\Build12\yourAPP

echo.
echo.
echo  Delete the yourAPP files from "%targetpath%"...
;rem  ---------------------------------------------------
del  "%targetpath%"\CSGI_yourAPP\*.*       %DeleteFlags% > NUL
del  "%targetpath%"\yourAPP\*.*            %DeleteFlags% > NUL
del  "%targetpath%"\yourAPP_asap\*.*       %DeleteFlags% > NUL
.
.
.
del  "%targetpath%"\yourAPP_usage\*.*      %DeleteFlags% > NUL
del  "%targetpath%"\yourAPP_wc\*.*         %DeleteFlags% > NUL

del  "%targetpath%"\*.pbr                  %DeleteFlags% > NUL
del  "%targetpath%"\*.exe                  %DeleteFlags% > NUL

echo  Copy the YOURAPP files from "%sourcepath%" into "%targetpath%...    
;rem  --------------------------------------------------------------------
xcopy "%sourcepath%"\CSGI_yourAPP\*.PBL        "%targetpath%"\CSGI_yourAPP\*.*        %CopyFlags%
xcopy "%sourcepath%"\yourAPP\*.PBL             "%targetpath%"\yourAPP\*.*             %CopyFlags%
xcopy "%sourcepath%"\yourAPP_asap\*.PBL        "%targetpath%"\yourAPP_asap\*.*        %CopyFlags%
.
.
.
xcopy "%sourcepath%"\yourAPP_usage\*.PBL       "%targetpath%"\yourAPP_usage\*.*       %CopyFlags%
xcopy "%sourcepath%"\yourAPP_wc\*.PBL          "%targetpath%"\yourAPP_wc\*.*          %CopyFlags%

xcopy "%sourcepath%"\*.PBR                     "%targetpath%"\*.*                     %CopyFlags%

echo  Change the file attributes of the new C drive yourAPP files....
attrib   -r "%targetpath%"\*.*   /s

;rem  =======================================================================
;rem  =======================================================================

color a2

pause
echo on

Hi Yuri,

It is possible to create a PBG file (file format: See PB Help) from either a PBL file or a folder in the file system.

• Create from PBL file
  • Use LibraryDirectory(fileName, DirAll!) to obtain list of all classes in the PBL file
  • Create PBG content from that list
• Create from file folder
  • Use DirList( * ) to populate ListBox with list of files in a specific folder
  • Create PBG content from that list

Some 3rd party tools may implement similar functionality.

HTH  /Michael