some proposals about blenderupdater HOT 7 CLOSED

Hey Simeon!
Thanks for the input! BlenderUpdater had a "one-click" feature a while ago, but I've removed it since (it wasn't really reliable).
Actually, I like your non-GUI way and think it would be nice to run the BlenderUpdater.exe with a flag such as --update, and then it will skip the GUI part, and just get the latest version of the OS and architecture as you did last time via the GUI, and also use the path entered in the last "full" execution.
So you could add "blenderupdater.exe --update" into your autostart.

Same applies for the 2.8 part - I'm thinking about a way to have easier 2.79 and 2.8 support. That could then be a separate flag (e.g. --28 or --279) for the .exe. Thinking about a sensible way to implement - and waiting for a few hours to implement it as soon as possible!

Thanks & cheers,
Tobi

from blenderupdater.

I do like the idea of filtering per architecture, but I'm unsure about the stable version. The original purpose of the script was to update the nightlies without much hassle, but I don't know if it's gonna be of much help to update the stable release every few months...

from blenderupdater.

I've got filtering per architecture running on my branch and it saves some searching. I'm sure it could've been implemented way cleaner (and with less string compares), but it does the job.
The only feature I could think of that might be beneficial to Blender Updater without breaking the time to develop / time it saves ratio would be something like "click to wipe all data associated with that version" (user prefs, HDRIs, Startup files, workspaces etc)

from blenderupdater.

That's actually a good idea. I'd have to look into what files need to be cleaned up first - thanks for the input!

from blenderupdater.

Oh, can you send a PR for your version, so I can add the architecture filtering back to my branch?

from blenderupdater.

hey tobias, here's my proposal:

Current flow is this:

• doubleclick exe
  (- confirm windows security check)
• choose path
• click version check
• choose version
• restart and repeat all steps to get another version

Maybe it's possible to create rules:
OS + architecture + version + path + autostart checkbox + closeOnFinish checkbox

In my case I'd create my update rule: Windows -> 64bit -> Version 2.8 -> C:...\Desktop\blender2.8_nightly -> autostart/closeOnFinish on. The result would be: I could create a shortcut to windows autostart -> every day after booting my pc, blender would be up to date. Yeah! No click needed!

Also if you don't want to automate to much (autostart off), behind every rule there could be the update button as one click solution.

Than I also could create a second rule for 2.79 - same pc. Because I like working with the current build but also testing 2.8.

Don't understand me wrong: love this tool so far, but these feature request came to my mind.

best regards
Simeon

from blenderupdater.

@noemis84 - I decided to write an additional script for the use-case you described. This removes the overhead of all the GUI dependencies when only using the command line.
See here: BlenderUpdaterCLI
You can create a .bat file to put it into Autostart, providing the needed flags.

No thorough error checking so far. Still a bit WIP, but it works so far. Let me know if you find any issues :) Tested on Windows only so far, but it should work on Linux and OSX as well.

Cheers,
-T

from blenderupdater.