Merge lp:~lderan/ubiquity-slideshow-ubuntu/test into lp:ubiquity-slideshow-ubuntu
Status: | Needs review |
---|---|
Proposed branch: | lp:~lderan/ubiquity-slideshow-ubuntu/test |
Merge into: | lp:ubiquity-slideshow-ubuntu |
Diff against target: |
100 lines (+52/-1) 3 files modified
Slideshow.py (+16/-0) slideshows/link-core/slideshow.js (+35/-0) slideshows/xubuntu/slides/00_welcome.html (+1/-1) |
To merge this branch: | bzr merge lp:~lderan/ubiquity-slideshow-ubuntu/test |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Dylan McCall | Needs Fixing | ||
Pasi Lallinaho | community | Approve | |
Ubiquity Slideshow | code | Pending | |
Review via email: mp+180747@code.launchpad.net |
Commit message
Slideshow.py - now fetches the version number and name and sends them to the slideshow
Slideshow.js - replaces objects with .versionId & .releaseName with Id and name respectively
Usage example:
You are installing Ubuntu<span class="
results in:
You are installing Ubuntu 13.04, Raring Ringtail.
In the case the slideshow can't acquire the the version name or number, the contents of version-details will be ignored:
You are installing Ubuntu.
Description of the change
Slideshow.py - now fetches the version number and name and sends them to the slideshow
Slideshow.js - replaces objects with .versionId & .releaseName with Id and name respectively
Usage example
<span class="
results in
13.04 Raring Ringtail
Unmerged revisions
- 572. By Thomas Molloy
-
tidying up
- 571. By Thomas Molloy
-
added a fallback and added an example to the xubuntu welcome
- 570. By Thomas Molloy
-
Change xubuntu welcome home back
- 569. By Thomas Molloy
-
version number and name passed to the slideshow
So, my feeling on this is each slideshow content version should be targeted towards a particular Ubuntu release. If it's necessary to grab the version ID automatically, my assumption is that means we're either shipping outdated content (because, really, a lot changes from one release to the next and we've already had a few instances where flavours ship with plainly incorrect slideshow content); or we're shipping very general content (which could be argued for…). Am I missing something? :)
Personally, I've always been an advocate of just not repeating the version number here at all since Ubiquity already communicates that and it isn't really relevant information at this stage, but I don't think I've won that argument.
Anyway, this is optional, so I don't mind, but for this change to work, we'll also need a change in a released or to-be-released version of Ubiquity that is similar to what you have in Slideshow.py. Has that happened at this stage? It might also be nice to have a sensible fallback in the event that the version ID isn't provided, too. Right now it looks like we'll get an empty space after a comma, and no version number. Perhaps wrap that whole thing in an element that disappears if there's no version number available, like "Xubuntu<span class=" versionDetails" >, <span class=" releaseName" ></span> <span class=" versionId" ></span> </span> "?
Also - and I promise this is a tiny thing - your element classes are inconsistent. Please use dashes instead of camel case, there, like "release-name" and "version-id".
Thank you!