Search options (Page 100 of 117)

Mă bag și eu să hijack the thread

Și ale mele sunt de dat în același fel, voi păstra doar unele chestii pentru EDH. Nu am multe chestii valoroase, dar am pus și eu ce-i peste 1$ în tradelist. Restul mai ieftine de atât (nu am updatat tradelistul și cu acelea, dar inventory-ul mi-e up to date, și puteți cere și de acolo) sunt de dat gratis.

Ce am în wishlist încă îmi mai trebuie, deci și trade e super ok.

http://deckbox.org/sets/2?s=i&o=d

Hmm... this is not good. I banned him, but where there is one...

I'll put up a captcha on the signup page, but that's not going to be enough, as I bet there's other registered ones already.

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!

Looks like I had forgotten the Ajani vs Nicol Bolas Duel Deck. Now it's imported: http://deckbox.org/games/mtg/cards?f=5399.

Thanks for the reminder mihai

We get the information from gatherer, who usually is updated with new sets a few days before the prerelease.

As we are off on holiday the next couple of weeks, the new set data will most probably be imported on sunday the 25th of september.

Fixed now. Thanks for reporting.

Quick status update:

I've moved the website to the new server last night, the move itself went pretty smooth, except for some database server weirdness that might have caused slow response times from time to time, until this morning. I addressed some of the possible culprits, should be smoother now, and it's being monitored.

Let us know if you see strange things today, like hanging pages, late responses or any other out of place things

Yes, this is a known bug and annoying to see but as it was not breaking anything it was not on the important list.

I know we have not dedicated too much time to features and bugfixing lately as we should, and I assure you we will start working more on it again soon. I also appreciate everybody's offers to help but as easy as that sounds "get someone to help", it is not a logistically trivial thing to do properly.

There was a lot of work for our dayjobs, and we have moved to a new country a year ago as well, so we spent a lot of free time compensating for this stress, and less weekends working on deckbox. I know I have promised a more formal announcement of what we plan on doing with deckbox in the future in the spring of this year and have not delivered.

We're going on a holiday in september finally, after 9 months of working, and when we come back fresh there will be more involvement, and a newsletter of what the status is and what we are going to do going forward. Please be patient with us, we shall deliver.

P.S. unclemantis, I have deleted your spam posts on the other threads. Please refrain from copy pasting the same annoying message all over the place.

Hello gmabber,

We are thinking about a mobile version of the website ourselves for some time too. An API is a good idea and possibly we'll have it, but it is a bit lower on the todo list