 | | | | | | |
| |
|
BLdb version 0.1 announcement
An application to register and manage your LEGO collection data (parts,
sets and
MOCs)
After several attempts to design a database that could help manage my LEGO
sets' collection and another one to manage my parts' collection, with
Microsoft Access, I understood it might be a better idea to join both
applications in a single, larger one.
What I intended was that such program updated both the parts' and sets'
collections every time I bought a new set.
Then adding this the possibility to download Peeron's Set Inventories, import
my own inventories from Parts Catalog (by Bob Kojima), and also the
possibility to import parts from a Ldraw/MLCAD file, as well as from
Lugnet's and Peeron's sets/parts databases.
After a while behind the keyboard, I already have a program that works to
some of the components I wish; missing still is the MOC part and the
shopping one.
Screenshots are available at:
http://www.brickshelf.com/cgi-bin/gallery.cgi?f=11852
As you can see, besides the first window where every utility is, there is
a second one for the parts collection where we can make several searches
(includes filters). On the right chart we insert colours and quantities
available from the selected part (this is updatable with every purchase)
Below are the sets/MOCs in which the selected part is (being) used. This
is useful when I need one particular part, and I dunno in which MOC it is
being used.
In the set collection window we have the options "Sort", "Search" and
"Filter". Also depicted is the parts list for that set, comparing the
proportion of every part in the totals you own - this way you know if you
can build a given set even if you don't own the original (when this
happens, the checkbox below is checked).
Of course this work is not yet complete; I expect to launch a beta version
for evaluation next week, and have a complete version around April
(assuming everything runs smoothly!).
This is what I would like to hear:
- Comments to the preview;
- Ideas;
- And someone that can provide space on-line to host the program, so that
anyone can download it (around 5 Mb). If download numbers could be
tracked, it would be just perfect (for statistical purposes)
Thanks go to the owners/administrators from Peeron, Lugnet, Parts Catalog,
Ldraw, MLCAD and LDaddon, whose resources enable this program!
Thanks,
Luís Baixinho
| | | | | | | | | | | | | | | |
In lugnet.announce, Luis Baixinho writes:
> BLdb version 0.1 announcement
> An application to register and manage your LEGO collection data (parts,
> sets and MOCs)
<snip>
> Screenshots are available at:
> http://www.brickshelf.com/cgi-bin/gallery.cgi?f=11852
<snip>
I really like it. One piece of information that would be useful is the
storage location for a part, this would really come in handy for those of us
who store across multiple containers and can literally spend hours looking
for a part in our 'sorted' collections, or so I thought it was :-(.
Thus the ability to generate a report for each storage location would be
useful too.
Jude
BTW, what will be requirements to use this app?
XPosting to .storage
| | | | | | | | | | | | | | | | | | | | | |
| |
|
>
> I really like it. One piece of information that would be useful is the
> storage location for a part, this would really come in handy for those of us
> who store across multiple containers and can literally spend hours looking
> for a part in our 'sorted' collections, or so I thought it was :-(.
>
> Thus the ability to generate a report for each storage location would be
> useful too.
>
> Jude
>
> BTW, what will be requirements to use this app?
>
> XPosting to .storage
i'm thinking in put a new alfanumeric field in the form of parts collection.
this field would be appear close to color/qtd of the parts (thinking in a
storage by colors and parts).
i'll be working in reports only in april. the last part of the program.
about the requirements, i'm working in a pentium IV with 256 mb ram on
windows xp
is working fine, except when i have very set inventories in database. when i
change part/set, the data about de relantion sets/parts last about 1-5
seconds to appear. of course, if i select hide sets/parts this delay not exists.
the program needs less than 5 mb space on disk, plus the space for pics and
database files (for example, the file with all sets with about 1mb, parts
with about 800kb ...)
i think the program will be work fine in a 500mhz.
thanks
lbaixinho
(sorry my english)
| | | | | | | | | | | | | | | | | | | | | | |
Luis,
Do you have a working version yet? and if so are you happy to sell it to
others? Only I am very interested in this tool.
Regards
Jason
| | | | | | | | | | | | | | | | | | | | | | |
In lugnet.loc.pt, Jason Briscoe writes:
> Luis,
>
> Do you have a working version yet? and if so are you happy to sell it to
> others? Only I am very interested in this tool.
>
> Regards
>
> Jason
yes. i have a working version of the BLdb (the 0.5)
of course is unfinished.
i'm thinking in upload to 1000steine in the next weeks.
i don't touch in the code after march. others works...
and the BLdb will be free.
lbaixinho
| | | | | | | | | | | | | | | | | | |
How about a feature to record what pieces are missing from a set? I have a
few sets where the sets were either incomplete when I bought them (from
garage sales or whatever) or because a part got damaged.
| | | | | | | | | | | | | | | | | | | | | |
Hi,
In lugnet.loc.pt, Matthew Bates writes:
> How about a feature to record what pieces are missing from a set? I have a
> few sets where the sets were either incomplete when I bought them (from
> garage sales or whatever) or because a part got damaged.
I think that in this case, you should create another inventory derivated from
the official, and name it with something like "8858 Rebel Wrecker Used" or
"8858 Rebel Wrecker bought on ebay".
The program might have something to distinct official sets from
unofficial/derivated ones.
zanette.
| | | | | | | | | | | | | | | | | | | | | | |
In lugnet.loc.pt, Matthew Bates writes:
> How about a feature to record what pieces are missing from a set? I have a
> few sets where the sets were either incomplete when I bought them (from
> garage sales or whatever) or because a part got damaged.
you're right, the same thing happens with me.
a point to the new features to the BLdb.
thanks
lbaixinho
| | | | | | | | | | | | | | | | | | |
| |
|
This is an awesome idea! In fact, I've begun the very same project a couple
times, but never run it to completion.
One feature that I wanted the most in my version, and would very much like
to see in your version is integration with BrickLink.
Ideally, you would be able to do the following:
* Calculate the rough value of a person's collection by using pricing
information from BrickLink (say fair/average market value).
* Click on a set and determine if you have all the pieces. If you don't you
could click a link to BrickLink which would allow you to purchase the parts
as necessary.
Obviously there is a lot of opportunity here for shopping features:
* find a store that can fulfill your entire parts shopping list, so you
don't have to shop multiple stores.
Also, integration with CAD applications - specifically LDraw and MLCAD
* Allow importing/reading of dat files which will add the MOC/set to the
BLdb file and automically list the parts used. It would be pretty nice to
have check marks next to the parts when your collection has all the parts to
build it also.
Does your application allow you to mark a part as used? It might be
interesting to track "unused" parts, versus ALL parts in your collection.
In a similar vein to the "storage location" suggestion, it would be nice to
know if the part is used in a MOC, unused opened, or still in the sealed box.
Can you further explain what you mean by database for MOC data?
Have you contacted the respective web hosters to find out if they mind your
tool banging on their servers. Presumably it's not too much bandwidth, but
they might not want unofficial tools running against it (hope I don't rain
on your parade!).
Looking forward to using it!
-Stephen
In lugnet.announce, Luis Baixinho writes:
> BLdb version 0.1 announcement
> An application to register and manage your LEGO collection data (parts,
> sets and
> MOCs)
>
> After several attempts to design a database that could help manage my LEGO
> sets' collection and another one to manage my parts' collection, with
> Microsoft Access, I understood it might be a better idea to join both
> applications in a single, larger one.
>
> What I intended was that such program updated both the parts' and sets'
> collections every time I bought a new set.
> Then adding this the possibility to download Peeron's Set Inventories, import
> my own inventories from Parts Catalog (by Bob Kojima), and also the
> possibility to import parts from a Ldraw/MLCAD file, as well as from
> Lugnet's and Peeron's sets/parts databases.
>
> After a while behind the keyboard, I already have a program that works to
> some of the components I wish; missing still is the MOC part and the
> shopping one.
>
> Screenshots are available at:
> http://www.brickshelf.com/cgi-bin/gallery.cgi?f=11852
>
> As you can see, besides the first window where every utility is, there is
> a second one for the parts collection where we can make several searches
> (includes filters). On the right chart we insert colours and quantities
> available from the selected part (this is updatable with every purchase)
> Below are the sets/MOCs in which the selected part is (being) used. This
> is useful when I need one particular part, and I dunno in which MOC it is
> being used.
>
> In the set collection window we have the options "Sort", "Search" and
> "Filter". Also depicted is the parts list for that set, comparing the
> proportion of every part in the totals you own - this way you know if you
> can build a given set even if you don't own the original (when this
> happens, the checkbox below is checked).
>
> Of course this work is not yet complete; I expect to launch a beta version
> for evaluation next week, and have a complete version around April
> (assuming everything runs smoothly!).
>
> This is what I would like to hear:
>
> - Comments to the preview;
> - Ideas;
> - And someone that can provide space on-line to host the program, so that
> anyone can download it (around 5 Mb). If download numbers could be
> tracked, it would be just perfect (for statistical purposes)
>
> Thanks go to the owners/administrators from Peeron, Lugnet, Parts Catalog,
> Ldraw, MLCAD and LDaddon, whose resources enable this program!
>
>
> Thanks,
> Luís Baixinho
| | | | | | | | | | | | | | | | | |
| |
|
In lugnet.loc.pt, Stephen Fisher writes:
> This is an awesome idea!
Thank you
> In fact, I've begun the very same project a couple
> times, but never run it to completion.
> One feature that I wanted the most in my version, and would very much like
> to see in your version is integration with BrickLink.
> Ideally, you would be able to do the following:
> * Calculate the rough value of a person's collection by using pricing
> information from BrickLink (say fair/average market value).
> * Click on a set and determine if you have all the pieces. If you don't you
> could click a link to BrickLink which would allow you to purchase the parts
> as necessary.
> Obviously there is a lot of opportunity here for shopping features:
> * find a store that can fulfill your entire parts shopping list, so you
> don't have to shop multiple stores.
the BLdb works offline, but you have good ideas, perhaps in the version 2 (i
hope finish v.1 in April)
> Also, integration with CAD applications - specifically LDraw and MLCAD
> * Allow importing/reading of dat files which will add the MOC/set to the
> BLdb file and automically list the parts used. It would be pretty nice to
> have check marks next to the parts when your collection has all the parts to
> build it also.
the only thing that BLdb do for now is import the MLCad files created on
menu Extras>Reports>Pieces
but i think in import direct from dat/ldr files.
> Does your application allow you to mark a part as used? It might be
> interesting to track "unused" parts, versus ALL parts in your collection.
> In a similar vein to the "storage location" suggestion, it would be nice to
> know if the part is used in a MOC, unused opened, or still in the sealed box.
in the beginnig i has thinking in that. i abandoned the idea because i'll
never use this, perhaps i'll reconsidered...
> Can you further explain what you mean by database for MOC data?
???
> Have you contacted the respective web hosters to find out if they mind your
> tool banging on their servers. Presumably it's not too much bandwidth, but
> they might not want unofficial tools running against it (hope I don't rain
> on your parade!).
my english is very bad and in the BLdb post i ask for a friend help, perhaps
the translation not said what i think. the BLdb works offline, maybe one day
(the bricklink idea) will works online...
> Looking forward to using it!
-Stephen
thanks
lbaixinho
| | | | | | |
