The rules are spread out across many different places, and the rules have changed overtime, so I honestly have no idea where to point you.
(also, I'm questing myself if no necroposting is a rule or not, but I do know that it is discouraged)
@bh (or someone of the snap team), would it be a good idea to write down all the forum rules in a single place that people can refer to?
its not.
I know some people dislike it, but I was just trying to help, and as "(What to do and what not to do on the Snap! forums)" says, its not necroposting really if it adds to the post.
there is a url for rules FAQ - Snap! Forum
I'm not sure how up to date it is though
I know about that, but it is kind of out of date, because there was a rule made about no swearing, but the faq page says it's fine. Not to mention, the faq page does not say anything about the "no off-topic" posts rule (which we're kind of violating right now), and the "no offsite mettings" rule.
I just want to point out that after reading the topic, you were not really contributing to the topic, because you said "I think he means how more modern the blocks themselves, More saturated, more colorful, and cleaner borders." which is basically what @bh was saying that he thinks is ugly, and he was pointing out that trying to make a programming language like what you're used to is not something you should be doing. Plus, you were replying to a post from 2021, and there have been many more posts later.
I'm just saying that it's still necroposting if you're replying to a very old post with a bunch of newer posts in the same topic. To not be necroposting, it has to revive a conversation that wasn't finished, and you probably only should reply if it's been a little more recent (like in the past year), and one of the last posts. Also, it's kind of an unspoken rule that necroposting on a topic you made is ok.
I dont think thats what he was calling ugly. Also gui components have nothing to do with how a coding lanuage works so i dont believe he was was refering to that. Correct me if Im wrong.
Anyways i responded because I had a simmilar problem. But it seems its "outdated". So that's all I have to say.
In a text based programming language, gui components do not matter, because that's up to the editor you choose. However, in a visual block based programming language, the gui is very important, because that is literally how you program in it, through the gui.
Not in terms of textures.
What I mostly hate about flat design is the white background. But also, the blocks just aren't as elegant as textured ones.
Of course the semantics of the blocks are exactly the same in either design.
Blockquote What I mostly hate about flat design is the white background.
Thats what mainly assumed, the white background thing. though I guess the blocks are part of it Aswell
Blockquote Of course the semantics of the blocks are exactly the same in either design.
Yes, that's what I was trying to come across. If as a dev you can make an option to switch, I would appreciate it. Else, that's really my only Pet peeve about snap.
You mean, switch in a script? We do have an option to switch! As for doing it programmatically, that's the sort of thing that Jens claims to be unnecessary, especially since it's generally a per-user choice, not per-project.
rip all the lawyers wanting to talk about a block language with like minded people on the language's official forum
I actually agree with Jens on this one. There's a lot of things I don't agree about his stance on programmatically enabling/disabling things the user could enable/disable programmatically, but this is not one of them
Not switch like the function, switch like switch between gui textures!
Sorry, what I meant was, don't try to see just how close you can get to violating a rule without being banned. And don't look for loopholes; follow the spirit as well as the letter of rules.
That's what I thought of when you said "Don't be a lawyer". I just saw it as a fun way to say that.
Nah I know