Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement editing vcal-status described in rfc 2445 and display options for different status #419

Closed
ionum opened this issue Apr 5, 2016 · 9 comments

Comments

@ionum
Copy link

ionum commented Apr 5, 2016

No description provided.

@georgehrke
Copy link
Contributor

please add an bit more elaborated description

@ionum
Copy link
Author

ionum commented Apr 5, 2016

VCAL has an option STATUS for indicating if the event is confirmed, tentative or canceled like this:
BEGIN:VCALENDAR
VERSION:1.0
BEGIN:VEVENT
STATUS:TENTATIVE
DTSTART:19960401T033000Z
DTEND:19960401T043000Z
SUMMARY:Your Proposal Review
END:VEVENT
END:VCALENDAR

This should be editable (simple dropdown) as well as displayed differently in the calendar

@MathieuSchopfer
Copy link
Contributor

Select the event status using a scroll-down select providing three values:
scoll_down

@MathieuSchopfer
Copy link
Contributor

Render the event using different styles, depending on its status:
events_rendering

I am not sure about the styling though ... Any suggestion ?

@georgehrke
Copy link
Contributor

@MathieuSchopfer Looks really good! :)
I'm not so sure about the question mark in front of tentative event though. cc @jancborchardt

@ionum
Copy link
Author

ionum commented Jun 23, 2016

@MathieuSchopfer Tres bien Mathieu!

Maybe less opacity and omit the question mark? outlook and thunderbird have an vertical bar on the left side for status... but this may be more difficult to implement....

@jancborchardt
Copy link
Member

Nice, the styles look good! Great work @MathieuSchopfer!

I would just remove the (?) from the tentative event because the opacity works to communicate that already. No further info is needed.

@MathieuSchopfer
Copy link
Contributor

MathieuSchopfer commented Jun 23, 2016

I am not convinced by the question mark either, let's get rid of it.

@ionum An icon, if really necessary, could be implemented in conjunction with #137.

@georgehrke
Copy link
Contributor

implemented by @MathieuSchopfer

will be released with 1.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants