Menu{Master,Maestro,etc} question(s)

[Fairlight]

>From inside the gravity well of a singularity, Del shouted:
> However, none of my customer's were concerned enough about it to pay for 
> a conversion, so the idea was never fully implemented.                   

Point one.

> But I still think the idea of replacing menu maestro (menu master) with
> a native filePro front end to read the same scripts is the way to go to
> achieve portability with our existing systems, because we have literally
> hundreds of menu maestro menus and converting them to filePro menus would
> be even more work than writing an interpreter.

Point two.

And the two points are mutually exclusive unless you know of someone
with lots of time to kill that doesn't mind busting their hump for
disproportionate returns.

This comes up often enough that people would either realise it -isn't-
worth it and drop it, or realise it -is- worth it and actually just do it.
I must have dealt with people both publicly and privately over half a dozen
times in the last year alone looking for a solution.  Bottom line is that
nobody wants to pay enough to have it done to make it worth doing.  And
numerous people have said so.

It's either worth it, or it's not.  So unless someone decides to haul off
and open source a solution they develop for themselves that does the whole
nine yards, it's going to likely continue to be, "Show me the money."
Which, to date, nobody has done to anyone--or the problem would have been
solved within the last few years.

I think (not for the first time) I just took three paragraphs to say two
words:  Dead Horse.

mark->