Thanks for the explanation Jason, and I completely appreciate the sentiment!! I agree software developers are often underappreciated, especially OSS. Are there any ways that we, as a community, can help push this along? I didn’t realize there was a preview to this feature yet so I guess I’ll try that next and provide some feedback but I just wanted to ask if there might be some other way we can help. For this reason, I am stuck unable to accept calendar invites that are sent to any address outside of won’t go into any more details but basically I’m desperately looking for a good replacement. Up until now Thunderbird has been great with the third party Google Provider for TB extension, but the latest version broke calendar invites through email and introduced a bug where dismissing notifications removes all invited parties. Evolution is bloated and not a great solution for anyone not using Gnome. I think the need for a combination email and calendar system on Linux has become more urgent recently.
#MAILSPRING GITHUB FREE#
That will free up Ben to implement these larger features, such as the Calendar. If you’d like to help things along, consider helping us fix some of the bugs, especially urgent ones. There is nothing about Mailspring that is simple and easy. I can determine the most urgent bugs and highest demand features, with an eye towards the actual development effort involved.Īll that to say, patience - yes, even years of it - is more than warranted. That’s why I was brought on as the Volunteer Community Manager. Software development is time-intensive at best, and Mailspring is a particularly complicated project. Over the last couple of years especially, the sheer mass of the issue list on GitHub - much of which consists of questions, minor edge-case bugs, duplicate issues, and wishlist feature requests - has made it difficult to find and focus efforts on the most urgent bugs and features, especially given limited development time. Historically, Mailspring has just one developer ( who works on this project in addition to a full-time job.
(There’s even another feature slated for this year that has been more in-demand than the Calendar, so that has to come first!) That’s been the case for some time as you can imagine, the stability and usability of existing features is more important than adding new features.
In the future, Mailspring may automatically disable packages when their React components throw exceptions.I say “hopefully” because there are a lot of major bugfixes and stability upgrades that have to be done this year, and that may potentially push back the Calendar. Instead of your component triggering a React Invariant exception in the application, an exception notice will be rendered in place of the unsafe component. On other platforms, you might subclass, they will be wrapped in a component that prevents exceptions in their React render and lifecycle methods from impacting your component. Keep in mind that React's Component model is based on composition rather than inheritance. To use a standard component, require it from nylas-component-kit and use it in your component's render method. Wrapping standard components makes it easy to build rich interfaces that are consistent with the rest of the Mailspring platform. Many of the standard components listen for key events, include considerations for different platforms, and have extensive CSS. Mailspring provides a set of core React components you can use in your packages. Using React's JSX syntax is optional, but both JSX and CJSX (CoffeeScript) are available.įor a quick introduction to React, take a look at Facebook's Getting Started with React. Packages that want to extend the Mailspring interface should use React. Mailspring uses React to create a fast, responsive UI.