[kepler-dev] Copying ptolemy classes instead of extending them

[ben leinfelder]

I'm pretty sure it was just an oversight putting reporting code in the  
root of trunk instead of under modules/reporting.
We'll get that squared away today.
-ben

On Jan 12, 2009, at 4:40 PM, Christopher Brooks wrote:

> Hi Debi,
> I'm just curious, but why are you copying Ptolemy classes instead of
> extending them?
> I saw Top.java get added a moment ago as well.
>
> In general, copies of classes end up causing problems because
> we end up with two classes with the same name, but different
> functionality.  Also, the copies don't get bug fixes, though
> some would say that having a frozen version of these base classes
> is a good thing.
>
>
> _Christopher
>
> staggs at ecoinformatics.org wrote:
> > Author: staggs
> > Date: 2009-01-12 16:23:41 -0800 (Mon, 12 Jan 2009)
> > New Revision: 16313
> >
> > Added:
> >    trunk/reporting/src/ptolemy/
> >    trunk/reporting/src/ptolemy/vergil/basic/BasicGraphFrame.java
> > Removed:
> >    trunk/reporting/ptolemy/
> >    trunk/reporting/src/ptolemy/vergil/basic/BasicGraphFrame.java
> > Modified:
> >    trunk/reporting/src/org/kepler/reporting/gui/ 
> ItemsOfInterestPanel.java
> >    trunk/reporting/src/org/kepler/reporting/gui/ReportingGUI.java
> > Log:
> > Moved some classes into a different location
> _______________________________________________
> Kepler-dev mailing list
> Kepler-dev at kepler-project.org
> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
>