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.

Sign up for GitHub

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

Jump to bottom

Support, Discussion, Suggestions, Critics for v1.5 #20

Closed
aceisace opened this issue Feb 5, 2019 · 123 comments
Closed

Support, Discussion, Suggestions, Critics for v1.5 #20

aceisace opened this issue Feb 5, 2019 · 123 comments
Assignees
@aceisace
Labels
enhancement New feature or request good first issue Good for newcomers outdated This issue is from a previous release and is most likey not relevant. (Archived)
Projects
Release v1.6

Comments

@aceisace
Copy link
Collaborator

aceisace commented Feb 5, 2019

Here you have an option to chat about improvement ideas regarding v1.5 of the E-Paper Calendar software.

As usual, nothing and nobody is perfect, but we can strive to get closer towards that. Please post your comments in a friendly way and remember to be nice. Thanks for your understanding.

All improvement ideas are welcome.
@aceisace aceisace added enhancement New feature or request good first issue Good for newcomers labels Feb 5, 2019
@aceisace aceisace pinned this issue Feb 6, 2019
@aceisace aceisace self-assigned this Feb 6, 2019
@zAm1987
Copy link

zAm1987 commented Feb 10, 2019 •
edited

I tried a fresh install of raspian stretch lite with the installer (option 2) for the new version.
After the first try somehow the E-Paper-Master folder was empty and so there was no script to start.

During my second try I watched the installer and it worked well. Only the description says "nano ... settings.py", but the filename is "settings.py.sample".

Also I tried a manuel calibration, because the display was offline for a while and the icons where somewhat distorted after running the new version for the first time. During the calibration the following error occured (I have the 2-color version)

pi@raspberrypi:~/E-Paper-Master/Calendar $ python3.5 calibration.py calibrating black... Traceback (most recent call last): File "calibration.py", line 40, in <module> main() File "calibration.py", line 37, in main calibration() File "calibration.py", line 27, in calibration epd.display_frame(epd.get_frame_buffer(red)) UnboundLocalError: local variable 'red' referenced before assignment

I think the distorted icons and the error in the calibration process indicates that the script somehow thinks the 3-color-display is connected and not the 2-color-display, despite the "bw" setting in the settings file...

@aceisace
Copy link
Collaborator Author

@zAm1987
Hi, it seems as though there were some conflicts with the Installer and the new version.
The error above seems to be caused by 2 different versions (v1.4 and v1.5) running in the same environment.

The best way to fix this is by backing up modified files form the E-Paper-Master directory (should normally only be the settings.py file) to the home directory. Then, please re-run the installer to uninstall the software and lastly, use the installer to install the software again. Your issue should be fixed after a reboot. Should something still go wrong, please paste the error here.

The missing settings.py file was a bug in the Installer. I've just now fixed it so a settings.py file exists when choosing the install option form the installer.

Thank you for pointing out the bug 👍

@zAm1987
Copy link

zAm1987 commented Feb 11, 2019

@aceisace

The question is how the two different versions came into place, because as I described it was a completely fresh Installation from an untouched raapian stretch lite image.

Anyway, I will try the uninstalling and reinstalling option and report whether it works or not ;)

@aceisace
Copy link
Collaborator Author

@zAm1987
I‘ve found the cause for this error. In settings.py, line 27 should have been indented but it wasn‘t. I‘ve just now fixed and tested the calibration module for the 2-colour display. It should work just fine now.

@zAm1987
Copy link

zAm1987 commented Feb 12, 2019 •
edited by aceisace

@aceisace

I used the uninstall option and installed again. I can confirm that the calibration now works as it should.

The settings.py file however is still missing after the install option.

And again, the Icons and the font looks somewhat distorted. I am not sure if this was the case with the older version, but it seems that everything is pixelated. Maybe the script still thinks it's a 3-color-version and so the missing red causes the jagged edges? It could be the voltage, too, because my actual "test bench" is fed via an usb-hub and the e-paper-display is known for having problems with slightly different voltages...

@aceisace
Copy link
Collaborator Author

@zAm1987
It's good to hear that the calibration module works as expected.
I'll look into the missing settings.py file again.
For now, please type in the following commands in the terminal:

cd /home/pi/E-Paper-Master/Calendar
cp settings.py.sample settings.py

In regards to the slightly disorted icons, this is a non-desired side-effect caused by switching from specially formatted .BMP icons to standard .JPEG icons. Up to v1.4, all icons were rotated, inverted and in .BMP format. The main problem was that the time taken for making even a single 'perfect' icon (in BMP) was too long for a project in development phase (adding more features etc.), so I'm using JPEG icons now. If you want to know more about it, please see this comment in issue1 (image to data conversion)

You can try reducing the disortion by editing this section in home/pi/E-Paper-Master/Calendar/epd7in5.py.

for y in range(self.height):
            for x in range(self.width):
                # Set the bits for the column of pixels at the current position.
                if pixels[x, y] != 0: # this part
                    buf[int((x + y * self.width) / 8)] |= 0x80 >> (x % 8)
        return buf

Currently, anything that isn't fully white, is converted to shades of grey. I did try to modify these values, but the results aren't as good yet. Once I've fixed a few iCalendar-related issues, I'll work on improving this section.

So the issue is not related to the fact that the main script thinks you're using a black-white-red display, nor is it related to a different voltage level caused by using usb-hub.

@zAm1987
Copy link

zAm1987 commented Feb 12, 2019

@aceisace

Ah okay, somehow i missed the switch to the jpg format. Sounds reasonable and I can understand it. Thanks for the explanation. :)
I will try to play around with the icons, when I finally have an bit more time.

For the missing settings file I already nano'ed into the sample file and saved / renamed it in order to fix it ;)

@aceisace
Copy link
Collaborator Author

@zAm1987
Sound good :)
Keep me updated when you make some progess with the icons. Thanks.

@aceisace
Copy link
Collaborator Author

For anyone interested, here is a breakdown on how long the main programm takes for each section:

  • Preparing monthly Calendar template: <1s
  • Connecting to openweathermap api servers and fetching data: 17 seconds
  • Filtering upcoming events: <3s
  • Converting Image to Data and sending it to the display: 60-70 seconds
  • Refreshing E-Paper-Display: 6s for black-white, 16s for black-white-red E-Paper display
  • Calibration time for black-white-red E-Paper-display: 443s
  • Calibration time for black-white E-Paper-display: 247s

@jankosso
Copy link

The Alert issue is quite annoying, because all my calenders use them.

Can you elaborates a little bit, what causes this issue?

@aceisace
Copy link
Collaborator Author

@jankosso
The Alert issue is supposed to have been fixed in the last few days. It consists of this section:

for icalendars in ical_urls:
                decode = str(urlopen(icalendars).read().decode())
                #fix a bug related to Alarm action by replacing parts of the icalendar
                fix_e = decode.replace('BEGIN:VALARM\r\nACTION:NONE','BEGIN:VALARM\r\nACTION:DISPLAY\r\nDESCRIPTION:')
                #uncomment line below to display your calendar in ical format
                #print(fix_e)
                ical = Calendar(fix_e)

The fix_e (fix error) line is meant to fix alert-based errors, at least for Google Calendar. I am using this myself and can confirm that it works with Google (i)Calendar.

The main issue lies with the ics.py python library (see here). The ics.py library is a bit picky with the formatting of the iCalendar. Although there is a standard for the iCalendar format, not every provider is using the latest version. Due to the differences in formatting, errors are caused. For example, in the iCalendar from google, the Alert=None part causes the issue. Ics.py does not support Action=None and throws an Alert-error. The above snippet replaces the None with Display so ics.py does not throw the error. You can let python print your iCalendar in the iCalendar format by uncommenting the line print(fix_e)
I did open an issue at the ics.py repo to report this issue and another one, but it seems as though it didn't really get any attention from the developer.

As every iCalendar (from different providors) varies slightly in format, it's difficult to implement the support for every single format. As Google Calendar is the most used one, it has been implemented first.

@7n2jju
Copy link

7n2jju commented Feb 19, 2019 •
edited

Hi, I just report a problem when week_starts_on = "Sunday" is used and fixed it.

This causes an error like:

Traceback (most recent call last):
  File "E-Paper.py", line 282, in <module>
    main()
  File "E-Paper.py", line 82, in main
    draw(weekplace, weeksun)
  File "/usr/local/lib/python3.5/dist-packages/PIL/ImageDraw.py", line 135, in bitmap
    self.draw.draw_bitmap(xy, bitmap.im, ink)
ValueError: bad transparency mask

So, I just removed line 82 in E-Paper.py that calls draw(weekplace, weeksun) following to the case Monday and it worked fine when week starts from Sunday.

@aceisace
Copy link
Collaborator Author

@7n2jju
Hi, thanks for finding the bug. I've just now removed line 82 from the E-Paper.py file on this repo to make sure it doesn't happen again.

@jankosso
Copy link

Regarding the Google calendar issue:

@aceisace thanks for the info, i dug a little deeper into that lib and i think i found the issue.
Your workarround only fixes Alert=None issue, but the library also doesn't work with Alert=Email.
In the alarm.py you can read, that is still a ToDo ;-)

`def get_type_from_action(cls, action_type):
# TODO: Implement EMAIL action
if action_type == 'DISPLAY':
return DisplayAlarm
elif action_type == 'AUDIO':
return AudioAlarm
elif action_type == 'NONE':
return None

    raise ValueError('Invalid alarm action')`

I just changed it to return None, when the action is Email and this fixed it:

`def get_type_from_action(cls, action_type):
# TODO: Implement EMAIL action
if action_type == 'DISPLAY':
return DisplayAlarm
elif action_type == 'AUDIO':
return AudioAlarm
elif action_type == 'NONE':
return None
elif action_type == 'EMAIL':
return None

    raise ValueError('Invalid alarm action')`

So for a workarround without patching the lib, you can also replace the ACTION:EMAIL
Like so:
fix_e = fix_e.replace('BEGIN:VALARM\r\nACTION:EMAIL','BEGIN:VALARM\r\nACTION:DISPLAY\r\nDESCRIPTION:')

@aceisace
Copy link
Collaborator Author

@jankosso
Thank you very much for taking your time to research about the iCalendar issue and finding a way to solve the issue :) 💯
I'll test out the recommended change tomorrow and will implement it as soon as I can confirm that it works.

@aceisace
Copy link
Collaborator Author

@jankosso
I've tested out your suggested fix for the raise ValueError('Invalid alarm action') and have implemented the change on the master branch. Thanks for contributing 👍

@aceisace
Copy link
Collaborator Author

Quick update:
The software was recently updated. Some of the main improvements are:

  • Added events_max_range parameter in the settings.py file. See the list in the README for more info
  • The space below the Calendar is used more efficiently. The Display will now display all events that can fit below the monthly Calendar. Depending on how much space there is, there may be 4 or 6. displayed events
  • Improved the calibration time by opening images instead of generating images.

If you want to switch to the latest version, please re-run the installer, selecting the 'update' option.
Should you notice a bug, please let me know either by mail or by opening an issue. Thanks.

@Clickbaitcake
Copy link

Clickbaitcake commented Feb 27, 2019 •
edited

Is there any possibility of getting a Day View similar to that in Outlook? This would really help me keep on top of my day. The moving bar shows the current time and how far into the next meeting block I should be. Further to this, is exchange connectivity possible?
Example screenshot attached.

What do you think?

image

@multimedial
Copy link

multimedial commented Feb 27, 2019 •
edited by aceisace

Hello,

I am from Duesseldorf, and found your project via the Waveshare page when trying to test my e-Ink Paper display.

I got an issue after installing your code and editing the settings.py file accordingly - the free API key provided from OpenWeatherMap is apparently not entitled to pull down the current weather forecast.

I was also wondering if I could discuss a project I am working on with you via email.

Looking forward to your answer, and thanks for the code.

Oh, and I would like to second a daily view for the current date - this is what I am currently striving for.

@aceisace
Copy link
Collaborator Author

@Clickbaitcake
Hi Secprentice, thanks for suggesting a new feature. The daily view is certainly possible but will require some time to finish. I'm estimating it'll take at least a few weeks, but it might be finished faster (or slower) than that.
As the space on the Calendar is almost used up, I can only implement the daily view by replacing the monthly Calendar. Does this sound like a good compromise?
I can also implement the moving bar which shows the current time on the daily view, but it might not be such an good idea for an E-Paper display as more frequent display updates are not good for the Display. If you don't mind an update interval of 15 minutes, I can implement it. But I wonder if it's useful if the time is updated every 15 minutes. If you do more frequent updates than 15 minutes, the Raspberry will be under pretty heavy load (nearly) all the time. Let me know about your opinion.
Also, I've not heard or come across 'exchange connectivity'. Do you mind elaborating a bit more about this? Thanks in advance.

@aceisace
Copy link
Collaborator Author

@multimedial
Hi, thanks for your interest in the E-Paper software, for your comment and your compliment :)
You did mention about an issue where your key was not entitled to get weather forecasts .

As there is no error message attached, it's a bit difficult finding out where exactly the issue lies. But these are the tips I can give you for now:

  • Make sure that your api-key is in string format in the settings.py file, for example:
    api_key = "somesecretopenweathermapapikey"
  • Free api-keys are not entitled to get weather forecasts, only the current weather. Previously, free users could get that access but openweathermap stopped it some time ago. If you're not trying to get the forecast or if you've not modified the E-Paper.py file, most likely it's the next point.
  • If you try to request the current weather data too many times in a short period of time, the server will temporarlily block the access. Usually, trying again in a few hours (or the next day) resolves the issue and
    everything will start to work like normal again.

If the error still persists, please paste the error message in your next comment. Then I can try to debug the issue more specifically.

Sorry I had to edit your comment. It's usually not a good idea adding personal details in a comment since it's available to everyone. But sure, feel free to contact me for discussing your project via Email (you can find the email address on the README page).

Also, thanks for your opinion. I'll be working on the daily view next. When I make some progress, I'll let you know.

@multimedial
Copy link

@aceisace
Thanks for getting back to me. The API key issue has vanished in the meantime, I think the key was not active yet when I started my experiments, I got everything to work now and am already tinkering with the code.

I would like to suggest to make the panel modular. There is a similar project, the magic mirror one (https://magicmirror.builders/) where the content to be displayed can be chosen from a variety of modules.

I will send you an email to your email address.

@aceisace
Copy link
Collaborator Author

@multimedial
Glad to hear your issue was fxed :)
Thank you for the suggestion about the MagicMirror2 project. I am familiar with the MagicMirror and use the software on a 42" LCD display at home. I really like the project, the repo and the modular software of the MagicMirror.

I'm also been thinking that it's about time to make the software modular, but unfortunately, there are still ways to go for me since I'm not too familiar with writing classes and modules just yet.

On the other hand, there is a very passionate forker of this repo who is working hard to make the software modular. You may see the progress to his repo here: https://github.com/mgfcf/E-Paper-Calendar-with-iCal-sync-and-live-weather. Once he's finished implementing the modules of this software, I'll be implementing them on the main repo.

Sure, looking forward forward to your mail.

@aceisace
Copy link
Collaborator Author

aceisace commented Mar 4, 2019 •
edited

@zAm1987
Hi, it's been a while. I've updated the software so that it can display the generated image much better now.
By evaluating each pixel of the generated image before sending it to the E-Paper, it's now possible to give each pixel a value of pure white, pure black (and pure red if using the 3-colour display), hence solving the problem with the 'jagged edges'.
I have tested it myself and have pushed the changes to the main repo. May I ask you to test the updated software and give some feedback regarding the displayed image? Thanks in advance.

Preview of converted images:

From left to right: unprocessed-image, processed-image for bw-display, processed image for bwr-display. For a bigger image, right-click the images and open them in a new tab

@zAm1987
Copy link

zAm1987 commented Mar 5, 2019

@aceisace

You're really putting effort into this project, keep up the good work! ;)

I just used the "update"-method of the installer, modified the settings file again and tried to run E-Paper.py. Somehow it failed, while the old version worked fine with the same settings (albeit the last time I tested it was some weeks ago). Still not working after a reboot, too.

The script output says:

`Fetching events from your calendar

Traceback (most recent call last):
  File "E-Paper.py", line 357, in <module>
    main()
  File "E-Paper.py", line 210, in main
    rule=rrulestr(r_string,dtstart=parse(r_start.group(1)))
AttributeError: 'NoneType' object has no attribute 'group'`

I'll try a fresh install in the next days to see if maybe the updating process mixed something up...

@aceisace
Copy link
Collaborator Author

aceisace commented Mar 5, 2019

@zAm1987
Hi, thanks for your compliment and for testing out the new software :)
Are you, by any chance, using a non-google Calendar? The error you're getting seems to be related to recurring events. As this feature was just recently (a few days ago) implemented, it's possible it might not be working as expected. I'd like to apologise for the inconvience.

In the meanwhile, you can bypass the Error by uncommenting/deleting lines 203-218 and dedenting 219-223 in the E-Paper file so that the section from line 202 (for events in ical.events:) looks like this:

                for events in ical.events:
                    if events.begin.date().month == today.month:
                        if int((events.begin).format('D')) not in events_this_month:
                            events_this_month.append(int((events.begin).format('D')))
                    if today <= events.begin.date() <= time_span:
                        upcoming.append({'date':events.begin.format('YYYY MM DD'), 'event':events.name})

Or, as an easier alternative, you can just use the attached 'E-Paper-mod.py' file, unzip it and replace it with the existing one (in /home/pi/E-Paper.Master/Calendar/). Don't forget to change the name of the file to E-Paper.py.

Attached file:
E-Paper-mod.zip

@aceisace
Copy link
Collaborator Author

@zAm1987
Hi, it seems as though there are some problems with the compatability of the installer on Raspbian Stretch-Lite. The cause is linked to some changed/missing packages that are not present on Stretch. I'll add a note of this behaviour in the README.
In regards to the missing 'Calendar' folder, I'd guess it's related to the recent problem of the Installer on Raspbain Stretch Lite, so this problem will also be fixed when running on Stretch with Desktop.

It will take at least several days to get it fixed and tested, so may I ask you to test the installer on Raspbian Stretch with Desktop?

Thanks in advance.

@ericwass
Copy link

ericwass commented May 14, 2019 via email •
edited by aceisace

@ericwass
Copy link

ericwass commented May 14, 2019 via email •
edited by aceisace

@zAm1987
Copy link

zAm1987 commented May 15, 2019 •
edited

@aceisace
I'll try it with full raspian stretch this afternoon.
Additional information that I hope helps: The last version however runs without problems on raspian stretch lite.

@aceisace
Copy link
Collaborator Author

@zAm1987
Sure, do let me know if it works as expected on Raspbian Stretch with Desktop. Also, thanks for the info regarding the last version. I'll do some more trial-runs to test the installer on Stretch Lite.

@aceisace
Copy link
Collaborator Author

@ericwass
I just re-tested the Agenda-View design using my own google iCalendar URL. It seems to be working fine, from what I see here:

Event: Testing a multi-day event starts on: Sat 18 May 19
Event: Hello World! (Sample Event) starts on: Wed 15 May 19
Event: First Event starts on: Thu 16 May 19
Event: Second Event starts on: Thu 16 May 19
Event: Third Event starts on: Thu 16 May 19
Event: Even more events starts on: Fri 17 May 19
Event: A lot of events starts on: Mon 27 May 19
Event: Test for a very long event name. Awefully long, isn‘t it? starts on: Tue 28 May 19

It did take around 10 seconds to parse these events from my iCalendar so I think that if you have a lot of events, it will take much longer, but it shouldn't be hanging.

Could you try using the 'Calendar' design for the middle section and test if the problem persists?
If it does, please open the E-Paper.py file, and change this section (line 341)

if middle_section is 'Agenda' and events in ical.timeline.included(now, agenda_max_days):
    upcoming.append(events)

to:

if middle_section is 'Agenda' and events in ical.timeline.included(now, agenda_max_days):
    upcoming.append(events)
    print('Event:', events.name, 'starts on:', events.begin.format('ddd D MMM YY', locale=language))

This will automatically print out the parsed events, just like the snippet from above. Do let me know if you see something similar to the output from above. Thanks in advance.

@zAm1987
Copy link

zAm1987 commented May 15, 2019

@aceisace
I tried the installer it with a fresh full raspian stretch and did not used the "upgrade operating system"-option. Now everything went smooth and the displays shows a very nice and crisp agenda view.
My only "critic" is that events (day long, without specific time) which are going on for a few days are only shown on the first day and not the following days, too.

In addition there seem to be a bug with the beginning times. All of my events are shown with a time two hours too early.

And after adding again the second ical-url (the problematic one in the past from my wife) the script stays at "fetching events" like forever (already 20mins of waiting). I'll try reducing the timespan in the settings file and wait another round...

@aceisace
Copy link
Collaborator Author

@zAm1987
Thank you very much for testing the new software. I tried to 'upgrade the operating system' on Raspbian Stretch with Desktop and it seems to be working fine. On the other hand, Lite still has some issues with the Installer.

Thanks for pointing out the bugs. About the multi-day events only showing up on the first day, I've taken a note of this behaviour and will fix it soon enough.

In regards to the beginning (and end ) times of timed events, are you by any chance living in a timezone that is +2 hours from UTC? If yes, that would explain the problem why the shift is exactly 2 hours. In that case, it would mean that the dates of events in an iCalendar are set to UTC by default and need to be 'manually' corrected.

I'm also going to take a look at the reason why certain iCalendar URLs take too much time to get parsed. Since this behaviour has been mentioned by @ericwass as well, could you try following the steps in this comment. The output should be similar, but if it isn't, do let me know.

@ericwass
Copy link

ericwass commented May 15, 2019 via email

@aceisace
Copy link
Collaborator Author

@ericwass @zAm1987
I've found the problem causing the loop to get stuck when fetching events. It seems that ics.py (the package that parses the iCalendar) is still somewhat buggy.

The only change made in the section that parses the events is a new function (from the ics package), which has problems correctly filtering events in a given range. I will take care of this bug by reverting the changes in the iCalendar section.

Once again, thank you very much for all your help and time :)

@ericwass
Copy link

ericwass commented May 15, 2019 via email

@aceisace
Copy link
Collaborator Author

@ericwass
Thank you as well for testing out the software and helping a lot with debugging 💯

@zAm1987
Copy link

zAm1987 commented May 16, 2019

@aceisace
Yes I am living in UTC+2 (Berlin Timezone). But my calendar events are set in UTC+2, too. And the problem did not occur in the last version...or at least hast not caught my attention .

@aceisace
Copy link
Collaborator Author

@zAm1987
I've done some more research on this issue. It seems the ics.py library always sets the start-time of any event to utc, regardless if the timezone is specified in your iCalendar.

The last version also had the same issue, but as you realised, it didn't catch your attention since only the date of events was shown, not the time.

I'm working on a way around this problem by setting the timezone explicitly from the system itself.

@aceisace
Copy link
Collaborator Author

@ericwass @zAm1987
OK, I've managed to fix some of the bugs related to the parsing and handling of events. For now:

  • Events that stretch out over more than 1 day will be displayed corectly now
  • The times of events should be displayed properly now, regardless in which timezone you might be living in.
  • The algorithm to fetch events in a given time was reverted to the one from the last version. As a result, the loop will not get stucked when parsing events.

That being the case, could you please confirm if it also working correctly on your end? Thanks in advance.

@ericwass
Copy link

ericwass commented May 17, 2019 via email •
edited by aceisace

@aceisace
Copy link
Collaborator Author

@ericwass
Sorry for that, I forgot to fix that when selecting 'Calendar' as the middle section and 'Events' as the bottom section. You should still be able to get this working by using 'Agenda' and 'RSS'.

As soon as it's fixed, I'll let you know.

@ericwass
Copy link

ericwass commented May 17, 2019 via email •
edited by aceisace

@aceisace
Copy link
Collaborator Author

@ericwass
Thanks for the info, I'm glad to hear it works. I've implemented the bugfix for 'bottom_section' == 'Events' just now. It should no longer cause any problems.

About the 24 hour/12 hour format, I'm going to work on that now. As soon as it's ready, I'll let you know.

@aceisace
Copy link
Collaborator Author

@ericwass
OK, I finished a bit faster than expected. The support of 12/24 hours in the agenda view has been implemented just now.

@ericwass
Copy link

ericwass commented May 17, 2019 via email •
edited by aceisace

@aceisace
Copy link
Collaborator Author

Just replacing the E-Paper.py file will be sufficient this time, since no other files were changed recently.

@ericwass
Copy link

ericwass commented May 17, 2019 via email

@ericwass
Copy link

ericwass commented May 17, 2019 via email

@aceisace
Copy link
Collaborator Author

You can paste the following commands in the Terminal:
cd /home/pi/Inky-Calendar/Calendar
rm E-Paper.py
wget https://raw.githubusercontent.com/aceisace/Inky-Calendar/Stable/Calendar/E-Paper.py

@aceisace
Copy link
Collaborator Author

Announcement

The E-Paper Calendar software has been updated from v1.5 to v1.6 just recently (Mid May 2019).

It contains a lot of improvements, the most significant ones being the agenda view, multiple languages, and the web-ui (credit to TobyChui). You can see all changes since the previous release in the Changelog.

Due to the new release, this issue will be closed now (since it was specifically for v1.5) and a new issue will be opened for v1.6. For all participants of this issue, thank you very much for all your suggestions, bug-reports, feature requests and critics. See you all in the next issue.

P.S.: If you notice any bugs, please let me know by opening an issue. Thanks in advance.

@aceisace aceisace unpinned this issue May 18, 2019
@aceisace
Copy link
Collaborator Author

@mauricecyril @Clickbaitcake
Just a quick update in case you didn't receive the news. The agenda-view has been implemented in the new release (v1.6). You can test out the new release by updating the software via the installer.

What do you think about the current agenda-view? Thanks in advance.

@aceisace aceisace added the outdated This issue is from a previous release and is most likey not relevant. (Archived) label Apr 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aceisace aceisace

Labels
enhancement New feature or request good first issue Good for newcomers outdated This issue is from a previous release and is most likey not relevant. (Archived)
Projects
No open projects
Release v1.6
  
Issues for the current release (v1.5)
Milestone
No milestone
Development

No branches or pull requests