Hi Mihael,
when using ExtJS there is basically 5 ways the client request data from
the server:
1. Accordions, where you have to use algorithms like JOE CELCO's tree
traversal
algorithm to make the JSON object out of the relational DB2 database
2. Grids - where you have selection and sorting criterias that should go
into the
black box and select the data on the passed criterias.
3. Remote Comboboxes, where you dynamically requests partial data based on
typing
and maybe even based on values of other selections in the form such as
select
country and then select city based on your selection of country.
4. Included Comboboxes, where you based on DB2 table values includes JSON
snippets
within the initial load of the EXT JS page.
5. Misc. client server communication and messaging such as "check this
customer
and if ok, return his name else return an errormessage".
Many times the flat file convertion isn't adequate, you may have to mix
several
tables or you may have to serve data that is generated by the systems
common
routines such as a items price for a particular customer or you may have
to check
if a particular menu option may be presented to the user.
What I have done in "my project" is that I have made program generators,
special
methods (subprocedures) and JSON node support that in combination adresses
all
5 areas.
While 1,2,3 and 5 is just plain GET/POST input and JSON output, 4 is where
you
have to implement a memory model where you can mix ExtJS code with
generated
JSON "snippets" like this where the "data" array is inserted dynamically
while
generating the field that is part of a dynamically form:
// extTemplate: /powerEXT/DMO/combo.asp Tag: combo_ExtJS3_mandatory
{fieldLabel:"Language Code"
,name:"WALNGCcombo"
,width:250
,maxHeight:300
,xtype:"combo"
,tpl:'<tpl for="."><div class="x-combo-list-item"
style="font-size:11px;">{select}</div></tpl>'
,resizable:true
,store:new Ext.data.SimpleStore({
fields:["WALNGC","select"]
,data:[
["da","da - Danish"]
,["de","de - German"]
,["en","en - English (US)"]
,["en_GB","en_GB - English (UK)"]
,["es","es - Spanish"]
,["fr","fr - French"]
,["it","it - Italian"]
,["nl","nl - Dutch"]
,["pt","pt - Portugese"]
]
})
,mode:"local"
,editable:true
,forceSelection:true
,hiddenName:"WALNGC"
,valueField:"WALNGC"
,displayField:"select"
,triggerAction:"all"
,allowBlank:false
,qtip:""
}
And this is where I combine CGIDEV2 abilities with my projects JSON node
support.
Regards
Henrik
"Schmidt, Mihael" <Mihael.Schmidt@xxxxxxxxxxx>
Sent by: web400-bounces@xxxxxxxxxxxx
20-07-2010 16:37
Please respond to
Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx>
To
Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx>
cc
Subject
Re: [WEB400] Convert DS/Record to JSON
One possibility I see is that I extend the RPG Next Gen Editor to create
an RFML file from a data structure and then that RFML file could be used
to convert from the data structure to a json object and back.
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On
Behalf Of hr@xxxxxxxxxxxx
Sent: Tuesday, July 20, 2010 4:12 PM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] Convert DS/Record to JSON
Hi Aaron,
what you are seeking cannot be done for several reasons:
1. take the tree most used field types: alpha, numeric and date fields. Do
you
know how many formats in a database dates can be stored in ? Yes, you
can make
a raw transfer, but then you just move the conversion problem to the
browser.
2. JSON is just a "packing" of data in a hierarchical datastructure, any
common
routine that packs the data without instructions and roules will be
useless,
it will be like making a mecanical conversion of an order database and
think it
will end up as a readable EDIfact ORDERS document - data has to be
converted
between server and client according to specifications both in datatypes
and
structure.
3. Yes, you can make a special black box that converts a DB2 file to a
JSON
EXT JS JSON datastore, but can you use this blackbox anywhere else -
NO.
In regards to powerEXT license powerEXT has now been devided into to
seperate
products/projects:
powerEXT Core - is as it says - the core, any similar code in AFW is
removed
and the Core is MIT licensed, but it also has, and depends on, a special
implementation of CGIDEV2 that has its own copyright according to IBM
rules.
powerEXT Application Framework - is build on top of Core and is still dual
licensed,
and has also EXT JS and a number of specially licensed UX's (User
eXtension) in it,
some GPL, some LGPL and some shareware licensed.
This license is a ballance, the GPL license ensures that any iSeries
customer can
download and use powerEXT without violating any's copyright, the
commercial license
ensures that any ISV that thinks this project could be a free ride to a
commercial
propritary product must rethink.
The basic rules are simple, as long as you develop (noncommercial)
software the
applies to GPL it is free, but if you make a application you sell, it's
not.
In my own company I have several standard applications my customers have
purchased
AND all pay's yearly fees to get their systems supported and further
developed. When
I move them over on powerEXT I have to give them a commercial license -
that is
I have to pay ExtJS and others for their software that I have included in
powerEXT
because I now earn money on directly on their work/license, otherwise I
have to
give up major revenues. I consider that as fair because they did not chose
to
become part of my project, I did.
I also have a customer/company that is using powerEXT as the framework to
their
payroll system that runs as a cloud application. They has to pay IBM,
System & Method
and other license in order to make that service available, I would be a
fool not
to have some piece of the action.
And if you consider my references to powerEXT as commercials, you should
take a
look at your own homepage where the commercial reference to the RPG-XML
SUITE is
all over the pages ;-)
Regards
Henrik
Aaron Bartell <aaronbartell@xxxxxxxxx>
Sent by: web400-bounces@xxxxxxxxxxxx
16-07-2010 20:58
Please respond to
Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx>
To
"Web Enabling the AS400 / iSeries" <web400@xxxxxxxxxxxx>
cc
Subject
Re: [WEB400] Convert DS/Record to JSON
Hi Henrik,
I have an older version of library PEXTCD2 on my machine and am wondering
if
you can point me to the MIT licensed code that does the conversion
discussed
earlier in this thread? I only see PEXTCD2/QSRC,PXAPXCGI.RPGLE. Or is
that
code part of the GPL v3 powerEXT?
Also, where do I go to read about the powerEXT dual license? I know I saw
it before in the back of a user manual, but I am not seeing it now.
Aaron Bartell
http://mowyourlawn.com
http://mowyourlawn.com/blog/
On Fri, Jul 16, 2010 at 1:21 PM, <hr@xxxxxxxxxxxx> wrote:
Aaron
powerEXY Core is MIT licensed - feel free to do anything what you want
to
do with it - can you use
any of it or any idears build in it - I would only appreciate it ;-)
However, I have some experience in working with programmers that are
"not
gifted childs"
(IQ <130 in WISC-III) and if you create very sofisticated blackboxes
they
will never understand.
.
Med venlig hilsen/Kind regards
Henrik Rützou
HR Software Development
Ved Stampedammen 39
DK 2970 Hørsholm
Denmark
E-mail: hr@xxxxxxxxxxxx
Phone: +45 2714 8449
Homepage: powerEXT.com
Aaron Bartell <aaronbartell@xxxxxxxxx>
Sent by: web400-bounces@xxxxxxxxxxxx
16-07-2010 19:49
Please respond to
Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx>
To
"Web Enabling the AS400 / iSeries" <web400@xxxxxxxxxxxx>
cc
Subject
Re: [WEB400] Convert DS/Record to JSON
How does the open source for powerEXT work? Am I allowed to use
snippets
of
code from powerEXT in a LGPL application like RPGUI? And if I do use
snippets from powerEXT does that mean those that use RPGUI are bound by
the
GPL of powerEXT?
Or is the code you are talking about part of powerEXT core (which I
believe
is under the MIT license)?
Concerning painting myself into a corner, the approach I intend to take
is
to have this new process populate a JSON pointer with the record data
and
that can subsequently have additional elements added. Mihael Schmidt's
JSON
*SRVPGM (LGPL) will work great for this purpose.
Aaron Bartell
http://mowyourlawn.com
http://mowyourlawn.com/blog/
On Fri, Jul 16, 2010 at 11:26 AM, <hr@xxxxxxxxxxxx> wrote:
Aaron,
this looks very similar to the way my powerEXT does the job - why
don't
you just make a programgenerator
the based on a DSPFFD generates the code ?
If you, like in Icebreak creates a "blackbox", you will eventual run
into
trouble when you wants to add additional or
leave out fields.
Med venlig hilsen/Kind regards
Henrik Rützou
HR Software Development
Ved Stampedammen 39
DK 2970 Hørsholm
Denmark
E-mail: hr@xxxxxxxxxxxx
Phone: +45 2714 8449
Homepage: powerEXT.com
--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.
--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.
midrange.com
