ShowcaseThat could be a good idea. HolySpirit (http://fr.sfml-dev.org/forums/index.php?topic=7513.0) and Ovid The Owl (http://en.sfml-dev.org/forums/index.php?topic=370) would also be nice candidates, I'm sure there are more.
When I check out a new library or engine out, I want to see where it has been used before. So I really think you need a Showcase section on the site. Not a wiki, but a personal selection of say 4 of the best projects you've seen that have used SFML. I think something like ATOM ZOMBIE SMASHER (http://en.sfml-dev.org/forums/index.php?topic=4024.0 (http://en.sfml-dev.org/forums/index.php?topic=4024.0)) would be awesome as a feature item.
Bug: It relies on the browser's default styles having a white background.I'll fix it this evening.
Bug:I already noticed that. I have no idea why it doesn't work, maybe a Doxygen bug?
Inheritance diagram for (...) doesn't seem to work. I'm using Chrome version 26.0.1410.64 m on Windows 7
JS Error: "toggleVisibility is not defined "
I think it would be great if we could navigate between the pages of the tutorial (with a simple link to the next page)Is it really needed? The tutorials are really independant, it's not as if they had to be followed in order.
and if there were some buttons to go up in the page in the doc/tutorial pages (it's not very necessary, but it's always great to have some kind of button like that).Could be done. But in this case, where should I put these buttons?
Might probably be a bit bigger though... And as soon as we have the "simple & fast multimedia library", we could include thatThis was a quick and dirty update. I'll improve it later. That would be great if I could integrate the website's banner directly.
SummaryWhy not ;)
I think that instead of "Welcome to the SFML website", you should put a short description about what SFML is. For example: "SFML is a Simple and Fast Multimedia Library that provides a solid foundation for developing games and multimedia software." Then you can give your 3 catchy points about multi-media, multi-platform, etc.
ShowcaseThe main menu on the website is already full, I can't add new sections (bad design, I know...). So I don't know where such a section would go. I guess it wouldn't be visible enough and kind of lost, on the wiki. Suggestions are welcome :P
When I check out a new library or engine out, I want to see where it has been used before. So I really think you need a Showcase section on the site. Not a wiki, but a personal selection of say 4 of the best projects you've seen that have used SFML. I think something like ATOM ZOMBIE SMASHER (http://en.sfml-dev.org/forums/index.php?topic=4024.0) would be awesome as a feature item.
QuoteYou mean, a list of people who say that SFML is great? I don't think this kind of stuff adds value to the website / library. Unless the quotes are from popular software developers / projects, but I have nothing like that to put on the website :P
Would be nice to see a quote from someone about SFML, maybe in the showcase?
Your forum avatar still has the old logo; so you might want to update that. Also the flattr page is still using the old logo.Done.
A bug I found is if you make your browser's width smaller than the minimum width of the site the horizontal scroll bars will appear correctly, however if you scroll to the right the green banner at the top will only stay the size of the browser window, basically the green banner needs a minimum width.Good catch, I didn't notice that.
Laurent, you really put a lot of effort into the Graphics tutorials! Nice work!Hopefully they will now answer most of the common questions asked on the forum, especially about vertex arrays, views and the new rendering API in general.
Maybe you could add again the symbols for the modules in the tutorial overview.I haven't found a consistent set of icons that all look good. Hum, maybe it's cleaner without them.
I'll try to improve the banner, this one was just a quick and dirty replacement.I guess a different banner might already give a better feel.
Or I could make the whole website blue, that's just one value to change in the CSSnooooo, I like the green so far. :)
I just had another idea while looking at the tutorials; it would be nice to have permanent links to the different sections in the tutorial.I started to do it and had style problems (anchors and links use the same HTML tag). But I guess it could be solved easily by using a specific CSS class for anchors. I'll see what I can do.
(anchors and links use the same HTML tag)Anchors rely on only the id attribute, which can be used on almost any tag.
Anchors rely on only the id attribute, which can be used on almost any tag.Ah, thanks. Last time I used HTML anchors was... really a long time ago ;D
For example <h2 id="foobar"> is where you will end up on somesite.com/page.html#foobar.
Regarding the main menu problem: "Docs" and "Tutorials" could be packed into "Help" which shows a page with further links. "Forum" and "Wiki" could go into "Community", again with a page containing links to the two.This is exactly how I started, but I didn't like the result. I ended up with almost empty pages.
I'm kinda missing a feature list. If you send a new user to the website and ask him to answer the question "What is SFML?" he won't be able to properly answer it, since he can't get any information on what SFML really is. ;)
Where can I find a list of features for this library?
there's nothing on the website (that I can find) that says what SFML is and what its features are.
I hope that people will know what SFML is before visiting the website. And the homepage says that SFML is a C++ library that deals with graphics, audio, network and windowing. I think it's enough to get the feeling of what SFML does. Details are in the documentation and tutorials.;)
I hope that people will know what SFML is before visiting the website. And the homepage says that SFML is a C++ library that deals with graphics, audio, network and windowing. I think it's enough to get the feeling of what SFML does. Details are in the documentation and tutorials.
The main menu on the website is already full, I can't add new sections (bad design, I know...). So I don't know where such a section would go.I think you should rearrange the menu items, according to their relevance and the frequency they are clicked. For me, the important ones are Tutorials, Doc, and Forum. Especially the latter two are constantly required, if you actively use SFML. License is secondary, one usually looks at it only one time. Download is only relevant each time a new release happens, or not at all, if you use the Git revisions. Wiki and Bugs are of medium importance.
Supported formats... is there any major format that is not supported?MP3 for example.
I mean, listing image/sound/fonts formats feels like we're back in the 90s. Now it's a basic feature that every library has.Maybe, but it still saves people from searching everywhere or asking in the forum. And the feature list would not only be about the formats. One would get a detailed overview of the library's capabilities, without skimming through the whole documentation. As mentioned, it is a good starting point to decide whether SFML is suitable for a project.
I suggest to merge rarely used categories. For example, you could make an item Overview or similar, which includes Features and License.Let's first see if new categories are really needed, and then we can decide where to add them.
MP3 for example.I mean free formats. Which is the maximum that a free library can support.
Maybe, but it still saves people from searching everywhere or asking in the forum.I think most people will just assume that it works, and come to the forum only if something doesn't work as expected. And it's if they want to know, they don't have to search everywhere, just in the doc of the loadFromfile functions ;)
One would get a detailed overview of the library's capabilities, without skimming through the whole documentation. As mentioned, it is a good starting point to decide whether SFML is suitable for a project.I really think that the tutorials index is a good summary of the important features. I couldn't do better if I created a features page.
I mean free formats. Which is the maximum that a free library can support.It's not obvious though. FFmpeg is a free library and supports decoding MP3/H.264/tons of other non-free codecs. So it's not obvious SFML doesn't support MP3. Also, does SFML support PPM? I don't know. But I'd like to, seeing as I have some PPM images that I generate. So I'm not even sure what free formats the library supports.
I know, you'll reply that it may not be obvious to everyone ;)
But it's also a really non-obvious place to look for features. If I wanted to know SFML's features, I would certainly not think of looking at the tutorials. And even if I did, I'd still prefer a more succinct yet detailed list.QuoteOne would get a detailed overview of the library's capabilities, without skimming through the whole documentation. As mentioned, it is a good starting point to decide whether SFML is suitable for a project.I really think that the tutorials index is a good summary of the important features. I couldn't do better if I created a features page.
Ok ok. I'll think about it :PDon't only think about it, do it! Most of the pros are already said...
Not all combinations between the dropdown fields are possible, so the dialog would have to account for that.Depending on which architecture is selected the items available for the compiler shall dynamically change.
Using PHP would require to reload the page on every action, which is not an option.I was thinking of PHP only determining the OS with the User Agent String, so that the page at least suggests the aim operating system.
I was thinking of PHP only determining the OS with the User Agent String, so that the page at least suggests the aim operating system.Ok. But I still think it's unnecessary, I assume people know what OS they use ;)
The only thing I would suggest is that you put what SFML stands for on the front page (or in the title bar) for brand new visitorsWe're trying to put it in the logo, and/or I'll put it in the home page too.
Great, I noticed this was fixed! However, new bug I noticed now:QuoteBug: It relies on the browser's default styles having a white background.I'll fix it this evening.
<h2>, <pre> and class="title" relies on the browser's default styles having black textFixed.
- Fixed all the CSS bugsNope, though I think it hasn't been reported yet.
Isn't it just because the vertical scrollbar appears on some pages (and thus pushes everything to the left) and not on others? :PNow that you say it... ;D
I have a bug to report. Whenever you search up sfml tutorials and click on the URL: www.sfml-dev.org/tutorials I get a forbidden access error. I'm on my iPhone right now so I don't know if it's an iOS related problem.
Yeah, you need a much nicer 403 and 404 messageLike what?
The new forum bar looks pretty cool, too -- I like the combination of green and blueThanks. It's not finished, I'll try to make it even better.
Will you use a blue bar on the website too? I like it much better than everything in green.Just the bar? Or replace every green thing with blue? :P
QuoteYeah, you need a much nicer 403 and 404 messageLike what?
The URL you requested was not found on this server.
Try our home page(link), or our search engines(link) - or use one of the other links on the left hand navigation.
Will you use a blue bar on the website too?I tried your suggestion. Although the green logo on blue bar looks good, the rest of the website looks strange. I agree that green everywhere is not fun, but it still looks better.
By default, entities are positionned relatively to their top-left corner; we'll see later how to change that with the 'origin' property.
In the tutorial on Transforms, the word 'positioned' has an extra n.Thanks, it's fixed.
By default, the sprite is positionned/rotated/scaled relatively to its top-left corner, because it is the local point (0, 0). But if we change the origin to be (5, 5), the sprite will be positionned/rotated/scaled around its center instead.
"Otherwise bas things may happen, like reading incomplete variables, or ignoring useful bytes."
Did you change something in the last few days?Nop.
On IE, the layout on the main page is totally upset (only "Home" is visible), and the blue forum bar doesn't appear. Can somebody reproduce that?With IE 10 everything is fine for me.
Can we have links to the next tutorial page? I think we had them in the old website.Why? There's no relation between tutorials, you're not supposed to read them in order like in a book.
The tutorial index is just one click away ("back" in your browser) or two ("top" + previous page in breadcrumbs).But there are always lazy people, and I personally don't like it either if I always have to go some steps back, only, to get to the next step.
But there are always lazy peopleMe included ;)
I personally don't like it either if I always have to go some steps back, only, to get to the next step.But at least, this way people can choose what they want to read next. And, considering the time to do one click compared to the time to read one tutorial, I don't think this is a major issue...
In Sound and probably in all classes docs if you click on inherited and not overridden member you are taken to original class page even though inherited class lists all inherited members and their descriptions.That is the intended behavior. Doxygen only duplicates brief descriptions, but not detailed descriptions.
please, at least make the URLs more friendlyCan you explain what you mean? In my opinion they are already quite friendly.
But maybe you could remove the .php extension.What difference does it make?
QuoteBut maybe you could remove the .php extension.What difference does it make?