Multiverse Feedback: Cardlist | Visual spoiler | Export | Booster | Comments | Search | Recent activity |
Mechanics | Upcoming releases | Skeleton |
CardName: Filter when viewing Visual spoiler/Cardlist Cost: 0 Type: Pow/Tgh: / Rules Text: Yeah, it would be really helpful when trying to figure out what my green commons in my set lack. Also, I know a little about web development, so I could help you out with this (hence 0 cost :D), so if you're interested I do believe my email is attached to my username in your database. Flavour Text: Set/Rarity: Multiverse Feedback Common |
History: [-] Add your comments: |
Hmm. Like applying the skeleton filters to the cardlist or visual spoiler. Makes sense.
That'd actually be really easy, now I come to think of it. Good suggestion - I'll probably work this into the next update.
As to the idea of contributing to the code: I appreciate the suggestion. I am set up to share Multiverse's code via Github, so it might be reasonable for people to propose changesets that way. I'm not sure my code is especially well documented or able to figure out... while I do try to follow good programming practices like DRY, I haven't exactly been writing it with a view to comprehensibility by others :-S
Well honestly I'd be okay with that, since I've been working at my job recently assembling webpages which use PHP, JavaScript and HTML to render the site, which displays information drawn from MySQL databases, so I'd say as long as you're not doing things in a totally offbeat way I should be able to figure it out. Plus I'll comment out anything that I work through so it will be more useful later. Also it would be cool to be able to have a gatherer-like search function to browse all the cards in the site, but that would ultimately probably be way less useful to most users than the search functionality in the Visual Spoiler/Cardlist. Also, I dunno if you know anything about hacking but if you're going to implement a search function like Gatherer on this site you're going to have to sanitize your inputs or risk someone for whatever reason purging your databases/hacking your website. A potential solution is making sure that the login info is stored on a separate database than cards. I only know a little about security though, definitely not my specialty.
PS: This website is so damn cool.
There is a "search whole site" option, linked from the top of every page. And yes, I do consider security, and I take care to sanitise my inputs already. (Multiverse is written in Ruby on Rails, which makes it very easy to do that.)
I'm glad you like the site :)
FWIW, I think it would be good if it were possible for other people to contribute stuff. I have't had time lately, but in principle it would be good to be able to say "How about blah, and here's a patch to do it" rather than "How about blah, though I know it's a lot of work." And that if you're ever not able to go on devoting time to Multiverse, it's easier for someone else to help out.
I wouldn't worry about the accessibility of the code: I think it's normal that people say "I really wish this was tidy, but unfortunately it's not; you're welcome to play with it if you want, but be warned, you may not want to" :)
Conversely, managing contributions to a project is a lot of work itself, so I think it's up to you whether you'd rather be coding yourself or managing patches :)
Yeah, it would be nice to open up Multiverse for user contributions. I am indeed a bit wary of the overhead of managing patches, but I ought to give it a go.
BTW, Mandroid, one option for looking at a subset of your cardset is: in Firefox, the cardlist page supports multi-sorting. So sort by rarity, then colour, and all your green commons will be grouped together. It's really irritating that this only works in Firefox, but I haven't got around to debugging the third-party table library I'm using.
implemented!
If this is indeed implemented, can somebody guide me? o.O
...Huh. Looks like I only plumbed it in for the visual spoiler, not the cardlist. Sorry about that. Will apply it to the cardlist too.
less implemented than I thought
I think I implemented this a little while ago