As a side project, it could be possisble to go through each of the examples / widgets
and
develop a dependancy list. This way, when a line of code changes in one file, we know
exactly which additional files could have been effected.
This would also mean that we only need to update The Matrix (he he he, white rabbit) by
checking the effected areas of the examples.
bob basques wrote:
> What about a preiodic collection from Source forge where the data could be updated
>and
> still be kept all in one spot. All that would be needed is some scoping on the
>content
> for the data upload form and the database structure.
>
> Could write something in a CGI that goes out and periodically collects the data from
> SourceForge and compile a compatibility chart from the information collected.
>
> Am I way off base here, should this be seperate from SourceForge?
>
> bobb
>
> bob basques wrote:
>
> > Michael Pemberton wrote:
> >
> > > Sounds great. How often would this be updated? I ask because with the a
>snapshot
> > > created daily and code changin by the minute, it would be great to know when a
> > > feature became broken / fixed.
> > >
> > > This would all for fututre monitoring of code to reduce the creation of similar
> > > mistakes.
> >
> > I can also envision a similar setup for the core objects, at least to track bugs.
>I
> > think that the updating by author is the key to something being used and
>successful.
> >
> > I need to ponder it some more though.
> >
> > bobb
> >
> > _______________________________________________
> > Dynapi-Help mailing list
> > [EMAIL PROTECTED]
> > http://lists.sourceforge.net/lists/listinfo/dynapi-help
>
> _______________________________________________
> Dynapi-Help mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/dynapi-help
--
Michael Pemberton
[EMAIL PROTECTED]
ICQ: 12107010
_______________________________________________
Dynapi-Help mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-help
