White Phoenix wrote:The internal, universal coding would be invisible to the users of the form.
You did miss one important point: the code itself should be visible to the users, who can copy-and-paste it around in forums, e-mails etc., and load it into whatever program they want.
Yes, you are correct. I have also started thinking about actual applications that this would be used for.
Here is a scenario:*
For example, I am developing a spreadsheet/program that would allow the user to test a team to see if it is in compliance with the venue they wish to play and then to check for strengths/weaknesses. Right now I am using OpenOffice Calc for the spreadsheet.
For another example, there is PokéSav. Unless I used the same language that PokéSav was written in, there would be no way for data from these two applications to be shared. PokéSav would save the data in its own format, but I would have to develop a version of my program that could use that output.
A third example would be Shoddy Battle. Which would not be able to use the output of either of the first two applications. Ideally, I would want the output of my program to be compatible with Shoddy Battle in order for it to be useful. Also output from Shoddy Battle should be compatible with my program.
The problem arises when I want output from my program to be compatible with PokéSav, Shoddy Battle and be able to be read in a post in a forum.
I am in the development stage of my program, so adapting to a standard would not be a real problem for me, but applications that are already in existence would need to adapt to the standard. That is going to be more difficult. The programmers of the various applications would have to agree to a standard then re-write their applications in order to comply (unless their application is already the standard).
Theoretically, a standard can work, but is it practical?
*I am only using these applications as examples and am not necessarily endorsing their use.