Board Thread:General Discussion/@comment-26692787-20151030123440/@comment-15636815-20151115232222

BentLauridsenDK wrote: Pella, it was also only a suggestions to make the code easier to read and at the same time make it easier for new editors to know where to fill in the needed informations. I know, and I didn't reject your idea. I just said it wasn't my favorite idea, followed by a statement that "my" favorite idea really is irrelevant in this community. :-)

I have also a suggestion regarding rli.

Why not use it in the objective column, so the users can see what they need to build, I just think that the image are more help there than in the reward column. Interesting, and a good point. So far, I've been working on higher priorities before moving to lower. When I developed Reward link and image, the priority was to eliminate typing the same format over and over, and even repeating the items name three times within the complicated format. It does make sense, though, that seeing an image of something to build or of wagons or locomotives to send would be far more valuable. Then again, those images are available both on the contract screen in the game and at the link in the contract list. Then again, so are the ones for the rewards. What we really need is a separate thread where we all can discuss what is really important to us to see on each of the different types of pages on the site before we continue with major modifications that may or may not be valuable. I'll start working on creating stuff for that in a few minutes.

By the way, is it possible for a page to get information from another page.

Ex if I add a building to a contract I was thinking if it was possible for the contract to read thie cost and the passenger output and size directly. Or if I add a wagon then read the wagons information from the wagon page Yes, and no.

There's an extension called Dynamic Page Link that can do the sort of thing you describe. It's not active by default, but Wikia Staff can activate it upon request. Right now, it's not active for us. When deciding whether to grant the request, Staff will want to know that our site's use of DPL is not going to overload their servers. DPL is very expensive in terms of how much processing power and time it needs to do what it does.

I've also been thinking about DPL as a solution pages like "Meadow Buildings", for example. When items are categorized correctly (which they're not, which is something else we need to fix soon), then DPL can find all items within a category and create a page that lists them, or even displays a table with certain information about them. That's similar to what we have now, only it's far better because we never have to update that type of list page again. We simply add a new page for an item, make sure it has the correct categories, and we're done. Instead of updating the big table page, just go to it, and the new item will be there.