JHoagland opened this issue on Sep 13, 2002 ยท 5 posts
JHoagland posted Fri, 13 September 2002 at 9:17 PM
As I go through the Poser character library, I'm starting to notice a lack of standards. Sure, this may seem like it is ""nit-picking", but it's also something that could have EASY been caught by Quality Control. Some examples:
VanishingPoint... Advanced 3D Modeling Solutions
kupa posted Fri, 13 September 2002 at 9:35 PM
John, We had a large team of volunteers and remote on-staff modelers overseas working on sections of the content project. We didn't implement a rigid naming system, though we should have. There were clothing items which were part of a set, such as the Clubbing Outfits, and some of these in the series were not included. Kupa
kupa posted Fri, 13 September 2002 at 9:37 PM
One other detail- the clothing was designated as P5--- to indicate that it conforms to a P5 figure, with the updated hip and collar structure. There is also a collection of P4 clothing which conforms to the the Poser 4 figures.
TygerCub posted Sat, 14 September 2002 at 5:24 AM
I like the P5 in front of models and accessories. This is great for people like me who tend to move files around to suit my needs. But if it bothers you, renaming the .CR2 and corresponding .RSR files is relatively simple and could actually be beneficial. For clothing and models that I use frequently, I number them (01, 02... 10, 11, etc) so they show up at the top of the list. That way, by the time I reach "10", everything remains in order. Good luck.
JHoagland posted Sat, 14 September 2002 at 10:58 PM
kupa- I agree that outsourcing development tasks is an excellent idea, however, it should be completely transparent to the end user. We (the public) buy Poser 5 from Curious Labs. The content within it (unless otherwise noted) should have the same naming convention, whether it was made by Vicky in Washington (developing the "MansPyjama" object), Don in Florida (the "FemalePajama" object), or Judy in Japan ("BoyPJ" object). By the time the product is shipped to the end user, these objects should have the exact same name and the figure they apply to: "MalePajama", "FemalePajama", and "BoyPajama". We should never know that CL outsourced anything. We didn't implement a rigid naming system, though we should have Why not? Was it a case of running out of time? I know CL has ship dates to meet (as do all software development companies), but this is a VERY old argument: Does a company release their software knowing that it's not "100%" finished to meet the "ship date" or does a company delay shipment to finish everything? Either decision has its pros and cons. Of course, the practice now (for a number of companies) seems to be "ship now, patch later": let the end users be the final beta testers. After a few months of "public beta test", the company will release a patch that fixes everything that should have been fixed before the product was released. This is what Microsoft did with Windows- the "public beta" was Windows 95 and the "final, patched version" was Windows 98. And this is also why the prevailing attitude towards Microsoft products is "Don't install [the new piece of software] until the first Service Pack comes out so they can have a chance to fix everything." And when will the first Service Pack for Poser 5 be available? Also, let me ask another question: If you go to the beach and get bit by a mosquito, it's annoying, but you stay at the beach. But, how many mosquito bites does it take for you to leave the beach? Meaning, how many "inconveniences" does it take before people stop purchasing a company's product? --John
VanishingPoint... Advanced 3D Modeling Solutions