Activity
From 01/19/2017 to 02/17/2017
02/17/2017
- 08:29 AM Feature #1521: implement gap analysis rules or backing database/marker approach
- Task branch @1521a@ for review updated to revision @11163@.
Adding changes in @gap_analysis_marking.xml@ to:
1. E... - 06:12 AM Feature #1521: implement gap analysis rules or backing database/marker approach
- > If the mark has been found on some step -> we can ignore further steps, saving CPU time, like this:
Good idea.
... - 07:42 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Task branch @1521a@ for review updated to revision @11162@.
In this update the global variables and built-in funct...
02/16/2017
- 03:47 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Task branch @1521a@ for review updated to revision @11161@.
Preparing candidate for global variables and built-in ... - 01:09 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Greg Shah wrote:
> > And I have reviewed the changes in 3209e since this merge. Do you think something is missed?
>... - 12:21 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- > And I have reviewed the changes in 3209e since this merge. Do you think something is missed?
Yes, I think there ... - 12:18 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Greg Shah wrote:
> Yes, please go ahead with adding all of these, including the webspeed functions. Treat the websp... - 05:03 AM Feature #1521: implement gap analysis rules or backing database/marker approach
- Yes, please go ahead with adding all of these, including the webspeed functions. Treat the webspeed functions just l...
- 10:33 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- The new candidates for built-in functions to add into @expressions.rules@ map:...
- 09:17 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Greg Shah wrote:
> Please fix @progress.g@ for @_msg@.
OK. Task branch @1521a@ for review updated to revision @11... - 08:48 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Please fix @progress.g@ for @_msg@.
- 08:41 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Good catch. I think this:...
- 07:44 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- OK. According to my refresh for variable/built-in functions criteria the @SUPER(kw_super)@ is the function, not varia...
02/15/2017
- 04:57 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Task branch @1521a@ for review updated to revision @11158@.
Fix removing function and system handles from global v... - 10:58 AM Feature #1521: implement gap analysis rules or backing database/marker approach
- If they have FUNC_ types they are not treated as global variables.
- 10:10 AM Feature #1521: implement gap analysis rules or backing database/marker approach
- >Please go back through your list of questions and make sure you only include VAR_ token types that are not system ha...
- 09:59 AM Feature #1521: implement gap analysis rules or backing database/marker approach
- Global variables are matched (see @profile.rpt@) using the @builtin_global_variables@ rule from @common-progress.rule...
- 09:19 AM Feature #1521: implement gap analysis rules or backing database/marker approach
- Several questions for handling built-in functions. The conversion support is performing in @convert/builtin_functions...
- 08:03 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Task branch @1521a@ for review updated to revision @11157@.
Added global variables list. Please take a look if som...
02/14/2017
- 10:29 AM Bug #3242 (Test): parser console output written out of order
- A fix is committed to 3209e/11208. We do not bypass the thread executor service as proposed above, but we use it with...
- 08:43 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- +Global variables sub-task+
The new variables to add taken from 4GL documentation:...
02/13/2017
- 01:57 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Greg Shah wrote:
> Sure. Please take all the changes to the gap analysis from there. Then remove them from 3209e s... - 01:15 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Sure. Please take all the changes to the gap analysis from there. Then remove them from 3209e so there are no mergi...
- 12:50 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Can I add/merge your changes(with @3209e@) I noted working with @poc@ application for @expressions.rules@ into @1521a...
- 12:00 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- > The mapping for both already defined in expressions.rules file, all adding/change for mapping must be done in this ...
- 11:44 AM Feature #1521: implement gap analysis rules or backing database/marker approach
- Greg Shah wrote:
> Next, please work on:
>
> * all global variables (these are often called "built-in functions" ... - 10:52 AM Feature #1521: implement gap analysis rules or backing database/marker approach
- The result is good.
Next, please work on:
* all global variables (these are often called "built-in functions" i... - 10:43 AM Feature #1521: implement gap analysis rules or backing database/marker approach
- Greg Shah wrote:
> I think we support the widget option @kw_width@ at conversion (it is mapped to @setWidthChars()@ ... - 10:20 AM Feature #1521: implement gap analysis rules or backing database/marker approach
- I think we support the widget option @kw_width@ at conversion (it is mapped to @setWidthChars()@ in @frame_generator....
- 12:24 PM Feature #3225: windows vs linux in p2j.cfg.xml
- Constantin Asofiei wrote:
> Ovidiu, can you take a look at @searchpath@ in directory.xml, too? From what I see, thi...
02/11/2017
- 04:22 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Task branch @1521a@ for review updated to revision @11154@.
Adding missed options after re-check with bigger proje... - 07:31 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Task branch @1521a@ for review updated to revision @11153@.
The changes:
1. @MENU-ITEM(WID_MENU_ITM)@ removed fro...
02/10/2017
- 05:55 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Greg Shah wrote:
> > This refers to validate() method, even not the attribute.
>
> No, this is not the validate()... - 05:51 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- > This refers to validate() method, even not the attribute.
No, this is not the validate() method. It is really a... - 05:49 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Almost all issues have fixed. One more point where I have some doubts.
The @widget_options@ function considers @KW... - 12:44 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- > Looks like we have the browse widget that considering as option for frame widget. This means it must be moved to th...
- 11:35 AM Feature #1521: implement gap analysis rules or backing database/marker approach
- Task branch @1521a@ for review updated to revision @11152@.
This is the first working release of the widget option... - 09:31 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- > I can see if the support level data are there to check the new rule set is working properly. Correct?
Yes.
> ... - 02:07 PM Feature #3247: need for different configuration values for different parts of a conversion project
- Starting with revision 11139, FWD configuration file (@fwd.cfg.xml@) is platform independent, meaning that the files ...
- 01:56 PM Feature #3247 (New): need for different configuration values for different parts of a conversion ...
02/09/2017
- 05:44 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Please clarify me some points if my understanding is wrong.
1. The control file is @reports/profile.rpt@, current ... - 02:04 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Task branch @1521a@ for review updated to revision @11151@.
More clean ups for @user_interface.rules@ file. The op... - 08:54 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Task branch @1521a@ for review updated to revision @11150@.
Fix for UI options list status maps. This is the base ...
02/08/2017
- 11:40 AM Feature #1521: implement gap analysis rules or backing database/marker approach
- > But from the other widgets map(where only fill-in is considering) the support is: rw.cvt_lvl_full | rw.rt_lvl_full....
- 11:18 AM Feature #1521: implement gap analysis rules or backing database/marker approach
- >The Progress docs say that auto-return can also be used for a browse column. If we don't support it fully at runtime...
- 08:52 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- I have prepared the new list of the widget's options:...
02/07/2017
- 11:26 AM Bug #3242: parser console output written out of order
- The parsing step of the front end conversion phase uses a thread pool managed by an @ExecutorService@ (see @ScanDrive...
- 11:01 AM Bug #3242 (Closed): parser console output written out of order
01/31/2017
- 09:37 AM Feature #1521: implement gap analysis rules or backing database/marker approach
- I think there are some problems with how you are going about this task.
1. There still seems to be confusion about...
01/30/2017
- 05:42 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Task branch @1521a@ for review updated to revision @11149@.
Added options for widgets other than browse and frame....
01/28/2017
- 09:59 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Task branch @1521a@ for review updated to revision @11148@.
Added options from general format phrase into widget o...
01/27/2017
- 12:23 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- > Widget options map should be separated from browse widget map?
Yes.
> Another word we will have 3 types of d... - 12:14 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Thinking about widget options map implementation. And some questions I have got:
1. Widget options map should be sep... - 11:01 AM Feature #1521: implement gap analysis rules or backing database/marker approach
- Task branch @1521a@ rebased with trunk @11140@, new version is @11147@.
- 10:21 AM Feature #1521: implement gap analysis rules or backing database/marker approach
- Task branch @1521a@ rebased with trunk @11139@, new version is @11146@.
- 09:12 AM Feature #1521: implement gap analysis rules or backing database/marker approach
- Task branch @1521a@ for review updated to revision @11145@.
Finished options support status adding into @user_inte... - 07:26 AM Feature #1521: implement gap analysis rules or backing database/marker approach
- Greg Shah wrote:
> > After rescan 4GL documents found more options to add:
>
> I don't understand. These are all... - 09:24 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- > After rescan 4GL documents found more options to add:
I don't understand. These are all visible in the @progres... - 09:22 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- > 1. @FRAME@ option of the clause like @FORM something WITH FRAME fr@. In this case will the @FRAME@ be the option of...
- 12:09 PM Feature #3225: windows vs linux in p2j.cfg.xml
- Greg Shah wrote:
> Please update the Conversion Handbook "Project Setup chapter":/projects/p2j/wiki/Chapter_6_Projec... - 08:57 AM Feature #3225: windows vs linux in p2j.cfg.xml
- Please update the Conversion Handbook "Project Setup chapter":/projects/p2j/wiki/Chapter_6_Project_Setup#Global-Confi...
- 08:48 AM Feature #3225: windows vs linux in p2j.cfg.xml
- Greg Shah wrote:
> I agree, let's get this into the trunk. Go ahead with the merge.
The changes from branch were m... - 06:59 AM Feature #3225: windows vs linux in p2j.cfg.xml
- I agree, let's get this into the trunk. Go ahead with the merge.
1. Did you look at @searchpath@ (CA's question i... - 06:02 AM Feature #3225: windows vs linux in p2j.cfg.xml
- The conversion of combined project finished without errors, configured with @opsys=win32@.
I ran a combined test (na...
01/26/2017
- 06:33 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- After rescan 4GL documents found more options to add:
+Frame phrase:+... - 05:50 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- I have found additional options to add to frame options status. It is related to @FRAME phrase@. But I need some clar...
- 04:11 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Greg Shah wrote:
> > Both are the frame options, not attributes.
>
> @expressions.rules@ is where we document the... - 12:03 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- > Both are the frame options, not attributes.
@expressions.rules@ is where we document the attributes, not the opt... - 11:51 AM Feature #1521: implement gap analysis rules or backing database/marker approach
- Greg Shah wrote:
> Are you talking about the attributes or the options? Although the 4GL generally implements both ... - 11:23 AM Feature #1521: implement gap analysis rules or backing database/marker approach
- Are you talking about the attributes or the options? Although the 4GL generally implements both with the same backin...
- 11:16 AM Feature #1521: implement gap analysis rules or backing database/marker approach
- Found the attributes @PAGE-BOTTOM@ and @PAGE-TOP@ are both fully supported for conversion and runtime.
Do I need t... - 09:13 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Task branch @1521a@ for review updated to revision @11143@.
Completed handling of the browse widget options/attrib... - 01:58 PM Feature #3225: windows vs linux in p2j.cfg.xml
- > Since in the combined project they share the same parameter, I've chosen the opsys=win32, mainly because of GUI req...
- 01:51 PM Feature #3225: windows vs linux in p2j.cfg.xml
- Greg Shah wrote:
> How is testing going?
I started the over night conversion for GUI, hoping to have it ready in ... - 01:21 PM Feature #3225: windows vs linux in p2j.cfg.xml
- How is testing going?
01/25/2017
- 11:51 AM Feature #3225: windows vs linux in p2j.cfg.xml
- Ovidiu, can you take a look at @searchpath@ in directory.xml, too? From what I see, this is OS-dependent, too...
- 11:50 AM Feature #3225: windows vs linux in p2j.cfg.xml
- > I don't think this will require retesting.
Agreed.
Excellent. After the @WINDOW-SYSTEM@ changes are checked... - 11:32 AM Feature #3225: windows vs linux in p2j.cfg.xml
- I already rebased the branch to latest trunk (rev 11144). Before rebasing, the branch passed all tests (devsrv01 and ...
- 11:21 AM Feature #3225: windows vs linux in p2j.cfg.xml
- Code Review Task Branch 3225a Revision 11144
I like the changes.
Other than the @WINDOW-SYSTEM@ defaults, what ... - 11:06 AM Feature #3225: windows vs linux in p2j.cfg.xml
- I believe that if the original application code is run in @prowin32.exe@, then @WINDOW-SYSTEM@ will return @MS-WIN95@...
- 10:58 AM Feature #3225: windows vs linux in p2j.cfg.xml
- Greg Shah wrote:
> For GUI projects, we should default @WINDOW-SYSTEM@ to @MS-WIN95@ for both:
>
> * @LogicalTerm... - 10:51 AM Feature #3225: windows vs linux in p2j.cfg.xml
- For GUI projects, we should default @WINDOW-SYSTEM@ to @MS-WIN95@ for both:
* @LogicalTerminal.getWindowSystem()@ ... - 09:44 AM Feature #3225: windows vs linux in p2j.cfg.xml
- @SESSION:WINDOW-SYSTEM@ handling is unchanged. It should be @TTY@ as defaulted in @com.goldencode.p2j.preproc.Options...
- 09:03 AM Feature #3225: windows vs linux in p2j.cfg.xml
- To what value are you defaulting the @WINDOWS-SYSTEM@ preprocessor define?
- 08:46 AM Feature #3225: windows vs linux in p2j.cfg.xml
- Ovidiu, 3225a rev 11143 looks OK - I see that you rely on @OPSYS=WIN32@ to determine if this is a Windows OS. I need...
- 07:38 AM Feature #1521: implement gap analysis rules or backing database/marker approach
- Ask Stanislav if you have any questions about the status of a browse option.
- 09:45 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Task branch @1521a@ for review updated to revision @11142@.
This is update for browse widget options status. Not a...
01/24/2017
- 05:56 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Greg Shah wrote:
> Both @MIN-HEIGHT-CHARS@ and @CREATE-ON-ADD@ can be marked as @rw.rt_lvl_stub@.
Task branch @15... - 05:11 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Both @MIN-HEIGHT-CHARS@ and @CREATE-ON-ADD@ can be marked as @rw.rt_lvl_stub@.
- 04:04 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- The attribute @CREATE-ON-ADD@ has limited support even less than @MIN-HEIGHT-CHARS@. It is implemented on the server ...
- 03:48 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- The attribute @MIN-HEIGHT-CHARS@ is supported but only by setting @config.minHeightChars@ value. Actually this value ...
- 02:39 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- @kw_creat_oa@ is an attribute. We have some support. You'll have to check the details.
- 02:26 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Greg Shah wrote:
> Method @kw_mov_col@ is now fully supported too.
OK. I looked inside the task and one point lef... - 02:19 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Method @kw_mov_col@ is now fully supported too.
- 02:13 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- > Is it normal?
Yes, for the FWD project (and TRPL and Harness).
> Our internals are now visible for everyone?... - 01:40 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Greg Shah wrote:
> I think some updates to the supported attributes are still missing.
>
> Both prog.kw_col_mov a... - 01:18 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- I think some updates to the supported attributes are still missing.
Both prog.kw_col_mov and prog.kw_col_res are n... - 09:30 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Task branch @1521a@ for review updated to revision @11139@. Rebased with trunk @11138@, new version is @11140@.
Cr... - 08:14 AM Feature #3225: windows vs linux in p2j.cfg.xml
- Task branch 3225a was updated yesterday. The current revision is 11142. The latest changes expect that all paths in @...
01/23/2017
- 05:30 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- I guess the answer depends on whether there are child nodes that represent unsupported configurations. For now, just...
- 03:24 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- The question:
If other phrases are the parts of the frame phrase or frame option - should it be also added into @u... - 04:13 AM Feature #1521: implement gap analysis rules or backing database/marker approach
- Greg Shah wrote:
> In preference to item 5 of note 7, please work on these parts of item 4:
>
> * frame options a...
01/21/2017
- 07:27 AM Feature #1521: implement gap analysis rules or backing database/marker approach
- In preference to item 5 of note 7, please work on these parts of item 4:
* frame options and frame phrases
* brow...
01/20/2017
- 06:06 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Yes. That makes sense.
- 05:42 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Greg Shah wrote:
> One tricky thing is that the PatternEngine will require us to pass in an AST when we run it. But... - 04:56 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- One tricky thing is that the PatternEngine will require us to pass in an AST when we run it. But all these rules don...
- 04:54 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- > As far as I understand we need to use the data provided by expression.rules file to generate the textile tables lik...
- 04:39 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Clarification for the implementation point number 5 in note #1521-7.
As far as I understand we need to use the dat... - 12:01 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Code Review Task Branch 1521a Revision 11138
The changes are good. - 11:03 AM Feature #1521: implement gap analysis rules or backing database/marker approach
- Task branch @1521a@ for review updated to revision @11138@.
The @expressions.rules@ updated to change the supporte... - 10:12 AM Feature #1521: implement gap analysis rules or backing database/marker approach
- Greg Shah wrote:
> @<rule>attrs.put(prog.kw_cur_iter, rw.cvt_lvl_full | rw.rt_lvl_partial)</rule>@ seems corre... - 09:21 AM Feature #1521: implement gap analysis rules or backing database/marker approach
- @<rule>attrs.put(prog.kw_cur_iter, rw.cvt_lvl_full | rw.rt_lvl_partial)</rule>@ seems correct. Please put a co...
- 08:56 AM Feature #1521: implement gap analysis rules or backing database/marker approach
- Rebased task branch @1251a@ from P2J trunk revision @11137@. Still no changes since branch creation.
- 09:08 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- I have scanned the files from bzr @log -v -r11021@. In addition I have looked into p2j/ui/* directory(with subdirs) a...
- 01:29 PM Feature #3225: windows vs linux in p2j.cfg.xml
- > I will fix the separators definition also.
What do you mean?
I think the @file-separator@ and @path-separato... - 01:22 PM Feature #3225: windows vs linux in p2j.cfg.xml
- Greg Shah wrote:
> > OTOH, we force in the definition of propath parameters that are dependent on the current machin... - 01:06 PM Feature #3225: windows vs linux in p2j.cfg.xml
- > so @file-separator@ and @path-separator@ are used by conversion to know how to parse the legacy strings found in co...
- 12:58 PM Feature #3225: windows vs linux in p2j.cfg.xml
- OK, so @file-separator@ and @path-separator@ are used by conversion to know how to parse the legacy strings found in ...
- 11:35 AM Feature #3225: windows vs linux in p2j.cfg.xml
- > I might not have understand it fully, but I had the feeling that the propath, file-separator and path-separator fro...
- 11:30 AM Feature #3225: windows vs linux in p2j.cfg.xml
- I might not have understand it fully, but I had the feeling that the @propath@, @file-separator@ and @path-separator@...
- 11:15 AM Feature #3225: windows vs linux in p2j.cfg.xml
- > please confirm, that these must be the legacy values as found on the OS where the legacy application was run, not w...
- 10:19 AM Feature #3225: windows vs linux in p2j.cfg.xml
- Ovidiu, review for 3225a rev 11141 :
* beside the @basepath@ which must use file-separator specific to the OS where ...
01/19/2017
- 02:44 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Created task branch @1521a@ from trunk revision @11136@.
- 01:57 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- I have found the @RESIZABLE@ attribute has runtime support. So at least one change is required for @expression.rules@...
- 01:32 PM Feature #3225: windows vs linux in p2j.cfg.xml
- Status of: 3225a/11139:
* passed full regression testing on devsrv01;
* conversion successful on both Linux/Windows...
Also available in: Atom