28 Nov
2012
28 Nov
'12
11:56 a.m.
Hi devs,
For the Mobile App Investigation, Ludovic has been playing with a XWiki
Mobile App prototype done with jQuery Mobile (http://jquerymobile.com/).
This is a proposal for a mobile application that matches the jQuery Mobile
framework capabilities and that provides minimal XWiki functionality (like
listing wikis, spaces, pages, accessing content, viewing recent activity,
etc.)
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/MobileApp
Thanks,
Caty
28 Nov
28 Nov
2:52 p.m.
Hi Cati,
Great proposals that enhances the current UI. My main comments concern
features that are not really finished in the current prototype and would
need some help also from a design/usability perspective:
1/ Adding a page to favorites and notifications
-> This has not been put in the UI and would be needed
-> Should it be a separate favorites than the XWiki Watch List. Right now
I don't think so because that would be yet another list and the Server wiki
will need to know about the favorites because it
-> A design for notifications and how they should show up would be great.
I think notifications could be a general UI item and also show up on the
home page. A notification is sent by the server to the device. The
notification is just a message. The XWiki Application can be activated from
the notification but will have to contact the server to know more (I'm not
sure if you get access to the notifications that the user clicked to
activate the App). I think a message could be just "this doc has been
updated" or "X documents have been modified" depending on the
notifications
settings of the user).
2/ Adding a page/space/applications to offline documents would be needed in
the UI and a management UI for the page/spaces/applications being in the
offline docs
3/ The offline editing features should be removed for now because they are
far from ready
4/ Commenting should be added in the UI
5/ A "share/open" button should be added which opens a popup proposing to
share by email/twitter/open in safari/etc..
6/ A configuration UI would be needed to add/update configuration for a new
Wiki. For now a simple URL would be enough + a username and password and an
"advanced" button. A specific service will probably be built in XE/XEM to
provide the configuration to the mobile App. It would be possible using
the "advanced configuration" to not need this server based configuration to
connect to any wiki but it will be more pratical with this configuration.
7/ I like the Application zone design. Now it should be reusing what is
done in the Application Panel since 4.2 (?). Now the issue is that a
specific REST/XWiki Page service might be needed here, as right now it's
manual configuration. Now the service used for the configuration could
handle that.
Ludovic
2012/11/28 Ecaterina Moraru (Valica) <valicac(a)gmail.com>
Hi devs,
For the Mobile App Investigation, Ludovic has been playing with a XWiki
Mobile App prototype done with jQuery Mobile (http://jquerymobile.com/).
This is a proposal for a mobile application that matches the jQuery Mobile
framework capabilities and that provides minimal XWiki functionality (like
listing wikis, spaces, pages, accessing content, viewing recent activity,
etc.)
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/MobileApp
Thanks,
Caty
_______________________________________________
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
4:27 p.m.
Hi Ludovic, Caty,
This is interesting.
Ludovic if you already started working on this, maybe you could send a
mail with more details and why not start a design document ? I think
there are several aspects of design (software design) that would be
interesting to be discussed.
Since you are working with jQueryUI, I imagine and will assume in the
rest of this mail that you are or plan on using a wrapper such as Apache
Cordova (PhoneGap) to package the app for mobile platforms. Couple of
random questions/remarks :
- Do you handle authentication with cookies ? I have started working on
a token-based authenticator with revokable tokens (with mobile clients
in mind as well).
- About notifications, I am not sure what you mean by "I'm not sure if
you get access to the notifications that the user clicked to activate
the App", but with Cordova there's an event that let's you know when an
app resumes (comes back from background). Maybe at that moment you can
check if you have new notifs.
- Also about notifications, the default strategy should be
pulled-notifications. Then it could be extended to an environment based
strategy that uses a long lived connection when the phone/device is
plugged (and maybe when it is connected on WiFi, not on mobile networks).
- Finally, a project to keep an eye on : http://maker.github.com/ratchet/
Jerome
On 11/28/2012 02:52 PM, Ludovic Dubost wrote:
Hi Cati,
Great proposals that enhances the current UI. My main comments concern
features that are not really finished in the current prototype and would
need some help also from a design/usability perspective:
1/ Adding a page to favorites and notifications
-> This has not been put in the UI and would be needed
-> Should it be a separate favorites than the XWiki Watch List. Right now
I don't think so because that would be yet another list and the Server wiki
will need to know about the favorites because it
-> A design for notifications and how they should show up would be great.
I think notifications could be a general UI item and also show up on the
home page. A notification is sent by the server to the device. The
notification is just a message. The XWiki Application can be activated from
the notification but will have to contact the server to know more (I'm not
sure if you get access to the notifications that the user clicked to
activate the App). I think a message could be just "this doc has been
updated" or "X documents have been modified" depending on the
notifications
settings of the user).
2/ Adding a page/space/applications to offline documents would be needed in
the UI and a management UI for the page/spaces/applications being in the
offline docs
3/ The offline editing features should be removed for now because they are
far from ready
4/ Commenting should be added in the UI
5/ A "share/open" button should be added which opens a popup proposing to
share by email/twitter/open in safari/etc..
6/ A configuration UI would be needed to add/update configuration for a new
Wiki. For now a simple URL would be enough + a username and password and an
"advanced" button. A specific service will probably be built in XE/XEM to
provide the configuration to the mobile App. It would be possible using
the "advanced configuration" to not need this server based configuration to
connect to any wiki but it will be more pratical with this configuration.
7/ I like the Application zone design. Now it should be reusing what is
done in the Application Panel since 4.2 (?). Now the issue is that a
specific REST/XWiki Page service might be needed here, as right now it's
manual configuration. Now the service used for the configuration could
handle that.
Ludovic
2012/11/28 Ecaterina Moraru (Valica) <valicac(a)gmail.com>
Hi devs,
For the Mobile App Investigation, Ludovic has been playing with a XWiki
Mobile App prototype done with jQuery Mobile (http://jquerymobile.com/).
This is a proposal for a mobile application that matches the jQuery Mobile
framework capabilities and that provides minimal XWiki functionality (like
listing wikis, spaces, pages, accessing content, viewing recent activity,
etc.)
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/MobileApp
Thanks,
Caty
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
8:31 p.m.
2012/11/28 Jerome Velociter <jerome(a)velociter.fr>
Hi Ludovic, Caty,
This is interesting.
Ludovic if you already started working on this, maybe you could send a
mail with more details and why not start a design document ? I think there
are several aspects of design (software design) that would be interesting
to be discussed.
Yes I'll try to do that when I find some time. I also plan to publish the
code but I still need to put the licence headers before I open the github
repository.
Since you are working with jQueryUI, I imagine and
will assume in the rest
of this mail that you are or plan on using a wrapper such as Apache Cordova
(PhoneGap) to package the app for mobile platforms.
The prototype is using PhoneGap/Cordova for the iPhone/iPad. It uses a
special plugin for Offline which I believe exists also for Android but I
haven't tested yet.
My development is also compatible with Titanium (Web) or MacGap allowing to
build a desktop application out of the code. This is also one of the target
of such a development.
Couple of random questions/remarks :
- Do you handle authentication with cookies ? I have started working on a
token-based authenticator with revokable tokens (with mobile clients in
mind as well).
Yes right now I use cookies. Indeed an OAUTH authentication would make
sense but require more work both server side and on the mobile side. I
would be great to have an OAUTH authentication.
- About notifications, I am not sure what you mean by
"I'm not sure if you
get access to the notifications that the user clicked to activate the App",
but with Cordova there's an event that let's you know when an app resumes
(comes back from background). Maybe at that moment you can check if you
have new notifs.
I haven't looked at this part yet but just tested Apple Notifications. See
below
- Also about notifications, the default strategy
should be
pulled-notifications. Then it could be extended to an environment based
strategy that uses a long lived connection when the phone/device is plugged
(and maybe when it is connected on WiFi, not on mobile networks).
I tried push notifications using on iPhone and iPad and the results were
interesting. I've used JavaPNS (http://code.google.com/p/javapns/) which
was quite simple to send a notification to an iOS device (except getting
the Apple Certificates). So I was more going with that. You inform the
XWiki Server which pages/spaces you want to track and the wiki will send
push notifications when there are changes on these documents. This is more
efficient than a pull based notification which requires the app to be
active.
- Finally, a project to keep an eye on :
http://maker.github.com/**
ratchet/ <http://maker.github.com/ratchet/>
Interesting, but I'm not sure I see the advantage of this versus directly
using JQuery Mobile
Ludovic
Jerome
On 11/28/2012 02:52 PM, Ludovic Dubost wrote:
--
Ludovic Dubost
Founder and CEO
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
Hi Cati,
Great proposals that enhances the current UI. My main comments concern
features that are not really finished in the current prototype and would
need some help also from a design/usability perspective:
1/ Adding a page to favorites and notifications
-> This has not been put in the UI and would be needed
-> Should it be a separate favorites than the XWiki Watch List. Right
now
I don't think so because that would be yet another list and the Server
wiki
will need to know about the favorites because it
-> A design for notifications and how they should show up would be
great.
I think notifications could be a general UI item and also show up on the
home page. A notification is sent by the server to the device. The
notification is just a message. The XWiki Application can be activated
from
the notification but will have to contact the server to know more (I'm not
sure if you get access to the notifications that the user clicked to
activate the App). I think a message could be just "this doc has been
updated" or "X documents have been modified" depending on the
notifications
settings of the user).
2/ Adding a page/space/applications to offline documents would be needed
in
the UI and a management UI for the page/spaces/applications being in the
offline docs
3/ The offline editing features should be removed for now because they are
far from ready
4/ Commenting should be added in the UI
5/ A "share/open" button should be added which opens a popup proposing to
share by email/twitter/open in safari/etc..
6/ A configuration UI would be needed to add/update configuration for a
new
Wiki. For now a simple URL would be enough + a username and password and
an
"advanced" button. A specific service will probably be built in XE/XEM to
provide the configuration to the mobile App. It would be possible using
the "advanced configuration" to not need this server based configuration
to
connect to any wiki but it will be more pratical with this configuration.
7/ I like the Application zone design. Now it should be reusing what is
done in the Application Panel since 4.2 (?). Now the issue is that a
specific REST/XWiki Page service might be needed here, as right now it's
manual configuration. Now the service used for the configuration could
handle that.
Ludovic
2012/11/28 Ecaterina Moraru (Valica) <valicac(a)gmail.com>
Hi devs,
______________________________**_________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/**mailman/listinfo/devs<http://lists.xwiki.org/ma…
--
For the Mobile App Investigation, Ludovic has been playing with a XWiki
Mobile App prototype done with jQuery Mobile (http://jquerymobile.com/).
This is a proposal for a mobile application that matches the jQuery
Mobile
framework capabilities and that provides minimal XWiki functionality
(like
listing wikis, spaces, pages, accessing content, viewing recent activity,
etc.)
http://incubator.myxwiki.org/**xwiki/bin/view/Improvements/**MobileApp<h…
Thanks,
Caty
______________________________**_________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/**mailman/listinfo/devs<http://lists.xwiki.org/ma…
10:36 p.m.
On 11/28/2012 08:31 PM, Ludovic Dubost wrote:
Is it the SQLite plugin ? If it is I think it has a slightly different
API than localStorage, which is SQLite for the web and that can be used
from Cordova, with limitations (max 5Mb and requires user explicit
permission). It's easy to write a common API for both so that if there
is no Android SQLite plugin one can use localStorage directly (or write
the Android plugin which shouldn't be very complex).
Yes that would be great. What I'm doing is not real OAuth either yet,
just revokable token based auth.
OK. I guess it works at the GSM network level, which is good for power
consumption vs AJAX from the app. That's proprietary to Apple though, so
we would need a more generic solution for other devices, which could be
HTTP pull against a REST end point.
Right. It has an advantage if you decide to not use jQuery mobile, and
go for a front-end MVC framework instead (like Backbone, angular.js
etc.), but indeed in your case jQuery is focused on UI components
already, so you don't need that.
Jerome
2012/11/28 Jerome Velociter
<jerome(a)velociter.fr>
Great
Hi Ludovic, Caty,
This is interesting.
Ludovic if you already started working on this, maybe you could send a
mail with more details and why not start a design document ? I think there
are several aspects of design (software design) that would be interesting
to be discussed.
Yes I'll try to do that when I find some time. I also plan to publish the
code but I still need to put the licence headers before I open the github
repository. Since you are working with jQueryUI, I imagine
and will assume in the rest
of this mail that you are or plan on using a wrapper such as Apache Cordova
(PhoneGap) to package the app for mobile platforms.
The prototype is using PhoneGap/Cordova for the iPhone/iPad. It uses a
special plugin for Offline which I believe exists also for Android but I
haven't tested yet. My development is also compatible with Titanium (Web)
or MacGap allowing to
build a desktop application out of the code. This is also one of the target
of such a development.
Cool
Couple of random questions/remarks :
- Do you handle authentication with cookies ? I have started working on a
token-based authenticator with revokable tokens (with mobile clients in
mind as well).
Yes right now I use cookies. Indeed an OAUTH authentication would make
sense but require more work both server side and on the mobile side. I
would be great to have an OAUTH authentication. - About notifications, I am not sure what you
mean by "I'm not sure if you
get access to the notifications that the user clicked to activate the App",
but with Cordova there's an event that let's you know when an app resumes
(comes back from background). Maybe at that moment you can check if you
have new notifs.
I haven't looked at this part yet but just tested Apple Notifications. See
below
- Also about notifications, the default strategy
should be
pulled-notifications. Then it could be extended to an environment based
strategy that uses a long lived connection when the phone/device is plugged
(and maybe when it is connected on WiFi, not on mobile networks).
I tried push notifications using on iPhone and iPad and the results were
interesting. I've used JavaPNS (http://code.google.com/p/javapns/) which
was quite simple to send a notification to an iOS device (except getting
the Apple Certificates). So I was more going with that. You inform the
XWiki Server which pages/spaces you want to track and the wiki will send
push notifications when there are changes on these documents. This is more
efficient than a pull based notification which requires the app to be
active. - Finally, a project to keep an eye on :
http://maker.github.com/**
ratchet/ <http://maker.github.com/ratchet/>
Interesting, but I'm not sure I see the advantage of this versus directly
using JQuery Mobile
Ludovic
Jerome
On 11/28/2012 02:52 PM, Ludovic Dubost wrote:
Hi Cati,
Great proposals that enhances the current UI. My main comments concern
features that are not really finished in the current prototype and would
need some help also from a design/usability perspective:
1/ Adding a page to favorites and notifications
-> This has not been put in the UI and would be needed
-> Should it be a separate favorites than the XWiki Watch List. Right
now
I don't think so because that would be yet another list and the Server
wiki
will need to know about the favorites because it
-> A design for notifications and how they should show up would be
great.
I think notifications could be a general UI item and also show up on the
home page. A notification is sent by the server to the device. The
notification is just a message. The XWiki Application can be activated
from
the notification but will have to contact the server to know more (I'm not
sure if you get access to the notifications that the user clicked to
activate the App). I think a message could be just "this doc has been
updated" or "X documents have been modified" depending on the
notifications
settings of the user).
2/ Adding a page/space/applications to offline documents would be needed
in
the UI and a management UI for the page/spaces/applications being in the
offline docs
3/ The offline editing features should be removed for now because they are
far from ready
4/ Commenting should be added in the UI
5/ A "share/open" button should be added which opens a popup proposing to
share by email/twitter/open in safari/etc..
6/ A configuration UI would be needed to add/update configuration for a
new
Wiki. For now a simple URL would be enough + a username and password and
an
"advanced" button. A specific service will probably be built in XE/XEM to
provide the configuration to the mobile App. It would be possible using
the "advanced configuration" to not need this server based configuration
to
connect to any wiki but it will be more pratical with this configuration.
7/ I like the Application zone design. Now it should be reusing what is
done in the Application Panel since 4.2 (?). Now the issue is that a
specific REST/XWiki Page service might be needed here, as right now it's
manual configuration. Now the service used for the configuration could
handle that.
Ludovic
2012/11/28 Ecaterina Moraru (Valica) <valicac(a)gmail.com>
Hi devs,
______________________________**_________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/**mailman/listinfo/devs<http://lists.xwiki.org/ma…
--
For the Mobile App Investigation, Ludovic has
been playing with a XWiki
Mobile App prototype done with jQuery Mobile (http://jquerymobile.com/).
This is a proposal for a mobile application that matches the jQuery
Mobile
framework capabilities and that provides minimal XWiki functionality
(like
listing wikis, spaces, pages, accessing content, viewing recent activity,
etc.)
http://incubator.myxwiki.org/**xwiki/bin/view/Improvements/**MobileApp<h…
Thanks,
Caty
______________________________**_________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/**mailman/listinfo/devs<http://lists.xwiki.org/ma…
5:25 p.m.
On Wed, Nov 28, 2012 at 3:52 PM, Ludovic Dubost <ludovic(a)xwiki.com> wrote:
Hi Cati,
Great proposals that enhances the current UI. My main comments concern
features that are not really finished in the current prototype and would
need some help also from a design/usability perspective:
1/ Adding a page to favorites and notifications
-> This has not been put in the UI and would be needed
-> Should it be a separate favorites than the XWiki Watch List. Right now
I don't think so because that would be yet another list and the Server wiki
will need to know about the favorites because it
IMO they are 2 different things. The problem is also our auto-watch feature
that register in the watchlist any page you made modifications to them, and
you don't quite have control over it.
Favorites are an explicit action that you do in order to later quick access
that page (similar to bookmarks), while watchlist is sort of an activity
stream for your specific range of pages, that you receive in your mail. So
IMO they should be separate.
Regarding the UI, the actions are displayed at the bottom of the page
(Edit, Syntax, Sync, etc. I've put just these actions because they were
also present in the prototype)
http://incubator.myxwiki.org/xwiki/bin/download/Improvements/MobileApp/page…
We will need a "More" button that would reveal additional actions, like
"Watch", "Favourite", etc. (depending on what and how many other
functionality we want to have for the Mobile App).
-> A design for notifications and how they should
show up would be great.
I think notifications could be a general UI item and also show up on the
home page. A notification is sent by the server to the device. The
notification is just a message. The XWiki Application can be activated from
the notification but will have to contact the server to know more (I'm not
sure if you get access to the notifications that the user clicked to
activate the App). I think a message could be just "this doc has been
updated" or "X documents have been modified" depending on the
notifications
settings of the user).
Regarding the notifications UI I think our notifications widget is just
fine http://platform.xwiki.org/xwiki/bin/view/DevGuide/XWikiNotifications
(a z-index div, with a color specific color depending on the notification
type, that is visible for a temporary period)
2/ Adding a page/space/applications to offline
documents would be needed in
the UI and a management UI for the page/spaces/applications being in the
offline docs
What is the difference between Offlice Documents, Offline Bookmarks and
Favorites?
Again I did the page actions mockup, but I was not sure what actions to put
http://incubator.myxwiki.org/xwiki/bin/download/Improvements/MobileApp/page…
but I imagined "Download" to represent adding the page to our Offline
Documents.
The action bar can be put to spaces, wikis, etc.
3/ The offline editing features should be removed for
now because they are
far from ready
4/ Commenting should be added in the UI
5/ A "share/open" button should be added which opens a popup proposing to
share by email/twitter/open in safari/etc..
6/ A configuration UI would be needed to add/update configuration for a new
Wiki. For now a simple URL would be enough + a username and password and an
"advanced" button. A specific service will probably be built in XE/XEM to
provide the configuration to the mobile App. It would be possible using
the "advanced configuration" to not need this server based configuration to
connect to any wiki but it will be more pratical with this configuration.
7/ I like the Application zone design. Now it should be reusing what is
done in the Application Panel since 4.2 (?). Now the issue is that a
specific REST/XWiki Page service might be needed here, as right now it's
manual configuration. Now the service used for the configuration could
handle that.
Regarding all the new functionality (sync, offline, bookmarks, editing, web
view, etc.) I am not really sure how they fully work (since they are not
yet complete) and I also don't know what level of other functionality you
want to add (you mentioned comments, share page, add wiki, etc.). Until now
I just focused on what was available.
Thanks for your feedback,
Caty
Ludovic
2012/11/28 Ecaterina Moraru (Valica) <valicac(a)gmail.com>
Hi devs,
For the Mobile App Investigation, Ludovic has been playing with a XWiki
Mobile App prototype done with jQuery Mobile (http://jquerymobile.com/).
This is a proposal for a mobile application that matches the jQuery
Mobile
framework capabilities and that provides minimal
XWiki functionality
(like
listing wikis, spaces, pages, accessing content,
viewing recent activity,
etc.)
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/MobileApp
Thanks,
Caty
_______________________________________________
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
4310
days inactive
4310
days old
5 comments
3 participants
participants (3)
-
Ecaterina Moraru (Valica) -
Jerome Velociter -
Ludovic Dubost