Re: Convert DS/Record to JSON -- WEB400

Hi Henrik,

I try to develop tools that lessen the time required for the programmer even
if they only address 80% of the scenarios they get involved in. So when you
say it "cannot" be done, i understand where you are coming from, but to not
pursue it because of that I believe we then miss out on developing a few
simple tools that greatly simplify the programmers life.

In regards to powerEXT license powerEXT has now been devided into

to seperate products/projects:

My point is that you need to have this clearly documented on your website so
people don't have to wonder how the code is licensed. Is what you just
conveyed available to the user without having to download powerEXT?

BTW, I fully agree with your wanting to gain monetarily from powerEXT -
that's one of the few ways we can continue to get good open source out into
the community. I have been able to gain monetarily from a number of RPGUI
projects through hourly work since it was released in Nov. The only
difference between RPGUI and powerEXT licensing is that RPGUI is LGPL and my
hope is that people use it liberally everywhere so RPG can once again become
a mainstay on the IBM i without the need to jump ship to Java/.NET/PHP for
the front end.

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 ;-)

That is a completely different context. When I recommend RPG-XML Suite as a
possible solution on these lists I clearly declare that I am a vendor with a
licensed commercial product.

Aaron Bartell
http://mowyourlawn.com
http://mowyourlawn.com/blog/

On Tue, Jul 20, 2010 at 9:12 AM, <hr@xxxxxxxxxxxx> wrote:

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