Messages

1

Feature requests / Re: HSL Color Standard

« on: October 19, 2012, 10:25:14 pm »

While you may like it and your idea does make some sense it's totally unpractical, just quoting this took a lot of unnecessary scrolling. I learned to use many quotes in one post in forum debates, when you are in a hard to swallow debate making a post for every single thing only creates spam and lack of control over what you write (in my opinion).

Of course this isn't anything similar to a debate, but it's still nicer to read when stuff like this is in the same post. The new quote is the one that implicitly marks the change in subject within the post.

If this becomes the policy of this forum, I'll follow it.

But I think that this way of posting also has advantage for moderation.
The moderator can then remove the posts with flames, and keep the ones with usual discuss.

I don't know how the forum engine works, but maybe this would also allow to split threads.

2

Feature requests / Re: HSL Color Standard

« on: October 19, 2012, 10:18:48 pm »

I am young and ignorant in regards to this, if there is anything I should learn to not have an issue like this again happen with my code I'm willing to learn.

Just have a look how other people provide their code.

For a project, usually it's recommanded to add a header in every source code file.

Some Debian packagers will also ask you to add a text file information for every single images, not only tell in the readme file that all images are released under the foo license.

But most of them are not that extremists.
It seems for example that the Debian SFML packager didn't said anything about sounds and images in SFML.

One day a Debian packager even asked me to add a licensing header in the README file!
This was very surprising to me because I don't see licensing information in most free softwares and libs.

Anyway, usually the header in every source file is enough.

For wikis, just see at the bottom of the pages.
Even then you can usually provide your content with alternative conditions.
If you do so this usually means that someone can choose between the default wiki conditions OR the one you added at the beginning of your code.
But sometimes it may also replace it, so people can only take your content with your conditions, and not the one from you.
Sometimes the wiki forbids another conditions from the authors.

Wikipedia doesn't allow other conditions than the default one.
Rosettacode allow contributors to provide alternative conditions.

3

Feature requests / Re: HSL Color Standard

« on: October 19, 2012, 10:18:28 pm »

Last time I checked exploiter was not your student or employee..

Yes, but it's requested to stay polite and friendly.

4

Feature requests / Re: HSL Color Standard

« on: October 19, 2012, 09:59:52 pm »

No, this is not what I meant.
I mean when there are real formating errors. Like different levels in the same block of code, or real inconsistency. (There was some in the HSL piece of code.)
The point is to keep code readable, not to change the style of the original author.

This was my bad, it was my first time trying to put something into the wiki and after two hours of trying I just gave up. I just checked it and saw that eXpl0it3r took the time to fix it while I had left my page untouched for over a week, thanks and sorry for the inconvenience.

Don't worry, wikis are made for this.
Just dump your draft, and don't loose your time.
Someone will correct if it needs so.

5

Feature requests / Re: HSL Color Standard

« on: October 19, 2012, 09:57:04 pm »

This is the same code, only the variable and class names are different.
The implementation is exactly the same, while one could implement this in different ways.
So please...

I strongly support this argument, the formula for conversion is not mine at all, I just took it and put it in C++ after trying to comprehend it a bit. Then again while I get quarks' point for making a big fuss over code copyrights, in my case I currently just don't care if my code gets stolen or used/modified in anyway (18 year old student with no "real" work experience). I just wanted to help out and save others from the headaches concealed if this types of functions.

I just said that I was surprised to read the same piece of code with different author names. I'm not the police.

In practice I know that a lot of people who provide code don't really care, or even don't care at all.
But I also know that there are also a lot of people who care a lot about their code and the licensing they have chosen.

6

Feature requests / Re: Wiki

« on: October 19, 2012, 09:46:30 pm »

You got some strange assumption there.
Just because the browser does show somethings differently won't change the data on the GitHub servers. ^^

The "logout" button is just displayed as an empty rectangle, so I had to try click on it to see that's the logout button.

Maybe the "fork" button is also displayed in a buggy way, and maybe I've clicked on it by accident.

7

Feature requests / Re: Wiki

« on: October 19, 2012, 09:43:41 pm »

If the license is not the same, we should ask the authors for changing the license of their content.

Sure!
It's just for the future entries and for the ones you can't reach. We've already informed every reader of the forum with the other thread I linked, so they know, if they want a different license they have to change it now, otherwise the default license will apply.

We can not assume that wiki contributors will read this message on the forum.

We need a real and explicit approbation of the authors to change their content licensing.

8

Feature requests / Re: Wiki

« on: October 19, 2012, 09:39:10 pm »

Please don't write a post for each quote, it makes it much harder to read and uses a lot of unnecessary space...

my teachers taught us to do so: "one subject = one message"

I'm not the kind to follow blindly what I'm taught. I've tryed with and without, and in practice I can say that this is always the better option.
Sometimes I don't because it's a little bit harder to do, and takes more time, but when I don't it happens quite often that I have to regret it.

I would recommend everyone to do the same, being for emails, posts, and even phone calls.

9

Feature requests / Re: Wiki

« on: October 19, 2012, 09:34:45 pm »

Please avoid acerbic tone.

There wasn't any tone in my sentence I just said the obvious truth.
And if you still didn't get it, I've already changed all the titles and page names, there is nothing to be done anymore and if you had read the linked thread you'd also see that now all the links are broken. So the decision has already been made and executed, thus if you were willing to do it, you're already too late, because it already happened. Get it?

Thank you for your work on the wiki. It is indeed better now.
But the "obvious truth" as you said is that you did that after we started to talk about it.

For the acerbity, I guess you don't talk to your customers or boss or teacher that way.
Please do not do it here too.