I haven't followed this thread all that close and don't plan to go back
and re-read all the responses, however I think the general gist was
Aaron wasn't comfortable using ExtJS for some licensing reason.



Since the RPGUI project is supposedly going to be open source which
ExtJS seems to support in their model, what's the issue ?



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 <mailto:richard@xxxxxxxxxxxxxxx>
Web Site: http://www.rjssoftware.com <http://www.rjssoftware.com/>
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT

---------------------------------------------------------

One of the things
<http://archive.midrange.com/web400/201001/msg00278.html> I liked about
Aaron's original plan to use ExtJS was that it was fairly complete and
single <http://archive.midrange.com/web400/201001/msg00278.html>
source. While I'm all in favor of plug-able architectures in general, I
think that to use anything that requires users of RPGUI to deal with
plugging in bits and pieces from multiple sources would be completely
counter to the declared intent of the project.

Those of us who are already "into" thins kind of stuff are not the
projects target audience
<http://archive.midrange.com/web400/201001/msg00278.html> surely. So
isn't it important to avoid any additional complexity as much as
possible?



Jon Paris
Speaking as someone who loves Eclipse
<http://archive.midrange.com/web400/201001/msg00278.html> but has torn
out many hairs trying to plug things in.


www.Partner400.com
www.SystemiDeveloper.com


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.