Re: [xwiki-devs] [GSoc] XDroid Platform

Hi, *1: User Config Saving* * * Xwiki android can now save user login data. I refered http://platform.xwiki.org/xwiki/bin/view/AdminGuide/AccessWiki. Currently assuming the authority part(platform.xwiki.org<http://platform.xwiki.org/xwiki/bin/view/AdminGu… only as a unique wiki identifier. But in the org.xwiki.android.entity.User I have the method setXWikiRealm(String url);: Here I have intended the meaning realm as the url root path for a unique wiki instance. i.e. it should identify a wiki using path upto http://host/xwiki/wiki/wikialias/ But that functionality is not implemented.I just mailed this asking for the opinion wether the usage of word realm was right here. Also do you have seperate users for wikis for path based wiki access.Or are they the same with the main wiki *http://<host>/xwiki*. *2: Entity model* * * About the convention for using C_ prefix for core entity tables. I was referring to make the android versions of these entities http://platform.xwiki.org/xwiki/bin/view/DevGuide/DatabaseSchema and start there db prefixes with C_ This is because other apps may need to store some specific tables needed for them. Rather than having a seperate DB schema for them we can put those tables here as well prefixing them with <appname>_ . I added more entities like User as well to the core entities(table C_User).Also will implement a Log Entity(C_Log table) for logging some important application activities(such as login attempts) But the Log may be a little additional weight to the space and performance.I may implement a generic DBCleaning service to clean the tables like Log, if I have time. (Perhaps this description will resolve the confusion about the DB conventions. Sorry I was not very clear in that earlier mail. ;-).) I am sorry to say I am somewhat confused with all those entities in http://platform.xwiki.org/xwiki/bin/view/DevGuide/DatabaseSchema. Any way to reduce my confusion I refered 1) XWiki Data Model<http://platform.xwiki.org/xwiki/bin/view/DevGuide/DataModel> : can you give me a link to a documentation that explains the workflow of how a normal request is converted in to the requested page by the bin View action . So I can get a better understanding of how classes , objects are used. 2) package com.xpn.xwiki.api: I don't need to consider this, do I? 3) Cache<http://extensions.xwiki.org/xwiki/bin/view/Extension/Cache+Module&… : Need not implement similar component. Android OS does it nicely for the REST responses but still don't have a clear picture on this. To save a blog doc option 1)Seems like I have to convert a document entity to relevent xwiki-model-simplexml entities and send to server. option 2) We also can edit the relevent simplexml model object fields directly. (Looks a bad option to me.It does not hide the complexity of lower levels for the client layer.Anyway my work load is reduced with opt:2 ;-)) *3: Development/architectural approach Change* * * I was first thinking for a addon like architecture for the XWiki android app. We have the client.Main app (with all platfrom libs included) and Blog app as a seperate apk. But here Blog app will need to have the platform lib also. That would be a complete waste of space. But dynamically extending the app is lot easier. The client.Main app can add the activities defined in other apks in to its launcher interface using android PackageManager class. http://stackoverflow.com/questions/9236803/android-build-an-application-tha… But with this approach rises additional complexities. For example naming conflicts in the Components library module when two apps have the same library with same activities defined. Sync issues etc etc.... So we will go with single .apk approach. When going with single .apk we dont need a content provider to share config/ preferences data. So sharing module is now not needed. The client applications now can directly access the Configuration.java class to get/put configuration entries. Also since I am having a User entity a configuration like defaultUser(currently the admin user , hard coded in login.xml layout file) will only be needed for the first use of the app. Otherwise users need not configure a default user as the application now suggests the user names and automatically fill the rest. *4: Plan for this week* * * Make a launch pad .We can launch XWiki Navigator, blog etc from this. The launch pad is shown when we launch XWiki main client. Consider adding the WYSIWYG to my blog. It will be useless without the ability to convert text formatting to xwiki syntax.So I may just integrate it and ignore the uselessness for now. We currently don't have any config to save( Other than default user) config. I will add some demo config data and have a developer tools app added to the above mentioned XWiki launch pad that can view/edit the config file. That will complete milestone 1. But it is not the Sharing module(intended to share data with other .apks).That is the configuration component does not have a ContentProvider to share config data with other apks. Also I will define a seperate class to have preferences which will be edited by users. Config files are for configuration stuff and will be edited by developers. Users have preferences files(natively supported by android) to change app preferences. For example users will add the default login username as a preference.(This will invalidate the use of default User entry in the config file which is used until the user edits his preferences) Beg your pardon if the mail is too lengthy.;-) Thank you. Best Regards. Sasinda Rukshan. Best Regards. On Wed, May 30, 2012 at 1:11 PM, Thomas Mortagne &lt;thomas.mortagne(a)xwiki.com&gt;wrote;wrote: