John Puccio wrote:Sometimes you need to do stuff client side that is just not possible or practical to do on the server. What I was suggesting is an ActiveX PB module so we could run native PB code client side. I wasn't suggesting an entire PB installation on the client. That would be silly. But a scaled down client side PB interpreter that installs in the browser would be really neat! Kind of like VBScript but with better (not MicroSoft) syntax!

Well, I only see 1 solution for this: Compile serverside and run the executable at the client's side.
1) A complete PB installation at the client side is tooooooo much overhead. Moreover, you could only use PB Demo version, as it is free for all.
2) I don't see a chance to even get a lite version of PB at the clients side. What you could leave away would be the manual and the example files and the IDE. But the remaining amount of data is still too much.
3) Even if you consider the way deswcribed in 1+2, you will be faced with the limitations of the Demoversion: No API, just 600-800 lines, always-on-debugger, etc.
In my opinion, a browser-plugin should upload a PB-code to the server. The server compiles it and passes the executable back to the client where it is executed. But obviously, it would be better, if the source code is stored server side too. This has 2 advantages: First, the plgin doesn't need to upload anything (it only tells the server how to compile: for windows, for linux, for mac, in 32 bits or 64 bits). Second, you cannot easily insert other codes to misuse the compiler.
// edit:
This solution requires at least 2 servers. A Linux server which could compile for Linux, a Windows server which compiles for Windows. And probably a Mac Server to support that platform. Still remaining would be all users who go online via mobile phone, too (like me).
Everybody must decide on his own, if this effort is worth it.