Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Existing Standards #19

Open
oeed opened this issue Jan 13, 2016 · 30 comments
Open

Existing Standards #19

oeed opened this issue Jan 13, 2016 · 30 comments

Comments

@oeed
Copy link
Owner

oeed commented Jan 13, 2016

To get this repo in a state where it is truely useable we need to have as many of the existing standards/formats/whatevers submitted. If you can think of something missing comment below or make a PR!

@viluon
Copy link
Collaborator

viluon commented Jan 13, 2016

Diffs and patch functionality should be definitely standardized!

@oeed
Copy link
Owner Author

oeed commented Jan 13, 2016

Didn't we already sorta discuss diffs in #1?

@oeed
Copy link
Owner Author

oeed commented Jan 13, 2016

...being?

@oeed
Copy link
Owner Author

oeed commented Jan 13, 2016

Don't really get what it has to do with standards though.. does it save the difference to a file?

@viluon
Copy link
Collaborator

viluon commented Jan 13, 2016

@oeed it's the generated difference file displayed when viewing a commit which shows which lines were added/removed. You can also see it when you edit a file in Sublime, right click and click on "Show unsaved changes".

@viluon viluon added the meta label Jan 13, 2016
@viluon viluon changed the title Suggestions for missing existing standards or things in need of standardisation Suggestions for Existing Standards Jan 13, 2016
@viluon viluon changed the title Suggestions for Existing Standards Existing Standards Jan 13, 2016
@ghost
Copy link

ghost commented Feb 7, 2016

.nbs noteblock songs?

@viluon
Copy link
Collaborator

viluon commented Feb 7, 2016

Could you link us to software using .nbs please @justsomeoneelseagain ?

@ghost
Copy link

ghost commented Feb 7, 2016

@viluon
Copy link
Collaborator

viluon commented Feb 7, 2016

NoteBlock API was released on 3rd July 2012. While it might very well work on current versions of ComputerCraft, I doubt it will. I didn't look into the code but I suspect it uses coloured cables, which are deprecated now.

@ghost
Copy link

ghost commented Feb 7, 2016

i just searched for a noteblock image format

@ghost
Copy link

ghost commented Feb 7, 2016

i mean audio format

@ghost
Copy link

ghost commented Feb 7, 2016

maybe @lyqyd ´s packman repository format if he agrees

@viluon
Copy link
Collaborator

viluon commented Feb 8, 2016

His nickname is @lyqyd @justsomeoneelseagain 😉

@ghost
Copy link

ghost commented Feb 8, 2016

yes, I realyced it afterwards

@lyqyd
Copy link
Collaborator

lyqyd commented Feb 9, 2016

Yeah, I'd have no problem with that. I don't really have the time/energy to write it up, but I'd be happy to answer any questions on it that the readme in the packman repository can't.

@Luca0208
Copy link
Contributor

Luca0208 commented Feb 9, 2016

we might want to standardize the intendation(Is that a word?) 2 spaces might be good, as that is what the normal edit program uses, someone can change Lua.md if enough people agree

@oeed
Copy link
Owner Author

oeed commented Feb 9, 2016

@Luca0208 Indentation tends to be fair subjective. Some people like tabs, others spaces. 2 spaces works better on the CC screens because the screen size isn't very big, but personally, I find 4 spaces much easier to read in external editors and only use that.

Hence, I'm not sure whether it's worth standardising. It's not something that's causing clashes or anything like that.

@Luca0208
Copy link
Contributor

Luca0208 commented Feb 9, 2016

The big problem comes when someone uses tabs to intend. It just looks awful in CC

@viluon
Copy link
Collaborator

viluon commented Feb 9, 2016

@Luca0208 that is the problem of CC, not tab indent. Few actual developers use the flawed ingame editor. Still not a reason to standardize indentation.

@lyqyd
Copy link
Collaborator

lyqyd commented Feb 9, 2016

Indentation is personal choice, and outside the scope of this project. The standards should be about how programs work or interact with other code/files, not about how they look.

On Feb 9, 2016, at 13:57, Andrew Kvapil [email protected] wrote:

@Luca0208 that is the problem of CC, not tab indent. Few actual developers use the flawed ingame editor.


Reply to this email directly or view it on GitHub.

@viluon
Copy link
Collaborator

viluon commented Feb 10, 2016

Agreed @lyqyd (and actually even with @demhydraz ).

@viluon viluon added the todo label Feb 10, 2016
@viluon viluon reopened this Feb 10, 2016
@viluon
Copy link
Collaborator

viluon commented Feb 10, 2016

Oops, this isn't a proposal, sorry!

@CrazedProgrammer
Copy link

What about .skch (layered image file from Oeed's Sketch) and .nfa (animation file from NitrogenFingers' NPaintPro) files?
I consider them pretty standard and useful.

@oeed
Copy link
Owner Author

oeed commented Jun 18, 2016

Yeah I don't object to that, sketch files and nfa do seem to be used a bit.

On 17/06/2016, at 7:35 AM, CrazedProgrammer [email protected] wrote:

What about .skch (layered image file from Oeed's Sketch) and .nfa (animation file from NitrogenFingers' NPaintPro) files?
I consider them pretty standard and useful.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@lyqyd
Copy link
Collaborator

lyqyd commented Oct 21, 2016

#59 contains a proposal for adding (a slightly modified version of) TRoR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants
@lyqyd @oeed @viluon @Luca0208 @CrazedProgrammer and others