SFML 2.0 RC

[tAKi]

Sorry, I don't see how this could be added without breaking API compatibility?

Adding a member to a struct, and an argument with default value to a function doesn't break API compatibility.

So when you say that the 2.0 API should not be broken, you exclude the C API?

[Laurent]

So when you say that the 2.0 API should not be broken, you exclude the C API?

That's a good point. I don't know if I'm going to provide API compatibility for the C API, since its purpose is to be a base for other bindings and not a ready-to-use API for C programers.

But I can also find workarounds (like defining a new function for that extra argument), and clean them in SFML 3.

[kaB00M]

How can I compute fps in 2.0? 
Thanks.

[Hiura]

what I get when I search for 'fps' : http://en.sfml-dev.org/forums/index.php?topic=8223.msg54975#msg54975 searching is fun! Do some.

[Conan]

just tried the RC, looks nice. Just one weird quirk:
i installed it into a custom directory.
however, when i set the PKG_CONFIG_PATH accordingly and try pkg-config --libs --cflags sfml-all
it shows the following:
-I/home/laurent/release/2.0-rc/sfml/SFML-2.0-rc/include  -L/home/laurent/release/2.0-rc/sfml/SFML-2.0-rc/lib -lsfml-system -lsfml-window -lsfml-graphics -lsfml-audio -lsfml-network 

alas, neither my name nor my user login is laurent, so i guess this directory is hardcoded somewhere.

[Laurent]

Yeah, pkg-config files contain absolute paths, they mustn't be distributed. I didn't noticed it because these files were added by someone else.

[Celtic Minstrel]

I was browsing the git repository a little while ago (can't quite remember why) and noticed this. I may be wrong, but I was under the impression that distributing Arial without a licence is not allowed, and that looks suspiciously like distributing Arial.

[Laurent]

Interesting, I never thought about that. I should definitely find a free replacement. It's not clear whether I can take a GPL font or not, though.

[Celtic Minstrel]

Maybe an OFL font? I'm not sure really; I'm not a lawyer or anything.

[eXpl0it3r]

What about Bitstream Vera?
The license states:

Copyright

Copyright (c) 2003 by Bitstream, Inc. All Rights Reserved. Bitstream Vera is a trademark of Bitstream, Inc.

Permission is hereby granted, free of charge, to any person obtaining a copy of the fonts accompanying this license (“Fonts”) and associated documentation files (the “Font Software”), to reproduce and distribute the Font Software, including without limitation the rights to use, copy, merge, publish, distribute, and/or sell copies of the Font Software, and to permit persons to whom the Font Software is furnished to do so, subject to the following conditions:

The above copyright and trademark notices and this permission notice shall be included in all copies of one or more of the Font Software typefaces.

The Font Software may be modified, altered, or added to, and in particular the designs of glyphs or characters in the Fonts may be modified and additional glyphs or characters may be added to the Fonts, only if the fonts are renamed to names not containing either the words “Bitstream” or the word “Vera”.

This License becomes null and void to the extent applicable to Fonts or Font Software that has been modified and is distributed under the “Bitstream Vera” names.

The Font Software may be sold as part of a larger software package but no copy of one or more of the Font Software typefaces may be sold by itself.

THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL BITSTREAM OR THE GNOME FOUNDATION BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM OTHER DEALINGS IN THE FONT SOFTWARE.

Except as contained in this notice, the names of Gnome, the Gnome Foundation, and Bitstream Inc., shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Font Software without prior written authorization from the Gnome Foundation or Bitstream Inc., respectively. For further information, contact: fonts at gnome dot org.

[Laurent]

It looks too limited:

Vera itself covers only common punctuation and the Latin alphabet with some diacritics

DejaVu seems to have a much wider glyph coverage.

[Marukyu]

Speaking of a built-in default font, it would be nice to have an easy way (perhaps some sort of compilation flag) to build SFML-Graphics without including Arial.hpp (or DejaVu.hpp if it's changed to that), without having to manually comment it out everytime. I personally never use sf::Text, as I have my own class that renders bitmap text, so there is essentially >300 KB of useless data in the graphics dll.

[eXpl0it3r]

DejaVu seems to have a much wider glyph coverage.

Oh didn't think about the glyph coverage, yeah this looks good.

Speaking of a built-in default font, it would be nice to have an easy way (perhaps some sort of compilation flag) to build SFML-Graphics without including Arial.hpp (or DejaVu.hpp if it's changed to that), without having to manually comment it out everytime. I personally never use sf::Text, as I have my own class that renders bitmap text, so there is essentially >300 KB of useless data in the graphics dll.

It's one thing just to not include a file and it's another thing to prevent any crash due to the missing file.
Also we don't live in the 90s anymore where every single bit was important, so imho it doesn't hurt to include those 300kb, although some might not like it.
I'm not sure but does it also get included when you link statically?

[Laurent]

Can you tell us why these 300 KB are so important?

[Laurent]

I added an issue on the tracker for the default font replacement.