Carsten Niehaus [Mon, 13 Jun 2005 12:19:22 +0000 (12:19 +0000)]
* adding isotope-date to data.xml
* adding comments to TODO
* improve the isotope-table
* fix the html-layout bug (we for some reasons defined
a width of 400 in the .css-file)
Carsten Niehaus [Thu, 9 Jun 2005 21:32:24 +0000 (21:32 +0000)]
* removing az()
* adding the info if an element is artificial
* adding the info if an element is radioactive
* Only show solid/gasoline/liquid in the som
* this and that
Carsten Niehaus [Fri, 3 Jun 2005 11:24:53 +0000 (11:24 +0000)]
As I will add more type of radii I need to add a lot more code
to element.h/cpp. This commit removed the now unused stuff and
adds the new stuff (which is currently doing nothing).
This avoids to big conflicts with pino coding
Carsten Niehaus [Mon, 30 May 2005 13:42:58 +0000 (13:42 +0000)]
* add the origin of the name of an element
TODO: Improve the infodilaog
* add the ionic radii.
TODO: Only one value possible but some elements (eg Fe) has more
than one ionic radius. But that is for kde4 I guess
Carsten Niehaus [Sun, 13 Mar 2005 18:47:22 +0000 (18:47 +0000)]
* xml-conversion is done. I hope everything works, I didn't see any bugs.
One more thing left to do: Ionisationenergy is not yet read from the
xml-file.
Jason Harris [Sat, 29 Jan 2005 20:54:08 +0000 (20:54 +0000)]
cleaning up some of the horrors in ExtDateTimeEdit. Lots of stale code
here, and not very robust (was causing a crash in PlanetViewer).
Fixed some of this, and lots of cosmetic whitespace fixes too.
I am planning a more complete overhaul here, "soon".
Jason Harris [Sun, 24 Oct 2004 07:01:29 +0000 (07:01 +0000)]
Eliminating flicker in KPlotWidget. Added "WNoAutoErase" flag to
QWidget ctor. It works well!
(note: I first tried to add "setBackgroundMode( QWidget::NoBackground )"
to the KPlotWidget ctor, but this didn't stop the flicker. This is
strange, because that's how I got rid of the flicker in the SkyMap
widget. SkyMap doesn't use WNoAutoErase, yet it is flicker-free. Odd.)
Jason Harris [Mon, 20 Sep 2004 14:51:08 +0000 (14:51 +0000)]
2 Fixes to ExtDateTime and the test program 'test_extdate'.
There were missing validity checks in the new ExtDate code, and
test_extdate needed the new date format strings.
Backporting to 3_3_BRANCH
Jason Harris [Mon, 20 Sep 2004 05:53:07 +0000 (05:53 +0000)]
Update ExtDatePicker to use the new KDE-like date format strings. One
problem: KGlobal::locale()->dateFormatShort() uses a 2-digit year,
which is especially ambiguous considering the huge range of dates
accessible with ExtDate.
Jason Harris [Mon, 20 Sep 2004 05:38:39 +0000 (05:38 +0000)]
Fixing bug #89098 (Date not localized in What's Up Tonight tool).
This is part one of a two-part fix. ExtDate used to use Qt's format strings for expressing dates. However, to localize the expression of the date, we need KGlobal::locale()->dateFormat(), which uses KDE's format strings (which are totally different from Qt's). This commit makes ExtDate and ExtDateTime use KDE format strings.
Jason Harris [Thu, 19 Aug 2004 04:09:41 +0000 (04:09 +0000)]
Fix highlighting of the selected date in the ExtDatePicker widget
for years < 2000. The highlighted date was off by one week because of a
bug in ExtDate::dayOfWeek().
Also, make ExtDate::addMonths() more robust.
This time I actually committed to the correct branch...
Jason Harris [Tue, 1 Jun 2004 01:33:18 +0000 (01:33 +0000)]
Fixing crash condition in ExtDateWidget. If initialized without a date
argument, it was initialized to an invalid date, which caused a crash in the
function ExtDate::daysInMonth(). Two fixes make the widget much more robust:
+ ExtDate::daysInMonth() and ExtDate::leapYear() now check the validity of the
date first, and return sensible default values if the date is invalid.
+ the default ctor ExtDateWidget() now initializes to the current date, rather
than an invalid date.
Jason Harris [Thu, 13 May 2004 07:07:35 +0000 (07:07 +0000)]
Fixing some problems in ExtDate and friends:
Fixed ExtDate::setJD() (did not set calendar date)
Fixed ExtDateTime::addSecs() (bad conversion from int to uint; simplified code)
(added author comment to extdatetbl.cpp)
Jason Harris [Wed, 28 Apr 2004 05:44:59 +0000 (05:44 +0000)]
ExtDate now stores the date internally as the actual Julian Day number, rather than the count of days since 1 Jan 0001. Added function ExtDate::jd() to return the Julian Day and ExtDate::setJD(long int) to set it. Some other code cleanups as well.
Jason Harris [Sun, 18 Apr 2004 07:58:44 +0000 (07:58 +0000)]
Adding ExtDate library to libkdeedu. ExtDate is a replacement for
QDate that eliminates its arbitrary date-range limits (QDate cannot
accept dates prior to year 1752 or after year 8000). There is no
theoretical limit to the range of dates that ExtDate can accept, but
I have imposed a range of -50000 to +50000 for now.
The ExtDate library is based on the initial work of Michel Guitel, who
wrote the original ExtDate class. I have added the following classes:
Most of the work was simply pasting in the class to be replaced, and
global-replacing QDate with ExtDate. However, there are some
remaining issues:
+ currently, only the Gregorian calendar is supported
+ using KLocale to set the date string format does not work
+ API docs are needed
Once the issues have been worked out, I would like to propose to
kde-core-devel that these classes be added to kdelibs for KDE4.
However, I am not sure if any other apps besides KStars really need
very remote dates.
The library includes two test-programs for verifying the performance
of ExtDate. The first (test_extdate) is a command-line program that
simply outputs the results of 9 tests comparing the performance of
ExtDate and QDate. If ExtDate is working correctly, then the only
differences will be for dates outside of QDate's valid range. The
second (test_extdatepicker) is a GUI app showing a KDatePicker and an
ExtDatePicker side-by-side (there is a slight rendering difference
between ExtDatePicker and KDatePicker on my system; I don't know
why this is happening).
The other way to test it is to run kstars; I am going to commit the
ExtDate code in kstars shortly...