V5R2 or above would make us more amenable to using the framework.
So the GNU GPLv3 license is pretty Grey looking.
Can you tell me the specifics of how we would need to comply and costs ?
We would certainly be willing to contribute source changes we may make
to the framework if we used it.
Regards,
Richard Schoen
RJS Software Systems Inc.
"Get the information you need. Now!"
Document Management, Workflow, Report Delivery, Forms and Business
Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site:
http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
-----Original Message-----
message: 1
date: Thu, 18 Mar 2010 15:36:58 +0100
from: hr@xxxxxxxxxxxx
subject: Re: [WEB400] Anybody have a good CGIDEV2 CRUD Samples program
?
At the moment it runs "V5R4M0 or later" but this is due to
3 RPGLE xml-into's that isn't supported on earlier releases.
These tre xml-into's is located in the two API's that builds menus
and grid/forms EXT JS configurations (in JSON).
I could rewrite these xml-into's because I just have added a
release independed XML reader to powerEXT Core and then bring
the Application Framework down to "V5R2M0 or later".
The CRUD modules (I call them RPC's) is SQLRPGLE programs
that are generated on the basis of an DSPFFD and will run
on "V5R2M0 or later".
The basic RPC's is a module that can read a HTTP GET/POST input and
either INITIALIZE, INSERT, UPDATE, DELETE a row or return a ROW
or a set of ROWS formatted in either HTML, XML or JSON.
Because all data (HTML/XML/JSON) is build by the nodesupport in
powerEXT Core, the data will always have the correct encoding of
special characters.
The RPC documentation can be found here:
http://powerEXT.com/pextdoc_RPC.htm
It will always process single records by RRN and if errors is
encounted it will return a error message in JSON format.
You can try an RPC here: (I have removed security (session and request))
http://212.242.251.247:1550/pextcgi/pxsvpxx9.pgm?func=getRows&output=xml
Generated without preparation it will handle the data format
according to the field type in the database.
But if fields are defined in the Central Metadata Model it will
also handle exceptions such as date and time fields defined as
numeric fields in the database and user/date/time for row create
and row update and row update counter checks etc.
The RPC's has nothing to do with the UI selected and thereby it
work on any chosen UI that runs AJAX requests.
Because you represent a software vendor you should be aware of
the GNU GPLv3 license.
powerEXT Application Framework is (like Ext JS) dual licensed,
so if you plan to used it as part of a payable standard system
either your customer needs a commercial license to powerEXT AF
and Ext JS or you will need an OEM license.
However, if you only want the RPC (CRUD) support you are able
to run powerEXT at your own site under the GNU GPLv3 license
and distribute the RPC's and powerEXT Core under the Core MIT
license. In that case the RPC would run "unprotected" or
protected under your own security.
Regards
Henrik
midrange.com
