• Content count

  • Joined

  • Last visited

  • Days Won


biodreamer last won the day on March 6

biodreamer had the most liked content!

About biodreamer

  • Rank
    Level 7 Stud

Contact Methods

  • Bricksafe URL

Profile Information

  • Gender
  • Location
    Stockholm, Sweden
  • Interests
    Software development, Games of all types (Computer,videogame,board games,..),Movies,Lego .
  • Favourite Set(s)
    6987-1, 375-2, 6085-1,6986-1,6985-1

Recent Profile Visitors

776 profile views
  1. Comment Spam?

    Can only agree on this. there is no reason to ever make a group like that Lego has nothing to do with religion let keep it that way it's only the Amish people who would need to stay away from the toy. so I guess you can never get them to join any group otherwise lets not add external unrelated limitation away from this site. unless there is rules that prevent you from making religious types of MOCS, (without religious messages) in that case I think it's wrong. Nothing wrong in building churches and temples with lego bricks if that is what you want to do.
  2. throttle in API

    No I am not but it's how things works. it's kind of independent of hardware. hardware only increase speed and capacity. it does not remove the fundamental rules. if you need to get all entries a few easy large one will take less resource then multiple advanced queries that still boil down to same result. the process time of those 5000 calls will always be more then those 28. but if it can handle a lot of connection you might get the result faster by splitting it but it won't take less server resources ever, only more.
  3. Link from Bricklink to Rebrickable throws error

    it's a sticker parts so don't expect to find any sticker parts on rebrickable.
  4. throttle in API

    what you can do is cache the data on your end and only query again after a certain time unless you know it has changed, and only query for what you need. ie if you intend to only show the first 40 items then don't get all 28000, but perhaps the first batch of a 1000, think both of your own performance and that of the API. and you will help Nathan in the process.
  5. throttle in API

    it's a database adding more conditions will slow it down. so 28 calls is better then 5000 calls even if each generate a big chunk of data.
  6. App Preferences?

    Use a sqlite database to cache stuff and async load/update them in a background thread. try to predict the need when possible and keep the cache for offline use. basically follow the google guide lines and suggestion from the their I/O, developers summits etc on YouTube. Use picasso or similiar to cache images.
  7. Building it for yourself is kind of inefficient. I mean the time to build a program like that is never saved in time you personally save in looking around for parts in your collection. it's like labels they are primarily for other potential user, you are bound to know your collection by heart and could find your parts without the helper. So those weeks you spend on the code would be hundreds of sets built. So you need to love to build programs as much as you like to build with LEGO or you made a bad hobby trade. on the other hand if you build software to help other people, its great and you should know what they want and need. and what alternatives they have today. I see following lacks today if you only have rebrickable. 1) no way to keep your instructions/boxes and minifigs organised but there is other web pages covering those needs 2) The collection management that is linked together with rebrickable keeping only one universal inventory without having to maintain two or more. while labeling and experimenting with storage solutions would make this awesome, however I am only aware of databases and spreadsheets that handles this and that means two sources to keep updated 3) Some better way of making MOC instructions right now this is no good software that can take a Lego 3D models dissect it and spit out a good step instruction with good angles. which gives a good instruction without a lot of tedious manual work. LDD tries to do it and often fails, other is purely manual. 4) an App that spit out building ideas or challenges to the builder based on it's part collection. more for builder that get stuck and can't decide what to build now or just challenge a builder creativity while still restrain his or her usage. or if they want to take it to another level and challenge other collectors and then just upload the result of the challenge in form of a MOC picture of the result. This can be made as basic/advanced and complex as the programmer wants and can handle. there is probably other but those four would peek my interest.
  8. well yeah but for what your doing I could easily just ask Nathan for a temporary checkbox next to the set inventory. like bricklink has for when you check your orders on arrival. and then go around my drawers checking the parts off while going through the inventory. I haven't seen that feature in the suggestion forum so it can't be a so urgent issue among the users. maybe they just print it and use a pen to tick them off. Then if I needed to actual mark the storage bin I could just upgrade my account here on rebrickable and use the pro feature. So the market for your app is kind of limited...
  9. Again I don't want to know in which bin the item is in. I want to know how to tetris my grid. so it's rather the reverse problem + that the picture I showed you is for the default layout some boxes will have 24 tiny 1x1 containers in them while other will have 4 large 2x4 containers in them all depending on what the part needs, there will be any combination in between those two. and Yes I know moving around drawers is unavoidable if you keep growing your collection and don't stagnate it. Since this takes time, it's also where the need and time saving of said software could be useful. it require dimensions of the parts and stacking rules and the container dimensions to be built then there is the user preference ie how little space are a item allowed to take to be allowed in it's own container instead of grouped with other parts. ie at least 25% of container should be used by parts how much space should be counted as auto wasted due to collector not optimizing the drawer content ie 100% usage would mean perfect optimal stacking, while ca 75% mean tightly piled parts. this most likely differ a bit on parts but I would assume about 1/3 can be wasted to save time in not stacking parts down into the container. then some kind of sorting hierarchy would be required ie when to keep parts grouped and when to split them into several containers and in that case in what order? ie category -> part -> color/pattern or do the user prefer those in a different order? For example my smallest container is 4x6x5 lego units in dimension (obviously the software should use metric but for easy reference). that means that anything larger then that would be disqualified and be automatically upgraded to the smallest container that fit that part. if you could do a application that solve how people store their collection in a good way while it's allowed to grow you solve a problem no web page or spreadsheets has been able to handle in an easy way,you will solve something any but the smallest collection will tackle. meaning instead of having two users you might get a couple of thousands. it's only those who still stores their parts in their original sets that would have no interests in the solution. in the end that could mean that I could feed in pending orders into the system and be proactive and fixing the layout, printing the new labels and be ready to put the pieces in the containers when they arrive by mail. PS for the keypad issue make sure you allow the activity to resize for the keypad. You do that in the android manifest. other then that keep those activities small so they will work in a smartphone. that or put in a minimum dp resolution on the screen if you don't want to support the smallest devices. this is also done in the android manifest.
  10. even with your solution I bet there is drawers moving around even if they don't reshapes as much.
  11. so what I would want is something that makes it easier for me to layout the puzzle of boxes. ie know exactly how many "slots" each part category and color takes up so I can arrange them with a little splits between boxes as possible. Since I am using these: where the sizes adapt to the content but making it easy to bring the part + color combination to the build table. Which is why I like it even if it's a expensive solution compare your much cheaper more common wall mounted solutions. You simply can't fit all the boxes around the desk anymore. So keeping a way of optimizing the content and aligning them together, so you can easily find them without knowing the catalog in your head. ie I know all my bricks is in the right most column of drawers, plates are in the third, Technic is in the fifth. means I almost hit spot on directly even when looking for a more rare part. I just need something that can manage my 6 x 6 x 6 x 4 matrix. so I don't waste space and know what colors that align well with others to reduce splits.
  12. Marking the parts up isn't the issue, and rarely really finding them it's all about a management and if you have to relabel everything when things move around it doesn't solve my main issue it only add another layer on top of it. The same reason why most of my labels get out of date quickly and I rarely have time to keep them in sync.
  13. well I have my collection of bricks in three major section small containers and large containers and extra large containers (most because of the practicality of stacking similar containers then of a way to easy find parts. Here the extra large containers contain the big parts and some mix of them. One contain all the base plates, another contains all the boats hulls and the last the trains switches and crossings. These are easy enough to find parts in because they are big and bulky. The large containers are plastics containers of varied sizes with lids stored on shelves. I refer to them as S,M, L, XL and XXL) where the S starts at 21x17x6 cm followed by M that is 11 cm high and Large at 15 cm high. XL is about twice the size with its 34x24x16 cm which is followed by the XXL which is about twice the size again larger. in these I store either large but not so extremely bulky parts such as large wheels, castle walls, supports, large panels etc. or simply large bulks of common parts such as one of the XXL is actually for storing red 2x4 bricks. Most of the old 7 colors of bricks are located here while all the newer colors usually still remain in much smaller quantites and are stored in the small containers. This section could use a label tools but is otherwise quite easy to manage. it might need some work soon since my collection start getting big here as well. so the final and most challenging part of the storage is the small containers which is basically a wall of raaco/co craft. drawers with a grid of 6x4 for interchangeable containers, where you can put 1x1,1x2,1x4, 2x2, 2x4, 4x2 containers in place. and when the drawer with lid is closed they won't move. I try to keep parts of same color and category next to each other and this often cause overflow effect when a container need to be upgraded to large size when I got more parts then what fitted in the last one. the oppocent will happen when a large container is evicted to the larger storage area making the spot the color part category shrink. when this happen in several places after each bricklink order you wish you had a way to overview the storage and could try to rearrange things in software before attempting it in the physical world. knowing how many new boxes that will be needed etc.
  14. I think it's because inventory system differ a lot. I don't think this program is useful at all together with mine and so would many other's system also. I would have more use of a way to print new labels to the boxes when I move stuff around then having a note. especially since I don't store pieces according to sets. if you really want interest in your project you should ask does this project benefit someone else then me? and is there some small changes I can do to increase the usefulness to others.
  15. Adding Tags to Sets

    Add the Boat Tag to Tips and Tricks: and remove the following sets from it: (No Boat in this set) (No Boat in this set) (Rafts hasn't been counted before, there is plenty of pirate rafts not listed if they would.)