You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Emanuele Gesuato (JIRA)" <ji...@apache.org> on 2012/11/09 12:30:11 UTC
[jira] [Created] (FELIX-3751) junit4osgi swingrunner improvement
with a more flexible layout
Emanuele Gesuato created FELIX-3751:
---------------------------------------
Summary: junit4osgi swingrunner improvement with a more flexible layout
Key: FELIX-3751
URL: https://issues.apache.org/jira/browse/FELIX-3751
Project: Felix
Issue Type: Improvement
Components: iPOJO
Affects Versions: iPOJO-1.6.0
Environment: The problem affects either linux or windows oses.
Reporter: Emanuele Gesuato
Priority: Trivial
Attachments: new_swingrunner.zip
The junit4osgi SwingRunner JFrame is currently created with a fixed layout. So if you try to enlarge the JFrame the content of the panel remains "fixed" with its own width and height.
This improvement allow the user to have a more comfortable user experience with a flexible layout manager. If the user tries to resize the new jframe the content of the jframe will be resized.
It was not so simple to create it because the source files in the trunk repository were not "right". It seems they were missing the constructor with InstanceManager parameter. Also there are some methods that were missing: the OSGIJUnitRunner field was not setted in any place. The result of my work was done decompiling the .class of SwingRunner. The result of its decompiling was quite different from the source file because in the decompiled one I got the missing methods. It seems that the .class was generated from a different source file than the one present in the repository.
I saw that the jframe was designed with netbeans: is it possible that the ide "removed" some of the missing methods ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FELIX-3751) junit4osgi swingrunner improvement
with a more flexible layout
Posted by "Emanuele Gesuato (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-3751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emanuele Gesuato updated FELIX-3751:
------------------------------------
Attachment: org.apache.felix.ipojo.junit4osgi.swing-gui.zip
swingrunner improved with flexible layout and search facility
> junit4osgi swingrunner improvement with a more flexible layout
> --------------------------------------------------------------
>
> Key: FELIX-3751
> URL: https://issues.apache.org/jira/browse/FELIX-3751
> Project: Felix
> Issue Type: Improvement
> Components: iPOJO
> Affects Versions: iPOJO-1.6.0
> Environment: The problem affects either linux or windows oses.
> Reporter: Emanuele Gesuato
> Priority: Trivial
> Labels: junit
> Attachments: org.apache.felix.ipojo.junit4osgi.swing-gui.zip
>
>
> The junit4osgi SwingRunner JFrame is currently created with a fixed layout. So if you try to enlarge the JFrame the content of the panel remains "fixed" with its own width and height.
> This improvement allow the user to have a more comfortable user experience with a flexible layout manager. If the user tries to resize the new jframe the content of the jframe will be resized.
> It was not so simple to create it because the source files in the trunk repository were not "right". It seems they were missing the constructor with InstanceManager parameter. Also there are some methods that were missing: the OSGIJUnitRunner field was not setted in any place. The result of my work was done decompiling the .class of SwingRunner. The result of its decompiling was quite different from the source file because in the decompiled one I got the missing methods. It seems that the .class was generated from a different source file than the one present in the repository.
>
> I saw that the jframe was designed with netbeans: is it possible that the ide "removed" some of the missing methods ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FELIX-3751) junit4osgi swingrunner improvement
with a more flexible layout
Posted by "Emanuele Gesuato (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-3751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emanuele Gesuato updated FELIX-3751:
------------------------------------
Attachment: (was: new_swingrunner.zip)
> junit4osgi swingrunner improvement with a more flexible layout
> --------------------------------------------------------------
>
> Key: FELIX-3751
> URL: https://issues.apache.org/jira/browse/FELIX-3751
> Project: Felix
> Issue Type: Improvement
> Components: iPOJO
> Affects Versions: iPOJO-1.6.0
> Environment: The problem affects either linux or windows oses.
> Reporter: Emanuele Gesuato
> Priority: Trivial
> Labels: junit
> Attachments: org.apache.felix.ipojo.junit4osgi.swing-gui.zip
>
>
> The junit4osgi SwingRunner JFrame is currently created with a fixed layout. So if you try to enlarge the JFrame the content of the panel remains "fixed" with its own width and height.
> This improvement allow the user to have a more comfortable user experience with a flexible layout manager. If the user tries to resize the new jframe the content of the jframe will be resized.
> It was not so simple to create it because the source files in the trunk repository were not "right". It seems they were missing the constructor with InstanceManager parameter. Also there are some methods that were missing: the OSGIJUnitRunner field was not setted in any place. The result of my work was done decompiling the .class of SwingRunner. The result of its decompiling was quite different from the source file because in the decompiled one I got the missing methods. It seems that the .class was generated from a different source file than the one present in the repository.
>
> I saw that the jframe was designed with netbeans: is it possible that the ide "removed" some of the missing methods ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FELIX-3751) junit4osgi swingrunner improvement
with a more flexible layout
Posted by "Emanuele Gesuato (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-3751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emanuele Gesuato updated FELIX-3751:
------------------------------------
Affects Version/s: iPOJO-1.8.0
> junit4osgi swingrunner improvement with a more flexible layout
> --------------------------------------------------------------
>
> Key: FELIX-3751
> URL: https://issues.apache.org/jira/browse/FELIX-3751
> Project: Felix
> Issue Type: Improvement
> Components: iPOJO
> Affects Versions: iPOJO-1.6.0, iPOJO-1.8.0
> Environment: The problem affects either linux or windows oses.
> Reporter: Emanuele Gesuato
> Priority: Trivial
> Labels: junit
> Attachments: org.apache.felix.ipojo.junit4osgi.swing-gui.zip
>
>
> The junit4osgi SwingRunner JFrame is currently created with a fixed layout. So if you try to enlarge the JFrame the content of the panel remains "fixed" with its own width and height.
> This improvement allow the user to have a more comfortable user experience with a flexible layout manager. If the user tries to resize the new jframe the content of the jframe will be resized.
> It was not so simple to create it because the source files in the trunk repository were not "right". It seems they were missing the constructor with InstanceManager parameter. Also there are some methods that were missing: the OSGIJUnitRunner field was not setted in any place. The result of my work was done decompiling the .class of SwingRunner. The result of its decompiling was quite different from the source file because in the decompiled one I got the missing methods. It seems that the .class was generated from a different source file than the one present in the repository.
>
> I saw that the jframe was designed with netbeans: is it possible that the ide "removed" some of the missing methods ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FELIX-3751) junit4osgi swingrunner improvement
with a more flexible layout
Posted by "Emanuele Gesuato (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-3751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emanuele Gesuato updated FELIX-3751:
------------------------------------
Attachment: new_swingrunner.zip
new swing runner source files.
> junit4osgi swingrunner improvement with a more flexible layout
> --------------------------------------------------------------
>
> Key: FELIX-3751
> URL: https://issues.apache.org/jira/browse/FELIX-3751
> Project: Felix
> Issue Type: Improvement
> Components: iPOJO
> Affects Versions: iPOJO-1.6.0
> Environment: The problem affects either linux or windows oses.
> Reporter: Emanuele Gesuato
> Priority: Trivial
> Labels: junit
> Attachments: new_swingrunner.zip
>
>
> The junit4osgi SwingRunner JFrame is currently created with a fixed layout. So if you try to enlarge the JFrame the content of the panel remains "fixed" with its own width and height.
> This improvement allow the user to have a more comfortable user experience with a flexible layout manager. If the user tries to resize the new jframe the content of the jframe will be resized.
> It was not so simple to create it because the source files in the trunk repository were not "right". It seems they were missing the constructor with InstanceManager parameter. Also there are some methods that were missing: the OSGIJUnitRunner field was not setted in any place. The result of my work was done decompiling the .class of SwingRunner. The result of its decompiling was quite different from the source file because in the decompiled one I got the missing methods. It seems that the .class was generated from a different source file than the one present in the repository.
>
> I saw that the jframe was designed with netbeans: is it possible that the ide "removed" some of the missing methods ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira