On 13 October 2011 13:46, Johannes Buchner <buchner.johannes@...> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> On 10/13/2011 02:05 PM, Arnaud Delobelle wrote:
>> On 13 October 2011 09:28, Johannes Buchner
>> <buchner.johannes@...> wrote:
>>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>>> On 10/13/2011 09:42 AM, Arnaud Delobelle wrote:
>>>> Hi all,
>>>> I am embedding jython into GeoGebra, an interactive
>>>> algebra/geometry software , in order to use it as a
>>>> scripting language for users. The project is still in its
>>>> early days but show potential (see ). One issue is that
>>>> Proguard is used in GeoGebra releases to obfuscate names (only
>>>> to save space, as GeoGebra is GPL and everybody has access to
>>>> the source), which creates a problem for jython scripts! I am
>>>> not sure how to tackle this issue and would be grateful for
>>>> some guidance.
>>>> The only solution I can think of at the moment [...]
>>> There is another, obvious solution. Don't obfuscate.
>>> See proguard -dontobfuscate
>> Thank you for the suggestion. Unfortunately, I can't do this.
> - From the Proguard page it is pretty clear that obfuscation only brings
> minuscule improvements, and most of the work is done by shrinking +
> optimization, so your motivation to insist on obfuscation is unclear
> to me.
> Of course you could write a script that creates Proxy classes from the
> Java code, but it will make your code difficult to understand and
> maintain (not to say obfuscated).
> It also looks like Proguard has quite sophisticated -keep* options,
> that would allow you to specify all public-facing (API) classes
> without listing them -- see the example with Serializable on the Usage
Hi Johannes. Thanks for the precisions. As a understand it, GeoGebra
has a sophisticated build process which has been refined over the
years. I am not in a position to modify it myself (and I certainly do
not understand it fully) but I will forward your comments.