PDECODE

Active Member
New version

3.40 - [10.02.2011]
+ Buffers are now listed extra in explorer and not as temp-tables
+ Added detection of outside changes on source file - on Save
+ Added highlighting matching '(', ')', '[', ']', '{' and '}'
+ Remember AutoHide explorer setting
+ Added ability to specify number of items in Recenly used files list
+ Possibility disable long line marker - by setting to 0
* Fixed switched Expand & Colapse icons
* Rewritted some initialization code
* Fixed shortcut for File Close Ctrl+W -> Ctrl+F4, it was word wrap shortcut
* Fixed aliases keyword casing
 

PDECODE

Active Member
New version

3.50 - [14.09.2011]
* Fixed "Code beautify" if tab length <> 2
+ Added indentation line after WHEN on beautify CASE structure
* Fixed some internal white space handling in "Code beautify"
+ Changed Goto Line command from CTRL-J to CTRL-G
* No warning message after escape in Goto Line
+ COMMENTS colors are now joined to one color setting
+ Added captions to styles (for future language translations)
+ After Find action center the result in the center of the screen
+ Added ability to open multiple files at the same time
+ Rectangular selections can now handle also lines that have inaccesable space at the end
+ Added Full Screen editing
+ Created in main menu View section and some items moved here
+ Support for UTF-8 encoded files
* Fixed bug with no matching braces
+ New version dll (2.03 -> 2.28)
 

D.Cook

Member
Re: New version

Thanks for sharing a great ABL editor! It's becoming quite a mature tool.

A question about the syntax check and run commands: are they supposed to use the Propaths defined in the bottom-right of the options dialog? If not, what are these Propaths for?
So far, I've just set my propath for the syntax command using an ini file..

Also, it would be fantastic if the syntax check command output could be captured and displayed within Piew, taking the user to the exact line number and column of the error (like in ConTEXT for example).

And another suggestion: more keyboard shortcuts would be great (eg for check syntax command and bookmarks).
 

UncleNel

New Member
Re: New version

Thanks for sharing a great ABL editor! It's becoming quite a mature tool.

A question about the syntax check and run commands: are they supposed to use the Propaths defined in the bottom-right of the options dialog? If not, what are these Propaths for?
So far, I've just set my propath for the syntax command using an ini file..

Also, it would be fantastic if the syntax check command output could be captured and displayed within Piew, taking the user to the exact line number and column of the error (like in ConTEXT for example).

And another suggestion: more keyboard shortcuts would be great (eg for check syntax command and bookmarks).

To answer your syntax question. It works for me, although I had to do some tweaking. Here is a snippet of the syntax file that I use:

Code:
COMPILE VALUE(SESSION:PARAMETER) SAVE = NO NO-ERROR.

IF /*COMPILER:ERROR*/ COMPILER:NUM-MESSAGES GT 0 THEN DO:
  ASSIGN cMsg = "".
  DO i =1 TO COMPILER:NUM-MESSAGES:
    ASSIGN cMsg = cMsg + SUBSTITUTE("&4:&1~n~tRow:&2 Col:&3~n",
                          COMPILER:GET-MESSAGE(i),
                          COMPILER:ERROR-ROW, 
                          COMPILER:ERROR-COLUMN,
                          if COMPILER:WARNING eq TRUE then "WARNING"
                          else "ERROR")  .
                          
  END.
  MESSAGE cMsg VIEW-AS ALERT-BOX TITLE "<<COMPILER MESSAGES>>".
  
  RUN WinExec (SUBSTITUTE("C:\Apps\Piew\Piew.exe &1|ROW:&2|COL:&3", 
                            SESSION:PARAMETER, /*input program name*/
                            COMPILER:ERROR-ROW, 
                            COMPILER:ERROR-COLUMN), 
        1, 
        OUTPUT iRet).
END. /*compiler error*/
ELSE DO: 
  MESSAGE "<<SYNTAX CHECK COMPLETE>>~n  NO ERRORS FOUND  " 
    VIEW-AS ALERT-BOX INFORMATION.
  
  RUN WinExec (SUBSTITUTE("C:\Apps\Piew\Piew.exe &1", 
                            SESSION:PARAMETER), /*input program name*/
        1, 
        OUTPUT iRet).
END. /*no compiler error*/
 

PDECODE

Active Member
Re: New version

If not, what are these Propaths for?
In settings you can set 5 Propaths profiles, they are used in "Open selected string as new file" function. Piew try search in these paths for selected string in current editor. Propaths can be enabled or disabled by clicking on checkbox. You can use more paths in each profile, delimiter is ';' character.
 

D.Cook

Member
Re: New version

Thanks guys, I hadn't realised you have to set the program directory in the syntax.p file. I think a good solution to avoid this would be to pass the program directory in as a parameter. And while we're at it pass, the propath as a parameter also.

For example:
Code:
cPiewDir = ENTRY(1, SESSION:PARAMETER). 
cProgram = ENTRY(2, SESSION:PARAMETER). 
PROPATH  = ENTRY(3, SESSION:PARAMETER). 

RUN WinExec (SUBSTITUTE("&1\Piew.exe &2|ROW:&3|COL:&4",
                             cPiewDir,
                             cProgram,
                             COMPILER:ERROR-ROW,
                             COMPILER:ERROR-COLUMN),
                           1, OUTPUT iRet).

This way, a future version of Piew could use the propaths set in the options dialog for the syntax check and run command (param %3), to save having to set up an ini file or modify the .p scripts. So the command line setting would look like this:
Code:
dlc102a\bin\prowin32.exe -pf mydb.pf -p "%1\syntax3.p" -param "%1,%2,%3"
(Where %3 would be the ticked propaths, this is just my suggested improvement. You could copy your propaths in here for now.)
 

Attachments

  • syntax3.p
    1.8 KB · Views: 14

D.Cook

Member
Re: New version

And if you don't like waiting for the GUI splash screen every time you compile, why not switch to character mode? Eg:

Code:
dlc102a\bin\[B]_progres.exe -cpinternal ISO8859-1[/B] -pf mydb.pf -p "%1\syntax3.p" -param "%1,%2,%3"

Note that Progress uses the console Screen Buffer Size instead of Window Size, which defaults to 300 and makes the display hard to read. From the context menu choose Properties, Layout Tab, and set Screen Buffer Size same as Window Size (25). Click ok then choose "Save properties for future windows with same title".
 

PDECODE

Active Member
Re: New version

If you have other ideas that can improve calling parameters - i can make some changes ...
 

PDECODE

Active Member
New version

3.60 - [16.04.2012]
+ Added possibility change charset from more types (problem with displaying Russian text written in code page 866)
+ Added possibility open files with Ctrl + Mouse click used in code
+ Changed brackets highlighting now only occur when the cursor is before the bracket
+ Added some shortcuts: Check syntax, Run and Bookmarks
+ Go to a line (ctrl-G) now focus the line in center of viewing area
* Removed function prototypes that "steal" space from code explorer
+ Added new replace parameter in check syntax and run command: %3 - replaces to checked PROPATHS in settings
* Changed syntax.p and run.p, read more inside (update your saved commandline if you use it!)
 

rash

Member
Hello,
I have set the propaths as given below:

Help File:
C:\Program Files\Progress\prohelp\
lgrfeng.hlp
Syntax Checking:
C:\Program Files\Progress\bin\prowin32.exe -ini "C:\Program Files\Progress\installd.ini" -pf "C:\Program Files\Progress\startup.pf" -p "%1\syntax.p" -param "%1,%2"
Run Progress File:
C:\Program Files\Progress\bin\prowin32.exe -ini "C:\Program Files\Progress\installd.ini" -pf "C:\Program Files\Progress\startup.pf" -p "%1\run.p" -param "%1,%2"

But while checking syntax it's throwing an error:
msgOpen:unable to open message file: PROMSGS
 

RealHeavyDude

Well-Known Member
You don't supply the -pf startup.pf. It will automatically be used by all Progress session - no need to specify it.

What is the installd.ini in the Progress installation directory? Is that a file you have created? Why would you create it in the installation directory?

The error message you see usually either means that the PROPATH variable in the ini file is not correct or the ini cannot be found, neither in the registry nor in the PROPATH.

Heavy Regards, RealHeavyDude.
 

rash

Member
Hi,
Now I can check the syntax & run the program.
But how to connect database?
e.q. What should I do to connect sports database in this editor?
 

Cringer

ProgressTalk.com Moderator
Staff member
You'll probably need to connect the db in the pf file mentioned in the startup shortcut.
 

PDECODE

Active Member
Hi,
Now I can check the syntax & run the program.
But how to connect database?
e.q. What should I do to connect sports database in this editor?

Piew doesn't support connection to PROGRESS DB (it's 3th party tool), maybe i can add feature that i can retrieve DB tables and fields through ODBC... and let user choose from them by editing ... Or some offline way with importing e.g. DB dump (*.df) file.

If you need connect to DB in you application then you should define it in *.pf file or directly in source.
 
Top