First of all , a brilliant application , and thank you for all the help till now .

This is my forms.py

from django import forms from openmaps.models import Open_Layers from django.contrib.admin import widgets
import floppyforms as forms class PointWidget(forms.gis.PointWidget, forms.gis.BaseGMapWidget): pass class MultiPointWidget(forms.gis.MultiPointWidget,forms.gis.BaseGMapWidget): pass class LineStringWidget(forms.gis.LineStringWidget,forms.gis.BaseGMapWidget): pass class PolygonWidget(forms.gis.PolygonWidget,forms.gis.BaseGMapWidget): pass class MultiPolygonWidget(forms.gis.MultiPolygonWidget,forms.gis.BaseGMapWidget): pass class GeoForm(forms.Form): point = forms.gis.PointField() multipoint = forms.gis.MultiPointField() line = forms.gis.LineStringField() poly = forms.gis.PolygonField() multipoly= forms.gis.MultiPolygonField()

According to this , all the points , multipoints , line etc load in separate openlayers maps , but in the same page . Is it by anychance possible to put in all the geometries in one map . And also , allow to change between maps like openlayers , osm , google maps using layerswitcher .

The error in the title is raised for Floppyforms widgets on Django 1.11.3 because of the change in this ticket (code here). The solution for now is to stay on 1.11.2 or lower until this is fixed in Floppyforms.

hello,

May be it's no relevant, but I would like to have a local copy of openlayers, and google (js and css) instead of getting them via their absolute URL.

• how can I achieve this ? (we could have sort of settings for that, instead of modify the widget Media class of BaseGMapWidget BaseOsmWidget or BaseMetacartaWidget)
• how interesting is it to use, for example django_compressor, to increase performance ?

thx

/home/foo/anaconda2/envs/flightsayer/lib/python2.7/site-packages/floppyforms/init.py:16: UserWarning: Unable to import floppyforms.gis, geometry widgets not available "Unable to import floppyforms.gis, geometry widgets not available")

Ok, I get that this happens on "from . import gis", but I don't understand what's going on.

(Everything worked fine until this morning, after I upgraded some stuff on my computer, and now I'm seeing this message and AHHHHH)

This fixes #89, allowing override of template_name in both __init__() (useful if you want to use the same widget class with two different templates without extra subclasses) and in render() (useful for more advanced use cases where you want to render the same widget instance on the same form field with two different templates, conditional on something).

Tests are included and pass on a full tox run.

I would happily add some docs as well, but in a quick perusal I didn't see where they would fit. As far as I can tell the individual widget classes are documented, but the core widget API isn't so far.

To avoid a validation error in chrome when entering decimals, the DecimalField template should specify

<input type="number" step="any" />

See: http://blog.isotoma.com/2012/03/html5-input-typenumber-and-decimalsfloats-in-chrome/

What I have done so far is this:

Added this to input.html:

{% if attrs.decimal %}step="any"{% endif %}

And created a new widget like this:

class DecimalInput(floppyforms.widgets.NumberInput):
    def __init__(self, *args, **kwargs):
        kwargs['attrs'] = {'decimal':True}
        super(DecimalWidget, self).__init__(*args, **kwargs)

Currently the documentation states "As for ModelForms, all the fields coming from the model still get a widget from django.forms and not from floppyforms, unless the widgets are overridden in the form’s Meta inner class." The reason for this is because Django has no officially sanctioned way for a form library to override this. The unofficial way would be to override the formfield_callback method but due to a quirk in Django's behavior, that gets lost in the inheritance chain.

There has been some discussion of how to best achieve this but no decisions have been made yet. We want to pick an implementation that is along the design path of Django itself.

The empty forms on a formset may have multiple extra empty forms. If one of the extra forms remains empty, but has any "required" fields, browsers that support HTML5 pre-submit validation (like Chrome) will refuse to submit the formset (even though it would be valid according to Django's logic.)

Django's admin doesn't have this problem because it just doesn't set the "required" attribute on any form fields. Maybe floppyforms should just do the same? Seems less complicated than the alternatives.

I have a Slider widget that was failing randomly. After spending several hours trying to find what was happening, I found that Input class turns True values into False. As you know, integer 1 equals to True in Python, therefore this code turns integers 1 into False. Thus my sliders where failing where value, min, max or step were equal to 1.

I've created a test and commented the lines that were breaking my Sliders. Even though all tests pass, you might want to change the code for your checked stuff.

One thing that I don't find very pythonic is the way True is checked:

if value == True:

Wouldn't it be better to do:

if value:

Cheers, Miguel

This tries to pull in various 1.11 fixes into one place, as well as test 1.11 properly

(This also reduces the scope of what the project tests to supported versions of Django)

Implementation of DateInput widget should render hardcoded "%Y-%m-%d" format.

1. In Django > 1.6 ISO formats are automatically appended to the list of input formats, unless they are not at first position. (see https://github.com/django/django/commit/90d3af380e8efec0301dd91600c6686232de3943)
2. floppyforms DateInput and DateTimeInput both uses first available format which is often not required "%Y-%m-%d" format. (https://github.com/gregmuellegger/django-floppyforms/blob/master/floppyforms/widgets.py#L279)

This renders date input as empty in browsers that support date html5 type, requiring user to enter date again:

<input type="date" name="date_of_birth" value="10.07.2014" required="" class="dateinput form-control" id="id_date_of_birth">

That in chrome renders as "dd/mm/yyyy" instead of "10/07/2014", client validation will not allow form to submit if it is required field and would set field to None if it is not required field, thus loosing information.

I propose that DateInput widget always render value in rfc3339 format.

Reference: https://github.com/gregmuellegger/django-floppyforms/issues/27

There are small typos in:

• docs/customization.rst
• docs/differences.rst
• floppyforms/static/floppyforms/js/MapWidget.js

Fixes:

• Should read seamlessly rather than seemlesly.
• Should read returned rather than returnes.
• Should read attributes rather than attibutes.

Semi-automated pull request generated by https://github.com/timgates42/meticulous/blob/master/docs/NOTE.md

Synced local file(s) with jazzband/.github.

This PR was created automatically by the repo-file-sync-action workflow run #2377882046

i am trying to draw polygon on using floppy-form map in geodjango is there a way by which i can restrict user to draw polygon in certain restricted area using map_options

in short i want to know how so i set map boundaries extent using JavaScript code for floppy form i know there is option for that in geodjango floppyform : "map_options"

but i don't know how do i set that can someone help me ?

Hi i am new to geodjango floppyform, i have some difficulty i working on application where i need to restrict user to create point or line-string(route) withing certain geofence(city), so in short while user creating route map would allow to create point and linestring (route) in certain regien by keeping other part of map disabled ? e.g i want to make entry for bust stop as a point A but while creating i want to restrict user so that point should be created in "XYZ" city region of the map only, it should not allow user to create any entry out of the bbox of XYZ city, is it possible ? can someone please guide me ? my map contain 100 such cities

https://github.com/gregmuellegger/django-floppyforms/issues/189

If don't want to use django's gis feature. Can disable to add FLOPPY_FORMS_USE_GIS = False option. It's simple fetch.