You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cayenne.apache.org by "Thomas Bernhard (JIRA)" <de...@cayenne.apache.org> on 2007/10/26 18:46:51 UTC

[JIRA] Created: (CAY-906) CM Usability: Use AppFramework - JSR-296 - to simplify the code

CM Usability: Use AppFramework - JSR-296 - to simplify the code
---------------------------------------------------------------

                 Key: CAY-906
                 URL: https://issues.apache.org/cayenne/browse/CAY-906
             Project: Cayenne
          Issue Type: New Feature
          Components: CayenneModeler GUI
            Reporter: Thomas Bernhard
            Assignee: Andrus Adamchik


Please use for CM the new AppFramework:
https://appframework.dev.java.net/ 
i.e. JSR-296 http://jcp.org/en/jsr/detail?id=296

This framework can greatly simplify the code impose good coding conventions for Swing apps, it will be part of the JDK (but untill than it still does the same job as a library), it's small and it's already supported/integrated by many tools/frameworks:
- NB 6 supports it out of the box
- even the well known JGoodies supports it now: http://jgoodies.com/downloads/changes.html 


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Re: [JIRA] Commented: (CAY-906) CM Usability: Use AppFramework - JSR-296 - to simplify the code

Posted by Andrus Adamchik <an...@objectstyle.org>.
On Oct 26, 2007, at 8:50 PM, Thomas Bernhard wrote:

>> Well, until then it is most definitely a problem.
>>
> Well, I don't understand why Apache is so picky about this entire LGPL
> thing, considering that in most cases such libraries will be only  
> used, not
> changed.

We are an Apache project so we do follow the licensing policy of the  
Foundation.

At the high level, the goal of this policy is rather simple - to only  
distribute software that is compatible with a certain "BSD'ish" open  
source license style. Why any given license is deemed compatible or  
not is a separate story, and I'd rather avoid arguing about it here  
(there is a legal-discuss list where that would be more appropriate).

> And if even SUN (or others that use this library) don't care:here's
> a quote from the AppFramework list:

They don't care because they own the code all the way and only they  
can change the license. This is the difference between Sun and us in  
this case.

I do regret that we can't use this framework until Java 7 (from the  
first glance it seems nice), but well... we can't.

Andrus


Re: [JIRA] Commented: (CAY-906) CM Usability: Use AppFramework - JSR-296 - to simplify the code

Posted by Thomas Bernhard <tb...@yahoo.com>.

Andrus Adamchik wrote:
> 
>>> LGPL is a no go for Cayenne inclusion
>> I don't think this should be a problem(if for SUN it's not) as it's  
>> just a temporary state until it's included into the JDK.
> 
> Well, until then it is most definitely a problem.
> 
Well, I don't understand why Apache is so picky about this entire LGPL
thing, considering that in most cases such libraries will be only used, not
changed. And if even SUN (or others that use this library) don't care:here's
a quote from the AppFramework list:


>> I'm curious why the LGPL license is being used for this project  
>> rather than the BSD or Apache license?  I do not believe that Java  
>> SE 6 distribution (http://java.sun.com/javase/6/javase-6- 
>> thirdpartyreadme.txt) included any LGPL licenses.  If this JSR is  
>> intended to be included with Java SE 7 does it plan to be  
>> distributed under a different license?
> 
> Not necessarily. Since Sun owns the copyright to all the code in app  
> framework, beans binding, swingx, etc. we can change the license if  
> included in Java SE. That's one reason why we require the JCA/CA to  
> be signed before we can accept code in these projects from external  
> contributors.
> 
> Richard
> 

Tom.
-- 
View this message in context: http://www.nabble.com/-JIRA--Created%3A-%28CAY-906%29-CM-Usability%3A-Use-AppFramework---JSR-296---to-simplify-the-code-tf4698490.html#a13432321
Sent from the Cayenne - Dev mailing list archive at Nabble.com.


[JIRA] Commented: (CAY-906) CM Usability: Use AppFramework - JSR-296 - to simplify the code

Posted by "Andrus Adamchik (JIRA)" <de...@cayenne.apache.org>.
    [ https://issues.apache.org/cayenne/browse/CAY-906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12568 ] 

Andrus Adamchik commented on CAY-906:
-------------------------------------

Looks nice, but there are a few issues with that:

* LGPL is a no go for Cayenne inclusion (is there another implementation under a different license?)
* Rearchitecture of the Modeler would require more resources than I think we can dedicate (unless new volunteers step in)
* Also worth looking into how this would play with our (still unimplemented) desire to switch to a plugin-based architecture.

> CM Usability: Use AppFramework - JSR-296 - to simplify the code
> ---------------------------------------------------------------
>
>                 Key: CAY-906
>                 URL: https://issues.apache.org/cayenne/browse/CAY-906
>             Project: Cayenne
>          Issue Type: New Feature
>          Components: CayenneModeler GUI
>            Reporter: Thomas Bernhard
>            Assignee: Andrus Adamchik
>
> Please use for CM the new AppFramework:
> https://appframework.dev.java.net/ 
> i.e. JSR-296 http://jcp.org/en/jsr/detail?id=296
> This framework can greatly simplify the code impose good coding conventions for Swing apps, it will be part of the JDK (but untill than it still does the same job as a library), it's small and it's already supported/integrated by many tools/frameworks:
> - NB 6 supports it out of the box
> - even the well known JGoodies supports it now: http://jgoodies.com/downloads/changes.html 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (CAY-906) CM Usability: Use AppFramework - JSR-296 - to simplify the code

Posted by "Andrus Adamchik (JIRA)" <de...@cayenne.apache.org>.
     [ https://issues.apache.org/cayenne/browse/CAY-906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrus Adamchik closed CAY-906.
-------------------------------

       Resolution: Won't Fix
    Fix Version/s: 3.0

Unfortunately we can not overcome the LGPL limitation as long as we are shipping the Modeler from Apache. If the ASF policies change in the future, we may revisit this.

> CM Usability: Use AppFramework - JSR-296 - to simplify the code
> ---------------------------------------------------------------
>
>                 Key: CAY-906
>                 URL: https://issues.apache.org/cayenne/browse/CAY-906
>             Project: Cayenne
>          Issue Type: New Feature
>          Components: CayenneModeler GUI
>            Reporter: Thomas Bernhard
>            Assignee: Andrus Adamchik
>             Fix For: 3.0
>
>
> Please use for CM the new AppFramework:
> https://appframework.dev.java.net/ 
> i.e. JSR-296 http://jcp.org/en/jsr/detail?id=296
> This framework can greatly simplify the code impose good coding conventions for Swing apps, it will be part of the JDK (but untill than it still does the same job as a library), it's small and it's already supported/integrated by many tools/frameworks:
> - NB 6 supports it out of the box
> - even the well known JGoodies supports it now: http://jgoodies.com/downloads/changes.html 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Re: [JIRA] Commented: (CAY-906) CM Usability: Use AppFramework - JSR-296 - to simplify the code

Posted by Andrus Adamchik <an...@objectstyle.org>.
On Oct 26, 2007, at 8:06 PM, Thomas Bernhard (JIRA) wrote:

>
>> LGPL is a no go for Cayenne inclusion
> I don't think this should be a problem(if for SUN it's not) as it's  
> just a temporary state until it's included into the JDK.

Well, until then it is most definitely a problem.

>> Rearchitecture of the Modeler would require more resources than I  
>> think we can dedicate
> I'm not an expert but I think AppFramework is very "non-invasive",  
> i.e. one can use is step by step.
> In many cases it requires only to add a few annotation to code and  
> voila - magic is happening :).

Yeah, looking through the docs a bit more, I think I agree.

Andrus



[JIRA] Commented: (CAY-906) CM Usability: Use AppFramework - JSR-296 - to simplify the code

Posted by "Thomas Bernhard (JIRA)" <de...@cayenne.apache.org>.
    [ https://issues.apache.org/cayenne/browse/CAY-906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12569 ] 

Thomas Bernhard commented on CAY-906:
-------------------------------------

> LGPL is a no go for Cayenne inclusion
I don't think this should be a problem(if for SUN it's not) as it's just a temporary state until it's included into the JDK.

> Rearchitecture of the Modeler would require more resources than I think we can dedicate 
I'm not an expert but I think AppFramework is very "non-invasive", i.e. one can use is step by step.
In many cases it requires only to add a few annotation to code and voila - magic is happening :).

> Also worth looking into how this would play with our (still unimplemented) desire to switch to a plugin-based architecture.
I don't think this has something to do with plug-ins, nor does it intefere with them - it's all about a good sturcture, and few conventions and annotations to make applications simpler.

> CM Usability: Use AppFramework - JSR-296 - to simplify the code
> ---------------------------------------------------------------
>
>                 Key: CAY-906
>                 URL: https://issues.apache.org/cayenne/browse/CAY-906
>             Project: Cayenne
>          Issue Type: New Feature
>          Components: CayenneModeler GUI
>            Reporter: Thomas Bernhard
>            Assignee: Andrus Adamchik
>
> Please use for CM the new AppFramework:
> https://appframework.dev.java.net/ 
> i.e. JSR-296 http://jcp.org/en/jsr/detail?id=296
> This framework can greatly simplify the code impose good coding conventions for Swing apps, it will be part of the JDK (but untill than it still does the same job as a library), it's small and it's already supported/integrated by many tools/frameworks:
> - NB 6 supports it out of the box
> - even the well known JGoodies supports it now: http://jgoodies.com/downloads/changes.html 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.