Part of lp.soyuz.browser.build View In Hierarchy
Known subclasses: lp.buildmaster.browser.builder.BuilderHistoryView, lp.soyuz.browser.archive.ArchiveBuildsView, lp.soyuz.browser.build.DistributionBuildRecordsView, lp.soyuz.browser.distroseries.DistroSeriesBuildsView, lp.soyuz.browser.sourcepackagebuilds.SourcePackageBuildsView
It retrieves the UI build_state selector action and setup a proper batched list with the requested results. See further UI details in template/builds-list.pt and callsite details in Builder, Distribution, DistroSeries, DistroArchSeries and SourcePackage view classes.
Method | label | Undocumented |
Method | setupBuildList | Setup a batched build records list. |
Method | arch_tag | Return the architecture tag from the request. |
Method | architecture_options | Return the architecture options for the context. |
Method | default_build_state | The build state to be present as default. |
Method | show_builder_info | Control the presentation of builder information. |
Method | show_arch_selector | Control whether the architecture selector is presented. |
Method | search_name | Control the presentation of search box. |
Method | form_submitted | Undocumented |
Method | no_results | Undocumented |
Method | _setupMappedStates | Build self.state and self.availableStates structures. |
Return None, so use tal:condition="not: view/setupBuildList" to invoke it in template.
self.state is the corresponding dbschema for requested state_tag
self.available_states is a dictionary containing the options with suitables attributes (name, value, selected) to easily fill an HTML <select> section.
Raise UnexpectedFormData if no corresponding state for passed 'tag' was found.
It allows the callsites to control which default status they want to present when the page is first loaded.
It allows the callsite to control if they want a builder column in its result table or not. It's only omitted in builder-index page.
This allows the callsite to control if they want the architecture selector presented in the UI.