@Erel
In order to do a full separation of the CLI compiler and the GUI IDE, I would suggest the following:
Move the license checking code from the GUI IDE to the CLI complier. Have it check for a license in the same directory as the compiler each time it's run. If a license doesn't exist, then ask the user to either purchase a license or move their license into the directory of the CLI complier.
Change from .bal/.bil files to XML. (XML is more "open". Plus, XML is super-easy to create. Would also allow members to share UIs.".)
To make a B4i version work, I'd suggest the following:
[-local-builder "<ip.txt>"] argument. (Local Builder's IP Address would need to be in a text file called "ip.txt".)
[-remote-builder "<login.txt>"] argument. (Login details would need to be stored in a text file called "login.txt", or maybe even included in the license file.)
The future of Anywhere Software is going to be amazing!
Last edited: Jan 16, 2015