So, do you guys have any idea about how to structure this? I was
initially thinking of building this on the structure of the
jumpstart, but I'm now not so sure that this is a good idea. I did do
this for RIFE/Crud though, and people don't seem to have a problem
with it since the binary distribution is simply a jar file. The
advantage of including the jumpstart is that it's very easy to
develop examples and allow people to try out the components. A
disadvantage is that the included jumpstart needs to be kept up-to-
date with each release, and doing this already takes up a lot of my
time.
What do you guys think?
On 01 Aug 2006, at 17:53, Steven Grimm wrote:
> I am now!
>
> Geert Bevin wrote:
>> Frederic, Steven and Tyler, are you guys subscribed to rife-devel,
>> I think it's more appropriate to continue this discussion there.
--
Geert Bevin
Uwyn "Use what you need" -
http://uwyn.comRIFE Java application framework -
http://rifers.orgMusic and words -
http://gbevin.com_______________________________________________
Rife-devel mailing list
Rife-devel@...
http://lists.uwyn.com/mailman/listinfo/rife-devel