[fpc-pascal] The new book: "WEB and database programming with fpc and Lazarus for newbies and professionals"
Burkhard Carstens
fpc at bcsoft.de
Fri Jun 18 09:25:07 CEST 2010
Am Freitag, 18. Juni 2010 04:13 schrieb Bee Jay:
> On 18 Jun 2010, at 02:58, Burkhard Carstens wrote:
> > What about ExtJS being GPL licensed? Got a developer license?
>
> Yes, if you make commercial apps.
:-(
> > Here you refere to the ExtJS components of fpweb, right? IOW. if
> > those are (or will be) universal, they should get renamed? (see,
> > you are in that stuff, so for you, all this is clear. for a newbie
> > (at least for me), it's still all confusing .. so having clear and
> > distinct names would help.. e.g. if it's about the fpWeb components
> > for use with ExtJS JavaScript Framework, they should be called
> > fpExtJS components ..)
>
> fpWeb is general purpose framework. You may use it with any JS
> frameworks out there. Michael had made an example how to use it with
> ExtJS. So, fpWeb is already an apropriate name, IMO.
Sure, fpWeb is fine. What I mean:
1) clear distinction between
a. "ExtJS Component" : a component of the ExtJS framework written in
JavaScript.
b. "fpExtJS Component" : a component of fpWeb written in pascal,
designed to deal with an ExtJS component.
It's just a documentation/communication issue: "..ExtJS components can
be modified to support jquerygrid.." vs. "..fpExtJS components can be
modified to support jquerygrid.."
2) *if* fpExtJS components get modified to also support jquerygrid, they
should be renamed to fpUniJS component (or so). A well choosen name,
which reflects the functionality, relationship and restriction of a
component saves half a page of documentation and makes it easier for a
newbie to get an overview.
regards
Burkhard
More information about the fpc-pascal
mailing list