<feed xmlns='http://www.w3.org/2005/Atom'>
<title>aerc/models, branch 0.3.0</title>
<subtitle>mirror of ~rjarry's aerc fork - a pretty good email client
</subtitle>
<id>https://git.tilde.institute/akspecs/aerc/atom?h=0.3.0</id>
<link rel='self' href='https://git.tilde.institute/akspecs/aerc/atom?h=0.3.0'/>
<link rel='alternate' type='text/html' href='https://git.tilde.institute/akspecs/aerc/'/>
<updated>2019-07-08T20:06:28Z</updated>
<entry>
<title>Factor IMAP-specific structs out of UI models</title>
<updated>2019-07-08T20:06:28Z</updated>
<author>
<name>Ben Burwell</name>
<email>ben@benburwell.com</email>
</author>
<published>2019-07-08T02:43:58Z</published>
<link rel='alternate' type='text/html' href='https://git.tilde.institute/akspecs/aerc/commit/?id=c610c3cd9dd47c400e52c1858e987f5f32a7a45b'/>
<id>urn:sha1:c610c3cd9dd47c400e52c1858e987f5f32a7a45b</id>
<content type='text'>
Before, we were using several IMAP-specific concepts to represent
information being displayed in the UI. Factor these structures out of
the IMAP package to make it easier for other backends to provide the
required information.
</content>
</entry>
<entry>
<title>Factor UI models out of the worker message package</title>
<updated>2019-07-08T20:06:23Z</updated>
<author>
<name>Ben Burwell</name>
<email>ben@benburwell.com</email>
</author>
<published>2019-07-08T02:43:56Z</published>
<link rel='alternate' type='text/html' href='https://git.tilde.institute/akspecs/aerc/commit/?id=cce7cb48081ca090ac2d3a0e781dfbc25d581946'/>
<id>urn:sha1:cce7cb48081ca090ac2d3a0e781dfbc25d581946</id>
<content type='text'>
Before, the information needed to display different parts of the UI was
tightly coupled to the specific messages being sent back and forth to
the backend worker. Separating out a models package allows us to be more
specific about exactly what a backend is able to and required to
provide for the UI.
</content>
</entry>
</feed>
