Opened 15 years ago
Closed 8 years ago
#43 closed task (fixed)
Restore GUI functionality
Reported by: | kilian | Owned by: | jr_reuter, chokoufe, cweiss |
---|---|---|---|
Priority: | P1 | Milestone: | v2.3.0 |
Component: | core | Version: | |
Severity: | major | Keywords: | |
Cc: |
Description
Develop a graphical interface. Some components and a basic Qt interface library exist and should be integrated in the W2 package.
Change History (9)
comment:1 Changed 14 years ago by
Milestone: | v2.1.0 → v3.0 |
---|
comment:2 Changed 9 years ago by
Milestone: | v3.0 → v2.3.0 |
---|---|
Owner: | changed from kilian, wirtz, trudewind to jr_reuter, chokoufe, malinauskas |
comment:3 Changed 9 years ago by
comment:4 Changed 9 years ago by
Owner: | changed from jr_reuter, chokoufe, malinauskas to jr_reuter, chokoufe, cweiss |
---|
comment:5 Changed 9 years ago by
Summary: | GUI → Merge GUI with WHIZARD trunk |
---|
comment:6 Changed 9 years ago by
Right now the GUI is located on bitbucket. It is basically functional and can be moved to the WHIZARD trunk for further development.
comment:7 Changed 9 years ago by
Summary: | Merge GUI with WHIZARD trunk → Restore GUI functionality |
---|
The merge of the GUI with the trunk has been done. Unfortunately, a change in the java-script libraries caused it to not work anymore.
comment:8 Changed 8 years ago by
Priority: | P3 → P1 |
---|
What is the status of this after BACN's latest commit? Working again?
comment:9 Changed 8 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
Indeed, as confirmed today, the GUI is working again with the functionality at then of the internship of Augustinas Malinauskas.
Some news in r7322: To allow for online update of histograms and other stuff, I implemented a callback feature.
The rt_data block contains an allocatable object called event_callback (abstract). The abstract type contains a procedure that would be called once after N events, where N is given by event_callback_interval. The callback procedure has access to the event object. To activate this, one has to extend the event_callback_t to a a concrete type which could, for instance, call a C function via its associated procedure. The object has to be injected via global%set_event_callback.
A concrete example is in the unit test commands_34, where the callback procedure executes analysis_write and thus prints the current analysis data once every N events. This should be useful for a GUI.
(Currently there is only one callback at a time; if this proves useful, the feature could be extended to multiple callbacks.)
What is not implemented is a means for providing the callback routine/object for WHIZARD from the outside. In the unit tests, this is hardcoded. Possibilities are a library routine, a commandline switch, or a libdl call. This depends on the actual application.