You can find the report at either  or down below as always.
---- REPORT TEXT BELOW -----
This week isn't as feature packed as previous weeks as I've been trying to figure
out where to go from the initial iteration of the ToDo Lists. I've added a blueprint
at[ 1] which details what I plan to do in the coming weeks. I hope it doesn't end up
taking me the remainder of the GSoC time as I would like to start looking at QML
integration but I think it's a killer feature for Entomologist to have so if it does
then that's not a loss to me as I would really like to have it implemented.
I've been working on adding iCalendar Export to the ToDo Lists and this revealed a few
issues with the design choices as iCalendar requires details such as e-mail addresses and
recipients to be included in the VTODO format. This is why I had to outline the steps
needed to get fully functional calendar export to work and I think a lot of new UI changes
need to be brought in to supplement that and to enhance the configurability of the ToDo
Initial testing of the iCalendar exporting appeared to work in iCal as it added the
Reminder but it would not sync with any of my cloud calendars that I have included. I
think that this is probably iCal itself not supporting the sync of ToDo Lists (or
Reminders in iCal parlance) rather than an issue with the format used. I've also used
iCalendar validators to check it and it seems that the .ics files produced are well formed
which, in all honesty, is the only thing I can really do. Adding little hacks for
different services is not the way I want this project to go as it would a) increase the
amount of code b) increase the complexity and c) it would break if something changed in
each individual service.
I think the best way to move forward is to take inspiration from the way that Trackers are
organised out and build objects that inherit from a base WebDAV/CalDAV client and add the
functionality required for API compatibility with various services. This would mean that
we support generic WebDAV servers that a user specifies and that we catch a lot of the
various services that exist without wasting lots of code trying to figure it out.
The primary services I want to target for this feature are:
Remember the Milk
External clients - Evolution/Thunderbird/iCal/Outlook.
I think Outlook might be a problem as a target as I'm not 100% sure it supports the
iCalendar format correctly. If it does then great, but I don't have a way to actually
test it as I don't own Microsoft Office on either a Mac or a Windows PC and I'm
not going to pay for it as I would never use it outside of the testing it would need.
I'm also not sure what calendar applications are popular on Windows but I'm
assuming that Thunderbird/Google Calendar based things are pretty common so I think
it's safe to target those.
So it's the 10th week and I've got a lot more work to do but it should all be
really interesting stuff to add and will be well worth the time it takes :).
 - http://wp.me/pjdJf-5n
 - http://trac.entomologist-project.org/wiki/ToDoListBlueprint
Thanks for reading,
Entomologist UI Changes.--
To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-project+help(a)opensuse.org