1 /* $Header: /cvs/gnome/gcalctool/TODO,v 1.74 2006/01/09 16:30:20 richb Exp $
3 * Copyright (c) 1987-2008 Sun Microsystems, Inc.
10 * From James Brown <alumnus at bigpond dot com>
11 In engineering it is typical to think of numbers in scientific notation
12 in powers of three for example
13 123473 - I would only use say 4 signification "digits" and would say
16 and .00000324 would be three point two four micro units
18 The only improvement I could suggest would be to have an engineering
19 mode where the postfix milli,micro,nano,pico,kilo,mega,giga etc
20 (m,u,n,p,k,M,G respectively) was shown next to the number.
22 * With the gcalctoolrc Gtk resources copied to a ~/.gcalctoolrc file, the
23 "*displayitem*" widget and the "*register_label<n>*" widgets background
24 color aren't being set to white.
26 * Improve the colors in the gcalctoolrc file.
28 * Now that constant and function definitions are read/written as Gconf
29 resources, there are three pieces of functionality that are no longer
30 present. Need to be consider whether we wish to reimplement them. They
32 - ability to read new constant/function definitions from a .gcalctoolcf
33 file in the current directory, which override the ones in the users
35 - ability to set initial values for the ten memory registers.
36 - ability to extensively comment the definitions in the file.
38 * Implement bugtraq rfe #1190372/#1105626.
39 It appears that function definitions are unable to handle all calculator
40 buttons. Buttons with a keyboard equivalent that is a special key (clear
41 display) or key combination (^s - Sin) appear to be rejected in functions
42 defs. This affects the availability of many of the calculator buttons.
44 * Implement bugtraq rfe #4023507.
45 The calculator in Scientific mode accepts hex entries of up to
46 eight digits. This was sufficient to deal with 32-bit addresses.
47 When Solaris is 64-bit, the calculator will be less useful.
48 Maybe there should be a Logical-64 mode.
50 * Consider adding in the ability to drag & drop from/to the display and
53 * Consider adding in some more functions:
55 ~ Common antilogarithm and natural antilogarithm.
57 ~ Root key. The y root of x.
58 ~ Rectangular to polar and polar to rectangular keys.
60 * Consider adding Reverse Polish notation functionality (as an option).
62 * Unit tests! Currently a test vector with button presses and result analysis
65 Gcalctool - Next Generation TODO (Arithmetic Precedence (AP) mode)
66 ------------------------------------------------------------------
68 * CE parser has 2 reduce/reduce errors (mostly harmless :)
70 * Answer cannot be used in logical calculations because answer may not
73 * Base conversions are not easy to use. (Only answer can be converted)
76 - History of previous expressions (scrollable)
77 - Support writing/editing expressions as a text.
78 - Copy / Paste support (especially reusing previous expressions and answers)
80 - Autocomplete / hints
82 * Gcalctool should give more detailed information in case of syntax error.
87 * Shouldn't have to convert back to a double in make_number() in order
88 to test if the number is too large to be displayed in fixed point.
90 * The cmax field for make_fixed should be dynamic, and depend upon how
91 many characters can be displayed (ie. a larger gcalctool will be able
94 * Tidy up the code in mp.c, to eventually use no labels and goto's.
96 * Adjust all uses of MP...[MP_SIZE] to use a dynamic size so that it's
97 possible to calculate to numbers of any length.