1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
|
Modifications needed for getting rid of Qt3Support dependency
=======
TODO items before the next release
=======
Features which need re-implementation in Qt5 port
=======
- dbus integration for documents (used to be dcop bindings for documents)
- TextDocument::clearUndo / clearRedo is not implemented; only used in newly created documents
Fixes that could be postponed after the first Qt5 release
=======
- property editor; property editor item
- fix glitch of reset button disappearing when horiznotally resizing the property editor
- in 0.40.0 it is glitching, too, when resizing
- need to fix reset to default button
- if user clicks on the editor, then the reset button appears
- proper solution is to add 2 widgets +layout in the cell, and do not do any custom widget resizing
- icon for component model widget is not displayed, used to be "locationbar_erase"; to add proper icon
- in flowcode if the PIC is "minimized", after adding a new item on the canvas, the
"Advanced..." button still appears on the canvas
- help->ktechlab manual does not work, shows only "documentation not found"
https://bugs.kde.org/show_bug.cgi?id=402158
- maximum size of collected oscilloscope data should be configurable and should signal the user that the buffer is full
- for now the line "flats out" when it reaches its limit; a Reset makes it collect data again
- undo / redo interface needs to be properly fixed for text documents: this interface is not exported by KDE4 KTextEditor
http://api.kde.org/4.10-api/kdelibs-apidocs/interfaces/ktexteditor/html/kte_port_to_kde4.html
- a hack is in place which works
- printing a text document needs fixing
- hack is in place, it works
- some PICs do not have SDCC support (e.g. Pic18Cxxx). These should not be selectable from the GUI
- minimize the number of bundled 3rd party icons; most should be usable from Oxygen icon theme
- loading C code to PIC fails
- apparently when using a project, the PIC gets recognized and uploading works; looks like a feature
- components have no description
- the context help exists; or something else is needed here?
- missing for: VCVS, VCCS, CCVS, CCCS, Push-to-Make, Push-to-Break, NPN, PNP, n-JFET, p-JFET, n-MOSFET, p-MOSFET,
Inductor, Bar Graph Display
- created subcircuits appear twice in the subcircuit list; investigation needed
- created subcircuits in some cases they cause crashes; investigation needed
- Translations: not all strings are available in gettext ( https://bugs.kde.org/show_bug.cgi?id=375726 )
- Oscilloscope view sometimes does not scale the signals correctly ( https://bugs.kde.org/show_bug.cgi?id=371625 )
- Op-amp with positive feedback behaves as amplifier; should behave as comparator ( https://bugs.kde.org/show_bug.cgi?id=371622 )
Modifications needed for KF5 port
=======
Old TODO entries, to be reviewed
=======
See http://wiki.ktechlab.org/ - not entirely ready yet, but I plan on moving (at least some of) the stuff in this TODO file to this wiki. This allows for better categorization, discussion, etc of ideas than a plain-text file in subversion that only a few people have write access to.
0.4 targets:
* Replace QCanvas with own optimized implementation.
* Only use IDs for items, etc, in ItemDocumentData - otherwise they lead to too many bugs.
* More intelligent connector routing.
* Variable time step in Simulation.
* Fix subcircuits so that they are saved in an itemdocument.
Bugs:
* At the moment, KTechlab auto-detects a point in the circuit to use as ground, according to a set of priorities (e.g. the Ground component has the highest priority, then voltage elements, etc etc). However, some circuits do not have any point which should be considered ground, e.g. "(+9V)-------(Battery)". Suggested solution: detect a point to have as a fixed voltage, that can be anything including 0V.
* Microbe should give "noline" where applicable in show-source (such as in delay routines).
Features:
* Bookmarks in the oscilloscope.
* Work area text: allow clickable URIs, rich text editor.
General TODO:
* optimize microbe some more?
Polishing:
* Informational message when user attempts to paste flowcode into a circuit (can't do so; must save and load into pic).
* On program startup, use "text blobs" pointing to sidebars to explain what they do.
* Update register info even when PIC is paused.
* replace "refresh rate" slider in settings dialog with standard one.
[Being worked on or soon to be worked on]
david:
electronerd:
* refactor the oscilloscope for better code reuse and so I can add a view that looks more like an oscilloscope's screen instead of a printed tape
william:
* In progress:
- variable capacitor/trimmer - Done.
- variable resistor - Done.
- Voltage Regulator - On Hold.
- bar graph display - Done.
* Future Ideas: (leave me a note if anyone wants to do any of these so I know and can remove them)
- crystal oscillator
- 16 seg display
- bridge rectifier
- opto isolator
- Scmidt NAND
- Schmidt Inverter
- Thyristor
- Zener Diode
- Logic analyser (16 bit) and graph output
- Variable Inductor
- Solenoid ( requires animation )
- Bar Graph Display Driver
=======
The following have been brainstormed with reference to other electronics software I have used. I have found these features useful and these are all wishes for the future that may or may not be relevant to the direction the software takes in the future. I will obviously consult before attempting any of them:
- Model poperty framework for components to include things like wattage, frequency, resistance, etc... of components using specs of manufactured components, with the future goal of accurate simulation of component destruction. This will also allow a parts list to be created when a circuit is completed. Just an idea, up for discussion.
- Allow labeling of components in circuit, eg. R1, R2, C1, C2 etc.. Maybe a caption facility.
- Right click properties for component model, values with separate value and multiplier selection to make it easier. This could be implemented in the Item editor too.
-Circuit drawing on a black background to better visualise animated wires and logic levels through wires. Different view options: voltage levels, current flow, logic levels, normal(no wire animation of any sort).
- A means for users to create a circuit which is intended for use in a component, and to link the created circuit to a generic component that automatically creates the required in/out pins with reference to the created component circuit. On top of this, a means for users to submit new components they have created this way to allow the library of components to be built. So instead of a long list of IC's one generic one may be used with a library containing the circuits needed to simulate different types which can be chosen for example through the Item Editor.
|
