When a user logins, can he automatically and systematically execute a "startup script", which would send a question box asking whether s/he wants to "get webcams" (which the script would then enable or not, based on the answer) ?
A long time ago, when assessing the need for an in-world editor
window, I wrote in a way to save such a script. There's such a thing
as a "client script editor" accessible from the tools menu. Executing
any script in this window, not only executes the script but saves it
to /scripts/startup.ez within that client's .wonderland directory (but
no others). I was afraid that people would experiment with it, write a
script that would go terribly wrong, and then be potentially locked
out of the wonderland client if I executed it on startup, so I left
that part out, not that it's particularly hard to re-enable, however.
To address your specific case, that of webcams and the like. Webcams
are highly dependent upon the JavaCV-Integration module. Further,
since I rarely work in Linux land, I never put the opencv and javacv
linux x86/x64 libraries into the module, hoping there would be
interest elsewhere in the community to do it for me. So for starters,
that particular module only supports Mac and Windows (maybe only
windows 7, not sure though). That said, there's another issue
regarding revealing that API to the scripting land. I can either make
EZScript depend on it, make it depend on EZScript, or create a third
module which depends on both. The third module seems to be the most
elegant but I would consider it rather bloated for such a small amount
of functionality. Perhaps it is worth it for some...
Bottom-line, I can re-enable the start-up execution. If absolutely
required, I can make a third module called
ezscript-javacv-integration, but in doing so I would strongly
encourage a donation be made to the Open Wonderland Foundation.
On Fri, Jun 29, 2012 at 3:14 PM, micheldenis <michel.m.de...@gmail.com> wrote:
> Ryan,
> When a user logins, can he automatically and systematically execute a
> "startup script", which would send a question box asking whether s/he wants
> to "get webcams" (which the script would then enable or not, based on the
> answer) ?
First of all, thank you very much for dealing with my crazy (but business-real) questions.
Un-deterministic behavior due to modern technology is not something business customers often accept.
For this reason I am looking for an alternative.
* Regarding your first idea:
Actually the sys admin would create a script which should apply for any user, hence it would not be created by each user, nor be stored in each user's local .wonderland
Thus I have the impression that the "client script editor" component would not be very useful in my case.
Question: is there a way for sys admins to oblige all users to execute a given script (probably to be located on the server) each time they log in ?
* Regarding your second idea:
Dealing with users' webcams is a very special domain by itself. People from Big Blue Button open source community have worked a lot in the domain of webcams, and they even use red5 in their software. Their webcams can be accessed using web strings like:
http://94.23.248.182/bigbluebutton/api/join?meetingID=1234&password=o... Just simple, except the script or program needs to get the username and calculate a Sha1 checksum, based on known parameters except the username, then pack the whole together and open the URL. For this reason I don't see the need to use Javacv & other packages, as the functionality exists already for years in BBB and is working fine. Cooperation between open source communities isn't it ?
Question: do you think it is a big deal to clone the Clickable link so that instead of taking the link property it would just pick up the username of the client, calculates the Sha1, and creates the string to be passed as URL to the browser ? I never wrote such program, that's why I am asking ..
> A long time ago, when assessing the need for an in-world editor
> window, I wrote in a way to save such a script. There's such a thing
> as a "client script editor" accessible from the tools menu. Executing
> any script in this window, not only executes the script but saves it
> to /scripts/startup.ez within that client's .wonderland directory (but
> no others). I was afraid that people would experiment with it, write a
> script that would go terribly wrong, and then be potentially locked
> out of the wonderland client if I executed it on startup, so I left
> that part out, not that it's particularly hard to re-enable, however.
> To address your specific case, that of webcams and the like. Webcams
> are highly dependent upon the JavaCV-Integration module. Further,
> since I rarely work in Linux land, I never put the opencv and javacv
> linux x86/x64 libraries into the module, hoping there would be
> interest elsewhere in the community to do it for me. So for starters,
> that particular module only supports Mac and Windows (maybe only
> windows 7, not sure though). That said, there's another issue
> regarding revealing that API to the scripting land. I can either make
> EZScript depend on it, make it depend on EZScript, or create a third
> module which depends on both. The third module seems to be the most
> elegant but I would consider it rather bloated for such a small amount
> of functionality. Perhaps it is worth it for some...
> Bottom-line, I can re-enable the start-up execution. If absolutely
> required, I can make a third module called
> ezscript-javacv-integration, but in doing so I would strongly
> encourage a donation be made to the Open Wonderland Foundation.
> best regards,
> -jW
> On Fri, Jun 29, 2012 at 3:14 PM, micheldenis <michel.m.de...@gmail.com> wrote:
>> Ryan,
>> When a user logins, can he automatically and systematically execute a
>> "startup script", which would send a question box asking whether s/he wants
>> to "get webcams" (which the script would then enable or not, based on the
>> answer) ?
I have no intention at this time to expose client startup scripts to
the server layer.
If you would like to use Big Blue Button, go for it, but unforunately,
I can't support it. My employer had a need not to use Big Blue Button,
and as such I needed to engineer a different implementation. That
implementation is the only one I'm prepared to support at this time.
I can't imagine it would be terribly hard to clone the Clickable link
capability to do what you describe.
On Fri, Jun 29, 2012 at 3:58 PM, Michel DENIS <michel.m.de...@gmail.com> wrote:
> Ryan,
> First of all, thank you very much for dealing with my crazy (but
> business-real) questions.
> Un-deterministic behavior due to modern technology is not something business
> customers often accept.
> For this reason I am looking for an alternative.
> * Regarding your first idea:
> Actually the sys admin would create a script which should apply for any
> user, hence it would not be created by each user, nor be stored in each
> user's local .wonderland
> Thus I have the impression that the "client script editor" component would
> not be very useful in my case.
> Question: is there a way for sys admins to oblige all users to execute a
> given script (probably to be located on the server) each time they log in ?
> * Regarding your second idea:
> Dealing with users' webcams is a very special domain by itself. People from
> Big Blue Button open source community have worked a lot in the domain of
> webcams, and they even use red5 in their software. Their webcams can be
> accessed using web strings like:
> http://94.23.248.182/bigbluebutton/api/join?meetingID=1234&password=o... > Just simple, except the script or program needs to get the username and
> calculate a Sha1 checksum, based on known parameters except the username,
> then pack the whole together and open the URL. For this reason I don't see
> the need to use Javacv & other packages, as the functionality exists already
> for years in BBB and is working fine. Cooperation between open source
> communities isn't it ?
> Question: do you think it is a big deal to clone the Clickable link so that
> instead of taking the link property it would just pick up the username of
> the client, calculates the Sha1, and creates the string to be passed as
> URL to the browser ? I never wrote such program, that's why I am asking ..
> Thanks,
> -michel
> jagwire a écrit :
> Michel,
> Finally, someone has asked this question :).
> A long time ago, when assessing the need for an in-world editor
> window, I wrote in a way to save such a script. There's such a thing
> as a "client script editor" accessible from the tools menu. Executing
> any script in this window, not only executes the script but saves it
> to /scripts/startup.ez within that client's .wonderland directory (but
> no others). I was afraid that people would experiment with it, write a
> script that would go terribly wrong, and then be potentially locked
> out of the wonderland client if I executed it on startup, so I left
> that part out, not that it's particularly hard to re-enable, however.
> To address your specific case, that of webcams and the like. Webcams
> are highly dependent upon the JavaCV-Integration module. Further,
> since I rarely work in Linux land, I never put the opencv and javacv
> linux x86/x64 libraries into the module, hoping there would be
> interest elsewhere in the community to do it for me. So for starters,
> that particular module only supports Mac and Windows (maybe only
> windows 7, not sure though). That said, there's another issue
> regarding revealing that API to the scripting land. I can either make
> EZScript depend on it, make it depend on EZScript, or create a third
> module which depends on both. The third module seems to be the most
> elegant but I would consider it rather bloated for such a small amount
> of functionality. Perhaps it is worth it for some...
> Bottom-line, I can re-enable the start-up execution. If absolutely
> required, I can make a third module called
> ezscript-javacv-integration, but in doing so I would strongly
> encourage a donation be made to the Open Wonderland Foundation.
> best regards,
> -jW
> On Fri, Jun 29, 2012 at 3:14 PM, micheldenis <michel.m.de...@gmail.com>
> wrote:
> Ryan,
> When a user logins, can he automatically and systematically execute a
> "startup script", which would send a question box asking whether s/he wants
> to "get webcams" (which the script would then enable or not, based on the
> answer) ?
> I have no intention at this time to expose client startup scripts to
> the server layer.
Wouldn't it be great and very natural to enable sys admin to create some common startup script for all users ?
> If you would like to use Big Blue Button, go for it, but unforunately,
> I can't support it. My employer had a need not to use Big Blue Button,
> and as such I needed to engineer a different implementation. That
> implementation is the only one I'm prepared to support at this time.
Actually I am not a fan of BBB and I would love to use your solution technology for that. My users just want the possibility to view users' webcams on their machine (PC or Mac):
- a webcams networking solution is running (based on red5 or anything else)
- at login each user chooses to use (ie send and show) webcams on or not, or they activate that using a menu item or clicking on an object (if and only if the click is always kicking up the script or program).
Is your implementation offering that ?
> I can't imagine it would be terribly hard to clone the Clickable link
> capability to do what you describe.
> On Fri, Jun 29, 2012 at 3:58 PM, Michel DENIS <michel.m.de...@gmail.com> wrote:
>> Ryan,
>> First of all, thank you very much for dealing with my crazy (but
>> business-real) questions.
>> Un-deterministic behavior due to modern technology is not something business
>> customers often accept.
>> For this reason I am looking for an alternative.
>> * Regarding your first idea:
>> Actually the sys admin would create a script which should apply for any
>> user, hence it would not be created by each user, nor be stored in each
>> user's local .wonderland
>> Thus I have the impression that the "client script editor" component would
>> not be very useful in my case.
>> Question: is there a way for sys admins to oblige all users to execute a
>> given script (probably to be located on the server) each time they log in ?
>> * Regarding your second idea:
>> Dealing with users' webcams is a very special domain by itself. People from
>> Big Blue Button open source community have worked a lot in the domain of
>> webcams, and they even use red5 in their software. Their webcams can be
>> accessed using web strings like:
>> http://94.23.248.182/bigbluebutton/api/join?meetingID=1234&password=o... >> Just simple, except the script or program needs to get the username and
>> calculate a Sha1 checksum, based on known parameters except the username,
>> then pack the whole together and open the URL. For this reason I don't see
>> the need to use Javacv & other packages, as the functionality exists already
>> for years in BBB and is working fine. Cooperation between open source
>> communities isn't it ?
>> Question: do you think it is a big deal to clone the Clickable link so that
>> instead of taking the link property it would just pick up the username of
>> the client, calculates the Sha1, and creates the string to be passed as
>> URL to the browser ? I never wrote such program, that's why I am asking ..
>> Thanks,
>> -michel
>> jagwire a �crit :
>> Michel,
>> Finally, someone has asked this question :).
>> A long time ago, when assessing the need for an in-world editor
>> window, I wrote in a way to save such a script. There's such a thing
>> as a "client script editor" accessible from the tools menu. Executing
>> any script in this window, not only executes the script but saves it
>> to /scripts/startup.ez within that client's .wonderland directory (but
>> no others). I was afraid that people would experiment with it, write a
>> script that would go terribly wrong, and then be potentially locked
>> out of the wonderland client if I executed it on startup, so I left
>> that part out, not that it's particularly hard to re-enable, however.
>> To address your specific case, that of webcams and the like. Webcams
>> are highly dependent upon the JavaCV-Integration module. Further,
>> since I rarely work in Linux land, I never put the opencv and javacv
>> linux x86/x64 libraries into the module, hoping there would be
>> interest elsewhere in the community to do it for me. So for starters,
>> that particular module only supports Mac and Windows (maybe only
>> windows 7, not sure though). That said, there's another issue
>> regarding revealing that API to the scripting land. I can either make
>> EZScript depend on it, make it depend on EZScript, or create a third
>> module which depends on both. The third module seems to be the most
>> elegant but I would consider it rather bloated for such a small amount
>> of functionality. Perhaps it is worth it for some...
>> Bottom-line, I can re-enable the start-up execution. If absolutely
>> required, I can make a third module called
>> ezscript-javacv-integration, but in doing so I would strongly
>> encourage a donation be made to the Open Wonderland Foundation.
>> best regards,
>> -jW
>> On Fri, Jun 29, 2012 at 3:14 PM, micheldenis <michel.m.de...@gmail.com>
>> wrote:
>> Ryan,
>> When a user logins, can he automatically and systematically execute a
>> "startup script", which would send a question box asking whether s/he wants
>> to "get webcams" (which the script would then enable or not, based on the
>> answer) ?
These ideas are all novel and I can see high value in them being a
part of the Wonderland experience.
The problem I'm trying to allude to is, they're incredibly time
consuming to engineer a well written and high-in-value solution,
rather than a hacked in file into a module. I can't speak for others,
but my involvement in the Wonderland community is largely volunteer
and non-profit. Often, general requirements [and less often, other
project's requirements] align nicely with the iSocial project, so I'm
able to kill two birds with one stone...that is to say, develop
something while I'm at work and give back to the community at the same
time. While I wish it could, being a volunteer doesn't let me cater to
every requirement that other projects have...especially those
commercial in nature. It would likely be in your best interest to hire
your own developer or make a donation to the Open Wonderland
Foundation so that they may provide you with one.
On Fri, Jun 29, 2012 at 4:49 PM, Michel DENIS <michel.m.de...@gmail.com> wrote:
> Hi Ryan, please see in-line:
> jagwire a écrit :
> Michel,
> I have no intention at this time to expose client startup scripts to
> the server layer.
> Wouldn't it be great and very natural to enable sys admin to create some
> common startup script for all users ?
> If you would like to use Big Blue Button, go for it, but unforunately,
> I can't support it. My employer had a need not to use Big Blue Button,
> and as such I needed to engineer a different implementation. That
> implementation is the only one I'm prepared to support at this time.
> Actually I am not a fan of BBB and I would love to use your solution
> technology for that. My users just want the possibility to view users'
> webcams on their machine (PC or Mac):
> - a webcams networking solution is running (based on red5 or anything else)
> - at login each user chooses to use (ie send and show) webcams on or not, or
> they activate that using a menu item or clicking on an object (if and only
> if the click is always kicking up the script or program).
> Is your implementation offering that ?
> I can't imagine it would be terribly hard to clone the Clickable link
> capability to do what you describe.
> The last solution I would consider but ..
> regards,
> -jW
> Many thanks Ryan,
> -michel
> On Fri, Jun 29, 2012 at 3:58 PM, Michel DENIS <michel.m.de...@gmail.com>
> wrote:
> Ryan,
> First of all, thank you very much for dealing with my crazy (but
> business-real) questions.
> Un-deterministic behavior due to modern technology is not something business
> customers often accept.
> For this reason I am looking for an alternative.
> * Regarding your first idea:
> Actually the sys admin would create a script which should apply for any
> user, hence it would not be created by each user, nor be stored in each
> user's local .wonderland
> Thus I have the impression that the "client script editor" component would
> not be very useful in my case.
> Question: is there a way for sys admins to oblige all users to execute a
> given script (probably to be located on the server) each time they log in ?
> * Regarding your second idea:
> Dealing with users' webcams is a very special domain by itself. People from
> Big Blue Button open source community have worked a lot in the domain of
> webcams, and they even use red5 in their software. Their webcams can be
> accessed using web strings like:
> http://94.23.248.182/bigbluebutton/api/join?meetingID=1234&password=o... > Just simple, except the script or program needs to get the username and
> calculate a Sha1 checksum, based on known parameters except the username,
> then pack the whole together and open the URL. For this reason I don't see
> the need to use Javacv & other packages, as the functionality exists already
> for years in BBB and is working fine. Cooperation between open source
> communities isn't it ?
> Question: do you think it is a big deal to clone the Clickable link so that
> instead of taking the link property it would just pick up the username of
> the client, calculates the Sha1, and creates the string to be passed as
> URL to the browser ? I never wrote such program, that's why I am asking ..
> Thanks,
> -michel
> jagwire a écrit :
> Michel,
> Finally, someone has asked this question :).
> A long time ago, when assessing the need for an in-world editor
> window, I wrote in a way to save such a script. There's such a thing
> as a "client script editor" accessible from the tools menu. Executing
> any script in this window, not only executes the script but saves it
> to /scripts/startup.ez within that client's .wonderland directory (but
> no others). I was afraid that people would experiment with it, write a
> script that would go terribly wrong, and then be potentially locked
> out of the wonderland client if I executed it on startup, so I left
> that part out, not that it's particularly hard to re-enable, however.
> To address your specific case, that of webcams and the like. Webcams
> are highly dependent upon the JavaCV-Integration module. Further,
> since I rarely work in Linux land, I never put the opencv and javacv
> linux x86/x64 libraries into the module, hoping there would be
> interest elsewhere in the community to do it for me. So for starters,
> that particular module only supports Mac and Windows (maybe only
> windows 7, not sure though). That said, there's another issue
> regarding revealing that API to the scripting land. I can either make
> EZScript depend on it, make it depend on EZScript, or create a third
> module which depends on both. The third module seems to be the most
> elegant but I would consider it rather bloated for such a small amount
> of functionality. Perhaps it is worth it for some...
> Bottom-line, I can re-enable the start-up execution. If absolutely
> required, I can make a third module called
> ezscript-javacv-integration, but in doing so I would strongly
> encourage a donation be made to the Open Wonderland Foundation.
> best regards,
> -jW
> On Fri, Jun 29, 2012 at 3:14 PM, micheldenis <michel.m.de...@gmail.com>
> wrote:
> Ryan,
> When a user logins, can he automatically and systematically execute a
> "startup script", which would send a question box asking whether s/he wants
> to "get webcams" (which the script would then enable or not, based on the
> answer) ?
> Thanks,
> -michel
> --
> Michel DENIS
> Président, Internet 3 Solutions SAS
> Tél: 06.72.87.17.50
> michel.de...@internet3solutions.com
> http://www.internet3solutions.com/
