Jump to content

Thread:AndersonDG/@comment-12138097-20150224095854/@comment-26009169-20150224220340

From Elite Dangerous Wiki
Unfortunately Gifs won't work (I've tried). Youtube functionality works, but to make it loop it reloads the video and thus is not seamless. Are there any other ways to add the video without using the video tag, a gif, or youtube?

Well, webm is the best way to do it. But I still don't agree that having animated files for the ship would be good as a default.

I agree that Elite makes them very dark, but I would assume that at some point Frontier could provide better looking images similar to what Digital Extremes did for the Warframe wiki. Eventually I'll contact Frontier and see if they could provide us with some nicer looking assets, but ideally I would like to know exactly what kind of assets and in what formats to be asking for before I contact them.

Having assets given to us would be great, but as you said it's what kind of assets that would be good. Having good representation assets for ships is a given and standalone icons for commidities. Another great thing would be to get some nice in-engine images of various mechanics and events, but that would mean that Frontier needs to spend money to do it which probably isn't worth it given the small amount of people checking the Wikia compared to the forums and reddit.

Now as to mobile and older browser support - if those platforms are going to hold back progress then I'm not too interested in supporting them. While I do believe that there should be fallbacks so that they can still view similar content (similar to what I've done with the nav buttons on the main page) I don't want cool features and progress to be stifled just to cater to devices that cannot display certain things. In the future I would like to have features that probably won't be able to be utilized on Mobile or old browsers. For example charts for commodities (example 1 example 2) and item/weapon comparisons (example 1 can be seen in the left table at the bottom).

Not supporting mobile is a no-no. The Wikia works very well in mobile, it is very heavy due to how Wikia works but even so you can get the information and images without missing out on information. For older browser support, i.e. browsers with less than 10% global usage use is something that isn't necessary, but restricting content that isn't accessable by not using scripts or flash isn't a good thing.

Charts for commidities such as the RuneScape ones aren't necessary content but is additional content and as such the article will be fine just without it but adding it would only cause nice content to be added. Having features like that is good, but restricting content such as the ship image being animated without a fallback would be an issue for people who want to know what the ship looks like. It is possible to have overlapping elements in CSS and as such having animated video/image and a fallback image, but that would mean loading both media-files with only one being visible (if JavaScript isn't possible in Wikia)

Sizing the <video> tag with css was my fault - I was playing around with things yesterday and it was easier to do everything with CSS while tinkering with things than to change both the CSS and the MediaWiki page for changes to be displayed. If we do use the video tags the final versions will have width and height placed in the video tag (which appear to be supported according the the documentation I've found).

Well, sizing it in CSS and through the HTML-tag (not recommended) is the same thing. I was more pointing out that one should resize the image/video to the correct size before setting it up for use. Resizing means a loss of content, as the file is bigger than is displayed, and the filesize is larger than necessary, meaning more bandwidth used

To your last paragraph - do you have suggestions? At this point I'm not sure what to implement for the infoboxes other than a bit of styling (which isn't my forte).

Using images to represent certain headings or content would be a nice feature and using iconfonts would be a nice addition to the content. With CSS3 using :hover combined with psuedoselectors such as ::before or ::after is something that's possible to improve the overall style. One can use hover class on one element to show content on another element might be a good feature. With ::before tags one can use .class::before:hover combined with .class:hover to hide and show elements without including multiple elements (hopefully, not tested it)

But if anything having assets given to us by Frontier would be worth a lot more as with consistency and design of the site

Edit: If you check the reddit and hover over the Submit a post you'll see an example of :hover combined with ::before to provide additional content. But ::before and ::after only goes by content provided in the CSS with `content:"text"`-styling

Start a discussion about Message Wall:AndersonDG/@comment-12138097-20150224095854/@comment-26009169-20150224220340

Start a discussion