kirby-deprecated-plugins / field-engineer Goto Github PK

If you delete a field and leave the page without saving, the field will still be there.
It should not be there and the sign "You have unsaved changes" should be visible.

This feature should be a bit different than how it works with structure.

• Write out labels on the top, like table headings.
• Skip to generate labels on each row.

Require to use width to specify how much space each "cell" takes. No magic.

This is a weird one: when you hit save, only the characters that you actually typed are retained, not the autocomplete suggestion that you selected.

A warning before delete is important because an engineer "wrapper" can not only contain multiple field and multiple fieldsets, but also multiple nested levels. A delete action can delete a lot, depending on the structure.

The field textarea is only working without buttons.
If I try to use buttons e.g.:

type: textarea
buttons:
  - bold

I get with c::set('engineer.debug', true); an Undefined index: _level error and the panel is broken.
With c::set('engineer.debug', false); the right side of the panel is just blank.

Hi, I’m new to Kirby, and i have to build a website that lets you insert tables mixed with other kinds of data.

To achieve this i’m trying to use field-engineer in combination with tablex.
I managed to display the table in the field-engineer 's row with a small addition to trigger.js, now when i check the saved data, of course the tableX structure (header: … ; table: …rows…) is lost.

I want to solve this and eventually make a PR out of it.

Where does the writing and loading of the data occour?
Do you have any ideas on how to perform the writing and loading in the case of a tableX in field-engineer?

Any informaton is greatly appreciated, thak you in advance!

When I try to use field-engineer within a kirby-visual-markdown
(https://github.com/JonasDoebertin/kirby-visual-markdown) I can't save informations in the field with the markdown-type. Has anyone any idea how it could work?

Uppercase is allowed in a blueprint for default field names, but any uppercase characters in the engineer field name breaks the panel interface: the Add button stops working.

For some reason it's always english right now. Try to find a nice way to use translated labels.

https://getkirby.com/docs/panel/blueprints/form-fields#translating-form-fields

Hi,

Great plugin, I'm currently evaluating for a project.
It seems the plugin is not able to work with global field definitions in blueprints, as described in https://getkirby.com/docs/panel/blueprints/global-field-definitions

So something like myimage: imageselect is not working within a field definition inside an engineer field and just producesIllegal string offset 'type' as an error.

Do you think that would be possible?

Kind regards,
Georg

The default option for nested page fields does not work.

Just like the structure field

I you sort fields and leave the page without saving, all order are lost.
It does not save the sorting order.

https://github.com/TimOetting/kirby-list-field

At the moment it does not add the data correctly. Not sure why but I've added a strange discovery here:
TimOetting/kirby-list-field#8

• DOM update trigger
• Trigger render on enter

Do we want to have a readonly blueprint option? In that case, if readonly is set on the parent, every child of that parent also needs to be readonly.

I get this error if I try to use a engineer field in my blueprints:

Parse error: parse error, expecting "identifier (T_STRING)"' in /Users/Sites/..../site/plugins/field-engineer/lib/presentation.php on line 91

I'm on Kirby 2.5 with PHP 5.6.30

I tried this example.

Hello Jens,
how can I buy a license?
And is there a advanced license available for selling this field with an template?

Cheers

Every field is supported but when DOM changes it needs to trigger js of js plugins to work.

The plugins that will be supported needs to add something new to the table. At the same time well maintained. Fields with modals or field controllers does not yet work so the fields should be more simple ones.

Future / Maybe

• https://github.com/AugustMiller/kirby-map-field
• https://github.com/distantnative/field-multiselect
• https://github.com/ian-cox/Kirby-Color-Picker
• https://github.com/JonasDoebertin/kirby-visual-markdown - Does not load DOM js correctly after add
• https://github.com/storypioneers/kirby-wysiwyg - Does not trigger keyup
• https://github.com/storypioneers/kirby-selector
• https://github.com/TimOetting/kirby-gallery
• https://github.com/Thiousi/kirby-color-list - Saves but does not select a color

Maybe

• https://github.com/floriankarsten/kirby-tablex
• https://github.com/JonasDoebertin/kirby-range-slider
• https://github.com/jenstornell/kirby-keyword-map
• https://github.com/TimOetting/kirby-list-field

i do not care so much about general validation ability but regex i would love to see. otherwise i could not use this plugin for complex pages.

you could use the parsley.js lib to validate in panel based on regex expressions.
i usually forward the blueprint regex to my frontend form with parsley. worked well so far.

When I try to use field-engineer within a builder field I get 'undefined index'. Has anyone got this plugin working with kirby builder?

https://forum.getkirby.com/t/using-form-class-makes-base-field-unaware-of-the-page-object/7234

For example the image field. It works fine to clone, DOM updates correctly on that field but drag and drop does not.

But after save it works of cause.

Radiobutton error on cloning.
The fieldset that was cloned loses the value of the radiofield!

When engineer.debug is true a set of blueprints should be registered.

• Blueprint with all supported plugin fields.
• Blueprint with nesting.
• Blueprint with grid (width).
• Blueprint with blueprint settings.

Maybe it's possible to combine some of them.