|
Replies:
29
-
Last Post:
Sep 11, 2007 3:07 AM
by: fester
|
|
|
|
|
|
|
|
Re: What SwingX version I use?
Posted:
Sep 3, 2007 3:29 PM
in response to: rafael_afonso
|
|
|
I upgraded from 0.8 to daily a few weeks ago, resulting in a huge amount of incompatibilities with existing client code so I think there just hasn't been released an official q-build (0.9?) for a while?! I would go with a weekly if I were you.
/Casper
|
|
|
|
|
|
|
|
|
Re: What SwingX version I use?
Posted:
Sep 3, 2007 11:12 PM
in response to: rafael_afonso
|
|
|
Weekly builds should be stable enough. 0.8 milestone build is archaic and there just was not newer milestone build made. The date for next milestone was not set yet.
Alternatively you can use DeveloperPack milestone build from February (here: https://swinglabs.dev.java.net/servlets/ProjectDocumentList?folderID=6904&expandFolder=6904&folderID=0 ), but it contains only some of the swingx components.
As for the API changes there should be no changes to the API of components marked in javadoc as @status REVIEWED.
Currenly those are:
AbstractBean
ErrorInfo
ErrorLevel
ErrorReporter
JXErrorPane
JXHeader
JXStatusBar
JXTitledSeparator
For all others there might be some changes from time to time, although if anything bigger is coming it is usually announced upfront in this forum and you can still stick to the whatever weekly build you were using prior any of such change.
HTH,
Jan
|
|
|
|
|
|
|
|
|
Re: What SwingX version I use?
Posted:
Sep 4, 2007 2:49 AM
in response to: rah003
|
|
|
Well I'd hate to say I told you so.. no, not really, here I go.. http://forums.java.net/jive/thread.jspa?messageID=233031𸹇
I'd still like to see the milestones vanish - it isn't entirely clear to me why swingx downloads are made available from swinglabs.org - it's just another thing to keep up-to-date, or not. If we've not updated the milestones for a couple of years is it not time for a rethink? At the very least add a huge health warning and a link to the project pages.
I tend to think the dev packs (and component shop) just confuse things further - unless they'res something I'm not getting here.
While I'm on my high horse <g> I'd would like to see some movement towards 1.0 (possibly a branch to tackle JDK6/7 compatibility?), integration with appframework and beansbinding projects (although the latter's been in a sorry state for some months it seems). Bit worried JavaFX is going to steal the limelight and set things back a year or two.
There said it.
- Richard
|
|
|
|
|
|
|
|
|
Re: What SwingX version I use?
Posted:
Sep 4, 2007 3:17 AM
in response to: osbald
|
|
|
Richard,
most of it is about politics, IMO 
> While I'm on my high horse <g> I'd would like to see some movement towards 1.0 (possibly a branch to tackle JDK6/7 compatibility?), integration with appframework and beansbinding projects (although the latter's been in a sorry state for some months it seems). Bit worried JavaFX is going to steal the limelight and set things back a year or two.
>
or about politics plus (minus) resources <g>
To put it bluntly (and it's just me, nothing official): I see no way at
all to maintain more than one version of whatever - and even that is
straining (looking at my worklog, September is nearly over, harhar). As
to integration with appframework and beansbinding - I try to keep some
examples in my incubator synched with the current versions (and disagree
with your evaluation of beansbinding being in poor state, it's been
worked on with a steady direction).
Jeanette
---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net
|
|
|
|
|
|
|
|
|
Re: What SwingX version I use?
Posted:
Sep 4, 2007 5:09 AM
in response to: Kleopatra
|
|
|
> To put it bluntly (and it's just me, nothing official): I see no way at
> all to maintain more than one version of whatever - and even that is
> straining
I just worry every time you & Karl undertake a overhaul of the JXTable or JXTreetable innards, highlighters etc.. that you're having to do so ignoring the elephant-in-the-room <g> From one perspective knowing that the swingx components have these incompatibilities cant be encouraging for new users and it throws up barriers to their adoption into the JDK. You've already stated the filtering and sorting are on minimal life support, so I can't help but wonder how do we then move on..
I'm on 1.5 so actually I'm quite happy with the status quo. Although I'm also aware I've painted myself into a corner somewhat with the swingx way of working the grouplayout, swingworker backports as well as beansbinding 0.61 (more fool me). No easy migration paths.
I know about your unsung work with the incubator album stuff, looked over it several times.. shame about the buffering difficulties. In terms of new users I'm wondering how easy the whole state of play is to get at. Let alone the most important bit about the imperial rules
I'll play bad cop then - because the whole history of beansbinding I find deeply frustrating and just when it seemed to have become stable enough for use (0.6.1) back in June it was suddenly rewritten (yet again?!! I lose count of the attempts now.. still maintain it's jinxed) and hasn't fully compiled since. Last time I tried it was the unit tests that failed. But I had been expecting them to provide the only reliable source of documentation/intent. It doesn't seem to be usable/complete even against the previous version yet and isn't likely to be for at least a couple of months more. Which is a blow after the early prognosis that Scott had left it pretty much complete. I'm not clear on the advantages of the new syntax - was it supposed to allow for an easier transition into full blown JDK7 properties? I lost the will to live during those never-ending discussions <g>. If you set it against the JSR/JDK7 timescale I suppose its not so terrible but if you have a longer memory and see it as swings binding framework its long, long overdue. Which is poor.
IMO
- Richard
|
|
|
|
|
|
|
|
|
Re: What SwingX version I use?
Posted:
Sep 5, 2007 3:03 AM
in response to: osbald
|
|
|
jdnc-interest@javadesktop.org schrieb:
>
> I just worry every time you & Karl undertake a overhaul of the JXTable or JXTreetable innards, highlighters etc.. that you're having to do so ignoring the elephant-in-the-room <g>
Hmm .. what exactly do you mean was/is ignored? (sorting/filtering is an
exception and was more the other way round <g>).
How to integrate is an open question - the problems were seen 2 years
ago and open-eyed postponed: the idea always was to "switch-over" and
then forget the old version. Now we're near to that point ...
Can't say much about beansbinding, not being involved in any way
Jeanette
---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net
|
|
|
|
|
|
|
|
|
Re: What SwingX version I use?
Posted:
Sep 5, 2007 5:38 AM
in response to: Kleopatra
|
|
|
I think the 'exception' is the thing I think you're ignoring. <g>
Unless they'res other incompatibilities I'm not aware of (since I'm chained to 1.5 I'm not fully up-to-date with the diffs). Does JDK6 make the filtering & sorting any easier/extensible or just different? do we then have an obligation to support the enhanced drag & drop (assuming that isn't an automatic inheritance).
How we handle the switch-over is what I'm really wondering - that and how much is enough? I'd like to see a branch for 1.5 even if it isn't officially maintained I'll be using the backports at the very least for a good while yet. Hope that's what you mean by 'forgetting'.
Is it worth hitting a 1.0 first? assuming it isn't as far off as 'by the book'.
- Richard
|
|
|
|
|
|
|
|
|
Re: What SwingX version I use?
Posted:
Sep 5, 2007 6:16 AM
in response to: osbald
|
|
|
jdnc-interest@javadesktop.org schrieb:
> I think the 'exception' is the thing I think you're ignoring. <g>
>
true. But nothing I can do about it (not my decision ...
> Does JDK6 make the filtering & sorting any easier/extensible or just different?
>
both - kind of: it's different (at its base not very much), it slims
down JXTable (no more hacks around super unaware of row index mapping),
but we loose features (list sorting) and control (header sortGesture,
sorting api on xtable), "gain" core bugs (sorts when clicking into
resize header region) ... still in the process of getting an overview
... it's simply work <g>
> How we handle the switch-over is what I'm really wondering - that and how much is enough? I'd like to see a branch for 1.5 even if it isn't officially maintained I'll be using the backports at the very least for a good while yet. Hope that's what you mean by 'forgetting'.
>
I'm sure there will be clear marker in the code-base <g>. Committers are
free to branch from there, I think.
> Is it worth hitting a 1.0 first? assuming it isn't as far off as 'by the book'.
>
Again, not my decision - I'm just the slave out in the open As you
recall, me and Richard disagree heartily about the requirement of
reviews (as formal precondition). As long as that's not modified I don't
see the option of any useful release. That said, I would first go for a
SwingX 1.0 targeted to jdk1.5. After that, immediately re-target to 1.6
- the release is a good branching point.
Jeanette
---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net
|
|
|
|
|
|
|
|
|
Re: Beansbinding 1.0 released.
Posted:
Sep 6, 2007 2:56 AM
in response to: osbald
|
|
|
Richard,
you probably already saw it, just to be sure (unit tests are not yet
updated - which shows their relative weight in the core team <g>).
Cheers
Jeanette
---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net
|
|
|
|
|
|
|
|
|
Re: Beansbinding 1.0 released.
Posted:
Sep 6, 2007 3:21 AM
in response to: Kleopatra
|
|
|
Yeah you're post just interrupted my first question http://weblogs.java.net/blog/shan_man/archive/2007/09/beans_binding_1.html via the old rss reader stealing the focus <g>. If that was part of my badgering then that's the kind of humiliation I can live with <g>. Although just a new release (0.7?) and the notes would have sufficed.
It seems a little, erm rash? to jump to 1.0 on the first outing of the new syntax and without the unit tests being updated or even compiling and just the one page of notes. But it is open source and so some of that procedure can be losened. Thats kind of what I was getting at yesterday.
I think swingx has been in danger of playing possum for too long - which like undocumented, unreviewed code isn't healthy either. Shame we didn't know about Timing and Binding releases - would have been nice to take the hat trick and bring them all up to 1.0.
- Richard
|
|
|
|
|
|
|
|
|
Re: Beansbinding 1.0 released.
Posted:
Sep 6, 2007 3:25 AM
in response to: osbald
|
|
|
A more suspicious person than I might note that the app framework,
timing framework and binding have all be promoted to 1.0 within the
last couple of weeks. Hmm... I smell marketing involved somewhere.
Patrick
---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net
|
|
|
|
|
|
|
|
|
Re: What SwingX version I use?
Posted:
Sep 4, 2007 8:26 AM
in response to: osbald
|
|
|
I agree that we should do something about the 0.8 problem.
0.8 was just a random check point. We could just randomly checkpoint a 0.9 in the same vain. No matter what the quality/stability of the weekly release is, some users will be frightened away unless it's an "official" release. I'd favor a 0.9, we've had some big changes since 0.8.
Or, if no one wants a 0.9 right now, I'd favor removal of the old releases from swinglabs.org and redirecting users to Hudson.
Karl
|
|
|
|
|
|
|
|
|
Re: What SwingX version I use?
Posted:
Sep 5, 2007 2:12 AM
in response to: kschaefe
|
|
|
It's unfortunate that we'd be at the 0.9 stage without having a clear picture of what 1.0 is. I mean is the current build really any closer to 1.0 than 0.8? We'd quickly have to go down the 0.91, 0.92.. route. Maybe that's part of the reason it stalled in the first place?
The other issue is what determines a milestone - a major change completed on the trunk? semi-regular? not to mention who has access to the machine hosting the site or committal rights on the project for that matter.. Should have prominent links to the snapshots & vcs in any case.
- Richard
|
|
|
|
|
|
|
|
|
Re: What SwingX version I use?
Posted:
Sep 5, 2007 3:03 AM
in response to: osbald
|
|
|
> It's unfortunate that we'd be at the 0.9 stage
> without having a clear picture of what 1.0 is. I mean
> is the current build really any closer to 1.0 than
> 0.8? We'd quickly have to go down the 0.91, 0.92..
Yeah. This is a part of the reason why there was no 0.9 milestone yet. Another piece of the puzzle is that for 1.0 release all of the files should be reviewed. Currently only very few are. Since review is not supposed to be only the formality, but should be real evaluation of the concepts and usefulness of give component as well as its alignment with future direction of swing it is a quite time&resource consuming and at this moment there is no one available to do the reviews.
Maybe it is time to think about another way to graduate components apart from the review ... maybe just look few things to see how mature it is:
- how stable the api of given component was over past 12 months
- are there any tutorials on how to use it
- are there any bugs open
- how easy/difficult it is to incorporate given component with other swing compoents.
- do we have any real use cases (people using given component in (near-)productive application, apart from the author)
- etc.
with the set of above we can agree on clear list of what component have to pass to be marked as mature and freeze the API on it. While this will not guarantee that component doesn't change once (if ever) the internal review is done in the future it would give some indication about the component and move us forward towards 1.0 release. Of course we would have to also agree on the fact that having internal review is no longer requirement for component to be considered ready for 1.0 release.
> not to mention who has access to the machine hosting the site or committal rights on the project for that
> matter.. Should have prominent links to the snapshots & vcs in any case.
I do, but being granted rights to do something doesn't necessarily equal to being given complete freedom to change everything. We need to discuss this with Richard and I'm afraid we can't get his feedback on the subject before next week. 
Cheers,
Jan
|
|
|
|
|
|
|
|
|
Re: What SwingX version I use?
Posted:
Sep 5, 2007 5:17 AM
in response to: rah003
|
|
|
> Another piece of the puzzle is that for 1.0 release all of the files should be reviewed.
Hmmm not according to the release strategy page in the wiki, the main difference it attaches to major release is unit test coverage, soak-in time and a demo application. Similarly the API reviews page doesn't say it's a precondition for release? I'd have thought two years of dev has given the code a considerable shakedown - although we do have a few dark corners. Josh's MutliSlider..?
Mostly that all sounds pretty sensible. Are we in danger of attaching too much value to a version number? Chet seemed to go from 0.5x to 1.0 overnight <g>.
> - are there any tutorials on how to use it
Oh give us a break you can't swap one showstopper (lack of reviews) for another (lack of documentation).. we'll never make any progress
> > By the rules I'm not sure the latest builds necessarily 'pass all unit tests'.
> That is a problem with hudson configuration. I'm currently trying to redo the download > page and as part of it I will also reconfigure hudson to produce weekly only when there
> were code changes in the past week and when all the tests are passing.
I'm just being pernickerty because I dislike politics. Would be genuinely nice to know a weekly/latest had some kind of pedigree - otherwise it's just a gamble. Developers should be able to navigate Hudson to find a passing build via the latest links - but as I said in the other thread are newbies being intimidated by Hudson?
- Richard
|
|
|
|
|
|
|
|
|
Re: What SwingX version I use?
Posted:
Sep 5, 2007 6:16 AM
in response to: osbald
|
|
|
> doesn't say it's a precondition for release? I'd have
> thought two years of dev has given the code a
> considerable shakedown - although we do have a few
> dark corners. Josh's MutliSlider..?
Not all the code is 2 years old, and yes, we have a few dark corners. Should not those things be seen to before 1.0 release?
> Mostly that all sounds pretty sensible. Are we in
> danger of attaching too much value to a version
> number? Chet seemed to go from 0.5x to 1.0 overnight
If release number is no more then A number, then you can think of a date in weekly builds as of A number only too and in that case we are releasing pretty often, aren't we?
> > - are there any tutorials on how to use it
> Oh give us a break you can't swap one showstopper
> (lack of reviews) for another (lack of
> documentation).. we'll never make any progress
I'm not swapping, I'm adding  And yes, I think we need those.
Since you always seem to take timingframework as an example, consider this:
- there was huge refactoring done on the code before 0.5 release.
- there were very few API changes to timingframework in last 6 months (mainly adding api to allow swapping the timer implementation and few bugfixes, but never changing existing api)
- the complexity of this project was different (Chet is the only developer there, so when he thought he was done, he was done.)
- there are plenty of examples on how to use it
with all the above, it was ready for 1.0, so 1.0 version was released.
Anyway if all you want is another milestone, all you have to do is to start looking into those open P1 issues ...
|
|
|
|
|
|
|
|
|
Re: What SwingX version I use?
Posted:
Sep 5, 2007 7:57 AM
in response to: rah003
|
|
|
> Not all the code is 2 years old, and yes, we have a few dark corners. Should not those
> things be seen to before 1.0 release?
I'd say in an ideal world yes. Although I was thinking more of a educated sweep out than a prolonged review process we've proved we don't have the resources or patience for. That's why I picked on MultiThumbSlider as an obvious 'not ready' target.
> If release number is no more then A number, then you can think of a date in weekly
> builds as of A number only too and in that case we are releasing pretty often, aren't
> we?
Yes kinda, that's why I asked about the importance we attach to 1.0. Development will contunue regardless. It's value is more in a guarantee of some maturity for the more nervous types, a story for java.net (not to mention a timely branching point for JDK6 issues). I think the milestones worth is to offer some protection from the kind of periodic 'painter upheavals' so devs can tackle the changes at their own pace.
My gut feel is swingx is pretty solid - not perfect but If asked I wouldn't have a problem with calling it 1.0.. I've seen (currently using) much worse. It's tricky to document a moving target.. just look at the bindings & appframework tuts. (Although the real reason is we all HATE writing documentation and it's not like we get paid for this - got a problem with that? Contribute!).
I only picked on Chet because of the *timing* <g> I was alluding to different projects, different rules, no betas, release candidates just done.. move on. I'd like to cry foul over the tutorials as he's just written a book about it.. no fair!
> Anyway if all you want is another milestone, all you have to do is to start looking into
> those open P1 issues ...
You might remember my first reaction was to say say get rid of those embrassing relics <g>. Anyway they're not P1s one of them isn't even a defect its a request, most are PLAF swapover issues hardly P1 in my book - who seriously supports that as a core part of their apps? the swing demo. I don't think Fred nor Josh (dmouse) are going to reply to those any time soon. I'd save the P1s for things like spontaneous human combustion and snuffing out of suns..
Anyway #88 didn't stop the .08 milestone now did it
- Richard
|
|
|
|
|
|
|
|
|
Re: What SwingX version I use?
Posted:
Sep 5, 2007 8:37 AM
in response to: osbald
|
|
|
> I'd say in an ideal world yes. Although I was
> thinking more of a educated sweep out than a
> prolonged review process we've proved we don't have
> the resources or patience for. That's why I picked on
> MultiThumbSlider as an obvious 'not ready' target.
Well this is what the DeveloperPack was supposed to be about - just handpicked components considered to be ready. But then politics & marketing daemons jumped on the sucker and we know where it all ended ... Tho there is still a chance we revive it.
But this has given me one interesting idea. I might try to setup some polls to get a feeling for what people things about different components ...
> Yes kinda, that's why I asked about the importance we
> attach to 1.0. Development will contunue regardless.
Well I think its importance was already described in the ReleaseStrategy wiki page. As long as we stay with <1.0 number we can do as many milestones as we decide on (and as long as there is no open P1 issue)
> It's value is more in a guarantee of some maturity
> for the more nervous types, a story for java.net (not
> to mention a timely branching point for JDK6 issues).
I would say that with JDK7 release we drop support for JDK5, create a branch for it at the same time and stop maintaining that branch apart from having cont/weekly build running for it on hudson, but this is just my personal opinion.
> My gut feel is swingx is pretty solid - not perfect
> but If asked I wouldn't have a problem with calling
> it 1.0.. I've seen (currently using) much worse. It's
Personally I agree... but we should still observe the protocol.
> bindings & appframework tuts. (Although the real
> reason is we all HATE writing documentation and it's
> not like we get paid for this - got a problem with
> that? Contribute!).
True, tho you expect respectable project to provide some amount of tutorials/documentation. It's a sign of mature project too. Don't hate it even more if you have to struggle with some library that have poor or no documentation?
> I only picked on Chet because of the *timing* <g> I was alluding to different projects, different rules,
> no betas, release candidates just done.. move on. I'd like to cry foul over the tutorials as he's just
> written a book about it.. no fair!
But then again writing a book is one way how to get paid for effort of documenting something, isn't it?
> > those open P1 issues ...
> You might remember my first reaction was to say say get rid of those embrassing relics <g>. Anyway
> they're not P1s one of them isn't even a defect its a request, most are PLAF swapover issues hardly P1 in
> my book - who seriously supports that as a core part of their apps? the swing demo. I don't think Fred nor
> Josh (dmouse) are going to reply to those any time soon. I'd save the P1s for things like spontaneous
> human combustion and snuffing out of suns..
Fine. I'll fix 451 (since solution is already there). I've no problem downgrading all the others from the P1 list to P2 or lower. Jeanette any opinions on that?
> Anyway #88 didn't stop the .08 milestone now did it
What can I say ... maybe just: "It Wasn't Me"
Anyway conclusion for #88 was to implement another method "setEnabledRecursive" or something like that so it is more a feature request then a bug.
|
|
|
|
|
|
|
|
|
Re: What SwingX version I use?
Posted:
Sep 5, 2007 8:56 AM
in response to: rah003
|
|
|
jdnc-interest@javadesktop.org schrieb:
>
> Well this is what the DeveloperPack was supposed to be about - just handpicked components considered to be ready. But then politics & marketing daemons jumped on the sucker and we know where it all ended ... Tho there is still a chance we revive it.
>
wouldn't agree - the devpack was a political thingy  And contained
classes (swingx!) which had not been reviewed ...
> But this has given me one interesting idea. I might try to setup some polls to get a feeling for what people things about different components ...
>
haha ... so we get as many favorites as answers <g>
>
> Fine. I'll fix 451 (since solution is already there). I've no problem downgrading all the others from the P1 list to P2 or lower. Jeanette any opinions on that?
>
no problem - for issues of type defects and tasks. (just closed
#579-swingx, because that was what all commentors agreed on). Not sure
what to do with enhancements/features: typically those are targeted to
some release/milestone version .. without such the priority is the only
relevant tag. Downgrading just to meet a criterion feels ... ehem ...
Maybe change the release draft so that "issues" are defects and tasks
only? Anyway, a long-standing (and hard to do properly) request like
fixed table columns shouldn't halt a release, core Swing lived with it
since its birth <g>
>> Anyway #88 didn't stop the .08 milestone now did it
>
".08" - LOL!
Whatever, before putting any work to it - Richard must be convinced to
revise his pet, the "reviewed"-requirement!
Back to family duties (no, you didn't see me here if you were asked
Jeanette
---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net
|
|
|
|
|
|
|
|
|
Re: What SwingX version I use?
Posted:
Sep 5, 2007 3:09 AM
in response to: osbald
|
|
|
jdnc-interest@javadesktop.org schrieb:
>
> The other issue is what determines a milestone -
have a look into the wiki - we have a release strategy draft which
answers that
Jeanette
---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net
|
|
|
|
|
|
|
|
|
Re: What SwingX version I use?
Posted:
Sep 5, 2007 4:14 AM
in response to: Kleopatra
|
|
|
http://wiki.java.net/bin/view/Javadesktop/ReleaseStrategy dated 29 Sept 2005 (nearly two years ago). I notice that there was only one (.08) milestone after you agreed on this - and we wondered why it stopped <g>
Don't see anything preventing a new milestone there. So long as we never write any demos its easy enough <g>. Not sure how anybody but the author could verify the visual/interactive tests.
But it doesn't say anything about when to release ~ I'd have thought after the painter changes and the highlighter overall had settled in were both good points. But also quarterly milestones that pick up random bugfixes might be helpful.
By the rules I'm not sure the latest builds necessarily 'pass all unit tests'. Too many weeklies on that swinglabs download page. Finally hasn't Chet just released TimingFramework 1.0?.
- Richard
|
|
|
|
|
|
|
|
|
Re: What SwingX version I use?
Posted:
Sep 5, 2007 4:41 AM
in response to: osbald
|
|
|
What makes SwingX so different from other open source projects? I have used many and during the course of using them I upgraded from version to version, but now that I'm using SwingX in my application, I have do download a weekly build from time to time and hope for the best.
Release early, release often...
|
|
|
|
|
|
|
|
|
Re: What SwingX version I use?
Posted:
Sep 5, 2007 5:06 AM
in response to: fester
|
|
|
Hi
This is not really a library/component project in the normal open-source
sense of the word.
Think of it as "helping Sun test their next-generation Swing code".
And yes, I think this is a good thing - we get way more eyeballs on the
code, and a chance for external people to review it and spot mistakes
before they get "baked in".
But for myself, I am in the process of removing SwingX from all of my
production projects.
Over the past year I have built my own clones of the various pieces of
SwingX machinery I found useful, and I have moved the bulk of my code over.
As it turns out, either (a) I only need a small piece of the
functionality or (b) there are other open-source libraries out there
that have real release cycles.
For example, I've built my own mini-beans-binding, based on a combo of
the Eclipse&SwingX API's, but with a very small fraction of the complexity.
(its about 1500 lines total). It doesn't do half of what the other
binding libraries do, but it's simple and stable.
Regards, Noel Grandin.
jdnc-interest@javadesktop.org wrote:
> What makes SwingX so different from other open source projects? I have used many and during the course of using them I upgraded from version to version, but now that I'm using SwingX in my application, I have do download a weekly build from time to time and hope for the best.
>
> Release early, release often...
> [Message sent by forum member 'fester' (fester)]
>
> http://forums.java.net/jive/thread.jspa?messageID=234009
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
> For additional commands, e-mail: jdnc-help@jdnc.dev.java.net
>
>
>
Disclaimer: http://www.peralex.com/disclaimer.html
---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net
|
|
|
|
|
|
|
|
|
Re: What SwingX version I use?
Posted:
Sep 5, 2007 9:35 AM
in response to: Noel Grandin
|
|
|
> For example, I've built my own mini-beans-binding,
> based on a combo of
> the Eclipse&SwingX API's, but with a very small
> fraction of the complexity.
> (its about 1500 lines total). It doesn't do half of
> what the other
> binding libraries do, but it's simple and stable.
Hi Noel,
I have also removed swingx from my ongoing projects.
And improvised a minimal binding library, but would be interested in looking at your package if you are able and willing to share this.
|
|
|
|
|
|
|
|
|
Re: What SwingX version I use?
Posted:
Sep 5, 2007 11:57 PM
in response to: jancarel
|
|
|
|
|
Hi
Have a look in the jdnc-incubator project under src/grandinj.
Some basic documentation is in the package.html file.
The API style is mostly derived from the SwingX approach, while the
internal architecture is quite similar to the Eclipse binding project.
It currently has a dependency on the apache jakarta-commons-beanutils
library.
Regards,
Noel Grandin
jdnc-interest@javadesktop.org wrote:
>> For example, I've built my own mini-beans-binding,
>> based on a combo of
>> the Eclipse&SwingX API's, but with a very small
>> fraction of the complexity.
>> (its about 1500 lines total). It doesn't do half of
>> what the other
>> binding libraries do, but it's simple and stable.
>>
>
> Hi Noel,
>
> I have also removed swingx from my ongoing projects.
>
> And improvised a minimal binding library, but would be interested in looking at your package if you are able and willing to share this.
> [Message sent by forum member 'jancarel' (jancarel)]
>
> http://forums.java.net/jive/thread.jspa?messageID=234071
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
> For additional commands, e-mail: jdnc-help@jdnc.dev.java.net
>
>
>
Disclaimer: http://www.peralex.com/disclaimer.html
[att1.html]
|
|
|
|
|
|
|
|
|
|
|
|
Re: What SwingX version I use?
Posted:
Sep 6, 2007 11:43 PM
in response to: rah003
|
|
|
> True but for some authors are difficult to reach so
> anybody using given component should have a look at
> the demo. Would be nice if you can report that given
> demo works/is-broken.
Maybe you should take a look at abbot[1]? I used it very effectively to test gui behaviour. I'm sure it could be used to test things like highlighters automatically.
regards,
Wim
[1] http://abbot.sourceforge.net/doc/overview.shtml
|
|
|
|
|
|
|
|
|
Re: What SwingX version I use?
Posted:
Sep 7, 2007 12:17 AM
in response to: fester
|
|
|
> Maybe you should take a look at abbot[1]? I used it
> very effectively to test gui behaviour. I'm sure it
> could be used to test things like highlighters
> automatically.
>
> regards,
>
> Wim
> [1] http://abbot.sourceforge.net/doc/overview.shtml
That sounds and looks great. Since you have already used it, would you be willing to write and donate few tests so we can quickly get up to speed with the tool?
Cheers,
Jan
|
|
|
|
|
|
|
|
|
Re: What SwingX version I use?
Posted:
Sep 11, 2007 3:07 AM
in response to: rah003
|
|
|
> That sounds and looks great. Since you have already
> used it, would you be willing to write and donate few
> tests so we can quickly get up to speed with the
> tool?
Sure, maybe I can take just one of the tests to show you how it is done. Can you send me the source code of the test you would like to see automated (I don't have CVS installed, or did you guys already switch to subversion?).
regards,
Wim
|
|
|
|
|
java.net RSS
