rattail/tailbone
1
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity

Remove some references to "buefy" name within docstrings, comments

Browse source
This commit is contained in:
Lance Edgar 2024-04-14 20:30:52 -05:00
parent c036932ce4
commit ba521abf4f
6 changed files with 13 additions and 18 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
tailbone/forms/core.py
View file

@ -968,10 +968,10 @@ class Form(object):
def render_field_complete(self, fieldname, bfield_attrs={}):
"""
Render the given field in a Buefy-compatible way. Note that
this is meant to render *editable* fields, i.e. showing a
widget, unless the field input is hidden. In other words it's
not for "readonly" fields.
Render the given field completely, i.e. with ``<b-field>``
wrapper. Note that this is meant to render *editable* fields,
i.e. showing a widget, unless the field input is hidden. In
other words it's not for "readonly" fields.
"""
dform = self.make_deform_form()
field = dform[fieldname] if fieldname in dform else None

10
tailbone/forms/widgets.py
View file

@ -57,11 +57,11 @@ class NumberInputWidget(dfwidget.TextInputWidget):
class NumericInputWidget(NumberInputWidget):
"""
This widget only supports Buefy themes for now. It uses a
``<numeric-input>`` component, which will leverage the ``numeric.js``
functions to ensure user doesn't enter any non-numeric values. Note that
this still uses a normal "text" input on the HTML side, as opposed to a
"number" input, since the latter is a bit ugly IMHO.
This widget uses a ``<numeric-input>`` component, which will
leverage the ``numeric.js`` functions to ensure user doesn't enter
any non-numeric values. Note that this still uses a normal "text"
input on the HTML side, as opposed to a "number" input, since the
latter is a bit ugly IMHO.
"""
template = 'numericinput'
allow_enter = True

2
tailbone/static/css/grids.rowstatus.css
View file

@ -2,7 +2,7 @@
/********************************************************************************
* grids.rowstatus.css
*
* Add "row status" styles for Buefy grid tables.
* Add "row status" styles for grid tables.
********************************************************************************/
/**************************************************

4
tailbone/templates/customers/view.mako
View file

@ -28,9 +28,7 @@
% endif
ThisPage.methods.detachPerson = function(url) {
## TODO: this should require POST, but we will add that once
## we can assume a Buefy theme is present, to avoid having to
## implement the logic in old jquery...
## TODO: this should require POST! but for now we just redirect..
if (confirm("Are you sure you want to detach this person from this customer account?")) {
location.href = url
}

4
tailbone/templates/roles/view.mako
View file

@ -15,9 +15,7 @@
% endif
ThisPage.methods.detachPerson = function(url) {
## TODO: this should require POST, but we will add that once
## we can assume a Buefy theme is present, to avoid having to
## implement the logic in old jquery...
## TODO: this should require POST! but for now we just redirect..
if (confirm("Are you sure you want to detach this person from this customer account?")) {
location.href = url
}

3
tailbone/views/settings.py
View file

@ -341,8 +341,7 @@ class AppSettingsView(View):
# specify error / message if applicable
# TODO: not entirely clear to me why some field errors are
# represented differently? presumably it depends on
# whether Buefy is used by the theme.
# represented differently?
if field.error:
s['error'] = True
if isinstance(field.error, colander.Invalid):