Discussion:
1.0?
mobileorg-android on behalf of hjh
2013-04-06 15:07:11 UTC
Permalink
On Apr 6, 2013 8:18 PM, "mobileorg-android on behalf of Henning Weiss" <
What would it take for MobileOrg to reach 1.0 in your mind?
Congrats on the thesis!

It's already logged, but (as a reminder) I don't think MobileOrg would be
ready for 1.0 as long as the agenda interface is completely broken on some
combinations of device and Android version.

hjh
--
You received this message because you are subscribed to the Google Groups "mobileorg-android" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mobileorg-android+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To post to this group, send email to mobileorg-android-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
Visit this group at http://groups.google.com/group/mobileorg-android?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
mobileorg-android on behalf of Henning Weiss
2013-04-06 12:18:26 UTC
Permalink
Hello MobileOrg(-android) community,

I handed in my master thesis a week ago and finally I have some time to
work on MobileOrg again. We still have a lot of open issues on github
(currently 54!), but I think that we are getting closer to 1.0. All the
essential features that I use on a regular basis are implemented and work
somewhat reliably. There's still a lot of work to do, but I think it might
be realistic to aim for the end of the year (maybe christmas?) to have a
1.0 release. Now we just need to know what that entails...

What would it take for MobileOrg to reach 1.0 in your mind? Are there any
features or bugs you would like to see implemented/fixed/changed that are
not on the issue tracker?

Henning
--
You received this message because you are subscribed to the Google Groups "mobileorg-android" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mobileorg-android+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To post to this group, send email to mobileorg-android-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
Visit this group at http://groups.google.com/group/mobileorg-android?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
mobileorg-android+noreply-APn2wQdrTAXbeEqg-Z2k-4IjRcba_OQ6KIUkbW-/
2013-04-08 07:41:57 UTC
Permalink
Post by mobileorg-android on behalf of Henning Weiss
Hello MobileOrg(-android) community,
I handed in my master thesis a week ago and finally I have some time to work on MobileOrg again. We still have a lot of open issues on github (currently 54!), but I think that we are getting closer to 1.0. All the essential features that I use on a regular basis are implemented and work somewhat reliably. There's still a lot of work to do, but I think it might be realistic to aim for the end of the year (maybe christmas?) to have a 1.0 release. Now we just need to know what that entails...
What would it take for MobileOrg to reach 1.0 in your mind? Are there any features or bugs you would like to see implemented/fixed/changed that are not on the issue tracker?
- Issue 291 is a big one for me, including the added info in the comments that have been posted on that issue - I'm prevented from using MobileOrg for most of my appointments, because they use some special diary functions - therefore I've nearly given up on MobileOrg altogether.

In general, emphasize the improvements that bring MobileOrg's parser closer to Org-mode's parser, so that MobileOrg users have less of a need to remember the list of things that MobileOrg won't parse. Having a flexible tool like Org-mode and then needing to use it in a very restricted way in order to satisfy another piece of software is frustrating.
--
Thanks!
David
--
You received this message because you are subscribed to the Google Groups "mobileorg-android" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mobileorg-android+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To post to this group, send email to mobileorg-android-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
Visit this group at http://groups.google.com/group/mobileorg-android?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
mobileorg-android+noreply-APn2wQc1Pqj6iSSoix2v4RkDgC9sxtdsl8oFnO-/
2013-04-08 12:09:12 UTC
Permalink
Hya all

im c complete neewb to emacs,org and mobile org but making baby steps and really enjoying it.

to be honest the thing that made me finally make the "jump" to org was mobile org :) since android sync is a must for me at work

One thing im a little surprised that dosent exist and would trully help me out (and seems pretty trivial to implement) is reading (and editing in plain text) org files not related to capture or agenda.

That is all my *.org files are in dropbox anyway, it would be cool to add a very simple option> view org file. one would load an org file and just view it inside mobile org (with nice color heading etc). that by itself would be fantastic

Also if the devs have time and like that idea, a simple editor for org files would also be great

Thx alot again

Z
mobileorg-android+noreply-APn2wQdrTAXbeEqg-Z2k-4IjRcba_OQ6KIUkbW-/
2013-04-09 21:49:44 UTC
Permalink
Post by mobileorg-android+noreply-APn2wQdrTAXbeEqg-Z2k-4IjRcba_OQ6KIUkbW-/
Post by mobileorg-android on behalf of Henning Weiss
Hello MobileOrg(-android) community,
I handed in my master thesis a week ago and finally I have some time to work on MobileOrg again. We still have a lot of open issues on github (currently 54!), but I think that we are getting closer to 1.0. All the essential features that I use on a regular basis are implemented and work somewhat reliably. There's still a lot of work to do, but I think it might be realistic to aim for the end of the year (maybe christmas?) to have a 1.0 release. Now we just need to know what that entails...
What would it take for MobileOrg to reach 1.0 in your mind? Are there any features or bugs you would like to see implemented/fixed/changed that are not on the issue tracker?
- Issue 291 is a big one for me, including the added info in the comments that have been posted on that issue - I'm prevented from using MobileOrg for most of my appointments, because they use some special diary functions - therefore I've nearly given up on MobileOrg altogether.
In general, emphasize the improvements that bring MobileOrg's parser closer to Org-mode's parser, so that MobileOrg users have less of a need to remember the list of things that MobileOrg won't parse. Having a flexible tool like Org-mode and then needing to use it in a very restricted way in order to satisfy another piece of software is frustrating.
Here's what I've come up with since I wrote that message: The problem for me is pretty specific. Items with org-class do show up in MobileOrg's agenda, but are not transferred to the phone's calendar (perhaps because of the way time stamps are read?); and what I really wanted out of MobileOrg was a way to get those org-class items on my phone calendar.

Am I just doing something incorrectly here?
--
Thanks again
David
--
You received this message because you are subscribed to the Google Groups "mobileorg-android" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mobileorg-android+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To post to this group, send email to mobileorg-android-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
Visit this group at http://groups.google.com/group/mobileorg-android?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
mobileorg-android on behalf of Henning Weiss
2013-04-09 23:42:47 UTC
Permalink
On Tue, Apr 9, 2013 at 11:49 PM, <
Post by mobileorg-android on behalf of Henning Weiss
Post by mobileorg-android+noreply-APn2wQdrTAXbeEqg-Z2k-4IjRcba_OQ6KIUkbW-/
Post by mobileorg-android on behalf of Henning Weiss
Hello MobileOrg(-android) community,
I handed in my master thesis a week ago and finally I have some time
to work on MobileOrg again. We still have a lot of open issues on github
(currently 54!), but I think that we are getting closer to 1.0. All the
essential features that I use on a regular basis are implemented and work
somewhat reliably. There's still a lot of work to do, but I think it might
be realistic to aim for the end of the year (maybe christmas?) to have a
1.0 release. Now we just need to know what that entails...
Post by mobileorg-android+noreply-APn2wQdrTAXbeEqg-Z2k-4IjRcba_OQ6KIUkbW-/
Post by mobileorg-android on behalf of Henning Weiss
What would it take for MobileOrg to reach 1.0 in your mind? Are there
any features or bugs you would like to see implemented/fixed/changed that
are not on the issue tracker?
Post by mobileorg-android+noreply-APn2wQdrTAXbeEqg-Z2k-4IjRcba_OQ6KIUkbW-/
- Issue 291 is a big one for me, including the added info in the
comments that have been posted on that issue - I'm prevented from using
MobileOrg for most of my appointments, because they use some special diary
functions - therefore I've nearly given up on MobileOrg altogether.
Post by mobileorg-android+noreply-APn2wQdrTAXbeEqg-Z2k-4IjRcba_OQ6KIUkbW-/
In general, emphasize the improvements that bring MobileOrg's parser
closer to Org-mode's parser, so that MobileOrg users have less of a need to
remember the list of things that MobileOrg won't parse. Having a flexible
tool like Org-mode and then needing to use it in a very restricted way in
order to satisfy another piece of software is frustrating.
Here's what I've come up with since I wrote that message: The problem for
me is pretty specific. Items with org-class do show up in MobileOrg's
agenda, but are not transferred to the phone's calendar (perhaps because of
the way time stamps are read?); and what I really wanted out of MobileOrg
was a way to get those org-class items on my phone calendar.
Am I just doing something incorrectly here?
Not at all, see issue
291<https://github.com/matburt/mobileorg-android/issues/291>.
Currently only "normal" active timestamped entries are supported.

Henning
--
You received this message because you are subscribed to the Google Groups "mobileorg-android" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mobileorg-android+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To post to this group, send email to mobileorg-android-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
Visit this group at http://groups.google.com/group/mobileorg-android?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
mobileorg-android+noreply-APn2wQdrTAXbeEqg-Z2k-4IjRcba_OQ6KIUkbW-/
2013-04-10 08:21:22 UTC
Permalink
Post by mobileorg-android+noreply-APn2wQdrTAXbeEqg-Z2k-4IjRcba_OQ6KIUkbW-/
Post by mobileorg-android+noreply-APn2wQdrTAXbeEqg-Z2k-4IjRcba_OQ6KIUkbW-/
Post by mobileorg-android on behalf of Henning Weiss
Hello MobileOrg(-android) community,
I handed in my master thesis a week ago and finally I have some time to work on MobileOrg again. We still have a lot of open issues on github (currently 54!), but I think that we are getting closer to 1.0. All the essential features that I use on a regular basis are implemented and work somewhat reliably. There's still a lot of work to do, but I think it might be realistic to aim for the end of the year (maybe christmas?) to have a 1.0 release. Now we just need to know what that entails...
What would it take for MobileOrg to reach 1.0 in your mind? Are there any features or bugs you would like to see implemented/fixed/changed that are not on the issue tracker?
- Issue 291 is a big one for me, including the added info in the comments that have been posted on that issue - I'm prevented from using MobileOrg for most of my appointments, because they use some special diary functions - therefore I've nearly given up on MobileOrg altogether.
In general, emphasize the improvements that bring MobileOrg's parser closer to Org-mode's parser, so that MobileOrg users have less of a need to remember the list of things that MobileOrg won't parse. Having a flexible tool like Org-mode and then needing to use it in a very restricted way in order to satisfy another piece of software is frustrating.
Here's what I've come up with since I wrote that message: The problem for me is pretty specific. Items with org-class do show up in MobileOrg's agenda, but are not transferred to the phone's calendar (perhaps because of the way time stamps are read?); and what I really wanted out of MobileOrg was a way to get those org-class items on my phone calendar.
Am I just doing something incorrectly here?
Not at all, see issue 291. Currently only "normal" active timestamped entries are supported.
Thanks. I'm probably just being a chauvinist regarding my own favourite parts of Emacs and Org-mode, so of course take this with considerable salt; but I'm not convinced of a version 1.0 that comes with the footnote "Some of the most attractive features of the Org-mode agenda are not supported." I guess the other side of that coin is, trying to support nearly-endless possibilities can get a little tricky. :)
--
David
--
You received this message because you are subscribed to the Google Groups "mobileorg-android" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mobileorg-android+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To post to this group, send email to mobileorg-android-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
Visit this group at http://groups.google.com/group/mobileorg-android?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
mobileorg-android on behalf of hjh
2013-04-10 09:31:34 UTC
Permalink
Post by mobileorg-android+noreply-APn2wQdrTAXbeEqg-Z2k-4IjRcba_OQ6KIUkbW-/
Thanks. I'm probably just being a chauvinist regarding my own favourite
parts of Emacs and Org-mode, so of course take this with considerable salt;
but I'm not convinced of a version 1.0 that comes with the footnote "Some
of the most attractive features of the Org-mode agenda are not supported."
I guess the other side of that coin is, trying to support nearly-endless
possibilities can get a little tricky. :)

The point about this that came up on the org list was, if you can call
arbitrary lisp functions (including user defined functions) in a timestamp
specifier, is it possible to support it fully without reimplementing every
lisp function from emacs, as well as a lisp parser? By itself, org-class
wouldn't be too hard (unless you call lisp functions in the argument
list... then... ugh).

I'd have to check, but I think MobileOrg is supposed to populate the
calendar using items from the pushed agenda views. You could perhaps define
a "today + 30 days" agenda and include that for push.

FWIW, my org calendar includes college courses, but I don't use org-class
because I want separate headers for every class session, where I can record
prep notes and after-class TODOs. That is, for me it's not just a reminder;
it's a thing of its own, with a little or a lot of associated info under it.

hjh
--
You received this message because you are subscribed to the Google Groups "mobileorg-android" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mobileorg-android+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To post to this group, send email to mobileorg-android-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
Visit this group at http://groups.google.com/group/mobileorg-android?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
mobileorg-android on behalf of Henning Weiss
2013-04-10 12:41:50 UTC
Permalink
Hi,

On Wed, Apr 10, 2013 at 11:31 AM, mobileorg-android on behalf of hjh <
Post by mobileorg-android+noreply-APn2wQdrTAXbeEqg-Z2k-4IjRcba_OQ6KIUkbW-/
Post by mobileorg-android+noreply-APn2wQdrTAXbeEqg-Z2k-4IjRcba_OQ6KIUkbW-/
Thanks. I'm probably just being a chauvinist regarding my own favourite
parts of Emacs and Org-mode, so of course take this with considerable salt;
but I'm not convinced of a version 1.0 that comes with the footnote "Some
of the most attractive features of the Org-mode agenda are not supported."
I guess the other side of that coin is, trying to support nearly-endless
possibilities can get a little tricky. :)
The point about this that came up on the org list was, if you can call
Post by mobileorg-android+noreply-APn2wQdrTAXbeEqg-Z2k-4IjRcba_OQ6KIUkbW-/
arbitrary lisp functions (including user defined functions) in a timestamp
specifier, is it possible to support it fully without reimplementing every
lisp function from emacs, as well as a lisp parser? By itself, org-class
wouldn't be too hard (unless you call lisp functions in the argument
list... then... ugh).
I'd have to check, but I think MobileOrg is supposed to populate the
calendar using items from the pushed agenda views. You could perhaps define
a "today + 30 days" agenda and include that for push.
The calendar works by finding timestamped entries. It does not use the
agenda view. Currently it only supports Scheduled, Deadline and active
timestamps in the body of entries. I have moved all the additional
timestamps I'll implement at some point
here<https://github.com/matburt/mobileorg-android/issues/381> --
org-class
timestamps is one of them.

Henning
--
You received this message because you are subscribed to the Google Groups "mobileorg-android" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mobileorg-android+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To post to this group, send email to mobileorg-android-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
Visit this group at http://groups.google.com/group/mobileorg-android?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
mobileorg-android+noreply-APn2wQdrTAXbeEqg-Z2k-4IjRcba_OQ6KIUkbW-/
2013-04-11 05:32:28 UTC
Permalink
The calendar works by finding timestamped entries. It does not use the agenda view. Currently it only supports Scheduled, Deadline and active timestamps in the body of entries. I have moved all the additional timestamps I'll implement at some point here -- org-class timestamps is one of them.
Thanks. Sounds good to me.
--
David
--
You received this message because you are subscribed to the Google Groups "mobileorg-android" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mobileorg-android+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To post to this group, send email to mobileorg-android-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
Visit this group at http://groups.google.com/group/mobileorg-android?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
mobileorg-android on behalf of Henning Weiss
2013-04-06 18:58:36 UTC
Permalink
On Sat, Apr 6, 2013 at 5:07 PM, mobileorg-android on behalf of hjh <
Post by mobileorg-android on behalf of hjh
On Apr 6, 2013 8:18 PM, "mobileorg-android on behalf of Henning Weiss" <
What would it take for MobileOrg to reach 1.0 in your mind?
Congrats on the thesis!
Thanks!
Post by mobileorg-android on behalf of hjh
It's already logged, but (as a reminder) I don't think MobileOrg would be
ready for 1.0 as long as the agenda interface is completely broken on some
combinations of device and Android version.
Yeah, definitely. It's one of the next things I'll look at.
--
You received this message because you are subscribed to the Google Groups "mobileorg-android" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mobileorg-android+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To post to this group, send email to mobileorg-android-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
Visit this group at http://groups.google.com/group/mobileorg-android?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
mobileorg-android on behalf of hjh
2013-04-08 12:11:55 UTC
Permalink
On Apr 7, 2013 2:58 AM, "mobileorg-android on behalf of Henning Weiss" <
Post by mobileorg-android on behalf of Henning Weiss
Post by mobileorg-android on behalf of hjh
It's already logged, but (as a reminder) I don't think MobileOrg would
be ready for 1.0 as long as the agenda interface is completely broken on
some combinations of device and Android version.
Post by mobileorg-android on behalf of Henning Weiss
Yeah, definitely. It's one of the next things I'll look at.
I saw the push message for this, thanks. I'm not set up to build from
source, and extremely short of time these days, so unfortunately I'm unable
to test just now.

I thought of another, not sure if it's logged: If I add a new scheduled
node in MobileOrg, it doesn't land in the Android calendar until I sync the
new entry over to the computer, org-mobile-pull and -push, and resync in
MobileOrg. That's an untidy workflow. (I'm aware I could "experimentally"
create appointments in the Droid calendar and have them show up as
Captures, but I would rather manage my calendar through the org interface,
among other reasons, to enter appointments into the right place in my
hierarchy to avoid structure editing when syncing.)

Thanks!
James
--
You received this message because you are subscribed to the Google Groups "mobileorg-android" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mobileorg-android+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To post to this group, send email to mobileorg-android-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
Visit this group at http://groups.google.com/group/mobileorg-android?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
mobileorg-android on behalf of Henning Weiss
2013-04-08 17:06:47 UTC
Permalink
Hi,

On Mon, Apr 8, 2013 at 2:11 PM, mobileorg-android on behalf of hjh <
Post by mobileorg-android on behalf of hjh
I thought of another, not sure if it's logged: If I add a new scheduled
node in MobileOrg, it doesn't land in the Android calendar until I sync the
new entry over to the computer, org-mobile-pull and -push, and resync in
MobileOrg. That's an untidy workflow. (I'm aware I could "experimentally"
create appointments in the Droid calendar and have them show up as
Captures, but I would rather manage my calendar through the org interface,
among other reasons, to enter appointments into the right place in my
hierarchy to avoid structure editing when syncing.)
Thanks!
James
this has been something I have been meaning to fix for while. The related
issue can be found
here <https://github.com/matburt/mobileorg-android/issues/241>.

Henning
--
You received this message because you are subscribed to the Google Groups "mobileorg-android" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mobileorg-android+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
To post to this group, send email to mobileorg-android-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
Visit this group at http://groups.google.com/group/mobileorg-android?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Loading...