Issue 0007224 submitted 2008-06-20. Patch was attached to the bug
report. although the name of the patch file is NOT what is really
being patched but the patch is correct.
--
Mike Jackson Senior Research Engineer
Innovative Management & Technology Services
On Aug 14, 2008, at 8:20 AM, Berk Geveci wrote:
Mike,
The easist thing to do would be to submit a patch too. We try to
support Mac well but it is not always on the top of our priority list.
The class that needs changing is pqPluginManager, I believe. Please
keep in mind that the server loads plugins too. The
~/Library/Application Support/... would only work for client side
plugins unless the server is a Mac too.
-berk
On Wed, Aug 13, 2008 at 5:04 PM, Mike Jackson
<[EMAIL PROTECTED]> wrote:
I had hacked into paraview (and submitted a bug/feature request)
to have
Paraview look in more places for plugins. I think I have mine
looking at the
same level as the paraview.app and also in ~/Library/Application
Support/ParaView/Plugins .. or something like that.
This is a good reason for adding those locations. Usually 3rd party
installers should NOT be installing plugins directly into a .app
package
which is what Samuel basically wants to do.
--
Mike Jackson Senior Research Engineer
Innovative Management & Technology Services
On Aug 13, 2008, at 5:28 PM, Samuel Crow wrote:
I think I'll have the Mac version install in the Paraview package
itself
so that the developer releases will automatically scan for them
on startup.
_______________________________________________
ParaView mailing list
[email protected]
http://www.paraview.org/mailman/listinfo/paraview
