Re: [Dynapi-Dev] improvements, widgets and stuff

[Scott A. L. <sc...@sc...>]

I agree.  We should probably separate out the widgets into packages with
descriptions and make them available as a separate download.  Then new
users can choose the package they feel most comfortable with.

I think only the core, ext, and util files should be hard-coded into the
DynAPI include libraries.  Everything else, like widget libraries, can
be added by the developer.

I suggest also moving lite classes out, because they're difficult to
maintain.  Any patch incorporated into the core has to be added to lite
classes too.

Since the only thing that's 'official' about DynAPI2 are the core files,
I think only those should be available in the core download.


Robert Rainwater wrote:
> 
> Hi,
> 
> I have no problem handling the new releases at sourceforge.  However,
> I think we need some guidelines and some consensus as to what
> additions should be made to releases.  There are always patches
> available in the patches sections, but we need to have more discussion
> as to whether the patches are worthy to be added to the next release.
> 
> Also, I would like to see a lot of the widgets and extra stuff in the
> distro moved out.  Maybe each person can provide there own widget pack
> in a separate download.  This would make the dynapi much less
> confusing to new users, than having 10 different peoples stuff in
> there to everyone.  Especially, since everyone uses a different style
> to create their widgets that new users will be lost when trying to
> learn how to right widgets.  If we provide separate widget packs, then
> users may decide they like one persons over another, but at least they
> will have a choice.  Maybe just include a few basic widgets (that we
> can decide on) and some documentation (we need some api docs anyone?).
> 
> Later,
> Robert <rai...@us...>
> 
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev