Content
View differences
Updated by Jens Ulferts almost 10 years ago
The feature is useful for all users. In order to reduce complexity we should therefore integrate this into the core application. This also makes the translations much easier to maintain.
**Integration approach**
- Keep having a separate xls export library (we might want to join it with pdf export into an export library)
- Move the export library to the opf domain on GitHub
- Reference the export library in the Gemfile (not Gemfile.plugins)
- Move everything from the core that has to do with exporting into the library
- Call the library’s interface from the core at the appropriate places
- Remove the engine from the library and with it the registration as a plugin
- Write unit tests for the library that are independent from the core. This might force us to come up with a better api which is desirable in any case.
- If desired move the translations to the core
- Write integration tests in the core
**Integration approach**
- Keep having a separate xls export library (we might want to join it with pdf export into an export library)
- Move the export library to the opf domain on GitHub
- Reference the export library in the Gemfile (not Gemfile.plugins)
- Move everything from the core that has to do with exporting into the library
- Call the library’s interface from the core at the appropriate places
- Remove the engine from the library and with it the registration as a plugin
- Write unit tests for the library that are independent from the core. This might force us to come up with a better api which is desirable in any case.
- If desired move the translations to the core
- Write integration tests in the core