I also suggested that in a previous message in this thread
https://s.apache.org/eSSf
pro: less work, less risks
cons: what about the thirdparty accounting elements? Clearly those should be
plugins
Jacques
Le 09/09/2018 à 09:49, Pierre Smits a écrit :
Instead of disentangling the AR and AP web-apps from accounting and
recreating them as new components in the plugins repository I suggest to
bring following UI functionalities under subsections of the Accounting
web-app:
Overviews [1] and [2] of outstanding invoices to become menu-items under
the InvoiceTabBar
[1] https://demo-trunk.ofbiz.apache.org/ap/control/listReports
[2] https://demo-trunk.ofbiz.apache.org/ar/control/listReports
The rest of the functionalities made available under the AP and AR web-apps
are already available in Accounting and having these in separate plugin
components adds - at the moment, with current designs - no extra value on
top of the existing functionalities in accounting.
Best regards,
Pierre Smits
Apache Trafodion <https://trafodion.apache.org>, Vice President
Apache Directory <https://directory.apache.org>, PMC Member
Apache Incubator <https://incubator.apache.org>, committer
*Apache OFBiz <https://ofbiz.apache.org>, contributor (without privileges)
since 2008*
Apache Steve <https://steve.apache.org>, committer
On Fri, Sep 7, 2018 at 11:58 AM, Nicolas Malin <[email protected]>
wrote:
Hello,
With you returns, I open the issue OFBIZ-10552 [1] with my first try.
Cheers,
Nicolas
[1] https://issues.apache.org/jira/browse/OFBIZ-10552
On 01/09/2018 14:09, Nicolas Malin wrote:
Hello,
After analyze the webapp accounting AR and accounting AP, I didn't see
any logic to keep them on the functional framework. The main webapp is
accounting, AP/AR are a business orientation that we can load at demand
through plugins.
Your opinion ?
PS: In the same idea we can move on separate plugin all thirdparty
accounting element to slimdown the accounting component and must harness
the plugin system :)
Nicolas
