Hi Ludovic,
Last few days I focused with the integrating childbrowser to Android
project function. As I mentioned earlier there was a problem of
missing classes in the Cordova version being used(Cordova 2.7.0) with
the childbrowser plugin. Therefore I compared both Cordova 2.3.0 and
Cordova 2.7.0 jar files and successfully created a new jar which now
can address the requirements of our Android project and can also work
with Child Browser. This can be edited to suit our requirements.
Then I integrated the childbrowser plugin to Android app. And to test
the integration, I used it at "Wiki" page to load that. (The screen
after clicking on a wiki name on the xiki list of the first screen).
For that I changed as below line in the xwiki-screen.js's mainScreen
screen object.
items += "<li><a class='x-icon x-icon-cloud'
href='#xwikihome/" +
wikiConfig.id + "' id='jqmlink'
onClick=\'cb.showWebPage(\"#xemhome/"
+ wikiConfig.id + "\")\'>" + wikiConfig.name +
"</a></li>";
Then I could add the plugin successfully and open it. But since we
have used relative paths('#xwikihome/" + wikiConfig.id +"') to load
this page in our application, apparently it is doesn't display the
"Wiki" page when calling through childbrowser. I know that is not the
place to call the childbrowser and I used it only to test the plugin.
But I dug into the code for find out where exactly the code calls the
page browser (xwiki-pagebrowser.js) is being called for iOS but could
not find where. Therefore I am confused with where I should exactly
call childbrowser plugin. Can you please tell for which screens it
should childbrowser be called and where it is being called in the code
so that I can call the child browser for Android at the same places.
Thank you.
On Thu, Jul 18, 2013 at 2:48 PM, Ludovic Dubost <ludovic(a)xwiki.com> wrote:
Hi Buddhi,
2013/7/18 Buddhiprabha Erabadda <buddhiprabha31481(a)gmail.com>
Hi Sergui, Hi all,
I have been working on the project past weeks and particularly on two
tasks.
One is making the application work on old Android versions. The
application
only works in new Android versions(3.0 and up)
and it does not wok with
versions of Android which have highest market share. I wrote to App
Framework community regarding this and it was confirmed that the problem
lies in our side as the framework supports both new and old versions.
After
analysing the code and doing some changes in the
code, I got the initial
screen working, but still the hyperlinks are not working. I carried out
many changes and tested but still it fails in old Android versions.
I think you
might be spending a bit too much time on this. If you can
publish the changes you made I can have a look at it and see if I can find
a solution.
Otherwise we can just drop Android 2.x support as anyway these devices will
go out of usage quite fast.
The other task is making ChildBrowser plugin work
in the application.
This
plugin[1] is no longer supported with Cordova
2.7[2] as mentioned by the
developers. But in our application ChildBrowser is used for iOS with high
customizations. For this plugin to work in Android, ChildBrowser.java
should be used with childbrowser.js and a class named(in
org.apache.cordova.api package) Plugin is used by the java file. This
class
file is not longer present in Cordova 2.7 as they
have discontinued the
support for the plugin. If the plugin is to be used, Cordova 2.3 should
be
used, but the application depends on a class file
which is present only
on
Cordova 2.7. Therefore it is not possible to add
ChildBrowser plugin for
Android. I've been looking into this issue but there is not workaround so
far. After discontinuing the support Cordova has integrated the same
functionality with InAppBrowser API. As I understand, if this is to be
used, the code implemented for iOS need to be changed as well, is that
so?
On this, I don't think it's too much a problem. What should be done is use
the ChildBrowser and inAppBrowser code as examples to write our own plugin.
Our use case is not fully supported by the standard code in inAppBrowser so
anyway we cannot use this and it is not meant to be modified.
So the solution is to do the same thing that was done for iOS, which is:
- writing a custom plugin using these existing plugins as examples
- the plugin for Android should use the same JS api as the plugin we wrote
for iOS
The specificities of the plugin are, compared to the existing plugins:
- no button bar
- custom code to resize the browser component when the UI of the XWiki
Mobile app requires it
- custom JS callbacks to the application when links are clicked in the HTML
So you should stop looking for using a standard component and start writing
the custom one compatible with the API I did for iOS
As for the issue of the class file not present in Cordova 2.7 but that was
in Cordova 2.3, it should be possible to add it back using your own naming
or you need to find a way to workaround it.
Ludovic
I would like to know suggestions of the community
regarding these.
Thank you.
[1]
https://github.com/phonegap/phonegap-plugins/tree/master/Android/ChildBrows…
[2]
http://community.phonegap.com/nitobi/topics/_childbrowser_plugin_deprecatin…
On Wed, Jul 17, 2013 at 6:57 PM, Sergiu Dumitriu <sergiu(a)xwiki.org>
wrote:
Hi Buddhi,
How is the project going? There seems to have been no activity in the
past
> 3 weeks. It would be nice if you could give a status update on the
list,
commit
the code you've worked on so far, and provide a demo for the
community to try out. The midterm evaluation is in about two weeks, and
we
> need to see some progress by then.
>
> Also, as Vincent announced on the list [1, 2], there's a Hackathon
going
on
> starting today for the next week or so, and as a member of the
community
we'd
really appreciate your participation.
[1]
http://markmail.org/message/3nra7ug7ynxx7qc5
[2]
http://dev.xwiki.org/xwiki/bin/Hackathon2013/
On Wed, May 29, 2013 at 4:00 AM, Ludovic Dubost <ludovic(a)xwiki.com>
wrote:
>
>> Hi Buddhi,
>>
>> Let's start the good work now.
>>
>> I'm in the process of preparing publishing the first version of the
iOS
>
mobile application on the current status (without the notifications
feature
> which is complicated and requires infrastructure). This might be a
medium
>> long process as we need to go through the AppStore review process.
>>
>> The first priority is to get the Android version ready for releasing
> which
>> means implementing the equivalent of the Native Page Browser (that I
>> implemented for iPhone) on Android. This is used to display the HTML
>> content of a web page inside a child browser. The objective here is
to
>> allow to have a nice scalable HTML view
on the content and also for
>> attached files instead of having an iframe with which we cannot do
>> everything we want. You should look at the iPhone code and we should
>> discuss. Currently Android is using the iframepagebrowser.js file
which
>> iPhone is using the native page browser.
>>
>> But as we should start not too complicated we should start with
>> attachments/comments display which you also mentioned in your
proposal.
> On
>> this you will need this pull request on the XWiki Core which adds
> features
>> to the REST api (allowing to get all page data in one request):
>>
https://github.com/xwiki/xwiki-platform/pull/111
>> This is a good task for you to get to know the code base. You should
>> compile this pull request on your localhost and setup an XWiki 5.0
with
>> multiple wikis (you need the XWiki
Workspaces extension installed)
with
> the
>> pull request patch. For this make a standard install of 5.0 first.
Then
>> checkout the core code on the
stable-5.0.x branch and apply the pull
>> request, and recompile the three rest module. You can then deploy
them
in
> WEB-INF/lib. Once you have a patched version
running we could start
with
> implementing:
>
> - the look and feel of the attachment buttons from Caty's design
proposal
> - implement a comment view
> - implement attachment and comment view for servers not having this
pull
>> request (this requires additional REST queries to get the list of
>> attachments and comments)
>>
>> On a general matter, I'm particularly counting a lot on you on being
my
>> Android counterpart for device specific
implementation. But that
should
not
> be all. The notifications feature is one of the big priorities but it
has
>> quite some complexities which we will need to discuss.
>>
>> Finally we should have all communications using the developers list
as
for
chat
> (and not Skype -> you can ping me on Skype to tell me you have
> questions for me on IRC as I don't follow too much there).
>
> Welcome to XWiki
>
> Ludovic
>
>
>
> 2013/5/28 Buddhiprabha Erabadda <buddhiprabha31481(a)gmail.com>
>
>> Hi,
>>
>> Thank you all. :)
>>
>> I am happy about being selected for GSoC 2013 to work with XWiki. I
am
>> thankful to Ludovic and XWiki community
for guidance regarding the
> project
>> during the proposal period. I will carry out development for the
mobile
>> client and will develop Android device
specific parts of the client
as
>> well.
>>
>> I am ready to start working with the project and I hope to
successfully
>> complete the project. I am looking
forward to next steps.
>>
>> Thank you.
>>
>> On Tue, May 28, 2013 at 2:23 PM, Asiri Rathnayake <
>> asiri.rathnayake(a)gmail.com> wrote:
>>
>>> Congrats!! :)
>>>
>>>
>>> On Tue, May 28, 2013 at 9:49 AM, Vincent Massol <
vincent(a)massol.net>
>>> wrote:
>>>
>>>> Cool!
>>>>
>>>> Let's make this a success :)
>>>>
>>>> Thanks
>>>> -Vincent
>>>>
>>>> On May 28, 2013, at 8:19 AM, Ludovic Dubost <ludovic(a)xwiki.com
> wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> I'd like to welcome Buddhiprabha Erabadda to our community on
the
>> GSOC
>>>>> Mobile Client project, which I will mentor. Buddhiprabha
Erabadda
> is
>>> our
>>>>> only GSOC student this year as we were not enough satisfied
with
> the
>>>>> quality of the other proposals. No pressure Buddhiprabha.
>>>>>
>>>>> The objective of Buddhiprabha will be to help me getting the
best
>>>>> possible
>>>>>> XWiki Mobile out the door on Android and iOS, with
particularly
>>>>>> notifications
implemented. We will also work with Caty on her
>>> proposals
>>>>> for
>>>>>> the mobile app:
>
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/MobileApp
>>>>>>
>>>>>> We will also add improvements to the XWiki REST Api during
the
>>
project
>>>>> especially to improve performance. There is already a pull
request
> to
>>> get
>>>>> more page data in one request (
>>>>>
https://github.com/xwiki/xwiki-platform/pull/111 )
>>>>>
>>>>> We have a jira project to track tasks:
>>>>
http://jira.xwiki.org/browse/XMMORPHO
>>>>>
>>>>> Welcome Buddhiprabha to XWiki
>>>>>
>>>>> Ludovic
>>>>
>>>> _______________________________________________
>>>> devs mailing list
>>>> devs(a)xwiki.org
>>>>
http://lists.xwiki.org/mailman/listinfo/devs
>>> _______________________________________________
>>> devs mailing list
>>> devs(a)xwiki.org
>>>
http://lists.xwiki.org/mailman/listinfo/devs
>>
>>
>>
>> --
>> *Buddhiprabha Erabadda*
>> *Department of Computer Science and Engineering*
>> *University of Moratuwa*
>> _______________________________________________
>> devs mailing list
>> devs(a)xwiki.org
>>
http://lists.xwiki.org/mailman/listinfo/devs
>
>
>
> --
> Ludovic Dubost
> Founder and CEO
> Blog:
http://blog.ludovic.org/
> XWiki:
http://www.xwiki.com
> Skype: ldubost GTalk: ldubost
> _______________________________________________
> devs mailing list
> devs(a)xwiki.org
>
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
*Buddhiprabha Erabadda*
*Department of Computer Science and Engineering*
*University of Moratuwa*
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Ludovic Dubost
Founder and CEO
Blog:
http://blog.ludovic.org/
XWiki:
http://www.xwiki.com
Skype: ldubost GTalk: ldubost
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
*Buddhiprabha Erabadda*
*Department of Computer Science and Engineering*
*University of Moratuwa*
_______________________________________________
devs mailing list
devs(a)xwiki.org