This sounds like a good approach and set of changes. On the issue of adding import/export APIs to the user layout store, one of the longer term roadmap tasks is to work on refactoring our legacy DAO classes, depending on your timeline for the import/export work we could talk about the general layout store work that is needed?

-Eric

Drew Wills wrote:
Hey folks,

I just completed an writeup and analysis of some proposed changes to layout Import/Export. Please take a look and share some insights: http://www.ja-sig.org/wiki/x/vwCPAQ

I believe these changes would address the following 5 issues in JIRA (as well as some that aren't in JIRA):

- UP-2358: Export and Import scripts do not fully support all DLM layout functions
  - UP-2255:  Import scripts don't deal with dlm-delete in layout files
- UP-2247: Users with rows in UP_LAYOUT_STRUCT with type="dlm:*" and name="width" or name="name" don't export their layouts - UP-2188: Make layout import/export smart enough to handle arbitrary layers of nesting (e.g. subtabs)
  - UP-2174:  Support multiple user profiles in import/export tool

drew

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to