<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
<style>
div.markdown { white-space: normal; }
blockquote { margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #136BCE; color: #136BCE; }
blockquote blockquote { border-left-color: #4B89CF; color: #4B89CF; }
pre { margin-left: 15px; margin-right: 15px; padding: 5px; border: thin solid gray; overflow: auto; background-color: #E4E4E4; }
</style>
</head>
<body>
<div class="markdown">
<p dir="auto">Benny wrote:</p>
<blockquote>
<blockquote>
<p dir="auto">Is there a keybinding that will make MailMate open a new viewer window? I want to use it as part of a compound binding, for example:</p>
<blockquote>
<pre><code>"?" = "newMessagesViewerWindow:", "searchAllMessages:" );
</code></pre>
</blockquote>
</blockquote>
<p dir="auto">I believe this should work:</p>
<p dir="auto">"s" = ( "newMessagesViewerWindow:", "searchAllMessages:" );<br>
(But the layout is going to be the default layout.)</p>
</blockquote>
<p dir="auto">It works like a champ, Benny. Thanks... I'll put it in my reference file that I'm building.</p>
<p dir="auto">I swear to god that I did a lot of googling and could not find that keybinding. Thanks for sharing. </p>
<p dir="auto">In another message, Benny writes:</p>
<blockquote>
<blockquote>
<p dir="auto">For myself, my priorities would be:</p>
<blockquote>
<p dir="auto">$30 - "makeNewViewerWindow:" binding that could be used in compound key bindings.</p>
</blockquote>
<p dir="auto">I've answered this in another email although it might not be exactly what you were looking for.</p>
<blockquote>
<p dir="auto">$10 - "recenterLine:" to recenter the currently viewed message in a message list binding (works in normal Cocoa programs).</p>
</blockquote>
</blockquote>
<p dir="auto">Late April I added this:</p>
<p dir="auto">New: Added centerSelectionInVisibleArea: for the mailbox/message lists (bound to ⌃L by default).<br>
This did not do what you were looking for?</p>
</blockquote>
<p dir="auto">Hmmm. I hadn't tried it yet. My bad. Again, works like a champ. </p>
<blockquote>
<blockquote>
<p dir="auto">$50 - Programmatic way to access messages (and message components such as Subject, Body, etc) using some API. Either Applescript (via the performCommand binding) or whatever. This would allow me to duplicate some of my workflows from Mail.app</p>
</blockquote>
<p dir="auto">It's possible to create a custom bundle command which can then be triggered using the perform AppleScript command, but I know that it would also be useful if there was more direct access via AppleScript -- especially when adapting existing scripts. I'll give it some more thought.</p>
</blockquote>
<p dir="auto">Yes, I saw that with my "OpenInOutlook" hacked bundle that I slammed together. Thanks for your guidance on that (especially the part about how you do the UUID :-) </p>
<p dir="auto">I'll clean up the script and release it to the mailing list in case there are others who use MailMate along with Microsoft's Outlook for calendaring. The bundle command that I added allows me to press Shfit-Ctrl-O to open up the corresponding message in Outlook so that I can a) see the date/time of the appointment, b) what events are around it, c) comment back to the meeting request, etc.</p>
<blockquote>
<blockquote>
<p dir="auto">The bounties shouldn't be the only factor that Benny should use. I would hate to see MM evolve into a purely "bourgeois" model where those with the most amount of money get a voice in feature requests.</p>
</blockquote>
<p dir="auto">I assure you that if I was motivated only by money then MailMate simply wouldn't exist :)</p>
</blockquote>
<p dir="auto">Oh, I don't doubt that at all. I can see it's a labor of love -- producing an elegant, powerful and extensible powerful tool that is leveraged by power-users.</p>
<p dir="auto">In another email to Kee Hinckley, Benny wrote:</p>
<blockquote>
<blockquote>
<p dir="auto">It's nice if people are willing to pay for a specific feature, but I cannot really make a living of that. The price of a feature would have to be more than most people would be able to pay. I also see a myriad of other potential problems :-) I'm probably also getting closer to a point where fixing/improving existing features is going to be more important than adding new (major) features. This is an important subject though (for me) since the lack of major new features are going to make it hard to do 3.0, 4.0, 5.0 feature releases — and 2.0 is free for all 1.x license key owners (at least those bought after October, 2013). I've already proven that I'm not very good at bumping version numbers :) Essentially, license keys bought by new users are currently the only potential revenue (except when users do like you have done). I'm considering how to best move forward, but let me just assure existing users that I have no plans to stop developing MailMate.</p>
</blockquote>
</blockquote>
<p dir="auto">Music to all of our ears! </p>
<p dir="auto">I just bought an additional license of MailMate, as well. Please take a friend out to Ruby and have a drink on me. </p>
<p dir="auto">Thanks to Kee Hinckley for the idea and example. </p>
<p dir="auto">Cheers,<br>
-Mike</p>
</div>
</body>
</html>