[dojo-contributors] rstwiki / ref-guide / moinmoin updates - for 1.6?

Peter Higgins dante at dojotoolkit.org
Wed Mar 2 09:28:22 EST 2011


Yes, keep using the Wiki at docs.dojocampus.org ... In fact, the "new 
wiki" should be a drop-in replacement for the moin wiki, so you won't 
really even notice that it changed (minus styles and speed).

We are NOT able to edit directly from the rst files YET. I will alert 
the world once this portion is complete and tested.

~phiggins

On 3/2/11 8:46 AM, Evan Huang wrote:
> Sorry if I've missed this in the context,  so for 1.6 I suppose we
> will still use the current campus doc site? e.g.
> http://docs.dojocampus.org/dojox
>
> Was trying to update Grid section with the latest changes/new
> features, seems the live samples are not running against our latest
> trunk or 1.6 (or am I missed anything?)  I will go ahead with the text
> updates first though.
>
> Thanks!
>
> - Evan
>
> 2011/2/22 Torrey Rice<itorrey at gmail.com>:
>> Do we plan to roll this out before/during the 1.6 release?
>> Pete, let's sync up tomorrow in IRC on this.
>> -Torrey
>> On Feb 21, 2011, at 7:21 PM, Bill Keese wrote:
>>
>> Sounds great.
>>
>>> Can limit these
>>> to individual sections. The above shows everything, the following only
>>> shows example blocks and a call signature, if they exist:
>>>
>>> .. api-inline :: dojo.byId
>>>       :examples:
>>>       :signature:
>>>
>> Looks good, I assume :summary: and :description: are possible filters too.
>>
>>> The thinking here is that we have no use for a "version selection"
>>> dropdown. The wiki will run trunk, the /reference-guide/ will run
>>> whatever /current-stable/ is, the wiki docs will target trunk so needs a
>>> recent dojo/ tree, and /ref-guide/ will ship a dojo/ tree so this will
>>> always remain working.
>> Makes sense.    We can branch the docs the same way that we branch the
>> source code. (Specifically, have a 1.6.0/ tag and if necessary a 1.6/
>> branch.)
>>
>>> dmachi even went so far as to say we drop the
>>> iframe in CodeGlass and just execute the .. code-example :: blocks in
>>> the context of the current page. Thoughts on that?
>> I guess that makes sense.
>>
>>> Now, the sample code is displayed INLINE with a collapse button offset.
>> That makes sense, the example code is the most important part of our
>> documentation; it should not be hidden, at least not initially / by default.
>>
>>>      .. js ::
>>>
>>>          alert("foo");
>>>
>>>      This is the css:
>>>
>>>      .. css ::
>>>
>>>          #main { color:blue }
>>>
>>> ... notice the lack of wrapping<script>  and<style>  tags
>>> for the .. js and .. css directives. I felt they were redundant and
>>> unnecessary cruft.
>> Great, that's an improvement.
>>
>> _______________________________________________
>> dojo-contributors mailing list
>> dojo-contributors at mail.dojotoolkit.org
>> http://mail.dojotoolkit.org/mailman/listinfo/dojo-contributors
>>
>>
>> _______________________________________________
>> dojo-contributors mailing list
>> dojo-contributors at mail.dojotoolkit.org
>> http://mail.dojotoolkit.org/mailman/listinfo/dojo-contributors
>>
>>
> _______________________________________________
> dojo-contributors mailing list
> dojo-contributors at mail.dojotoolkit.org
> http://mail.dojotoolkit.org/mailman/listinfo/dojo-contributors



More information about the dojo-contributors mailing list