Jenkins is overloading the server too much for my taste lately, so I'm considering rewriting the nightly builds page as static HTML, without any JavaScript. Another reason for the rewrite: the builds page is impossible to load on slow network connections.
Any volunteers to help me with this task? I'm going to use a Python script similar to this one (https://bitbucket.org/hudson/magic-lantern/src/tip/features/), and here's what I came up with so far (edited manually, based on the previous template):
http://builds.magiclantern.fm/550D.html
Here's a proof of concept Python code to retrieve Jenkins build data, using JenkinsAPI (http://pythonhosted.org/jenkinsapi/):
from jenkinsapi.jenkins import Jenkins
J = Jenkins('http://builds.magiclantern.fm/jenkins')
B = J['500D.111'].get_last_good_build()
artifact = list(B.get_artifacts())[0]
print artifact.url
Feedback is also welcome (while I'm at it). There's some extra functionality I'd like to add, too.
Any idea how long the nightly server will be down? I just bought 600D and want to instal. If it's going to be a while I'll try and figure out how to compile but otherwise I can just wait. Thanks!
No idea, it all depends on the volunteers. The previous configuration can no longer be used because of a hardware issue on the server, unfortunately.
Hi, I went to the download page today to download the latest version of ML for the 60D and found that the download site is down. I had a previous version on my card a while ago, but since then my wife has formatted my card and I lost magic lantern. I haven't really needed it so I didn't worry about it, but I'm filming a wedding this weekend and needed to put it back on. I might be able to go back and search my computer for the old magic lantern, but it was literally over a year ago that I had it on. I don't know how the download site works, but is there any way someone could send me or put on dropbox or some other download site the latest stable or nightly of ML for the 60D? I would greatly appreciate it. Thanks.
> Any volunteers to help me with this task?
I help you a1ex.
A minute ago I was able to download ML for 60d from https://builds.magiclantern.fm/jenkins/.
I would recommend running jenkins just once every 24 hours or something to that effect. Or if the repo has webhooks (like github does) then you can have it fire a rebuild request to your build server whenever new code is merged. From there, you could do something as simple as letting your webserver list directory contents of a build folder. You can do this with apache or nginx. If you wanted a better interface than that, I'd be happy to volunteer for that. I have a platform that I use called Lightning for dynamic content. It's an extremely lightweight CMS built for speed and high volume requests. It can even run without a database, although even with it, you can handle plenty of requests. If you want to talk about it send me a PM.
Is a service like Dropbox a possibility?
A1ex, I've got a simple Python script running now, that reads a generic template file, takes the URL of the latest nightly build from Jenkins and write everything into a new HTML file. I could not manage to read anything else (e.g. build time, changeset hash or the number of downloads) from the Jenkins instance so far. I need to understand the Python JenkinsAPI better if it's even possible. To bad currently Jenkins is not reachable here. So I couldn't test out things.
https://bitbucket.org/tecgen/magic-lantern/branch/nightly-builds-page-redesign-static-html#diff
> There's some extra functionality I'd like to add, too.
Could you tell me what you like to add in future?
Do you plan to use one Python script that generates multiple HTML file or do you need to call it with parameters for each camera model?
Quote from: macdabby on September 21, 2016, 07:32:43 PM
I would recommend running jenkins just once every 24 hours or something to that effect.
Yes, that's my plan. The download links appear to require Jenkins running though, but this should be fixable.
Before Jenkins, we had some directory listing (h5ai) and a cron job that ran daily. It did the job well, but a nicer interface is tempting as well.
Quote from: tecgen on September 21, 2016, 09:24:38 PM
A1ex, I've got a simple Python script running now, that reads a generic template file, takes the URL of the latest nightly build from Jenkins and write everything into a new HTML file.
Sounds good!
Quote
Too bad currently Jenkins is not reachable here. So I couldn't test out things.
Just restarted it, hope it's fine now. It used to lock up within minutes after starting, but since I've disabled the builds page, it's a little better. Not sure how to diagnose it - the symptom is very high CPU usage with no apparent reason (and no obvious increase in website traffic - it's actually pretty quiet).
Quote
Do you plan to use one Python script that generates multiple HTML file or do you need to call it with parameters for each camera model?
I don't mind, either way should be fine.
Quote
> There's some extra functionality I'd like to add, too.
Could you tell me what you like to add in future?
Sure, most of it should be obvious from the extra menu items from the example HTML, but I'll give some details below.
Here's what I'd like to address:
* design: OK to keep it along the same lines as the old one?
* compatibility with Windows or Mac browsers: does my HTML template look fine there?
* validation: I'm not good at web development, so other than the w3c validator, I'm not sure what to look for.
* top menu:
- main builds: ports merged to mainline
- early ports: ports that are still in progress and can be compiled from their own branches (e.g. 1200D)
- additional modules:
- here I'm thinking to list the modules that are not widely used, or still experimental (e.g. io_crypt, tiltcalc, raw_diag)
- I can compile from user repos as well
- todo: a list with what's worth including here
- what about naming this just Modules, moving the modules section from the features page here, and listing additional modules below?
- utilities
- things like mlv_dump, raw2dng, cr2hdr, with both win/mac builds
- todo: a list with what's worth including here
- experiments
- builds from branches like new_sound_system, crop_rec, iso-research
- what about compiling pull requests automatically, so users can give feedback easier?
- other stuff worth including?
* buttons:
- change log
- this used to be a popup box, which looks nice, but requires javascript, which I'd rather avoid
- I'm open to suggestions on how to make them more obvious
- what about displaying the changes for latest build right below the buttons?
- the changes for old builds could be in a large HTML page; maybe only show the last month or so?
- build log: plain text is fine for me; better suggestions?
- old builds: large HTML page?
- screenshots and tests:
- proof of concept here (http://www.magiclantern.fm/forum/index.php?topic=12396.msg119592#msg119592)
- we may start with some menu screenshots from qemu (should already work on some cameras like 60D, 5D3, 500D, 1200D), and do the rest later.
- a simple test would be to start each binary in QEMU and check whether ML config file gets created (this should also work on models with SD card that cannot boot the GUI yet)
- this section has huge potential IMO (automated burn-in tests and such), but let's start with something easy, just to get the ball rolling.
- discussion: just links to the forum (for each camera)
We don't need to finish all of these in order to get it back online; just the basics (previous functionality). I'm just thinking in advance, what would be nice to have over the next few months.
That's it for now, thanks for helping on any of those items. I expect to have some more time next week, to work on it; meanwhile, I'm mostly available during evenings (European time). We may discuss on IRC as well if you prefer.
@Alex
Suggested additional top menu items "Popular Apps", "Canon Firmware Files"
The "Popular Apps" menu could be populated with links to the home pages of 3rd party applications used by members (Public Domain only and/or Commercial).
E.G.: AutoStakkert, CombineZP, DeepSkyStacker, Astro Photography Tool, Startrails, Startrax, Raw Therapee, UFRaw etc...
The "Canon Firmware Files" menu item would be populated with links to ML supported Canon firmware files by camera model.
Suggested items for the "Utilities" menu could be links to things like:
- Card testing and undelete utilities that have been recommended by community members.
- EOSCard
- EOSinfo - shutter count program
- Magic Rescue
- dcraw
- exiftool
Maybe make a distinction between pure utilities like card testers vs workflow apps. e.g.: I would treat the likes of BarracudaGUI, CeroNoice, MLVProducer, etc. as workflow apps
Under "Additional Modules" suggest to include: "bolt_raw", "bulb_nd" and "foc_inf"
A1ex, I make some progress with the Python script. Now I could generate HTML files with the data from Jenkins, that contain almost every information, like your 550D.html page example in your first post, but for every camera currently supported by ML. Missing within the HTML is currently the hash of the Mercurial changeset from the repository, the commit messages and the number of downloads. I need to extract the first two values from a structure which appears to me like a JSON object or array.
[
{
'node': '15eb9aaa05c022c637c6ece48095a219ee7069c3',
'deletedPaths': [],
'modifiedPaths': ['modules/raw_rec/Makefile'],
'author':
{
'absoluteUrl': 'https://builds.magiclantern.fm/jenkins/user/alex@thinkpad',
'fullName': 'alex@thinkpad'
},
'timestamp': -1,
'rev': 12166,
'commitId': None,
'date': '1473959453.0-10800',
'merge': False,
'addedPaths': [],
'_class': 'hudson.plugins.mercurial.MercurialChangeSet',
'affectedPaths': ['modules/raw_rec/Makefile'],
'msg': 'raw2dng and related: use HOST_CFLAGS (should fix building raw_rec with older compilers)'
}
]
The number of downloads must be read somehow with the JenkinsAPI, but I don't know how to do it yet. I pushed my latest progress into my development branch.
https://bitbucket.org/tecgen/magic-lantern/commits/c562c7bfd54ffc088ce79d3aba9c8b0349be3970?at=unified
Hey folks,
Before you finish a non-Javascript version. I created a Javascript-based website for people to use in the meantime.
https://coloraggio.github.io/builds.magiclantern.fm/
It is as fast as Jenkins API allows (I optimized query parameters to make responses faster).
I also implemented a client-side caching to save useless request when user is navigating back and forth between pages.
@jzedurqn Nice work !
Indeed that's a nice look to start off with @jzedurqn!
@jzedurqn, thanks for the facelift, I like it!
@tecgen: the number of downloads is not given directly by Jenkins - that's my hack, and the info is available in a separate JSON file ( http://builds.magiclantern.fm/download-stats/api/json ). It only contains the most downloaded ones, and it's a static file (recomputed periodically).
BTW, the old site is available at http://builds.magiclantern.fm/index-js.html, for reference.
Yes looks very good , but I notice you can only download the latest nightly builds , What about older builds ?
How will there be accessed ? As we all know the latest nighty builds sometime can very problematic .
So we my have to reverting back to a older build.
Before you could show all the older builds from a dropdown menu , I think this needs to be re-implemented .
Current status: https://builds.magiclantern.fm/5D2-212.html
(a small HTML page with latest build, a larger HTML page with all the old builds, and a huge HTML listing all the changes as well)
The changeset info from Jenkins appears both broken (e.g. incorrect on 1100D) and incomplete (missing branch info, for example), so I guess I should take just each build's changeset from Jenkins and lookup the other changes directly on mercurial.
I'm also thinking to show only the large changes (e.g. merged pull request XYZ, with link), since a large page with all that stuff doesn't look quite easy to read. Better ideas?
a1ex - the page design looks nice, it follows with what has gone before it. lean but usable. :)
Hi folks,
I tested the new builds page a bit and it looks good! Great work!
I just have a few things to suggest for a better readability.
1st. It would be nice to group the changeset list and make it like the Older builds one. So you can click on "changes", or whatever you want, and show the list and then hide it.
2nd. Could you set the the fw version under the camera model a little bit bigger? My eyes are still good but I had to read it two times to choose the right version. :D
Another possible solution for this, that would also shorten the list, would be: Write the camera model as simple text and write one or more firmware versions as links on its right or below it.
For example:
5D Mark III 1.1.3 (http://1.1.3) 1.2.3 (http://1.2.3)
5D Mark III
1.1.3 (http://1.1.3) 1.2.3 (http://1.2.3)
Keep up the good work guys!
Quote from: anDyIII on September 24, 2016, 04:02:41 PM
2nd. Could you set the the fw version under the camera model a little bit bigger? My eyes are still good but I had to read it two times to choose the right version. :D
html :
<span>Canon Firmware Version:<span>1.1.3</span></span>css:
.camera-list span span {
display: inline;
font-size: 12px;
font-weight: bold;
}
@Greg
Thanks.
I updated my post right now with another solution I thought that could also clean up the cameras list.
It's live!
Credits go to tecgen (initial script), jzedurqn (layout ideas) and Greg (CSS help). Thanks, guys!
There's still some missing functionality, and contributions are still welcome. Tidying the HTML, fine-tuning for mobile devices, checking the links, suggesting useful information... you name it.
A1ex
Had a quick look and seems pretty good.
One observation is that I would suggest we need a way for seeing what each new build adds/subtracts from the previous build, ie info/text about functionality changes or enhancements.
At the moment 'all' you have is a link to the code.
Thanks to you and others for your continuing dedicated work.
Cheers
Garry
Click on "Older Builds", then on "show details".
Any suggestion about how to make this more readable / obvious?
Nice work a1ex!
I would change camera list CSS to this, so it can left align well with the text.
.camera-list {
margin: 0 100px 20px 0;
float: left;
}
About the "other builds" page. In my opinion skipping the "short" version and directly showing the full version when user clicks "older builds" is better, since it's just an HTML page and person interested in older builds will prefer information about changes right away.
P.S. a1ex is the source of this website on bitbucket? I can contribute on HTML, CSS, typography, etc.
Applied those as well, thanks.
I'll upload it to bitbucket as well, but right now I need a little break :D
Meanwhile, changes can be made directly to the HTML. Turning it into template is easy for me (I use the Mako engine), but when it comes to design, I just do this:
(http://i.imgur.com/SZPjHwzm.jpg)
@a1ex thank you for everything you're doing for ML!
At some point when it's on Bitbucket people (me or others) can contribute and do fixes here and there.
The most important thing is that the website right now as it is looks fine and works fine.
@A1lex
Just a couple of suggested wording changes (in red) to the following section on the "Builds" page.
When it will be ready?
Unfortunately, Magic Lantern ports don't happen to a schedule.
There is no plan, and there is no Magic Lantern organization that specifies which port happens next.
If there is work being done on a camera, there will be a development thread in the forum.
If there is no mention of development activity on the forum, there is no reason to ask about that camera's status: It is not supported, and there is no way for anyone to know if or when it might be supported. Your guess is as good as ours.
If there is no ML available for your camera, you should act like it never will be. -- Walter Schulz
There is a mispelling on the nightly builds page.
Marked in red ;)
QuoteYour cameara is not listed?
A port of a new camera model happens if and only if there is a developer who has the camera and sufficient time.....
Changes look great guys! Keep 'em coming. :)
Just thought.
Maybe display the latest Build Date and Time under each camera model on the Nightly Build landing page or some other indicator that a new build exists. This would remove the need to drill down further unless a new build was available.
Under 'Ports In Progress'; 70D should be enlisted as 1.1.2 and 1.0.1 for the 100D.
700D page links to Canon containing most recent firmware (1.1.5). Please check links and - my suggestion - replace them with links to pelican's site.
EDIT: Same issue with 6D.
Hello,
I'm brand new on this forum but I'm a young amateur independent web designer. I would like to help as much as I can, because I think that I may have some good ideas or advices and that it may be great experience too !
So, to begin softly, I just ran a quick speed test on your page, using common tools, here are the results :
from Goolge's PageSpeed Insight :
https://developers.google.com/speed/pagespeed/insights/?url=http%3A%2F%2Fwww.magiclantern.fm%2Fdownloads.html
Pingdom tools :
https://tools.pingdom.com/#!/cJ3aiF/http://www.magiclantern.fm/downloads.html
Talking about SEO optimizations, here are some advices :
http://seositecheckup.com/seo-audit/www.magiclantern.fm/downloads.html
Consider this as a beginning, a way to start optimizing the website...
Hope you enjoyed, coming back soon :)
Just a few suggestions :
- Increase the size of the Warning display bye something like 150% (1.5em)
- Try to use a two columns design to present the download : it would allow you to pull up the download button (just like they did on VLC download page https://www.videolan.org/vlc/)
- You should update the copyrights dates to 2016 and why not using Creative Commons ?
- If you hitch up the download button, try to get a different background for this section
Cheers ;)
Canon updated firmware for a whole bunch of cams. At time of writing these nightly build pages are linked to Canon downloads with firmware not supported by ML:
6D
60D, 60Da
700D
650D
600D
500D
1100D
I suggest to use links to Pelican's repository instead
Description for 70D should be edited (1.1.1 -> 1.1.2). And 100D, too: 1.0.0 -> 1.0.1
I suggest to avoid links to Canon at all and use Pelican's repository for 5D2, 550D and 50D instead.
Installation instructions for 5D3.113 and 5D3.123 may be altered from
"[...] If you are running 1.3.3, you can downgrade with EOS Utility."
to
"[...] If you are running 1.3.3 or higher, you can downgrade with EOS Utility 2.x."
A link to EOS Digital Solution Disk 29.1A (containing EOS Utility 2.14.10) might be helpful. For all I know EOS Utility 3.x will not allow downgrading firmware.
Don't know if you already have this but it would be great to track the number of downloads per platform. The Nightly builds page would be an obvious place to show the number of downloads.
Reasons for this are:
1- People looking into buying a camera can see which camera and firmware version is the most popular with ML users.
2- Developers can see when a new feature shows a spike in the number of downloads.
I've been posting some test builds from development branches and was surprised at the amount of interest in the 5D3.123 despite what seems to be a recommendation to use 5D3.113 for better performance or if clean HDMI out, dual monitor support and AF at f/8 with teleconverters is not required.
A bit off topic but since Walter brought it up -- when upgrading or downgrading the Canon firmware I've always put the Canon firmware on the card and done the process in camera without problems. The issue with not being able to downgrade seem to apply only to users attempting to do it using EOS Utility 3.x. Am I missing something by doing it in camera?
One more thing -- you can include the 5D3 to the list of Canon updated firmware. Version 1.3.4 was released on November 29, 2016. Pelican has already added it to his site.
Re up/downgrading, I successfully went backwards and forwards between 5D3 113 and 123 several times yesterday: all by 'just' using the canon in-camera upgrade firmware approach.
QuoteThe issue with not being able to downgrade seem to apply only to users attempting to do it using EOS Utility 3.x. Am I missing something by doing it in camera?
Firmware can only be downgraded to 1.1.3 from eos utility when going from 1.3.4. Do it from the card and your camera will tell you no. Do it from eos utlity and we,re ok. Thankfully.
The issue doesn,t seem to occur with 1.1.3 to 1.2.3 and back.
@dfort & garry23: Canon introduced firmware downgrade check with 1.3.3 for 5D3. As Danne wrote downgrading is blocked in 1.3.3 and 1.3.4 when using the cam's menu option.
@dort: Links for 5D3 - as you can check - are leading to Pelican's repository. Therefore 5D3 is not included in the list above.
@Walter thanks for the claification. I'll be sticking to 123 for now, as I need the F/8 AF on my x2 extender 70-200.
For me, not shooting video, 113 doesn't seem to add much, if anything, over 123.
One day I might try ML raw video :-), i.e. On my EOSM. But I do 'worry' it is a lot of effort, but then again I haven't really tried it.
I wonder what the easiest way is to get into raw video on the EOSM?
Cheers
Garry
Can we keep it to the topic, please?
Wrist suitably slapped ;)
Walter started it :o
Download counters are back :)
Additional pages (modules, utilities) are also starting to appear. Not yet fully functional, but at least it's a start.
Excellent progress @al1ex! ;D
(https://c2.staticflickr.com/1/716/31316082673_95970d74a6.jpg) (https://flic.kr/p/PHi7kT)
Thanks. Can you help me create screenshots for all the modules from this page?
https://builds.magiclantern.fm/modules.html
A GIF similar to the one from bulb_nd should be fine. If there's nothing interesting to show, a submenu screenshot would be enough.
For module authors: to add your module to this page, I need a link to your repository and a screenshot.
@a1ex Thought I'd be helpful, did a GIF for burst.mo(I hope no one else is making the same gif as I post, but if you are, I'm sorry, but still post it because it's probably better than mine)
(http://gdurl.com/YITu)
Is the 5D2 screen resolution the same as others? I thought it was 640x480 but the screenshots are 720x480
The build server is on Linux? Any chance the Utilities page could also host Linux/Mac apps besides those Windows ones since you can just build them anyway?
Ilia: thanks, I've resized it like this:
convert -coalesce burst.gif burst.png
convert -delay 100 -loop 0 burst-*.png -resize 50% -layers Optimize burst2.gif
Reason: current web browsers don't seem to do a good job at resizing the original (aliasing issues).
5D2 has 640x480 physical resolution, but 720x480 logical buffer. The exact mapping from buffer to display is unknown; can be probably found with a bit of patience to try some patterns.
@Licaon_Kter: do Linux binaries make any sense? (I mean, compiling host binaries on this system usually just works)
For Mac, I need some help setting up the build environment. I've tried a while ago on the old server, with advice from kichetof (https://www.magiclantern.fm/forum/index.php?topic=7139.msg126726#msg126726), but got stuck.
Quote from: a1ex on January 06, 2017, 01:05:29 AM
@Licaon_Kter: do Linux binaries make any sense? (I mean, compiling host binaries on this system usually just works)
Like on any other platform, don't just go the "if you run Linux you already compile stuff" way :) (if your response was like that)
Else, that page kinda says "You'll need Windows to use Magic Lantern" otherwise ;)
Okay, pull request welcome for statically linking these binaries, preferably with this tool (http://ptspts.blogspot.com/2014/01/announcing-pts-xstatic-tool-for.html). Bonus points for x86 and ARM support in the same binary.
Quote from: a1ex on January 06, 2017, 02:05:28 AM
Bonus points for x86 and ARM support in the same binary.
So you can run
raw2dng on your Android phone?
I'm running a derivative of it on Axiom Beta (ARM processor, Arch Linux).
There are some ARM tablets running Linux as well.
This page is looking very nice! Good work! ;D
Is there any easy way to get to the experimentals (https://builds.magiclantern.fm/experiments.html) page from the home page (http://magiclantern.fm/) by following links? Seems like the only way to access that page is by the URL posted on various forum posts.
Are the experimentals also on a nightly schedule? Just wondering because there were some updates that haven't come through yet.
Finally, which branches are the experimentals coming from? The Crop mode recording build log says 5D3.113-crop3x-april-1st-edition which isn't in the main repository and the log doesn't have any trace of 5D3.123 yet there's a build for it.
Experiments.
(https://s30.postimg.org/ptqgb2s5d/Screen_Shot_2017_01_10_at_18_47_02.png)
Doh!
:-X
Just realized this... these screenshots are literally from 2013! :o
(https://c1.staticflickr.com/1/538/32122043772_53796ecaa8.jpg) (https://flic.kr/p/QWvSuU)
Unless this was intended for but should we try and get new screenshots of every feature in this page (https://www.magiclantern.fm/features.htmlpage)?
I'd be happy to help out @a1ex!
Read Audionut's signature and follow those links.
With lua and qemu, could the autobuilder generate those screenshots?
Quote from: DeafEyeJedi on January 12, 2017, 09:06:20 PM
Just realized this... these screenshots are literally from 2013! :o
Hey, how did you get there? I removed that page a while ago, because it was pretty outdated and some things were not exactly true. Would be nice to have it updated.
Quote from: koenkooi on January 12, 2017, 09:31:05 PM
With lua and qemu, could the autobuilder generate those screenshots?
Yes. Would you volunteer to write some scripts? A starting point is in the QEMU test suite.
Look here as well: http://www.magiclantern.fm/forum/index.php?topic=12396.msg119592
Quote from: a1ex on January 13, 2017, 12:34:19 AM
Hey, how did you get there?
http://www.magiclantern.fm/downloads.html
http://www.magiclantern.fm/about.html
http://www.magiclantern.fm/donate.html
http://www.magiclantern.fm/about.html
Each of those pages has a link at the top of the page to that old features page.
The new pages are looking great.
Quote from: a1ex on January 13, 2017, 12:34:19 AM
Hey, how did you get there? I removed that page a while ago, because it was pretty outdated and some things were not exactly true. Would be nice to have it updated.
http://www.magiclantern.fm/features.html and yes I'm interested in helping out on getting you updated screenshots for the feature page since the new layouts looks really nice and easy to scroll through -- is that right, @Audionut? :)
Quote from: a1ex on January 13, 2017, 12:34:19 AM
...Would be nice to have it updated.
Here they are (coming from a 7D since it has the Audio Controls) and if for any reason(s) you prefer screenshots from the 5D3 -- just let me know!
https://flic.kr/s/aHskSAJT6u
Guys!
It may be a silly question but my firmware version was 1.1.0, after I found 1.1.2 on Canon's official page, so I've installed it. Can I install ML on my camera anyway?
Quote from: DeafEyeJedi on January 16, 2017, 06:02:24 AM
https://flic.kr/s/aHskSAJT6u
"The owner has disabled downloading of their photos"
(I could try some things like screenshot followed by recompression, but the end result will not be the best - Flickr doesn't even show them at native resolution)
I thought I had them enabled. They should be now.
No Still can't download them.
Man I keep forgetting to click on 'Save' after selecting allowing for downloads from Public (it was on Flickr members only) so yes it should be downloadable now.
(https://c1.staticflickr.com/1/441/31807055554_d14862297d.jpg) (https://flic.kr/p/QsFtty)
Thanks for checking @Ottoga!
Forgive me if I've got this wrong.
In the experimental area would it be useful to place a link in each sub section, eg Lua_fix etc, including sections such as Lua_api_docs, that took one straight to the correct area to report things and suggest changes.
At the moment you need to know where to report, and if you don't know you are rather lost.
Just a thought.
Each experimental build has a link to the relevant forum thread...
@A1ex
Yes I know that, but I wondered if there was a 'better' link when you are suggesting changes, ie rather than 'just' the forum thread.
Also the lua_api doc doesn't have a form area, ie where we can all contribute.
As I said: just a thought. No big deal if we stay where we are :-)
Added a link to BitBucket page for each section, and a link to forum threads where it's explained how one can help.
I'd like to keep the pages static (simple and robust), and I don't see the need for an additional section for comments (besides the forum).
:)
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
On the Top of the Page is written:
QuoteMain 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
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 (http://www.magiclantern.fm/forum/index.php?topic=20455) problem (http://www.magiclantern.fm/forum/index.php?topic=20445.0);
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 (http://www.magiclantern.fm/forum/index.php?topic=20560).
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.)
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?
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.
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 (http://ashleydw.github.io/lightbox/) or that (https://blueimp.github.io/Gallery/#links)
If I'll also compare the screenshots with the previous run (http://www.magiclantern.fm/forum/index.php?topic=12396.0), 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.
Just noticed the tool tip, seems good :)
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.
Quote from: Walter Schulz on October 03, 2017, 02:38:35 PM
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 (https://getbootstrap.com/2.3.2/javascript.html#tabs) or accordion (https://getbootstrap.com/2.3.2/javascript.html#collapse)
I think, it's good to keep links to forum in cam main page (not hidden in tabs/accordion)
And a "Known Issues" section, please. Minimize further flicker issue duplicates for 6D/70D/700D/EOS M, for example.
Quote from: a1ex on September 19, 2017, 10:37:57 PM
1) fix the user guide (http://www.magiclantern.fm/forum/index.php?topic=20455) problem (http://www.magiclantern.fm/forum/index.php?topic=20445.0);
Missed you linked this thread.
I didn't reply there yet because I wanted to wait for Audionut's and your opinions on that.
Quote from: Walter Schulz on October 03, 2017, 02:38:35 PM
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...
Quote
Now to cam build page (example 5D Mark II 2.1.2):
...
Suggestions:
- Seperate sections "Test status", "Changes", "Useful links", "Statistics", "Logs"
Quote from: kichetof on October 03, 2017, 03:47:54 PM
Good Idea ! Maybe with tabs (https://getbootstrap.com/2.3.2/javascript.html#tabs) or accordion (https://getbootstrap.com/2.3.2/javascript.html#collapse)
Better like this?
http://builds.magiclantern.fm/700D-115.html
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 [...]
Quote from: a1ex on October 04, 2017, 11:17:27 AM
Better like this?
Looks good! To be sure user clicks on accordion, add a chevron in the right of the button, like that (https://www.codeply.com/go/gOBrMgWpzS/bootstrap-collapse-accordion-with-chevron-icons)
Minor update with the border under the button, add a little margin
(8px like padding in alert) in your css:
.accordion-inner {
padding: 9px 15px;
margin-top: 8px;
border-top: 1px solid #e5e5e5;
}
Quote from: Walter Schulz on October 04, 2017, 11:52:29 AM
- Change order of item 1 and 2 in "Installation".
+1
Done - should I leave the installation text always visible, or it's better hidden?
This chapter should be visible when loading (add 'in' class) but is ok to collapse it
<div id="collapse-install" class="accordion-body collapse in">
<div class="accordion-inner">
Maybe adding a button to expand all in one time ?
<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 (http://www.magiclantern.fm/forum/index.php?topic=14704), 5D3 123 (http://www.magiclantern.fm/forum/index.php?topic=11017)
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"...
(https://farm5.staticflickr.com/4456/36848389613_002eb16c3c.jpg) (https://flic.kr/p/Y9aCsi)
But on the new designed Nightly page it's fine with up to date stuff (2017) and whatnot.
Just not in the Download page (http://www.magiclantern.fm/downloads.htmlDownload%20page).
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.
700D firmware (https://builds.magiclantern.fm/700D-115.html) 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 (https://www.dropbox.com/sh/uvdmveo80wz8zs6/AAAFbubagD1pVWBH94h_uFSBa?dl=0), and contain all the firmwares once uploaded.
Missing:
5D3 1.3.4
Quote from: Audionut on September 28, 2018, 04:10:33 AM
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 (https://bitbucket.org/daniel_fort/magic-lantern/downloads/). Look for the "5D3 Canon Firmware for Testers.zip" package.
Quote from: Audionut on September 28, 2018, 04:10:33 AM
Missing:
5D3 1.3.4
?
Screenshot pel.hu/down:
(https://img2.picload.org/image/dcgdipwr/pel.hu.png)
Some updates to the installation instructions on the download page, starting from this suggestion (https://www.magiclantern.fm/forum/index.php?topic=23129.msg209209#msg209209):
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).
We've been naughty, I suppose. Unwanted present: Pel.hu is down, links to outdated firmware no longer working.
Strange--I thought the links were going to archived web pages.
In any case -- good reason to move the firmware updates higher on the priority list.
Maybe offtopic:
ime modules are built every day but last change was July 2018.
(https://img.picload.org/image/dcipaadp/ime_builds.png)
Bug or feature?
Bug.
Back then, the nightly builds were built in the same way (that was the default config, I think). Some people actually thought there were daily updates, and some of them even reported differences between identical builds!