Difference between revisions of "Talk:Programming"
From Space Engineers Wiki
Line 9: | Line 9: | ||
:::::At any rate, I keep getting sidetracked when trying to get work done on this. Tomorrow I'm going to try and come up with a list of things that need made to at least act as a rough starting point. [[User:Ketura|Ketura]] ([[User talk:Ketura|talk]]) 14:25, 11 January 2015 (UTC) | :::::At any rate, I keep getting sidetracked when trying to get work done on this. Tomorrow I'm going to try and come up with a list of things that need made to at least act as a rough starting point. [[User:Ketura|Ketura]] ([[User talk:Ketura|talk]]) 14:25, 11 January 2015 (UTC) | ||
+ | ::::: [http://steamcommunity.com/id/DraygoKorvan/] - My profile on steam. --[[User:Draygo|Draygo]] ([[User talk:Draygo|talk]]) 01:02, 12 January 2015 (UTC) |
Revision as of 01:02, 12 January 2015
I'm thinking that for organizational and readability purposes we should split this off into smaller documents, like the API docs for modding. At the moment, this page is pretty overwhelming to look at. We should also make a new category: Programmable Block (or similar) so we can tag overlaps in the API documentation and not reinvent the API wheel for every interface.Textor (talk) 07:09, 9 January 2015 (UTC)
- Agreed. In the official Modding Guide, Keen mentions that they eventually want 3 different types of customization, all of which technically exist now but still need to be completely fleshed out. These three are in-game Scripting (which we just got), workshop-friendly API Modding, and then *.dll modding, roughly in this order from least to most impactful/difficult. At the very least we need things to be divided along those three lines. I'm thinking further divisions could also exist for Mechanics, Guides, and Documentation, which would explain, respectively, What This Is And How to Use It, Changing Things 101, and References, roughly targeting most players, new modders, and experienced modders. This makes about 9 different base articles, with perhaps some satellite in-depth ones as well. Thoughts? Ketura (talk) 09:09, 9 January 2015 (UTC)
- Sounds good. I think tutorials should also get difficulty tags, so we may want to make three tutorial categories: beginner, intermediate, and advanced so that the difficulty of the concepts can be more easily classified and filtered. If each interface was given its own page (which I think they started doing on the API side) we can also have a section for notes, in case any interesting facts or quirks are discovered that are significant enough to justify noting on the wiki page for that entry. I think we can contain everything about an interface on the interface's page, however-- I don't see the need to divide the interface into individual properties, methods, and events. Each one would have little individual information and would be better suited to the main interface article.Textor (talk) 12:00, 9 January 2015 (UTC)
- Agreed on all points. I think first order of business is to get a couple top-level API pages up, something that's got more red links than...something with a lot of red links. Pages like this make it simpler to see what needs to yet be created. Also a page listing the sort of information we can expect to have, that acts as a sort of table of contents. I also have a list of URLs at http://www.spaceengineerswiki.com/Talk:Programmable_Block that can be referenced to see the sort of stuff we'd like to go over.
- Sounds good. I think tutorials should also get difficulty tags, so we may want to make three tutorial categories: beginner, intermediate, and advanced so that the difficulty of the concepts can be more easily classified and filtered. If each interface was given its own page (which I think they started doing on the API side) we can also have a section for notes, in case any interesting facts or quirks are discovered that are significant enough to justify noting on the wiki page for that entry. I think we can contain everything about an interface on the interface's page, however-- I don't see the need to divide the interface into individual properties, methods, and events. Each one would have little individual information and would be better suited to the main interface article.Textor (talk) 12:00, 9 January 2015 (UTC)
- There really needs to be like a wiki IRC or something. Ketura (talk) 07:13, 11 January 2015 (UTC)
- Like steam chat? We had a group of people working on importing and creating API documentation but then they just dropped the project suddenly. --Draygo (talk) 12:02, 11 January 2015 (UTC)
- Steam chat could work. Is there a steam group already set up for wiki editors? That sort of thing could work nicely for more than one thing.
- Like steam chat? We had a group of people working on importing and creating API documentation but then they just dropped the project suddenly. --Draygo (talk) 12:02, 11 January 2015 (UTC)
- There really needs to be like a wiki IRC or something. Ketura (talk) 07:13, 11 January 2015 (UTC)
- At any rate, I keep getting sidetracked when trying to get work done on this. Tomorrow I'm going to try and come up with a list of things that need made to at least act as a rough starting point. Ketura (talk) 14:25, 11 January 2015 (UTC)
- [1] - My profile on steam. --Draygo (talk) 01:02, 12 January 2015 (UTC)