Samuel Loury writes:
> I have been using the XML-RPC trac plugin³ for a while now and I made we
> wonder if we could reproduce this in the scope of mobile org. With an
> RPC interface, one would be free to create their own interface easily
> (at least python xml-rpc library is really easy to mani
Xebar Saram writes:
> would LOVE to try it as well
So would I !
>>> Henning Weiss writes:
>>>
I have been working over the last couple of months on a private
prototype. I'm currently using it in my daily life and it works for me. It
uses Git (and only Git) for synchronization an
would LOVE to try it as well
thx!
z
On Thu, Aug 14, 2014 at 4:36 PM, Jorge A. Alfaro-Murillo <
jorge.alfaro-muri...@yale.edu> wrote:
> Eric Abrahamsen writes:
>
>> Henning Weiss writes:
>>
>>> I have been working over the last couple of months on a private
>>> prototype. I'm currently using i
Eric Abrahamsen writes:
Henning Weiss writes:
I have been working over the last couple of months on a private
prototype. I'm currently using it in my daily life and it works
for me. It uses Git (and only Git) for synchronization and
doesn't use org-mobile at all. The idea is that you keep al
Henning Weiss writes:
> Hi,
>
> My name is Henning and I am the co-maintainer of MobileOrg Android.
>
> The reason I stopped working on the project is partially the lack of
> time, but also because I didn't believe in the design of
> org-mobile-push/pull and edit nodes. Almost half of the bugs on
Hi,
My name is Henning and I am the co-maintainer of MobileOrg Android.
The reason I stopped working on the project is partially the lack of time,
but also because I didn't believe in the design of org-mobile-push/pull and
edit nodes. Almost half of the bugs on our issue tracker are with regards
Sean Escriva writes:
>>> https://cordova.apache.org/
>>http://kivy.org
> From the little experience I have with them, cross platform frameworks
> do suffer from a loss of fidelity compared to native applications but
> as mentioned that may be an acceptable trade off.
We are talking about
It's probably hard to assertain interest because
1) iOS projects have a high barrier to entry contribution wise.
2) A lot of people feel mobileorg doesn't fit their current needs, and
are using something else.
I definitely fall into both categories. I wouldn't be surprised if a few
people come ba
Greetings Org users!
(Current MobileOrg iOS maintainer here)
Great to read some feedback. It's often hard to know who really cares if
MobileOrg even exists.
Jacek Generowicz writes:
> Alexis writes:
>
>> i can't help but wonder if the 'MobileOrg' endeavour needs a reboot.
>
> It seems clear
Carlos Sosa writes:
> There's a difference feature wise between MobileOrgNG[1] and
> MobileOrg-Android[2], which I believe should be merged into one project.
> For instance, I don't know of MobileOrgNG having a SSH synchronizer
> which many people make use of, including me, but with that said,
>
Jacek Generowicz writes:
> Alexis writes:
>
>> One could, for example, create an entirely new project on GitHub
>> called 'MobileOrgRebooted', and create entirely new apps in the
>> respective stores using that name.
>
> That strikes me as the sensible thing to do.
>
>> (As it is, there's not a
Alexis writes:
> One could, for example, create an entirely new project on GitHub
> called 'MobileOrgRebooted', and create entirely new apps in the
> respective stores using that name.
That strikes me as the sensible thing to do.
> (As it is, there's not a uniformly named app in any case - we
That seems reasonable to me.
--
Ashton Kemerling
David Wagle writes:
> What's involved in 'rebooting' the project?
My thought involves starting from scratch. Say we use Cordova (i can't
speak to the pros and cons of Cordova vs. Kivy in terms of things like
functionality provided, possible barriers to contribution etc.). Cordova
takes care of a
Ashton Kemerling writes:
> I can say for certain that we would have to figure out the handoff of
> various credentials from the old maintainers (who I am assuming would
> not like to continue being maintainers) for the respective app-stores
> and Dropbox tokens.
Not necessarily. One could, for
David Wagle writes:
> What's involved in 'rebooting' the project? Are the various owners of
> the iPhone and Android packages on this list?
>
> I'm not a coder at all, but I've administratively managed software
> projects before. I'm more than happy to do what I know how to do --
> which is most
What's involved in 'rebooting' the project? Are the various owners of the
iPhone and Android packages on this list?
I'm not a coder at all, but I've administratively managed software projects
before. I'm more than happy to do what I know how to do -- which is mostly
send out emails asking people i
I did some digging into that a few months ago. While I'm not an
experienced iOS dev, I flailed about for a few weeks trying to add
deadline parsing and failed miserably.
I'm fairly convinced that most of the code is either super platform
specific or in need of replacing with easier to maintain &
Alexis writes:
> i can't help but wonder if the 'MobileOrg' endeavour needs a reboot.
It seems clear that it does.
> More specifically, it seems to me that rebuilding MobileOrg as a single
> project [...] might be a way forward,
This is vital!
> on top of Apache Cordova:
>
> https://cordova
Alexis writes:
> Hi all,
>
> In light of recent discussions about 'MobileOrg' - which seemingly
> actually constitutes two distinct projects for two different platforms -
> together with the apparent relative lack of activity of both projects,
> despite demand for them, i can't help but wonder if
Would love to see a reboot and further development on org-mobile. I am not
a developer myself but would love to help out with testing , writing
documentation etc
best
Z
On Sat, Aug 9, 2014 at 3:56 AM, Alexis wrote:
>
> Hi all,
>
> In light of recent discussions about 'MobileOrg' - which seemi
21 matches
Mail list logo
