Verify should not download firmware about particle-dev HOT 7 CLOSED

To remove it we would have to add another step:
Verify -> Download binary -> Flash
We could move downloading it to Flash to keep it simple but then there wouldn't be a way to download binary and use DFU.

IMO current workflow works but we can change it if annoys more users.

from particle-dev.

Maybe we can hide it for users a bit. Download the binary when verifying, but keep the last several (or maybe just one) in tmp storage. Somehow in the UI give users a "get last firmware binary" option. Just a suggestion. Any thoughts @jenesaisdiq?

from particle-dev.

In the Web IDE, there is no idea of LOCAL to the user really... Local in that sense is the Server's HDD. I'm guessing the server DOES actually download or create a binary and store it after Verify. That way if a user presses Flash without changing the code, the server just takes the already created binary and flashes it, instead of duplicating the load on the server and recompiling when flashing.

When you compile this code first via Verify in Spark Dev, and then likely you are re-uploading the code through the Spark-CLI in the background again when you Flash... if I'm correct about the Server, then it just takes the stored binary and uses that for Flashing.

The problem I see with saving a binary in the user's directory for every Verify is that it quickly becomes annoying when you have a bunch of files that have to delete manually. I like the idea of saving a temporary file, but this seems like not a very fun thing to manage with Spark Dev. I also like the idea of only saving the latest generated binary.

Another thought, perhaps there should be a Clean project button/command that removes all build artifacts (in this case, just the binaries).

BTW: I would love it if F6 on the DFU-Util Package would compile and download. However, since flashing OTA is so fast now, I've just been doing that lately and it works hands free with just a few more seconds of time.

An issue somewhat related to all of this:
#28

from particle-dev.

Hopefully this shows how fast things can build up in 30 minutes of development

from particle-dev.

Good grief man! If I see two bins, OCD kicks in and I have to delete them :)

from particle-dev.

How about we remove old firmware when newer is available so there's only one .bin file which is always the latest one and allow user to disable removing binaries in settings?

Pros:

• doesn't add another command
• works with DFU util
• doesn't create infinite number of .bin files
• no additional steps for the user

Cons:

• user who wants to have all firmware files has to go to settings and disable this behaviour manually

@technobly when we'll create our own dfu-util package it will be able to trigger compiling. For now I use Cmd+R / F6 combo

from particle-dev.

Sounds good ^

Also I have been using CMD+R / F6 but also have to click on the project tree window before CMD+R works.

from particle-dev.