[MGNLIMG-81] Provide link generator Created: 08/Apr/11 Updated: 04/Nov/15 Resolved: 04/Nov/15 |
|
| Status: | Closed |
| Project: | Imaging |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.x |
| Type: | New Feature | Priority: | Neutral |
| Reporter: | Magnolia International | Assignee: | Magnolia International |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Template: |
|
||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||
| Date of First Response: | |||||||||||||
| Description |
|
Creating a url to a generated image is currently cumbersome, as one needs to know gory details of how the paths are decoded in the ParameterProviderFactory corresponding to the generator they want; all that should be required of a client api to get a link to a generated image is the generator name and its parameter (i.e a node or property, usually) This could probably be simplified if the ImagingServlet was a SelfMappingServlet. ImagingTemplatingFunctions will probably also be impacted. |
| Comments |
| Comment by Christopher Zimmermann [ 05/Dec/13 ] |
|
If you are not using STK - it should still be convenient to use. |
| Comment by Michael Mühlebach [ 04/Nov/15 ] |
|
Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes. |