[PATCH] new function "create and open eml file"

[Matthias]

I have developed a new feature: "Create and open eml file"

My Use case:

- Select revisons in log dialogs.

- Context menu command "create and open eml file"

- an eml file with flag "X-Unsend" is created, it contains all informations and about the selected revisions in the mail body including links (revision links, bug links, url links etc.)

- the eml is opened with shell execute, all common mail clients can open this as unsend mail dialog

- before sending the sending developer can add questions, remarks about the selected revision

- additionally the text with link can be opened as html file

technical implementation:

For the creation of the eml file I did not find a proper library for unnmanaged C++. I used the some functions of the .net framework. The Managed Code code is in a separate projekt "TortoiseManagedCode".

It is called via dll-Exort / dll-Import.

[Matthias]

There is a compile error in this path. I refactored someting before createing it. please do not apply it. I will correct it soon.

[Stefan]

I'm sorry, but something like this is way out of TSVN's scope. It's just a too custom feature.

So I'm not going to apply this patch, sorry.

Stefan

[Matthias]

the corrected path

[Matthias]

I'm a bit suprised about your opinion. Communication about commits and revisions takes place in each developer team. Ergo in each team using TortoiseSvn.

[Matthias]

Would a context menu plugin mechanism be in scope of TortoiseSvn?

[Stefan]

On Sunday, January 24, 2021 at 1:23:14 PM UTC+1 Matthias wrote:

I'm a bit suprised about your opinion. Communication about commits and revisions takes place in each developer team. Ergo in each team using TortoiseSvn.

communication yes, but not via email. Because that means there's no central archive of the communication.

Most teams use issue trackers and messaging boards.

[Matthias]

Ok, thank you for your explantion. I can understand that.
We use issue trackers as well and use it extensively, but not each small question should end up in the issue tracker. But I can understand that this depends on the developping team. For a open source community direct e-mail is not what you want. So the e-Mail use is in fact custom usage.

[Matthias]

So I have two more questions:

If I develop a generic plugin mechanism to extend the menu, is there a chance that you apply this?

If not: Would you give me the permission to create a custom version for our enterprise? I certainly would publish the sources to meet open source license. I definitely not interested in maintaining a proper product site. And I defintely want to avoid to annoy you. I'm graceful for your create work and I think TortoiseSvn is your baby. 

[Stefan]

On Sunday, January 24, 2021 at 2:59:50 PM UTC+1 Matthias wrote:

So I have two more questions:

If I develop a generic plugin mechanism to extend the menu, is there a chance that you apply this?

you mean the context menus of TSVN dialogs? Yes, of course. If it's generic.

 

If not: Would you give me the permission to create a custom version for our enterprise? I certainly would publish the sources to meet open source license. I definitely not interested in maintaining a proper product site. And I defintely want to avoid to annoy you. I'm graceful for your create work and I think TortoiseSvn is your baby. 

You can of course do that if you like. 

Stefan

[Matthias]

Yes, I meant the context menus of TSVN dialog. Im do not know yet if I want to invest the time. If yes I would start with a generic mechanism for the log dialog.

I'll have to think now what i want to do. Thank you for your answers and support.