User:Aakash: Difference between revisions
| Line 22: | Line 22: | ||
I plan to make it something like this - | I plan to make it something like this - | ||
[[File:PyGTK Study - 1.png] | [[File:PyGTK Study - 1.png]] | ||
[[File:PyGTK Study - 2.png]] | [[File:PyGTK Study - 2.png]] | ||
Revision as of 16:08, 1 July 2011
Aakash is a Google Summer of Code 2011 Student. He has undertaken a project for GUI Improvements & Bug Squashing for the PyGTK GUI.
Development branch: aakash:
Project goals
The primary goals, in order of importance would be –
- Porting extra features of old GUI to the new GUI.
- Addition of requested features. (will think of some too)
- Add whatever more that the GTK library has to offer.
- Check for and fix bugs in my code.
Progress reports
1 July 2011
Implementing the STUDY function in PyGTK GUI now. Had a discussion with John, and for the beginning it will only be 1-D, i.e, we will be varying only one parameter. The implementation will work together with the 'Observers' functionality which is already there.
The idea is that the user can 'observe' all the variables to be studied. Then, one can select which one of them will be varied. There will be a dialog box for setting the upper bound, lower bound, number of steps, distribution type (linear or logarithmic) and an option to run a particular method before each solving. We have also thought of adding a feature where the output data could be written to a file during the solving.
I plan to make it something like this -
27 Jun 2011
Almost completed the port from libglade to GTK Builder. A few warnings related to missing signal connect handlers remain.
Tried it on OS X, Ubuntu and Windows 7. Need to talk to Richard regarding easier setup in OS X. The main issue I am facing is whether to use Apple's Python or Python.org python.
Presently looking into :
12 Jun 2011
Some work on replacing libglade with Gtk Builder in the PyGTK GUI changeset 3483.
14 May 2011
After a discussion with John, the more important bugs to be fixed are
- bug 423 Changing value of solved variable should force removal of 'solved' indication
- bug 501 pygtk/ascdev fails to load solvers under Windows 7
- bug 507 propagate var/relation 'solved' status up through model hierarchy in processVarStatus
- bug 429 default units often not very useful
- bug 472 slvreq: with SOLVER statement before FIX/FREE methods, model is not updated
- bug 294 Implement 'STUDY' function in PyGTK GUI