[Rwp] OSARA revisiting installation issues

[onlineeagle]

Like the idea of an option to put the keymap in the keymaps folder for manual import, as I have quite a few custom actions. Unless there is a way for me to somehow do something at my end to do the instalation but still import my own actions on top, without having to add them all again manually?

Sent from my iPhone

> On 24 Feb 2016, at 05:00, Chris Belle <cb1963 at sbcglobal.net> wrote:
> 
> That is reasonable enough,
> and yes, having the key map extracted to use in a manual manner would be useful.
> I think that is a good compromise.
> 
> 
>> On 2/23/2016 10:47 PM, James Teh wrote:
>> The only time the installer is ever a problem as far as the dll is concerned is if you previously installed manually. Obviously, the installer can't account for a previous manual installation. If you only ever used the installer (which will be true for anyone who uses it from now on), it's not going to be an issue. I don't think it's unreasonable to expect those who did a manual install to clean up after their own manual install. If they had the knowledge to do the manual install in the first place, they should have the knowledge to clean it up.
>> 
>> Having two distributions creates multiple problems, not least being confusion about which one to use. It's also redundant and means there is yet another piece of the puzzle when trying to track down issues.
>> 
>> The only unanswered issue, then, is the ability to merge key maps. I could probably get around that by having the installer extract the OSARA key map to the REAPER key maps directory so you can import it manually if you wish.
>> 
>> Jamie
>> 
>>> On 24/02/2016 2:39 PM, Chris Belle wrote:
>>> Well, if it's still for consideration at all, I vote to have a manual zip file method available for manual installs,
>>> like the JSonar project did,
>>> this makes it easier to update rather than replace keymaps,
>>> and the process of cleaning up and putting the dll in a place rather than have an install do it makes it less likely
>>> to mess up and get it in two places.
>>> Unless there are issues I'm not aware of,
>>> for future growth, things like registry entries, or other dlls
>>> etc, then this seems so simple and straight forward to me.
>>> I only have a few custom actions now, and I can work around this, exporting my
>>> actions, and re-importing them,
>>> but when the list grows it will get to be a longer process.
>>> and having only the options to leave it alone or replace it totally is not as good as being able to just import the keymap old school yes I am aware there can be conflicts,
>>> but this gives me the maximum flexibility to keep my actions and get the new ones with out having to play ring around with files
>>> and such.
>>> Thank you for all your hard work,
>>> 
>>> 
>>> 
>>>> On 2/23/2016 2:46 PM, James Teh wrote:
>>>> My care factor is 0 for the following reasons:
>>>> 1. I specifically posted about removing these files on this list. Given OSARA's pre-release status (which I've been very clear about), I'd expect users to be watching for messages like this before they try things.
>>>> 2 Anyone who installed OSARA the manual way already declared a certain degree of tech saviness and willingness to play with such things.
>>>> 3. In the readme, I previously documented that users should copy to userPlugins.
>>>> 
>>>> Sent from a mobile device
>>>> 
>>>>> On 24 Feb 2016, at 4:11 AM, Chris Belle <cb1963 at sbcglobal.net> wrote:
>>>>> 
>>>>> Hey Jamie?
>>>>> Since you went to the trouble of making an install and also fixing up a portable support,
>>>>> we have a possible snag.
>>>>> Normally we always just dumped the osara plug in to the plugins dir.
>>>>> Now you changed that to
>>>>> UserPlugins
>>>>> but what happens is that if the user doesn't delete the original osara plug out of the plugins dir, then it takes authority and the new installed plug doesn't work.
>>>>> So do we fix it so this doesn't happen, or just warnn everyone to make sure to clean up before running the install?
>>>>> because I can see this tripping up newbies big time.
>>>>> Maybe not, because someone running a portable install will probably be clued up with paths and such, but just saying for the record, so we don't end up with an old plug put in the normal manner stsopping the show.
>>>>> What you think?
>>>>> 
>>>>> _______________________________________________
>>>>> RWP mailing list
>>>>> RWP at bluegrasspals.com
>>>>> http://bluegrasspals.com/mailman/listinfo/rwp
>>>> _______________________________________________
>>>> RWP mailing list
>>>> RWP at bluegrasspals.com
>>>> http://bluegrasspals.com/mailman/listinfo/rwp
>>> 
>>> _______________________________________________
>>> RWP mailing list
>>> RWP at bluegrasspals.com
>>> http://bluegrasspals.com/mailman/listinfo/rwp
> 
> _______________________________________________
> RWP mailing list
> RWP at bluegrasspals.com
> http://bluegrasspals.com/mailman/listinfo/rwp