llCreateLink vs llForceLink

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

llCreateLink vs llForceLink

Dr Ramesh Ramloll
Hello,
I was wondering if there is any interest in having a function such as llForceLink. Often requests for permissions have a negative impact of flow of user interactions. That's why I tend to use forced attach functions for e.g. whenever I can. It really speeds up user engagement, and users do not have to wonder what is this permissions dialog box ...asking for permissions etc....  basically it is a distraction (and I doubt my casual users would even bother why it is needed). Of course there are cases where permissions are important, but I think it should be optional. Any thoughts?
R

--
'Consider how the lilies grow. They do not labor or spin.'
Rameshsharma Ramloll PhD, CEO CTO DeepSemaphore LLC, Affiliate Research Associate Professor, Idaho State University, Pocatello, ID 83209 Tel: 208-240-0040

_______________________________________________
Opensim-users mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/opensim-users
Reply | Threaded
Open this post in threaded view
|

Re: llCreateLink vs llForceLink

justincc
Sounds reasonable to me.  In this case, I think the function would be an OSSL called osForceCreateLink() to be
consistent with existing force functions and so it's possible to control whether and to whom it is available.

Wouldn't be hard to do - a small case of refactoring so that the OSSL function can call the parts of llCreateLink() that
are after the perms checks in the same way that a function such as osForceAttachToAvatar() does this.

If there's no further discussion I can look to create it next week, though you may need to prod me.  Or a patch to do
this would be very welcome.

On 01/03/14 16:17, Dr Ramesh Ramloll wrote:

> Hello,
> I was wondering if there is any interest in having a function such as llForceLink. Often requests for permissions have a
> negative impact of flow of user interactions. That's why I tend to use forced attach functions for e.g. whenever I can.
> It really speeds up user engagement, and users do not have to wonder what is this permissions dialog box ...asking for
> permissions etc....  basically it is a distraction (and I doubt my casual users would even bother why it is needed). Of
> course there are cases where permissions are important, but I think it should be optional. Any thoughts?
> R
>
> --
> 'Consider how the lilies grow. They do not labor or spin.'
> *Rameshsharma Ramloll* PhD, CEO CTO DeepSemaphore LLC, Affiliate /Research Associate Professor/, Idaho State University,
> Pocatello, ID 83209 Tel: 208-240-0040
> LinkedIn <http://www.linkedin.com/in/rameshramloll>, DeepSemaphore LLC <http://www.deepsemaphore.com>, RezMela
> <http://www.rezmela.com>, Google+ profile <https://plus.google.com/103652369558830540272/about>R
>
>
> _______________________________________________
> Opensim-users mailing list
> [hidden email]
> https://lists.berlios.de/mailman/listinfo/opensim-users
>


--
Justin Clark-Casey (justincc)
OSVW Consulting
http://justincc.org
http://twitter.com/justincc
_______________________________________________
Opensim-users mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/opensim-users
Reply | Threaded
Open this post in threaded view
|

Re: llCreateLink vs llForceLink

Dr Ramesh Ramloll
Thanks Justin for looking into this :)


On Tue, Mar 4, 2014 at 8:47 PM, Justin Clark-Casey <[hidden email]> wrote:
Sounds reasonable to me.  In this case, I think the function would be an OSSL called osForceCreateLink() to be consistent with existing force functions and so it's possible to control whether and to whom it is available.

Wouldn't be hard to do - a small case of refactoring so that the OSSL function can call the parts of llCreateLink() that are after the perms checks in the same way that a function such as osForceAttachToAvatar() does this.

If there's no further discussion I can look to create it next week, though you may need to prod me.  Or a patch to do this would be very welcome.


On 01/03/14 16:17, Dr Ramesh Ramloll wrote:
Hello,
I was wondering if there is any interest in having a function such as llForceLink. Often requests for permissions have a
negative impact of flow of user interactions. That's why I tend to use forced attach functions for e.g. whenever I can.
It really speeds up user engagement, and users do not have to wonder what is this permissions dialog box ...asking for
permissions etc....  basically it is a distraction (and I doubt my casual users would even bother why it is needed). Of
course there are cases where permissions are important, but I think it should be optional. Any thoughts?
R

--
'Consider how the lilies grow. They do not labor or spin.'
*Rameshsharma Ramloll* PhD, CEO CTO DeepSemaphore LLC, Affiliate /Research Associate Professor/, Idaho State University,

Pocatello, ID 83209 Tel: <a href="tel:208-240-0040" value="+12082400040" target="_blank">208-240-0040
LinkedIn <http://www.linkedin.com/in/rameshramloll>, DeepSemaphore LLC <http://www.deepsemaphore.com>, RezMela
<http://www.rezmela.com>, Google+ profile <https://plus.google.com/103652369558830540272/about>R


_______________________________________________
Opensim-users mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/opensim-users



--
Justin Clark-Casey (justincc)
OSVW Consulting
http://justincc.org
http://twitter.com/justincc
_______________________________________________
Opensim-users mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/opensim-users



--
'Consider how the lilies grow. They do not labor or spin.'
Rameshsharma Ramloll PhD, CEO CTO DeepSemaphore LLC, Affiliate Research Associate Professor, Idaho State University, Pocatello, ID 83209 Tel: 208-240-0040

_______________________________________________
Opensim-users mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/opensim-users