...
The following is a proposal for the definition of a list of short and medium term tasks list: your input, suggestions and help is welcome. Please add your comment at the bottom of the page.
Legenda:
- "People interested": the people that think that the feature should be considered a priority for the project (in the short term)
- "People willing to help": persons that are in the position to help with the development of the task; if possible specify an approximately number of hours per week or month to give an idea of the total resources available for each task
Complete the support for VAT (Value-Added-Tax)
See the project's specific page here.
People interested: Jacques Le Roux,
People willing to help: Jacques Le Roux
...
Content
Table of Contents |
---|
Prioritized tasks by order of appearance
Introduce a plugin system
Replace Minilang and widgets actions by a Groovy DSL
...
Not yet prioritized tasks (backlog)
Add support for online contextual help
...
help
...
Sharan said today (2014/01/28) that she wants to continue to help.
...
...
server | ASF JIRA |
---|---|
serverId | 5aa69414-a9e9-3523-82ec-879b028fb15b |
key | OFBIZ-4274 |
...
Improve the Content Management Component
have a content management system which is comparable, in terms of features, to the more popular open source content management applications
People interested:
People willing to help:
Add at least a versionning system to the content management
Sascha built the foundations
Jira | ||||||
---|---|---|---|---|---|---|
|
...
have a SFA/CRM which is comparable, in terms of features, to the more popular open source SFA/CRM applicationsPeople interested: Pierre Smits, Jacques Le Roux People willing to help: Jacques Le Roux
Improve the Project Manager Component
Improve and enhance the Project Manager ComponentPeople interested: Pierre Smits People willing to help: Pierre Smits
Ecommerce component enhancements
See the project specific page here
People interested: Anil Patel, Jacques Le Roux
People willing to help: Anil Patel, Jacques Le Roux
Improve SEO with
Jira | ||||||
---|---|---|---|---|---|---|
|
Complete the migration of older bsh/ftl files to widgets
...
Backend widget & application HTML clean-up
...
Jira | ||||||
---|---|---|---|---|---|---|
|
Manufacturing improvement
People interested: Pierre Smits
People willing to help: Pierre Smits
Especially regarding lifecycle mgt of recipes (BoM and production schema) and on in-situ adding materials, production resources and outputs of end and by-products (like we had the discussion on dev ML about in September 2013).
Expense Declaration
...
Jira | ||||||
---|---|---|---|---|---|---|
|
Theme framework (Bootstrap, Zurb, etc.) integration (for both back and frontend)
...
http://markmail.org/message/i7fnxid55cq5uiiz
http://markmail.org/thread/6hvrvzkdz2huennv
Introduce Websocket usage
People interested: Jacques Le Roux
People willing to help: Jacques Le Roux
See
Jira | ||||||
---|---|---|---|---|---|---|
|
Services exposed as RESTful web services
...
People willing to help: Adrian Crum, Jacques Le RouxREST Service Implementation
Export service using REST Jira
OFBIZ-4274 | ||||||
Jira | ||||||
---|---|---|---|---|---|---|
|
...
(this section related with the "UI (User Interface) enhancements" section, to be clarified)
People interested: Ean Schuessler
People willing to help: Ean Schuessler
It would be genuinely interesting if we could write a client side form widget interpreter that would delegate generation of the interface to the client side and then supply the "action" interface via AJAX. It may be interesting to approach this as a "bridge" where we begin to layer dynamic AJAX functionality more aggressively onto the existing widgets.
...
(this section needs to be checked and possibly split into more accurate sections)
...
Links in screenlets.
- Have less (or even no) buttons in header
- It was also suggested to use screenlets like gmail does. Notably
- Three buttons max
- Dropdown for other actions
- The idea of duplicating at bottom
- Having breadcrumbs under the title bar
- Using portlets in place of screenlets
- Recently (12/08) it was discussed if we should remove the screenlet's navigation-form-name attribute. There are (at least) 3 reasons for that
- Less information/features than with default (pages numbers, ability to jump to any page)
- The last button does not always work (try with widget.form.defaultViewSize=2 when listing invoices)
- Pagination should be available to the user always in the same way in order to have a consistent UI.
Then we have 2 possibilities- Remove this attribute and all current uses.
- Keep it but then
- we should at least make it works (last button issue)
- make it consistent with the standard way (direct page access)
...