From: <arn...@ga...> - 2004-03-11 00:25:57
|
Hello all, I'm back to JFreeChart and having some time in the next two weeks to help coding. My main focus : - nice visible value labels - auto-range - copy/paste functionnality with the swing version : copy the chart and paste it in your office suite software (Openoffice, MS Office, ...) - extended JDBC CategoryDataset - serialization - ... David, could you indicate me your roadmap for version 0.9.17 so that I could be perhaps (hopefully) helpfull for some parts. Regards, Arnaud |
From: Nicolas <nic...@fr...> - 2004-03-11 17:54:52
|
=2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Arnaud! Le Jeudi 11 Mars 2004 01:06, Arnaud Leli=E8vre a =E9crit : > Hello all, > > I'm back to JFreeChart and having some time in the next two weeks to > help coding. > > My main focus : > - nice visible value labels - auto-range > - copy/paste functionnality with the swing version : copy the chart and > paste it in your office suite software (Openoffice, MS Office, ...) Good idea. You mean to copy it as an bitmap image? > - extended JDBC CategoryDataset > - serialization I'd like to work in this area too. What do you think of specifying serial=20 version UID for all relevant classes? This would allow to re-load serialize= d=20 graphs from one JFreeChart version to another, while continue to improve th= e=20 API. It would allow binary-compatibility with future class versions, with=20 only very little restrictions on class evolution. And if such an evolution = is=20 really necessary, it is precisely the goal of changing the class UID to mar= k=20 incompatible changes.=20 Is there something scheduled along these lines? Could I do it if nobody=20 complains? > - ... > > David, could you indicate me your roadmap for version 0.9.17 so that I > could be perhaps (hopefully) helpfull for some parts. > > Regards, > Arnaud Cheers, Nicolas =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAUKXxmWwS8Tie5G4RAnXBAJsGYzNKQz49NN5DcxQUb8UkTgAfgACgjw5j LXuSATxSOZ/7pPIj0NL7Ysg=3D =3DMmet =2D----END PGP SIGNATURE----- |
From: David G. <dav...@ob...> - 2004-03-11 19:23:19
|
Nicolas wrote: >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > >Hi Arnaud! > >Le Jeudi 11 Mars 2004 01:06, Arnaud Lelièvre a écrit : > > >>Hello all, >> >>I'm back to JFreeChart and having some time in the next two weeks to >>help coding. >> >>My main focus : >> - nice visible value labels - auto-range >> - copy/paste functionnality with the swing version : copy the chart and >>paste it in your office suite software (Openoffice, MS Office, ...) >> >> > >Good idea. You mean to copy it as an bitmap image? > > > >> - extended JDBC CategoryDataset >> - serialization >> >> > >I'd like to work in this area too. What do you think of specifying serial >version UID for all relevant classes? This would allow to re-load serialized >graphs from one JFreeChart version to another, while continue to improve the >API. It would allow binary-compatibility with future class versions, with >only very little restrictions on class evolution. And if such an evolution is >really necessary, it is precisely the goal of changing the class UID to mark >incompatible changes. > >Is there something scheduled along these lines? Could I do it if nobody >complains? > > > Nothing is scheduled, so feel free to work on it. I don't understand the version UID yet, but I'll read up on it. I can't promise to preserve binary-compatibility prior to the version 1.0 release, but if it is not too hard I'll try. Regards, Dave Gilbert JFreeChart Project Leader |
From: Christian W. Z. <Zuckschwerdt@Mathematik.Uni-Oldenburg.DE> - 2004-03-11 19:35:55
Attachments:
jfreechartplotter.tar.gz
|
Hi, a little off topic as this can't possible be a 0.9.17 feature: I'm working on 2D functions currently and got a working draft with minimum effort. Please tell me if this is the right approach or if we should make more visible and complex model for that. Attached is are three extension classes to jfreechart and one sample applet/application. Here is a sketch: - Provide an interface to (XY) Dataset to get interpolated data. (Think of line charts with other means that just to "connect dots", i.e. bezier curves). - Some XYRenderer that make use of those extra information (currently just a proof of concept, ugly one) - Function2Ds in wrapped in such a interpolateable dataset so they can be properly evaluated at all screen dots. This is a minimalistic approach with the drawback od "hiding" the 2D functions from renderer. I think exposing means to interpolate values from dataset is a nice general feature though. One could use these functions combined with other (XY) charts. I.e. regression functions over quarterly sales data. I haven exploited CategoryDataset, but I assume there could be interpolated data as well and this approach scales to that (as well as 3D f.e.), too. Let me know if this is worth stuffing into jfreechart in the first place. cu, Christian |
From: David G. <dav...@ob...> - 2004-03-11 18:43:33
|
Arnaud Lelièvre wrote: > Hello all, > > I'm back to JFreeChart and having some time in the next two weeks to > help coding. > > My main focus : > - nice visible value labels - auto-range > - copy/paste functionnality with the swing version : copy the chart > and paste it in your office suite software (Openoffice, MS Office, ...) > - extended JDBC CategoryDataset > - serialization > - ... > > David, could you indicate me your roadmap for version 0.9.17 so that I > could be perhaps (hopefully) helpfull for some parts. > > Regards, > Arnaud Sorry I forgot to send my earlier reply to the list: Hi Arnaud, Thanks for your e-mail. I'm close to releasing 0.9.17. I have redone a lot of things in the pie charts (including better labelling) and that should get checked in to CVS very shortly. Also not in CVS yet is the addition of value labels for XYPlots. Once those two things are committed to CVS, I'll update the documentation and do the release. Numerous other changes are already in CVS, there is now a change log so you can see what has been done. I'm glad to have some help for the coding. One thing to watch for is that we target JDK 1.2.2 - the one thing on your list that this may cause trouble for is the copy/paste function. Regards, Dave |
From: Nicolas <nic...@fr...> - 2004-03-11 23:28:43
|
=2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > >Is there something scheduled along these lines? Could I do it if nobody > >complains? > > Nothing is scheduled, so feel free to work on it. I don't understand > the version UID yet, but I'll read up on it. I can't promise to > preserve binary-compatibility prior to the version 1.0 release, but if > it is not too hard I'll try. OK, so I'll do it probably next week or so. I can't promise I can do it in= =20 time for 0.9.17 (I don't know you planning), though it would be nice to=20 reload 0.9.16 objects. I'll also have to check about the JVM 1.2.2 note you= =20 wrote in another mail, to check how UIDs were supported back then. About binary compatibility, in fact, it's quite hard to break by API change= s.=20 You can add/remove fields, add/remove/change methods, change a class=20 inheritance diagram, move it from one package to another, etc... and the=20 serialized data will still load. The only common thing that breaks it is to= =20 change a field type (ex: float =3D> long). But then, it's always possible t= o=20 remove this field and add another one with a different name. Cheers, Nicolas =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAUPScmWwS8Tie5G4RApjzAJwPnNYu4s6FSXmn0pLD9A7PSExmcgCdGzwA mWrytz4Qc6x4TgJ1CASDbD0=3D =3DmYa6 =2D----END PGP SIGNATURE----- |
From: David G. <dav...@ob...> - 2004-03-12 14:23:56
|
Nicolas wrote: >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > > >OK, so I'll do it probably next week or so. I can't promise I can do it in >time for 0.9.17 (I don't know you planning), though it would be nice to >reload 0.9.16 objects. I'll also have to check about the JVM 1.2.2 note you >wrote in another mail, to check how UIDs were supported back then. > > 0.9.17 will be released during next week, so I'd suggest aiming for 0.9.18. I expect that 0.9.18 will follow within a couple of weeks of 0.9.17 because there is a lot of new code being released and it will have bugs. Regarding JDK 1.2.2, let me know what you find. I definitely want to support JDK 1.3, and I stuck with JDK 1.2.2 because there doesn't seem to be a lot to gain by dropping it. But if there is a good reason to step up to 1.3, it is worth considering. 1.2.2 has been EOLed by Sun, so there should be very few people still using it. Regards, Dave Gilbert JFreeChart Project Leader |
From: Nicolas <nic...@fr...> - 2004-03-14 21:40:55
|
=2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Le Vendredi 12 Mars 2004 15:04, David Gilbert a =E9crit : > 0.9.17 will be released during next week, so I'd suggest aiming for > 0.9.18. I expect that 0.9.18 will follow within a couple of weeks of > 0.9.17 because there is a lot of new code being released and it will > have bugs. OK, so UIDs will correct the "can't load file" bug in 0.9.18 then :) > Regarding JDK 1.2.2, let me know what you find. I definitely want to > support JDK 1.3, and I stuck with JDK 1.2.2 because there doesn't seem > to be a lot to gain by dropping it. But if there is a good reason to > step up to 1.3, it is worth considering. 1.2.2 has been EOLed by Sun, > so there should be very few people still using it. Well, it seems serialization won't be the determinant factor either, as 1.2= =2E2=20 should be OK for what we do. Here are my findings: =2D - Big protocol change between v1.1 and v1.2. No protocol change after v= 1.2. =2D - Strings longer than 64K not backward compatible between v1.3 and v1.2= =20 (should not be a problem for JFreeChart however) =2D - v1.2 OK with the serialPersistentFields feature to support usually=20 'incompatible' API change, like renaming a class. It is not used now in=20 JFreeChart, but would be useful to maintain backward compatibility even wit= h=20 otherwise too complex API changes, and even with v1.2. =2D - Specific 1.4 extensions like readUnshared() are not used in JFreeChar= t,=20 whereas validateObject(), which is used, is available since v1.2 More information available at http://java.sun.com/j2se/1.4.2/docs/guide/serialization/spec/serialTOC.= html Especially about possible/incompatile class changes, including for forward compatibility (I'm interested only in backward, but I'm not alone here!): http://java.sun.com/j2se/1.4.2/docs/guide/serialization/spec/version.ht= ml#wp6678 =46or example, forward compatibility would also demand not to delete a fiel= d=20 unless its default value is OK for the old class, unlike what I said in a=20 previous mail concerned only with backward compatibility. Cheers, Nicolas =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAVNQpmWwS8Tie5G4RAp5AAKC0S2pX+MrsZx5ApoW5mjADFiu+lgCfRDHb NVdf3zTOzbG+aN8yNbI+8LI=3D =3Dp5cV =2D----END PGP SIGNATURE----- |