PSPad unicode 4.5.3 (2271) English

Hallo Holger,

you are right. Every Programmer has his own style and everyone is profited by enhancement of code-explorer. Send a email with your needs and some(all) sourcecode-samples you need to Jan. He does the (good) job.

Christian

Joël:

So $ always open a formula excepted if there is a \ just before $.
I hope this is clear !!

Yes, it's clear.

holger:

One more bug:
a temp-table definition can begin outside the first columns.

OK

komfa:

Send a email with your needs and some(all) sourcecode-samples you need to Jan. He does the (good) job.

Christian

Hallo Christian,

I think my sparely needs are posted already and for all occurences I sended him the Openedge Language Reference (.CHM) with many exambles inside.
Progress is one of the difficult languages concerning the amount of features and possibilities.

Holger

Sorry, but from help I don't now e.g. order of Code explorer items. Examples are fine, but I need to know what you really want.

What I need:
1. list of items (trees) and it's order in Code explorer
2. litle description and small example for each item, e.g. this definition starts from line begin and I want to see this part of line in the code explorer.

I think it's OK for both sides. I will do better code explorer for you and you will spare my time from reading whole language help.

OK,
except the found bugs and the feature to display Items under Procedures or Functions (only in this Case "run Statements" make a sense, so everything step by step).

1. Trees
Worktables (and Synonym: Workfiles)
Buffers
Both can be displayed under Temp-Tables in this order.

2. syntax and exambles are given in last post.
In Progress everything can begin anywhere.
The displayed Items can have the same behavior as that for Temp-Tables with only the Name. The names are always after the definition keyword.
exambles:
define new shared buffer <Name> ...
define new shared private workfile <Name> ...
define new shared private work-table <Name> ...

Where buffer, workfile and work-table are the keywords (like temp-table: to be searched for).
The Keywords should only be guilty if a "define" is given before.
I guess there's no need to know what comes after the <Name> (would be silly to display details!)

In the posted Syntax everything whats in [] is optional, and have to be ignored, when before the " Keyword Name " Section.

Hope it's cleared. Thank you very much.

Holger

Yes, it is clear.
buffers, workfiles, work-tables and temp-tables are ready. Will be available in the next build.

1) The bug I reported in 2269 regarding FTP file listing is still problematic in 2271. Just a friendly reminder.
2) With the HTML multi-highlighter, the following will cause a rendering issue. Use any HTML that contains at least two sets of tags where the start and close are not on the same line, such as:
<div>

</div>
<div>

</div>
a) Highlight part of one tag. The start / end tag should be highlighted blue.
b) Highlight part of the other tag. The start / end tag should be highlighted blue. The tag of the first set is still highlighted.

Note: you might have to repeat these steps to see this behavior.

Hi Jan,

I'm very happy actually with being able to see just function and procedure names, to be able to jump through code quickier. I thought that showing include files was a nice touch and just wanted to make it work better if possible.

I also noticed that function parameters are displayed only if they are on the same line with the function definition, should display everything starting from ( and ending with ), right now it's showing from ( to end of line.

Thanks again for a great job.
Cristian

mce:

Hi Jan,

I'm very happy actually with being able to see just function and procedure names, to be able to jump through code quickier. I thought that showing include files was a nice touch and just wanted to make it work better if possible.

I also noticed that function parameters are displayed only if they are on the same line with the function definition, should display everything starting from ( and ending with ), right now it's showing from ( to end of line.

Thanks again for a great job.
Cristian

Code explorer parses code line by line using regular expressions. It isn't syntax parser.