design-id vs item-id


Re: design-id vs item-id
#10
Michael Heidemann Wrote:
Code:
A file storage convention (e.g. a new LDraw/Items folder) would impact tools that don't have the capability to extend the search path through a configuration file.
I do not think that there are many of those applications in use.

To solve this issue by file storage is the best solution in my eyes. Depending on the application we also do not need to care about existing models that are build with itemID parts.

The idea of a prefix is not my favorite. If I have the booklet from TLG I am searching for that number that is written there. We should not make it more complex than necessary. If we have a different storage place it should be possible to handle that smoothly.

The software could handle the naming convention for file access separately from a user interface presentation, so using a prefix would not necessarily present a bad user experience, and it has the advantage of working with existing software (albeit without as nice a user interface).
Reply
« Next Oldest | Next Newest »



Messages In This Thread
design-id vs item-id - by Michael Heidemann - 2013-03-17, 19:25
Re: design-id vs item-id - by Roland Melkert - 2013-03-17, 19:43
Re: design-id vs item-id - by Tim Gould - 2013-03-17, 20:46
Re: design-id vs item-id - by Roland Melkert - 2013-03-17, 21:01
Re: design-id vs item-id - by Chris Dee - 2013-03-17, 21:25
Re: design-id vs item-id - by Joshua Delahunty - 2013-03-23, 16:19

Forum Jump:


Users browsing this thread: 1 Guest(s)