Author Topic: And for my birthday I wish... (Read 6648 times)

model76 · « **on:** February 14, 2012, 03:09:18 am »

Today, the 14th, is my birthday. That means I am allowed wishes, don't you know?

So here is my wish:

That Laurent will work on SFML today.
Implementing the new naming convention would be my preference, and a big step for SFML, but anything would be great, really.

Here is for hoping

Grimshaw · « **Reply #1 on:** February 14, 2012, 06:07:03 am »

Happy birthday man!

Not wishing to bore the hell out of Laurent, but I backup that name change thing!

As a matter of fact, I am changing all my code to the new convention already, regardless of what Laurent does, because it really looks neat !

Anyway, Happpy birthday and please do make a beautiful cake game and share with us !

Laurent · « **Reply #2 on:** February 14, 2012, 08:00:21 am »

Quote

That Laurent will work on SFML today

I work on SFML everyday. Not hard to fulfill

I'm currently very busy with the C and .Net bindings. It takes a huge amount of my free time to upgrade them to the new graphics API, but I have almost finished.

darekg11 · « **Reply #3 on:** February 14, 2012, 10:47:11 am »

Waiting for C release <3

model76 · « **Reply #4 on:** February 25, 2012, 04:41:24 pm »

Quote from: "Laurent"

I work on SFML everyday.

That's good to hear. I wasn't sure since I don't see many changes to the bug/task tracker. I guess every day is my birthday!

I am also glad that you are taking your sweet time with SFML 2, making sure 2.0 will be stellar.
However, I do feel a commit with the new naming convention would be very beneficial to the community.

Laurent · « **Reply #5 on:** February 25, 2012, 04:47:15 pm »

Quote

That's good to hear. I wasn't sure since I don't see many changes to the bug/task tracker

The bug tracker contains major tasks, or tasks added by other people; but there are many other things that don't appear in it and that keep me very busy.

Quote

However, I do feel a commit with the new naming convention would be very beneficial to the community.

Finished to update the bindings today, working on this task right now

Delarock · « **Reply #6 on:** March 01, 2012, 11:44:51 pm »

May I ask if the new naming convention is already up?

Laurent · « **Reply #7 on:** March 02, 2012, 07:51:12 am »

No it's not.

nietaki · « **Reply #8 on:** March 03, 2012, 04:16:05 pm »

Could anybody point me to the "naming convention" you are talking about?

The amount of code I have already based on SFML 2.0 is getting bigger and bigger and I'd like to know the extent to which it will be affected

Nexus · « **Reply #9 on:** March 03, 2012, 04:33:18 pm »

Quote from: "nietaki"

Could anybody point me to the "naming convention" you are talking about?

http://www.sfml-dev.org/forum/viewtopic.php?t=6709

Quote from: "nietaki"

The amount of code I have already based on SFML 2.0 is getting bigger and bigger and I'd like to know the extent to which it will be affected

You don't really want to know the extent. Every single SFML function is affected :twisted:

Basically, it is planned to rename functions to Java style, e.g. GetPosition() becomes getPosition().

Grimshaw · « **Reply #10 on:** March 03, 2012, 05:19:11 pm »

Java-style is C++ style too

almost!

But honestly, it really looks neat. While both naming conventions have their beauty, there are names that look particularly bad in upper case, such as IsSomething(), in my opinion.

If you are using more than a couple middleware in your project, chances are 70% of them are in lowerCase() . And the standard library of C++ is lower too, and that won't change while the minority of middleware in CamelCase can adapt anytime

Cmon, my birthday is coming too ! xD

CyberRascal · « **Reply #11 on:** March 03, 2012, 05:28:50 pm »

Quote from: "DevilWithin"

Java-style is C++ style too almost!

But honestly, it really looks neat. While both naming conventions have their beauty, there are names that look particularly bad in upper case, such as IsSomething(), in my opinion.

If you are using more than a couple middleware in your project, chances are 70% of them are in lowerCase() . And the standard library of C++ is lower too, and that won't change while the minority of middleware in CamelCase can adapt anytime

Cmon, my birthday is coming too ! xD

But the stdlib is in lower_case, not lowerCase.. As is boost. Why do you (SFML dev and users) prefer camel case over the convention used by the stl?

Laurent · « **Reply #12 on:** March 03, 2012, 05:59:28 pm »

Quote

Why do you (SFML dev and users) prefer camel case over the convention used by the stl?

1. it has already been discussed
2. if you want to add something don't do it here, there's a dedicated thread

Thank you

nietaki · « **Reply #13 on:** March 03, 2012, 07:25:18 pm »

Quote from: "Nexus"

You don't really want to know the extent. Every single SFML function is affected :twisted:

Basically, it is planned to rename functions to Java style, e.g. GetPosition() becomes getPosition().

Well the new style fits my preference so I won't complain