Ladies and Gentlemen
As Black Adder used to say, "I have a cunning plan”
and thought you might find it useful.
Unfortunately I cannot post any code as my work belongs to my employer. However, I came up with the original idea before he hired me. Since he refuses to look at Powerbasic then I guess it is his loss.
I will explain the concept in broad terms and then you are on your own. Some feedback would be nice.
When speed of the GUI is not an issue we can use a web browser as our GUI front-end. Here is how…
We write all the application's logic in Powerbasic and compile it into an .exe. When the plication is invoked, it will show a very simple Dialog/Splash screen (simple stuff in DDT). If necessary, we ask for username and password here. Then the program will detect and show the IP address of the PC (in large friendly letters
). The program then invokes the browser and “serves” a “default.html” file to the browser and minimises itself. What is in the browser is our application’s main “screen”.
The program then enters the main loop and monitors “Port 80” for user interaction. The entire user interface is handled through HTML pages and a browser. The program either dynamically builds the HTML pages in memory or retrieves them from the disk and modifies them through text substitution.
The advantages are many. Here are some of them…
1. We do not need to worry about Windows messages and callback functions any more.
2. We do not need to learn DDT or API and the complexities of Windows GUI. Just HTML/XML.
3. As HTML and XML standards evolve we can do better and better user interfaces.
4. Our applications can be content driven.
5. We can change the user interface very quickly.
Of course this is not appropriate for every application and there are many disadvantages too
.
Obviously performance is a major consideration, but as someone suggested before, many applications sit idle most of the time while the user or the database back-end do their bit.
This option will give us total independence from Windows native GUI and can be used with any language. PB/CC and PB/DLL are obviously among the best.
The fact that these programs can also communicate with other similar programs through “Port 80” over any TCP/IP connection should open interesting avenues for distributed computing.
If the concept is successful then Bob Zale and his team can consider introducing native support for this model at the compiler level.
I know this sounds quite revolutionary and GUI elements in a browses are not as mature as Windows native GUI. But lateral thinking never hurt anyone.
Siamack
[This message has been edited by Siamack Yousofi (edited March 06, 2000).]
As Black Adder used to say, "I have a cunning plan”

Unfortunately I cannot post any code as my work belongs to my employer. However, I came up with the original idea before he hired me. Since he refuses to look at Powerbasic then I guess it is his loss.

I will explain the concept in broad terms and then you are on your own. Some feedback would be nice.

When speed of the GUI is not an issue we can use a web browser as our GUI front-end. Here is how…
We write all the application's logic in Powerbasic and compile it into an .exe. When the plication is invoked, it will show a very simple Dialog/Splash screen (simple stuff in DDT). If necessary, we ask for username and password here. Then the program will detect and show the IP address of the PC (in large friendly letters

The program then enters the main loop and monitors “Port 80” for user interaction. The entire user interface is handled through HTML pages and a browser. The program either dynamically builds the HTML pages in memory or retrieves them from the disk and modifies them through text substitution.
The advantages are many. Here are some of them…
1. We do not need to worry about Windows messages and callback functions any more.
2. We do not need to learn DDT or API and the complexities of Windows GUI. Just HTML/XML.
3. As HTML and XML standards evolve we can do better and better user interfaces.
4. Our applications can be content driven.
5. We can change the user interface very quickly.
Of course this is not appropriate for every application and there are many disadvantages too

Obviously performance is a major consideration, but as someone suggested before, many applications sit idle most of the time while the user or the database back-end do their bit.
This option will give us total independence from Windows native GUI and can be used with any language. PB/CC and PB/DLL are obviously among the best.
The fact that these programs can also communicate with other similar programs through “Port 80” over any TCP/IP connection should open interesting avenues for distributed computing.
If the concept is successful then Bob Zale and his team can consider introducing native support for this model at the compiler level.

I know this sounds quite revolutionary and GUI elements in a browses are not as mature as Windows native GUI. But lateral thinking never hurt anyone.

Siamack
[This message has been edited by Siamack Yousofi (edited March 06, 2000).]
Comment