After saving your view, it should be an available choice in the list of preset views.
Worth noting however, that the presented list of preset views is dependant on the media types listed.
If you save a view that only lists image files, it will not be presented as a choice if you try to add or load the view to your audio branch.
It's a shame really, because the system should allow us to share view schemes, but this limitation means that the system is really limited to only basic audio, image, video or data schemes. Mix up the media types in any way, and there's no gaurantee everyone will ever see the view in the list of presets.
I think the package installer should deal with jvi file downloads too. It should catch the incoming file and save it in the correct location, likewise, double clicking a jvi file saved locally should invoke the package installer. If the process of importing jvi files could be made easier in this respect, starting a repository of downloadable views might be a viable project.
I say 'might be' because, in my experience, once we move away from the default, stock views as provided by the MC installer, our views tend to become quite personal affairs, containg things like file path restrictions, cutom library field rules, expressions etc. which render them totally non-portable. I still think it would worth a bash if the jvi import process were to be more automated.
-marko.