You are not logged in. Please login or register.
The latest patch doesn't work because the site changed again while the quickfix version was in review at Apple :-/ I'm working with Sebi to resolve this issue ASAP.
I'm sorry for the trouble :-(
The app is working :-) Go try it out :-)
429 (100%)
Thanks for the update. I can enter my account and see that it exists, but I still only ever get my wishlist and trade list updated. I get a connection error after about a minute or two. Any idea why my inventory won't load?
Thanks for the update. I can enter my account and see that it exists, but I still only ever get my wishlist and trade list updated. I get a connection error after about a minute or two. Any idea why my inventory won't load?
Hello PSREX. I just tried to load your data into the app and I stumbled upon the same problem. The thing is, when I try to manually export your inventory through my web browser, same thing happens. This leads me to believe it's a server side issue with big inventories, since my account works fine (about 1.8k distinct cards total) and Shoe's and yours doesn't (you both have big, over 10k libraries).
I'll drop Sebi a line about the matter and we'll see what can be done to fix this.
I think you should contact deckbox admin/dev and work with them instead of parsing the html produce by deckbox...
The app could be really better and you should not have to change your app after a small change in deckbox UI.
Thank you for your works, it's really appreciate!
I think you should contact deckbox admin/dev and work with them instead of parsing the html produce by deckbox...
The app could be really better and you should not have to change your app after a small change in deckbox UI.Thank you for your works, it's really appreciate!
I concur. HTML sparsing works, but direct access to the DB's will allow the app to work despite updates. Also will not create memory issues. You're essentially copying the entire page of HTML, then breaking it dowm. It is no wonder it fizzles on large db's
I guess it's nice, but an Android version seems essential. There are more Android devices than Apple devices.
This is true but I don't deal in android devices. I'm focused on Apple stuff. I don't even have an android phone, not to mention time for making and maintaining a separate version of the app for a different platform :-(
HTML sparsing works, but direct access to the DB's will allow the app to work despite updates. Also will not create memory issues. You're essentially copying the entire page of HTML, then breaking it dowm. It is no wonder it fizzles on large db's
Direct access to a db is something nobody sane would allow. There are plans for an API for deckbox.org, but other things have taken priority and since I don't own deckbox there is nothing I can possibly do about it. I guess we'll have to wait patiently and work with what we have at our disposal.
I think you should contact deckbox admin/dev and work with them instead of parsing the html produce by deckbox...
The app could be really better and you should not have to change your app after a small change in deckbox UI.Thank you for your works, it's really appreciate!
Thanks for kind words :-) It's not that I have to parse everything ;-) Sebi provided us with a csv export on which I rely to grab one's data. The hardest part is grabbing info about set numbers for inventory, tradelist and wishlist - from there it's like a walk in the park. Unfortuately there's no api to get those numbers so I have to scrape html code and problems like the last one we faced occur. In 1.3 I'll improve code which grabs the number and try to make it less prone to layout changes. I don't see me going into xpath and such things though, since eventualy there will be an API to comfortably get the needed data.
429 (100%)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.
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.
I don't know the exact number, but there are no problems with my database, which clocks around 2200 distinct cards, inventory, wishlist and tradelist combined.
Last edited by gmabber (2013-01-12 07:49:15)
2013-01-13 15:43:58Do 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 :-)
429 (100%)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
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?
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.
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
2014-05-19 08:01:10I'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.
2014-05-19 08:02:03Sebi, 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
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.
Last edited by gmabber (2014-05-20 04:19:54)