[00:28] <superm1> ev, okay so looking it over, at least my recovery plugin will may need a fair bit of work to fit in this depending on the intents and what's still missing on your branch; i think a core question is going to be what the plans are for that progress_section widget.  will it be present on *all* pages, including the introduction/first page?
[00:31] <superm1> and further, what's the thought on showing that widget during oem-config too
[07:32] <jussi> ev: I came across https://bugs.edge.launchpad.net/ubuntu/+source/ubiquity/+bug/288675 - not sure if its related, but wanted to draw your attention to it in anycase. (and yes, I realize it is _old_) :)
[07:32] <ubot2> Launchpad bug 288675 in ubiquity (Ubuntu) "no partitions listed in partition table (dup-of: 335376)" [Undecided,New]
[07:32] <ubot2> Launchpad bug 335376 in ubiquity (Ubuntu) "[MASTER] ubiquity should warn users about unusable mounted partitions (affects: 6) (dups: 1) (heat: 10)" [High,Fix released]
[09:11] <ev> superm1: wow, awesome work on the packaging branch.  Thanks so much for doing that.  I'll give it a review in a little bit.
[09:13] <ev> superm1: As for the progress section widget, the intention is to display the greeter page, then the prepare to install Ubuntu page, then (if there's no network connection and wirelesss hardware is present) the wireless page, then partitioning.  Once you hit "Install Now" from the partitioning page, the progress section will appear and the core installation process will begin in parallel to the rest of the pages.
[09:13] <ev> I've set it to always display for now to make sure I'm paying attention to the maximum size of the window and how most pages will look.
[09:15] <ev> I'll be doing the debconffilter plumbing to allow this parallel work at the sprint next week
[09:49] <ev> cjwatson: might you be able to tell me what the :sl#: directives in debconf templates mean?  I've been digging through the source and cannot find that processed anywhere.  Apologies if this is immensely obvious.
[09:55] <cjwatson> yeah, they're translation sublevels
[09:56]  * cjwatson hunts for the docs
[09:57] <cjwatson> http://d-i.alioth.debian.org/doc/i18n/ch01s04.html#sublevels
[09:58] <ev> ah!  Very much appreciated, thanks!
[10:02] <ev> ah, that's why.  The source package doesn't have l10n-sync
[10:03] <cjwatson> yeah, none of this is actually used in Ubuntu, but I've made a practice of trying to set the right sublevel comments anyway where possible in order to make future patch submissions easier
[10:10] <CIA-97> partman-auto: evand * r326 ubuntu/debian/po/templates.pot: Update template
[10:17] <CIA-97> partman-auto: evand * r327 ubuntu/debian/changelog: releasing version 91ubuntu3
[10:58] <CIA-97> partman-auto-loop: cjwatson * r55 ubuntu/debian/ (changelog rules):
[10:58] <CIA-97> partman-auto-loop: Use 'dh $@ --options' rather than 'dh --options $@', for
[10:58] <CIA-97> partman-auto-loop: forward-compatibility with debhelper v8.
[11:00] <CIA-97> partman-iscsi: cjwatson * r56 ubuntu/debian/ (changelog rules):
[11:00] <CIA-97> partman-iscsi: Use 'dh $@ --options' rather than 'dh --options $@', for
[11:00] <CIA-97> partman-iscsi: forward-compatibility with debhelper v8.
[11:01] <CIA-97> partman-uboot: cjwatson * r12 ubuntu/debian/ (changelog rules):
[11:01] <CIA-97> partman-uboot: Use 'dh $@ --options' rather than 'dh --options $@', for
[11:01] <CIA-97> partman-uboot: forward-compatibility with debhelper v8.
[11:43] <CIA-97> ubiquity: evand * r4148 maverick-redesign/ubiquity/plugins/ubi-partman.py:
[11:43] <CIA-97> ubiquity: * Support resizing or replacing one partition on each disk, as implemented in
[11:43] <CIA-97> ubiquity:  partman-auto 91ubuntu-3.
[11:50] <CIA-97> ubiquity: evand * r4149 maverick-redesign/gui/gtk/stepPartAuto.ui: missed signal handler in previous commit.
[11:52] <CIA-97> ubiquity: evand * r4150 maverick-redesign/ (6 files in 5 dirs): * Start of ubi-wireless conversion to a debconf plugin.
[11:53] <CIA-97> ubiquity: evand * r4151 maverick-redesign/ubiquity/plugins/ubi-timezone.py: note on how to implement the timezone page
[12:00] <CIA-97> ubiquity: evand * r4152 maverick-redesign/ (92 files in 8 dirs): Merge with Mario's packaging branch.
[12:00] <ev> superm1: ^ thanks again!
[15:02] <ameetp> cjwatson:  Could you or someone from your team take a look at bug 604685 when you get a chance.
[15:02] <ubot2> Launchpad bug 604685 in ubiquity (Ubuntu) "[Maverick] No "Forward" button when selecting timezone (affects: 2) (heat: 12)" [High,Triaged] https://launchpad.net/bugs/604685
[15:03] <ev> that's a pygtk bug
[15:04] <ev> notice that the exception starts inside the gobject introspection module
[15:04] <ameetp> ev: oh okay
[15:06] <ameetp> thanks
[15:06] <ev> sure thing
[16:14] <superm1> ev, ah that makes much more sense then about the progress section widget, gotcha.  np on the packaging branch. thanks for the merge
[16:17] <ev> for what it's worth the timezone design is changing slightly.  A combobox doesn't work well (pulls focus to the wrong area), even with submenus, so on michaelforrest1's advice I'm working on writing a menu button that will sit just to the right of what was the combobox but is now an entry widget.
[16:17] <ev> amazed that gtk doesn't have this already
[17:33] <ev> http://people.canonical.com/~evand/tmp/timezone_menu_button.png - michaelforrest, perhaps the wrench icon wouldn't be such a bad fit.
[17:35] <ev> or a cog
[17:40] <michaelforrest> ev: I think something menu-like would be more appropriate
[17:40] <michaelforrest> three lines of a list or whatever
[17:41] <michaelforrest> a cog feels like 'settings' to me
[18:02] <CIA-97> ubiquity: superm1 * r4133 ubiquity/ (debian/changelog ubiquity/frontend/gtk_ui.py):
[18:02] <CIA-97> ubiquity: Disable the "Installing the System" title before Ubiquity comes up
[18:02] <CIA-97> ubiquity: in automatic mode to prevent confusion before it actually does damage
[18:02] <CIA-97> ubiquity: in case there are any confirmation screens that should come up first.
[19:27] <jussi> ev: any chance you are about? i got it to install...


[16:42] <OvenWrks> Eickmeyer: I think I need to revisit ubuntustudio-menu-item-creator after controls is out.
[16:50] <Eickmeyer> OvenWrks: Well, yeah. The KDE Menu Editor does xdg pretty well and nested menus, so I'm even wondering if there's any point to it going forward.
[16:56] <OvenWrks> Eickmeyer: I had reason to use it to help my son add a desktop file for an application that came without one and found the process "unintuitive". I think an install style with a bunch of next/back buttons would make more sense...
[16:57] <Eickmeyer> OvenWrks: Ok, I'd like to see that.
[16:57] <Eickmeyer> Honestly, though, makind a desktop file for an application that comes without one can be done from packaging.
[16:57] <Eickmeyer> *making
[16:57] <OvenWrks> Eickmeyer: Is the kde menu editor seems (at least in my studio over kubuntu) hard to find
[16:58] <Eickmeyer> Right-click on launcher, "Edit Applications...". Not hard at all.
[16:58] <OvenWrks> in my son's case that was not an option.
[16:58] <Eickmeyer> Did you try?
[16:58] <OvenWrks> ah, I was looking in settings
[17:00] <OvenWrks> maybe what you mean by packaging is not what I am thinking. To me that means bug the packager (this was not a package he started with).
[17:01] <OvenWrks> going forward, he is learning programing
[17:01] <OvenWrks> python right now, but mybe c++ as well
[17:02] <Eickmeyer> Well, if it's an application that doesn't include a .desktop file, that can be provided by the packager. I could even do it if it's something in the repos already.
[17:08] <OvenWrks> it's a game editor from the game site.
[17:08] <OvenWrks> I think it came as a zip
[17:09] <OvenWrks> no install script
[17:09] <Eickmeyer> Ah, I see.
[17:09] <OvenWrks> " go to the directory where you unzipped your download and open <filename>"
[17:10] <Eickmeyer> Lazy packaging. So many devs think they have to do the actual packaging.
[17:14] <OvenWrks> Eickmeyer: for menu-item-creator I am thinking a first screen with "I want to:" with two options A: create a new menu item, B: edit an existing item
[17:16] <OvenWrks> Next would go to a menu item name dialog having three things: an entry box, a search box and a dropdown. Maybe just an entry for create and just search and drop down for existing.
[17:18] <OvenWrks> for create, next would go the menu item editor we start normally. but existing could go right to the edit page we have now.
[17:21] <OvenWrks> I think when I install 21.10 for PW testing. I will play with kmenuedit. If it seems to do whatever our little menu editor does. it can replace it.
[17:22] <OvenWrks> maybe add an item to the settings menu :)