[ 
https://issues.apache.org/jira/browse/PHOTARK-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Subash Chaturanga updated PHOTARK-66:
-------------------------------------

    Attachment: changedJCRStructure.patch

In this patch I have changed all methods of JCRGalleryImpl and JCRAlbumImpl amd 
changed the AlbumAggregator class  so that they adhere to the new album 
structure where we insert albums of local and remote separately. For instance 
/local/..all local child albums and /remote/flicker/..  and /remote/picasa/...  
. Actually in this case I have put a comment on all methods I have changed 
saying "Adhered to new structure" . Because I didn't remove any existing 
method. I just added overloaded method for each  JCRGalleryImpl and 
JCRAlbumImpl class. So that when any one try the patch it wont give any build 
failures as the UI already calling to previous model.

> Improve the album storage structure in photark (trunk) local jcr
> ----------------------------------------------------------------
>
>                 Key: PHOTARK-66
>                 URL: https://issues.apache.org/jira/browse/PHOTARK-66
>             Project: PhotArk
>          Issue Type: Improvement
>         Environment: Linux
>            Reporter: Subash Chaturanga
>         Attachments: changedJCRStructure.patch
>
>   Original Estimate: 96h
>  Remaining Estimate: 96h
>
> Currently in photark trunk, all albums are directly put under the root of 
> local jcr regardless of the album type. Currently photark has basically two 
> main album types, local and remote (flicker and picasa). So If the local jcr 
> structure is much more organized in trunk such that it stores each album type 
> under the relevant category. Hence  in future when some more other album 
> types introduces it won't be too complex in the jcr level also. And it is 
> efficient and fast, when we do jcr operations where we don't need to go 
> through the whole album list each time, when we want to acquire all albums of 
> one particular type.   

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to