Activity
From 10/27/2017 to 11/25/2017
11/26/2017
- 08:09 PM Feature #3262: implement COM/OLE Automation support
- Task branch @3262b@ has been updated for review to revision @11231@.
Fix for regression caused by shifting from si...
11/25/2017
- 05:06 PM Feature #3262: implement COM/OLE Automation support
- Task branch @3262b@ has been rebased with trunk @11205@, new revision is @11230@.
11/24/2017
- 03:39 PM Feature #3262: implement COM/OLE Automation support
- Task branch @3262b@ has been rebased with trunk @11204@, new revision is @11229@.
- 02:20 PM Feature #3262: implement COM/OLE Automation support
- Task branch @3262b@ has been updated for review to revision @11226@, @11227@.
This update implements improved obje... - 06:45 AM Feature #3262: implement COM/OLE Automation support
- > Looks like we also need to change gap report processing rules to reflect the added implementation, this is one more...
- 10:45 PM Feature #3262: implement COM/OLE Automation support
- OK. Looks like the @4GL@ @COM@ garbage collector approach has been clarified. The internal object taken from given @C...
- 09:11 PM Feature #3262: implement COM/OLE Automation support
- Greg Shah wrote:
> > The COM objects has no actual parent-child relationships. The same object can be obtained for r... - 07:05 PM Feature #3262: implement COM/OLE Automation support
- Greg,
Looks like we also need to change gap report processing rules to reflect the added implementation, this is o...
11/23/2017
- 06:42 PM Feature #3262: implement COM/OLE Automation support
- Task branch @3262b@ has been updated for review to revision @11225@.
This update adds extent array support for pro... - 06:25 AM Feature #3262: implement COM/OLE Automation support
- > The COM objects has no actual parent-child relationships. The same object can be obtained for re-use from different...
- 09:42 PM Feature #3262: implement COM/OLE Automation support
- Task branch @3262b@ has been updated for review to revision @11224@.
This is minor cleanup update. I have designed...
11/22/2017
- 04:36 PM Feature #3262: implement COM/OLE Automation support
- Greg Shah wrote:
>Eugenie: Can you write the Java-side array changes that are needed? Constantin is busy with anothe... - 03:50 PM Feature #3262: implement COM/OLE Automation support
- Eugenie: Can you write the Java-side array changes that are needed? Constantin is busy with another task.
What el... - 02:17 PM Feature #3262: implement COM/OLE Automation support
- Task branch @3262b@ has been rebased with trunk @11202@, new revision is @11223@.
- 02:00 PM Feature #3262: implement COM/OLE Automation support
- Task branch @3262b@ has been updated for review to revision @11222@.
This is code partial cleanup and adding inter... - 08:05 AM Feature #3262: implement COM/OLE Automation support
- Greg Shah wrote:
> If I understand correctly, they are stating that the user is responsible for releasing all of the... - 06:05 AM Feature #3262: implement COM/OLE Automation support
- > The intermediate COM handles created with lines like comObject:prop1:prop2:(prop|method()) is not explicitly releas...
11/21/2017
- 06:33 PM Feature #3262: implement COM/OLE Automation support
- Task branch @3262b@ has been updated for review to revision @11221@.
This updates has changes to make chain calls ... - 06:07 PM Feature #3262: implement COM/OLE Automation support
- Constantin Asofiei wrote:
> Eugenie Lyzenko wrote:
> > Honestly I do not understand why we need attributes support ... - 05:37 PM Feature #3262: implement COM/OLE Automation support
- Eugenie Lyzenko wrote:
> Honestly I do not understand why we need attributes support for @COM-HANDLE@. @COM-HANDLE@ ... - 05:32 PM Feature #3262: implement COM/OLE Automation support
- I would suggest to change @com_access.rules@ to:...
- 04:56 PM Feature #3262: implement COM/OLE Automation support
- Constantin Asofiei wrote:
> Eugenie Lyzenko wrote:
> > The @NAME@ is a reserved keyword? What makes @NAME@ property... - 02:57 PM Feature #3262: implement COM/OLE Automation support
- Eugenie Lyzenko wrote:
> The @NAME@ is a reserved keyword? What makes @NAME@ property to process differently?
Is a ... - 02:55 PM Feature #3262: implement COM/OLE Automation support
- Constantin Asofiei wrote:
> Eugenie Lyzenko wrote:
> > 2. Consider the following @4GL@ code:
> > [...]
> >
> > ... - 02:13 PM Feature #3262: implement COM/OLE Automation support
- Eugenie Lyzenko wrote:
> This is correct conversion and we have property getter and method call. Both of them return... - 01:54 PM Feature #3262: implement COM/OLE Automation support
- Constantin Asofiei wrote:
> Eugenie Lyzenko wrote:
> > Guys,
> >
> > I have two notes at this time for Java side... - 01:20 PM Feature #3262: implement COM/OLE Automation support
- Eugenie Lyzenko wrote:
> Guys,
>
> I have two notes at this time for Java side with real @Excel@ application:
> ... - 01:16 PM Feature #3262: implement COM/OLE Automation support
- Guys,
I have two notes at this time for Java side with real @Excel@ application:
1. The @NativeComObject@ must ... - 09:56 PM Feature #3262: implement COM/OLE Automation support
- The testcases repo has been updated to revision @1700@.
The real @MS Office@ testcases have been added. The curren...
11/18/2017
- 06:20 PM Feature #3262: implement COM/OLE Automation support
- Constantin Asofiei wrote:
> Eugenie, see 11220 - it should work, I'm sending null value for empty parameters.
Yes... - 05:47 PM Feature #3262: implement COM/OLE Automation support
- Eugenie, see 11220 - it should work, I'm sending null value for empty parameters.
- 04:39 PM Feature #3262: implement COM/OLE Automation support
- Constantin Asofiei wrote:
> Yes, I missed this part - how do you want it to work? Just set that value to @null@, and... - 04:29 PM Feature #3262: implement COM/OLE Automation support
- Eugenie Lyzenko wrote:
> Constantin,
>
> The current Java side support for optional parameters is incomplete. The... - 12:01 PM Feature #3262: implement COM/OLE Automation support
- Constantin,
The current Java side support for optional parameters is incomplete. The using @comhandle.EMPTY(new Ob... - 06:44 AM Feature #3262: implement COM/OLE Automation support
- Task branch @3262b@ has been updated for review to revision @11219@.
The update adds native support for optional p... - 08:02 PM Feature #3262: implement COM/OLE Automation support
- The testcases repo has been updated to revision @1699@.
The read-only property test has been added. With respectiv...
11/17/2017
- 06:52 PM Feature #3262: implement COM/OLE Automation support
- The required change to support optional parameters for method call has been prepared for native code. The idea is bas...
- 12:24 AM Feature #3262: implement COM/OLE Automation support
- Rebased with recent trunk, new revision is @11217@.
Some implementation details. Property set for indexed case is ... - 12:04 AM Feature #3262: implement COM/OLE Automation support
- Task branch @3262b@ has been updated for review to revision @11216@.
This adds support for indexed properties hand...
11/16/2017
- 12:21 PM Feature #3262: implement COM/OLE Automation support
- Constantin Asofiei wrote:
>
> Eugenie: looks like 4GL allows a construct like @comVar:comProperty(1,2,3) = someVal... - 11:07 AM Feature #3262: implement COM/OLE Automation support
- The parse, conversion and Java ComOleHelper API changes are in 3262b rev 11215.
Eugenie: looks like 4GL allows a c... - 09:21 PM Feature #3262: implement COM/OLE Automation support
- > What I suggest is to separate at least the indexed property usage in fwdAppl:int1DIndexedProperty(3) = intVar1. fro...
- 09:16 PM Feature #3262: implement COM/OLE Automation support
- > ComParamter.EMPTY
I like this. - 09:09 PM Feature #3262: implement COM/OLE Automation support
- The testcases repo has been updated to revision @1698@.
Added testcases to verify indexed property feature and obj... - 07:34 PM Feature #3262: implement COM/OLE Automation support
- Constantin Asofiei wrote:
> Eugenie, for the third case in your example: that one needs to be disambiguated by the F...
11/15/2017
- 06:07 PM Feature #3262: implement COM/OLE Automation support
- Constantin Asofiei wrote:
>...
> I think we can check this if COM_METHOD is first child of a KW_ASSIGN. How is the... - 05:22 PM Feature #3262: implement COM/OLE Automation support
- Eugenie, for the third case in your example: that one needs to be disambiguated by the FWD native side - i.e. check i...
- 05:21 PM Feature #3262: implement COM/OLE Automation support
- > I'm debugging the @4GL@ @COM@ automation indexed properties. There are a some issues while converting this feature....
- 05:14 PM Feature #3262: implement COM/OLE Automation support
- Guys,
I'm debugging the @4GL@ @COM@ automation indexed properties. There are a some issues while converting this f... - 04:58 PM Feature #3262: implement COM/OLE Automation support
- Greg Shah wrote:
> > I think we need to change method call processing on conversion level to have converted code lik... - 09:10 AM Feature #3262: implement COM/OLE Automation support
- > I think we need to change method call processing on conversion level to have converted code like this:
>
>> call(... - 08:14 PM Feature #3262: implement COM/OLE Automation support
- The testcases repo has been updated to revision @1697@.
Added testcases to verify @CREATE ...@, @CREATE ... CONNEC... - 07:44 PM Feature #3262: implement COM/OLE Automation support
- The investigation and debugging results for today.
1. The large application has object creation modes: @CREATE "Co...
11/14/2017
- 07:30 PM Feature #3262: implement COM/OLE Automation support
- The testcases repo has been updated to revision @1696@.
Added tests to verify optional parameter mode for method c... - 07:18 PM Feature #3262: implement COM/OLE Automation support
- Task branch @3262b@ has been updated for review to revision @11212@. Rebased with recent trunk, new revision is @1121...
11/13/2017
- 06:37 PM Feature #3262: implement COM/OLE Automation support
- Other findings for today:
1. The option @BY-VARIANT-POINTER@ is never used in our large @4GL@ code.
2. The option... - 06:16 PM Feature #3262: implement COM/OLE Automation support
- Constantin, Greg,
I'm debugging different data input modes for COM object method call and found one issue to discu...
11/12/2017
- 11:10 AM Feature #3262: implement COM/OLE Automation support
- Task branch @3262b@ has been rebased with trunk @11199@, new revision is @11211@.
11/11/2017
- 08:03 PM Feature #3262: implement COM/OLE Automation support
- Task branch @3262b@ has been updated for review to revision @11210@.
The update adds support for @OUTPUT@ and @INP...
11/10/2017
- 06:00 PM Feature #3262: implement COM/OLE Automation support
- Constantin Asofiei wrote:
> Eugenie Lyzenko wrote:
> > Constantin,
> >
> > Some consideration about usage @BY-PO... - 05:39 PM Feature #3262: implement COM/OLE Automation support
- > BTW, if BY-POINTER is used for INPUT, I assume the variable on that argument will be changed?
Actually, I think... - 05:27 PM Feature #3262: implement COM/OLE Automation support
- Eugenie Lyzenko wrote:
> Constantin,
>
> Some consideration about usage @BY-POINTER@ and @INPUT-OUTPUT@ or @OUTPU... - 05:07 PM Feature #3262: implement COM/OLE Automation support
- Constantin,
Some consideration about usage @BY-POINTER@ and @INPUT-OUTPUT@ or @OUTPUT@ data modifiers. The usage @... - 09:11 PM Feature #3262: implement COM/OLE Automation support
- The testcases repo has been updated to revision @1693@, @1694@.
This adds testcase to check different modes includ... - 02:17 PM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- Stanislav:
Please write up the documentation for this feature. It should be placed in:
[[p2j:JasperReports Int...
11/09/2017
- 06:35 PM Feature #3262: implement COM/OLE Automation support
- Task branch @3262b@ has been rebased with trunk @11198@, new revision is @11209@.
- 06:14 PM Feature #3262: implement COM/OLE Automation support
- Task branch @3262b@ has been updated for review to revision @11208@.
Small improvement to unify the common code in... - 10:42 AM Feature #3262: implement COM/OLE Automation support
- Constantin Asofiei wrote:
> Eugenie, can you check if 4GL allows something like this, @i = i + comVar:extentProp[1]@... - 07:46 AM Feature #3262: implement COM/OLE Automation support
- Eugenie, can you check if 4GL allows something like this, @i = i + comVar:extentProp[1]@ ? Currently FWD can't conve...
- 07:06 AM Feature #3342 (Closed): implement a facility to easily run a JasperReports report definition from...
- 06:50 AM Feature #3342 (Review): implement a facility to easily run a JasperReports report definition from...
- 06:49 AM Feature #3342 (WIP): implement a facility to easily run a JasperReports report definition from 4G...
- 3342с has been merged into the trunk as bzr revision 11198.
- 06:25 AM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- Code Review Task Branch 3342c Revision 11200
I'm good with the code.
Please merge to trunk. - 06:15 AM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- Please take a look at 3342c rev 11200 and I'll merge to trunk.
11/08/2017
- 06:59 PM Feature #3262: implement COM/OLE Automation support
- Task branch @3262b@ has been rebased with trunk @11197@, new revision is @11207@.
- 06:43 PM Feature #3262: implement COM/OLE Automation support
- Task branch @3262b@ has been updated for review to revision @11206@.
This is the COM method return value fix to re... - 01:39 PM Feature #3262: implement COM/OLE Automation support
- The bzr repo updated to revision @1691@.
This adds the testcase to check the method accepting 3 input parameters a... - 12:06 PM Feature #3262: implement COM/OLE Automation support
- Task branch @3262b@ has been updated for review to revision @11205@.
Finished adding @COM->Java@ transformation fo... - 06:38 PM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- Code Review Task Branch 3342c Revision 11199
I really like it.
The only request: the @getFileFromClient()@ sh... - 05:32 PM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- Rebased task branch 3342c from P2J trunk revision 11197. Please review.
11/07/2017
- 06:14 PM Feature #3262: implement COM/OLE Automation support
- Task branch @3262b@ has been updated for review to revision @11204@.
This is extent support adding for native modu... - 02:11 PM Feature #3262: implement COM/OLE Automation support
- Greg Shah wrote:
> The idea is to hide the logic in some code that is specific to COM Automation. I don't want to p... - 12:17 PM Feature #3262: implement COM/OLE Automation support
- Constantin Asofiei wrote:
> Eugenie Lyzenko wrote:
> > This is small update:
> >
> > The single not array return... - 12:12 PM Feature #3262: implement COM/OLE Automation support
- Can we hide this inside the runtime? For example, instead of this:...
- 11:50 AM Feature #3262: implement COM/OLE Automation support
- Eugenie Lyzenko wrote:
> This is small update:
>
> The single not array return value will be just a @1@ item size... - 11:36 AM Feature #3262: implement COM/OLE Automation support
- This is small update:
The single not array return value will be just a @1@ item size array case.
- 11:34 AM Feature #3262: implement COM/OLE Automation support
- Constantin,
I'm implementing native support for extent based array. And looks like I need you to make some changes... - 09:35 PM Feature #3262: implement COM/OLE Automation support
- Greg Shah wrote:
> I appreciate the idea. But since COM Automation is platform specific and hard coded to Windows, ...
11/06/2017
- 06:50 PM Feature #3262: implement COM/OLE Automation support
- I appreciate the idea. But since COM Automation is platform specific and hard coded to Windows, it is not a feature ...
- 06:29 PM Feature #3262: implement COM/OLE Automation support
- Greg Shah wrote:
> > Greg, what do you think? Do we need this feature to be tried to implement in our FWD native COM... - 06:25 PM Feature #3262: implement COM/OLE Automation support
- > Greg, what do you think? Do we need this feature to be tried to implement in our FWD native COM automation support?...
- 06:11 PM Feature #3262: implement COM/OLE Automation support
- Some additional consideration for @MEMPTR@. Technically I think we can implement support for this data type in our @F...
- 04:08 PM Feature #3262: implement COM/OLE Automation support
- Task branch @3262b@ has been rebased with trunk @11196@, new revision is @11203@.
- 03:51 PM Feature #3262: implement COM/OLE Automation support
- Task branch @3262b@ has been updated for review to revision @11202@.
The update has full support for @RAW@ data ty... - 03:07 PM Feature #3262: implement COM/OLE Automation support
- The bzr repo updated to revision @1688@.
Added the @RAW@ and @MEMPTR@ data type tests. Conclusion - the @4GL@ does... - 01:50 PM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- I suppose that @MultiClassLoader@ can get resource from any jar (see @MultiClassLoader.findResource@). Is there any d...
11/04/2017
- 10:09 AM Feature #3262: implement COM/OLE Automation support
- > but Java doesn't compile as "y is not effectively final". I can promote this to instance field... but although this...
- 09:20 PM Feature #3262: implement COM/OLE Automation support
- Constantin,
Please update class source files header for your @comauto@ modifications revision @11200@.
Greg, Co... - 08:10 PM Feature #3262: implement COM/OLE Automation support
- Task branch @3262b@ has been rebased with trunk @11195@, new revision is @11201@.
11/03/2017
- 07:56 PM Feature #3262: implement COM/OLE Automation support
- Task branch @3262b@ has been updated for review to revision @11199@.
This is the fixes for @date/datetime/datetime... - 06:11 PM Feature #3262: implement COM/OLE Automation support
- Constantin Asofiei wrote:
> Eugenie, 3262b rev 11198 contains the first pass at extent support from Java side.
Ar... - 05:47 PM Feature #3262: implement COM/OLE Automation support
- Eugenie, 3262b rev 11198 contains the first pass at extent support from Java side. Some other questions:
* can a CO... - 05:38 PM Feature #3262: implement COM/OLE Automation support
- Greg, I need an advice. 4GL allows a construct like this at parse time:...
- 01:14 PM Feature #3262: implement COM/OLE Automation support
- Eugenie Lyzenko wrote:
> Constantin Asofiei wrote:
> >Where it gets complicated is the OUTPUT/INPUT-OUTPUT paramete... - 12:03 AM Feature #3262: implement COM/OLE Automation support
- More checks shows the additional issue with @date/datetime/datetime-tz@ data type support. We loose precision passing...
- 11:57 PM Feature #3262: implement COM/OLE Automation support
- Constantin Asofiei wrote:
>Where it gets complicated is the OUTPUT/INPUT-OUTPUT parameters: ComOleHelper.call needs ... - 10:04 PM Feature #3262: implement COM/OLE Automation support
- Eugenie Lyzenko wrote:
> Constantin,
>
> As you know we need to add support for arrays produced from 4GL extent o... - 08:57 PM Feature #3262: implement COM/OLE Automation support
- Constantin,
As you know we need to add support for arrays produced from 4GL extent option. My plan is following:
... - 11:03 AM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- You can also look at @LogicalTerminal.setImage()@ to see how it is a 2 level search.
- 10:56 AM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- Stanislav Lomany wrote:
> > Eugenie wrote image loading code that first checks the application's jar and then search... - 09:35 AM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- > Eugenie wrote image loading code that first checks the application's jar and then searches the propath on the clien...
11/02/2017
- 04:37 PM Feature #3262: implement COM/OLE Automation support
- 3262b rev 11197 contains the changes to make the @comhandle@ id unique for FWD's COM object representation and not re...
- 02:52 PM Feature #3262: implement COM/OLE Automation support
- The cleanup for @comhandle@ has been uploaded as rev @11196@.
- 02:29 PM Feature #3262: implement COM/OLE Automation support
- Constantin Asofiei wrote:
> Eugenie Lyzenko wrote:
> > Constantin Asofiei wrote:
> > > Eugenie, I've looked at 326... - 02:03 PM Feature #3262: implement COM/OLE Automation support
- Eugenie Lyzenko wrote:
> Incorrect screen, both numbers are different but must be the same and both numbers are too ... - 01:54 PM Feature #3262: implement COM/OLE Automation support
- Constantin Asofiei wrote:
>Can the com-handle variable be used with HANDLE function?
No, incompatible data type.
... - 12:58 PM Feature #3262: implement COM/OLE Automation support
- Eugenie Lyzenko wrote:
> Constantin Asofiei wrote:
> > Eugenie, I've looked at 3262b rev 11195 and I have these com... - 12:56 PM Feature #3262: implement COM/OLE Automation support
- Eugenie Lyzenko wrote:
> Constantin Asofiei wrote:
> > Eugenie, I've looked at 3262b rev 11195 and I have these com... - 12:46 PM Feature #3262: implement COM/OLE Automation support
- Constantin Asofiei wrote:
> Eugenie, I've looked at 3262b rev 11195 and I have these comments for the Java changes:
... - 12:39 PM Feature #3262: implement COM/OLE Automation support
- Constantin Asofiei wrote:
> Eugenie, I've looked at 3262b rev 11195 and I have these comments for the Java changes:
... - 11:25 AM Feature #3262: implement COM/OLE Automation support
- Eugenie, I've looked at 3262b rev 11195 and I have these comments for the Java changes:
* @NativeComObject@ - the @i... - 09:56 PM Feature #3262: implement COM/OLE Automation support
- Task branch @3262b@ has been updated for review to revision @11195@.
This is the fix for @COM-HANDLE@ attribute ge... - 04:27 PM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- > The generated report doesn't necessarily has to keep the name on different executions (an example are reports ran f...
- 04:11 PM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- > If I understand correctly, the use of @jasperContext.setFileResolver(fileName -> new File(ReportFactory.getFilePath...
- 04:05 PM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- If I understand correctly, the use of @jasperContext.setFileResolver(fileName -> new File(ReportFactory.getFilePath(f...
- 04:02 PM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- Stanislav Lomany wrote:
> > In this case, compiling the .jrxml will be done 'on-the-fly', don't know how easy is to ... - 04:00 PM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- Stanislav Lomany wrote:
> > Something else: someone can design a report which refers to a client-side resource (i.e.... - 03:51 PM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- > In this case, compiling the .jrxml will be done 'on-the-fly', don't know how easy is to cache it (especially build ...
- 03:46 PM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- > Something else: someone can design a report which refers to a client-side resource (i.e. an image local to the clie...
- 03:08 PM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- And also add the @reporting.Report@ interface to the @HandleCommon@ interface; any extension resource in FWD must be ...
- 03:07 PM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- Stanislav Lomany wrote:
> > Or do you want the 4GL business logic to design the report from scratch, too, and compil... - 03:01 PM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- > Isn't compiling the @jasper@ file done only once, after the design is complete?
Right. If we are going to put ... - 02:27 PM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- Stanislav Lomany wrote:
> Compiling reports is a big performance hit.
Isn't compiling the @jasper@ file done only o... - 02:20 PM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- > If you feel that the client-side support doesn't provide the same capability, then it is OK to do a 3 level process...
- 01:43 PM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- > Yes, but I have to note that having files outside of jar is very convenient at report development stage.
If you ... - 01:40 PM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- > we can search in the server's jars first and, if not found, search it on the client-side
OK, I'll go this way. S... - 01:27 PM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- Stanislav Lomany wrote:
> > From (unmodified) converted code there is no way to write or read from the server filesy... - 01:21 PM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- > From (unmodified) converted code there is no way to write or read from the server filesystem. That means that the ...
- 12:49 PM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- > Do you want me to remove capability to read non-in-jar files or limit access to the reports directory only?
From... - 12:26 PM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- > 1. We do expect that application-specific resources would come from the application's jar file. This would be on t...
- 09:54 AM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- > But unfortunately the current directory is the P2J server directory.
Sorry, I completely missed the part about f... - 08:29 AM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- > One question: why not default the reports directory to "." instead of "reports"?
On my taste the best place for ... - 06:11 AM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- Code Review Task Branch 3342c Revision 11194
I'm fine with the changes.
One question: why not default the repor... - 09:35 PM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- Rebased task branch 3342c from P2J trunk revision 11193. Please review. Contains final fixes for Jasper. Images were ...
- 05:58 AM Feature #3343 (Closed): implement a 4GL syntax extension and the runtime backing to send emails (...
- The documentation for this functionality can be found in "Email Send":https://proj.goldencode.com/projects/p2j/wiki/E...
11/01/2017
- 02:30 PM Feature #3292 (Closed): i18n improvements
- The runtime implementation for this task was written in branch 1830b and was merged to trunk as revision 11188.
BI... - 10:19 PM Feature #3262: implement COM/OLE Automation support
- Greg Shah wrote:
> > I'm not 100% sure however having deep suggestion the Java has one bug in Windows package. The l... - 10:07 PM Feature #3262: implement COM/OLE Automation support
- Task branch @3262b@ has been updated for review to revision @11194@.
This fixes the @DATE@ conversion issue for @J...
10/31/2017
- 11:32 AM Feature #3262: implement COM/OLE Automation support
- Created task branch @3262b@ from trunk revision @11193@.
- 11:18 AM Feature #3262: implement COM/OLE Automation support
- > I'm not 100% sure however having deep suggestion the Java has one bug in Windows package. The long value can not be...
- 12:09 AM Feature #3262: implement COM/OLE Automation support
- Now I would like to note about some limitations and known issues:
1. As we discussed - no events firing support fr... - 11:32 PM Feature #3262: implement COM/OLE Automation support
- Branch @3262a@ was merged to trunk as revno @11190@ then it was archived.
Sorry it has taken more time I have expe... - 11:24 PM Feature #3262: implement COM/OLE Automation support
- Task branch @3262a@ has been rebased with trunk @11189@, new revision is @11209@.
Starting merge into trunk. - 10:56 PM Feature #3262: implement COM/OLE Automation support
- Task branch @3262a@ has been updated for review to revision @11205@.
This is bug fixing and cleanup for COM automa... - 09:51 PM Feature #3262: implement COM/OLE Automation support
- Good plan.
- 09:48 PM Feature #3262: implement COM/OLE Automation support
- Testing completed. No regressions have found. The results: @3262a_11204_a5eeab0_20171030_evl.zip@.
So planning to ... - 09:26 AM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- Created task branch 3342c from P2J trunk revision 11192.
- 09:21 AM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- 3342b has been merged into the trunk as bzr revision 11192.
- 09:13 AM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- Code Review Task Branch 3342b Revision 11192
I'm fine with the change. Please merge 3342b to trunk. - 09:07 AM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- Rebased task branch 3342b from P2J trunk revision 11191.
- 08:07 AM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- Created task branch 3342b from P2J trunk revision 11190.
- 09:38 PM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- 3342a has been merged into the trunk as bzr revision 11189.
- 09:24 PM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- I saw the same thing in my run. I don't think it will make a difference. I think you are OK.
- 09:23 PM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- There seems to be conversion mismatch: order of widgets changed in frame definition:...
- 09:40 PM Feature #3343: implement a 4GL syntax extension and the runtime backing to send emails (including...
- Conversion and manual testing has passed.
Task branch 3353a was merged to trunk as revision 11187. Branch 3353a h...
10/30/2017
- 07:27 PM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- Code Review Task Branch 3342a Revision 11195
The changes overall are really good. Some of the conversion changes ... - 06:48 PM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- Rebased task branch 3342a from P2J trunk revision 11188.
- 06:41 PM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- Rebased task branch 3342a from P2J trunk revision 11187.
- 06:06 PM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- Rebased task branch 3342a from P2J trunk revision 11186.
- 11:31 AM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- Use @com.goldencode.p2j.reporting@. The overlap is confusing but we will deal with it for now.
- 09:57 AM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- Into which package should I put all classes related to (Jasper) reports? We have @com.goldencode.p2j.report@, but it ...
- 11:06 PM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- > we have <customer_package_redacted>.BufferedOutputStreamWrapper class. Can I copy-paste it under com.goldencode pac...
- 05:38 PM Feature #3262: implement COM/OLE Automation support
- > Is it acceptable plan?
Yes. - 05:18 PM Feature #3262: implement COM/OLE Automation support
- The status of the @3262a@ branch:
1. The first main cycle of the testing completed. The results are prettu good. B... - 01:09 PM Feature #3262: implement COM/OLE Automation support
- Eugenie Lyzenko wrote:
> Constantin, have you made commit for @3262a@?:
> [...]
>
> So I will have to re-run con... - 01:09 PM Feature #3262: implement COM/OLE Automation support
- Constantin Asofiei wrote:
> Eugenie, please fix these as you find them.
Task branch @3262a@ has been updated for ... - 11:31 AM Feature #3262: implement COM/OLE Automation support
- Eugenie Lyzenko wrote:
> Another issue in Java code:
> @ComObject.unmarshal()@ produces @NPE@ for empty input param... - 11:29 AM Feature #3262: implement COM/OLE Automation support
- Another issue in Java code:
@ComObject.unmarshal()@ produces @NPE@ for empty input parameters for method call. like ... - 10:45 AM Feature #3262: implement COM/OLE Automation support
- Greg Shah wrote:
>
> Yes, the @progress.g@ and @com_access.rules@ changes are enough to require it.
The convers... - 10:43 AM Feature #3262: implement COM/OLE Automation support
- Constantin Asofiei wrote:
> Eugenie Lyzenko wrote:
> > If you see another opportunity - let me know. I think it can... - 10:39 AM Feature #3262: implement COM/OLE Automation support
- Eugenie Lyzenko wrote:
> If you see another opportunity - let me know. I think it can not be implemented today due t... - 10:36 AM Feature #3262: implement COM/OLE Automation support
- Constantin Asofiei wrote:
> Eugenie, another question: is @enable-events@ an API which can be used by COM OLE automa... - 10:15 AM Feature #3262: implement COM/OLE Automation support
- Eugenie, another question: is @enable-events@ an API which can be used by COM OLE automation regardless of 4GL enviro...
- 09:54 AM Feature #3262: implement COM/OLE Automation support
- The HWND is not a widget handle. It is the actual WIN32 HWND that matches the OpenEdge window-widget's WIN32 native w...
- 09:52 AM Feature #3262: implement COM/OLE Automation support
- Greg Shah wrote:
> > two usages of a HWND attribute passed as method argument, like in comVar:comMethod(CURRENT-WIND... - 09:50 AM Feature #3262: implement COM/OLE Automation support
- > two usages of a HWND attribute passed as method argument, like in comVar:comMethod(CURRENT-WINDOW:HWND).
These m... - 09:44 AM Feature #3262: implement COM/OLE Automation support
- I've been looking through how COM are used and I found these:
# one usage of @com:enable-events@ - so we need event ... - 07:17 AM Feature #3262: implement COM/OLE Automation support
- Task branch @3262a@ has been rebased with trunk @11185@, new revision is @11202@.
The testings restarted. - 06:59 AM Feature #3262: implement COM/OLE Automation support
- Greg Shah wrote:
> > Do we need the conversion tests to run?
>
> Yes, the @progress.g@ and @com_access.rules@ cha... - 10:57 PM Feature #3262: implement COM/OLE Automation support
- > Do we need the conversion tests to run?
Yes, the @progress.g@ and @com_access.rules@ changes are enough to requi... - 09:46 PM Feature #3262: implement COM/OLE Automation support
- Task branch @3262a@ has been updated for review to revision @11201@.
Bug fixing in native code and @ComParameter@ ... - 09:15 PM Feature #3262: implement COM/OLE Automation support
- Greg Shah wrote:
>
> Yes, this makes sense. Please go ahead.
OK. I'm planning to make the branch update soon(i... - 09:11 PM Feature #3262: implement COM/OLE Automation support
- > So my offering is to start regression testing now. Meantime I will finalize Windows specific changes(we can commit ...
- 04:53 PM Feature #3343: implement a 4GL syntax extension and the runtime backing to send emails (including...
- Branch 3353a rebased to trunk revision 11186. 11209 is now the latest revision.
This version is going through con... - 04:51 PM Feature #3343: implement a 4GL syntax extension and the runtime backing to send emails (including...
- Revision 11201 has a complete implemention that has been tested and cleaned up. It supports HTML and TEXT, attachmen...
10/29/2017
- 04:05 PM Feature #3262: implement COM/OLE Automation support
- Constantin,
I have the changes for @ComParameter@ class, two method to write/read the class over network:... - 09:19 AM Feature #3262: implement COM/OLE Automation support
- Looks like the Java part is OK (creation, property get/set and method call converted correctly). While the window nat...
- 02:54 PM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- Quick question: we have @<customer_package_redacted>.BufferedOutputStreamWrapper@ class. Can I copy-paste it under @c...
10/28/2017
- 04:37 PM Feature #3262: implement COM/OLE Automation support
- Task branch @3262a@ has been rebased with trunk @11184@, new revision is @11200@.
- 04:19 PM Feature #3262: implement COM/OLE Automation support
- Going to rebase @3262a@ in a 5 min of nobody objects.
- 10:45 AM Feature #3262: implement COM/OLE Automation support
- Eugenie Lyzenko wrote:
> Correct me if I'm wrong but for now the COM event processing is not supported in @FWD@.
CO... - 09:38 PM Feature #3262: implement COM/OLE Automation support
- Task branch @3262a@ has been rebased with trunk @11183@, new revision is @11199@.
So the currently requested @JNI@... - 09:14 PM Feature #3262: implement COM/OLE Automation support
- Task branch @3262a@ has been updated for review to revision @11198@.
Added usage of @DataType@ helper option suppo... - 07:15 AM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- Created task branch 3342a from P2J trunk revision 11183.
10/27/2017
- 06:38 PM Feature #3262: implement COM/OLE Automation support
- Of course @DataType@ is @enum@, not @union@.
- 05:54 PM Feature #3262: implement COM/OLE Automation support
- Task branch @3262a@ has been updated for review to revision @11197@.
Added handling for @DATE@ variables exchange ... - 05:28 PM Feature #3262: implement COM/OLE Automation support
- I have next drop to commit for @3262a@. Planning to do this in a 5 min if nobody objects.
- 12:41 PM Feature #3262: implement COM/OLE Automation support
- Task branch @3262a@ has been updated for review to revision @11196@.
Changed @COM-HANDLE@ @ID@ processing to excha... - 12:25 PM Feature #3262: implement COM/OLE Automation support
- Constantin Asofiei wrote:
> Eugenie Lyzenko wrote:
> > Constantin,
> >
> > Please help me to understand the @COM... - 11:11 AM Feature #3262: implement COM/OLE Automation support
- Eugenie Lyzenko wrote:
> Constantin,
>
> Please help me to understand the @COM-HANDLE@ @FWD@ internals related to... - 11:00 AM Feature #3262: implement COM/OLE Automation support
- Constantin,
Please help me to understand the @COM-HANDLE@ @FWD@ internals related to long @comID@ we use to identi... - 12:32 AM Feature #3262: implement COM/OLE Automation support
- Task branch @3262a@ has been updated for review to revision @11195@.
Added the @Java<->COM@ data transformations f... - 04:09 PM Feature #3292: i18n improvements
- I have chosen the @EnvironmentOps.isUnderWindowsFamily()@ instead of @TC.isUnderWindows()@. The returned value can be...
- 08:41 AM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- OK, go with this plan.
- 08:38 AM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- > The idea here is that there would be 4GL code to calculate the value of a column, possibly with access to state (va...
- 07:33 AM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- Can you show an example of embedding an image in the report?
- 07:32 AM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- >> 2. It seems to me that some reports might take more than one query to provide the needed details. Is that possible...
- 07:24 AM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- > 1. Do I understand correctly that the runtime will figure out the mapping between the columns returned by the query...
- 06:10 AM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- Overall, I like the approach. It is different from the callback approach we took previously. Some questions:
1. ... - 05:59 AM Feature #3342: implement a facility to easily run a JasperReports report definition from 4GL code...
- My suggestion on how 4GL code for a jasper report should look like:...
Also available in: Atom