-
-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AWT #144
Comments
AWT is presently unsupported. |
It's not supported on Windows either. |
AWT is a windowing toolkit. I can't quite figure out what you're suggesting. |
Headless mode might work. |
Will leave this issue around to discuss eventual AWT support. Ideas: First off, I think abandoning the existing WinForms support is probably the right thing to do, at least for now. It needs a serious reassessment for Core anyways. I think a better initial strategy would be to port the actual OpenJDK AWT toolkits to IKVM. They consist currently of mostly native callouts to existing Windowing libraries: Win32, GTK, etc. I think it would be fine to consider compiling the actual C of this, and having it distributed in some separate OS specific packages. IKVM.Java.AWT.Windows, IKVM.Java.AWT.GTK, or something. Given how well JNI works, this shouldn't actually be much of a problem. We get to make the thing work while not having to write much code of our own. If somebody wants to, they can implement a managed AWT toolkit. |
I don't know what that error is in reference to. You're going to have to be more specific. |
AWT is not supported....... |
IKVM.AWT.WinForms, which is the AWT toolkit implemented on top of WinForms. It was never a very well-completed project, and ended up pretty broken on Core. Not to mention completely non-cross platform. |
I don't understand the question. Do what? This thread is about AWT, but none of your questions seem to have to do with AWT. If somebody wants to fix IKVM.AWT.WinForms, they can. It's not on my list of things to work on. If somebody wants to get the Sun/Oracle native AWT toolkits compiling, they can. But also, not really a focus of mine. |
You should probably not bother Jeroen. He is unlikely to answer.
The native libraries encompassed two parts originally: the JNIEnv bridge, and a number of one-off functions used in various parts of IKVM (mmap, few other minor things). The mmap stuff was removed (by me). All that remains is the JNIEnv bridge. And that continues to live in the ikvm-native library. |
What tests? What are you talking about? |
Yes, but what tests? |
Java has a headless mode. Look it up. |
|
Please do not close this issue, as it represents actual future work that should be accomplished. |
This will be done in a couple of weeks Other reference |
AWT support merged into develop branch. |
Using the latest 8.9.0-pre.1 using System.Diagnostics;
using java.awt;
namespace IKVM.ConsoleApp
{
public static class Program
{
public static void Main(string[] args)
{
while (!Debugger.IsAttached)
System.Threading.Thread.Sleep(100);
AWTExample1.Foo();
java.lang.System.@out.println("hi");
System.Console.ReadLine();
}
public class AWTExample1 : Frame
{
AWTExample1()
{
var t = new TextField("THIS IS TEXT");
t.setBounds(30, 30, 80, 30);
add(t);
var b = new Button("1234");
b.setLabel("1234");
b.setBounds(30, 100, 80, 30);
add(b);
var b2 = new Button("1234");
b2.setLabel("1234");
b2.setBounds(30, 200, 80, 30);
add(b2);
setSize(300, 300);
setTitle("This is our basic AWT example");
setLayout(null);
setVisible(true);
}
public static void Foo()
{
new AWTExample1();
}
}
}
} |
Not relevant
The text was updated successfully, but these errors were encountered: