[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #47700] Octave JDialogBox interface uses depre
From: |
Kai Torben Ohlhus |
Subject: |
[Octave-bug-tracker] [bug #47700] Octave JDialogBox interface uses deprecated features |
Date: |
Fri, 15 Apr 2016 11:50:29 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.75 Safari/537.36 |
Update of bug #47700 (project octave):
Status: None => Need Info
Assigned to: None => siko1056
Operating System: GNU/Linux => Any
_______________________________________________________
Follow-up Comment #1:
Maybe we should abandon all Java-dialogs, instead of trying to fix and
maintain unused code. There are two concurrent implementations of dialogs
(Java and QT). The documentation still mentions only Java:
https://www.gnu.org/software/octave/doc/v4.0.1/Dialog-Box-Functions.html#Dialog-Box-Functions
The concurrency is visible in
scripts/gui/private/message_dialog.m,
where first always the QT variant is tried, thereafter the Java variant. Thus
I think no one has ever really seen the Java variant before, as QT works
naturally with the GUI.
The java variant is implemented in
scripts/java/org/octave/*.java
the QT variant in
libinterp/corefcn/octave-link.{h/cc}
The only pro for the Java-variant is, that it is able to print some TeX
symbols
https://www.gnu.org/software/octave/doc/v4.0.1/Which-TeX-symbols-are-implemented-in-dialog-functions_003f.html
This doesn't apply for the QT-variant, but for me this feature has never been
accessible before and it is a minor victim for clarifying the code a lot.
As I don't get negative respone, I will remove the Java-variant with changes
to the calling code and documentation.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?47700>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/