. I can use one of these
for persistence module.
Its easy for me to use direct SQLlite for my purpose. But for platform We
can use one of these and annotate our models so we can easily persist
them.(OK.This is if I hv time when I finish rich text editor)
On Wed, Apr 4, 2012 at 8:49 PM, sasinda rukshan <sasindarukshan(a)gmail.com
Hi Thomas,
Sorry I could not respond to you earlier.I was traveling.
Thank you for the suggestion.In stack overflow it was said that you have
to checkout an old revision in the repository and the latest version was
now not available.(The new one is deleted somehow. On purpose, maybe).I
will check it tomorrow.
I will make the proposal saying I will do the blog application and the
architecture proposed above is just for structuring my work and to show
what the *potential* is (specially to the Google) If Google does not
select this project to be a good suggestion out of the slots they are
offering for XWiki, I have a risk, so I will leave the proposed
architecture and highlight the fact that this is just to show how the
project will be directed in the future. I am not smart to implement all
those platform modules in the give period.Some I don't have enough
knowledge. But I had a brief idea on how to implement them.Like for example
Cache module can be implemented using the last modified time stamp of the
Object data(not HTML response's last modified date, as it sure is generated
from a servlet) inside the HTML response that the RESTful APIs return.
Now the issue is by doing a WYSYWIG editor I will mainly contributing a
reusable UI element to XWiki Mobile Platform. As it looks like this will
take some time. So it goes a little out of you vision for a XWiki mobile
platform(i.e. I am going deep in to one direction in the platform instead
of scratching the breadth of it).
A) So my main contribution would be WYSYWIG and Android account content
shareing ( I am thinking of using Android ContentProviders,from what I
read, that's what Android platform is using to share its settings etc.).
B) I like to do
Persisting the blog document for later editing. (persistency parts
I would add to the Persistence module.Its a Facade.Hmm... If there was JPA
in android...)
Remember password.Store it in the device (encrypted.Use SKE. Key
would be also stored in the device anyway.).
From my experience some tricky program parts take time way more than I
expect. So maybe I may not have enough time to do (B).
What is your suggestion. I like to do the WYSYWIG. If I am to do it I
will need to store the styles using HTML and inline CSS. It can be done
while editing the doc or by at the end transforming Android native
formating to HTML .(1 st option is easy but not optimal at memory
usage.Since people see the functionality not our optimization's I vote for
1).
If you are voting for a WYSIWYG I'll create mock ups and add to the
proposal.
To tell about the architecture, Domain Model Module:
Almost all of the model parts are done in the Google Android
Connector.So I have nothing much to do there.
Can you suggest what is doable within time frame? Is it OK to propose
those features even I am not sure whether I will have enough time?
*As I am on study leave from Friday (I am skipping the university
tomorrow ;-)), Shall I make a document to explain what the Android XWiki
mobile main app suggestion is about. (One main app to hold every thing). I
am not going to make it. I don't have enough experience to make a program
with pluggable architecture in Android.Maybe some other developers
interested may look at it. Will it be relevant to link it in melangae.*
Is Google looking at other projects we have done? Or is it just for
you.If it is needed I can upload code of my past projects.( not much,
Servlet based web apps, Battle Tanks game with AI, JGame lib was used).
Regards,
Sasinda.
On Wed, Apr 4, 2012 at 2:36 PM, Thomas Mortagne <
thomas.mortagne(a)xwiki.com> wrote:
On Wed, Apr 4, 2012 at 10:32 AM, sasinda rukshan
<sasindarukshan(a)gmail.com> wrote:
> Dear* Thomas,*
> I think it will take the same time with android. No difference. I am
also
> thinking that it is easy to propose but hard to make. I will lower
the set
> of requirements to a doable set. I will almost complete the proposal
by
> today night.
Well probably a bit less time since you don't have do deal with
browser differences like the XWiki WYSIWYG does but still a big work
if there is nothing to help doing this on Android.
I just found
http://code.google.com/p/droid-writer/ by searching a bit
on Google, maybe that would help you.
> Thanks for frequently checking out.
My pleasure ;)
>
> Regards,
>
> Sasinda Rukshan,
> _______________________________________________
> devs mailing list
> devs(a)xwiki.org
>
http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs