The server sends textual information – not graphics, I am using standard http requests and exposed to any known hole, I am using a unique token (similar to the ASP.NET session id mechanism), some of my customers installed it under https protocol for better safety.
I built it as add-on to VS and am using VS+C# for development and debugging.
In the beginning I used native run time environments.
It took me a while to develop a steady and fast HTML run time that works in all major browsers; for now all my desktop clients are using it. The main trick was building a generic ASP.NET site that helps the JS with the heavy staff.
I am not sure I understood the question about copy and paste text.
There are many more issues I had to deal with; I think it worth a face to face meeting, demonstration and explanation.
No doubt that designing with tag/XML language and adding handlers with code is the most popular way of developing a front-end.
JS is bad, it creates spaghetti code and multi thread mess.
But a big question is whether XAML+C# is better than XML+Java for android?
XAML is lot more sophisticated but it is hard to learn, there for only developers that had crossed over this barrier love it – but it is a big barrier.
XAML+C# is popular among organizations that can organize and afford courses and support for their programmers; and it limited for inside use.
The issue is that the market demand HTML for desktop and native for mobile and you cannot fight this.
Couple of multi-platforms tools tries to give a generic XAML+C# and compiles it to different platforms, but it is not an easy task, first of all the C# that you know is rely on .Net and iOS and Android don't support it, each one has a totally different framework. Farther more - those tools don't support HTML.
The Approach of my tool is to translate textual information to UI (like any Internet Browser can do) and to run the code behind at the server so it run with the latest .Net framework regardless the user device O/S – users can work native or HTML.
@Marc Roussel, no it is not what Razor Engine does, it is an object that include controls, properties and code behind (like WPF or any other UI technology) but at run-time instead of creating an instance on the user device it creates the instance on the server.
@Marc, you are right and it is a shame that the industry did not adopt Silverlight as a standard.
From my reach experience I can assure you that nothing is event close to Silverlight or WPF.
I believe that the programmer job is to teach the computer what it should do in the most simple and clean way.
Silverlight (or WPF), Binding, XAML, BLEND and C# are the best set of tools that I know to develop a front-end,
But application is not front-end alone it has also backend - my goal was to find the best way to teach the computer what the whole application should do.
So, Silverlight (or WPF), Binding, XAML, BLEND and C# are good start, but instead of controls that run on the front-end and render graphics, I developed controls that run on the backend and render textual information that can be translated automatically to any platform.
@mike with dotNetify you build your UI as HTML they give nice 2-Way data binding I find some similarity to Angular and to the binding idea of WPF.
My tool is completely different you build your UI with generic controls on the server, you can put data directly to the control.
Just imagine that you are working on a standard .net project on the backend and can use directly controls like TextBox, TextBlock Grid, Button, Camera, GPS – that simple.
@mike what I meant it that my solution uses standard HTTP protocol over ASP.NET and IIS in order to get and send information to the client with the latest framework therefore I am limited to those abilities. If IIS can support Millions concurrent users so do I,
I have an actual application with Hundreds concurrent users. It installed on a single IIS server on a virtual machine and work fine.
I don't familiar with the server load/scale problem that you asked about.
No problem to address these two aspects and it is proven with solutions I delivered.
1) Is the same scaling as ASP.NET – see no problem with big solution – and also can be installed on IIS server farm.
2) The same code run for Windows, iOS, Android and HTML. I am sure Avalonia and Noesis worked hard to achieve it because they need to compile the code to different platforms, for me it is easy – the code run on the same server for all platforms.
@Mike I took a different approach, I developed a library of client controls that run on the server.
Programmers work with the whole .NET framework and are able to combine client and server components – for example in the onClick handler you can use sqlConnection and a TextBlock – The code run on the server.
My controls do not render graphics instead they send information to the client. It is similar to WebControls of ASP.NET but with different way of rendering and sending information.
In order to run the app - in the client machine I have a generic native app or JS that can translate the information into native UI or HTML and send back to the server information about the client's events.
For you question whether my is better the answer is depended. For games and real-time I will not use my solution yet. But for enterprise solutions and web sites it is not just better it is a game changer.
Mike-EEE, maybe one day I will get mass following/branding/awareness – I am building now an online multi-platform application and database generator. I have other projects for paying customers and it will take some time.
I develop my concept as addon for VS and am using it for some time, am sure it is the "real deal", it is not just the multi-platform ability it is far beyond that and if MSFT will not even review – it is their lost.
I am posting it to this forum in order to find the right person in MSFT
I already develop project like this, it works and already delivered solutions, just searching the right person from Microsoft to review and adopt.
My project offers more than just generic client that can run in many platforms.
There are logical objects on the server that represents UI and other equipment on the end device.
The result is a single logical object that include the whole application including the exact design, events and business logic.
The development process become significantly easier because programmers are not required to separate front-end and backend any more.
It opens endless new abilities for developing powerful stuff that combine client and server resources (like MS-Access).
For me it is a proven concept I work years on this and had delivered dozens of solutions some of them are big and sophisticated.
For demonstration or any question email@example.com
1 voteYoram Bucks shared this idea ·