User talk:SignpostMarv Martin/Hair Plug
Jump to navigation
Jump to search
Style Format
Dimensions
Any variables pertaining to strands should be defined at the maximum scale. Prims can generally be downscaled without a problem, but upscaling is likely more problematic.
- SignpostMarv Martin 23:01, 10 January 2008 (PST)
Style by Sculptie UUID
In a wig that is not designed to make allowances for flexi-prims (bar dynamically generated loose strands), the style document could be defined as a list of sculpt map/texture key pairs, e.g.
d962089b-2197-993c-9ec9-4993eb0a95f2:6db0dff6-6f7a-8b93-3b83-4b75e3f6d3a4
d962089b-2197-993c-9ec9-4993eb0a95f2:6db0dff6-6f7a-8b93-3b83-4b75e3f6d3a4
d962089b-2197-993c-9ec9-4993eb0a95f2:6db0dff6-6f7a-8b93-3b83-4b75e3f6d3a4
d962089b-2197-993c-9ec9-4993eb0a95f2:6db0dff6-6f7a-8b93-3b83-4b75e3f6d3a4
Each entry in the list would correspond to a internally numbered "strand".
- SignpostMarv Martin 17:36, 22 January 2008 (PST)
XHTML-esque method
'Seperating Style from Layout' With either llHTTPRequest() or llGetNotecardLine(), the layout (e.g. llSetLinkPrimitiveParams() calls) can be held in a separate resource to the style resource.
Using the #Style by Sculptie UUID example, consider the following:
Layout:83b3987f-9520-4275-8efe-3ac13dd3f635
d962089b-2197-993c-9ec9-4993eb0a95f2:6db0dff6-6f7a-8b93-3b83-4b75e3f6d3a4
d962089b-2197-993c-9ec9-4993eb0a95f2:6db0dff6-6f7a-8b93-3b83-4b75e3f6d3a4
d962089b-2197-993c-9ec9-4993eb0a95f2:6db0dff6-6f7a-8b93-3b83-4b75e3f6d3a4
d962089b-2197-993c-9ec9-4993eb0a95f2:6db0dff6-6f7a-8b93-3b83-4b75e3f6d3a4
Layout:http://hp.example.com/sculpt/83b3987f-9520-4275-8efe-3ac13dd3f635
d962089b-2197-993c-9ec9-4993eb0a95f2:6db0dff6-6f7a-8b93-3b83-4b75e3f6d3a4
d962089b-2197-993c-9ec9-4993eb0a95f2:6db0dff6-6f7a-8b93-3b83-4b75e3f6d3a4
d962089b-2197-993c-9ec9-4993eb0a95f2:6db0dff6-6f7a-8b93-3b83-4b75e3f6d3a4
d962089b-2197-993c-9ec9-4993eb0a95f2:6db0dff6-6f7a-8b93-3b83-4b75e3f6d3a4
Using remote (HTTP) resources
Advantages
- Can be remotely updated if their is a bug in the layout document or viewer that needs to be corrected
- Useful for Living Hair
- Would allow web-based management of hair styles (e.g. http://hp.example.com/resident/83b3987f-9520-4275-8efe-3ac13dd3f635 )
- Can use HTTP Headers to control access to styles
- Doesn't need to be pieced together
- Allows for inter-grid use of hair layouts (so Teens and non-LL users could benefit from the products)
Disadvantages
- Layout documents would be limited to 2048 bytes
Using notecard resources
Advantages
- Prevents inter-grid use of hair layouts (If you want to restrict distribution)
- Layout document can be larger than 2048 bytes
Disadvantages
- Layout document lines limited to 255 bytes
- Lack of dynamic asset support on Linden Lab grids prevents layouts from being remotely updated
- Document would need to be pieced together line by line