brewtarget-devs team mailing list archive

[Philip Lee <rocketman768@xxxxxxxxx>]

Good idea. Yes, I know you can run scripts with the NSIS installer. Check
into that and let me know if it looks good or bad.


On Sat, Aug 24, 2013 at 1:53 PM, mik firestone <mikfire@xxxxxxxxx> wrote:

> I think it may be too late by that point, but I will look into it. My
> other thought is maybe we can do something with the installer? If we could
> move these dialogs into that, all the problems go away. It would also allow
> us to keep the very specific windows stuff isolated.
>
> I guess I'll start researching if that can be done and how to do it if it
> can.
>
> Mik
> On Aug 24, 2013 2:18 PM, "Philip Lee" <rocketman768@xxxxxxxxx> wrote:
>
>> This is not exactly pretty, but can we start the event loop and, instead
>> of bringing up the MainWindow directly, bring up some little upgrade dialog
>> that starts the main window when it exits?
>>
>>
>> On Sat, Aug 24, 2013 at 12:01 PM, mik firestone <mikfire@xxxxxxxxx>wrote:
>>
>>> For this release, yes. After this release, that information will be
>>> available in the registry and we can skip the prompt and file browser.
>>>
>>> Mik
>>> On Aug 24, 2013 12:49 PM, "Philip Lee" <rocketman768@xxxxxxxxx> wrote:
>>>
>>>> Is this the (ideal) process for upgrading on windows?
>>>>
>>>> 1) Ask user where old installation is.
>>>> 2) Copy old database into new installation.
>>>> 3) Start up as normal and all the migrations happen.
>>>>
>>>>
>>>> On Wed, Aug 21, 2013 at 9:22 PM, mik firestone <mikfire@xxxxxxxxx>wrote:
>>>>
>>>>> I'm slowly working on getting the Windows upgrades working the way I
>>>>> expected them to work. I actually have the v1.2.x databases being properly
>>>>> upgraded.
>>>>>
>>>>> The v2.0.x databases are proving to be more challenging, for all that
>>>>> the operations are theoretically easier. In short, I cannot figure out how
>>>>> to copy the old database into place. For a lot of reasons (most of them
>>>>> involving prompts, file browsers, etc.), I cannot do this until the
>>>>> MainWindow is instantiated and qApp->exec() is called. It seems mucking
>>>>> with the database file after MainWindow has been instantiated causes a core
>>>>> dump.
>>>>>
>>>>> Does anybody have a clever idea on how to do this?
>>>>>
>>>>> Mik
>>>>>
>>>>> --
>>>>> In a world of ninja v. pirate, I pilot a Gundam
>>>>>
>>>>> --
>>>>> Mailing list: https://launchpad.net/~brewtarget-devs
>>>>> Post to     : brewtarget-devs@xxxxxxxxxxxxxxxxxxx
>>>>> Unsubscribe : https://launchpad.net/~brewtarget-devs
>>>>> More help   : https://help.launchpad.net/ListHelp
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Philip G. Lee
>>>> rocketman768@xxxxxxxxx
>>>>
>>>> --
>>>> Mailing list: https://launchpad.net/~brewtarget-devs
>>>> Post to     : brewtarget-devs@xxxxxxxxxxxxxxxxxxx
>>>> Unsubscribe : https://launchpad.net/~brewtarget-devs
>>>> More help   : https://help.launchpad.net/ListHelp
>>>>
>>>>
>>
>>
>> --
>> Philip G. Lee
>> rocketman768@xxxxxxxxx
>>
>> --
>> Mailing list: https://launchpad.net/~brewtarget-devs
>> Post to     : brewtarget-devs@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~brewtarget-devs
>> More help   : https://help.launchpad.net/ListHelp
>>
>>


-- 
Philip G. Lee
rocketman768@xxxxxxxxx