On Tue, 2011-05-10 at 11:12 +0200, [email protected] wrote: > On Tue, 10 May 2011 11:02:07 +0200 (CEST), [email protected] > wrote: > > On Tue, 10 May 2011, Joost van der Sluis wrote: > > > >> On Tue, 2011-05-10 at 01:24 +0200, Darius Blaszyk wrote: > >>> Here's a first version of a graphical front end for fppkg. > >>> Currently it supports all basic commands. It's my plan to extend this > >>> front end in the future and at some time support lazarus packages as > >>> well. > >> > >> I didn't looked at it yet, but how does it works? Does it call fppkg > >> on > >> the command-line? > >> > >> I'm happy that you are doing all this work, that way I don't have to > >> do > >> it. ;) > >> > >> But my plan was to do one of the following: > >> > >> A: Install the fppkg units, so that these can be used to create > >> frontends to fppkg > >> B: Create a fppkg-lib, so that that one can be used to build > >> fppkg-frontends. > >> > >> Question is what is the best option? > > > > Since everything is based on classes, I would think that A is the > > best > > option. We can create a lazarus package for it, which contains all > > units as > > virtual units. > > I would say A as well. However I have no idea what you mean with > virtual units. What are they? Also if I'm not mistaking fppkg lives in > utils. Should this be moved to packages then?
That's exactly the idea. When those units are moved to packages, they are available (virtual) to everyone. Lazarus and non-Lazarus. (So making them a Lazarus package is not the right way, imho) Problems of this option can be that the fppkg version installed on a system is different then the version which is used when building the application. The library solves that problem. Joost. -- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
