Hello,
Thanks for the "fantastic project" :-)
In fact, I have no plan. Yapbam is a hobby and the software I personally use to manage my bank accounts. Currently, I have no time to enhance it much (Add functonnalities, switch from deprecated Swing library to something more modern, create an Android version, etc ...). Maybe when I will be retired (between some month and some years).
Nevertheless, I accept any help ;-)
Best regards,
Jean-Marc Astesana
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Jean-Marc,
I too have been using YapBam for many years and I also busy with taken care of the translation of the program into Italian but I am sorry to see that the project (although it is already very complete and free of critical bugs) does not have a road and a constant release schedule like projects similar for example GnuCash which is constantly updated by the community. Personally I would like to do something for the YapBam project but I don't know which task to follow and I also find that the source code could have more visibility on platforms like GitHub or GitLab also with a view to capturing more developers and more users ...
I have knowledge of Java and PHP, are there any simple tasks that I could follow in the next period?
Marco
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Marco,
Thanks (again) for your great job on Yapbam translation :-)
Of course, Yapbam is not GnuCash. I started this project 12 years ago because I found GnuCash (and its competitors) to much complicated for me. I agree that sourceforge is no more the mainstream to share open source project, and probably I should migrate to GitHub like some other projects I've created on that (Microsoft !) platform. If you have a look at https://github.com/fathzer?tab=repositories, you will see a "YapbamDroid" project, an old try to port Yapbam to Android (which is probably The thing that people ask me the most). Unfortunately, I was not good enough on Android to make it a good product.
I've also created an "organization" named Yapbam in order to transfer the sourceforge hosted code there ... but not did it yet.
What could be done :
- Migrate to Github or Gitlab (I use Gitlab at work, it's suitable too).
- Develop an android version. That's a lot of work, and it's quite hard, especially to ensure the app could work without Internet connexion and synchronized its data with the Desktop app when network is there again.
- Clean the "plugin architecture" of the Desktop version. Today the architecture is almost there, but the plugin should depend on the whole Yapbam app! I think, its not the easiest thing to start (Probably it should be my personal highest priority).
- One of the accepted feature request posted on sourceforge.
- Switch the GUI from (deprecated) Swing to JavaFX (hope its mature enough).
I'm currently on holiday, with no dev environment and intermittent Internet connection, so I can't help before end of month.
Best regards,
Jean-Marc
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Regarding a personal task I think I will start working on ticket # 86 (https://sourceforge.net/p/yapbam/feature-requests/86/) hoping that it is not too complex to deal with, according to my opinion Swing is still the best solution for Yapbam also because it allows it to run on a standard jvm without further installations and allows you to make it 100% portable also it does not seem to me that apart from the look that can be fixed with a special library for example FlatLaf (https://github.com/JFormDesigner/FlatLaf) Yapbam has no limitations related to Swing.
As for the plugins, those present in yapbam are not real plugins because they cannot access the app data it would be better to call them external utilities, by plugin we should mean a jar package stored in a special folder that, loaded at runtime, executes operations also on the data present in the app.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
Thanks for the "fantastic project" :-)
In fact, I have no plan. Yapbam is a hobby and the software I personally use to manage my bank accounts. Currently, I have no time to enhance it much (Add functonnalities, switch from deprecated Swing library to something more modern, create an Android version, etc ...). Maybe when I will be retired (between some month and some years).
Nevertheless, I accept any help ;-)
Best regards,
Jean-Marc Astesana
Hi Jean-Marc,
I too have been using YapBam for many years and I also busy with taken care of the translation of the program into Italian but I am sorry to see that the project (although it is already very complete and free of critical bugs) does not have a road and a constant release schedule like projects similar for example GnuCash which is constantly updated by the community. Personally I would like to do something for the YapBam project but I don't know which task to follow and I also find that the source code could have more visibility on platforms like GitHub or GitLab also with a view to capturing more developers and more users ...
I have knowledge of Java and PHP, are there any simple tasks that I could follow in the next period?
Marco
Hi Marco,
Thanks (again) for your great job on Yapbam translation :-)
Of course, Yapbam is not GnuCash. I started this project 12 years ago because I found GnuCash (and its competitors) to much complicated for me. I agree that sourceforge is no more the mainstream to share open source project, and probably I should migrate to GitHub like some other projects I've created on that (Microsoft !) platform. If you have a look at https://github.com/fathzer?tab=repositories, you will see a "YapbamDroid" project, an old try to port Yapbam to Android (which is probably The thing that people ask me the most). Unfortunately, I was not good enough on Android to make it a good product.
I've also created an "organization" named Yapbam in order to transfer the sourceforge hosted code there ... but not did it yet.
What could be done :
- Migrate to Github or Gitlab (I use Gitlab at work, it's suitable too).
- Develop an android version. That's a lot of work, and it's quite hard, especially to ensure the app could work without Internet connexion and synchronized its data with the Desktop app when network is there again.
- Clean the "plugin architecture" of the Desktop version. Today the architecture is almost there, but the plugin should depend on the whole Yapbam app! I think, its not the easiest thing to start (Probably it should be my personal highest priority).
- One of the accepted feature request posted on sourceforge.
- Switch the GUI from (deprecated) Swing to JavaFX (hope its mature enough).
I'm currently on holiday, with no dev environment and intermittent Internet connection, so I can't help before end of month.
Best regards,
Jean-Marc
Regarding a personal task I think I will start working on ticket # 86 (https://sourceforge.net/p/yapbam/feature-requests/86/) hoping that it is not too complex to deal with, according to my opinion Swing is still the best solution for Yapbam also because it allows it to run on a standard jvm without further installations and allows you to make it 100% portable also it does not seem to me that apart from the look that can be fixed with a special library for example FlatLaf (https://github.com/JFormDesigner/FlatLaf) Yapbam has no limitations related to Swing.
As for the plugins, those present in yapbam are not real plugins because they cannot access the app data it would be better to call them external utilities, by plugin we should mean a jar package stored in a special folder that, loaded at runtime, executes operations also on the data present in the app.
Hi,
You can start with that (take the plunge ;-)).
I was thinKing JavaFX is included in recent standard JRE.
There's really a plugin architecture. You can have a look at https://sourceforge.net/p/yapbam/code/HEAD/tree/Yapbam/src/net/yapbam/gui/statementview/StatementViewPlugin.java for an example. If I remember well, you can't yet easily put jars in a specific folder, but many parts of Yapbam are "internal" plugins.
Best regards