Hello Jens and Susan,
just saw your discussion :-)
I think the main difference between Jens proposal and our tool is:
* He seems to think more in a direction of an explorer like
application to inspect the server
* Our tool is more about tracing data and logs + analysis +
visualization.
So probably a different use-case ?!?
Maybe we could share/align some effort on opc/ua ?
One idea that comes into my mind:
We plan to extend the OPC/UA extension with scripting support
(_javascript_ based; like the CANBus extension,...)
to enable the user to do things beyond the UI.
* To set Values
* call Functions
* handle changes
* do tests
* and so on
I think this would be also useful in an explorer like application.
Maybe from our tool, the explorer can be started, or vice versa.
There may be more...
thanks,
Thomas
On 26.02.2018 12:15, Susan Iway wrote:
The code is in the plg-in and on github (EPL) like
eclipse code is.
If i do a change, the maintainer needs to accept.
Or I clone and nobody needs to accept.
Cant see the difference.
Susan
I think offering to create
something new has nothing to do with
"truth" or any religious approach.
What if you want to make changes to
the "professional tool" itself? Can
you clone the git repo of that as
well? And make changes, bring them
back into the main distribution of
that tool? I guess not.
I think open source is not only about
being able to "read the source code",
but also about the ability to make
changes to a solution. That requires
some kind of a governance model, which
the Eclipse Foundation provides. Looking
at the OPC UA plugin you suggest, it is
advertised as the source is "Available
in the plugin package". That doesn't fit
my idea of open source.
Again, I think it is fine to create and sell
a closed source solution. Nothing is wrong
with that.
But starting to talk people out of
contributing to open source in favor of a
close source solution on the mailing list of
an open source project, that simply sounds
wrong to me. With that argument you could also
ask people to stop contributing to the Eclipse
IDE as there are other commercial offerings
available.
To cut that old "open source vs close source"
discussion short …
… if someone likes to buy that tool. Please to do
so.
… otherwise I am still looking forward to mentor a
GSoC project about creating an OPC UA explorer tool.
Jens
_______________________________________________ milo-dev
mailing list milo-dev@xxxxxxxxxxx To change your
delivery options, retrieve your password, or unsubscribe
from this list, visit https://dev.eclipse.org/mailman/listinfo/milo-dev
_______________________________________________
milo-dev mailing list
milo-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/milo-dev
|