FWD » Core Development » Conversion Tools

04/12/2017

04:49 PM Feature #1514: implement fully dynamic reports (backed by the database)

A few notes about the RPC. While I agree with Greg that the REST-like programming model isn't a good fit, I think we ... Hynek Cihlar

11:59 AM Feature #1514: implement fully dynamic reports (backed by the database)

The objective for this task is to create a Java-based reporting engine that has an embedded web server (leveraging Je... Greg Shah

04/11/2017

05:39 PM Feature #1514: implement fully dynamic reports (backed by the database)

AngularJS can be use as a client of RESTful Web Services, https://docs.angularjs.org/tutorial/step_10, https://docs.... Sergey Ivanovskiy

04:29 PM Feature #1514: implement fully dynamic reports (backed by the database)

Eric Faulhaber wrote:
> What I'm trying to get at is your impression of GWT and specifically the RPC functionality
... Hynek Cihlar

03:36 PM Feature #1514: implement fully dynamic reports (backed by the database)

Eric, 3222a exposes @com.goldencode.p2j.admin.AdminServerImpl@ remotely to the browser GWT client. It implements an a... Sergey Ivanovskiy

02:23 PM Feature #1514: implement fully dynamic reports (backed by the database)

Hynek Cihlar wrote:
> Eric, let me first ask about the design of the report app. Why is the backend needed? Is the d... Eric Faulhaber

01:44 PM Feature #1514: implement fully dynamic reports (backed by the database)

Eric Faulhaber wrote:
> Hynek, Sergey, I've added you as watchers to this issue because I would like your feedback, ... Hynek Cihlar

01:18 PM Feature #1514: implement fully dynamic reports (backed by the database)

Thanks, I'm reading through the GWT project website now.
What I'm trying to get at is your impression of GWT and s... Eric Faulhaber

12:56 PM Feature #1514: implement fully dynamic reports (backed by the database)

It seems that there are these GWT capabilities http://www.gwtproject.org/doc/latest/tutorial/JSON.html, http://www.gw... Sergey Ivanovskiy

12:24 PM Feature #1514 (WIP): implement fully dynamic reports (backed by the database)

Created branch 1514a. Eric Faulhaber

12:13 PM Feature #1514: implement fully dynamic reports (backed by the database)

Hynek, Sergey, I've added you as watchers to this issue because I would like your feedback, based on your use of GWT ... Eric Faulhaber

08:27 AM Feature #1521: implement gap analysis rules or backing database/marker approach

Greg Shah wrote:
> It will depend on the list of use cases. Make the list here and I will share specific thoughts.
... Eugenie Lyzenko

05:26 AM Feature #1521: implement gap analysis rules or backing database/marker approach

> The remaining keyword is SYMBOL. As I recall there were notes for this keyword, need to perform special processing ... Greg Shah

05:25 AM Feature #1521: implement gap analysis rules or backing database/marker approach

> If the keyword is not encountered in rule file - does it always mean the support level is none?
Usually, yes.
... Greg Shah

04/10/2017

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

Task branch @1521c@ for review updated to revision @11149@.
This is the next step update. For @OO@ and @SQL@ group... Eugenie Lyzenko

04/08/2017

11:56 AM Feature #1521: implement gap analysis rules or backing database/marker approach

> We do not even have the WID_* keyword for control frame widget. Is it OK at this time for progress.g?
Yes, this ... Greg Shah

11:46 AM Feature #1521: implement gap analysis rules or backing database/marker approach

You are mis-interpreting the parser.
This code:... Greg Shah

11:28 AM Feature #1521: implement gap analysis rules or backing database/marker approach

Greg Shah wrote:
> I think you are mistaken. What makes you think they are transformed into other elements?
For ex... Eugenie Lyzenko

09:22 AM Feature #1521: implement gap analysis rules or backing database/marker approach

> I declared all of them as having full support.
No, it is incorrect. All of these are NONE.
> Although I hav... Greg Shah

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

Task branch @1521c@ for review updated to revision @11148@.
This is not yet complete version. Items under investig... Eugenie Lyzenko

04/06/2017

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

Greg Shah wrote:
> Eugenie Lyzenko wrote:
> The questions for the widgets:
>
> 1. Do we support the inclusion of... Eugenie Lyzenko

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

Rebased task branch @1521c@ from P2J trunk revision @11146@. New revision is @11147@. Eugenie Lyzenko

05:36 AM Feature #1521: implement gap analysis rules or backing database/marker approach

Eugenie Lyzenko wrote:
> Searched widget support level. And found all of them except @wid_sub_menu@ has partial supp... Greg Shah

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

Searched widget support level. And found all of them except @wid_sub_menu@ has partial support level. This means ther... Eugenie Lyzenko

04/05/2017

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

Greg,
Support level marking question:
Assume for the button widget all references are supported within expression... Eugenie Lyzenko

04/01/2017

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

> So the background to describe the support level is detailing investigation of the convert/expressions.rules, corre... Greg Shah

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

Thinking about the way to find out the support status info for expression related keywords. Looks like the simple sea... Eugenie Lyzenko

03/31/2017

03:21 AM Feature #1521: implement gap analysis rules or backing database/marker approach

> These are known as "compiler constants" and having predefined values(0,1,2,...).
Yes.
> This means all of the... Greg Shah

03/30/2017

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

Greg Shah wrote:
> > Add to existed marking for literals?
>
> Yes, just add them to the map of literals. Why do ... Eugenie Lyzenko

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

Greg Shah wrote:
> Ignore FILENAME, in expressions it needs no marking.
>
> @COLON@ needs to be handled. It shou... Eugenie Lyzenko

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

Ignore FILENAME, in expressions it needs no marking.
@COLON@ needs to be handled. It should be handled on its own... Greg Shah

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

Updated and fixed keywords distribution into the groups:
@fields@
FIELD_BLOB
FIELD_CHAR
FIELD_CLASS
FIELD_CLOB... Eugenie Lyzenko

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

>> Add to existed marking fro literals?
>Yes, just add them to the map of literals. Why do anything else?
OK. Eugenie Lyzenko

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

> Add to existed marking fro literals?
Yes, just add them to the map of literals. Why do anything else?
> It ... Greg Shah

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

Greg Shah wrote:
> > KW_FIND_CS
> > KW_FIND_GLO
> > KW_FIND_NO
> > KW_FIND_PO
> > KW_FIND_WA
> > KW_WIN_DMIN
>... Eugenie Lyzenko

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

> KW_AVG
> KW_COUNT
> KW_MAX
> KW_MIN
> KW_SUM
These are already handled.
> MULTIPLY
This is handled tod... Greg Shah

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

I have added @primary_expr@ with these sub-rules into general @expr@ schema. As to "unusual" built-in functions, almo... Eugenie Lyzenko

08:21 AM Feature #1521: implement gap analysis rules or backing database/marker approach

>> I thought this was replaced with SYMBOL:
> ... Greg Shah

07:40 AM Feature #1521: implement gap analysis rules or backing database/marker approach

Greg Shah wrote:
> What about DB_REF_NON_STATIC?
I thought this was replaced with @SYMBOL@:... Eugenie Lyzenko

03:48 AM Feature #1521: implement gap analysis rules or backing database/marker approach

What about DB_REF_NON_STATIC? Greg Shah

03:47 AM Feature #1521: implement gap analysis rules or backing database/marker approach

Did you check to see if we are marking all of the "unusual" built-in functions properly? Here is a list:
sql_aggr... Greg Shah

03:47 AM Feature #1521: implement gap analysis rules or backing database/marker approach

I think that @primary_expr@ is missing from the @expr@ call tree in #1521-153. Have you handled all of these cases? Greg Shah

03:41 AM Feature #1521: implement gap analysis rules or backing database/marker approach

> KW_BETWEEN
> KW_BY_PTR
> KW_BY_VAR_P
> KW_IS
These are not variables. All variables are VAR_ only. Please l... Greg Shah

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

Here is the expressions related keywords distributed to the respective groups. We can create either single file for a... Eugenie Lyzenko

03/29/2017

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

The candidate list in note #149 has been updated based on recent research. Start separating the keywords for standalo... Eugenie Lyzenko

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

This is the complete @expr@ rules tree:... Eugenie Lyzenko

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

New keywords to process:... Eugenie Lyzenko

03/28/2017

05:34 AM Feature #1521: implement gap analysis rules or backing database/marker approach

> The question for UNKNOWN_TOKEN. This special artificial keyword means the detected keyword behind is not registered... Greg Shah

03/27/2017

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

I have checked once again all already marked categories in @gaps/gap_analysis_marking.xml@ and have not found somethi... Eugenie Lyzenko

09:11 AM Feature #1521: implement gap analysis rules or backing database/marker approach

The candidate list for expression related keywords to add:... Eugenie Lyzenko

03/24/2017

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

Greg Shah wrote:
> > There are two more double items found for built-in functions:
>
> Fix those in 1521c.
Don... Eugenie Lyzenko

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

Created task branch @1521c@ from trunk revision @11144@. Eugenie Lyzenko

11:00 AM Feature #1521: implement gap analysis rules or backing database/marker approach

> There are two more double items found for built-in functions:
Fix those in 1521c. Greg Shah

11:00 AM Feature #1521: implement gap analysis rules or backing database/marker approach

> The remaining FUNC_ that are not marked are:
> ...
> Correct?
No. We already mark any FUNC_ type that is mar... Greg Shah

10:54 AM Feature #1521: implement gap analysis rules or backing database/marker approach

Greg Shah wrote:
>
> By the way, we already handle all the @FUNC_@ types that are marked as "builtin". The non-bu... Eugenie Lyzenko

08:24 AM Feature #1521: implement gap analysis rules or backing database/marker approach

> General gap concept question. We need to enumerate all possible keywords and put them in a separate groups by some ... Greg Shah

12:25 AM Feature #1521: implement gap analysis rules or backing database/marker approach

New expression related(direct or indirect from @9th and highest precedence level of Progress 4GL expressions@) keywor... Eugenie Lyzenko

03/23/2017

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

I checked in "Made 'all' build target depend on 'distribution' target." to 1521b revision 11149. Hynek Cihlar

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

Fixed. Greg Shah

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

Greg,
Checking the keywords for already handled status I found small issue in @gaps/expression.rules@ file:... Eugenie Lyzenko

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

1521b is frozen at this time. Eric is putting it through conversion regression testing. It has no runtime implicati... Greg Shah

07:38 AM Feature #1521: implement gap analysis rules or backing database/marker approach

> What about 9th and highest precendence level of Progress 4GL expressions? Do we need to consider the cases included... Greg Shah

03/22/2017

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

Greg Shah wrote:
> Most of the token types in your list are already handled by the operators list in @gaps/expressio... Eugenie Lyzenko

09:02 AM Feature #1521: implement gap analysis rules or backing database/marker approach

Most of the token types in your list are already handled by the operators list in @gaps/expressions.rules@, right?
... Greg Shah

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

The keywords extracted from different kind of expressions(in @progress.g@):... Eugenie Lyzenko

03/21/2017

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

I want you to focus on the @expr@ rule in @progress.g@. Do not worry about @convert/expression.rules@.
> I have a... Greg Shah

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

Studied the task objective. Correct me if I'm wrong. I have scanned @convert/expression.rules@ and found the candidat... Eugenie Lyzenko

03/15/2017

09:58 AM Feature #3265: enhance pphints to have references, expansions and details in and about directives

The pphints mechanism was deliberately implemented to only contain information regarding code that exists in the full... Greg Shah

09:52 AM Feature #3265 (New): enhance pphints to have references, expansions and details in and about dire...

Greg Shah

09:50 AM Bug #3256 (Closed): comments disappear inside strings when the preprocessor evaluates expressions

3255a was merged to trunk as revision 11143. Greg Shah