You can subscribe to this list here.
2005 |
Jan
(6) |
Feb
(1) |
Mar
|
Apr
(20) |
May
(5) |
Jun
(19) |
Jul
|
Aug
(7) |
Sep
(2) |
Oct
(8) |
Nov
(16) |
Dec
(3) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2006 |
Jan
(10) |
Feb
(2) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(11) |
Aug
|
Sep
|
Oct
(2) |
Nov
(3) |
Dec
(7) |
2007 |
Jan
(2) |
Feb
(8) |
Mar
(1) |
Apr
(3) |
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2009 |
Jan
(4) |
Feb
(14) |
Mar
(12) |
Apr
(17) |
May
(40) |
Jun
(25) |
Jul
(35) |
Aug
(3) |
Sep
(3) |
Oct
|
Nov
|
Dec
(14) |
2010 |
Jan
(7) |
Feb
(6) |
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
(2) |
Oct
(1) |
Nov
|
Dec
|
2011 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(3) |
Dec
|
2012 |
Jan
|
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(4) |
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
|
2013 |
Jan
(1) |
Feb
(2) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2014 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
(3) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
2016 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
2017 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: riccardo <ric...@ya...> - 2005-11-10 19:28:30
|
Hi all, in this last weak i work on lib :). I try to begin whit a simple steps: modify SplashWindow.java and introduce a new component BitField. In my little experience of work i see some application that have a indeterminate SplashWindow or have a JDialog whit a progress bar indeterminate. For that reasons change the Splash for work in that way. There are most reasosns for use a graphics component like BitField, for example if manage most flag in your application.In this components i try to create a bean class serializable, because i use my graphic tool for create a GUI, and it's work whit serializable component. Include a change log, and the class modified. Thanks to all. I try to do may best. Riccardo. ___________________________________ Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB http://mail.yahoo.it |
From: riccardo <ric...@ya...> - 2005-11-10 19:20:43
|
Hi all, in this last weak i work on lib :). I try to begin whit a simple steps: modify SplashWindow.java and introduce a new component BitField. In my little experience of work i see some application that have a indeterminate SplashWindow or have a JDialog whit a progress bar indeterminate. For that reasons change the Splash for work in that way. There are most reasosns for use a graphics component like BitField, for example if manage most flag in your application.In this components i try to create a bean class serializable, because i use my graphic tool for create a GUI, and it's work whit serializable component. Include a change log, and the class modified. Thanks to all. I try to do may best. Riccardo. ___________________________________ Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB http://mail.yahoo.it |
From: Felix B. <bf...@gm...> - 2005-11-03 11:07:40
|
On Thursday 03 November 2005 06:59, riccardo wrote: > anoder stupid question: when i think to find something > an idea or enithing else, i sent an email to advise or > else? If it's a new feature that you would like to add, it's best to discuss it on the mailinglist first, yes. Felix -- Try Debian GNU/Linux! http://www.felix.beldesign.de/ |
From: riccardo <ric...@ya...> - 2005-11-03 05:59:30
|
tnk Felix, i try to help xnap common project, and i hope to make something helpfull for me and oders :) ( sorry form my very very bad english ). anoder stupid question: when i think to find something an idea or enithing else, i sent an email to advise or else? tnk so mouch. Riccardo --- Felix Berger <bf...@gm...> ha scritto: > On Wednesday 02 November 2005 22:56, Felix Berger > wrote: > > and add a translation using the webinterface > provided by launchpad or by > > downloading the po file at > > > > > https://launchpad.net/products/xnap-commons/%2Bseries/main/%2Bpots/xnap-com > >mons/%2Bexport > > > > and translating it using poedit > (http://poedit.org/) kbabel or emacs. > > Actually if you're doing it this way, downloading > the file from here saves you > the trouble of making a launchpad account: > > http://cvs.sourceforge.net/viewcvs.py/*checkout*/xnap-commons/xnap-commons/po/keys.pot > > Felix > > -- > Try Debian GNU/Linux! > http://www.felix.beldesign.de/ > > > ------------------------------------------------------- > SF.Net email is sponsored by: > Tame your development challenges with Apache's > Geronimo App Server. Download > it for free - -and be entered to win a 42" plasma tv > or your very own > Sony(tm)PSP. Click here to play: > http://sourceforge.net/geronimo.php > _______________________________________________ > xnap-commons-devel mailing list > xna...@li... > https://lists.sourceforge.net/lists/listinfo/xnap-commons-devel > ___________________________________ Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB http://mail.yahoo.it |
From: Felix B. <bf...@gm...> - 2005-11-02 22:13:25
|
On Wednesday 02 November 2005 22:56, Felix Berger wrote: > and add a translation using the webinterface provided by launchpad or by > downloading the po file at > > https://launchpad.net/products/xnap-commons/%2Bseries/main/%2Bpots/xnap-com >mons/%2Bexport > > and translating it using poedit (http://poedit.org/) kbabel or emacs. Actually if you're doing it this way, downloading the file from here saves you the trouble of making a launchpad account: http://cvs.sourceforge.net/viewcvs.py/*checkout*/xnap-commons/xnap-commons/po/keys.pot Felix -- Try Debian GNU/Linux! http://www.felix.beldesign.de/ |
From: Felix B. <bf...@gm...> - 2005-11-02 21:56:24
|
On Wednesday 02 November 2005 22:14, ricky wrote: Hi Ricky, I assume you're using xnap as an abbreviation for xnap commons, otherwise check out http://xnap.sf.net if you want to help with the xnap project. > Hi all, i have some experience in Java programming, i > like to help us to expand xnap, how can i start? :) As our current todo list is pretty short the best and most natural way to help would be fixing a bug that you found or adding a feature that you think is missing. Another helpful contribution would be translating the messages bundle. If you want you can check out: https://launchpad.net/products/xnap-commons/+translations and add a translation using the webinterface provided by launchpad or by downloading the po file at https://launchpad.net/products/xnap-commons/%2Bseries/main/%2Bpots/xnap-commons/%2Bexport and translating it using poedit (http://poedit.org/) kbabel or emacs. Thanks, Felix -- Try Debian GNU/Linux! http://www.felix.beldesign.de/ |
From: ricky <ric...@ya...> - 2005-11-02 21:15:06
|
Hi all, i have some experience in Java programming, i like to help us to expand xnap, how can i start? :) ciao ___________________________________ Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB http://mail.yahoo.it |
From: Felix B. <bf...@gm...> - 2005-11-01 17:22:15
|
Hi, the xnap-commons team is pleased to announce the XNap Commons 0.9.2 release! Changes in this version include: New Features: o FileHelper has support for ProgressMonitors in copy methods. o A default file transfer handler for trees has been added. It takes care of dragging and dropping of files from/to a JTree and displays a progress dialog while copying dropped files into the selected directory of the tree. Fixed bugs: o A NullPointerException has been fixed in the FileChooserPanel. o FileHelper.readText() has been fixed again after new test cases had uncovered unexpected behavior of the implementation. Changes: o CompletionPopup and other components have been made aware of ComponentOrientation. Have fun! -The xnap-commons team |
From: Sean C. <sc...@gm...> - 2005-10-30 00:20:37
|
> The current cvs already contains the changes to the layout managers and t= he > property listener for the completion box. Wow, that's fast. Thanks, Felix! |
From: Felix B. <bf...@gm...> - 2005-10-29 15:26:41
|
On Friday 28 October 2005 17:21, Sean Crotty wrote: > I'm a little confused on how this is supposed to work. It does seem > logical that each component would "automatically" get its orientation > from the Locale. But the book I'm reading provides example code that > recursively traverses through nested components to set it. I need to > look into this further. I'm not entirely sure either, but for me it looks like you have to explicitly call Component.applyComponentOrientation(ComponentOrientation o) after it has been created and all its child components have been added. The current cvs already contains the changes to the layout managers and the property listener for the completion box. Felix -- Try Debian GNU/Linux! http://www.felix.beldesign.de/ |
From: Felix B. <bf...@gm...> - 2005-10-29 15:23:17
|
On Thursday 27 October 2005 23:02, Sean Crotty wrote: > Other xnap commons GUI components like the various > org.xnap.commons.gui.Dialogs hide access to the underlying > java.awt.Component and so even setting the ComponentOrientation is > impossible for them. The static methods in Dialogs all use JOptionPane for creating the dialogs and JOptionPane takes the parent's component orientation and sets it for the dialog. So this should work fine. Felix -- Try Debian GNU/Linux! http://www.felix.beldesign.de/ |
From: Sean C. <sc...@gm...> - 2005-10-28 15:21:45
|
On 10/27/05, Felix Berger <bf...@gm...> wrote: > Are you supposed to call that for every component individually in the nor= mal > use case or shouldn't it be taken from the currently set locale, see > > static ComponentOrientation getOrientation(Locale locale) > > So if you set the locale before you use any of the dialogs they should us= e the > proper layout after we made the necessary changes, at least I'd hope it w= ould > work like this. I'm a little confused on how this is supposed to work. It does seem logical that each component would "automatically" get its orientation from the Locale. But the book I'm reading provides example code that recursively traverses through nested components to set it. I need to look into this further. > Maybe I should warn you that our current I18n class lacks proper plural > support as it is offered by GNU gettext. Thanks for the warning. :) > I'd be interested to hear what other requirements come up. We are interes= ted > in improving the xnap commons code base, if the requirements prove to add= to > the general value of the components. I'll keep posting as I notice things. Thanks Felix! Sean |
From: Felix B. <bf...@gm...> - 2005-10-27 23:19:16
|
On Thursday 27 October 2005 23:02, Sean Crotty wrote: > > Could you be a bit more specific as to what components you would expect > > to have support for component orientation and in what way? Does this only > > affect text components? > > I think all the xnap commons GUI components need work in this regard. After a first couple of tests it doesn't look that bad after all, the layout managers are orientation aware, so I just had to change a few constructor calls from new Boxlayout(BoxLayout.X_AXIS) to new BoxLayout(BoxLayout.LINE_AXIS) to get the desired effects. For the completion boxes we will have to add a propertychangelistener to the text fields to keep the orientations in sync. > For example, FileChooserPanel inherits from java.awt.Component and > thus offers an API to setComponentOrientation( > java.awt.ComponentOrientation o ). Unfortunately, from what I can > tell, using this API this does not rearrange the parts (text box, edit > box, folder icon) of the FileChooserPanel based on the > ComponentOrientation passed in. If I do: > > FileChooserPanel chooser = new FileChooserPanel(20); > chooser.setComponentOrientation(ComponentOrientation.RIGHT_TO_LEFT); > The shown FileChooserPanel does not seem to rearrange for > right-to-left languages like Arabic or Hebrew. > This could be remedied by what I described above. > Other xnap commons GUI components like the various > org.xnap.commons.gui.Dialogs hide access to the underlying > java.awt.Component and so even setting the ComponentOrientation is > impossible for them. Are you supposed to call that for every component individually in the normal use case or shouldn't it be taken from the currently set locale, see static ComponentOrientation getOrientation(Locale locale) So if you set the locale before you use any of the dialogs they should use the proper layout after we made the necessary changes, at least I'd hope it would work like this. > The reason I ask is that I'm evaluating frameworks that will help > facilitate development on a new project. However, this project must be > fully I18N, G11N, L10N compliant. This includes supporting physical > layout changes of GUI components for languages written right-to-left > or even vertically. > > Many of the tools in xnap commons are attractive for my needs. If I > can negotiate the time, I might even be able to devote some time to > providing such support in the xnap commons source. It will really come > down to whether the benefit of using the xnap commons components in > their current state more than offset the time required to get them > fully I18N-able. Maybe I should warn you that our current I18n class lacks proper plural support as it is offered by GNU gettext. I'd be interested to hear what other requirements come up. We are interested in improving the xnap commons code base, if the requirements prove to add to the general value of the components. Thanks, Felix -- Try Debian GNU/Linux! http://www.felix.beldesign.de/ |
From: Sean C. <sc...@gm...> - 2005-10-27 21:09:12
|
On 10/27/05, Felix Berger <bf...@gm...> wrote: > On Thursday 27 October 2005 20:16, Sean Crotty wrote: > > > >From what I see, most of the xnap components don't support > > > > java.awt.ComponentOrientation other than LEFT_TO_RIGHT. > > > > 1) Am I right about this? > > I think you're right about this. > > > 2) If so, is there any plan to enable this? > > Could you be a bit more specific as to what components you would expect t= o > have support for component orientation and in what way? Does this only af= fect > text components? I think all the xnap commons GUI components need work in this regard. For example, FileChooserPanel inherits from java.awt.Component and thus offers an API to setComponentOrientation( java.awt.ComponentOrientation o ). Unfortunately, from what I can tell, using this API this does not rearrange the parts (text box, edit box, folder icon) of the FileChooserPanel based on the ComponentOrientation passed in. If I do: FileChooserPanel chooser =3D new FileChooserPanel(20); chooser.setComponentOrientation(ComponentOrientation.RIGHT_TO_LEFT); The shown FileChooserPanel does not seem to rearrange for right-to-left languages like Arabic or Hebrew. Other xnap commons GUI components like the various org.xnap.commons.gui.Dialogs hide access to the underlying java.awt.Component and so even setting the ComponentOrientation is impossible for them. The reason I ask is that I'm evaluating frameworks that will help facilitate development on a new project. However, this project must be fully I18N, G11N, L10N compliant. This includes supporting physical layout changes of GUI components for languages written right-to-left or even vertically. Many of the tools in xnap commons are attractive for my needs. If I can negotiate the time, I might even be able to devote some time to providing such support in the xnap commons source. It will really come down to whether the benefit of using the xnap commons components in their current state more than offset the time required to get them fully I18N-able. I apologize if I way off base here. I've been working through O'Reilly's "Java Internationalization" (ISBN 0-596-00019-7) for information on how to make my application compliant. There is a chapter in there specifically regarding I18N GUIs. Thanks, Sean |
From: Felix B. <bf...@gm...> - 2005-10-27 20:05:39
|
On Thursday 27 October 2005 20:16, Sean Crotty wrote: > >From what I see, most of the xnap components don't support > > java.awt.ComponentOrientation other than LEFT_TO_RIGHT. > > 1) Am I right about this? I think you're right about this. > 2) If so, is there any plan to enable this? Could you be a bit more specific as to what components you would expect to have support for component orientation and in what way? Does this only affect text components? Thanks, Felix -- Try Debian GNU/Linux! http://www.felix.beldesign.de/ |
From: Sean C. <sc...@pi...> - 2005-10-27 18:16:37
|
>From what I see, most of the xnap components don't support java.awt.ComponentOrientation other than LEFT_TO_RIGHT. 1) Am I right about this? 2) If so, is there any plan to enable this? Thanks! Sean |
From: Felix B. <bf...@gm...> - 2005-09-30 09:41:56
|
On Friday 30 September 2005 02:39, Steffen Pingel wrote: > I got stuck preparing the next release... as I told you before: cvs must > alwayz complize!!!!! My JHylaFAX customers are impatiently waiting for the > next version so pleaz this needz to be fixed know!!!! Pleaz trie again now. Downloaded cvs at http://ftp.gnu.org/non-gnu/cvs/, it compiled, nothing I can doe about dis ;-) Felix -- Try Debian GNU/Linux! http://www.felix.beldesign.de/ |
From: Steffen P. <ste...@gm...> - 2005-09-30 00:39:39
|
Hi, I got stuck preparing the next release... as I told you before: cvs must alwayz complize!!!!! My JHylaFAX customers are impatiently waiting for the next version so pleaz this needz to be fixed know!!!! Steffen PS: And please... don't take me seriously whatsoever ;). -- Steffen Pingel - ste...@gm... - http://steffenpingel.de |
From: Steffen P. <ste...@gm...> - 2005-08-25 00:01:56
|
Hi, I am proud to announce the first release of XNap Commons. It is available from our maven repository and from the SourceForge file release system. I have also submitted a request for a Freshmeat project that will hopefully be approved within the next few days. Felix has setup a LaunchPad project where translators can easily add localization for any language through a web interface: https://launchpad.net/products/xnap-commons/+translations Steffen -- Steffen Pingel - ste...@gm... - http://steffenpingel.de |
From: Steffen P. <ste...@gm...> - 2005-08-20 02:22:33
|
Hi, I have updated the web page to reflect the current cvs statistics and code coverage. Unfortunatelly jcoverage can't cope with Java 5.0 very well therefore I if have generated reports with clover that are available at: http://xnap-commons.sourceforge.net/clover/ We are currently in the process of preparing the first release. There are still a few bugs to fix and some documentation to write. We are aiming to keep the API as stable as we can, so we will try to clean it up as good as we can and not rush the release. Nevertheless I expect it to be ready within the next few days :). Steffen -- Steffen Pingel - ste...@gm... - http://steffenpingel.de |
From: Felix B. <bf...@gm...> - 2005-08-17 10:38:20
|
On Wednesday 17 August 2005 02:59, Steffen Pingel wrote: > I guess I didn't express myself clearly as I should have... I didn't > acctually do the clean up. I just though I should mention it in case anyone > feels like doing it :). Done. > True, so we should go ahead and remove these descriptions all along. Done. Felix -- Try Debian GNU/Linux! http://www.felix.beldesign.de/ |
From: Steffen P. <ste...@gm...> - 2005-08-17 01:00:21
|
Hi, > > I have added a German translation. During the process I noticed that some > > of the strings could use some polish (mostly stuff like directory vs. > > folder)... > > Did you go with "folder"? Native speakers told me that's the non-technical > and less scaring term for users (one syllable less ;-)). I guess I didn't express myself clearly as I should have... I didn't acctually do the clean up. I just though I should mention it in case anyone feels like doing it :). > > throw new IllegalArgumentException(I18n.tr("Separator must not be > > empty")); > > Funny, where was that code? It is part of the pre-condition checks in most StringHelper methods. I didn't bother to look up who wrote it. I guess it was me anyways. > > Also I am thinking about removing the tooltips from the dialog buttons in > > favour of "What's This" support. > > > > Any opinions? > > We don't have that support yet, but I'd say yes, those button texts are > very common and should be self-explanatory. True, so we should go ahead and remove these descriptions all along. Steffen -- Steffen Pingel - ste...@gm... - http://steffenpingel.de |
From: Felix B. <bf...@gm...> - 2005-08-16 23:37:52
|
On Tuesday 16 August 2005 22:07, Steffen Pingel wrote: > I have added a German translation. During the process I noticed that some > of the strings could use some polish (mostly stuff like directory vs. > folder)... Did you go with "folder"? Native speakers told me that's the non-technical and less scaring term for users (one syllable less ;-)). > I removed a funny call to I18n.tr() for an IllegalArgumentException in > StringHelper: > > throw new IllegalArgumentException(I18n.tr("Separator must not be > empty")); Funny, where was that code? > I don't think translating those makes sense, since the user should never be > bothered with programming errors. For non runtime exeptions that may be > displayed, having a translation may be useful. Maybe one of us did it just out of the mere joy of so easily being able to do it :-) > Also I am thinking about removing the tooltips from the dialog buttons in > favour of "What's This" support. > > Any opinions? We don't have that support yet, but I'd say yes, those button texts are very common and should be self-explanatory. Felix -- Try Debian GNU/Linux! http://www.felix.beldesign.de/ |
From: Steffen P. <ste...@gm...> - 2005-08-16 20:07:57
|
Hi, I have added a German translation. During the process I noticed that some of the strings could use some polish (mostly stuff like directory vs. folder)... I removed a funny call to I18n.tr() for an IllegalArgumentException in StringHelper: throw new IllegalArgumentException(I18n.tr("Separator must not be empty")); I don't think translating those makes sense, since the user should never be bothered with programming errors. For non runtime exeptions that may be displayed, having a translation may be useful. Also I am thinking about removing the tooltips from the dialog buttons in favour of "What's This" support. Any opinions? BTW, Felix will setup a translation interface at https://launchpad.net/products/xnap-commons shortly so anyone who wants to help with localization will be able to go ahead. Steffen -- Steffen Pingel - ste...@gm... - http://steffenpingel.de |
From: Steffen P. <ste...@gm...> - 2005-08-14 17:45:20
|
Hi, I have setup another sub project on the XNap Commons page that contains the code of the XNap package manager: http://xnap-commons.sourceforge.net/package-manager/ The point is distribute the dependency viewer for people to play with and to have the source code split out as a separate package in case someone wants to fiddle with package manager. Steffen -- Steffen Pingel - ste...@gm... - http://steffenpingel.de |