Activity
From 01/30/2017 to 02/28/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....
Also available in: Atom