Is there a way to mix LGPL and Pro?

[atomatom]

I'm sold on the utility of the server side parts of SmartGWT.

However, it drives me bananas having a client library in Javascript that is obfuscated. With the Pro version, there is no "Debug" mode and you cannot trace through javascript in the browser to understand where things are going wrong.

My question then, is can I mix the LGPL version with the Pro version?

Being able to tell where things are blowing up would give me better understanding of why the framework is not behaving. In the case of bugs, it would let me create my own patches - which I could submit to the LGPL project.

I posted this as a wish in the other forum. I am posting it here to ask if there is any way I can do this myself?

I wonder also if this is really in the spirit of the LGPL? Don't make me sing the Gnu song like Stallman. :) But seriously, I'd like to be able to modify and fix code, which is really where all this came from.

[Isomorphic]

Mixing won't work.

We plan *Debug versions of Pro modules but very, very few people want this and other highly requested things have to take priority.

If you're desperate, you can switch your DataSources over to RestDataSources via putting Constructor="RestDataSource" in your .ds.xml files and using a dataURL that points to the RestHandler. This should allow everything but eg exportData() and upload/download to work (including queuing as of 3.0).

But what you probably want to do is use a different debug methodology, or, post actual test cases instead of anecdotal information, which is less work on your end than JavaScript debugging anyway.

[atomatom]

Thanks for confirming that it won't work and the suggestion w.r.t. RestDataSource.

In terms of test cases, I do try and post as much information as I can within a reasonable time. I appreciate that you take the time to fix most of the bugs reported here. In the ideal world, I'd have a paid support contract, but that's not where I'm at yet.

Aside from debugging, the other main benefit is an understanding of how the client side framework operates so that I can extend it where I need to.