Eric Dalquist wrote:
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?
Yes, definitely.
As usual, there are some near-term due dates looming that will
(probably) constrain us not to undertake everything we might like to do.
But it's still a great opportunity to get on the same page about where
this is going so we can (1) do everything that can be done for the plan
and (2) make sure we don't make decisions that it more difficult.
drew
-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
--
Andrew Wills
UNICON, Inc.
Office: (480) 558-2476
http://cernunnos.googlecode.com/
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/uportal-dev
