|
If you were logged in you would be able to see more operations.
|
|
|
|
File Attachments:
|
None
|
|
Image Attachments:
|
|
|
Environment:
|
any
|
|
Issue Links:
|
Relates
|
|
This issue Relates to:
|
|
|
SVC-706 New Primitive/Object/Link functions
|
|
|
|
 |
|
SVC-93 llSetPrimitiveParams PRIM_ROTATION and llSetRot incorrectly implemented for child prims
|
|
|
|
|
|
|
MISC-428 Hierarchical linking of prim/objects
|
|
|
|
|
|
|
MISC-227 Implement optional prim-joint hierachy
|
|
|
|
|
|
|
MISC-969 New Feature: Prim Animations - Less laggy, smoother, avatar like, animations on prims
|
|
|
|
|
|
|
SVC-105 Script control for link sets (linked prims).
|
|
|
|
|
|
|
MISC-1434 Add an orientable linking capability
|
|
|
|
|
|
|
SVC-301 Meta-issue: New LSL Functions
|
|
|
|
|
|
|
MISC-398 Meta-Issue: Meta-Issue Organization
|
|
|
|
|
|
MISC-2639 Meta Issue: LSL3+ feature proposals
|
|
|
|
|
|
|
|
This meta-issue is supposed to advocate for hierarchical linking of objects as well as changes in scripting, that will most likely require a LSL3.
More about hierarchical linking: http://wiki.secondlife.com/wiki/Prim_and_Object_Hierarchy
The proper place for discussing these topics seems to be the "AWGroupies"-meeting and/or zero linden's office hours.
This is a meta-issue, covering a lot of different parts of the SL system, because the required changes cant be seen as individual small incremental feature-additions but must be looked at as a whole.
The scope of these changes might reach from a new "Edit linked Sub-Object"-checkbox in the SL Build menu for linked objects, to the opportunity to use bvh-animations for animating linked objects client-side. (maybe only phantom)
In general, hierarchical linking would be greatly empowering for content-creation and a very intuitive structure to build and modify objects by hand and by script.
Instead of each child-prim having a rotation and position relative to the root, each prim would have a rotation, an offset and a scale, relative to its parent.
Such a structure would be equivalent to "Nodes" in collada and other model-hierarchies.
Each prim, that is not root or leaf, could be used as joint.
To avoid interference with existing content, LSL3 should be considered once more.
To underline the real need for a LSL3, have a look at http://jira.secondlife.com/browse/SVC-93
It might be a good idea to think of LSL3 and hierarchical linking at the same time, because it could also suggest changes to link-messages and most likely other aspects of scripting.
Developing LSL3 and hierarchical linking together and restricted mixing with old content, would be very helpful for the poor developers who have to work on it and at the same time be a solid wall to protect existing content.
Sooner or later we NEED a brave Linden approaching this topic or SL will fall behind competing VWs, which will be using hierarchical models for objects.
Think of image-manipulation-software without support for layers. They wouldnt be around long, no matter how good the rest works.
|
|
Description
|
This meta-issue is supposed to advocate for hierarchical linking of objects as well as changes in scripting, that will most likely require a LSL3.
More about hierarchical linking: http://wiki.secondlife.com/wiki/Prim_and_Object_Hierarchy
The proper place for discussing these topics seems to be the "AWGroupies"-meeting and/or zero linden's office hours.
This is a meta-issue, covering a lot of different parts of the SL system, because the required changes cant be seen as individual small incremental feature-additions but must be looked at as a whole.
The scope of these changes might reach from a new "Edit linked Sub-Object"-checkbox in the SL Build menu for linked objects, to the opportunity to use bvh-animations for animating linked objects client-side. (maybe only phantom)
In general, hierarchical linking would be greatly empowering for content-creation and a very intuitive structure to build and modify objects by hand and by script.
Instead of each child-prim having a rotation and position relative to the root, each prim would have a rotation, an offset and a scale, relative to its parent.
Such a structure would be equivalent to "Nodes" in collada and other model-hierarchies.
Each prim, that is not root or leaf, could be used as joint.
To avoid interference with existing content, LSL3 should be considered once more.
To underline the real need for a LSL3, have a look at http://jira.secondlife.com/browse/SVC-93
It might be a good idea to think of LSL3 and hierarchical linking at the same time, because it could also suggest changes to link-messages and most likely other aspects of scripting.
Developing LSL3 and hierarchical linking together and restricted mixing with old content, would be very helpful for the poor developers who have to work on it and at the same time be a solid wall to protect existing content.
Sooner or later we NEED a brave Linden approaching this topic or SL will fall behind competing VWs, which will be using hierarchical models for objects.
Think of image-manipulation-software without support for layers. They wouldnt be around long, no matter how good the rest works. |
Show » |
made changes - 21/Jan/09 05:55 PM
| Field |
Original Value |
New Value |
|
Link
|
|
This issue Relates to MISC-227
[ MISC-227
]
|
made changes - 21/Jan/09 05:59 PM
|
Link
|
|
This issue Relates to MISC-969
[ MISC-969
]
|
made changes - 21/Jan/09 07:31 PM
|
Attachment
|
|
current.png
[ 21551
]
|
made changes - 21/Jan/09 07:34 PM
|
Description
|
This meta-issue is supposed to advocate for hierarchical linking of objects as well as changes in scripting, that will most likely require a LSL3.
The proper place for discussing these topics seems to be the "AWGroupies"-meeting and/or zero linden's office hours.
This is a meta-issue, covering a lot of different parts of the SL system, because the required changes cant be seen as individual small incremental feature-addition and must be looked at as a whole.
(related issues and explanatory pictures about hierarchical linking will be added here soon)
|
This meta-issue is supposed to advocate for hierarchical linking of objects as well as changes in scripting, that will most likely require a LSL3.
The proper place for discussing these topics seems to be the "AWGroupies"-meeting and/or zero linden's office hours.
This is a meta-issue, covering a lot of different parts of the SL system, because the required changes cant be seen as individual small incremental feature-addition and must be looked at as a whole.
|
made changes - 21/Jan/09 08:00 PM
|
Description
|
This meta-issue is supposed to advocate for hierarchical linking of objects as well as changes in scripting, that will most likely require a LSL3.
The proper place for discussing these topics seems to be the "AWGroupies"-meeting and/or zero linden's office hours.
This is a meta-issue, covering a lot of different parts of the SL system, because the required changes cant be seen as individual small incremental feature-addition and must be looked at as a whole.
|
This meta-issue is supposed to advocate for hierarchical linking of objects as well as changes in scripting, that will most likely require a LSL3.
The proper place for discussing these topics seems to be the "AWGroupies"-meeting and/or zero linden's office hours.
This is a meta-issue, covering a lot of different parts of the SL system, because the required changes cant be seen as individual small incremental feature-additions but must be looked at as a whole.
|
made changes - 21/Jan/09 08:08 PM
|
Link
|
|
This issue Relates to SVC-93
[ SVC-93
]
|
made changes - 21/Jan/09 08:12 PM
|
Link
|
|
This issue duplicates SVC-105
[ SVC-105
]
|
made changes - 21/Jan/09 08:12 PM
|
Link
|
This issue duplicates SVC-105
[ SVC-105
]
|
|
made changes - 21/Jan/09 08:12 PM
|
Link
|
|
This issue Relates to SVC-105
[ SVC-105
]
|
made changes - 21/Jan/09 08:16 PM
|
Link
|
|
This issue Relates to MISC-428
[ MISC-428
]
|
made changes - 21/Jan/09 08:21 PM
|
Link
|
|
This issue Relates to SVC-706
[ SVC-706
]
|
made changes - 21/Jan/09 08:29 PM
|
Link
|
|
This issue Relates to SVC-301
[ SVC-301
]
|
made changes - 21/Jan/09 09:29 PM
|
Description
|
This meta-issue is supposed to advocate for hierarchical linking of objects as well as changes in scripting, that will most likely require a LSL3.
The proper place for discussing these topics seems to be the "AWGroupies"-meeting and/or zero linden's office hours.
This is a meta-issue, covering a lot of different parts of the SL system, because the required changes cant be seen as individual small incremental feature-additions but must be looked at as a whole.
|
This meta-issue is supposed to advocate for hierarchical linking of objects as well as changes in scripting, that will most likely require a LSL3.
The proper place for discussing these topics seems to be the "AWGroupies"-meeting and/or zero linden's office hours.
This is a meta-issue, covering a lot of different parts of the SL system, because the required changes cant be seen as individual small incremental feature-additions but must be looked at as a whole.
The scope of these changes might reach from a new "Edit linked Sub-tree"-checkbox in the SL Build menu for linked objects, to the opportunity to use bvh-animations for animating linked objects.
|
made changes - 21/Jan/09 09:35 PM
|
Summary
|
Requiered additions and changes to objects and scripting, for improving content-creation capabilities.
|
[hierarchical linking] Requiered additions and changes to objects and scripting, for improving content-creation capabilities.
|
made changes - 21/Jan/09 09:53 PM
|
Description
|
This meta-issue is supposed to advocate for hierarchical linking of objects as well as changes in scripting, that will most likely require a LSL3.
The proper place for discussing these topics seems to be the "AWGroupies"-meeting and/or zero linden's office hours.
This is a meta-issue, covering a lot of different parts of the SL system, because the required changes cant be seen as individual small incremental feature-additions but must be looked at as a whole.
The scope of these changes might reach from a new "Edit linked Sub-tree"-checkbox in the SL Build menu for linked objects, to the opportunity to use bvh-animations for animating linked objects.
|
This meta-issue is supposed to advocate for hierarchical linking of objects as well as changes in scripting, that will most likely require a LSL3.
The proper place for discussing these topics seems to be the "AWGroupies"-meeting and/or zero linden's office hours.
This is a meta-issue, covering a lot of different parts of the SL system, because the required changes cant be seen as individual small incremental feature-additions but must be looked at as a whole.
The scope of these changes might reach from a new "Edit linked Sub-tree"-checkbox in the SL Build menu for linked objects, to the opportunity to use bvh-animations for animating linked objects.
To avoid interference with existing content, LSL3 should be considered once more.
To underline the real need for a LSL3, have a look at http://jira.secondlife.com/browse/SVC-93
It might be a good idea to think of LSL3 and hierarchical linking in the same breath, because it could also suggest changes to link-messages and most likely other aspects of scripting.
|
made changes - 21/Jan/09 10:01 PM
|
Description
|
This meta-issue is supposed to advocate for hierarchical linking of objects as well as changes in scripting, that will most likely require a LSL3.
The proper place for discussing these topics seems to be the "AWGroupies"-meeting and/or zero linden's office hours.
This is a meta-issue, covering a lot of different parts of the SL system, because the required changes cant be seen as individual small incremental feature-additions but must be looked at as a whole.
The scope of these changes might reach from a new "Edit linked Sub-tree"-checkbox in the SL Build menu for linked objects, to the opportunity to use bvh-animations for animating linked objects.
To avoid interference with existing content, LSL3 should be considered once more.
To underline the real need for a LSL3, have a look at http://jira.secondlife.com/browse/SVC-93
It might be a good idea to think of LSL3 and hierarchical linking in the same breath, because it could also suggest changes to link-messages and most likely other aspects of scripting.
|
This meta-issue is supposed to advocate for hierarchical linking of objects as well as changes in scripting, that will most likely require a LSL3.
The proper place for discussing these topics seems to be the "AWGroupies"-meeting and/or zero linden's office hours.
This is a meta-issue, covering a lot of different parts of the SL system, because the required changes cant be seen as individual small incremental feature-additions but must be looked at as a whole.
The scope of these changes might reach from a new "Edit linked Sub-Object"-checkbox in the SL Build menu for linked objects, to the opportunity to use bvh-animations for animating linked objects.
To avoid interference with existing content, LSL3 should be considered once more.
To underline the real need for a LSL3, have a look at http://jira.secondlife.com/browse/SVC-93
It might be a good idea to think of LSL3 and hierarchical linking at the same time, because it could also suggest changes to link-messages and most likely other aspects of scripting.
|
made changes - 21/Jan/09 10:23 PM
|
Description
|
This meta-issue is supposed to advocate for hierarchical linking of objects as well as changes in scripting, that will most likely require a LSL3.
The proper place for discussing these topics seems to be the "AWGroupies"-meeting and/or zero linden's office hours.
This is a meta-issue, covering a lot of different parts of the SL system, because the required changes cant be seen as individual small incremental feature-additions but must be looked at as a whole.
The scope of these changes might reach from a new "Edit linked Sub-Object"-checkbox in the SL Build menu for linked objects, to the opportunity to use bvh-animations for animating linked objects.
To avoid interference with existing content, LSL3 should be considered once more.
To underline the real need for a LSL3, have a look at http://jira.secondlife.com/browse/SVC-93
It might be a good idea to think of LSL3 and hierarchical linking at the same time, because it could also suggest changes to link-messages and most likely other aspects of scripting.
|
This meta-issue is supposed to advocate for hierarchical linking of objects as well as changes in scripting, that will most likely require a LSL3.
The proper place for discussing these topics seems to be the "AWGroupies"-meeting and/or zero linden's office hours.
This is a meta-issue, covering a lot of different parts of the SL system, because the required changes cant be seen as individual small incremental feature-additions but must be looked at as a whole.
The scope of these changes might reach from a new "Edit linked Sub-Object"-checkbox in the SL Build menu for linked objects, to the opportunity to use bvh-animations for animating linked objects client-side. (maybe only phantom)
This would be greatly empowering for content-creation and a very intuitive structure to build and modify objects by hand and by script.
Instead of each child-prim having a rotation and position relative to the root, each prim has a rotation and position relative to its parent.
Each prim, that is not root or leaf, could be used as joint.
To avoid interference with existing content, LSL3 should be considered once more.
To underline the real need for a LSL3, have a look at http://jira.secondlife.com/browse/SVC-93
It might be a good idea to think of LSL3 and hierarchical linking at the same time, because it could also suggest changes to link-messages and most likely other aspects of scripting.
|
made changes - 22/Jan/09 12:12 AM
|
Attachment
|
|
rotate.png
[ 21558
]
|
made changes - 22/Jan/09 12:13 AM
|
Attachment
|
|
linking.png
[ 21559
]
|
made changes - 22/Jan/09 12:14 AM
|
Attachment
|
|
conclusion.png
[ 21560
]
|
made changes - 22/Jan/09 12:16 AM
|
Attachment
|
conclusion.png
[ 21560
]
|
|
made changes - 22/Jan/09 12:50 AM
|
Description
|
This meta-issue is supposed to advocate for hierarchical linking of objects as well as changes in scripting, that will most likely require a LSL3.
The proper place for discussing these topics seems to be the "AWGroupies"-meeting and/or zero linden's office hours.
This is a meta-issue, covering a lot of different parts of the SL system, because the required changes cant be seen as individual small incremental feature-additions but must be looked at as a whole.
The scope of these changes might reach from a new "Edit linked Sub-Object"-checkbox in the SL Build menu for linked objects, to the opportunity to use bvh-animations for animating linked objects client-side. (maybe only phantom)
This would be greatly empowering for content-creation and a very intuitive structure to build and modify objects by hand and by script.
Instead of each child-prim having a rotation and position relative to the root, each prim has a rotation and position relative to its parent.
Each prim, that is not root or leaf, could be used as joint.
To avoid interference with existing content, LSL3 should be considered once more.
To underline the real need for a LSL3, have a look at http://jira.secondlife.com/browse/SVC-93
It might be a good idea to think of LSL3 and hierarchical linking at the same time, because it could also suggest changes to link-messages and most likely other aspects of scripting.
|
This meta-issue is supposed to advocate for hierarchical linking of objects as well as changes in scripting, that will most likely require a LSL3.
The proper place for discussing these topics seems to be the "AWGroupies"-meeting and/or zero linden's office hours.
This is a meta-issue, covering a lot of different parts of the SL system, because the required changes cant be seen as individual small incremental feature-additions but must be looked at as a whole.
The scope of these changes might reach from a new "Edit linked Sub-Object"-checkbox in the SL Build menu for linked objects, to the opportunity to use bvh-animations for animating linked objects client-side. (maybe only phantom)
This would be greatly empowering for content-creation and a very intuitive structure to build and modify objects by hand and by script.
Instead of each child-prim having a rotation and position relative to the root, each prim has a rotation and position relative to its parent.
Each prim, that is not root or leaf, could be used as joint.
To avoid interference with existing content, LSL3 should be considered once more.
To underline the real need for a LSL3, have a look at http://jira.secondlife.com/browse/SVC-93
It might be a good idea to think of LSL3 and hierarchical linking at the same time, because it could also suggest changes to link-messages and most likely other aspects of scripting.
In this context sculpt-to-sculpt stitching within a linkset could also be re-considered.
( https://jira.secondlife.com/browse/VWR-5189 )
|
made changes - 22/Jan/09 01:22 AM
|
Link
|
|
This issue Relates to MISC-398
[ MISC-398
]
|
made changes - 22/Jan/09 09:07 AM
|
Description
|
This meta-issue is supposed to advocate for hierarchical linking of objects as well as changes in scripting, that will most likely require a LSL3.
The proper place for discussing these topics seems to be the "AWGroupies"-meeting and/or zero linden's office hours.
This is a meta-issue, covering a lot of different parts of the SL system, because the required changes cant be seen as individual small incremental feature-additions but must be looked at as a whole.
The scope of these changes might reach from a new "Edit linked Sub-Object"-checkbox in the SL Build menu for linked objects, to the opportunity to use bvh-animations for animating linked objects client-side. (maybe only phantom)
This would be greatly empowering for content-creation and a very intuitive structure to build and modify objects by hand and by script.
Instead of each child-prim having a rotation and position relative to the root, each prim has a rotation and position relative to its parent.
Each prim, that is not root or leaf, could be used as joint.
To avoid interference with existing content, LSL3 should be considered once more.
To underline the real need for a LSL3, have a look at http://jira.secondlife.com/browse/SVC-93
It might be a good idea to think of LSL3 and hierarchical linking at the same time, because it could also suggest changes to link-messages and most likely other aspects of scripting.
In this context sculpt-to-sculpt stitching within a linkset could also be re-considered.
( https://jira.secondlife.com/browse/VWR-5189 )
|
This meta-issue is supposed to advocate for hierarchical linking of objects as well as changes in scripting, that will most likely require a LSL3.
More about hierarchical linking: http://wiki.secondlife.com/wiki/Prim_and_Object_Hierarchy
The proper place for discussing these topics seems to be the "AWGroupies"-meeting and/or zero linden's office hours.
This is a meta-issue, covering a lot of different parts of the SL system, because the required changes cant be seen as individual small incremental feature-additions but must be looked at as a whole.
The scope of these changes might reach from a new "Edit linked Sub-Object"-checkbox in the SL Build menu for linked objects, to the opportunity to use bvh-animations for animating linked objects client-side. (maybe only phantom)
This would be greatly empowering for content-creation and a very intuitive structure to build and modify objects by hand and by script.
Instead of each child-prim having a rotation and position relative to the root, each prim has a rotation and position relative to its parent.
Each prim, that is not root or leaf, could be used as joint.
To avoid interference with existing content, LSL3 should be considered once more.
To underline the real need for a LSL3, have a look at http://jira.secondlife.com/browse/SVC-93
It might be a good idea to think of LSL3 and hierarchical linking at the same time, because it could also suggest changes to link-messages and most likely other aspects of scripting.
In this context sculpt-to-sculpt stitching within a linkset could also be re-considered.
( https://jira.secondlife.com/browse/VWR-5189 )
|
made changes - 23/Jan/09 01:06 PM
|
Description
|
This meta-issue is supposed to advocate for hierarchical linking of objects as well as changes in scripting, that will most likely require a LSL3.
More about hierarchical linking: http://wiki.secondlife.com/wiki/Prim_and_Object_Hierarchy
The proper place for discussing these topics seems to be the "AWGroupies"-meeting and/or zero linden's office hours.
This is a meta-issue, covering a lot of different parts of the SL system, because the required changes cant be seen as individual small incremental feature-additions but must be looked at as a whole.
The scope of these changes might reach from a new "Edit linked Sub-Object"-checkbox in the SL Build menu for linked objects, to the opportunity to use bvh-animations for animating linked objects client-side. (maybe only phantom)
This would be greatly empowering for content-creation and a very intuitive structure to build and modify objects by hand and by script.
Instead of each child-prim having a rotation and position relative to the root, each prim has a rotation and position relative to its parent.
Each prim, that is not root or leaf, could be used as joint.
To avoid interference with existing content, LSL3 should be considered once more.
To underline the real need for a LSL3, have a look at http://jira.secondlife.com/browse/SVC-93
It might be a good idea to think of LSL3 and hierarchical linking at the same time, because it could also suggest changes to link-messages and most likely other aspects of scripting.
In this context sculpt-to-sculpt stitching within a linkset could also be re-considered.
( https://jira.secondlife.com/browse/VWR-5189 )
|
This meta-issue is supposed to advocate for hierarchical linking of objects as well as changes in scripting, that will most likely require a LSL3.
More about hierarchical linking: http://wiki.secondlife.com/wiki/Prim_and_Object_Hierarchy
The proper place for discussing these topics seems to be the "AWGroupies"-meeting and/or zero linden's office hours.
This is a meta-issue, covering a lot of different parts of the SL system, because the required changes cant be seen as individual small incremental feature-additions but must be looked at as a whole.
The scope of these changes might reach from a new "Edit linked Sub-Object"-checkbox in the SL Build menu for linked objects, to the opportunity to use bvh-animations for animating linked objects client-side. (maybe only phantom)
In general, hierarchical linking would be greatly empowering for content-creation and a very intuitive structure to build and modify objects by hand and by script.
Instead of each child-prim having a rotation and position relative to the root, each prim would have a rotation, an offset and a scale, relative to its parent.
Such a structure would be equivalent to "Nodes" in collada and other model-hierarchies.
Each prim, that is not root or leaf, could be used as joint.
To avoid interference with existing content, LSL3 should be considered once more.
To underline the real need for a LSL3, have a look at http://jira.secondlife.com/browse/SVC-93
It might be a good idea to think of LSL3 and hierarchical linking at the same time, because it could also suggest changes to link-messages and most likely other aspects of scripting.
Developing LSL3 and hierarchical linking together and restricted mixing with old content, would be very helpful for the poor developers who have to work on it and at the same time be a solid wall to protect existing content.
Sooner or later we NEED a brave Linden approaching this topic or SL will fall behind competing VWs, which will be using hierarchical models for objects.
Think of image-manipulation-software without support for layers. They wouldnt be around long, no matter how good the rest works.
|
made changes - 27/Jan/09 01:52 AM
|
Attachment
|
|
Prims_2_0.png
[ 21649
]
|
made changes - 27/Jan/09 01:56 AM
|
Attachment
|
Prims_2_0.png
[ 21649
]
|
|
|
Meta Issue
As such, I propose using XPath
for searching for prims and their attributes. XPath has good market penetration, it's not difficult to use and there is plenty of documentation on it.
I look forward to making LSL a sane language with LSL3. I would love to see getters and setters used instead of having to call specialized functions.
You can find a discussion of LSL3 here:
https://wiki.secondlife.com/wiki/LSL3