[Request] Better Export Options and Deck Checker

Hi,

If you make yourself a copy of the deck in the decklist section you can import the deck into it.  After doing that it will show you if your collection has the proper cards for the deck, and if not you can add how many you need to your wishlist on the same page.

Hope that helps,
Jeff

I agree with the exporter, that would be great to be able to export and have a paper trail...

I have worked out a method to get your library into a Microsoft Excel Workbook.  It uses macros and is relatively easy to use.  There are a couple of manual steps that I would be willing to work around if there is interest.

Before I post it (or a link), I would like to hear from the Admin to see if that is OK to do.  This allows you to scrape your inventory pages and capture all the info.  If you (Admin) would like me to send you the workbook first let me know.

Thanks,
-SH

I know this has already been requested.  But I really, really, really want an export feature that contains all information for all cards in my inventory.  For me, this one feature is more important than any other on this site.  I don't want to spend hours upon hours putting all my cards into the site, but then not be able to save that data elsewhere should I so choose.  Pretty please?

Otherwise, awesome site! I love it, thanks for this resource!

Last edited by zotnick (2011-09-05 20:10:53)

I'm merging the threads requesting exporting options, to keep the discussion in one place.

I know this is something many people want, and we shall implement it. It is coming

No, there is only one price stored per card. It doesn't take different editions or special versions (foil etc.) into account.

This request has been on file for over a year. It makes me wonder if the coming soon response is just a front to placate everyone. Looking from a database stand point its a trivial matter to export data into a CSV format. I know this is coming off as a rant and i apologize for that but come on guys the way it reads in the forum is that you dont take the feature requests seriously. there was not an update in over a year and it was only updated when someone requested it a second time.

As a php developer I can tell you it would take about 5 minutes to write an export to csv function, and another 5 minutes to integrate it into the front end. That said, it's probably not priority one for the developers because you can already export your card list using the print option, which is almost as easy to parse as csv.

Me and my shiny new "Deckbox 2 CSV" converter disagree with you.

http://killobyte.com/magic/

I couldn't access your database so I had to write a parser, not just and exporter. Of course I've never seen your codebase, maybe your tools take longer to use. Do you use PHP? In PHP the applicable part for you would be:

public function printCsv() {
        header('Content-Type: text/csv');
        header('Content-Disposition: attachment; filename="Deck.csv"');

        echo 'quantity,name,sideboard'."\r\n";

        foreach ($this->getCardList() as $card) {
            echo '"'.$card['quantity'].'","'.$card['name'].'",""'."\r\n";
        }

        foreach ($this->getSideBoard() as $card) {
            echo '"'.$card['quantity'].'","'.$card['name'].'","YES"'."\r\n";
        }
}

where $this->getCardList() and $this->getSideBoard() return an array of cards.

Anyway, looking forward to seeing what you come up with.

Looks like we're not discussing about the same thing here then .  What you did there is parse a string and inject commas and quotes into it.

This thread is about implementing the backend and UI design for exporting inventories, tradelists, wishlists and decks, for 3 card games, with a user-customizable (chooseable) number of fields that represent card properties. The card data is stored in normalized tables, there are 52 tables that deal with information about cards (both static information and user inputed info like foil flags, editions, condition etc).

show tables where `Tables_in_deckbox_production` regexp '(mtg_)|(wow_)|(whi_)';
<snip>
52 rows in set (0.01 sec)

I really don't want to turn this thread into some kind of back and forth flame discussion, so I'll stop here with the explanation. I don't want to justify the big delay by showing the problem is complex, it's of course not as complex as to take a year to implement . I only replied because these "5 minutes" estimations are 2 orders of magnitude away from a correct assessment, when considering defining requirements, structure, code design, UI, functional tests, back and forth manual testing, improvements and fixes, etc. etc. etc.

So I will stop talking about it in this thread and just do it. It will be done this week, cross my heart!

Thank you from the bottom of my heart!