Hi, apologies for late notice, as I just seen your message now. As far I know for good train sets are usually SO offer, which seem give best one (that usually with gems though). Otherwise u can see more on this via Train Sets page.
Okay, thank you. I'll try to find one that has the best money per passenger, as I find running out of passengers is usually something that is decently frustrating to me :P
Cool 😎👍🏽, happy to help. If u running out of passengers, I suggest to look at Flags pages which can help u build up more passengers too. Also, if it is possible, you can see Buildings and Special Buildings pages for increase base passengers for your station.
Yeah 🙈. Also cool 👍🏽 I just pass Giovanni 50’s benchmark at moment..... not often I tend to do two contractors at same time, which I am doing again Giovanni and Samuel now.... since I’m like Gio.... yeah might do something else with it 😎.
Sousa324 wrote:
Then what about 2 Ethans and Cornelius?
Hmm that what I was thinking which one I should go for... I could done Ethan 2 or Cornelius but thing is I also used mats for my station i.e. local and IT, storage ... so I thought I might do another HL mats as I rarely used those often unlike old mats I do.
I might pick one of them after I done Giovanni.
You didn't get back to me, so I did some digging and found your DPL test pages. Is there anything in particular that you haven't been able to get working the way you want or improvements you'd like to make?
Hi Flanqer, apologies it slip out my mind to reply back.
Yeah there was, if it is possible but so far I had to do it slightly different way, when I tried get Offer and Infobox item to work in pair...
Each time I tried get Offer and Infobox items (both are Template) which seem doesn’t like each other (otherthan what I done currently). As I can’t seem get it work well as I wanted it to be as.
Whereas Steam Locomotives (Shop) is solely on infobox item which work fine.... Which lead me to see if u give one template to dpl, dpl is happy but if u give two template to dpl, dpl is not happy 🤦🏼♂️.
I don’t know if you can help out on this (All Offer side I.e. Steam Locomotives (Limited), Steam Locomotives (Special/Vintage)), it only areas I been asking people how I can get dpl to like two templates and to make it work (other than what I done currently).
Wait for your reply on this matter, apologies for delay notice.
Yes, I see the problem. It's a matter of finding a way to control how DPL renders the data from the secondary (Offer) templates. I'll dig into it and try to find a solution.
Flanqer wrote:
Yes, I see the problem. It's a matter of finding a way to control how DPL renders the data from the secondary (Offer) templates. I'll dig into it and try to find a solution.
Ah cool, I know admin (TrashTerrier) and I, did many different way doing this of trying to get it to work.
It be a great help if you can find a solution for this, if it can be solve, then definitely can replace current version to new improve version for DPL to like Offer side... as I’m like if I can get one template to work with DPL, so why can’t I get two templates (or more but very unlikely though) work with DPL 🤦🏼♂️. I wait for update on this matter...
I wish I could met you before during my free time and ask you on this.
Also... I'm not sure if Offer DPL version can be apply similar to this way as how Steam Locomotives (Shop) was done. Template:LocoShop.dpl which is front side, so table layout.
Template:Infobox items.dpl.loco.shop which is back side, where the DPL actually search and pull the data from the wiki.... As I'm not sure if you can get two templates (Offer and Infobox items) work in hand as it should be.
I've modified Category:Diesel Locomotives (Limited) Test to format the table closer to what you want. I haven't found a way yet to put lines between multiple Offer rows; that may require more advanced DPL options that I haven't tried yet.
Note that you were getting a blank column because you had specified {Infobox items}:name as a column, and the name= field is blank on all of the Locomotive pages. (DPL automatically includes the page name/link as the first column, so it's not necessary to specify that in the include-page= parameter.)
I rearranged the columns to prevent a glitch that occurs if the second column is an {Offer} field; I also think it's a bit more readable to have all the multirow columns grouped together.
Also I agree with you on making it more readable by having multirow columns grouped together, which I tired to get DPL Offer to do similar thing as DPL Shop did... but I couldn't do it due to DPL didn't like two template, but if I was do it as one template, like Infobox items side only or Offer side only it work fine.... but trying get it to join as one... was pain in butt 🤦♂️... so What I done was only way I could do it, but really I would prefer DPL Offer to have same way how DPL Shop was done.
Do you want me do DPL Offer as DPL Shop as Test version, so you could try it out and fiddle with it to try get it to work?
If you want the set link to be inserted into one of the other columns, like you did with the Notes column on the Shop page, that could be done too, but it'd have to be another {Infobox items} column, not an {Offer} column.
Flanqer you are best! 🤩... okay I didn’t know u could do that for set.
For Notes part 🤔 hmmm okay that what you say, as I see there problem, lol, as I notice if I was going ask u, it would be Offer Limit with infobox items Set into notes, but that isn’t going to work. So I will leave it as it is. 😎, I’m liking this very much 😁.
Now this what you done has given me an idea for date side.... since Limited already got icon, if I can get Special (S) and Vintage (V) as icon then I can removed Type column.... just need to see how I can or get it to work.
Once I got that sorted, then only thing left as you said is
Flanqer wrote: "I also think it's a bit more readable to have all the multirow columns grouped together."
What is left to do, as I’m wondering how can this be done? 🤔 As I also agree on this.
Okay, update, I tried uses similar way what you did for Set... for Date side (so I could remove type) but it didn't work as it made layout goes very wrong ({{Offer.dpl.date}}). As it given me layout I was getting when I tried to get DPL to work with two templates. So I'm seeing that when I try to make Offer DPL to be similar to Shop DPL, it cause the layout to goes wrong... hmmm finding this very annoying.
Unless you got a way to resolve this?
Update... I have remove one template (which I mention in this message) since I can't even get it work right without DPL giving error to it (since it doesn't like two templates).
As I notice way I did for Diesel_Locomotives_(Limited) was done with {{#dpl... format, so I'm like oh shoot.. so I'm not sure if tablerow will work on that?
The main problem you were having with {{Offer.dpl.data}} and {{Offer.dpl.cost}} is that you were trying to add a new row in one column of a row, which can't be done. You could get a similar effect by just putting an <hr/> tag between cost and cost2, but it would mess up the alignment with the values in the Level, Buy, etc columns. A better alternative would be to display both costs on the same line, separated by a "/" or the word "or".
Flanqer wrote:
The main problem you were having with {{Offer.dpl.data}} and {{Offer.dpl.cost}} is that you were trying to add a new row in one column of a row, which can't be done. You could get a similar effect by just putting an <hr/> tag between cost and cost2, but it would mess up the alignment with the values in the Level, Buy, etc columns. A better alternative would be to display both costs on the same line, separated by a "/" or the word "or".
Hmm this I didn’t expect, lol 😂, as this very different to how DPL Shop was done... but look fine to me though 👍🏽.
Just wondering for Offer.dpl.date? What your view on this? (As I just updated test page on this, but I can see where u coming from for date side... which making me want to put it back old way and leave it with type instead 🤔. Also I wait until you have seen the update at Diesel Locomotives (Limited) Test, before I change date section back to old way).
Update - I assume u already seen it, so I have put back old way and deleted Offer.dpl.date, since it could work but as u said I cannot place it since it is one row... hmmmm I wish I could have that sorted 🤦🏻♂️ But it seem it will not work, so type column will stay in still. (I was hoping to remove it so it could be done in date column).
As I notice way I did for Diesel_Locomotives_(Limited) was done with {{#dpl... format, so I'm like oh shoot.. so I'm not sure if tablerow will work on that?
Okay, I have figure it out how to do this... but I now got next issue, erm... how do I make some of column header as non-sorted list? See Diesel Locomotives (Limited) Test page to see what I'm referring to, as I keep getting error for Cost, Buy
, Level, Type, Date and Limit which should be as non sorted column.
There should be a pipe character (|), not a comma, between class="unsortable" and the column name. And you have to do it separately for each column that you want to be unsortable. Like this: class="unsortable"|Cost, class="unsortable"|Buy, ...
class="unsortable" does not remove the table's other classes, so you don't have to set those again on the unsortable columns. You only have to specify the things that you want added or changed, such as column alignment.
Hi, I see it work for < dpl > but when I tried to do same way for parser version, it will not work? as you can see test page. lol.. any reason on this?
The parser version uses pipe characters to mark the start of a parameter, so any other pipes have to be masked like class="unsortable"{{!}}Cost. I think the parser version should only be used if you need the extra features that it allows; otherwise it's better to use the simpler syntax of the <dpl> tag.
Maybe? I'm not sure how DPL count and offset behave when a template is used several times per page.
It might be better to reduce the total number of items to be listed on a page. For example, instead of one page listing all Steam Locomotives, you might divide it into 3 pages for Steam Locomotives with low-, medium-, and high-power (which would likely require adding appropriate categories to the locomotive pages).
Or you might consider removing the Offer data from the table. How important is it for people to see the offer details in a table that lists all the steam locomotives? Although it may seem useful to have all the data in one table, it can also make the table harder to read and require scrolling sideways to see the data. On the Xenoblade wiki we had complaints about quest tables being too confusing and hard to read until we cut them down to just the most important details.
As far I know DPL Shop, DPL Reward does allow Information to carry on without breaking table apart since it used |format.... whereas DPL Offer doesn’t, so it will break it up, what I can see at moment.
I will leave it as unresolved since there isn’t a way to allow it carry on for DPL Offer side, whereas DPl Shop and Reward allow it.
But what I can see DPL Offer has slightly improved to last time when I did it, with all information u gave, 😊👍🏽, thanks.
Since it not 100% perfect to get DPL Offer to be same as DPL Shop and Reward side but it better than before though 👍🏽.
Flanqer, are you in any way familiar with #dplvar?
The page isn't in any way clear about how it works and what it does, but on one of my earlier tests with it it didn't seem to want to pass the variable any further than the same page the variable is set
I don't have any test pages/templates, i know i've tried something (forgot why), failed, and removed everything lol
The reason i'm thinking about dplvar again are the offers AP is working on, as the lists are now, it's a bit pointless to display the cost info for differend offers if they are the same, so i thought maybe dplvar could be set to contain the differend offers, but only pass the last one
I've asked another Wiki Manager who has more experience with DPL. He thinks it should be possible, but he's having trouble getting it to work. I'l let you know if he finds a solution.
After some experiments, we've concluded that it's not possible. DPL variables do get passed to the phantom templates, but the problem is that #if and #switch are processed before the DPL variables, so they compare the names of the DPL variables instead of their values.
The only alternative would be to use Lua instead of DPL, but that would require moving all the data from the templates into one big data page, and would make it more difficult for the average person to make corrections or add new locomotives, offers, etc.
but the problem is that #if and #switch are processed before the DPL variables, so they compare the names of the DPL variables instead of their values.
If i understand you correctly, you tried something like "#if/#switch" before #dplvar, but what if it's the other way around? Like #dplvar:set|variable|#if/#switch, thus moving the #if/#switch inside
That wouldn't work. To compare two variables, they have to be placed inside the #if or #switch. Putting the #if inside a variable would be like putting a postal scale inside the box that you're trying to weigh.
It's currently not possible, because the numbers in those tables don't exist on the set pages (Adore (Set) etc). If you add the data to all of the set pages, in either {{Infobox set}} or a new template, it would then be possible to use DPL to constrruct the tables.
I was afraid of that
I've already tried to create a dpl template for the material part, that would be triggered from a dpl template for the set part, but i keep hitting brick walls
well, I started Ethan back in 2015, and then I stopped due to lack of materials. I restarted back on July 2018 on task number 5, and then, 7 months and a half later, I finished