How do you deploy JInput?

Engines, Libraries and Tools JInput
#1

Hi

Just trying to figure out if the old controller directory and plug in scanning code is still needed.

Endolf

#2

We use jinput directly, not through either webstart nor the LWJGL wrapper, but I voted LWJGL since that’s the closest option.

  • elias
#3

Ok, looks like I missed an option :slight_smile:

Anyone else for any other ways to deploy it? :slight_smile:

Endolf

#4

I wonder if I could ask those using the plugins in a controller directory, which version they are using?, as far as I was aware, from the release of JInput 2, until last night, it was broken (oops), but I could be wrong :slight_smile:

Endolf

#5

i use it thought Slick, which wraps LWJGL, so LWJGL is all hidden :slight_smile:

#6

Excellent, I’ve been doing it since we were at uni, and I can do it again now. Thats one vote for ‘blame Kev’ :slight_smile:

Endolf

#7

I deploy locally, since that’s how you explained it to me a couple of days ago ;D

#8

That would be the one vote for combined packages deployed locally then :slight_smile:

Although I suspect thats what should have been there when Elias voted, so I count his as in there too.

Endolf

#9

I use it directly, as it was explained in the “getting started”, but I plan to use webstart as soon as I understand how to use this animal.