opencirclesolutions / dynamo Goto Github PK

Currently, we only support the BigDecimal data type for dealing with decimal numbers. It would be nice to also have support for floats and doubles.

We currently allow the programmer to modify the button bar that is displayed below the search results table (e.g. SimpleSearchLayout, or any SplitLayout), but not the button bar that contains the save/edit/cancel buttons that is part of the actual edit form. I'd like to have the option to post-process this button bar as well.

The composite layout components currently only support a single sort order. It should be possible to pass multiple sort orders to these components. This affects SimpleSearchLayout, and all SplitLayouts.

Instead of 1 annotation (com.ocs.dynamo.domain.model.annotation.Attribute) with all kind of properties that are not all related to each other, create annotations to group the properties.
For example DateAttribute and NumberAttribute

The table to Excel export functionality (TableExportActionHandler) contains a piece of inefficient code that must be fixed: when iterating over the properties, they are retrieved from the table individually. It is much faster to retrieve the Item once and then get the properties from the item.

Already fixed for BL but must be merged into this code.

The pom for the dynamo-spring project currently contains Apache Camel dependencies. These really have no place in the dynamo-spring project. I propose creating a new subproject for Camel-related functionality and move all Camel-related stuff from dynamo-spring to dynamo-camel.

Default strategy (from Vaadin) for displaying the displayName is to uppercase each word, for example:
member: minimumAge
default behaviour: Minimum Age

Create a strategy to set this to another default, for example to create: Minimum age

Minor request: the CollectionTable component that is used to edit a property annotated with @ElementCollection currently only support String and Integer data types. At the very least we must add support for the Long data type

The validation messages are missing in the archetype and show case.

In short: Travis CI and Sonar.

Add the option to SimpleSearchLayout to defer the first search until the user actually presses the search button

Make the Dynamo project available as a BOM (Bill Of Materials).
This way it is easier to develop a new project using the Dynamo framework without the hassle of finding out all the right dependency versions and plugins (for example Vaadin and querydsl-apt plugin)

Reorganize the code base in multiple modules.

Currently, we only support JPA/relational databases as storage. We should add support for alternate storage types (exactly which types this will be is still open for discussion)

There are two package trees, nl.ocs and com.ocs. Remove nl.ocs.

Make both artefacts part of the standard build.

Add functionality for displaying charts using 3djs

Please add a separate setting to the Attribute Model that can be used to set the display name of an attribute when displayed in a table header.

If no value is provided for this setting, the framework should fall back to the default "displayName"

Add sensible plugins to the Maven build for QA.

To make it more easier to set different properties, use a Builder pattern.
new FormOptions.setXXX(..).setYYY(..)

The PivotContainer contains a piece of inefficient code with regard to creating the pivot items: typically the container will try to create the same item many times, only for each pivoted item. This can be improved by using a cache

Take care not to cache all rows though (just a recently used subset) otherwise the memory usage will go through the roof for large data sets

Add functionality for advanced filtering (click complex filters together using the UI)

Add documentation in Word or PDF format.

The ProgressForm currently uses a fairly ugly mechanism that requires the user to pass along and update an atomic integer. This can easily be improved by using an observer-like constructions (have the progress form implement an interface, pass this interface along to the batch process, call the "increment" method on the interface)

Add system/application wide defaults for the following attributes:

• TrueRepresentation
• FalseRepresentation
• searchCaseSensitive
• searchPrefixOnly

When generating a form, Dynamo now generates a text field for editing a property of type Integer (or Long).

I would propose adding functionality that makes it possible to configure that a spinner field should be used instead

The currently ServiceLocator is tied directly to Spring. We need to create an abstraction here so that a ServiceLocator can be created regardless of whether Spring or JEEE is used.

We currently only provide support for a horizontal menu. We need to extend this so that it is also possible to include a vertical menu (e.g. one that can be placed on the left side of a screen)

To new maven project structure:

• dynamo-common - utility and other reusable classes
• dynamo-api - Only interfaces for the (entity) model, DAO api, NO JPA dependencies, including the common (entity model implementations)
• dynamo-dao-jpa - The JPA dao implementation
• dynamo-service - Both API and default service implementations
• dynamo-ui-vaadin - Common Vaadin UI components without JPA dependencies
• dynamo-ui-vaadin-jpa - The JPA Vaadin Entity model factory implementation
• dynamo-camel - All common camel integration components
• dyname-jee - JEE specific configuration
• dynamo-spring - Spring specific configuration

Update the archetype with:

• css from showcase
• exception logging (issue 5)
• use bom for dependencies and plugins (feature 55)
• runnable with jetty:run

Concluded on 8-11-2016 with @wittekip and @pdeenen;

• Favor a clean framework internally without any Spring dependencies
• May very well operate in a Spring container.
• As Spring contributes a big part to dynamo this will not have a high priority.

A field annotated with dateType = AttributeDateType.TIMESTAMP will by default show a calendar but only the date is displayed in the inputfield.
Workaround: give annotated field the displayFormat = "dd-MM-yy HH:mm:ss"

This feature comprises of two parts:

• Provide a uniform way of accessing system properties - right now, access to system properties is done in several ways by simply using System.getProperty or System.getInt. I propose adding a utility that provides static methods for accessing system properties
  • Make certain parameters configurable, e.g. default number of rows in list select

Copy the in-house Open Circle Solutions version to GitHub

For now only java.util.Date is supported, add support for java.time types

See JPA 2.1 overview
It wil simplify fetch queries in Dynamo.

Add the option to specify that only certain file extensions can be uploaded using the UploadForm component.

The showcase application and application create with the archetype are both giving WARN messages about missing log4j appenders

The checkstyle and eclipse formatter configuration enforces 4 whitespaces to be used. This needs to be tabs.

Submodules for:

• UI
• Domain
• Core

Currently, there is no option to mark a field in a search screen as required. This would be useful to have (in combination with Feature 46) in order to deal with very large data sets

Allow the domain object to expire or a activate on a certain date.

This is not implemented in the TabularEditLayout. This prevents the Show Case to compile. The following code is added:

protected void detailsMode(T entity) { // TODO Make the Show Case Compile. }