[Kstars-devel] RFC: Redesing of KStars

[Jason Harris]

Hello,

On Wednesday 03 August 2005 06:46, Thomas Kabelmann wrote:
> Hi Jason,
>
> the names component and composite are a name convention, so everybody who
> is familar with this design pattern would easiely understand this concept.
> But surely it's just names, so we can think about how to call it else.
>
> Currently we have a concept of separating data of it's representation. Data
> are stored in SkyObject and representation is in SkyMap. I don't want to
> mess up SkyObject with drawing code etc. A SkyComponent, or whatever we
> will call it, should have the interface with init/draw/update. Subclasses
> of SkyComponent contain a pointer to it's data. This is because not all
> components need skyobjects, for example the horizon is a list of SkyPoints.

Okay, that makes sense,  thank you for the explanation.  If 
component/composite are standard names, then let's stick with the standard.

Jason
-- 
KStars: KDE Planetarium
http://edu.kde.org/kstars