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

[Feature Request] Support more fields #2

Open
fohfuu opened this issue Aug 16, 2022 · 2 comments
Open

[Feature Request] Support more fields #2

fohfuu opened this issue Aug 16, 2022 · 2 comments
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed

Comments

@fohfuu
Copy link

fohfuu commented Aug 16, 2022

I want to preserve these information fields when exporting: DTEND (the event end day & time), LOCATION, and CATEGORIES. It would be nice to have options for CREATED and LAST-MODIFIED, too.

Is there a way to implement this?

@k3b
Copy link
Owner

k3b commented Aug 17, 2022

you want to (optionally) add

  • event-end-date-time (DTEND )
  • LOCATION
  • CATEGORIES
  • (Date-)CREATED
  • (Date-)LAST-MODIFIED

how should this feature be used without becoming too complicated to use?

what exactly is your usecase that needs the additional fields?

=======

my current usecase:
create a confirmation text for an appointment, that does not need the new fields.


currently the app has this hard-coded pattern that is used all the time

%MesssagePrefix%
%date% %title%
%messageContent%

message short=%date% %title%
message medium=%MesssagePrefix% %date% %title%
message long=%date% %title% %messageContent%
message full=%MesssagePrefix% %date% %title% %messageContent%

message short/medium/long/full will not work anymore whith the additional fields: too many combinations :-(


probably too much work and too complicated to use: Templateeditor
Requirements:

  • formatting-template-engine with %name%-placeholders that defaults to the current hardcoded pattern
  • in configActivity a
    • template editor where each template can be stored-to/read-from a file
    • template chooser

@k3b k3b added enhancement New feature or request help wanted Extra attention is needed good first issue Good for newcomers labels Aug 17, 2022
@fohfuu
Copy link
Author

fohfuu commented Aug 24, 2022

Sorry for the slow reply - life got in the way.

I would need to go into my personal details for my particular use case, but I will make a fictional comparison.

Let's say I have a Chemistry lecture every day. It is in different lecture halls on different days because the university has a room shortage, but there is nothing different about the content of the lectures, so when I wrote my timetable in my calendar, I gave each event the same name, "Chemistry", and added the room number in the location field. If I lose my calendar data and I go to check my backup using CalEF, I can't see what rooms I need to go in future.

You can imagine a similar situation for categories. I could have named both my lab sessions and lectures "Chemistry" and told them apart
by their category.

Including the end of the event would let me see how long my lab sessions are booked for.

The others fields would just be nice to have for future reference, but I don't have a particular need for them.

I thought there may be a limitation like this, that's a shame. I don't have anything else I can add to development, unfortunately. If the app is restructured in the future, it could be considered then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants