FWD » Core Development » Conversion Tools

01/20/2017

06:06 PM Feature #1521: implement gap analysis rules or backing database/marker approach

Yes. That makes sense. Greg Shah

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... Eugenie Lyzenko

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... Greg Shah

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... Greg Shah

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... Eugenie Lyzenko

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. Greg Shah

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... Eugenie Lyzenko

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... Eugenie Lyzenko

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... Greg Shah

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. Eugenie Lyzenko

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... Eugenie Lyzenko

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... Greg Shah

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... Ovidiu Maxiniuc

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... Greg Shah

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 ... Ovidiu Maxiniuc

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... Greg Shah

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@... Ovidiu Maxiniuc

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... Greg Shah

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 ... Constantin Asofiei

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@. Eugenie Lyzenko

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@... Eugenie Lyzenko

07:23 PM Feature #1521: implement gap analysis rules or backing database/marker approach

I think you have the right idea. I don't need you to review every line of code change. Instead, I just want you to ... Greg Shah

07:16 PM Feature #1521: implement gap analysis rules or backing database/marker approach

Let me clarify the point number 1 in in #1521-7.
The expression.rules file is a list of 4GL language elements(lite... Eugenie Lyzenko

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... Ovidiu Maxiniuc

01/17/2017

12:05 PM Feature #1521 (WIP): implement gap analysis rules or backing database/marker approach

Eugenie: You and I will be working on this together. It is time to complete this.
h3. Todos
# -Make sure that ... Greg Shah

11:23 AM Feature #1515: implement gap analysis views in all reports

This involves updating the @profile.rpt@ and @schema.rpt@ to change the @<report>@ element to include this attribute:... Greg Shah

01/13/2017

03:05 PM Feature #3225: windows vs linux in p2j.cfg.xml

Ovidiu Maxiniuc wrote:
> The same stands for @case-sensitive@, @path-separator@ and @file-separator@. They are used ... Constantin Asofiei

12:54 PM Feature #3225: windows vs linux in p2j.cfg.xml

Greg Shah wrote:
> I prefer to encode everything in a standard way (using @/@ and @:@).
Committed 1st revision. A... Ovidiu Maxiniuc

01/12/2017

02:58 PM Feature #3225: windows vs linux in p2j.cfg.xml

When we run conversion, you have to have a different @p2j.cfg.xml@ file that depends on whether you are running the c... Greg Shah

02:41 PM Feature #3225 (WIP): windows vs linux in p2j.cfg.xml

Greg Shah