Announcement

Collapse
No announcement yet.

For those using UltraEdit or thinking of using it

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

  • For those using UltraEdit or thinking of using it

    I have posted an update to PBShell here.

    For anyone who eschews visual designers and is using UltraEdit, or is thinking about it, this is worth checking out. I couldn't live without it! Much slicker than batch files or scripts! UltraEdit now fills all my text/hex/html editing and multiple language programming needs.

    Implements PB-specific tools on the UltraEdit toolbar for:

    * Compile only (source code or resource script)
    * Syntax Check Compile (no output file)
    * Compile and Debug (invokes the PB debugger)
    * Compile and Execute (one-click test)
    * Execute last compilation of the program

    In addition, PBShell implements a mechanism for optional pre and/or post compilation processing (now additionally supports the #UTILITY metastatement).

    I've updated the description and help, concentrating on UltraEdit rather than "any editor", with simplified step-by-step implementation instructions.

    The files for download include an UltraEdit wordfile for PB/CC 5 & PB/Win 9 for syntax highlighting, code folding, function listing, etc.

    Add the PB help file(s) to the Help menu and you've got yourself an excellent PB IDE in addition to all the other features that UltraEdit provides!

    It's freeware, supplied with full PB source code.
    - LJ

  • #2
    I thought you were going to mention UEx, the new Linux version of UltraEdit.

    Because this is one half of a magic solution - the editor; the other half would be a (command-line) compiler from a well-known company in Florida

    Comment


    • #3
      Actually Laurence, your PBShell is a nice and well thought-out tool. I particularly like the pre- and post-compilation options.

      Comment


      • #4
        Thanks Christopher. I had some inspiration though - as I said, my aim was SED within UE.

        On the Linux and UEx issue, I would offer the following observations:

        (a) People attracted to Linux are probably the same people attracted to C/C++.
        (b) Linux users expect to get all their software for free.

        These two factors, in my opinion, make the potential user base PB for Linux vanishly small (albeit very vocal!). Given the development effort required to port a compiler to another operating system, I would be very surprised if PowerBASIC Inc. is giving priority to it. If I were them, I would be giving priority to 64-bit Windows.

        UE is different. The development effort is less (assuming that UE is written in C) and it's probably a sensible hedge for them which may (or may not) pay off in the future. I would be surprised if it made up a large part of their business in the short term though.

        While we're on the subject, there is something I've long wanted to get off my chest. The most vocal advocates for PB/Linux also tend to be vocal advocates for SDK style programming. Surely the programs most likely to recompile with minimal problems under a hypothetical PB/Linux are those written entirely using DDT.
        - LJ

        Comment


        • #5
          Laurence

          UltraEdit 15, is still my editor of choice, i will give a try to your PBShell utility asap, thank you for sharing it with us!

          ...
          Patrice Terrier
          www.zapsolution.com
          www.objreader.com
          Addons: GDImage.DLL 32/64-bit (Graphic library), WinLIFT.DLL 32/64-bit (Skin Engine).

          Comment


          • #6
            Surely the programs most likely to recompile with minimal problems under a hypothetical PB/Linux are those written entirely using DDT.
            That is why I use DDT only and no SDK

            Comment


            • #7
              Trying to get PBSHELL to work with PBWIN10.04

              UltraEdit Text/Hex Editor (x64)
              Version 25.00.0.68UEDIT64.

              Changed

              $DDE_SERVICE = "uedit64" was uedit32
              MajorWINMax_LG = 10 was 9

              Now it compiles but does not open the source code at the error point.


              My trace diagnostics show it is opening log and has determined the file, line number and column

              PBMAINError_ST=K:\Compilers\PBWin10\bin\PBWin.exe /L /Q /I.\;"K:\Compilers\PBWin10\WinApiJrs4";"K:\Compilers\PBWin10\SocketTools" "TETCIO.BAS"
              PBMAINError_ST=TETCIO.LOG
              PBMAINError_ST=POWERBASIC 10 FOR WINDOWS
              PBMAINError_ST=COPYRIGHT (C) 1996-2012 POWERBASIC INC.
              PBMAINError_ST=ENGLEWOOD, FLORIDA USA
              PBMAINError_ST=ALL RIGHTS RESERVED
              PBMAINError_ST=
              PBMAINError_ST=ERROR 519 IN K:\PYRI_PB\SHELLS\TETCIO\TETCIO_SOURCE\TETCIO.BAS(95:005): MISSING DECLARATION: DATADIRZ
              PBMAIN Mark_LG= 10
              OPENFILEINEDITOR File_ST=K:\PYRI_PB\SHELLS\TETCIO\TETCIO_SOURCE\TETCIO.BAS FileLine_LG= 95 Column_LG= 5

              Not sure what I else I need to fix?




              Comment


              • #8
                Ended up changing

                $DDE_MESSAGE = "uedit64 /foi " + $dq + "%F%/%L%/%C%" + $dq

                was

                '$DDE_MESSAGE = "[open (" + $dq + "%F%/%L%/%C%" + $dq +")]"

                Instead of using DDE In function OpenFileInEditor I used Shell

                Shell Message_ST, 0


                Comment

                Working...
                X