JInput migration.

classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

JInput migration.

Pixelapp
Will JInput be offered here at Jogamp?

I don't see it anywhere.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: JInput migration.

gouessej
Administrator
Hi

I spoke about it to Sven last week, he should do that soon.
Julien Gouesse | Personal blog | Website
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: JInput migration.

Pixelapp
Glad to hear that.

The thing is Gouesse if we don't bring it here, then everyone has to get a certificate separately. This can end up costing us upward of 10,000 USD annually.

However bringing it here, no one has to get any certificate. Which makes it virtually free.

That is, going from $10,000 USD to $0 USD annually makes the difference.

You rock Gothel !

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: JInput migration.

Pixelapp
In reply to this post by Pixelapp
Ok, so I found out how deal with two separate certificates.

So, Sven you may migrate JInput to this site for development purposes only. There is no need to sign them anymore.

Yay!.

I guess I'll chat with Endolf (from JInput) to see if we can renew JInput certificates.


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: JInput migration.

gouessej
Administrator
In reply to this post by Pixelapp
Actually, you've forgotten to mention that you can create your own (free of charge) certificate without paying 10000 USD as I have already done since 2007 for my own first person shooter. Secondly, when Oracle left the boat, I explained how to deploy JOGL 1 and 2 by 2 ways:
- put GlueGen and JOGL onto your own server, sign them with your own certificate and use a single JNLP file
- use signed versions or these libraries but use separate JNLP files (one per certificate)

In no way I want to force people to pay a lot of money for certificates but using self made ones (for free) is not the end of the world, you just get a more scary warning; if people trust you, they won't give up installing your application.

I will be glad to see your contributions in JInput with Kinect support but I'm not the bad guy. Don't hesitate asking us some technical questions, here or in the XMPP chatroom but don't assume any of us is against you. I have done lots of efforts to explain to JOGL users how to use Java Web Start, I updated the user guide some months ago (the changes are on Github but maybe not yet online), some contributors added some nice tutorials in the wiki, I cannot force you to read them but you should do so instead of doing wrong suppositions. This community is quite friendly, I don't want to discourage anybody.

If you want to get rid of the scary warning by the way you suggest (JInput signed by Endolf with a "real" certificate), you won't have to pay but he will have to do so.
Julien Gouesse | Personal blog | Website
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: JInput migration.

Sven Gothel
Administrator
In reply to this post by gouessej
On 06/18/2012 11:41 PM, gouessej [via jogamp] wrote:
> Hi
>
> I spoke about it to Sven last week, he should do that soon.

Yes, 'soon'.

The SVN repo cloning to patch the sources
is still something I don't look forward to it.

Explanation:
To integrate JInput to JogAmp we should:
  [1] - retain the build information (JAR's manifest)
  [2] - use our native lib loading
  [3] - like to have a NEWT 'input source'

This would force us to patch the actual software,
so either:
  [a] - clone the official SVN server to our own
        to create branches

  [b] - SVN -> GIT, host ourselves

  [c] - confirm that the JInput git repo PixelApp
        showed is 1:1 bwd compatible w/ the original

I have hoped you (Julien + PixelApp) would deal
with [a] - [c] - i.e. telling me w/ a unique voice,
where our git repo for JInput is.

Since this did not happen, I guess I have to
follow [b] .. for which I have to find time
to voluntarily suffer in this task :)

QUESTION: All JogAmp / JInput users are happy with
          the plan to do: [b] and [1] - [3] ?

Please answer and correct.

~Sven



signature.asc (910 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: JInput migration.

Pixelapp
First. Julien found the correct sources which are

, forget about anything else.

Do not do "[b] - SVN -> GIT, host ourselves" ,I think we don't need to do that. I was thinking of just [a] - clone the official SVN server to our own  to create branches. After all, that was the idea Endolf (from JInput) was happy with.

I repeat, a clone branch will do just fine.

Moreover, to answer your question. I don't like [b]. Do [1] if you like, I don't think much of it. Additionally, [3] I don't know much about it; but I'll say seems like a lot of work and we really don't need it.

In short, we should clone the official SVN server to create branches. And just Sign and Post the current JInput builds. Just two easy actions.

Now let's hear what others like or dislike.
-------- Original Message --------
Subject: Re: JInput migration.
From: "Sven Gothel [via jogamp]"
<[hidden email]>
Date: Tue, June 19, 2012 8:53 am
To: Pixelapp <[hidden email]>

On 06/18/2012 11:41 PM, gouessej [via jogamp] wrote:
> Hi
>
> I spoke about it to Sven last week, he should do that soon.

Yes, 'soon'.

The SVN repo cloning to patch the sources
is still something I don't look forward to it.

Explanation:
To integrate JInput to JogAmp we should:
  [1] - retain the build information (JAR's manifest)
  [2] - use our native lib loading
  [3] - like to have a NEWT 'input source'

This would force us to patch the actual software,
so either:
  [a] - clone the official SVN server to our own
        to create branches

  [b] - SVN -> GIT, host ourselves

  [c] - confirm that the JInput git repo PixelApp
        showed is 1:1 bwd compatible w/ the original

I have hoped you (Julien + PixelApp) would deal
with [a] - [c] - i.e. telling me w/ a unique voice,
where our git repo for JInput is.

Since this did not happen, I guess I have to
follow [b] .. for which I have to find time
to voluntarily suffer in this task :)

QUESTION: All JogAmp / JInput users are happy with
          the plan to do: [b] and [1] - [3] ?

Please answer and correct.

~Sven



signature.asc (910 bytes) Download Attachment



If you reply to this email, your message will be added to the discussion below:
http://forum.jogamp.org/JInput-migration-tp4025238p4025249.html
To unsubscribe from JInput migration., click here.
NAML
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: JInput migration.

gouessej
Administrator
In reply to this post by Sven Gothel
[a] or [b] and [1] [2] [3] is fine for me. [3] is important for me in order to have a full JInput support with a NEWT plugin under GNU Linux to work around the same limitations than the current AWT plugin but without AWT this time. Does Oracle still plan to deliver a new AWT-less Java plugin? [2] is important to ease the use of JInput in JogAmp applications, especially the deployment. Actually, it would not be consistent as is. [a] or [b] would be fine to do what we want.

JInput for JogAmp will be absolutely useless for me if it drives the deployment harder and if I lose keyboard support in some cases.
Julien Gouesse | Personal blog | Website
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: JInput migration.

donn
In reply to this post by Pixelapp
Hi

Is there any plan to support OpenAL Soft? Some GNU Linux distros don't install it by default, it would be fine to have it. Several people spoke about it several months ago but it has not been implemented.
DONN
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: JInput migration.

Sven Gothel
Administrator
On 11/13/2013 07:16 AM, donn [via jogamp] wrote:
> Hi
>
> Is there any plan to support OpenAL Soft?
We already do .. for quite some time.

> Some GNU Linux distros don't install
> it by default, it would be fine to have it. Several people spoke about it
> several months ago but it has not been implemented.

We deploy it w/ JOAL.

~Sven

> DONN
>


signature.asc (911 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: JInput migration.

gouessej
Administrator
In reply to this post by donn
I agree with Sven and I don't understand why you claim that it hasn't been implemented because its native libraries are already deployed with JOAL and I have used them for months. I'm under Mageia Linux 3. I tested under OS X and Windows too.
Julien Gouesse | Personal blog | Website
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: JInput migration.

Rami Santina
Administrator
Hi guys,

Yes would like to see it with NEWT definitely, 
Does this include, input be changed to push instead of poll like its currently in jinput.

used jinput to integrate with SpaceNavigator, having it with newt would clean that code :)

cheers,
Rami


On Wed, Nov 13, 2013 at 11:10 AM, gouessej [via jogamp] <[hidden email]> wrote:
I agree with Sven and I don't understand why you claim that it hasn't been implemented because its native libraries are already deployed with JOAL and I have used them for months. I'm under Mageia Linux 3. I tested under OS X and Windows too.


If you reply to this email, your message will be added to the discussion below:
http://forum.jogamp.org/JInput-migration-tp4025238p4030609.html
To start a new topic under jinput, email [hidden email]
To unsubscribe from jogamp, click here.
NAML

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: JInput migration.

gouessej
Administrator
It's already planned:
https://jogamp.org/bugzilla/show_bug.cgi?id=814

I need to clarify some aspects before implementing this feature.
Julien Gouesse | Personal blog | Website
Loading...