Closed (fixed)
Project:
Scald: Media Management made easy
Version:
7.x-1.x-dev
Component:
Provider: image
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
18 Feb 2015 at 17:49 UTC
Updated:
21 Mar 2015 at 13:54 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
nagy.balint commentedHere is a patch that achieves that.
(There could be a follow up issue to solve the pluggability of these atom properties. As currently there is even a problem with backward compatibility. Basically if a provider wants to add a new atom property, it has to be written for both the old way of embed and the new. Which is unnecessary duplication.)
Comment #2
gifad commentedHi nagy.balint,
ok for your patch;
now about pluggability of these atom properties :
1 - the name of "Atom properties" is wrong : there are "Atom embedding options"
2 - those options do not come from nowhere : they are implemented in either an atom provider, or a scald player, or a context provider;
3 - so the show/hide status of each option can be set if we know the rendering path that the atom will follow in scald_render();
the attached little patch sets a Drupal.settings.dnd.contexts_config to make this tracking possible (if not easy)
(this is the raw output of scald_context_config_load($context))
additionally, it adds Drupal.dnd.Atoms[id].meta.provider
NB: this makes sense only in the "new" (embed_div) storage method, where the "options" field can travel transparently all the rendering steps
Comment #3
jcisio commentedThe first patch is ok to me, but the second is not complete: is there anything to do on the JS side? Could we merge into a single patch?
Comment #5
jcisio commentedI think again and decide to commit #1. About #2, it will be a separate issue: to show the link option for other providers that support it.
Comment #6
gifad commentedThis is Pluggable Options for Atom Properties