Change the Repository name
mpostol opened this issue · comments
OPCUA is too broad and it is recognized as the Client/Server interoperability - I call it interactive networking.
This project must target reactive networking. OPC UA ( 20+ specifications) defines it only in Part 14.
My proposals:
- ReactiveNetworking.MobileHMI (see the project Networking.MobileHMI
- IoT.MobileHMI - because reactive networking is recognized as native communication for IoT application domain IoT versus SCADA/DCS Data Acquisition Patterns
Yes, I was wondering about the name of repository but after submitting the questionnaire I didn't want to change the name without consulting it as the link would be rendered invalid.
Hmm, I'm not sure about the Mobile part as we will be getting desktop versions automatically from Xamarin.Forms, hence I named it Cross so maybe:
- ReactiveNetworking.CrossPlaftormHMI
Good point. The problem is what is the goal, and what is the side effect. From the goals of the project we can read:
- The distance between the data source and the user.
For the desktop applications, it is not important. Harmonization of the screen content with the current geographical location is the main goal for this application case because it really adds value from the end users point of view.
Of course in the summary, we must stress that the solution is multiplatform, but as the result of the previous decision.
Anyway, it is up to you. It is your project.
As long as the project is private adding any link doesn't make sense - first, you must add GitHub pages to make something publicly visible.
There are some laptops that do have GPS built in for example and there are some that have detachable screens so they become similar to tablets. The boundary where Mobile ends and Desktop starts is quite blurry.
Mobile is primary target but it can work equally well with desktop with minimal effort given that it can provide GPS coordinates.
I meant the link on WIKAMP questionnaire.
I agree except devices equipped with the detachable screens. The only important feature of the applications domain in concern is the necessity to use variable location as a parameter to select the screen content.
WIKAMP is a resource that is not available for the audience of this repository after publishing, so let's avoid any discussion related to it.
Let's settle for ReactiveNetworking.CrossHMI