Nightly builds page redesign (static HTML)

[a1ex]

Added links to more ports in progress (actually "stalled" might be a better word for some of them) on the download page.

http://builds.magiclantern.fm/#ports-in-progress

Also added links to existing ROM dumpers:

http://builds.magiclantern.fm/#rom-dumpers

[Andreasb242]

On the Top of the Page is written:

Main Builds
These builds have been around for some time, and they are unlikely to cause major issues.
In most cases, regressions are fixed quickly - if you report them.

I like this text, and think they are OK.

But the builds here display once a day the Warning message "This is a development snapshot for testing purposes." etc. (menuhelp.c, draw_beta_warning)

In my opinion, this is a inconsistency. I would remove this message from ML.
Or an alternative would be to display the history, if ML is updated (once, not every day), like some Android Apps does, and then the Text: "Please report all bugs at www.magiclantern.fm"

(Or change the nightly build, and defined CONFIG_RELEASE_BUILD?).

I know, it's a little bit offtopic, but I think the message should match the new Download page, even if the page is not that new anymore...

Andreas

[a1ex]

Right, it's a good idea to update the message (maybe use a different one for experimental builds). However, before considering the builds as release, I'd like to:

1) fix the user guide problem;

2) make sure the builds are tested before posting; that was done manually years ago, when the feature set was small and I was working on 1 or 2 camera models; however, this approach no longer works (with hundreds of menu options - if not one thousand - and several modules, workflows, bleeding edge features and so on).

Made some progress for #2 - most of the nightly builds are now tested, to a limited extent, in QEMU.

[a1ex]

Playing around with the presentation of QEMU test results -> http://builds.magiclantern.fm/

Suggestions welcome (maybe you found the old page easier to navigate, or maybe you can suggest better CSS or nicer layout or whatever.)

[ilia3101]

Layout is still fine to navigate, but it's a little confusing: when some builds pass less tests than others, does that mean they failed some?
How would it present failing half and passing half?
Maybe say how many there were in total?

[a1ex]

It's because I'm triggering a few builds manually after adding new tests - they will all auto-update at the next nightly.

Also, some of the tests can only be run on some cameras - for example the silent picture test, because of emulator limitations.

Look at 600D and 1100D for failing half and passing half. Tried something like "1 / 5 failed" but didn't like the result (better idea?). The total is on the tool-tip.

[kichetof]

Design looks good and comprehensive (with tooltip info)
Maybe you could warn users when the build failed tests if it's "dangerous" to play with it (if a test is crucial for install it for exemple, maybe with a ponderation if needed)

About print screen, what do you think to add a gallery inside the build page ? like that or that

[a1ex]

If I'll also compare the screenshots with the previous run, there will be a *lot* of screenshots - and the current tests are just scratching the surface. I'd keep a few important screenshots on the main page, then add an additional page with detailed test reports. For now I'm just linking to Jenkins log, but that's not going to scale with more than 10-20 tests.

For the main page, a gallery could be a little more user-friendly, indeed.

[ilia3101]

Just noticed the tool tip, seems good

[Walter Schulz]

My 2 cents:

Meta data access is intriguing. Want to check which options are available (brain fart developing).

Page layout in https://builds.magiclantern.fm/index.html is useable.
Minor: I do not like use of colours that much. Blue captions for camera builds tend to be overlooked because red and green tags will attract vision first. Should be the other way round: User is looking for the cam in use. Maybe there is way to hide/grey out metadata and only get info if cursor hoovers over the caption/cam area?

Bigger one: Wording.
Most ML users (in my opinion) do not have the slightest idea what QEMU is and don't understand the concept of emulators either. Users have to know there is (at time of writing) a difference running emulations and running ML in cam and why automated tests are useful but not sufficient to avoid software errors (bugs).

Same for "regression". Let's - for simplification - just call it "bug".


Now to cam build page (example 5D Mark II 2.1.2):
Not happy with layout.
There are 5 lines with checkmarks for each test and then a line beneath with a ballot box and a checkmark and then changes and then ...

Suggestions:
- Seperate sections "Test status", "Changes", "Useful links", "Statistics", "Logs"

-"Test status": Make "Test results" to stick out a bit and put single test results somewhere below.

[kichetof]

Suggestions:
- Seperate sections "Test status", "Changes", "Useful links", "Statistics", "Logs"

-"Test status": Make "Test results" to stick out a bit and put single test results somewhere below.

Good Idea ! Maybe with tabs or accordion

I think, it's good to keep links to forum in cam main page (not hidden in tabs/accordion)

[Walter Schulz]

And a "Known Issues" section, please. Minimize further flicker issue duplicates for 6D/70D/700D/EOS M, for example.

[Walter Schulz]

1) fix the user guide problem;

Missed you linked this thread.
I didn't reply there yet because I wanted to wait for Audionut's and your opinions on that.

[a1ex]

Meta data access is intriguing. Want to check which options are available (brain fart developing).

Anything you can think of - data from Bitbucket, from Jenkins, from parsing the source code, or the result of some emulation, or the result of some Lua script running on the camera, or a list with menu entries present in the build, or a list with included modules...

Now to cam build page (example 5D Mark II 2.1.2):
...
Suggestions:
- Seperate sections "Test status", "Changes", "Useful links", "Statistics", "Logs"

Good Idea ! Maybe with tabs or accordion

Better like this?

http://builds.magiclantern.fm/700D-115.html

[Walter Schulz]

I like it!

Cream on top:
- Add link to supported Canon firmware file (pelican's repository) into "Useful Links". Yes, I know it's present in "Installation", too.
- Change order of item 1 and 2 in "Installation".
1. Make sure [...]
2. Format card [...]

[kichetof]

Better like this?

Looks good! To be sure user clicks on accordion, add a chevron in the right of the button, like that
Minor update with the border under the button, add a little margin (8px like padding in alert) in your css:

Code Select Expand


.accordion-inner {
    padding: 9px 15px;
    margin-top: 8px;
    border-top: 1px solid #e5e5e5;
}


- Change order of item 1 and 2 in "Installation".

+1

[a1ex]

Done - should I leave the installation text always visible, or it's better hidden?

[kichetof]

This chapter should be visible when loading (add 'in' class) but is ok to collapse it

Code Select Expand

<div id="collapse-install" class="accordion-body collapse in">
      <div class="accordion-inner">


Maybe adding a button to expand all in one time ?

Code Select Expand

<script type="text/javascript">$(".collapse").collapse("show")</script>
or 'toggle' if you prefer

For QEMU captures, you could add a gallery like on the main page of ML http://www.magiclantern.fm/#carousel with specific image of each cam



5D3 pages (both firmware) has the firmware version repeated twice in the breadcrumb list :  » 5D Mark III 1.1.3 1.1.3



Features page: bad links for both 5D3 firmware, should be: 5D3 113, 5D3 123

[DeafEyeJedi]

Also notice (don't remember if I had already mentioned this already) that copyright section on the bottom of download page still has "Copyright (C) 2009-2014 Magic Lantern Development Team"...



But on the new designed Nightly page it's fine with up to date stuff (2017) and whatnot.

Just not in the Download page.

[Audionut]

Suggestion:  https://builds.magiclantern.fm/experiments.html


Collapse all of the build information to headings, so that you can see all builds when navigating to that page.  Click on heading to un-collapses all of the information for that build.
Linkable headings could be useful also.

[Audionut]

700D firmware link broken.
https://web.archive.org/web/20171210204515/http://pel.hu/down/v115-t5i-700d-x7i-win.zip


I have downloaded Canon firmwares for all of the available ML models. This will be a backup, and contain all the firmwares once uploaded.

Missing:
5D3 1.3.4

[dfort]

Missing:
5D3 1.3.4

I also backed up the Canon firmware updaters. You'll find all of the applicable versions for the 5D3 on my Bitbucket downloads page. Look for the "5D3 Canon Firmware for Testers.zip" package.

[Walter Schulz]

Missing:
5D3 1.3.4

?
Screenshot pel.hu/down:

[a1ex]

Some updates to the installation instructions on the download page, starting from this suggestion:

https://builds.magiclantern.fm/700D-115.html -> click on Installation

Further suggestions welcome (including CSS tweaks, writing improvements, spell/grammar checking, better screenshots and so on).

[Walter Schulz]

We've been naughty, I suppose. Unwanted present: Pel.hu is down, links to outdated firmware no longer working.