[SDL] Cut and Paste in SDL

[Jeremy]

Why can't you look past your personal desire for SDL to do only what YOU
want and support the rather trivial functionality that would not only
benefit others but that you could also take advantage of easily as well.
Many games support c&p in their in-game consoles now, which more SDL games
could do if it was added to the core. Sure it's not NEEDED, but nor is it
ever NEEDED. It's a very useful convenience functionality that makes the end
users life easier. Surely you can understand the value of users being able
to c&p into text fields in your game gui, the game console, maybe even your
chat input. Personally it annoys the hell out of me when games don't support
such things for their text input.

I can't speak for linux or mac support, but c&p functionality is pretty easy
on windows. I'd be happy with simple string support, since it is likely the
most common and useful one, though bitmap support should also be easy to do.
I'm asking for an SDL wrapper for basic cut, copy, and paste functionality
through a generic interface, for strings primarily, possibly images. This
isn't something that is going to bloat SDL at all. Support compiling it out
for all I care as well, for the people counting bits.

J

On 1/11/07, Kuon - Nicolas Goy - 時期精霊 (Goyman.com SA) <kuon at goyman.com>
wrote:
>
>
> On Jan 10, 2007, at 11:31 PM, Mattias Karlsson wrote:
>
> >
> >
> > Why must it be part of the core libary and not a add-on, like say
> > SDL_net?
> >
> > Am I the only one who have a nagging feeling that the core SDL
> > library is
> > becoming more and more bloated? Or am I part of a dying breed of
> > developers that think that size realy do matters?
> >
>
> I agree, for me, having a lib as little as possible, doing only what
> I want is my need.
>
> I use SDL as a low level API to access OpenGL in a cross platform
> way. And in our game, C&P is not needed.
>
> It's a feature which is nice, and I think it should be implemented as
> an addon. Or maybe #define CP_SUPPORT, so we could compile from
> scratch without it. (remember what the S in SDL stand for)
>
> Just to clarify, we speak about C&P interaction with the OS right?
> The ability to access OS last copy (or maybe history) and the ability
> to put a new buffer in the OS stack? I think it's not a trivial
> feature, as OS can copy many things as already discussed.
>
> I'm not an SDL coder, but as a user, I can say I want to keep the lib
> as clean and small as possible.
>
>
> Regards
>
> --
> Kuon
> Programmer and sysadmin.
>
> "Computers should not stop working when the users' brain does."
>
>
>
>
>
>
> _______________________________________________
> SDL mailing list
> SDL at libsdl.org
> http://www.libsdl.org/mailman/listinfo/sdl
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.libsdl.org/pipermail/sdl-libsdl.org/attachments/20070111/bc774861/attachment.html