Greetings, There has been some dialog on changing the way vTcl is shipping, namely moving the cvs toward only shipping with core, user, customBWidgets and vtcl widgets. Then having all other widget support available for adoption and maintenance. Supported widgets could then be made available to download and plug in to vTcl. The hope is that this would allow the following:
* vTcl core shipment can become very stable. * Provide a clean base footprint for users and developers to extended. Perhaps with other licenses beyond the GPL. * Developers can adopt a widget to provide the support they desire. * With good documentation on the model to interface a widget to vTcl the job of keeping widgets up2date would be broken down to smaller peices that should allow more skill levels of developers to assist. * Allow for the project to move more quickly to support new widgets or correct existing widgets that suffer problems from new release changes. Thoughts and ideas welcome. ---------- RJEnt Linux Solutions ------------------------------------------------------- This SF.Net email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn firsthand the latest developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV, and more! http://www.apachecon.com/ _______________________________________________ vtcl-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/vtcl-user
