I have spent some time thinking about this, so this is going to seem more
like a dump of information than any one singular point.

What I'm alluding to here with regards to licensing is that for 1.3 we're
going to put Growl into the mac app store. Part of the problem with
licensing is that you just can't do that with GPL and LGPL code. Growl is
BSD so we're luckily able to avoid the licensing problems that the others
are running into.

Your plugin looks good from just the screenshot as a means to an end. I
haven't really looked at the code yet since I really am concerned about
looking at it and then not being able to include it. I think it'd be a great
benefit to our users who tend to use the MailMe display.

In the end we want to split Visual displays from Action displays so that you
can fire 1 or more action type displays, like this one, along with a Visual
display based on the Applications tab. While MailMe is far from what you
have here, it certainly does have a somewhat easier time with regards to
configuration, so to speak. So I think being able to use either the MailMe
or your way of doing things is valid. However, I don't foresee many people
needing both, just one or the other if that makes any sense.

So, there are multiple things to do here before this can be included in
Growl proper:

1) Licensing adjustments. If this cannot be resolved, then the plugin will
need to remain external from the project. If that's the case I would like to
link to it from somewhere.
2) Replicate MailMe in this plugin, figure out a way to make it easy for the
end user to select and understand.
3) Code review.
4) UI review
5) Inclusion in Growl

I realize this may seem like a lot, but at the same time I think it'd be a
beneficial process for all of us (you, us, etc etc) if we can work through
it all. I'll understand if you choose to not go down this path. However I
believe that if you work towards this goal that there is a lot of benefit to
everyone involved.

Chris

On Fri, Jun 17, 2011 at 4:05 PM, Alessandro Volz
<[email protected]>wrote:

> Ok,
>
> - I'm switching to .m files
> - I'll try and read SMTP account data from Mail.app, and allow users to
> "Use a Mail.app SMTP account". This will fill the "SMTP Server" fields in
> the plugin pref pane with the selected Mail.app account information.
>
> Nitrogen is a lib where I put useful stuff I may need in other projects...
>     - Connectivity stuff: XMLRPC impl, an NSStream wrapper, a listener
> wrapper
>     - GUI stuff
>     - Categories on base classes, like:
>
> @interface NSException (N2)
>
> -(NSString*)stackTrace;
> -(NSString*)printStackTrace;
>
> @end
>
> @interface NSFileManager (N2)
>
> -(NSString*)findSystemFolderOfType:(int)folderType forDomain:(int)domain;
> -(NSString*)userApplicationSupportFolderForApp;
> -(NSString*)tmpFilePathInDir:(NSString*)dirPath;
> -(NSString*)tmpFilePathInTmp;
> ...
>
> In the plugin I'm using just a couple of these classes.
> But changing these to .m would be more annoying than the plugin files...
>
> Cheers,
> Alessandro
>
>
> On Jun 16, 2011, at 1:53 AM, Christopher Forsythe wrote:
>
>
>
> On Wed, Jun 15, 2011 at 6:35 PM, Josh <[email protected]> wrote:
>
>>
>> On 15 Jun 2011, at 23:43, Peter Hosey wrote:
>>
>> > On Jun 15, 2011, at 15:11:29, Christopher Forsythe wrote:
>> >> If we can resolve a few items, and get some code review, I don't see a
>> problem with using this.
>> >>
>> >> Perhaps integrating mailme's functionality (using mail.app accounts
>> instead of having to configure this yet again) could be a cool option if
>> it's not there already.
>> >
>> > I'd favor a merger of their functionalities: Default to Mail.app's
>> settings, but enable changing the configuration if appropriate.
>> >
>> > Perhaps a radio button group, currently with two options: “Mail settings
>> ([address it would be sending from])” and “Custom”. Anyone who wants support
>> for borrowing Thunderbird's or Sparrow's settings could contribute a patch.
>>
>> surely if possible a 'select Mail account to send messages from' (+ or
>> custom)?
>> then users aren't stuck with only the first account from mail as they are
>> now.
>>
>>
>>
>
> Ya, maybe.
>
> Regardless, we've got enough work for 1.3 already. Let's look at this after
> 1.3 is out.
>
> Chris
>
> --
> You received this message because you are subscribed to the Google Groups
> "Growl Discuss" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/growldiscuss?hl=en.
>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Growl Discuss" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/growldiscuss?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Growl Discuss" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/growldiscuss?hl=en.

Reply via email to