Activity
From 03/31/2017 to 04/29/2017
04/27/2017
- 12:40 PM Bug #2356 (New): pphints bug - nested includes are missing from the.pphints file
- OK, that makes sense.
- 12:19 PM Bug #2356: pphints bug - nested includes are missing from the.pphints file
- Greg Shah wrote:
> I've looked deeper at this. Expansions that are inside of preprocessor directives are deliberate... - 10:59 AM Bug #2356 (Rejected): pphints bug - nested includes are missing from the.pphints file
- I've looked deeper at this. Expansions that are inside of preprocessor directives are deliberately excluded from the...
04/26/2017
- 02:18 PM Feature #3277: implement call-graph v3
- Greg Shah wrote:
> 1. The @CGW.CallGraph.addTarget()@ does not add to the @traversed@ list. Is that expected?
I th... - 02:05 PM Feature #3277: implement call-graph v3
- 1. The @CGW.CallGraph.addTarget()@ does not add to the @traversed@ list. Is that expected?
2. I don't understand ...
04/21/2017
- 04:02 PM Feature #3277: implement call-graph v3
- Greg Shah wrote:
> >> a list of the linkages that need to be reworked into the "normalized" graph (where all linkage... - 02:53 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Greg Shah wrote:
> No, I'll handle it.
OK. - 02:52 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- No, I'll handle it.
- 02:29 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Greg,
While I'm working on another task should I keep rebasing @1521c@ branch with the upcoming new trunk versions? - 03:03 AM Feature #1514: implement fully dynamic reports (backed by the database)
- Eric Faulhaber wrote:
> Hynek, I have a simple class which starts up a simple Jetty server with SSL, based on Greg's... - 10:55 PM Feature #1514: implement fully dynamic reports (backed by the database)
- Hynek Cihlar wrote:
> A few notes about the RPC. While I agree with Greg that the REST-like programming model isn't ...
04/20/2017
- 04:26 PM Feature #3277: implement call-graph v3
- >> a list of the linkages that need to be reworked into the "normalized" graph (where all linkage types are first cla...
- 04:09 PM Feature #3277: implement call-graph v3
- Interesting article on using the later Tinkerpop with the older OrientDB:
https://christinemdraper.wordpress.com/2... - 04:09 PM Feature #3277: implement call-graph v3
- Having a mechanism for Object to Graph Mapping (OGM) seems useful. Unfortunately, the existing solutions are relativ...
- 04:05 PM Feature #3277: implement call-graph v3
- Something that makes me concerned about OrientDB:
http://orientdbleaks.blogspot.com/2016/06/one-year-of-orientdb-l... - 01:27 PM Feature #3277: implement call-graph v3
- Greg Shah wrote:
> My sense is that OrientDB may be the better solution. There are two concerns:
>
> * It will t... - 12:27 PM Feature #3277: implement call-graph v3
- Greg, a good read is the documentation in callgraph/callgraph_lib.rules - it documents all the call sites which are i...
- 11:37 AM Feature #3277: implement call-graph v3
- Interesting D3 samples:
http://vowl.visualdataweb.org/webvowl/ (very close, code is at https://github.com/VisualDa... - 11:34 AM Feature #3277: implement call-graph v3
- One question I am considering is whether we should move to a newer graph database implementation. It seems like the ...
- 10:35 AM Feature #3277: implement call-graph v3
- Constantin: I am refreshing my understanding of the current implementation. As I dig into the code, it would be very...
- 10:32 AM Feature #3277: implement call-graph v3
- This work is intended to provide a web UI to display and explore a more complete version of the call graph.
+Objec...
04/19/2017
04/18/2017
- 06:26 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Rebased task branch @1521c@ from P2J trunk revision @11148@. New revision is @11152@.
- 12:53 PM Feature #1514: implement fully dynamic reports (backed by the database)
- Branch 1514a was rebased from trunk rev 11147.
04/17/2017
- 06:05 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Rebased task branch @1521c@ from P2J trunk revision @11147@. New revision is @11151@.
- 01:46 PM Feature #1521: implement gap analysis rules or backing database/marker approach
- Task branch @1521c@ for review updated to revision @11150@.
All changes for only @gaps/expressions.rule@. This upd...
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 ...
- 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...
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....
- 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
... - 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...
- 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... - 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, ... - 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... - 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...
- 12:24 PM Feature #1514 (WIP): implement fully dynamic reports (backed by the database)
- Created branch 1514a.
- 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 ...
- 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.
... - 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 ...
- 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.
...
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...
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 ... - 11:46 AM Feature #1521: implement gap analysis rules or backing database/marker approach
- You are mis-interpreting the parser.
This code:... - 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... - 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... - 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...
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... - 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@.
- 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... - 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...
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...
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...
- 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...
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...
Also available in: Atom