Menu
▾
▴
jmoney-devel
|
From: <jav...@mi...> - 2008-12-05 04:20:10
|
Hi Dimitri, It is really good of you to help out with the translations. I guess the important and most stable plug-ins are the jdbcdatastore plug-in (though that probably doesn't have a lot of user messages except error messages which probably are not complete), the currency plug-in (hasn't changed in years but essential if you use more than one currency). I have just added a search plug-in, which although just a week old, is probably going to get a bit of use and I don't expect the existing messages to change. Some of the messages are the same as in Eclipse so we could probably use Eclipse translations for those. The stock plug-in is fairly core (at least for me as I am just starting to use it in production), but there may be a few changes over the next few months as its usage increases. The reconciliation plug-in is fairly core, being the plug-in that handles import of data downloaded from Bank's web sites etc. This is fairly stable too, though the pattern matching used to automatically categorize entries may need to be made more user friendly. It uses the Perl pattern matching available in Java which makes it very powerful for me but probably too difficult for non-developer users as you have to enter the raw patterns through the UI. Plug-ins not to do are the category plug-in, as that is no longer needed. I personally consider the report and chart plug-ins to be disused. The chart plug-in never worked for me and the developer has left the team. I believe BIRT is a more strategic charting product for us to use though I have not actually produced a chart using it. Then there are the plug-ins specific to a more limited set of users, Ameritrade and Paypal. Anyway, that is a quick overview of most of the plug-ins and how I see them. I note that you use the class name as a prefix to the keys. I am sure this is a common convention, but I have concerned that I am messing this up during re-factoring. For example if I move code from Actions into Handlers then the class names will no longer match. I am not sure what to do about this, though one solution would be to use some other convention for the keys, such as where the message is used in the UI instead of where it is used in the code. Nigel > -------Original Message------- > From: HERLA Dimitri <dim...@nr...> > Subject: JMoney : i18n... > Sent: 03 Dec '08 12:13 > > Hi, > > For you, what is the order to make i18n change on plugin ? > I have already made : > net.sf.jmoney > net.sf.jmoney.serializeddatastore > > Regards > > Dimitri > > > Dimitri HERLA > Responsable de service | Nouvelles Technologies > > > NETWORK RESEARCH BELGIUM > Parc Industriel des Hauts Sarts, 2ème avenue - 65 | 4040 Herstal > Tél. : +32 4 249 77 15 > [LINK: mailto:88d...@nr...] dim...@nr... | [LINK: > http://www.nrb.be/] www.nrb.be |
|
From: <jav...@mi...> - 2008-12-06 20:17:03
|
I have just checked in some changes that allow the user to open a new session in a new window, keeping the old session open. 'Open in New Window' menu item. Even if it is not felt that this is a useful feature, I think it is a better architecture. By using the session manager object as input to the workbench page, we can remove some kludgy code that restores the session from whatever view happens to be restored first. I have also replaced the navigation view with a version that is based on the CNF (Common Navigator Framework). This is something I had sitting in a workspace for almost a year but had never checked in because I wasn't sure it was fully working. The two are sort of tied together, and I did not want to have to implement the changes needed in the old navigator view if it was going away. By using the CNF, plug-in developers have considerably more ability to contribute to the navigator view than they had before, and also allows us to remove bits of our custom extension points. There is still a bit of cleanup to do, but I think it is just about usable and the cleanup work should all be straight forward. Nigel > -------Original Message------- > From: Johann Gyger <jo...@gy...> > Subject: Re: JMoney : i18n... > Sent: 05 Dec '08 07:06 > > Hi Nigel, > > On Fri, Dec 5, 2008 at 05:20, <jav...@mi...> wrote: > > Hi Dimitri, > > > > It is really good of you to help out with the translations. I guess the important and most stable plug-ins are the jdbcdatastore plug-in (though that probably doesn't have a lot of user messages except error messages which probably are not complete), the currency plug-in (hasn't changed in years but essential if you use more than one currency). I have just added a search plug-in, which although just a week old, is probably going to get a bit of use and I don't expect the existing messages to change. Some of the messages are the same as in Eclipse so we could probably use Eclipse translations for those. The stock plug-in is fairly core (at least for me as I am just starting to use it in production), but there may be a few changes over the next few months as its usage increases. The reconciliation plug-in is fairly core, being the plug-in that handles import of data downloaded from Bank's web sites etc. This is fairly stable too, though the pattern matching used to autom! > > atically categorize entries may need to be made more user friendly. It uses the Perl pattern matching available in Java which makes it very powerful for me but probably too difficult for non-developer users as you have to enter the raw patterns through the UI. > > > > Plug-ins not to do are the category plug-in, as that is no longer needed. I personally consider the report and chart plug-ins to be disused. The chart plug-in never worked for me and the developer has left the team. I believe BIRT is a more strategic charting product for us to use though I have not actually produced a chart using it. > > So shall I remove those plug-ins or do we need alternatives before > removing them? The chart plug-in never worked for me either so this > one will vanish for sure. For the category plug-in we will probably > need a replacement based on property editors as you proposed. The > report plug-in could be removed without replacement at the moment. > > WDYT? > > Regards, > Johann > > > > > Then there are the plug-ins specific to a more limited set of users, Ameritrade and Paypal. > > > > Anyway, that is a quick overview of most of the plug-ins and how I see them. > > > > I note that you use the class name as a prefix to the keys. I am sure this is a common convention, but I have concerned that I am messing this up during re-factoring. For example if I move code from Actions into Handlers then the class names will no longer match. I am not sure what to do about this, though one solution would be to use some other convention for the keys, such as where the message is used in the UI instead of where it is used in the code. > > > > Nigel > > > >> -------Original Message------- > >> From: HERLA Dimitri <dim...@nr...> > >> Subject: JMoney : i18n... > >> Sent: 03 Dec '08 12:13 > >> > >> Hi, > >> > >> For you, what is the order to make i18n change on plugin ? > >> I have already made : > >> net.sf.jmoney > >> net.sf.jmoney.serializeddatastore > >> > >> Regards > >> > >> Dimitri > >> > >> > >> Dimitri HERLA > >> Responsable de service | Nouvelles Technologies > >> > >> > >> NETWORK RESEARCH BELGIUM > >> Parc Industriel des Hauts Sarts, 2ème avenue - 65 | 4040 Herstal > >> Tél. : +32 4 249 77 15 > >> [LINK: mailto:88d...@nr...] dim...@nr... | [LINK: > >> http://www.nrb.be/] www.nrb.be > > > |
|
From: <jav...@mi...> - 2008-12-06 22:10:24
|
I have checked in some changes to connect the objects to the Eclipse property sheet. You need to open the property sheet using the Open View menu item under Window. We probably need to make the properties more accessible than this, but I am not sure how. Either we could make the view always open in the perspective or add a 'Properties' at the bottom of the context menu. With this I think we can remove the categories plug-in, but we should be sure all the messages are moved first so we don't lose translations. Nigel > -------Original Message------- > From: Johann Gyger <jo...@gy...> > Subject: Re: JMoney : i18n... > Sent: 05 Dec '08 07:06 > > Hi Nigel, > > On Fri, Dec 5, 2008 at 05:20, <jav...@mi...> wrote: > > Hi Dimitri, > > > > It is really good of you to help out with the translations. I guess the important and most stable plug-ins are the jdbcdatastore plug-in (though that probably doesn't have a lot of user messages except error messages which probably are not complete), the currency plug-in (hasn't changed in years but essential if you use more than one currency). I have just added a search plug-in, which although just a week old, is probably going to get a bit of use and I don't expect the existing messages to change. Some of the messages are the same as in Eclipse so we could probably use Eclipse translations for those. The stock plug-in is fairly core (at least for me as I am just starting to use it in production), but there may be a few changes over the next few months as its usage increases. The reconciliation plug-in is fairly core, being the plug-in that handles import of data downloaded from Bank's web sites etc. This is fairly stable too, though the pattern matching used to autom! > > atically categorize entries may need to be made more user friendly. It uses the Perl pattern matching available in Java which makes it very powerful for me but probably too difficult for non-developer users as you have to enter the raw patterns through the UI. > > > > Plug-ins not to do are the category plug-in, as that is no longer needed. I personally consider the report and chart plug-ins to be disused. The chart plug-in never worked for me and the developer has left the team. I believe BIRT is a more strategic charting product for us to use though I have not actually produced a chart using it. > > So shall I remove those plug-ins or do we need alternatives before > removing them? The chart plug-in never worked for me either so this > one will vanish for sure. For the category plug-in we will probably > need a replacement based on property editors as you proposed. The > report plug-in could be removed without replacement at the moment. > > WDYT? > > Regards, > Johann > > > > > Then there are the plug-ins specific to a more limited set of users, Ameritrade and Paypal. > > > > Anyway, that is a quick overview of most of the plug-ins and how I see them. > > > > I note that you use the class name as a prefix to the keys. I am sure this is a common convention, but I have concerned that I am messing this up during re-factoring. For example if I move code from Actions into Handlers then the class names will no longer match. I am not sure what to do about this, though one solution would be to use some other convention for the keys, such as where the message is used in the UI instead of where it is used in the code. > > > > Nigel > > > >> -------Original Message------- > >> From: HERLA Dimitri <dim...@nr...> > >> Subject: JMoney : i18n... > >> Sent: 03 Dec '08 12:13 > >> > >> Hi, > >> > >> For you, what is the order to make i18n change on plugin ? > >> I have already made : > >> net.sf.jmoney > >> net.sf.jmoney.serializeddatastore > >> > >> Regards > >> > >> Dimitri > >> > >> > >> Dimitri HERLA > >> Responsable de service | Nouvelles Technologies > >> > >> > >> NETWORK RESEARCH BELGIUM > >> Parc Industriel des Hauts Sarts, 2ème avenue - 65 | 4040 Herstal > >> Tél. : +32 4 249 77 15 > >> [LINK: mailto:88d...@nr...] dim...@nr... | [LINK: > >> http://www.nrb.be/] www.nrb.be > > > |
|
From: Johann G. <jo...@gy...> - 2008-12-05 07:06:36
|
Hi Nigel, On Fri, Dec 5, 2008 at 05:20, <jav...@mi...> wrote: > Hi Dimitri, > > It is really good of you to help out with the translations. I guess the important and most stable plug-ins are the jdbcdatastore plug-in (though that probably doesn't have a lot of user messages except error messages which probably are not complete), the currency plug-in (hasn't changed in years but essential if you use more than one currency). I have just added a search plug-in, which although just a week old, is probably going to get a bit of use and I don't expect the existing messages to change. Some of the messages are the same as in Eclipse so we could probably use Eclipse translations for those. The stock plug-in is fairly core (at least for me as I am just starting to use it in production), but there may be a few changes over the next few months as its usage increases. The reconciliation plug-in is fairly core, being the plug-in that handles import of data downloaded from Bank's web sites etc. This is fairly stable too, though the pattern matching used to autom! > atically categorize entries may need to be made more user friendly. It uses the Perl pattern matching available in Java which makes it very powerful for me but probably too difficult for non-developer users as you have to enter the raw patterns through the UI. > > Plug-ins not to do are the category plug-in, as that is no longer needed. I personally consider the report and chart plug-ins to be disused. The chart plug-in never worked for me and the developer has left the team. I believe BIRT is a more strategic charting product for us to use though I have not actually produced a chart using it. So shall I remove those plug-ins or do we need alternatives before removing them? The chart plug-in never worked for me either so this one will vanish for sure. For the category plug-in we will probably need a replacement based on property editors as you proposed. The report plug-in could be removed without replacement at the moment. WDYT? Regards, Johann > > Then there are the plug-ins specific to a more limited set of users, Ameritrade and Paypal. > > Anyway, that is a quick overview of most of the plug-ins and how I see them. > > I note that you use the class name as a prefix to the keys. I am sure this is a common convention, but I have concerned that I am messing this up during re-factoring. For example if I move code from Actions into Handlers then the class names will no longer match. I am not sure what to do about this, though one solution would be to use some other convention for the keys, such as where the message is used in the UI instead of where it is used in the code. > > Nigel > >> -------Original Message------- >> From: HERLA Dimitri <dim...@nr...> >> Subject: JMoney : i18n... >> Sent: 03 Dec '08 12:13 >> >> Hi, >> >> For you, what is the order to make i18n change on plugin ? >> I have already made : >> net.sf.jmoney >> net.sf.jmoney.serializeddatastore >> >> Regards >> >> Dimitri >> >> >> Dimitri HERLA >> Responsable de service | Nouvelles Technologies >> >> >> NETWORK RESEARCH BELGIUM >> Parc Industriel des Hauts Sarts, 2ème avenue - 65 | 4040 Herstal >> Tél. : +32 4 249 77 15 >> [LINK: mailto:88d...@nr...] dim...@nr... | [LINK: >> http://www.nrb.be/] www.nrb.be > |
Thanks for helping keep SourceForge clean.
X