|
Re: new API Ref up: msg#00492web.dojo.devel
I assume you're referring to the "pre" formatting (indentation and newlines) of the dojo.event.connect examples in that function. The parser is outputting the "summary" in the "local/json" output without newlines or any new line markers, and smooshing all the white space, so there's nothing I can do in the front end at this point. What I suggest is this: 1) we come up with a convention to indicate "this is a code block" in comments 2) the parser encodes newlines as "\n" and leaves in spaces in summary/description blocks (like it does with src blocks) 3) the front end will strip out all newlines except those that sit inside a code block, and will <pre> (at least) the code blocks. Alternatively, we could define an "example" keyword, like the summary/ description/etc keywords, which would be treated just like the "src" block. It's not as flexible, but would be easy to do. Separating out the examples from the summary would be nice from a visual standpoint when the API viewer is in "summary" mode. Also, Alex, I recommend that extended text like that go in a "description" block rather than "summary." Thoughts? Neil? thanks O ------------------------- Whenever I despair, I remember that the way of truth and love has always won. There may be tyrants and murderers, and for a time, they may seem invincible, but in the end, they always fail. Think of it: always. -- Mohandas K. Ghandi On Oct 29, 2006, at 11:10 PM, Alex Russell wrote: Is there some way to get some block of formatting preserved from the |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: documenting widgets was: release 0.4.1 bugtriage: 00492, Tom Trenka |
|---|---|
| Next by Date: | Re: new API Ref up: 00492, Owen Williams |
| Previous by Thread: | Re: new API Ref upi: 00492, Owen Williams |
| Next by Thread: | Re: new API Ref up: 00492, Neil Roberts |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |