Welcome, Guest
Username: Password: Remember me
  • Page:
  • 1

TOPIC:

JSON fields not rendered by the builder 16 Mar 2017 18:37 #15043

  • vlemos
  • vlemos's Avatar Topic Author
  • Offline
  • Elite Member
  • Elite Member
  • Posts: 295
  • Thank you received: 41
JSON fields no longer rendered by the builder :ohmy:

Please Log in or Create an account to join the conversation.

JSON fields not rendered by the builder 11 May 2017 16:25 #15126

  • admin
  • admin's Avatar
  • Offline
  • Administrator
  • Administrator
  • Chef
  • Posts: 3711
  • Thank you received: 986
This is normal,
JSON has never been rendered, it is simply a helper at the moment.

In future, JSON field will propose :
- a sub form in the FORM
- a sub layout in the FLY
- a sub layout in the GRID

At the moment, when you instance a JSON field it simply place this code in populateObjects()
if (!empty($item->my_object_json) && is_string($item->my_object_json))
{
	$registry = new JRegistry;
	$registry->loadString($item->my_object_json);
	$item->my_object_json = $registry->toObject();
}

And in save() :
if (isset($data['my_object_json']) && is_array($data['my_object_json']))
{
	$registry = new JRegistry;
	$registry->loadArray($data['my_object_json']);
	$data['my_object_json'] = (string) $registry;
}

Simply a coder/decoder. Nothing else.
I should explain it better in the docs.

Note : The docs are under construction, I am currently creating that,
I will release it during 2017. It is gonna be beautiful, but it is a long way.
Coding is now a piece of cake
The following user(s) said Thank You: vlemos

Please Log in or Create an account to join the conversation.

Last edit: by admin.
  • Page:
  • 1
Time to create page: 0.075 seconds

I jumped and started to work on a demo component... but 2 days later this demo component became the real component. I just showed today the end result to my customer and he turned to me and said... "this is more than I expected"... All of this is because Cook did cut about 70% of my work and provided me more ways to improve the usability of the component. The end result was 17 tables all related between than to generate a full dashboard for the travel agents. Thanks for Cook developers for such great tool. This component would not be possible to be done at short time with all the features in it
Griiettner (Forum)  

Get Started