Difference between revisions of "User talk:VariousMetals"

From Kerbal Space Program Wiki
Jump to: navigation, search
m (Stupid question: idea)
Line 33: Line 33:
 
:The hierarchy of the Parts lists has been bugging me for a while too. I've been mainly focused up until now on just completely filling out the Parts page to include at least one instance of every currently implemented part. The reason I'd been dividing up hybrid parts into multiple tables and moving around parts between tables was to include as much relevant information in them as possible without messing up the table format or wasting space. So in the case of the "modular" wings, I wanted to preserve the already compiled information about the dimensions of those wings, and put the wings with no exact dimensions into a different table. In the case of all the "hybrid" parts, I started including them in multiple locations because I wasn't sure where to put them, and because it was impossible to include them in a single table without either: giving each one its own new table, including an awkward figure in parenthesis or a new column somewhere in the table for the information, or just putting the information in a footnote or leaving it out entirely.
 
:The hierarchy of the Parts lists has been bugging me for a while too. I've been mainly focused up until now on just completely filling out the Parts page to include at least one instance of every currently implemented part. The reason I'd been dividing up hybrid parts into multiple tables and moving around parts between tables was to include as much relevant information in them as possible without messing up the table format or wasting space. So in the case of the "modular" wings, I wanted to preserve the already compiled information about the dimensions of those wings, and put the wings with no exact dimensions into a different table. In the case of all the "hybrid" parts, I started including them in multiple locations because I wasn't sure where to put them, and because it was impossible to include them in a single table without either: giving each one its own new table, including an awkward figure in parenthesis or a new column somewhere in the table for the information, or just putting the information in a footnote or leaving it out entirely.
  
I'm still not sure about the best format for the Parts page, but as for the specific examples you mentioned, feel free to change them if you want, and anything else you notice. For the tail connectors and service bays though, I still think they're fine where they are, because they seem similar enough to the other parts in their tables. I'd recommend just renaming "nose cones" to "aerodynamic cones" and "cargo bays" to "cargo bays/service bays" instead of putting them in separate tables. [[User:VariousMetals|VariousMetals]] ([[User talk:VariousMetals|talk]]) 23:18, 8 June 2015 (UTC)
+
:I'm still not sure about the best format for the Parts page, but as for the specific examples you mentioned, feel free to change them if you want, and anything else you notice. For the tail connectors and service bays though, I still think they're fine where they are, because they seem similar enough to the other parts in their tables. I'd recommend just renaming "nose cones" to "aerodynamic cones" and "cargo bays" to "cargo bays/service bays" instead of putting them in separate tables. [[User:VariousMetals|VariousMetals]] ([[User talk:VariousMetals|talk]]) 23:18, 8 June 2015 (UTC)
  
:the "Parts" page has grown fat, loads slowly, and maybe some category-template should be blanked temporarily for updating. Dividing to subpages have some difficulty as some parts have no even link to its table from its real category (example: LES). We should economize the repetitions.
+
::the "Parts" page has grown fat, loads slowly, and maybe some category-template should be blanked temporarily for updating. Dividing to subpages have some difficulty as some parts have no even link to its table from its real category (example: LES). We should economize the repetitions.
  
:I reckon that, if a group of parts worthy for a separate page (and the service bays and the tails have such a different purpose), worthy for a separate table. And as all the wings - independently from their modularity - have same purpose, and the winglets have a different one (although, they can be used for building complex wings too). I don't believe if the fuel holding wings should be appeared among the fuel tanks, as no one use it for primarily, and even they are empty as default. - [[User:NWM|NWM]] ([[User talk:NWM|talk]]) 21:18, 9 June 2015 (UTC)
+
::I reckon that, if a group of parts worthy for a separate page (and the service bays and the tails have such a different purpose), worthy for a separate table. And as all the wings - independently from their modularity - have same purpose, and the winglets have a different one (although, they can be used for building complex wings too). I don't believe if the fuel holding wings should be appeared among the fuel tanks, as no one use it for primarily, and even they are empty as default. - [[User:NWM|NWM]] ([[User talk:NWM|talk]]) 21:18, 9 June 2015 (UTC)
 +
 
 +
:::The parts page has the same problems as the game itself. The "sort by function" format of the in-game parts menu hasn't changed since back when there were only a few available parts (namely, parts are only divided up into Pods, Fuel Tanks, Engines, etc., and each part only appears as an image until mousing over it) Recently, other filter options were added that sorted based on module, tech level, etc., rather than just a subjective singular arbitrary "function".
 +
 
 +
:::A while ago, I pitched the idea to make all of the tables on the parts page expandable and collapsed by default. That's still an option, and I'm currently working on something over [[User:VariousMetals#new stats table header|here]] to standardize all of the tables and make them collapsible and list the relevant modules in addition to primary function.
 +
 
 +
:::Alternatively, what if we formatted the parts page to be the same as the in-game menu: a page occupied exclusively with a grid of the images of the parts and minimal information, that would load additional information upon mouseover? The benefit of doing that would be that we wouldn't be restricted by having to fit every part into a tabled format any more, so each part could have its own box. In fact, since we already have a /Box for every part, all that we'd need to do is make that appear. We could make it so the stats tables are used within their own pages rather than all in the one parts page.
 +
 
 +
:::Actually, wait, that could work really well. I'm gonna go get started experimenting with that right now. [[User:VariousMetals|VariousMetals]] ([[User talk:VariousMetals|talk]]) 13:18, 10 June 2015 (UTC)

Revision as of 13:18, 10 June 2015

Math problems

Hi VariousMetals, yep you are right that the math-tag doesn't work properly too. For example {{Thrust}} also doesn't work. Did you get the same error when you tried it in your edit? — xZise [talk] 14:24, 14 May 2015 (UTC)

I have next to no experience with wiki markup in general, so I spent a fair amount of time wondering why the only thing I wrote that would actually render was . The error message was just "PNG conversion failed", so I assume it's related to all the other file problems and it'll work again once they get fixed. VariousMetals (talk) 18:43, 14 May 2015 (UTC)
Here's a thought: since the migration issue might not be getting fixed anytime soon, we should create "Category:File problems", and list all the pages that need to be updated once the file problems get solved.VariousMetals (talk) 18:57, 14 May 2015 (UTC)
Huh that math-thingy worked. I'm also not sure why we need a category. Hopefully when Squad fixes the issues with this server images should work like before so that we don't need to solve any file problems. — xZise [talk] 10:49, 15 May 2015 (UTC)

Moved stats table

I have moved the stats tables as you suggested and by that also your note removed regarding the structural fuselage, but not because I don't agree but just because I didn't know where to leave that note and just want to finish something first before I handle that issue. So if you want you can go ahead and move it to another stats table or suggest something in the talk page. Just want to inform you here so that this part doesn't get lost. — xZise [talk] 14:06, 28 May 2015 (UTC)

Move help

Hi, if possible it would be nice when you suggest a move to help prepare it. For example if you want to move A to B and B doesn't exist yet, create a redirect to A and update the pages which use A to now use B. So that when I move it I only have to move it and not move any references.

Of course this should only happen on obvious suggestions and when there should be no redirect from A to B (e.g. because it's an internal template). — xZise [talk] 14:18, 8 June 2015 (UTC)

Thanks for moving the page. I had left the links as is because I wasn't really sure whether replacing the original links would make it easier to move the page, and I was worried that it might make it more difficult if I somehow did something incorrectly and it had to be reverted. I'll add the links and redirect in the future. VariousMetals (talk) 14:57, 8 June 2015 (UTC)
Especially if there are many links it's a bit tedious and unfortunately the MediaWiki doesn't automatically replace references. — xZise [talk] 16:09, 8 June 2015 (UTC)

Stupid question

Sorry, if you find the next a bit annoying, and not coherent, but I am drunk at this moment (love is suck: promising heaven, but opens the gates of hell), and I am not a pleasant person anyway. But before think I am JERK, worth to know, you are one of the few editor, whom I admit, worth to cooperate (Yes there are some, like kspjaptrans, mowaw...), and thinks about many cases about the wiki like I do.

According to the latest editons: don't you feel urge to put the cabins into the "monopropellant tanks" template as they holds some monopropellant?

The parts table system worked by classification of the main function. The tails are not practical in role of nose cones, and the services bay almost useless in cargo bay role (separate table). No one put a great wing for using a fuel tank! (In this case the landing cabins are monopropellant tank, and the small landing gear is an illuminator. The "non-modular" wings can be built together with the set of the modular wings, but not useful as winglets - as they are used to stabilize the rockets. The resource detectors separation from the detectors is acceptable, as they mainly used for another purposes.

Long story short: some kind of reconsideration is needed about this theme...

Yours sincerely - NWM (talk) 22:08, 8 June 2015 (UTC)

The hierarchy of the Parts lists has been bugging me for a while too. I've been mainly focused up until now on just completely filling out the Parts page to include at least one instance of every currently implemented part. The reason I'd been dividing up hybrid parts into multiple tables and moving around parts between tables was to include as much relevant information in them as possible without messing up the table format or wasting space. So in the case of the "modular" wings, I wanted to preserve the already compiled information about the dimensions of those wings, and put the wings with no exact dimensions into a different table. In the case of all the "hybrid" parts, I started including them in multiple locations because I wasn't sure where to put them, and because it was impossible to include them in a single table without either: giving each one its own new table, including an awkward figure in parenthesis or a new column somewhere in the table for the information, or just putting the information in a footnote or leaving it out entirely.
I'm still not sure about the best format for the Parts page, but as for the specific examples you mentioned, feel free to change them if you want, and anything else you notice. For the tail connectors and service bays though, I still think they're fine where they are, because they seem similar enough to the other parts in their tables. I'd recommend just renaming "nose cones" to "aerodynamic cones" and "cargo bays" to "cargo bays/service bays" instead of putting them in separate tables. VariousMetals (talk) 23:18, 8 June 2015 (UTC)
the "Parts" page has grown fat, loads slowly, and maybe some category-template should be blanked temporarily for updating. Dividing to subpages have some difficulty as some parts have no even link to its table from its real category (example: LES). We should economize the repetitions.
I reckon that, if a group of parts worthy for a separate page (and the service bays and the tails have such a different purpose), worthy for a separate table. And as all the wings - independently from their modularity - have same purpose, and the winglets have a different one (although, they can be used for building complex wings too). I don't believe if the fuel holding wings should be appeared among the fuel tanks, as no one use it for primarily, and even they are empty as default. - NWM (talk) 21:18, 9 June 2015 (UTC)
The parts page has the same problems as the game itself. The "sort by function" format of the in-game parts menu hasn't changed since back when there were only a few available parts (namely, parts are only divided up into Pods, Fuel Tanks, Engines, etc., and each part only appears as an image until mousing over it) Recently, other filter options were added that sorted based on module, tech level, etc., rather than just a subjective singular arbitrary "function".
A while ago, I pitched the idea to make all of the tables on the parts page expandable and collapsed by default. That's still an option, and I'm currently working on something over here to standardize all of the tables and make them collapsible and list the relevant modules in addition to primary function.
Alternatively, what if we formatted the parts page to be the same as the in-game menu: a page occupied exclusively with a grid of the images of the parts and minimal information, that would load additional information upon mouseover? The benefit of doing that would be that we wouldn't be restricted by having to fit every part into a tabled format any more, so each part could have its own box. In fact, since we already have a /Box for every part, all that we'd need to do is make that appear. We could make it so the stats tables are used within their own pages rather than all in the one parts page.
Actually, wait, that could work really well. I'm gonna go get started experimenting with that right now. VariousMetals (talk) 13:18, 10 June 2015 (UTC)