Wiki - Content - FS version applicability

[BASys]

Hi Folks

To aid quick recognition of a doc's FS version applicability,
I've created an infobox for placement on every wiki page.

Example in use - FSDev - Wiki - Missions

Please apply to your wiki pages.
For instructions how to, see - Template:Infobox-Applicable-FSVersion/doc

HTH
ATB
Paul

 

[arno]

Great idea Paul, once I finished with the moving I will adapt the pages I made.

 

[MarkkuS]

A good idea!

I assume FSXA (=FSX Acceleration?) also means FSX with SP2 (and not SP1), but I'm not sure everybody knows.

 

[BASys]

Hi Folks

Cheers.
Should be useful.

FSXA (=FSX Acceleration?) also means FSX with SP2

Markku -
Yes FSXA = Acceleration
Acceleration adds extra functionality to FSX.

No doesn't mean SP2.
SP2 adds no functionality, it only fixes issues with FSX.

HTH
ATB
Paul

 

[arno]

So with FSX we mean the normal FSX, but patched to the latest version (SP2 in this case). FSXA is for the Acceleration pack with new features. I think it is not weird to assume users would patch till the latest version.

Also, once all the articles have been edited to add this indication, I guess we can get rid of the categories for the different versions. That does not add so much anymore in that case.

 

[BASys]

Hi Folks

Arno -

So with FSX we mean the normal FSX,
but patched to the latest version (SP2 in this case)

Yes the normal FSX
i.e. RTM, SP1, or SP2.

Also, once all the articles have been edited to add this indication,
I guess we can get rid of the categories for the different versions.

Nooooo.... please.

That'd mean you'd have to open the topic
to find out what it was relevant to.

Users aren't interested
in old inappropriate methods
that don't apply to their FS version.



The most practical solution for all users,
would be to elevate the FS-version sub-categories
to being true top-level 'parent' categories.

I'll close this issue here
and restart in a specific thread,
as it's being discussed in at least two threads.



HTH
ATB
Paul

 

[arno]

Hi Paul,

Nooooo.... please.

That'd mean you'd have to open the topic
to find out what it was relevant to.

Users aren't interested
in old inappropriate methods
that don't apply to their FS version.



The most practical solution for all users,
would be to elevate the FS-version sub-categories
to being true top-level 'parent' categories.

I'll close this issue here
and restart in a specific thread,
as it's being discussed in at least two threads.

I did not find your new thread, so let's continue here. I guess I use the Wiki differently, as I do not find the FS version categories useful at all. Only when you could combine to categories (for example scenery design and FSX) it could be a bit useful.

I think before we continue we need to discuss the structure more, so that we all have the same goal in mind. Now to many different principles are used.

Also I think we should discuss when an article relates to FSX, when the tweak still works (using backwards compatibility of old files) or when it can be applied to FSX specific output as well.

 

[arno]

Guys,

Also I think we should discuss when an article relates to FSX, when the tweak still works (using backwards compatibility of old files) or when it can be applied to FSX specific output as well.

This question is getting more urgent now, as I am working on the Wiki now. When do we tag an article as FSX?

• When it relates to something that can be done according to the FSX SDK?
• When it relates to something that works in FSX (that includes old tweaks that work due to the backwards compatibility)?

I am not sure what my own opinion is on this. The first option is good as it makes people clear when they do something not according to the SDK. The second might also be good to indicate a tweak still works.

Your opinions please.