1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
|
%global _empty_manifest_terminate_build 0
Name: python-DynamicForms
Version: 0.70.11
Release: 1
Summary: DynamicForms performs all the visualisation & data entry of your DRF Serializers & ViewSets and adds some candy of its own: It is a django library that gives you the power of dynamically-shown form fields, auto-filled default values, dynamic record loading and similar candy with little effort. To put it differently: once defined, a particular ViewSet / Serializer can be rendered in multiple ways allowing you to perform viewing and authoring operations on the data in question.
License: BSD-3-Clause
URL: https://github.com/velis74/DynamicForms
Source0: https://mirrors.nju.edu.cn/pypi/web/packages/32/cd/3793c18eecfc9a13c13de7b470619bebae49e04053adfd43d4238bb57297/DynamicForms-0.70.11.tar.gz
BuildArch: noarch
Requires: python3-six
Requires: python3-pytz
Requires: python3-coreapi
Requires: python3-django
Requires: python3-djangorestframework
Requires: python3-django-filter
Requires: python3-django-enumfields
Requires: python3-jsonschema
Requires: python3-pillow
Requires: python3-django-cors-headers
Requires: python3-versio
Requires: python3-typing
%description
# Notice to users of this library
Releases 0.50.x and 0.70.x are interim releases with which we prepare the stage for 1.x release.
0.50.x moves all "existing" code to `dynamicforms_legacy` module. If you weren't following vue
development branches, you will need to change all imports in python to this "new" module.
This is done to keep legacy code still running as existing code is transitioned to vue-based approach. Unless there is
significant interest, we will remove this module with 1.x release.
0.70.x re-introduces `dynamicforms` module, but this time refactored to only provide .componentdef OPTIONS +
payload data responses needed by the vue front-end library. This will hopefully be refactored to be more OpenAPI
compatible. The new primary branch is now `main`.
HTML renderers will no longer be supported and have been removed from the "new" dynamicforms module. It was too slow
and required too many hacks to remain viable. So we moved to Vue. The components in 0.70 will be vue3, vuetify3, vite
and typescript-compatible. We're in final stages of adapting to the new stack. Some inputs and some table functionality
isn't working yet.
We're keeping the Bootstrap stubs too, but not actively developing to support seamless selection of the two frameworks.
If there is interest to support CSS frameworks other than Vuetify, pull requests welcome. Hopefully the stubs should
point the way on how to do it.
Migration path is thus:
- Upgrade to dynamicforms \>= 0.50.3
- replace all dynamicforms imports with dynamicforms_legacy
- because of the rename, there is a bit of work required in settings.py so that Django can find the templates and
filters:
``` python
from dynamicforms_legacy import __file__ as DYNAMICFORMS_BASEDIR_FILE
DYNAMICFORMS_BASEDIR = os.path.dirname(DYNAMICFORMS_BASEDIR_FILE)
...
INSTALLED_APPS = [
...
'dynamicforms_legacy'
TEMPLATES = [
...
'DIRS': [
os.path.join(DYNAMICFORMS_BASEDIR, 'templates'),
...
'OPTIONS': {
...
'libraries': {
'dynamicforms': 'dynamicforms_legacy.templatetags.dynamicforms',
}
STATICFILES_DIRS = [
...
os.path.join(DYNAMICFORMS_BASEDIR, 'static'),
]
```
- replace any javascript dynamicforms progress calls with progress-legacy
- all other javascript code remains the same (including the dynamicforms object with support functions)
- check that everything still works
- Upgrade dynamicforms to \>= 0.70.1
- Start migration to Vue front-end and the new backend
# What is DynamicForms?
DynamicForms wants to eliminate HTML form boilerplate for generic tables & forms. Specifying a single DRF Serializer /
ViewSet and possibly desired form layout instantly provides both HTML renders and JSON renders (and anything else DRF
supports) keeping you free to implement your project.
There are two parts to DanymicForms:
- Django / DRF extensions providing the JSON definitions for on-screen objects
- HTML / Javascript component library providing the visualisation
It performs all the visualisation & data entry of your DRF Serializers & ViewSets and adds some candy of its own: It is
a [django](https://www.djangoproject.com/) library that gives you the power of dynamically-shown form fields,
autofilled default values, dynamic record loading and similar candy with little effort. To put it differently: once
defined, a particular ViewSet / Serializer can be rendered in multiple ways allowing you to perform viewing and
authoring operations on the data in question.
It is based on
[django-rest-framework](http://www.django-rest-framework.org/)
Documentation [on readthedocs](https://dynamicforms.readthedocs.io/)
## Why DynamicForms
- Turn your rest-framework ViewSets into HTML tables & forms
- Powerful HTML based CRUD
- Support for fetching "new" records
- Render to table, form or dialog, with plenty of customisation options
- Full nested data support
- Dynamically display & hide fields based on other fields' values
- Easily add actions and place the buttons to execute them anywhere you like
- Clear separation of list & dialog templates
- Dynamic loading of additional records for table views supported by infinite scroll
- Responsive tables (multiple table layouts for various screen widths)
- Easy implementation of filtering
- Action items, declared globally, placed where you need them
- Custom templates whenever & wherever you want them
- Support for form validation, will show errors even if they are not tied to a field
- Progress dialog for long lasting ajax operations
%package -n python3-DynamicForms
Summary: DynamicForms performs all the visualisation & data entry of your DRF Serializers & ViewSets and adds some candy of its own: It is a django library that gives you the power of dynamically-shown form fields, auto-filled default values, dynamic record loading and similar candy with little effort. To put it differently: once defined, a particular ViewSet / Serializer can be rendered in multiple ways allowing you to perform viewing and authoring operations on the data in question.
Provides: python-DynamicForms
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-pip
%description -n python3-DynamicForms
# Notice to users of this library
Releases 0.50.x and 0.70.x are interim releases with which we prepare the stage for 1.x release.
0.50.x moves all "existing" code to `dynamicforms_legacy` module. If you weren't following vue
development branches, you will need to change all imports in python to this "new" module.
This is done to keep legacy code still running as existing code is transitioned to vue-based approach. Unless there is
significant interest, we will remove this module with 1.x release.
0.70.x re-introduces `dynamicforms` module, but this time refactored to only provide .componentdef OPTIONS +
payload data responses needed by the vue front-end library. This will hopefully be refactored to be more OpenAPI
compatible. The new primary branch is now `main`.
HTML renderers will no longer be supported and have been removed from the "new" dynamicforms module. It was too slow
and required too many hacks to remain viable. So we moved to Vue. The components in 0.70 will be vue3, vuetify3, vite
and typescript-compatible. We're in final stages of adapting to the new stack. Some inputs and some table functionality
isn't working yet.
We're keeping the Bootstrap stubs too, but not actively developing to support seamless selection of the two frameworks.
If there is interest to support CSS frameworks other than Vuetify, pull requests welcome. Hopefully the stubs should
point the way on how to do it.
Migration path is thus:
- Upgrade to dynamicforms \>= 0.50.3
- replace all dynamicforms imports with dynamicforms_legacy
- because of the rename, there is a bit of work required in settings.py so that Django can find the templates and
filters:
``` python
from dynamicforms_legacy import __file__ as DYNAMICFORMS_BASEDIR_FILE
DYNAMICFORMS_BASEDIR = os.path.dirname(DYNAMICFORMS_BASEDIR_FILE)
...
INSTALLED_APPS = [
...
'dynamicforms_legacy'
TEMPLATES = [
...
'DIRS': [
os.path.join(DYNAMICFORMS_BASEDIR, 'templates'),
...
'OPTIONS': {
...
'libraries': {
'dynamicforms': 'dynamicforms_legacy.templatetags.dynamicforms',
}
STATICFILES_DIRS = [
...
os.path.join(DYNAMICFORMS_BASEDIR, 'static'),
]
```
- replace any javascript dynamicforms progress calls with progress-legacy
- all other javascript code remains the same (including the dynamicforms object with support functions)
- check that everything still works
- Upgrade dynamicforms to \>= 0.70.1
- Start migration to Vue front-end and the new backend
# What is DynamicForms?
DynamicForms wants to eliminate HTML form boilerplate for generic tables & forms. Specifying a single DRF Serializer /
ViewSet and possibly desired form layout instantly provides both HTML renders and JSON renders (and anything else DRF
supports) keeping you free to implement your project.
There are two parts to DanymicForms:
- Django / DRF extensions providing the JSON definitions for on-screen objects
- HTML / Javascript component library providing the visualisation
It performs all the visualisation & data entry of your DRF Serializers & ViewSets and adds some candy of its own: It is
a [django](https://www.djangoproject.com/) library that gives you the power of dynamically-shown form fields,
autofilled default values, dynamic record loading and similar candy with little effort. To put it differently: once
defined, a particular ViewSet / Serializer can be rendered in multiple ways allowing you to perform viewing and
authoring operations on the data in question.
It is based on
[django-rest-framework](http://www.django-rest-framework.org/)
Documentation [on readthedocs](https://dynamicforms.readthedocs.io/)
## Why DynamicForms
- Turn your rest-framework ViewSets into HTML tables & forms
- Powerful HTML based CRUD
- Support for fetching "new" records
- Render to table, form or dialog, with plenty of customisation options
- Full nested data support
- Dynamically display & hide fields based on other fields' values
- Easily add actions and place the buttons to execute them anywhere you like
- Clear separation of list & dialog templates
- Dynamic loading of additional records for table views supported by infinite scroll
- Responsive tables (multiple table layouts for various screen widths)
- Easy implementation of filtering
- Action items, declared globally, placed where you need them
- Custom templates whenever & wherever you want them
- Support for form validation, will show errors even if they are not tied to a field
- Progress dialog for long lasting ajax operations
%package help
Summary: Development documents and examples for DynamicForms
Provides: python3-DynamicForms-doc
%description help
# Notice to users of this library
Releases 0.50.x and 0.70.x are interim releases with which we prepare the stage for 1.x release.
0.50.x moves all "existing" code to `dynamicforms_legacy` module. If you weren't following vue
development branches, you will need to change all imports in python to this "new" module.
This is done to keep legacy code still running as existing code is transitioned to vue-based approach. Unless there is
significant interest, we will remove this module with 1.x release.
0.70.x re-introduces `dynamicforms` module, but this time refactored to only provide .componentdef OPTIONS +
payload data responses needed by the vue front-end library. This will hopefully be refactored to be more OpenAPI
compatible. The new primary branch is now `main`.
HTML renderers will no longer be supported and have been removed from the "new" dynamicforms module. It was too slow
and required too many hacks to remain viable. So we moved to Vue. The components in 0.70 will be vue3, vuetify3, vite
and typescript-compatible. We're in final stages of adapting to the new stack. Some inputs and some table functionality
isn't working yet.
We're keeping the Bootstrap stubs too, but not actively developing to support seamless selection of the two frameworks.
If there is interest to support CSS frameworks other than Vuetify, pull requests welcome. Hopefully the stubs should
point the way on how to do it.
Migration path is thus:
- Upgrade to dynamicforms \>= 0.50.3
- replace all dynamicforms imports with dynamicforms_legacy
- because of the rename, there is a bit of work required in settings.py so that Django can find the templates and
filters:
``` python
from dynamicforms_legacy import __file__ as DYNAMICFORMS_BASEDIR_FILE
DYNAMICFORMS_BASEDIR = os.path.dirname(DYNAMICFORMS_BASEDIR_FILE)
...
INSTALLED_APPS = [
...
'dynamicforms_legacy'
TEMPLATES = [
...
'DIRS': [
os.path.join(DYNAMICFORMS_BASEDIR, 'templates'),
...
'OPTIONS': {
...
'libraries': {
'dynamicforms': 'dynamicforms_legacy.templatetags.dynamicforms',
}
STATICFILES_DIRS = [
...
os.path.join(DYNAMICFORMS_BASEDIR, 'static'),
]
```
- replace any javascript dynamicforms progress calls with progress-legacy
- all other javascript code remains the same (including the dynamicforms object with support functions)
- check that everything still works
- Upgrade dynamicforms to \>= 0.70.1
- Start migration to Vue front-end and the new backend
# What is DynamicForms?
DynamicForms wants to eliminate HTML form boilerplate for generic tables & forms. Specifying a single DRF Serializer /
ViewSet and possibly desired form layout instantly provides both HTML renders and JSON renders (and anything else DRF
supports) keeping you free to implement your project.
There are two parts to DanymicForms:
- Django / DRF extensions providing the JSON definitions for on-screen objects
- HTML / Javascript component library providing the visualisation
It performs all the visualisation & data entry of your DRF Serializers & ViewSets and adds some candy of its own: It is
a [django](https://www.djangoproject.com/) library that gives you the power of dynamically-shown form fields,
autofilled default values, dynamic record loading and similar candy with little effort. To put it differently: once
defined, a particular ViewSet / Serializer can be rendered in multiple ways allowing you to perform viewing and
authoring operations on the data in question.
It is based on
[django-rest-framework](http://www.django-rest-framework.org/)
Documentation [on readthedocs](https://dynamicforms.readthedocs.io/)
## Why DynamicForms
- Turn your rest-framework ViewSets into HTML tables & forms
- Powerful HTML based CRUD
- Support for fetching "new" records
- Render to table, form or dialog, with plenty of customisation options
- Full nested data support
- Dynamically display & hide fields based on other fields' values
- Easily add actions and place the buttons to execute them anywhere you like
- Clear separation of list & dialog templates
- Dynamic loading of additional records for table views supported by infinite scroll
- Responsive tables (multiple table layouts for various screen widths)
- Easy implementation of filtering
- Action items, declared globally, placed where you need them
- Custom templates whenever & wherever you want them
- Support for form validation, will show errors even if they are not tied to a field
- Progress dialog for long lasting ajax operations
%prep
%autosetup -n DynamicForms-0.70.11
%build
%py3_build
%install
%py3_install
install -d -m755 %{buildroot}/%{_pkgdocdir}
if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi
if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi
if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi
if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi
pushd %{buildroot}
if [ -d usr/lib ]; then
find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/lib64 ]; then
find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/bin ]; then
find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/sbin ]; then
find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst
fi
touch doclist.lst
if [ -d usr/share/man ]; then
find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst
fi
popd
mv %{buildroot}/filelist.lst .
mv %{buildroot}/doclist.lst .
%files -n python3-DynamicForms -f filelist.lst
%dir %{python3_sitelib}/*
%files help -f doclist.lst
%{_docdir}/*
%changelog
* Tue Apr 25 2023 Python_Bot <Python_Bot@openeuler.org> - 0.70.11-1
- Package Spec generated
|
