rusefi.com

My suggestion is when you click on the photo it downloads the rusefi_bundle file. When you click on "Click here to see what's new!" it brings up some info about the changes that have been made.

Just see what you think guys and say if it's possible to do?

Sexy...
Perfect idea ...

Thank you for the artwork!

See https://rusefi.com//wiki/index.php?title=Main_Page
See https://github.com/rusefi/rusefi/commit/7afb09d3537d4b4f60508f22526372c39380b68b

Changelog link added to the left bar.

Hopefully these improvements are a good balance between efforts (have to minimize the efforts) and the results

I should check, but does the firmware number include the revision date? AKA quick check of the date tells you if you are outdated, and by how long you are outdated.

Once you download the folder name insize the zip file gives you the date.

Without downloaing you can see the date on https://rusefi.com//build_server/ but I am not aware of a trivial way to embed this file timestamp into the main page in an automated manner.

a simple inline php or cgi sniplet) (but I don't know it. need to google)
do not remember exactly, but there might be an ussue when several versions being released the same day. you've finally included the version number, haven't you?
Personally I don't see much use of this 'usability' improvement: those who get interested in the code just head to github (that's the way I used to learn about new updates to the code). But if people download the code, they might first start asking lots of silly questions before they understand that this code doesn't suit them.

Personally I don't see much use of this 'usability' improvement: those who get interested in the code just head to github (that's the way I used to learn about new updates to the code).

Yes that's true, but it doesn't make the wiki very user friendly. I don't think that all the users are interested in coding. I remember how much time I had to spend to grasp all the needed info...

But if people download the code, they might first start asking lots of silly questions before they understand that this code doesn't suit them.

To prevent people asking silly questions we should make some more clear manuals/instructions - easy to follow. (One day I'll start doing something towards this)

For now there is lots of information split into small pieces and located in different places.
There are many cars, and every car has different valves, connectors, sensors but the general idea of each engine is the same... the problem is there is not much clear info about it on the wiki. By clarifying these simple things, there should be less silly questions on the forum.

Having an easy access to the latest files is not a bad thing. Now to download the new bundle I just type rusefi.com and click the DOWNLOAD button. It would be nice to have the date on the front, so you could easily tell that there is something new to play with

Before I kept forgetting if the bundle was in the "Hard U Manual - wiki" or "Soft U Manual - wiki" I know... haha it's just me...
...I'm just trying to think of anything that could help to improve things for the forum members and other people.

RadMx5 wrote:It would be nice to have the date on the front, so you could easily tell that there is something new to play with

I agree - it's just that I do not know how to do it in 15 minutes and I do not have 3 hours to find a solution

We've made at least some progress with the new image and link

okay, sharing my experience. N.B. I am not a system administrator and I am not a programmer, I just know there are some shell scripts, and I know how to google.
There were days in the past, when the bundle was updated several times a day. More often though, at least once a few days. To update the firmware I had to download the firmware, unzip it, launch the terminal and type few commands (with some tricky syntax). Then I had to do the same with java console (which also needed some terminal command to launch, osx weidness). To save some time, I spent probably half an hour to build that shell script, which checked the date and time the bundle was created on the server, displayed the time of my locally downloaded bundle, download the newer once if necessary (I had to type 'y' or 'n'), and flash the firmware. But that was appropriate a year or two ago. These days I am not sure this aproach is relevant.