Hello,
This question relates to the LGPL version.
I’ve been hacking away with SmartClient over the past few weeks and believe that sometimes having access to the non obfuscated version of the source code at runtime would be helpful in debugging some tricky problems.
As part of my due diligence in evaluating the software, I’d also like to be sure that the source code matches the runtime (obfuscated) version.
I am aware from http://forums.smartclient.com/showthread.php?t=2037 that you use the FileAssembler internally to build the runtime (obfuscated and compressed) from the source. I understand that loading up the source directly may end up loading extremely slowly, however I’m prepared to accept this occasional limitation in order to allow me to debug some hard to track down bugs in my software.
I’ve noted that the source code is in the “source/” tree and that in the source/system/modules tree are files with conspicuously similar names to those in the “isomorphic/system/modules” tree. I spent a few minutes looking at the module files in the source tree and noted that they merely load up all of their included files using a simple array and document.write loop.
I’ve also noted that they load from the “system” directory which doesn’t actually exist, so as a quick hack I copied the client directory tree to an equivalent “system” directory tree. After then loading the source module files into my browser I was greeted by innumerable javascript syntax errors.
I believe that you are using the (non-LGPLed) FileAssembler to do this construction when you release the product, which may also be addressing the syntax errors. However, I have been unable to find any build documentation on how you have exactly configured the FileAssembler to do this. I’m not really keen on reverse engineering the module files into the XML syntax required run the FileAssembler.
I believe that to be truly “LGPL” it must be possible to build the runtime version from the supplied source code (even if this requires non-LGPL tools), or it must be possible to run directly from the source code (which I have been unable to do).
Can you provide further information on how I can independently verify that the obfuscated code was indeed constructed from the supplied source code? Can you provide details on how to run the source code directly, performance caveats noted?
On a related topic, the patch files are only supplied in their obfuscated form. Again, to be LGPL compliant, these should also be supplied in source code form.
Hopefully more and more developers will discover SmartClient and a community may build up to help debug issues and contribute new functionality. However, I don’t see the tools currently being provided making this a possibility for the time being.
And by the way, SmartClient is a great product with some great ideas! Keep up the good work and I look forward to seeing version 7.