Page History

...

1. 1. Jira
      server Magnolia - Issue tracker key MGNLUI-2656

   2. DetailSubApps as well as Dialogs depend on JCR but not tightly - once the previous steps are completed it should be possible to completely get rid of JCR dependency without even extracting the child classes.
   3. The similar data management tasks that we have in BrowserSubApp occur in DetailSubApp: we need to serialize/de-serialize item ids to fragments, query items by item id etc.
      
      1. A reasonable solution would be to share a capable component between sub-apps. 
      2. As long as content apps work over same domain - we could introduce the DataSourceManager component shared between sub-apps. It would encapsulate the solution of most of Level1/Level3 problems and could be useful for all other components that would need to connect to data of the app.

      3. DataSourceManager initial interface could look as follows for starters. 

         Code Block
         language java title DataSourceManager interface
         public interface DataSourceManager { String serializeItemId(Object itemId); Object deserializeItemId(String strPath); Item getItemById(Object itemId); Object getItemId(Item item); boolean itemExists(Object itemId); }

         
          
         

Level 4: Redefine ContentPresenter apis

...