|
Replies:
27
-
Last Post:
Aug 10, 2008 10:30 PM
by: rah003
|
|
|
|
|
|
|
swingx.jar getting smaller
Posted:
Jul 27, 2008 2:46 PM
|
|
|
just to let you know:
I've removed all bean infos from the swingx.jar. They now reside in their own swingx-beaninfo.jar and thanks to that, swingx.jar is about 200KB smaller. Apart from the little size decrease of the main jar we should also get better integration with NetBeans.
Cheers,
Jan
|
|
|
|
|
|
|
Re: swingx.jar getting smaller
Posted:
Jul 28, 2008 8:07 AM
in response to: rah003
|
|
|
Thank you! I was always looking for a way to make Swingx.jar smaller without having to manually remove stuff. 200K less is very good! Do you know when this will be released?
|
|
|
|
|
|
|
|
|
Re: swingx.jar getting smaller
Posted:
Jul 28, 2008 11:35 AM
in response to: carcour
|
|
|
Weekly build will be available on Sunday, next release ... if there is enough demand I can do it perhaps before the end of August.
Before that I would also like to split painters in their own jar if not in their own project with its own release cycle.
|
|
|
|
|
|
|
|
|
Re: swingx.jar getting smaller
Posted:
Jul 29, 2008 1:34 AM
in response to: rah003
|
|
|
A Bit OT: Where can i find the Maven Packages of SwingX ?
|
|
|
|
|
|
|
|
|
Re: swingx.jar getting smaller
Posted:
Jul 29, 2008 10:15 AM
in response to: mac_systems
|
|
|
0.9.1 and 0.9.2 releases are in central maven repo, 0.9.3 (binary only) is in java.net maven repo. I hoped that java.net maven repo would be synced with central, but it doesn't seem to be the case, so I'll have to setup our own and sync it with central repo to get future releases there.
|
|
|
|
|
|
|
|
|
How to build for Netbeans
Posted:
Jul 30, 2008 2:30 AM
in response to: rah003
|
|
|
About this change, will this mean you shouldn't use the swingx.jar to merge into Netbeans palette going forward, but always prefer the nbm? (has the wiki page been updated?)
Also how do you build the nbm? tried 'ant nbm' on a snapshot from this morning and I get:
BUILD FAILED
C:\Java\swingx\build.xml:54: java.lang.IllegalArgumentException
- Richard
|
|
|
|
|
|
|
|
|
Re: How to build for Netbeans
Posted:
Jul 30, 2008 8:05 AM
in response to: osbald
|
|
|
This change was actually requested from NetBeans team and they are working now on the integration. Once they are ready I'm sure they will explain how adding should work with this structure.
Apart from that I think adding it to the palette should work same way as now, you only have to ensure that apart from all the jars in lib/optional you have also swingx-beaninfo.jar on the classpath for the library.
|
|
|
|
|
|
|
|
|
Re: How to build for Netbeans
Posted:
Jul 30, 2008 8:06 AM
in response to: rah003
|
|
|
Either way the beaninfo stuff is irrelevant for normal application use and 200K gain in size seems to me worth the hassle.
|
|
|
|
|
|
|
|
|
Re: How to build for Netbeans
Posted:
Jul 30, 2008 8:40 AM
in response to: rah003
|
|
|
Ah, so the instructions aren't the same. My existing palette bound to just swingx.jar appears to have lost all it's beaninfo (editors, icons etc..). Where do I put swingx-beaninfo.jar to get it on the Netbeans classpath? Adding it to my project classpath dosn't make much sense? Some of the utility classes and editors swept-up in the process could be of use, but the beaninfo isn't (unless you're a gui builder). You can only add from a single jar, you don't get to choose a classpath. The library (nbm?) build is broken at the moment? So I should manually create my own library from the two jars (never tried)? I thought this change was supposed to make life easier? winge winge <g>
Wouldn't adding swingx.jar to the swingx-beaninfo.jar manifest make life easier? (assuming that works for Netbeans too?) then the two jars would just have to be in the same directory.. like dist? While I'm at it what about adding swingworker and swinglayout (and optionals)? to a swingx.jar manifest classpath? or are these frowned upon in libraries?
In any case swingx.jar has a main class defined that isn't present and wouldn't make much sense even if it did. Not the demo - which'd be too big anyway.
|
|
|
|
|
|
|
|
|
Re: How to build for Netbeans
Posted:
Jul 30, 2008 9:10 AM
in response to: osbald
|
|
|
OK that wasn't so tricky - mostly follow http://wiki.java.net/bin/view/Javadesktop/SwingXIDE although don't add your new Library to your project if you don't need the beaninfo (might need two SwingX libraries? how are conflicts resolved - Netbeans already bundles swinglayout, appframework & beansbindings).
Finally If like me you've been adding to the palette directly from the swingx.jar you'll need to delete them all and re-add from the (beaninfo inclusive) Library instead. Hadn't been into Libraries before and I'm probably confusing the term Library with nbm.. don't have a clue what you'd use them for then.
Only dip into Netbeans for the GUI builder, still can't stand editing in the thing and If I didn't use a gui builder I'd end up being pinged for every little spelling mistake and cosmetic change (even worse trying to reverse engineer a juniors layout sins). Otherwise it'd be GridBag all the way for me, hmmm a baseline GridBag would be quite nice. Really should try JFormDesigner someday..
|
|
|
|
|
|
|
|
|
Re: How to build for Netbeans
Posted:
Jul 30, 2008 2:05 PM
in response to: osbald
|
|
|
If this is about what I'm thinking about, it's about my little
javabeans -> NetBeans palette module generator:
http://weblogs.java.net/blog/timboudreau/archive/2006/04/got_javabeans_h.html
which I later turned into an Ant task as well:
http://weblogs.java.net/blog/timboudreau/archive/2007/02/generate_a_netb.html
A quick fix for generating the NetBeans module (possibly the only
fix?) would be to patch the swingx build script to generate a single
true design-time jar for swingx that includes everything in one JAR,
and use that to build the nbm file.
The tool that generates it could perhaps be enhanced to contain
multiple jars, so a separate beaninfo JAR could be embedded, but the
resulting UI inside NetBeans wouldn't be terribly pretty (the user
would see two libraries, SwingX and SwingX-Beaninfo or something like
that, and without changes, the default would be to end up with both
bundled in your application). Since most of the world seems to accept
the (somewhat loathsome, but nonetheless...) idea of design-time vs.
run-time jars, that seems the way to solve it.
There *might* be a way to hack around with the metadata to avoid
having two "libraries" in the UI, but I'm not 100% confident it
wouldn't have other issues (there are "jar" type libraries which don't
show up in the UI, but need hard-coded paths), and getting the IDE not
to bundle the beaninfo when you build might be an issue.
-Tim
On Jul 30, 2008, at 11:40 AM, jdnc-interest@javadesktop.org wrote:
> Ah, so the instructions aren't the same. My existing palette bound
> to just swingx.jar appears to have lost all it's beaninfo (editors,
> icons etc..). Where do I put swingx-beaninfo.jar to get it on the
> Netbeans classpath? Adding it to my project classpath dosn't make
> much sense? Some of the utility classes and editors swept-up in the
> process could be of use, but the beaninfo isn't (unless you're a gui
> builder). You can only add from a single jar, you don't get to
> choose a classpath. The library (nbm?) build is broken at the
> moment? So I should manually create my own library from the two jars
> (never tried)? I thought this change was supposed to make life
> easier? winge winge <g>
>
> Wouldn't adding swingx.jar to the swingx-beaninfo.jar manifest make
> life easier? (assuming that works for Netbeans too?) then the two
> jars would just have to be in the same directory.. like dist? While
> I'm at it what about adding swingworker and swinglayout (and
> optionals)? to a swingx.jar manifest classpath? or are these frowned
> upon in libraries?
>
> In any case swingx.jar has a main class defined that isn't present
> and wouldn't make much sense even if it did. Not the demo - which'd
> be too big anyway.
> [Message sent by forum member 'osbald' (osbald)]
>
> http://forums.java.net/jive/thread.jspa?messageID=290380
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
> For additional commands, e-mail: jdnc-help@jdnc.dev.java.net
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net
|
|
|
|
|
|
|
|
|
Re: How to build for Netbeans
Posted:
Jul 30, 2008 11:57 PM
in response to: Tim Boudreau
|
|
|
Hi guys,
I have to admit that I'm confused: as far as I understood Jan, the
swinglabs-beaninfo was broken out because of a request from the Netbeans
team. And now it turns out that it's practically impossible (except for
the very experienced, patient and daring developer) to use SwingX in
Netbean's builder because there are two jars?
Jeanette
---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net
|
|
|
|
|
|
|
|
|
Re: How to build for Netbeans
Posted:
Jul 31, 2008 2:35 AM
in response to: Kleopatra
|
|
|
> I have to admit that I'm confused
I think most of the confusion was mine, mostly because I didn't fully read the wiki documentation and continued to do the easiest thing which was import via a jar file. Which won't work now Netbeans needs two. I also confused the term 'Library' with the nbm target and the discussions about the NBM (NetBeans Module) generator - probably because the default Libraries are mostly from modules.
But actually they appear to perform two functions. They allow global library definitions (classpath, src & docs) that Netbeans itself appears to have access to, but also can be added to your projects. Which is why I thought you'd possibly need two libraries one with swingx-beanfo (for Netbeans) and one without (for Projects) otherwise Netbeans might try bundling swingx-beaninfo with your dist builds, web start dists etc.. voiding any size-reduction benefits. You could always avoid the 2nd Library and add swingx.jar (plus others) to your projects as individual jars every time.. Also added a bit of worry about possible conflicts with swingx dependencies and what Netbeans already bundles (esp if you define two copies).
What isn't clear to me is whether this is a stepping stone? are we waiting on the Netbeans team to come up with something better? or is this it? Are they intending to bundle swingx with Netbeans? or offer releases via the autoupdate?
Also pointed out that specifying our classpath dependencies in the jar manifests might be useful, but I wasn't sure how other developers feel about them.
..and the documentation for Netbeans integration hasn't been updated in the wiki nor swinglabs (is swinglabs.org hopelessly out-of-date?)
..and the nbm target in the swingx build script was broken.
..and swingx.jar manifest had an odd main-class definition.
The latter three should probably be raised as issues.
|
|
|
|
|
|
|
|
|
Re: How to build for Netbeans
Posted:
Jul 31, 2008 7:59 AM
in response to: osbald
|
|
|
jdnc-interest@javadesktop.org schrieb:
> ..and the documentation for Netbeans integration hasn't been updated in the wiki nor swinglabs (is swinglabs.org hopelessly out-of-date?)
>
> ..and the nbm target in the swingx build script was broken.
>
> ..and swingx.jar manifest had an odd main-class definition.
>
> The latter three should probably be raised as issues.
>
probably - and once the procedure is clear, somebody should update the
wiki (not me! 
Jeanette
---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net
|
|
|
|
|
|
|
|
|
Re: swingx.jar getting smaller
Posted:
Jul 30, 2008 8:00 AM
in response to: rah003
|
|
|
jdnc-interest@javadesktop.org schrieb:
> just to let you know:
> I've removed all bean infos from the swingx.jar. They now reside in their own swingx-beaninfo.jar and thanks to that, swingx.jar is about 200KB smaller.
a nice side-effect is that test coverage jumped up - if we kicked out
everything with coverage near zero, we probably would be very near the
final target 
Jeanette
---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net
|
|
|
|
|
|
|
|
|
Re: swingx.jar getting smaller
Posted:
Aug 4, 2008 4:47 AM
in response to: rah003
|
|
|
jdnc-interest@javadesktop.org schrieb:
> just to let you know:
> I've removed all bean infos from the swingx.jar.
just noticed that they are still in the javadoc. Looks like littering to
me - so would suggest to remove (that is not creating or separately
creating java doc for those)
Jeanette
---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net
|
|
|
|
|
|
|
|
|
Re: swingx.jar getting smaller
Posted:
Aug 4, 2008 6:05 AM
in response to: Kleopatra
|
|
|
> separately creating java doc for those
Don't forget to include links to the core javadocs if you do - would that make it an extra six minutes?
|
|
|
|
|
|
|
|
|
Re: swingx.jar getting smaller
Posted:
Aug 4, 2008 11:18 PM
in response to: osbald
|
|
|
> > separately creating java doc for those
>
> Don't forget to include links to the core javadocs if you do - would that make it an extra six minutes?
I don't think so. As far as I'm concerned there is no value in beaninfo's javadoc. I'll go through it again to double check, but right now i think it will not be generated it at all.
|
|
|
|
|
|
|
|
|
Re: swingx.jar getting smaller
Posted:
Aug 4, 2008 11:37 PM
in response to: rah003
|
|
|
jdnc-interest@javadesktop.org schrieb:
> I don't think so. As far as I'm concerned there is no value in beaninfo's javadoc. I'll go through it again to double check, but right now i think it will not be generated it at all.
>
you mean I'm seeing white elephants? Like BeanSupportInfo,
HorizontalLayoutBeanInfo, JXBusyLabelBeanInfo ... could go on forever
Cheers
Jeanette
---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net
|
|
|
|
|
|
|
|
|
Re: swingx.jar getting smaller
Posted:
Aug 4, 2008 11:41 PM
in response to: rah003
|
|
|
oh ... what happened to the weekly doc? seems to create (part or
complete) core doc as well ... maybe that's the extra minutes
Jeanette
---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net
|
|
|
|
|
|
|
|
|
Re: swingx.jar getting smaller
Posted:
Aug 4, 2008 11:43 PM
in response to: Kleopatra
|
|
|
Kleopatra schrieb:
>
> ... maybe that's the extra minutes
>
many minutes - the last weekly took over 20.
Jeanette
---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net
|
|
|
|
|
|
|
|
|
Re: swingx.jar getting smaller
Posted:
Aug 5, 2008 2:25 AM
in response to: rah003
|
|
|
How do you modify the build script Jan? I thought it was a Netbeans build so does that limit your changes to aspects the IDE exposes? do you risk losing modifications it the IDE regenerates sections?
Or do you have separate build scripts for hudon continuous, weeklies etc..? if so are those in the project? are those the poms? how do they get used? dare I ask if the builds are documented anywhere..
|
|
|
|
|
|
|
|
|
Re: swingx.jar getting smaller
Posted:
Aug 6, 2008 10:19 PM
in response to: osbald
|
|
|
Oh, my ... so many questions in one post 
> How do you modify the build script Jan? I thought it
To split beaninfo from swingx I've split compilation and packaging steps.
To have javadoc refering to JDK I didn't modify anything just provided build with a location of jdk sources via -Djdk.sources.something=... parameter
> was a Netbeans build so does that limit your changes
> to aspects the IDE exposes? do you risk losing
Was me. I just reversed earlier step of including beaninfo src foulder into the main build stream.
> modifications it the IDE regenerates sections?
Not really, and even if someone readded beaninfo into the main compilation step i can always rollback such version of the build script
>
> Or do you have separate build scripts for husdon
> continuous, weeklies etc..? if so are those in the
Script is the same, parameters differ slightly.
> project? are those the poms? how do they get used?
Poms are not finished yet, you can safely ignore them for now. I would like to move whole build from ant to maven. It would make my life easier, but it would also mean to restructure the project. It was not discussed yet so I'm not even sure if anyone else would be in favor of doing so and if, then I guess the decision will be to wait until after 1.0 release.
> dare I ask if the builds are documented anywhere.
You can always ask Perhaps I should put together some documentation tho there are is nothing special about it. Builds run the "bundles" target and there is bunch of params to provide location of things needed for the build. Plus now we have multiple copies of the build machine so if it goes down we can easily restore it elsewhere.
|
|
|
|
|
|
|
|
|
Re: swingx.jar getting smaller
Posted:
Aug 7, 2008 8:49 AM
in response to: rah003
|
|
|
Thanks now I know where to look (frustrated that I couldn't take a peak at hudsons config).
Would you say the swingx build still a functional Netbeans script then? just wondering if a user opens up the project via the nbproject might it fail to build after your manual changes. I mean you wouldn't hand-code the build like the Netbeans auto-generated one.
Know what you mean about maven, although I think you can change the default directory structure. Deviating from the standard and doing that without really understanding maven is daunting (running before you can walk). Hoping Don Browns efforts in making maven a little easier bears fruit. Another thing that potentially worries me about maven and swingx/incubator in particular is the number of un-mavenised jars that are used. I know you can manually insert jars into your own repo via some magic incantation, but its a pain. Whereas with Apache-IVY I can define my own repositories with relative ease (or use public maven ibiblios). So I could have a project repository based on just the folder/name conventions and under vcs. Or that may just be a lack of maven awareness on my part.
|
|
|
|
|
|
|
|
|
Re: swingx.jar getting smaller
Posted:
Aug 10, 2008 10:30 PM
in response to: osbald
|
|
|
> Thanks now I know where to look (frustrated that I couldn't take a peak at hudsons config).
No secrets here:
continuous:
jar javadoc coverage grok -Djavadoc.core.packagelist=/hudson/jdk1.5docs/api -Dlibs.junit.classpath=/hudson/ant/lib/junit.jar:/hudson/ant/lib/xalan.jar -Djar.compress=true
weekly:
bundles coverage update-posted-file -Djavadoc.core.src=/hudson/jdk1.5src -Djavadoc.core.packagelist=/hudson/jdk1.5docs/api -Dlibs.junit.classpath=/hudson/ant/lib/junit.jar:/hudson/ant/lib/xalan.jar -Dposted.txt=/hudson/posted.txt -Djavadoc.compress=true -Djar.compress=true
> Would you say the swingx build still a functional
> Netbeans script then? just wondering if a user opens
as far as I know, yes it is still functional. The worse thing that can happen in this case is that if build is changed locally, either user won't have bean infos build locally, or he/she will re-merge them in the main jar.
> Know what you mean about maven, although I think you
> can change the default directory structure. Deviating
Unfortunately as of maven-2.0.9 current swingx project structure breaks emma and release plugins functionality, so i can either fix those or restructure the swingx ... the latter seems easier
... apart from the two above i had also problem with something else ... maybe checkstyle, but not sure. Anyway as long as every other plugin stops working with non standard structure i prefer to stick to the standard.
|
|
|
|
|
|
|
|
|
Re: swingx.jar getting smaller
Posted:
Aug 7, 2008 5:45 PM
in response to: rah003
|
|
|
I'm confused too. I'd like to use SwingX in Netbeans. Can someone please put things together to show how to use SwingX in Nebeans builder? Thanks.
|
|
|
|
|
|
|
|
|
Re: swingx.jar getting smaller
Posted:
Aug 8, 2008 2:24 AM
in response to: vinh_truong
|
|
|
So long as you're using the binaries it shouldn't differ from the instructions here http://wiki.java.net/bin/view/Javadesktop/SwingXIDE too much until 0.9.4 is released (which hopefully won't be today after saying that).
The discussion above was dipping into the core swingx development.
|
|
|
|
|
java.net RSS
