Ticket #2531184 (accepted task)
Reporter  Eric Ferraiuolo |
Opened: 09/22/11 Last modified: 07/20/12 Status: accepted Type: task |
Owner Jeff Conniff |
Target Release: FUTURE Priority: P3 (normal) |
|---|---|---|---|
| Summary: | Path Drawing Utility example is missing full source on example page | ||
| Description: | http://stage.yuilibrary.com/yui/docs/graphics/graphics-pathutility.html All the examples have the full source pretty-printed on the example page, but the source is missing from this one. |
||
| Type: | task | Observed in Version: | development master |
| Component: | Graphics | Severity: | S3 (normal) |
| Assigned To: | Jeff Conniff | Target Release: | FUTURE |
| Location: | Website | Priority: | P3 (normal) |
| Tags: | Relates To: | ||
| Browsers: | N/A | ||
| URL: | |||
| Test Information: | |||
Change History
|
Posted: 09/22/11
|
|
Posted: 09/23/11
|
|
Posted: 09/26/11
Maybe we have this as a tool linked off of the user guide, but not as an example per se? |
|
Posted: 10/31/11
|
|
Posted: 10/31/11
I had a conversation with Ryan. He's not certain a side-box for utilities is the right solution. Reassigning to him to find the right solution with Jenny |
|
Posted: 11/9/11
|
|
Posted: 11/28/11
What's status on this one? |
|
Posted: 11/28/11
I'd like to make it possible for documentation templates to define content that should appear in the sidebar, but in a freeform way rather than as hard-coded support for a "utilities" sidebox. Giving documentation writers control over adding content to the sidebar makes sense, but adding a specific "utilities" category with baked-in metadata support would be of limited usefulness since it wouldn't serve any purpose for most components. I don't have time to do this work during sprint 1, and may not have time before sprint 3. In the meantime, documentation pages that want to link to "utilities" and treat them separately from examples should put these links in the main content area, perhaps under a heading labeled "Utilities". |
|
Posted: 11/28/11
Gotcha, makes sense. So to clarify, is this bug blocked by code changes to Selleck? |
|
Posted: 11/28/11
Yep, although I think the workaround I mentioned above should be enough to hold people over for now. |
|
Posted: 11/28/11
Waiting for https://github.com/rgrove/selleck/issues/6. Backlog for 3.5.0 should be sufficient. |
|
Posted: 11/29/11
|
|
Posted: 12/2/11
I did the workaround. |
|
Posted: 12/2/11
workaround for #2531184. Changed Graphics path utility from example to a section on the page with a header |
|
Posted: 12/6/11
workaround for #2531184. Changed Graphics path utility from example to a section on the page with a header |
|
Posted: 01/4/12
|
|
Posted: 05/29/12
Blocked by Selleck bug. Let's track loosely for now and not assign to any release/sprint. |
|
Posted: 07/20/12
|
This would be 400 - 500 lines of code.
I was thinking of this as a utility for developers to more easily generate Graphics code, rather than example code like the others.
I'm inclined not to add the code on the page. I'll ask Tripp what he thinks.