Mine has 6800 unique and works fine.

psrex wrote:Do you have any idea of the normal number of cards for a collection that is working properly?

For now I'll delete my collection and then just add back in cards that are in decks or in my trade binder.

Please do not delete you collection, this is definitely our fault, all features have to work for all our users, with inventories big or small :)

We fixed some performance problems now, the export to csv should work again faster. It will still take 10-20 seconds for very large inventories, but it does finish successfully, so the iOS apps should work for you again.

Let us know if you encounter other problems.

Just tested on Shoe's and Psrex's accounts and the app is working just fine :-)

Thanks for taking care of this, Sebi :-)

Thanks! Everything loads now.

gmabber,

May I suggest a 'decks' feature/button where a user can manually enter their set number they can get via their browser URL?

I suppose it is a bit of work for the user, and leaves a lot of room for confusion/error, but I still see it as being a pretty useful feature.

Now... If we could only get these deckbox folks to work on a API, this site could be boomin! ;)

-Esteban

Esteban wrote:May I suggest a 'decks' feature/button where a user can manually enter their set number they can get via their browser URL?
I suppose it is a bit of work for the user, and leaves a lot of room for confusion/error, but I still see it as being a pretty useful feature.
Now... If we could only get these deckbox folks to work on a API, this site could be boomin! ;)

I wanted to include deck imports, but the csv export works only for Inventory, Wishlist and Tradelist. If it worked with decks, they'd be included already ;-)

Blast! You're right. I tried tricking the page into exporting a different set number by using the

 Tcg.ui.Window.exportCSV(**set_number**,'','');return false; 

, but it shot back with a 500 error.

Sounds like its 1 conditional, and a little bit of logic away from being a working feature!

Y'all should Github these projects. I'm sure plenty of us nerds would be more than willing to help build these sites. :]

dosent seem to work no more, cannot connect from iphone or update list?

561895118 wrote:dosent seem to work no more, cannot connect from iphone or update list?

It doesn't and it won't until Sebi and the Team release a working API for the site. I'm done with scraping the site for info and keeping up with deckbox.org updates. I've been promised a working API about two years ago. Based on the promise I made an app which people really want to have and use but since the team has other priorities, I decided to have other priorities, too, so the app remains unfinished and unpolished.

*If* you want to have a better app, please let the Team know. For now the app is removed from the App Store because I don't have time to answer a few emails per day asking why can't somebody use the app.

gmabber wrote:I'm done with scraping the site for info and keeping up with deckbox.org updates.

BTW: you can use the print feature. the link format is as follows:
http://deckbox.org/sets/<set number>/export
so my wishlist is
http://deckbox.org/sets/406621/export
and one of my decks is*
http://deckbox.org/sets/658234/export

get the text (not the html) of the page.

Does this help?



*You will need to strip a little bit from the ones for decks

gmabber wrote: I've been promised a working API about two years ago. Based on the promise I made an app which people really want to have and use but since the team has other priorities, I decided to have other priorities, too, so the app remains unfinished and unpolished.

I'm sorry for the promises i made, I am always too optimistic with what I think I can do, and it always turns out it's not so easy... I will try to announce less things in the future until I know they are almost done.

API is still very important to me, and I still want to have it. It does require work and it depends on some structural changes that are not yet done. It will come, I'm not sure when.

Chaim wrote:BTW: you can use the print feature. the link format is as follows:

He is already using the CSV export.

Sebi, I really don't need all that much to make the app work... If you could just provide me with a read-only API, that'd be enough for now. CSV exports for everything are there... all I need is a stable way of acquiring set numbers with names for users in one convenient JSON response. I could take over from there and import stuff into the app. Managing those sets could be implemented later. Right now people can't access their data because there's no way for me to get inventory, tradelist and wishlist set numbers and I'm not going to ask people to find them out on their own because I'll drown under support requests.

im sorry guys i didnt want to start a fight, i tought the app was a great thing and that it was working great until i wanted to update my card list on my phone

but keep up the good work i love the app

561895118 wrote:im sorry guys i didnt want to start a fight

It most definitely is not a fight :-) Also, I'm glad you like the app. I'd make it much more but without an API I'd constantly be struggling with things like login problems, set downloading progress, one star reviews (which are really really disappointing for me), support requests and others and I simply don't have the rime for that. Either I can do something great or it's not worth it to waste my time on and right now I'd be wasting my time.

gmabber wrote: It most definitely is not a fight :-) Also, I'm glad you like the app. I'd make it much more but without an API I'd constantly be struggling with things like login problems, set downloading progress, one star reviews (which are really really disappointing for me), support requests and others and I simply don't have the rime for that. Either I can do something great or it's not worth it to waste my time on and right now I'd be wasting my time.

Completely understandable. I will start on a readonly alpha version after this release, even if it's just going to be authentication and fetching a user's list of sets.

sebi wrote:Completely understandable. I will start on a readonly alpha version after this release, even if it's just going to be authentication and fetching a user's list of sets.

Awesome! Just drop me a line when you finish and I'll update the app :-)

sebi wrote:I will start on a readonly alpha version after this release, even if it's just going to be authentication and fetching a user's list of sets.

Sounds nice. Will it be available to devs in general?

Also, would it be able to have a plaintext set export?

Chaim wrote:

sebi wrote:I will start on a readonly alpha version after this release, even if it's just going to be authentication and fetching a user's list of sets.

Sounds nice. Will it be available to devs in general?

Also, would it be able to have a plaintext set export?

Yep @ availability. We already have a CSV export available for sets.

sebi wrote:We already have a CSV export available for sets.

Yeah, but how do I grab and trim that with js?

Also, will we be able to fetch card images easily?

Chaim wrote:

sebi wrote:We already have a CSV export available for sets.

Yeah, but how do I grab and trim that with js?

Also, will we be able to fetch card images easily?

You mean with js from a browser? I assume you can't do that easily because of cross-domain issues. You can't do it easily with normal JSON apis either, you need to do it serverside.

For card images, right now you can get them for ex with:

http://deckbox.org/mtg/Swamp/tooltip

Support for separate printings to come later.

sebi wrote:You mean with js from a browser? I assume you can't do that easily because of cross-domain issues. You can't do it easily with normal JSON apis either, you need to do it serverside.

Not a normal browser, no. Cross-domain is not an issue.

sebi wrote:For card images, right now you can get them for ex with:

http://deckbox.org/mtg/Swamp/tooltip

Support for separate printings to come later.

I get a page of gibberish at that link.

Chaim wrote:Not a normal browser, no. Cross-domain is not an issue.

Then you can just make a get request to the csv export url and parse it with something like https://github.com/wdavidw/node-csv . But I'll add a json one too in the API at some point.

sebi wrote:I get a page of gibberish at that link.

Yeah, the mime type is set to html by the cacher, old bug. That's a valid jpg image of the card though if you save it and open it.

sebi wrote:

Chaim wrote:Not a normal browser, no. Cross-domain is not an issue.

Then you can just make a get request to the csv export url and parse it with something like https://github.com/wdavidw/node-csv . But I'll add a json one too in the API at some point.

Chaim wrote:I get a page of gibberish at that link.

Yeah, the mime type is set to html by the cacher, old bug. That's a valid jpg image of the card though if you save it and open it.

Testing. The following should be an image of the most recent swamp.

gmabber, a temporary solution that might help you get the app running again:

http://deckbox.org/sets/list.json?user_login=sebi

It does not list private inventories and decks yet, but you can use it as a quick solution until the proper API is coming.

sebi wrote:gmabber, a temporary solution that might help you get the app running again:

http://deckbox.org/sets/list.json?user_login=sebi

It does not list private inventories and decks yet, but you can use it as a quick solution until the proper API is coming.

Works great! Thanks! :D

sebi wrote:gmabber, a temporary solution that might help you get the app running again:

http://deckbox.org/sets/list.json?user_login=sebi

It does not list private inventories and decks yet, but you can use it as a quick solution until the proper API is coming.

Sebi, has anything changed with the CSV exports? The card count i'm getting always equals to zero... I'm forming url's as you described some time ago...

Should be the same. Could you send me an url to the export that is causing troubles?

sebi wrote:Should be the same. Could you send me an url to the export that is causing troubles?

I made some tests and it turns out the export works ok for Inventory, Wishlist and Tradelists but returns 0 as a count for exported decks. Also, there's no indication if a card is maindecked or in sideboard, which is kind of important.

For me it seems to work, both the count, and the sideboard flag.

E.g. http://deckbox.org/sets/export/97230?format=csv&s=&o=&columns=&v2=true