<feed xmlns='http://www.w3.org/2005/Atom'>
<title>aerc/models, branch mdps1</title>
<subtitle>Mirror of https://git.sr.ht/~sircmpwn/aerc
</subtitle>
<link rel='alternate' type='text/html' href='https://git.benburwell.com/mirrors/aerc/'/>
<entry>
<title>Factor UI models out of the worker message package</title>
<updated>2019-07-05T02:37:29+00:00</updated>
<author>
<name>Ben Burwell</name>
<email>ben@benburwell.com</email>
</author>
<published>2019-07-05T02:34:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.benburwell.com/mirrors/aerc/commit/?id=b46b497f99d7f4dcba8936ce0ebfe8cf982cec1f'/>
<id>b46b497f99d7f4dcba8936ce0ebfe8cf982cec1f</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>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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.
</pre>
</div>
</content>
</entry>
<entry>
<title>Factor UI models out of the worker message package</title>
<updated>2019-07-05T02:03:04+00:00</updated>
<author>
<name>Ben Burwell</name>
<email>ben@benburwell.com</email>
</author>
<published>2019-07-03T20:10:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.benburwell.com/mirrors/aerc/commit/?id=91529df0fecc68d5b0fdbb682529ee545884e7c5'/>
<id>91529df0fecc68d5b0fdbb682529ee545884e7c5</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>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
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.
</pre>
</div>
</content>
</entry>
</feed>
