Hey all,

Now that the site links to static dumps of the docs, what's the
mechanism for editing? Are the exports cron'd?

Regards

Search Discussions

  • Torrey Rice at Feb 12, 2010 at 5:22 pm
    We're working on that now and will have the answer early next week.

    This version was done manually but our Phase 2 task is to make it automated in some fashion.

    On Feb 12, 2010, at 2:19 PM, Alex Russell wrote:

    Hey all,

    Now that the site links to static dumps of the docs, what's the
    mechanism for editing? Are the exports cron'd?

    Regards
    _______________________________________________
    dojo-contributors mailing list
    dojo-contributors at mail.dojotoolkit.org
    http://mail.dojotoolkit.org/mailman/listinfo/dojo-contributors
  • Adam Peller at Feb 12, 2010 at 5:30 pm
    So that means we can continue making our edits on campus, for the time being?
    On Fri, Feb 12, 2010 at 5:22 PM, Torrey Rice wrote:
    We're working on that now and will have the answer early next week.

    This version was done manually but our Phase 2 task is to make it automated in some fashion.

    On Feb 12, 2010, at 2:19 PM, Alex Russell wrote:

    Hey all,

    Now that the site links to static dumps of the docs, what's the
    mechanism for editing? Are the exports cron'd?

    Regards
    _______________________________________________
    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
  • Torrey Rice at Feb 12, 2010 at 5:32 pm
    Yeah we'll do another export either way since apparently we're out of date at the moment.

    On Feb 12, 2010, at 2:30 PM, Adam Peller wrote:

    So that means we can continue making our edits on campus, for the time being?
    On Fri, Feb 12, 2010 at 5:22 PM, Torrey Rice wrote:
    We're working on that now and will have the answer early next week.

    This version was done manually but our Phase 2 task is to make it automated in some fashion.

    On Feb 12, 2010, at 2:19 PM, Alex Russell wrote:

    Hey all,

    Now that the site links to static dumps of the docs, what's the
    mechanism for editing? Are the exports cron'd?

    Regards
    _______________________________________________
    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
  • Marcus Reimann at Feb 13, 2010 at 8:28 am
    The Wiki is good for editing and creating docs and we already have done
    a lot of new docs with the current Wiki installation. So, I don't think
    this will change (otherwise I would love to see a open discussion about
    other solutions).

    So, all we need is a Shell-Skript, which rsync with the current source
    directory of the Wiki and after that, start the build-run for the static
    docs. It's not voodoo, it's just a simple Shell Skript (and the
    installation of rsync on the server, which was planned anyway).

    Torrey, Dustin or Tobias: If you need help with this task, send me a note.

    Marcus



    Adam Peller wrote:
    So that means we can continue making our edits on campus, for the time being?

    On Fri, Feb 12, 2010 at 5:22 PM, Torrey Ricewrote:
    We're working on that now and will have the answer early next week.

    This version was done manually but our Phase 2 task is to make it automated in some fashion.


    On Feb 12, 2010, at 2:19 PM, Alex Russell wrote:

    Hey all,

    Now that the site links to static dumps of the docs, what's the
    mechanism for editing? Are the exports cron'd?
  • Tobias Klipstein at Feb 15, 2010 at 12:21 pm
    Hi everyone,

    because I mainly did the setup for the current reference guide I would like
    to say some words about the current structure and how the wiki on
    livedocs.dojotoolkit.org is transferred to the statically generated
    reference-guide.

    Just for better understanding, i would like to point out the two
    documentation systems we currently have. Both systems are using an extended
    restructured text markup (e.g. .. code-example, ...):

    Wiki
    ------
    On livedocs.dtk.otg we are using a moinmoin wiki, that has a simple
    folder/file structure for saving the documents and doing the versioning.

    Sphinx (static generation)
    -----------------------------------
    The other system is the respository at
    http://svn.dojotoolkit.org/dojo_doc_wiki/ where we are using the
    documentation system Sphinx (http://sphinx.pocoo.org/: written in Python and
    it is also used for writing the Python documentation) for generating the
    static documentation you currently see at
    http://dojotoolkit.org/reference-guide.


    For creating the static documentation I currently copy the "pages" directory
    of the wiki and use the script
    http://svn.dojotoolkit.org/dojo_doc_wiki/_addon/moinconverter.py to generate
    all files that can be consumed by the reference guide. Until this stage
    everything could be automated, but afterwards starts a manual task to
    cleanup the generated documents.

    That is because:
    - Both systems use a different method for linking
    - Sphinx has a concept for generating a Table-Of-Content

    Since release 1.3 I do this process for every new Dojo release and I did the
    last conversion at 2010/02/10.

    Because I really don't like having two systems and having a process
    inbetween to convert from one to another (even it could be automated), i
    would like to propose to get rid of the Wiki in the future.

    But before getting rid of that, I have to finish a WYSIWYG editor for
    restructured text, so that editing will be much easier.

    PROS for getting rid of the Wiki:
    -------------------------------------------
    - Just one system to maintain
    - Versions of the documentation could be aligned with the Dojo source code
    and also tagged with the same versions
    - Documentation bugs could be filed within Trac
    - Bulk editing of ReST documents is much easier (search + replace)
    - We could use the power of Sphinx for doing a complex TOC
    - Generating PDF, when the TOC is structured better
    - Not editing a large ReST document within a textarea (a doc editor could
    use his favourite text editor)

    CONS:
    ----------
    - Changes are not visible immediately to everyone
    - Enabling everyone to change documentation
    - Generated page is visible directly after editing

    For solving the two cons above I would recommend to create a new group
    called "Dojo documentation contributor", that are able to commit to the
    Sphinx SVN repository. All people who documented within the Wiki since a
    year and those that aren't Dojo committers already will get that role, so
    they will be able to make changes to the documentation. The problem with the
    immediate visibility isn't solvable, but for tackling that, an automatic
    generation could happen every hour. And the last con point on the list will
    be solved by an WYSIWYG editor.

    Until we decided that it would be good, if the Wiki is included in the Dojo
    backup (Dustin?) and I will continue doing the process of converting the
    Wiki to Sphinx, when there is a new Dojo version.

    Regards, Tobias

    2010/2/13 Marcus Reimann <marcus-nospam at dojotoolkit-forum.de>
    The Wiki is good for editing and creating docs and we already have done
    a lot of new docs with the current Wiki installation. So, I don't think
    this will change (otherwise I would love to see a open discussion about
    other solutions).

    So, all we need is a Shell-Skript, which rsync with the current source
    directory of the Wiki and after that, start the build-run for the static
    docs. It's not voodoo, it's just a simple Shell Skript (and the
    installation of rsync on the server, which was planned anyway).

    Torrey, Dustin or Tobias: If you need help with this task, send me a note.

    Marcus



    Adam Peller wrote:
    So that means we can continue making our edits on campus, for the time being?
    On Fri, Feb 12, 2010 at 5:22 PM, Torrey Ricewrote:
    We're working on that now and will have the answer early next week.

    This version was done manually but our Phase 2 task is to make it
    automated in some fashion.

    On Feb 12, 2010, at 2:19 PM, Alex Russell wrote:

    Hey all,

    Now that the site links to static dumps of the docs, what's the
    mechanism for editing? Are the exports cron'd?
    _______________________________________________
    dojo-contributors mailing list
    dojo-contributors at mail.dojotoolkit.org
    http://mail.dojotoolkit.org/mailman/listinfo/dojo-contributors
    -------------- next part --------------
    An HTML attachment was scrubbed...
    URL: http://mail.dojotoolkit.org/pipermail/dojo-contributors/attachments/20100215/ec6d9b18/attachment.htm
  • Jared Jurkiewicz at Feb 15, 2010 at 12:36 pm
    Frankly, I like the wiki. The more steps you put in in the way of
    those writing documentation (svn, checkin/out, etc), the less likely
    it is people will improve the documentation.

    A wiki is easy to use and anyone with a browser can do doc work.
    When you get to source control, you start putting more and more
    requirements on installed tools to test the output and so on, which is
    going to start cutting down on the group of people willing to spend
    time documenting.

    Sorry to say that, but it's true. If you make it harder for me to
    update docs, I'll be updating them less.

    -- Jared

    2010/2/15 Tobias Klipstein <tobias.klipstein at googlemail.com>:
    Hi everyone,

    because I mainly did the setup for the current reference guide I would like
    to say some words about the current structure and how the wiki on
    livedocs.dojotoolkit.org is transferred to the statically generated
    reference-guide.

    Just for better understanding, i would like to point out the two
    documentation systems we currently have. Both systems are using an extended
    restructured text markup (e.g.? .. code-example, ...):

    Wiki
    ------
    On livedocs.dtk.otg we are using a moinmoin wiki, that has a simple
    folder/file structure for saving the documents and doing the versioning.

    Sphinx (static generation)
    -----------------------------------
    The other system is the respository at
    http://svn.dojotoolkit.org/dojo_doc_wiki/ where we are using the
    documentation system Sphinx (http://sphinx.pocoo.org/: written in Python and
    it is also used for writing the Python documentation) for generating the
    static documentation you currently see at
    http://dojotoolkit.org/reference-guide.


    For creating the static documentation I currently copy the "pages" directory
    of the wiki and use the script
    http://svn.dojotoolkit.org/dojo_doc_wiki/_addon/moinconverter.py to generate
    all files that can be consumed by the reference guide. Until this stage
    everything could be automated, but afterwards starts a manual task to
    cleanup the generated documents.

    That is because:
    - Both systems use a different method for linking
    - Sphinx has a concept for generating a Table-Of-Content

    Since release 1.3 I do this process for every new Dojo release and I did the
    last conversion at 2010/02/10.

    Because I really don't like having two systems and having a process
    inbetween to convert from one to another (even it could be automated), i
    would like to propose to get rid of the Wiki in the future.

    But before getting rid of that, I have to finish a WYSIWYG editor for
    restructured text, so that editing will be much easier.

    PROS for getting rid of the Wiki:
    -------------------------------------------
    - Just one system to maintain
    - Versions of the documentation could be aligned with the Dojo source code
    and also tagged with the same versions
    - Documentation bugs could be filed within Trac
    - Bulk editing of ReST documents is much easier (search + replace)
    - We could use the power of Sphinx for doing a complex TOC
    - Generating PDF, when the TOC is structured better
    - Not editing a large ReST document within a textarea (a doc editor could
    use his favourite text editor)

    CONS:
    ----------
    - Changes are not visible immediately to everyone
    - Enabling everyone to change documentation
    - Generated page is visible directly after editing

    For solving the two cons above I would recommend to create a new group
    called "Dojo documentation contributor", that are able to commit to the
    Sphinx SVN repository. All people who documented within the Wiki since a
    year and those that aren't Dojo committers already will get that role, so
    they will be able to make changes to the documentation. The problem with the
    immediate visibility isn't solvable, but for tackling that, an automatic
    generation could happen every hour. And the last con point on the list will
    be solved by an WYSIWYG editor.

    Until we decided that it would be good, if the Wiki is included in the Dojo
    backup (Dustin?) and I will continue doing the process of converting the
    Wiki to Sphinx, when there is a new Dojo version.

    Regards, Tobias

    2010/2/13 Marcus Reimann <marcus-nospam at dojotoolkit-forum.de>
    The Wiki is good for editing and creating docs and we already have done
    a lot of new docs with the current Wiki installation. So, I don't think
    this will change (otherwise I would love to see a open discussion about
    other solutions).

    So, all we need is a Shell-Skript, which rsync with the current source
    directory of the Wiki and after that, start the build-run for the static
    docs. It's not voodoo, it's just a simple Shell Skript (and the
    installation of rsync on the server, which was planned anyway).

    Torrey, Dustin or Tobias: If you need help with this task, send me a note.

    Marcus



    Adam Peller wrote:
    So that means we can continue making our edits on campus, for the time
    being?

    On Fri, Feb 12, 2010 at 5:22 PM, Torrey Rice<itorrey at gmail.com> ?wrote:
    We're working on that now and will have the answer early next week.

    This version was done manually but our Phase 2 task is to make it
    automated in some fashion.


    On Feb 12, 2010, at 2:19 PM, Alex Russell wrote:

    Hey all,

    Now that the site links to static dumps of the docs, what's the
    mechanism for editing? Are the exports cron'd?
    _______________________________________________
    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
  • Bill Keese at Feb 15, 2010 at 2:41 pm
  • Tobias Klipstein at Feb 15, 2010 at 3:27 pm
    Hi Jared and Bill,

    just to be clear on that: livedocs.dojotoolkit.org == docs.dojotoolkit.org.
    Both domains point to the same wiki instance, so changes on
    livedocs.dojotoolkit.org will immediately be visibile at
    docs.dojotoolkit.org.

    Jared: i would like to write a WYSIWYG editor for ReST documents, so editing
    could still happen in the browser. The only difference would be that there
    needs to be a checkin via svn afterwards. Maybe that also could be done via
    a web-interface too (same as on the wiki at google code).

    My goal is to have a documentation system, that everyone can use for his own
    JS project and we are not really far away from that.

    Regards, Tobias

    2010/2/15 Bill Keese <bill at dojotoolkit.org>
    I'm confused, livedocs.dojotoolkit.org is just a rename of
    docs.dojotoolkit.org, right? I thought everything was already working
    automatically, because on docs.dojotoolkit.org I can see the page as soon
    as I hit the save button. Why do you need code converting from the dojo
    rest format into sphinx format? I can understand wanting to make a static
    copy of the doc, but can't you just copy the HTML from
    docs.dojotoolkit.org?

    Tobias Klipstein wrote:

    Hi everyone,

    because I mainly did the setup for the current reference guide I would like
    to say some words about the current structure and how the wiki on
    livedocs.dojotoolkit.org is transferred to the statically generated
    reference-guide.

    Just for better understanding, i would like to point out the two
    documentation systems we currently have. Both systems are using an extended
    restructured text markup (e.g. .. code-example, ...):

    Wiki
    ------
    On livedocs.dtk.otg we are using a moinmoin wiki, that has a simple
    folder/file structure for saving the documents and doing the versioning.

    Sphinx (static generation)
    -----------------------------------
    The other system is the respository at
    http://svn.dojotoolkit.org/dojo_doc_wiki/ where we are using the
    documentation system Sphinx (http://sphinx.pocoo.org/: written in Python
    and it is also used for writing the Python documentation) for generating the
    static documentation you currently see at
    http://dojotoolkit.org/reference-guide.


    For creating the static documentation I currently copy the "pages"
    directory of the wiki and use the script
    http://svn.dojotoolkit.org/dojo_doc_wiki/_addon/moinconverter.py to
    generate all files that can be consumed by the reference guide. Until this
    stage everything could be automated, but afterwards starts a manual task to
    cleanup the generated documents.

    That is because:
    - Both systems use a different method for linking
    - Sphinx has a concept for generating a Table-Of-Content

    Since release 1.3 I do this process for every new Dojo release and I did
    the last conversion at 2010/02/10.

    Because I really don't like having two systems and having a process
    inbetween to convert from one to another (even it could be automated), i
    would like to propose to get rid of the Wiki in the future.

    But before getting rid of that, I have to finish a WYSIWYG editor for
    restructured text, so that editing will be much easier.

    PROS for getting rid of the Wiki:
    -------------------------------------------
    - Just one system to maintain
    - Versions of the documentation could be aligned with the Dojo source code
    and also tagged with the same versions
    - Documentation bugs could be filed within Trac
    - Bulk editing of ReST documents is much easier (search + replace)
    - We could use the power of Sphinx for doing a complex TOC
    - Generating PDF, when the TOC is structured better
    - Not editing a large ReST document within a textarea (a doc editor could
    use his favourite text editor)

    CONS:
    ----------
    - Changes are not visible immediately to everyone
    - Enabling everyone to change documentation
    - Generated page is visible directly after editing

    For solving the two cons above I would recommend to create a new group
    called "Dojo documentation contributor", that are able to commit to the
    Sphinx SVN repository. All people who documented within the Wiki since a
    year and those that aren't Dojo committers already will get that role, so
    they will be able to make changes to the documentation. The problem with the
    immediate visibility isn't solvable, but for tackling that, an automatic
    generation could happen every hour. And the last con point on the list will
    be solved by an WYSIWYG editor.

    Until we decided that it would be good, if the Wiki is included in the Dojo
    backup (Dustin?) and I will continue doing the process of converting the
    Wiki to Sphinx, when there is a new Dojo version.

    Regards, Tobias

    2010/2/13 Marcus Reimann <marcus-nospam at dojotoolkit-forum.de>

    The Wiki is good for editing and creating docs and we already have done
    a lot of new docs with the current Wiki installation. So, I don't think
    this will change (otherwise I would love to see a open discussion about
    other solutions).

    So, all we need is a Shell-Skript, which rsync with the current source
    directory of the Wiki and after that, start the build-run for the static
    docs. It's not voodoo, it's just a simple Shell Skript (and the
    installation of rsync on the server, which was planned anyway).

    Torrey, Dustin or Tobias: If you need help with this task, send me a note.

    Marcus



    Adam Peller wrote:
    So that means we can continue making our edits on campus, for the time being?
    On Fri, Feb 12, 2010 at 5:22 PM, Torrey Ricewrote:
    We're working on that now and will have the answer early next week.

    This version was done manually but our Phase 2 task is to make it
    automated in some fashion.

    On Feb 12, 2010, at 2:19 PM, Alex Russell wrote:

    Hey all,

    Now that the site links to static dumps of the docs, what's the
    mechanism for editing? Are the exports cron'd?
    _______________________________________________
    dojo-contributors mailing list
    dojo-contributors at mail.dojotoolkit.org
    http://mail.dojotoolkit.org/mailman/listinfo/dojo-contributors


    ------------------------------

    _______________________________________________
    dojo-contributors mailing listdojo-contributors at mail.dojotoolkit.orghttp://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
    -------------- next part --------------
    An HTML attachment was scrubbed...
    URL: http://mail.dojotoolkit.org/pipermail/dojo-contributors/attachments/20100215/45621ab3/attachment.htm
  • Jared Jurkiewicz at Feb 15, 2010 at 3:32 pm
    Just always bear in mind:

    More steps == less people contributing.

    I'm not kidding. Barrier to entry on docs must be kept as low as
    possible as it isn't exactly a popular activity in the first place.
    Anything that makes it harder (even slightly), and people will quit.

    -- Jared


    2010/2/15 Tobias Klipstein <tobias.klipstein at googlemail.com>:
    Hi Jared and Bill,

    just to be clear on that: livedocs.dojotoolkit.org == docs.dojotoolkit.org.
    Both domains point to the same wiki instance, so changes on
    livedocs.dojotoolkit.org will immediately be visibile at
    docs.dojotoolkit.org.

    Jared: i would like to write a WYSIWYG editor for ReST documents, so editing
    could still happen in the browser. The only difference would be that there
    needs to be a checkin via svn afterwards. Maybe that also could be done via
    a web-interface too (same as on the wiki at google code).

    My goal is to have a documentation system, that everyone can use for his own
    JS project and we are not really far away from that.

    Regards, Tobias

    2010/2/15 Bill Keese <bill at dojotoolkit.org>
    I'm confused, livedocs.dojotoolkit.org is just a rename of
    docs.dojotoolkit.org, right??? I thought everything was already working
    automatically, because on docs.dojotoolkit.org I can see the page as soon as
    I hit the save button.??? Why do you need code converting from the dojo rest
    format into sphinx format??? I can understand wanting to make a static copy
    of the doc, but can't you just copy the HTML from docs.dojotoolkit.org?

    Tobias Klipstein wrote:

    Hi everyone,

    because I mainly did the setup for the current reference guide I would
    like to say some words about the current structure and how the wiki on
    livedocs.dojotoolkit.org is transferred to the statically generated
    reference-guide.

    Just for better understanding, i would like to point out the two
    documentation systems we currently have. Both systems are using an extended
    restructured text markup (e.g.? .. code-example, ...):

    Wiki
    ------
    On livedocs.dtk.otg we are using a moinmoin wiki, that has a simple
    folder/file structure for saving the documents and doing the versioning.

    Sphinx (static generation)
    -----------------------------------
    The other system is the respository at
    http://svn.dojotoolkit.org/dojo_doc_wiki/ where we are using the
    documentation system Sphinx (http://sphinx.pocoo.org/: written in Python and
    it is also used for writing the Python documentation) for generating the
    static documentation you currently see at
    http://dojotoolkit.org/reference-guide.


    For creating the static documentation I currently copy the "pages"
    directory of the wiki and use the script
    http://svn.dojotoolkit.org/dojo_doc_wiki/_addon/moinconverter.py to generate
    all files that can be consumed by the reference guide. Until this stage
    everything could be automated, but afterwards starts a manual task to
    cleanup the generated documents.

    That is because:
    - Both systems use a different method for linking
    - Sphinx has a concept for generating a Table-Of-Content

    Since release 1.3 I do this process for every new Dojo release and I did
    the last conversion at 2010/02/10.

    Because I really don't like having two systems and having a process
    inbetween to convert from one to another (even it could be automated), i
    would like to propose to get rid of the Wiki in the future.

    But before getting rid of that, I have to finish a WYSIWYG editor for
    restructured text, so that editing will be much easier.

    PROS for getting rid of the Wiki:
    -------------------------------------------
    - Just one system to maintain
    - Versions of the documentation could be aligned with the Dojo source code
    and also tagged with the same versions
    - Documentation bugs could be filed within Trac
    - Bulk editing of ReST documents is much easier (search + replace)
    - We could use the power of Sphinx for doing a complex TOC
    - Generating PDF, when the TOC is structured better
    - Not editing a large ReST document within a textarea (a doc editor could
    use his favourite text editor)

    CONS:
    ----------
    - Changes are not visible immediately to everyone
    - Enabling everyone to change documentation
    - Generated page is visible directly after editing

    For solving the two cons above I would recommend to create a new group
    called "Dojo documentation contributor", that are able to commit to the
    Sphinx SVN repository. All people who documented within the Wiki since a
    year and those that aren't Dojo committers already will get that role, so
    they will be able to make changes to the documentation. The problem with the
    immediate visibility isn't solvable, but for tackling that, an automatic
    generation could happen every hour. And the last con point on the list will
    be solved by an WYSIWYG editor.

    Until we decided that it would be good, if the Wiki is included in the
    Dojo backup (Dustin?) and I will continue doing the process of converting
    the Wiki to Sphinx, when there is a new Dojo version.

    Regards, Tobias

    2010/2/13 Marcus Reimann <marcus-nospam at dojotoolkit-forum.de>

    The Wiki is good for editing and creating docs and we already have done
    a lot of new docs with the current Wiki installation. So, I don't think
    this will change (otherwise I would love to see a open discussion about
    other solutions).

    So, all we need is a Shell-Skript, which rsync with the current source
    directory of the Wiki and after that, start the build-run for the static
    docs. It's not voodoo, it's just a simple Shell Skript (and the
    installation of rsync on the server, which was planned anyway).

    Torrey, Dustin or Tobias: If you need help with this task, send me a note.

    Marcus



    Adam Peller wrote:
    So that means we can continue making our edits on campus, for the time
    being?

    On Fri, Feb 12, 2010 at 5:22 PM, Torrey Rice<itorrey at gmail.com> ?wrote:
    We're working on that now and will have the answer early next week.

    This version was done manually but our Phase 2 task is to make it
    automated in some fashion.


    On Feb 12, 2010, at 2:19 PM, Alex Russell wrote:

    Hey all,

    Now that the site links to static dumps of the docs, what's the
    mechanism for editing? Are the exports cron'd?
    _______________________________________________
    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

    _______________________________________________
    dojo-contributors mailing list
    dojo-contributors at mail.dojotoolkit.org
    http://mail.dojotoolkit.org/mailman/listinfo/dojo-contributors
  • Marcus Reimann at Feb 16, 2010 at 2:05 pm
    Hi Tobias,
    Am 15.02.2010 17:21, Tobias Klipstein wrote:

    Since release 1.3 I do this process for every new Dojo release and I
    did the last conversion at 2010/02/10.
    But, it's obvious that there are a lot of outdated pages within this
    generated pages. For example look at

    * http://docs.dojocampus.org/dojox/form/FileUploader - trutwijd
    added a note on http://bugs.dojotoolkit.org/ticket/10576 at
    2009-12-31 16:52:59 vs
    http://dojotoolkit.org/reference-guide/dojox/form/FileUploader.htm
    - no such note
    * http://docs.dojocampus.org/dojo/objectToQuery - it was corrected
    at 2009-12-30 21:17:35 vs.
    http://dojotoolkit.org/reference-guide/dojo/objectToQuery.html -
    still the wrong title
    * http://docs.dojocampus.org/dojo/fx/slideTo - it was corrected at
    2010-01-14 23:15:40 vs.
    http://dojotoolkit.org/reference-guide/dojo/fx/slideTo.html -
    still the wrong text with "wipeIn" instead of "slideTo".
    * Some additional examples: dojo/style
    dijit/Tooltip Dialog
    dijit/Tree
    dijit/Toolbar
    dijit/TitlePane
    dijit/Progress Bar
    dijit/MenuBar
    dijit/Menu
    dijit/Declaration
    dijit/Color Palette
    dijit/Calendar
    dijit-a11y-statement
    dijit-a11y-req
    quickstart/writing Widgets/a11y Testing
    quickstart/writing Widgets/a11y
    dijit-a11y-resources
    dijit-a11y-strategy
    dijit-a11y
    dijit/_Widget
    dijit/_Templated
    dijit/info
    dijit/layout/Tab Container
    dijit/layout/Content Pane
    dijit/layout/Border Container
    dijit/layout/Accordion Container
    dijit/layout/_Layout Widget
    dijit/layout
    dijit/form/Slider
    dijit/form/Radio Button
    dijit/form/Form
    dijit/form/Check Box
    dijit/form/Toggle Button
    dijit/form/Drop Down Button
    dijit/form/Combo Button
    dijit/form/Filtering Select
    dijit/form/Multi Select
    dijit/form/Combo Box
    dijit/form/Time Text Box
    dijit/form/Text Box
    dijit/form/Textarea
    dijit/form/Simple Textarea
    dijit/form/Number Text Box
    dijit/form/Number Spinner
    dijit/form/Date Text Box
    dijit/form/Currency Text Box

    I reckon that there are some problems/errors during the build, so that
    these pages aren't exported at all and what we see are some old files
    instead (exported during the last error-free build).

    Also, the http://dojotoolkit.org/reference-guide/ shows a very old
    version of this page (from 2009-01-05). This is the current one:
    http://docs.dojocampus.org/manual/index

    Marcus
  • Tobias Klipstein at Feb 16, 2010 at 3:32 pm
    Hi Markus,

    thanks for pointing out the problems. Seems there was a mistake in copying
    the files. Will take care.

    Regards, Tobias

    2010/2/16 Marcus Reimann <marcus-nospam at dojotoolkit-forum.de>
    Hi Tobias,
    Am 15.02.2010 17:21, Tobias Klipstein wrote:

    Since release 1.3 I do this process for every new Dojo release and I
    did the last conversion at 2010/02/10.
    But, it's obvious that there are a lot of outdated pages within this
    generated pages. For example look at

    * http://docs.dojocampus.org/dojox/form/FileUploader - trutwijd
    added a note on http://bugs.dojotoolkit.org/ticket/10576 at
    2009-12-31 16:52:59 vs
    http://dojotoolkit.org/reference-guide/dojox/form/FileUploader.htm
    - no such note
    * http://docs.dojocampus.org/dojo/objectToQuery - it was corrected
    at 2009-12-30 21:17:35 vs.
    http://dojotoolkit.org/reference-guide/dojo/objectToQuery.html -
    still the wrong title
    * http://docs.dojocampus.org/dojo/fx/slideTo - it was corrected at
    2010-01-14 23:15:40 vs.
    http://dojotoolkit.org/reference-guide/dojo/fx/slideTo.html -
    still the wrong text with "wipeIn" instead of "slideTo".
    * Some additional examples: dojo/style
    dijit/Tooltip Dialog
    dijit/Tree
    dijit/Toolbar
    dijit/TitlePane
    dijit/Progress Bar
    dijit/MenuBar
    dijit/Menu
    dijit/Declaration
    dijit/Color Palette
    dijit/Calendar
    dijit-a11y-statement
    dijit-a11y-req
    quickstart/writing Widgets/a11y Testing
    quickstart/writing Widgets/a11y
    dijit-a11y-resources
    dijit-a11y-strategy
    dijit-a11y
    dijit/_Widget
    dijit/_Templated
    dijit/info
    dijit/layout/Tab Container
    dijit/layout/Content Pane
    dijit/layout/Border Container
    dijit/layout/Accordion Container
    dijit/layout/_Layout Widget
    dijit/layout
    dijit/form/Slider
    dijit/form/Radio Button
    dijit/form/Form
    dijit/form/Check Box
    dijit/form/Toggle Button
    dijit/form/Drop Down Button
    dijit/form/Combo Button
    dijit/form/Filtering Select
    dijit/form/Multi Select
    dijit/form/Combo Box
    dijit/form/Time Text Box
    dijit/form/Text Box
    dijit/form/Textarea
    dijit/form/Simple Textarea
    dijit/form/Number Text Box
    dijit/form/Number Spinner
    dijit/form/Date Text Box
    dijit/form/Currency Text Box

    I reckon that there are some problems/errors during the build, so that
    these pages aren't exported at all and what we see are some old files
    instead (exported during the last error-free build).

    Also, the http://dojotoolkit.org/reference-guide/ shows a very old
    version of this page (from 2009-01-05). This is the current one:
    http://docs.dojocampus.org/manual/index

    Marcus
    _______________________________________________
    dojo-contributors mailing list
    dojo-contributors at mail.dojotoolkit.org
    http://mail.dojotoolkit.org/mailman/listinfo/dojo-contributors
    -------------- next part --------------
    An HTML attachment was scrubbed...
    URL: http://mail.dojotoolkit.org/pipermail/dojo-contributors/attachments/20100216/8da773d9/attachment.htm

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupdojo-contributors @
categoriesdojo
postedFeb 12, '10 at 5:19p
activeFeb 16, '10 at 3:32p
posts12
users7
websitedojotoolkit.org

People

Translate

site design / logo © 2021 Grokbase