FUZE Showcase Gallery - The "Not a Competition" Competition!
-
@Dave are you saying that if I can get a program of mine on the FUZE player all my friends can see it on their switch?
-
@LinkCraft02 Exactly that. For free :)
-
Wow ok
One more thing when will it be to late to submit a program if it will ever be to late -
@LinkCraft02 The time restriction is only if you want your program to be considered for inclusion in the release application included programs This is an on-going thing - there is no "too late" in terms of getting into the Showcase Gallery! The gallery will be updated regulalry with new accepted submissions.
-
Amazing I love this idea
-
I think this is very cool
-
When does this come out?
-
@LinkCraft02 Can't answer that one yet I'm afraid!
-
Sniff sniff 😢
-
Hey that is a great thing, I love the player idea and am eager to think about a submission.
Just to troll you a bit: Do I need to use tabs?? Two spaces should be more when enough...😁
I live for the idea and am curious to see what can and will be created.👨💻👨💻
-
@mario-bodemann Not a fan of tabs myself and I think that 2 spaces should be enough, but 4 seems to be the standard
-
@pianofire @mario-bodemann it's one keypress instead of two..!
We would allow two space tabs.
-
Will we get more detaills how it works how we can submit our programms
-
-
@petermeisenstein Yes you will
-
@pianofire I knew it ... ;-)
-
@pianofire Thank you.One question is this only a plan or an idea or is this 100 save
-
@petermeisenstein This post wouldn't be here if there wasn't good reason for it to be!
-
Congratulations on the progress that you where ready to announce this, it is exciting news! 😀
Tabs vs spaces
Is it ok to use tabs in stead of 2 or 4 spaces?I'm used to the IDE making the right decision for me when I type tab (when auto formatting is not available for the type of file I'm working on). For example: try typing tab in Visual Studio Code (a free IDE by Microsoft), and you'll notice it places 4 spaces by default. Because of this, I use tab in my Fuze sources, it also makes my life easier while navigating code with arrow keys.
Comments
Under normal circumstances I would prefer that code is easy enough to read, so that comments are hardly required. Comments always risk to be out dated when they describe what the code does (when something changes, the comments often don't change). If reading the could would not explain why it is there, that is a good reason for a comment.However, Fuze is an environment where people may read your code to learn coding, and that does influence my view on this for Fuze a little. But still, I think it's easier to learn from well written code than bad written comments.
So I'm curious about the opinion of the Fuze team on this.
Forwards compatibility
As I mentioned in a separate post, it is currently possible to use bugs in Fuze for functionality. When these bugs are fixed, the games using these bugs, would break.How will the Fuze team approach this scenario?
- Will games be taken offline with updates that break them?
- Will the Fuze Team maintain projects that are handed to them?
- Will the original author be able to submit updates? (and what if this undo's changes under the previous bullet by the Fuze team?)
- Will the original author have any obligation or legal accountability after submitting the game?
License agreement
Couple of questions about the license agreement:- Can it contain my handle in stead of my real name?
- Is it allowed for the author to redistribute his/her/other own content, without the permission of FUZE Technologies Ltd.?
- What about a remake of a game that was released under an open source license (for example the MIT license), would it be ok to submit such content under this license?
-
Count me in.
Hopefully you can update because all my stuff is always half done in that I like to add more.
Just can't help myself.
