Forum Coordinators: RedPhantom
Poser - OFFICIAL F.A.Q (Last Updated: 2025 Jan 24 4:20 pm)
Sounds like a good idea, but.... :)
"Few are agreeable in conversation, because each thinks more of what he intends to say than that of what others are saying, and listens no more when he himself has a chance to speak." - Francois de la Rochefoucauld
Intel Core i7 920, 24GB RAM, GeForce GTX 1050 4GB video, 6TB HDD
space
Poser 12: Inches (Poser(PC) user since 1 and the floppies/manual to prove it!)
Good idea. I've seen many threads over just last couple of years, suggesting various structures, most of them good.
I don't know why Rendo or DAZ don't require merchants to follow a structure.
Hi, my namez: "NO, Bad Kitteh, NO!" Whaz
yurs?
BadKittehCo
Store BadKittehCo Freebies
and product support
Quote - Because the wheel isn't squeaky enough yet. >:D
I doubt that is the case.
Vendor folder and file organization is one of the monthly recurring themes. I saw one on DAZ Commons just earlier this week.
Hi, my namez: "NO, Bad Kitteh, NO!" Whaz
yurs?
BadKittehCo
Store BadKittehCo Freebies
and product support
Quote -
I don't know why Rendo or DAZ don't require merchants to follow a structure.
probably because no one agrees on what that structure should be
Quote - > Quote -
I don't know why Rendo or DAZ don't require merchants to follow a structure.
probably because no one agrees on what that structure should be
giggle
Ain't that the truth!
Hi, my namez: "NO, Bad Kitteh, NO!" Whaz
yurs?
BadKittehCo
Store BadKittehCo Freebies
and product support
Quote - > Quote -
I don't know why Rendo or DAZ don't require merchants to follow a structure.
probably because no one agrees on what that structure should be
Ditto that.
Quote - > Quote -
I don't know why Rendo or DAZ don't require merchants to follow a structure.
probably because no one agrees on what that structure should be
How do you know? I guess what you really mean is everyone doesn't agree. But who cares? That's why nothing gets done in a pure democracy. You just don't ask everyone. You set up a couple of people to come up with a few possible structures. Then you let everyone vote (or not :) ). Then the Rosity, DAZ, EF, or a combination implement the changes and its over with.
Like I said, you don't need to please everyone. You just need to come up with something reasonable. Then artists would know where to put things (with plenty of flexibility within their own folders) customers would know where to look to begin their inevitable customization, and the problem would be finished.
This isn't brain surgery.
Quote - > Quote - > Quote -
I don't know why Rendo or DAZ don't require merchants to follow a structure.
probably because no one agrees on what that structure should be
How do you know?
Stonemason knows everything - just trust me on that one!
First thing would be to get Rendo people, DAZ people, and EF people to agree internally that there's actually a need for standardization. Good luck with that ;)
You may be interested in bringing that idea up at the content creators guild: http://www.contentcreatorsguild.net/
Hi, my namez: "NO, Bad Kitteh, NO!" Whaz
yurs?
BadKittehCo
Store BadKittehCo Freebies
and product support
Quote - It certainly isn't, it's the Poserverse equivalent of "World Peace".
Nah. More like indoor plumbing.
Quote - First thing would be to get Rendo people, DAZ people, and EF people to agree internally that there's actually a need for standardization. Good luck with that ;)
That's a valid caveat, obviously. Which is what I meant with my point about the squeaky wheel. If it's a big enough problem, the vendor sites will act. If not, they won't. Because clearly it's an easy task. After taking suggestions from a variety of sources (maybe even a simple web page with the proposals and polls to see what is best liked) to make sure people who want to be heard have their say, it would take all of an evening or two for 1 to 3 people to hash it out and create a proposal. Some criticism, some more suggestions, a revision or two later, and problem solved.
Again (I've learned through hard experience that repetition is key to clarity), the goal is not to create the ideal structural standard, or even a very good one; the goal is to create a reasonable one so there can be a standard at all. This would even serve the interests of those people who are impossible to please and would wind up hating the standard structure.
Quote - You may be interested in bringing that idea up at the content creators guild: http://www.contentcreatorsguild.net/
Thanks, never even knew there was such a thing.
This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.
I think the folks at a few of the bigger vendors of Poser content, like the owners of Renderosity and DAZ should agree on a document outlining the basic configuration of content. If they did, most of the other vendors would fall into line I think. There could be an open license, allowing artists to add a trademark or seal of approval or whatever to tell customers they'd made the minimal effort necessary to comply with standards. It would be easier for artists, really, because they'd have guidelines and wouldn't need to make as many decisions when creating content. And it would sure as hell simplify the lives of their customers.
For example, the easiest structure that springs to mind for me for non-library files is content type>Vendor>Artist>[below this level is at discretion of artist].
For library files, things get a bit trickier since they need to be a bit more finely tuned. Maybe default folder (character, pose, hair, etc.)>category*>Vendor (optional; needed more for vendors like DAZ)>Artist>[Artist's discretion]
"Content type" really means "depends on context" here. E.g., geometry goes in the geometry folder, morphs go into the morphs folder (btw, isn't the morphs folder created by default inside the libraries folder in P7?), etc.
Personally I prefer that artists put each product in its own folder, with EVERYTHING NAMED INTELLIGENTLY (or at least uniquely), but I realize that may be a bit much to ask, and it might be better just to give suggestions for best practices beyond the level of the Artist's "root" folders (e.g., the artist's name, and the product name, should be on every file (but not necessarily folder).
I don't know all that much about naming conventions myself, other than what common sense and experience tell me works for me. But I DO know that more is better than less when dealing with "broadcasting," where one person's efforts during creation dictate how much work the far greater numbers of customers will have to deal with after purchase. E.g., if an artist is a schmuck and names his shirt "shirt," and puts the library files right into the character folder, he's pretty much guaranteeing that all his customers will have to at least create a new folder, maybe as many as three, and maybe rename the thing. This gets old fast; one person's laziness and lack of forethought have dictated that x people now have to do the work he didn't do.
My own library folder structure is very different from what's outlined above, but if there was any kind of standard I'd probably just go with it and be satisfied; it's the total lack of any kind of sensible standard that forces me to roll my own.
I'd be willing to discuss the details of something like this, if the parties mentioned above were willing to support such a document, but not put in the work creating one.
I know the main argument against a standard for library content (no good argument against standardizing non-library folder structures, like geometry, that I can think of ATM) is that every customer has his own preferred structure, and no standard could ever possibly keep them all happy, but at least a standard would give him a consistent place to LOOK for things in the first place when he goes to sort his library folders.
Just an idea. :)