wanted Implementing STEP-like tables for packs

[CJ2311]

As for right now, all packs use the PackTable Template, which to be honest limits the quantity of information you can put in the guide (such as required DLC, recommended version, etc...)

 

Would it be possible to give pack authors the choice between that template, and one that would be similar to the STEPTable template used in the STEP guide (perhaps with the quality options column removed, since that part does not really apply to packs other than STEP after all)

Or at least, some explanation on how the STEP Table template works so I can attempt to replicate it D:

[z929669]

Both 'Forms' usue unique template sets, and all is constructed using Semantic Mediawiki.The way data needs to integrate precludes the use of user-created templates (unless you know SMW and out SMW config, which only s4n knows really well).

 

I even only mess with the system as little as possible due to the complexity and ease of breaking things, so please just submit these requests and we can eventually address. Project:Data Dictionary describes much of this, but it is a bit outdated (and it also uses its own SMW classes). Pretty complex stuff really.

 

In order to construct the ideal Pack Guide system, we will likely need to rebuild our config under a dev environment and test thoroughly prior to implementing on the production server.

[CJ2311]

  On 3/20/2014 at 2:12 PM, z929669 said:

I even only mess with the system as little as possible due to the complexity and ease of breaking things.

That is exactly why I didn't think of messing around with it, and posted this as a suggestion instead. :)

 

Hopefully it'll be taken into account when packs become official with 2.3.0.

[z929669]

We need some advanced STEP users to 'step' forward and be willing to learn SMW well enough to understand how to revise the system. The only way to do that is to install a VM with effectively a snapshot of our wiki. We may be able to construct a server side instance for dev purposes that uses several sandbox namespaces for independent dev envs to exist, since SMW integrates with the entire wiki (i.e., it is not possible to do sandbox dev on the standard wiki namespaces without disrupting the entire prod system)

[CJ2311]

I'm by no means an advanced STEP user (haven't even dabbled with wikis prior to this one), but if you get me a list of pre-requisites to get a virtual server running and a snapshot of the wiki, I could have a try at it

 

A VM sounds overkill for just learning though, wouldn't something similar to LAMP or XAMPP be enough for that?

[z929669]

You can use whatever means you want to establish a functional MW dev install. Just go out to Tools > Special Pages > Versions to get the list of components/plugins and the versions we are using, then you need to set up a connection to your MW and begin developing in SMW. You don't really need an exact copy of ours, but it would be helpful to configure the same SMW classes that we have configured here.

 

If you PM me and invite s4n to that, then I will defer to him as to how to set up a dev env (or if we can set one up for anyone that is interested on our server)

[CJ2311]

Alright then, I'll start setting up a local install in the next days (getting PHP 5.5 to work on WAMP is gonna be fun ) and I'll keep you informed via PM after that.

[stoppingby4now]

Short Answer: It should be very simple to get the same look and feel in the tables.

 

The STEP tables are nothing more than a template that generates table contents based on results from a SMW query. The same should be true for Packs, which means the "styling" can be setup to mirror the STEP tables. I wasn't involved with the setup of the Pack stuff, so I'm not completely familiar with what was done (yet). Pack look'n'feel should mirror that of the STEP guide though, so it's something that deserves attention.