Spring Roo
  1. Spring Roo
  2. ROO-631

Complete the Part III of the reference guide

    Details

    • Type: Task Task
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: @ RESOURCES
    • Labels:
      None

      Description

      The present of the Roo project right now is very good.
      A lot of people are trying to adapt the tool to their environment or at least, "playing" with the tool.
      Nevertheless, I think it is very important to complete the Part III of the reference guide (Internals and Add-On development), because then, it will be a crucial timestamp to increase the Roo community or people interested in the tool.
      Currently, if you want to develop and Add-On, you have to make a great effort looking into another ones, source code, reaching (not always correct) conclusions,...
      So, I think it's very important to complete this part of the reference documentation to invite even more people to the Roo Community and project.
      By the way, I would appreciate a lot if you can add some Add-On implementation examples to the reference guide. I mean, the general Spring Framework Reference Guide is superb. Why does not Roo deserve a documentation like that? Please, do not misunderstand me. The current reference guide is very good, but this segment of the documentation is crucial for the complete success of the project (in my opinion).
      Thank you very much

        Activity

        Hide
        Ben Alex added a comment -

        We have every intention of completing the Roo documentation, but our priority to date has been to deliver regular Roo releases with zero known Roo bugs in each release, and offer first-class support on the community forum. In the meantime my Roo technical deep dive presentation at http://www.slideshare.net/benalexau/spring-roo-100-technical-deep-dive is the best way to learn about add-ons and Roo internals.

        We have recruited another member of the Roo team who starts 1 March 2010 and this will give us the necessary extra capacity to deal with new features and catch up on areas like documentation.

        Show
        Ben Alex added a comment - We have every intention of completing the Roo documentation, but our priority to date has been to deliver regular Roo releases with zero known Roo bugs in each release, and offer first-class support on the community forum. In the meantime my Roo technical deep dive presentation at http://www.slideshare.net/benalexau/spring-roo-100-technical-deep-dive is the best way to learn about add-ons and Roo internals. We have recruited another member of the Roo team who starts 1 March 2010 and this will give us the necessary extra capacity to deal with new features and catch up on areas like documentation.

          People

          • Assignee:
            Unassigned
            Reporter:
            Juanjo Martin
          • Votes:
            27 Vote for this issue
            Watchers:
            14 Start watching this issue

            Dates

            • Created:
              Updated: