From kde-commits  Sat Apr 30 22:20:54 2005
From: Jason Harris <kstars () 30doradus ! org>
Date: Sat, 30 Apr 2005 22:20:54 +0000
To: kde-commits
Subject: kdeedu/kstars/kstars/tools
Message-Id: <20050430222054.78EBD665 () office ! kde ! org>
X-MARC-Message: https://marc.info/?l=kde-commits&m=111489966722459

CVS commit by harris: 

Adding ability to load/save observing lists.  Please test if you have 
time.  I'd like opinions on some design decisions in this feature:

+ When saving an observing list, should we ask the user to specify the 
filename (as we do for DCOP scripts), or simply create a filename from 
the user's list name, and place it in $KDEHOME/share/apps/kstars (as we 
do for color schemes and other stuff)?  Right now, I am asking for the 
filename, but I think it might be better to just "hide" the actual files 
in $KDEHOME. 

+ When opening an observing list, if there are already objects in the 
current list, should the new observing list be appended to the current 
one, or should the current list be cleared first (with save warning, if 
applicable)?  Right now, I have it clear the current list before loading 
a new one.  

+ Any brilliant ideas to improve the UI?  I'm not very excited about 
having two rows of buttons at the top of the window.

thanks for any input!

CCMAIL: kstars-devel@kde.org


  M +135 -14   observinglist.cpp   1.10
  M +16 -1     observinglist.h   1.4
  M +147 -1    observinglistui.ui   1.3