SatishaSetty / indic-keyboards

Automatically exported from code.google.com/p/indic-keyboards
0 stars 0 forks source link

Is it possible to port this application to C++ ? #10

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
This issue is for understing only.
I like to know why this application is made using java ? I feel Java is a
bad choice for such keyboard handling application. Is it possible to port
this to c++ ? if yes, how difficult is it to port to c++

Original issue reported on code.google.com by hostmast...@bigbridge.com.au on 18 Nov 2009 at 6:11

GoogleCodeExporter commented 9 years ago
Java keeps most of the code platform independent. Except for the actual 
interface
with the keyboard (which is written in C/C++), the code is pretty much (90%) 
the same
on both windows and Linux. Also designing interfaces with Eclipse SWT is 
painless
compared to the C/C++ alternatives like QT, GTK+ etc. (Bear in mind we are 
talking
about doing it on both Windows and Linux) 

I don't see any reason to port this to C++.

Original comment by u.aks...@gmail.com on 20 Nov 2009 at 6:56

GoogleCodeExporter commented 9 years ago
For the reasons that Akshay mentioned above, Java and Unicode have been our
preferences since beginning.

Original comment by shiv...@gmail.com on 20 Nov 2009 at 7:06

GoogleCodeExporter commented 9 years ago
I like you to reconsider this bug on the following points:

1. The java based indic keyboards is very slow in windows computers.
2. They require addional bulky java dependency - this makes us difficult to 
introduce
this softeware to new users.
3. Since this software is meant to be sitting in the memory always till the
multilingual user logs on to windows, this should consume less memory and run 
faster.
This can be achived only thro a C/C++ based tool.
4. C++ tools like QT are meant to be cross platform and as you have already 
mentioned
you use java only for the UI and real keyboard logic is still done using C++. It
makes sense to design the UI also in QT (or any other c++ cross platform GUI 
libraries)
5. If you want more easy cross platform code you can try using Python or ruby 
plugins
for QT
6. And you already know the software is not usable in Linux right now. Atleast 
make
this efficient in windows using c++, we can get it ported to linux very easily.

Original comment by mugunth on 24 Nov 2009 at 12:29

GoogleCodeExporter commented 9 years ago
This is not a bug.

1. Linux you mean?

2. JRE is the only dependency. Don't confuse it with JDK. (Python, Ruby and even
C/C++ for that matter needs a runtime to function.) 

3. Please rephrase this point 

4. SWT libraries are easier to port in Windows compared to QT. If QT is used, in
Linux the software will not work on GTK based applications. For example Ubuntu 
is GTK
based. If our software was written using QT, it wouldn't have worked in Ubuntu. 
UI is
not all that is done in Java. Please go through the source code.

5. Read points 2 & 4

6. The memory fingerprint of our software in windows is less than 5MB and the
processor usage is almost 0.1%. This, I believe is efficient. Were you trying 
to tell
us something else? We are working on the Linux issue. C/C++ or Java is not the 
reason
for seeing English characters as you type in Linux.

Original comment by u.aks...@gmail.com on 24 Nov 2009 at 4:43

GoogleCodeExporter commented 9 years ago
Ok fine. 

I will respond after stuying source code in detail.

Original comment by mugunth on 2 Dec 2009 at 6:25