Comparison SFML vs SDL -> GUI and OGRE3D

[eXpl0it3r]

I know SFML don't support the IOS(iPhone OS). So i thought to use the OIS(Object Oriented Input System) for IOS Touch.

It's iOS and not IOS, that's what got me confused...

But i read in other posts, that laurent is planning for -> "3.0 +" IOS support. It would be nice, but we cannot be sure

Well if you plan on waiting 10 years or so...

What eXpl0it3r probably meant is that these three classes may already know be independent of a window.

Yes!

[FRex]

SFML is under the MIT license so feel free to do whatever you want.

No it's not:

SFML libraries
(...)
Source code is provided under the terms of the zlib/png license

But that's even more permissive.

[noobie]

I try to figure out the sense from your answers.

Well if you plan on waiting 10 years or so...

So you think there will be no changes and i shouldn't use SFML for Input?

What eXpl0it3r probably meant is that these three classes may already know be independent of a window.

So the Input System can be easily separated-> so  use SFML? Separate it by myself and don't wait for changes ...

Or do you agree with me? -> Use SFML for Keyboard, Mouse, Joystick and others for iOS

 

Maybe you know this guy
http://www.wreckedgames.com/forum/index.php/topic,5598.0.html

[eXpl0it3r]

SFML is under the MIT license so feel free to do whatever you want.

No it's not:

Right, I always confuse them since they are quite similar.

So you think there will be no changes and i shouldn't use SFML for Input?

If you look at the SFML 2 history which is over 2 years long, then you can guess that SFML 3 won't be out next month or so. 10y was obviously just a joke (at least I hope so).

So the Input System can be easily separated-> so  use SFML?

You still didn't get it: It's already seperated!
It's just within the window mosule but nobody forces you to use a window.

Separate it by myself and don't wait for changes ...

Or do you agree with me? -> Use SFML for Keyboard, Mouse, Joystick and others for iOS

Do whatever fits your needs, it really doesn't matter as long as you can work with it.

Maybe you know this guy
http://www.wreckedgames.com/forum/index.php/topic,5598.0.html

Never heard of him or OIS.

[N_K]

I don't really get what's the problem with the input system. Although haven't tried it myself, I've seen people using SFML for rendering and using OIS for input handling. OIS is engine/framework independent, you can even use it with text-mode applications if you want.

But, think about it. SFML already has its own input system, designed and developed by the same developer who did the library itself, so unless you need to use some really special input device (PS2/PS3/XBox(360)/Wii controllers, steering wheels, etc.), don't make your life harder and just use the input system that comes with SFML.

[Laurent]

SFML is under the MIT license

zlib license

[noobie]

So, one evening later i looked at the input code

I just changed the lines in the mouse class with Window calls e.g.:

Vector2i InputImpl::getMousePosition(const Window& relativeTo)
{
    WindowHandle handle = relativeTo.getSystemHandle();

to

Vector2i InputImpl::getMousePosition(const WindowHandle relativeTo)
{

so far it seems to work 

[noobie]

Me again!

I still don't get it! Where is the Input System separated from the Window?

I removed all Window classes, picked out the Input methods and made one EventListener class to store the Events per Window (e.g. Ogre -> the RenderWindow), see attachement.

The Window events,Mouse and Keyboard seems to work per Frame and buffered now.
Just have to love the SFML code!

Still don't have a Joystick, but as i see it doesn't need a Window Handle or something?
The Joystick States are updated in the pollEvent loop (per Frame?)?



[attachment deleted by admin]

[eXpl0it3r]

I still don't get it! Where is the Input System separated from the Window?

Yeah we still don't get what you don't get either...
sf::Keyboard, sf::Mouse and sf::Joystick are classes that are not directly connected to sf::Window or sf::RenderWindow, but of course they get compiled into the same library as sf::Window and sf::Event etc.
The functions themself though aren't connected to the window class, you can just take the functions (SFML/src/Window/<OS>/InputImpl.cpp & SFML/src/Window/<OS>/InputImpl.hpp) and plug them into your own stuff without having to write-out hundreds of SMFL code parts you don't need.
Thus the input system (sf::Keyboard, sf::Mouse and sf::Joystick) is separated from the window itself (sf::Window).

[noobie]

see it as a request or improvement suggestion for the current window system if users just want the input system. 
As far as i can see the pollEvent cannot be used without the window Object.

But so far i can live with it (Did it by myself and got it to work with Ogre).

[Nexus]

see it as a request or improvement suggestion for the current window system if users just want the input system.

See what as request? Sorry, I don't exactly see your problem, either.
 

As far as i can see the pollEvent cannot be used without the window Object.

Yes, and as I already mentioned, it doesn't make sense without a window object, since the events are connected to the window. For example, a Closed event fires when the window is closed, MouseMoved event triggers when the mouse is moved in the window, etc.

[noobie]

grrr

I feel like a stupid little piece of scum now. 

My Problem?
- I searched for a good input System for Ogre
- Didnt find a solution to use SFML for Ogre

And now i got it to work with much changes ....

So jesus, what can u not understand what my problem is/was ?

[eXpl0it3r]

Events are something totally different than just plain input stuff and we've many times stated that events can only be used with a window.

If you're requesting to split the sf::Keyboard, sf::Mouse and sf::Joystick into their own small 'input' library or similar, than this is 'okay', although I don't think this should be done to SFML...
If you want a separated library that can handle events, then this is simply not possible, since as Nexus already stated just now and earlier, events are connected to a window.

[noobie]

if there's no way i have to accept it , but i don't want to believe it 

[Laurent]

No way to what? To know if a window is closed, without a window? To know if a key is pressed in a window, without a window? To know if a window gains/loses focus, without a window? ...

You see, all events are connected to a window, there's no event that could make sense without one.

So what exactly would you like to be able to do? Say it clearly (be more precise than "input system") and let's end this endless discussion