User talk:Dosvidaniya

From Guild Wars 2 Wiki
Jump to navigationJump to search

Dye Page[edit]

I've updated the dye page with the information I have gathered. Any feedback / criticism is appreciated.

Dye Information[edit]

Dye information contributed in June 2012 comes from my own screenshots. Located here:

The RGB comes from sampling the center-most 36 pixels of the three different material types. The RGB value is taken for pixels within a +/-7 variance (within +/-7 red, +/-7 green, and +/-7 blue) of the center-most pixel. The average is computed for the final RGB value.


Just as a tip, it is possible to move files to new names without having to reupload and mark the old one for deletion. There's an arrow next to the search box and if you put your cursor over it, you can select move. Should make it a lot easier. :) — Rhoot User Rhoot sig.png 16:13, 22 June 2012 (UTC)

Oh, thanks a ton. Dosvidaniya 16:14, 22 June 2012 (UTC)

dye sub-categories[edit]

I think those would more properly be called "Dyes by hue"/etc. rather than "Dye hues", the same way that we have "Category:Skills by profession"/etc. —Dr Ishmael User Dr ishmael Diablo the chicken.png 03:22, 23 June 2012 (UTC)

Upcoming Changes Verification[edit]

Thanks for the help. Before I go and make a mess, I figure I'll get input from those that know what they are doing. I have posted a new copy of the dye page on my sandbox. I'm currently planning on using the following hierarchy and nomenclature; any input is appreciated.

I'm planning on using the Template:Dye infobox to create the dye pages. Do you see any missing information or issues with the template? See any nomenclature issues? (Like the use of parenthesis with the color for conflicting names). Any hierarchical issues? Would it be a good or bad idea to include the individual dyes in the Category:Dyes?

Thanks for your help! Dosvidaniya 04:15, 23 June 2012 (UTC)

That looks good, except for the conflicting names - there should be a space between the base name and the disambiguation, and the disambiguation should not use title case. I've edited your list above to show this. —Dr Ishmael User Dr ishmael Diablo the chicken.png 14:08, 23 June 2012 (UTC)

DPL & Performance[edit]

The performance of DPL frankly scares me. It's 80% of why I won't touch it. Ishy indicated that caching results is spotty. Crafting pages are going to be a big draw for many, I don't like the idea of spotty performance being a component of something that will span 5000+ pages of content that will see heavy use. Can you assure me that DPl will perform without bringing the wiki to its knees? —Torrenal 14:53, 29 June 2012 (UTC)

DPL performance scares me too right now. The caching settings seem to favor updating frequently. The extension to explicitly set the cache time isn't installed. In order to make the current setup work, we need to sub-categorize recipes by discipline. That'd cut the overhead by 800%. I imagine that would cut the load time down to a couple seconds when the page refreshes. I'm not certain how often the cache is refreshed. Maybe that is still too much overhead.
If it is still a big concern, we can just take the raw page data approach. We'd still want to standardize the designs in the same fashion. We could just let contributors hard code everything and replace the listings when the server gets updated. -- Dosvidaniya 15:31, 29 June 2012 (UTC)
I'm fine with raw pages-for now. Right now the drive is for structured content, not for how said content is created. SMW looks to have the advantage there in how it manages data and changes to same. Hang onto the DPL bits, even as sucky as it looks, performance wise, there's a few places I could see safely(ish) leveraging, and can probably get Ishy to check on DPL cache configs for us. —Torrenal 15:40, 29 June 2012 (UTC)