Here are the most popular ideas ever about OpenPetra.org.
Document Management
Written by pokorra the 25 Aug 09 at 11:58.
New
How important would it be to have document management integrated with OpenPetra?
This would mean that PDFs, Word files, Excel sheets and other file types can be associated with partners, finance transactions, personnel records, conferences etc.
Access permissions would be integrated in the OpenPetra user management
Handling Exchange rates
Written by pokorra the 26 Aug 10 at 09:21.
New
at the moment, there are 3 tables for storing exchange rates: a_daily_exchange_rate, a_corporate_exchange_rate, a_prev_year_corp_ex_rate
This is quite complicated for reports.
Webinterface to have an alternative to the fat .net client
Written by pokorra the 16 Mar 10 at 08:38.
New
Advantages of a Web Interface are that the users don't need to patch their client, deploying a new version can be controlled on the server.
Depending on the technology used, it does not require to install additional software (eg. .Net) on the workstations, and can just run in the browser.
Nowadays even AJAX solutions can be quite powerful, so the user should be able to work quite comfortably.
We could rewrite the Winforms generator to produce any other code we like.
Solution #1:
Generate the UI with extJS
Written by
pokorra the 16 Mar 10 at 08:38.
This is a powerful javascript and AJAX solution, with lots of GUI controls.
It has solutions for communicating with the server via SOAP etc.
We could modify our Winforms generator to produce the appropriate Javascript code.
A lot of thought would need to be put in managing data on the client side, and about how to minimise coding the verification code both in c# and javascript.
The GPL license of extJS should fit nicely for OpenPetra.
This is a powerful javascript and AJAX solution, with lots of GUI controls.
It has solutions for communicating with the server via SOAP etc.
We could modify our Winforms generator to produce the appropriate Javascript code.
A lot of thought would need to be put in managing data on the client side, and about how to minimise coding the verification code both in c# and javascript.
The GPL license of extJS should fit nicely for OpenPetra.
Solution #2:
Silverlight web client
Written by
pokorra the 16 Mar 10 at 08:38.
Advantages are that the code is in C#.
The gui elements should be quite similar as in Winforms.
Support for printing was added in Silverlight 4.0, which used to be a show stopper.
Disadvantages are that the user has to install the Silverlight (or Moonlight for Linux) runtime environment in order to be able to use the client in the browser.
Advantages are that the code is in C#.
The gui elements should be quite similar as in Winforms.
Support for printing was added in Silverlight 4.0, which used to be a show stopper.
Disadvantages are that the user has to install the Silverlight (or Moonlight for Linux) runtime environment in order to be able to use the client in the browser.
Solution #3:
No need for a web client
Written by
pokorra the 16 Mar 10 at 08:49.
the OpenPetra client already has automatic patches ie it is always uptodate.
The fat client is much easier to use.
We should focus on getting the functionality done, and fully support the client running on Mono, then we can cover MacOS and Linux as well.
the OpenPetra client already has automatic patches ie it is always uptodate.
The fat client is much easier to use.
We should focus on getting the functionality done, and fully support the client running on Mono, then we can cover MacOS and Linux as well.
Preview effect of posting a GL batch to avoid accounting mistakes
Written by pokorra the 3 Sep 09 at 12:24.
New
this was reported by a user; they would like to be able to see the balances of the accounts involved, so that they can quickly estimate if the batch posts to the correct places; otherwise it would be a hassle to adjust transactions etc to fix mistakes.
Solution #1:
Preview Report
Written by
pokorra the 3 Sep 09 at 12:24.
a preview report should be displayed, that shows the current balances and the balance that would take effect after the posting of the batch. The user can then confirm the posting, or cancel, and change the batch.
implementation: a special posting function which rolls back at the end, after getting old balances of accounts (datarowview.oldstate?), and new, display somehow easy to see, in a grid message box
a preview report should be displayed, that shows the current balances and the balance that would take effect after the posting of the batch. The user can then confirm the posting, or cancel, and change the batch.
implementation: a special posting function which rolls back at the end, after getting old balances of accounts (datarowview.oldstate?), and new, display somehow easy to see, in a grid message box
simple GL transactions with just 2 account/cost centres
Written by pokorra the 3 Sep 09 at 12:36.
New
a simplified transaction entry option for non-bookkeepers where you can just enter the actual event (eg. I spent £20 on a book) and OpenPetra will generate the two transactions that need to go in the GL.
(Attention: In Petra, a transaction does not have same credit and debit totals, but only has one amount to it; we might need to change the wording in the language files...)