Update of the "official" SFML description

[Sonkun]

I'm packaging SFML, wanna update its "official" description ?

The current one in Debian repositories is:

"SFML is an modern multimedia library offering a wide range of subsystems useful to produce an multimedia app. It offers OpenGL integration for Hardware accelerated Graphics, Windowing and Input support, Audio and Network facilities and supports GNU/Linux MS Windows and Mac OS X."

[Sonkun]

Even if the Thor library hasn't yet an official stable release, it can be done for it too. I need official descriptions for sfeMovie, TGUI, SFGUI and all other library based on SFML 2.0 worth being packaged lol.

[binary1248]

If you want an "official" description of SFGUI, jump on IRC #sfgui and spam Tank with messages until he gives in. If you ask me, I wouldn't have anything against "A modest attempt at providing some form of GUI capability on top of SFML." but that's just me . I don't know about providing an official SFGUI debian package, considering how "incomplete" SFGUI currently is. I never bothered reading their policies/guidelines but I can imagine stuff like this belongs in the experimental branch until it is truly polished. Then again... telling people to just "apt-get install libsfgui-dev" is kind of appealing...

[Nexus]

I'm not very familiar with packages, but I don't know if it's worth packaging Thor package at its current state. A lot of things are expected to change, people shouldn't feel encouraged to use an unstable version or consider it an official release, they currently do better if they follow the Git version until the library becomes more stable.

Or what do you think? What would its version number be anyway?

[Laurent]

The description is still ok.

[Sonkun]

If you want an "official" description of SFGUI, jump on IRC #sfgui and spam Tank with messages until he gives in. If you ask me, I wouldn't have anything against "A modest attempt at providing some form of GUI capability on top of SFML." but that's just me . I don't know about providing an official SFGUI debian package, considering how "incomplete" SFGUI currently is. I never bothered reading their policies/guidelines but I can imagine stuff like this belongs in the experimental branch until it is truly polished. Then again... telling people to just "apt-get install libsfgui-dev" is kind of appealing...

Okay, I'll do that By the way, the current one is: "SFGUI (Simple and Fast Graphical User Interface) is a fast, simple and native C++ GUI library for SFML 2.0. It provides a rich set of widgets and is highly customizable in its looks. The library has been designed with flexibility and extensibility in mind and provides a modern and clean C++ API."

As for "how incomplete SFGUI currently is, no problem", the stable version (1.0) is in the sfml-stable repo while the next version (2.0) is in sfml-development. People are aware when adding my repo that sfml-development contains unstable versions of works based on SFML.

I'm not very familiar with packages, but I don't know if it's worth packaging Thor package at its current state. A lot of things are expected to change, people shouldn't feel encouraged to use an unstable version or consider it an official release, they currently do better if they follow the Git version until the library becomes more stable.

I do understand that (and you already told me btw :p). I agree with you but I meant we could already think of a description so we don't have to do it later, when Thor 2.0 is officially released. Unfortunately, Thor was already packaged before you told me that. However, while I was bringing Thor to Python, I found the snapshot I used quite stable (actually I had no issues at all). Anyways, it's there and might help people discover it, I'm sure they'll appreciate, even if that's not the final API. (The purpose of packaging it was to provide python-thor package too).

[Nexus]

Unfortunately, Thor was already packaged before you told me that.

In other words: It was packaged without asking me

But now I am confused a bit, could you give me an overview about the current state and what you intend to change? Is Thor currently packaged (if so, how is the package called and where can I find it?)

However, while I was bringing Thor to Python, I found the snapshot I used quite stable (actually I had no issues at all).

I mainly meant API stability. What I want to avoid is that Linux people begin to use the package instead of a more up-to-date Git revision, and as a result, people stick to outdated versions and eventually, a lot of unnecessary code porting is required. Unnecessary because they could have used a more recent Git version in the first place. This is a smaller problem once Thor 2 is released, as I intend to avoid bigger API changes from then.