tag:blogger.com,1999:blog-9018398.post3310993721682371352..comments2017-12-26T00:23:16.260+07:00Comments on Fancy one more Java cup?: DesignGridLayout: final 1.0 soon released! Or not?Jean-Francois Poilprethttp://www.blogger.com/profile/00898429429517716882noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-9018398.post-46880222359500326322008-10-30T06:12:00.000+07:002008-10-30T06:12:00.000+07:00Hi Jean-Francois!Very exciting. Thank you for your...Hi Jean-Francois!<BR/><BR/>Very exciting. Thank you for your hard work.<BR/><BR/><I>Unfortunately I have very little feedback from DesignGridLayout users so far...</I><BR/><BR/>This is normal. In general, you'll receive very little feedback. Back when I published shareware, I estimated I heard from 1 in 100.<BR/><BR/>Fortunately, now that we have the Internet, you can track projects using your work. It's very rewarding to see your work pop up in unexpected places.<BR/><BR/>All the best!Zappinihttps://www.blogger.com/profile/03774518609592812824noreply@blogger.comtag:blogger.com,1999:blog-9018398.post-13083488163808987872008-10-29T19:13:00.000+07:002008-10-29T19:13:00.000+07:00Yes Petteri, you are perfectly right!For quality, ...Yes Petteri, you are perfectly right!<BR/><BR/>For quality, I can only talk about the tests I launch systematically on the library after each build. <BR/><BR/>This test suite is quite comprehensive but probably does not cover all possibilities that users may find in their own forms.<BR/><BR/>Unfortunately I have very little feedback from DesignGridLayout users so far (I'd rather think this is because they are all happy with it and have no bug or enhancement to report;-)).<BR/><BR/>I'll probably release a 1.0-rc1 this week-end (after I close issues #15 and #21 as mentioned in a former comment). I will make it available through maven as well. I'll wait for feedback during a few weeks until releasing a final 1.0 (with the same features but any reported bugs fixed).<BR/><BR/>In parallel, in November, I intend to work on issue #10, that will go in a 1.1 version (official by end of 2008 if everything is fine).Jean-Francois Poilprethttps://www.blogger.com/profile/00898429429517716882noreply@blogger.comtag:blogger.com,1999:blog-9018398.post-46619328406069070242008-10-29T14:52:00.000+07:002008-10-29T14:52:00.000+07:00It's just a number you're talking about. Release e...It's just a number you're talking about. Release early, release often but don't claim it to be official when you know it is not. <BR/><BR/>Thus my opinion is to release another beta and spare the official stamp until very certain about the quality!Petterihttps://www.blogger.com/profile/08241082706092605157noreply@blogger.comtag:blogger.com,1999:blog-9018398.post-43645767162185163402008-10-29T07:36:00.000+07:002008-10-29T07:36:00.000+07:00Thanks for the ,suggestion Peter, (and also for re...Thanks for the ,suggestion Peter, (and also for reminding me about the OSS mantra, which I had forgotten, by the way).<BR/><BR/>I'll take my decision by the end of this week.<BR/><BR/>In the meantime, I'll still fix issues 15 and 21, because these fixes break the current API. I want to avoid API breaks once 1.0 is released; afterwards I will focus more on additions to the API, rather than changes.Jean-Francois Poilprethttps://www.blogger.com/profile/00898429429517716882noreply@blogger.comtag:blogger.com,1999:blog-9018398.post-66394811263916167952008-10-28T21:11:00.000+07:002008-10-28T21:11:00.000+07:00I'd follow the open source mantra,Release Early, R...I'd follow the open source mantra,<BR/>Release Early, Release Often.<BR/><BR/>So go ahead a release v1.0<BR/><BR/>You will always be adding new features and improving the api.<BR/><BR/>Releasing v1 will give you a line in the sand marking a stable release.<BR/><BR/>Just my 0.02 worth.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-9018398.post-72797588088940595842008-10-28T20:42:00.000+07:002008-10-28T20:42:00.000+07:00After a quick reflection, I have just created a ne...After a quick reflection, I have just created a new issue #21 to improve the API used for multi-label rows.<BR/>It is preferable to have the best possible API before V1.0 final release.<BR/>I have also decided to fix issue #15 (resolution independence: change margins() API) for the same reason.<BR/>So I will implement these issues first before 1.0 release (should be a matter of days anyway).<BR/><BR/>But the question for other issues (#10 in particular) is still open...Jean-Francois Poilprethttps://www.blogger.com/profile/00898429429517716882noreply@blogger.com