Diese Seite mit anderen teilen ...

Informationen zum Thema:
Forum:
JAPI Forum
Beiträge im Thema:
13
Erster Beitrag:
vor 15 Jahren, 2 Monaten
Letzter Beitrag:
vor 13 Jahren, 6 Monaten
Beteiligte Autoren:
Merten, Arjan, sammy, Matthias, Lindon, Cousin, Oyvind, Carl, Luigi, Uwe Schmidt

The future of japi

Startbeitrag von Merten am 02.04.2003 08:17

Hi all,

i want to change the basis of japi away from JAVA. I'v testet a lot of alternative librarys for plattform independet GUI development. The goals are:

1) Of course keep platform and speech independence
2) support further platforms like other Unixe, MacOs, Os2, and maybe some other like Beos, Qnx and Atheos
3) keep printing support
4) keep the API of japi as much as possible
5) leave the client-server base, and replace with traditional linking.

The best libs i've testet:

1) GTK:
a very nice and easy programming lib. No printing and a strange textarea component. No mac support

2) Qt:
Very nice and easy. Win32, Unix, Mac. Has all i need. But Qt is not open source and not free for commercial programms.

3) wxWindows
Very strange programming style. Has all i need. Support for Win32, Unix, Mac, Os2 and some other plattforms. Open source. The first thing i've done, was a patch to get a own mainloop under unix:-( With wxWindows japi will grow up to severeal megabytes. Nevertheless, wxWindows is one of my first choice.

4) fltk2:
first of all, it seems to be the best. fltk2 seems to have all components i need. Its very small and fast. Open Source. A lot of plattforms are supported. fltk2 is in progress, for now, there is no official release. But it will take some time to realise all japi functions with fltk2. Maybe fltk2 will become stable in this time.

There is no decision done at all. I want to know, what YOU think and aspect?

waiting for comments....

Merten

Antworten:

Fltk2 has some attractive properties, in my view, one of them being OpenGL support, which is what I most miss in Japi today. There seems to be a plan for making a release of fltk2 by the end of 2003, and an alpha release mid-2003. This progress plan is fast enough for any Japi use, in my opinion.

The only negative thing I can say about Qt is the licensing.

So, maybe fltk2 would be my first choise :-)

Oyvind

von Oyvind - am 03.04.2003 08:11
Why not start with fltk-1.1.3?

It has it all:
- it is released and stable
- Win32, Unix, Mac support without the need of an bloated underlining
framework (wxwindows2 needs gtk2 on Unix, forget about wxX11)
- simple html widget (suitable for for showing help files)
- OpenGL
- fluid: simple visual gui generator tool. Maybe the output can be
parsed and transformed to generate some kind of gui description
data files helping building japi programes
- several addons: (see the bazaar)
- fl_device: patch for printing support (both unix, and win32 gdi) (alpha)
- fl_cartesian: simple plotter canvas
- fl_connect: better c++ callback support (based on c++ templates)
- Fl_Connnect: (yes, same name): socket support for fltk (alpha?)
- Fl_Table widget: lists, tables ..
- Fl_Tree: tree widget (surprise..)
- fl_utf8: unicode: utf8-patch and others

wxwindows is great on Windows and maybe Linux. I gaved up to try to compile
it on hpux i.e. wxwindows is much richer, but I doubt this is useful for japi
applications.

Carl

von Carl - am 03.04.2003 10:09
In the past I wanted to use wxwindow and fltk but I gave up because of the C++ (I've no time to spend for a new language). With Japi this complexity will be hided to the final user. So I think that the size and speed of the executable should be put at first place. It means I prefer FLTK. Moreover it has even an ODBC support.

Regards,

Luigi

von Luigi - am 03.04.2003 11:58

Hi Merten,

At present, I use JAPI in the intention to provide to distant clients (connected by the intermediary of a simple Internet navigator) a user interface with programs which turn only on a server and which are not easy to compile on another platform.

I believe that the strength of the current version of Japi is that it allows client/server communications. To my mind, JAPI is an interesting tool for people who aren't expert in JAVA programming.

Would it be possible to do the same things with FLTK ?

In addition, I think that you could improve the current version with OpenGL functionalities provided by Java3D or GL4java libraries for example.

Best regards,

Pascal

von Cousin - am 05.04.2003 20:10
> Why not start with fltk-1.1.3?

Of cause, i've tested 1.1.3 too. But i run into big problems by the static menu contruction, which is nearly impossible to addapt this to dynamic creation of menus which is unsed in japi.

In fltk2 there is are dynamic menu realised with ItemGroups.

As fare as i have adapted japi, i find fltk2 stable enough ;-)

Merten

von Merten - am 16.04.2003 11:47
> At present, I use JAPI in the intention to provide to distant clients (connected by the intermediary of a simple Internet navigator) a user
> interface with programs which turn only on a server and which are not easy to compile on another platform.

> I believe that the strength of the current version of Japi is that it allows client/server communications. To my mind, JAPI is an interesting tool
> for people who aren't expert in JAVA programming.

> Would it be possible to do the same things with FLTK ?

Because the new version will not be based on client/server it will overcome a lot of problems many people have to get japi running. But of couse there will be a client-sever version of the new library which keeps the current japi feeling. This means, that output redirection will be able with japi-fltk too.


> In addition, I think that you could improve the current version with OpenGL functionalities provided by Java3D or GL4java libraries for example.

Adding opengl is not as easy as it seems. Gl4java provides thousends of new functions to java which all has to be adapted for japi. It seems to be easier with fltk, because there you can put pure opengl functions between the two calls of 'gl_start' and 'gl_finsh'.

So please be patient,

Merten

von Merten - am 16.04.2003 12:49
Hi everybody,

I'm waiting for a new JAPI version and I hope it comes out soon,
because my programs written with JAPI do not satisfy my colleagues. The biggest problem is speed of the graphics. I am programming GIS - geographical - "homebrew" software in C.
MY PHD-thesis for anybody who is interested: [hss.ulb.uni-bonn.de] And another problem is the correct installation of JRE and networking. Very often my colleagues get that message which says
JAVA not installed or networking not installed or something like that.
So Merten, hope toe hear from you soon saying the FLTK-version
of your GUI-library is ready. Will it be difficult to switch from JAPI
to FLTK ???

Uwe

von Uwe Schmidt - am 24.04.2003 08:11
> I'm waiting for a new JAPI version and I hope it comes out soon,
> because my programs written with JAPI do not satisfy my colleagues. The biggest problem is speed of the graphics.
> And another problem is the correct installation of JRE and networking.

I know, this are the major drawback of japi. A lot of people are running into network problems by using japi. It's the main reason why i want to change to fltk to build up an easy to use library.

> So Merten, hope toe hear from you soon saying the FLTK-version of your GUI-library is ready. Will it be difficult to switch from JAPI to FLTK ???

No. You will find the new version nearly identical to the JAVA based versions. Of cource threre will be some minor changes because of the different APIs of JAVA and fltk. Eg. the textarea size will now be specified by pixel and not by rows and colomns. And the filedialog will become a new parameter to filter the shown filenames.

Unfortunately, the new semester has started and i have to do my job first :-(

Have Fun

Merten

von Merten - am 25.04.2003 08:44
I'd personally go with wxWindows rather than Fltk... wxWindows if more 'science oriented' with better standard GUI component, such as a very nice 2d plotter. Plus, wxWindows is already ported to many languages like python/basic/lua, while fltk is only C++.

von Lindon - am 18.07.2003 21:55
Hi,

With impatience I have checked this discussion for the past few months. I consider myself to be an end-user and consequently I have little (=no) interest in knowing the details of your new solution. This is not arrogance: JAPI is so good in simplifying my software-interfaces that I have never had a need to deviate from my main focus on the scientific problems that I was solving with my programs. As an end-user of JAPI I appreciate this beautiful castle that you have built and I am curious to know if there is any progress. What's new? Have you reached a verdict about which library to use? And: is there any idea of when you'll find the time to accomplish the effort?

(High) regards,

Arjan

von Arjan - am 30.07.2003 09:52
Hi,

I just found JPI.

Well, i think using java is a great idea.
I did not tested it already,
but instead of using the AWT, you could use the SWT.

I think this will give better performance and
native look on each platform supported.

Good work !!!!

:spos: :spos: :spos:
:-)

Sammy

von sammy - am 06.09.2003 22:27
Well I just would like to know what a user, who wants to run a program developed by me with JAPI based on FLTK2 has to have to run it?

If I want to share a program now (JAPI based on JRE/JAVA) the user just have to download jre1.2 or something from the official sites of sun and he can use my program. What a user has to download if JAPI is based on FLTK2 if he wants to run my program?

Furthermore I would like to know if I can go on programming now even though the GUI toolkit will change? So if the new JAPI is released based on FLTK2 (or what is decided then to use) I won't have to do too much changes in my programs. Or should I wait until the release is made because the changes will be so extensive that I can begin new with developing the program I am currently working on?

von Matthias - am 10.12.2004 11:56
Zur Information:
MySnip.de hat keinen Einfluss auf die Inhalte der Beiträge. Bitte kontaktieren Sie den Administrator des Forums bei Problemen oder Löschforderungen über die Kontaktseite.
Falls die Kontaktaufnahme mit dem Administrator des Forums fehlschlägt, kontaktieren Sie uns bitte über die in unserem Impressum angegebenen Daten.