Runtime, a.k.a. I'm redeeming a coupon for one stupid question
Korpin.Sulat
Posts: 414
in The Commons
Keep in mind I've only been in this game for about a year now. But I often hear a lot of long-time users and artists refer to their/my/your runtime. Recently saw a forum comment where someone said they had 30 runtimes. I've always understood the word to mean something that wouldn't necessarily be applicable to Daz at all, so I'm utterly confused.
From context, I'm gathering that when you guys say "runtime," it's essentially shop-talk for "file directory"? When did that first come into use?
I'm not being sarcastic or standoffish, I'd genuinely like to know. I expect to get a history lesson.
Comments
As I understand it, runtime is technically runtime environment or runtime directory. Your runtime may include scripts and accessory software so it is more than just a file directory and more of an extension of the program. Thus the usage is typical for software.
In Daz/Poser it's a fancy way of saying "my file directory" like "My Library" or "My Daz Library".
This stems from the Poser days because in Poser all is kept in the Runtime folder.
Many of the long time users like to make a "library" or "runtime" sorted by the site they bought the item from, genre and other things.
So something like this;
Daz Stuff/
Renderosity Stuff/
Commissioned project for Bob/
---
It's a lot more complicated and can be a lot of work to maintain, but some users like and even need this level of control.
I wouldn't suggest this until you have some experience in handling manual content installs. You can very easily turn your library into an unusable mess.
Currently there is no automated way to handle this.It's all done manually by the users.
The term runtime itself is computer program terminology. The files used in Poser (or Studio) will usually call on other files within that runtime environment (e.g., when you click the icon to run the script to load a figure, it loads the rigging, looks to the data folder to load the geometry, the textures folder to load the maps, etc.). Whether or not Poser ever intended to use the term "runtime", that was the name of the folders for the library and the name stuck. You can still see the folder even using only D|S native content because the "textures" folder is still under runtime.
As far as why it is still used now, as mentioned above, it's just because the name stuck and so much historic documentation and tutorials use it that it would be hard to get people to call it something else now. Same reason that the save icon in most software is a floppy disk, even if the software was made by people who have never seen one, but people learn that this means "save".
Ooh, that second paragraph reads like you've written articles before.
Oh, I have a second hard drive and directory for all my third-party stuff and I take control of the folders that the main .duf files go into (organizing characters/clothing, correcting the difference between environments and props, that kind of thing), and that's just because it's easier to uninstall by keyword that way. But that's as far as I go, I think. Data and Runtime folders go untouched. I usually don't give a rat's butt about documentation since I can usually find it on the product page or in the original zip (I keep those backed up, too) if I desperately need them, so those folders go bye-bye.
Daz does its own thing, though, and I just let it.
Daz Install Manager lets you install a product to any directory folder you desire so long as you have it designated under the Installation tab in Advanced Settings. Then, all you need do is select a file you want to install, enable "Show Details" on the Ready To Install tab and choose the directory from the dropdown menu at "Content Path Shortcuts". It will install to any folder on any drive you have designated.
That was a detail I had just noticed this morning when I checked that box by mistake.
Like I said, It can get a bit complicated. Doesn't take much and you have some extra work to do to get it sorted the way you want again.
Not impossible, just not as straight forward to everyone.The extra steps may not seem all that much to some, but will to others.
Don't forget to add those paths to the CMS in Studio. :)
...and be careful not to nest them.