There are two parts - The first part is the re-routing of my Windows
app so that all UI goes to a central function - This function uses
TCP/IP and XML to communicate with the Ajax web side. Therefore, the
same app with the same source code can run as a Windows or web
client. When run as a web client, an app EXE is spawned for each
logged in user.
Intresting for example button function you use
randy_userinterface("button","test",{randy_action()}
inside randy_userinterface you have a function that is able to go to
win32 or use tcpip to webserver using ajax
I receive a button event (as XML) from the web side - I then simulate
this event in the app by posting a WM_LBUTTONDOWN and WM_LBUTTONUP
message to my event handler - At this point, my app does not care if
the event came from Windows of the Web.
you can't use get system as compatibility layer or any gt?
We tried to implement field masking (similar to the get system) but
it was too slow for each keystroke. Therefore, the user can enter
whatever they want into a field - As soon as they leave the field,
the field mask is enforced. If the data violates the field mask,
input focus remains on the field and the field mask is displayed so
the user knows how to enter the data.
Wich rdd are you using?
ADS (local), ADS (server) and SQL (Mediator).
Why When run as a web client, an app EXE is spawned for each logged in user?
We were not ready to convert our app to be multi-threaded so this
seemed like the best alternative and actually works quite well. We
may convert the app to be multi-threaded so that only a single app
instance is required per server. However, as mentioned, it runs very
well like this so we may just leave it as is - It's much simpler!
My app was originally written to centralize all UI to a common
place. Therefore, very little of my app needed to change - I simply
needed to re-route any UI code to a new place. I then simulate
Windows events (eg. user clicking on a button) when events come in
from the web - This allows all my message handling to remain
untouched. So, the code on the app side is fairly straight forward.
However, the Java/.NET code is VERY complex and sophisticated. We
originally wanted to target all browsers but there seemed to be too
many browser-specific issues so we opted for support of only IE 7/8
and FireFox 2/3.
and i think Google Chome in future becase is very good for speed
Harbour app uses TCP/IP and XML to communicate with the Ajax web side.
the server side is Java or wich languages of .NET ?
Have a little demo?
Not yet but soon...
Tell me informed
also same print screen will be very intresting
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
