Hi,
> Anyone who uses the java-gnome libraries in a GUI-based Java
> application is risking tying that application into GNOME. By contrast,
> if they use Swing or SWT, they can easily port the application across a
> wide range of supported platforms.
Let me point that I can run popular GTK apps
Mark,
[EMAIL PROTECTED] said:
> On Thursday 11 March 2004 18:44, Mark Howard wrote:
> > The big question is: should we switch to CNI?
>
> No.
I agree with Chris 100%. [Or perhaps I should say 110% :-)]
JNI is the standard for portably calling C / C++ from Java. It works
well enough for the jo
> "Elias" == Elias Martenson <[EMAIL PROTECTED]> writes:
Elias> Going CNI-only would severely limit the number of 3'rd
Elias> party component you'd be able to integrate.
You can mix and match CNI and JNI in a single process. This happens
any time you use JNI in libgcj. Maybe you meant to sa
On Thursday 11 March 2004 18:44, Mark Howard wrote:
> Dear Java Developers,
>
> I am writing to you on behalf of the java-gnome project for advice
> regarding a major change we are currently considering. I apologise if
> this is off topic for this mailing list but we really need input and you
> are
On Thu, 2004-03-11 at 09:44, Mark Howard wrote:
> The big question is: should we switch to CNI?
As much as I like CNI, and want to promote gcj usage, and to the extent
that supporting both CNI and JNI is not an option, then I believe that
java-gnome should stick with JNI.
I don't believe there ar
Chris Gray wrote:
On Thursday 11 March 2004 18:44, Mark Howard wrote:
The big question is: should we switch to CNI?
No.
Though I'm obviously in the CNI "camp", I tend to agree.
But I think the folloup-question is: should java-gnome
switch from JNI-only implementation to some kind of dual
JNI-or-C
I think it is a good idea to keep JNI support, but provide
CNI using a hybrid approach.
For example we can replace:
JNIEXPORT void JNICALL Java_org_gnu_gnomevte_Terminal_vte_1terminal_1feed
(JNIEnv *env, jclass klass, jint handle, jbyteArray data, jint length){
BODY
}
by:
NATIVE_METHOD(org.gnu
I'm not a contributor too, but I'm a (quite experienced) java developer.
I just want to subscribe everything Elias wrote on this mail, I
completely agree.
Thanks,
Alex
On Thu, 2004-03-11 at 20:04, Elias Martenson wrote:
> tor 2004-03-11 klockan 18.44 skrev Mark Howard:
> > Dear Java Developers,
Package: wnpp
Severity: wishlist
* Package name: libcommons-discovery-java
Version : 0.2
Upstream Author : Richard Sitze, Craig R. McClanahan, Costin
Manolache, James Strachan <[EMAIL PROTECTED]>,
Matthew Hawthorne <[EMAIL PROTECTED]>
* URL
On Fri, 2004-03-12 at 04:44, Mark Howard wrote:
> The big question is: should we switch to CNI?
My experience is running through some of the java-gnome tutorials, using
gcj to compile 'native executables'. I just used whatever defaults were
there, and from what you say below it is currently jni. I
tor 2004-03-11 klockan 18.44 skrev Mark Howard:
> Dear Java Developers,
>
> I am writing to you on behalf of the java-gnome project for advice
> regarding a major change we are currently considering. I apologise if
> this is off topic for this mailing list but we really need input and you
> are th
Dear Java Developers,
I am writing to you on behalf of the java-gnome project for advice
regarding a major change we are currently considering. I apologise if
this is off topic for this mailing list but we really need input and you
are the most knowledgeable open source java developers; it may als
On Thu, 2004-03-11 at 04:56, Stefan Gybas wrote:
> I'll ask the ftp admins to remove
> libant1.5-java after sarge has been released so Debian packages should
> start to migrate to libant1.6-java.
Just a formal note, that the curren pracitce is that the apps first
migrate to a newer tool, _then_
Isn't it interesting in our Meta-Package project?
Describe Open Source Projects with XML, Part 1
Edd Dumbill, IBM developerWorks
There are many different open source software registries: perhaps the
best known and longest-running of these is Freshmeat, but there are
many more, often meeting more
Hallo Aurélien,
* Aurélien Labrosse wrote:
>at java.util.zip.Inflater.end(Native Method)
Known and reported. See the BTS for the workarounds.
I really don't know, how I can make
#228599: [SUN derived JVM] crash in zip related code
any clearer...
Jan
--
Jan Schulz [
Aurélien Labrosse wrote:
Hi,
I have some trouble using Eclipse, on a Debian Sid.
Software versions:
j2sdk : 1.4.1-6 (Blackdown)
eclipse: 2.1.2-1
kaffe: 1.1.4-2
* Using blackdown jvm :
[EMAIL PROTECTED]:~$ eclipse
Including user settings ~/.eclipse/eclipserc...
Using /home/aurelien/eclipse as de
Hi,
Have you search the archives of this list? I think this was already
reported...
I have some trouble using Eclipse, on a Debian Sid.
Software versions:
j2sdk : 1.4.1-6 (Blackdown)
If I remember correctly, this is specific to that JVM. You could try
installing Sun's version (using j2se-packa
Hi,
I have some trouble using Eclipse, on a Debian Sid.
Software versions:
j2sdk : 1.4.1-6 (Blackdown)
eclipse: 2.1.2-1
kaffe: 1.1.4-2
* Using blackdown jvm :
[EMAIL PROTECTED]:~$ eclipse
Including user settings ~/.eclipse/eclipserc...
Using /home/aurelien/eclipse as default workspace...
Using
Daniel Bonniot wrote:
What is the rationale for /usr/share/ant1.X/lib ? Is it designed for
plugins that would only work with a certain version of ant?
Plugins should work with both versions since the API for them has not
changed. The reason for /usr/share/ant1.X is that both libant1.5-java
and
19 matches
Mail list logo
