Page 1 of 2

Close smart client.

PostPosted: Wed Jan 21, 2009 2:46 pm
by pcm
Hi All,
I am working on sample application in Servoy in this application i want to close smart client to another smart client.

Let i have server S where is my application deployed. I am accessing smart client on machine A as SC1 and machine B as SC2. Now i have two different client(SC1,SC2) on two different machine(A,B). Now i want to close SC2 of machine B from SC1 of machine A.

How can i make it possible?

We can do from the servoy admin page. I want to do from servoy script.

Thanks

Re: Close smart client.

PostPosted: Wed Jan 21, 2009 2:52 pm
by Joas
I think you can do that with Scott's Robot plugin.

Re: Close smart client.

PostPosted: Fri Jan 23, 2009 9:12 am
by pcm
Hi Joas,

I am getting following error, while i am clicking on JSClient option under servoyguy_robot.

error.PNG
error.PNG (61.62 KiB) Viewed 8982 times


I have downloaded latest version of robot_plugin.

Servoy Version: 4.1.0 - build 651
Java Version 6 update 11 (build 1.6.0_11-b03)


Thanks
Prem

Re: Close smart client.

PostPosted: Tue Jan 27, 2009 1:08 pm
by pcm
Hi All,

Is there any one from servoy or servoyguy who tell me. Why Servoyguy robot plugin is not working on my end? I had posted the error.

Thanks

Re: Close smart client.

PostPosted: Tue Jan 27, 2009 1:59 pm
by IT2Be
That is an issue with the Robot Plug-in using an old API I think.

Re: Close smart client.

PostPosted: Tue Jan 27, 2009 4:24 pm
by patrick
Yes, it is. This won't work in Servoy 4.

Re: Close smart client.

PostPosted: Tue Jan 27, 2009 9:24 pm
by Thomas Parry
I too am concerned as a user of the Robot and other plugins on Scott's site.
I am proposing that the robot plugin code be made accessible to the forum users so that we may correct it for version 4 and other issues that may arise.

Would Scott be amenable to placing the code into Google code (similar to the JasperReport plugin) and allowing one person to "be responsible" for its release etc?

It appears to me that there is potential for faster turnaround time due to issues if Scott is not interested in the maintenance side of it. So I am suggesting a community like approach to the maintenance of such code.

Please let the community know if the plugins on Scott's site are very private and cannot be allowed to be released into the public domain or what the situation is?

If other plugin developers have similar code in their arsenal could they respond with alternatives (paid or not).

Please discuss this issue of maintenance of closed code so we know were we stand. Perhaps the robot and other plugins are private or owned by Servoy?

Regards,
Tom

Re: Close smart client.

PostPosted: Tue Jan 27, 2009 9:37 pm
by sbutler
The Robot plugin uses and old API, and some private code which can't be released. Maybe someone should start a community effort to build such a plugin from scratch, as my source code wouldn't be of any use anyway. Maybe Marcel would consider building such a plugin if a group would commission him to do so.

Re: Close smart client.

PostPosted: Wed Jan 28, 2009 12:25 am
by IT2Be
Maybe Marcel would consider building such a plugin if a group would commission him to do so.
Always willing, in fact part of the technology is already included in the (still private ) Servlet Plugin.
I can not make it for free though. So when a couple of people want to sponsor the project I can make it 'lift off'...

Re: Close smart client.

PostPosted: Wed Jan 28, 2009 7:00 am
by pcm
Hi All,

patrick wrote:Yes, it is. This won't work in Servoy 4.
It is now working even in Servoy 3.5.2+. So we have forget robot_plugin.

What about the entire effort behind this plugin ?

Tom is right, Servoy or Servoyen doesn't want robot_plugin with the error. Some how it should bug free.

Thanks

Re: Close smart client.

PostPosted: Wed Jan 28, 2009 1:05 pm
by IT2Be
What about the entire effort behind this plugin ?

Tom is right, Servoy or Servoyen doesn't want robot_plugin with the error. Some how it should bug free.
I am going to step in for Scott here...
The Robot Plug-in was a free product from the beginning made by Scott in his spare time (I think it is even said on his website).
To maintain a product you need to have and be able to give it the time it deserves.

I do agree that developers started using the plugin, simply because is was there, should be able to do that.

Because of the above, I guess, Scott suggested that I take over the project.
However, when we would take it on without asking money for the work we would hurt other projects.

On the other hand, maybe somebody else wants to step in and do it for free...

When I start the project, I guarantee that it will be maintained as long as Servoy has an API for it...

I hope this clarifies things a bit.

Re: Close smart client.

PostPosted: Wed Jan 28, 2009 2:36 pm
by patrick
Since we had the same issues with the Robot plugin, we also built our own. I recently managed to get it to work under Servoy 4 as well. The functionality is currently part of an internal plugin, but could be more or less easily isolated. The API calls the plugin is using are not public. So I cannot publish a plugin like that "open source". Also, since the plugin uses a "few hacks" to work right, there is no guarantee it will work with future versions of Servoy.

Re: Close smart client.

PostPosted: Wed Jan 28, 2009 2:49 pm
by IT2Be
The functionality is currently part of an internal plugin
Seems like we do the same thing more than once :)
I cannot publish a plugin like that "open source"
But are you doing it for free? If not for free we make the same offer.
When you are willing to do this for free I am sure most of the Servoy Developers prefer your plugin...

Re: Close smart client.

PostPosted: Wed Jan 28, 2009 3:17 pm
by patrick
Marcel, you want to offer this as part of your (commercial) servlet-plugin?

Re: Close smart client.

PostPosted: Wed Jan 28, 2009 4:41 pm
by IT2Be
The basic client connection functionality will be on the server/servlet side of the Plug-in.

When requested the discussed functionality could be added as well but only as part of the above plugin and as a commercial project.

When you are willing to do it for free please be my guest.
I think the people in this thread would like to have it...
It is not that I am 'hungry' to take this on but more because these developers have to move on.