Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create "address book" tutorial #4

Open
pedersen opened this issue Sep 24, 2012 · 6 comments
Open

Create "address book" tutorial #4

pedersen opened this issue Sep 24, 2012 · 6 comments

Comments

@pedersen
Copy link
Member

This issue existed in Trac. The original can be viewed at http://trac.turbogears.org/ticket/1831

This issue existed on SourceForge. The original can be viewed at https://sourceforge.net/p/turbogears2/tickets/7

@pedersen
Copy link
Member Author

Original Author: pedersen, Original Timestamp: 2011-03-10 02:47:37.009000

Original Body: Create a second "address book" tutorial with a more complex model, and more complex templates, which uses and explains widgets, Catwalk/Sprox for setup, etc.


Kind of working on similar thing: I'll let you know when done. http://lucasmanual.com/mywiki/TurboGears2


I have made some progress on this tutorial. http://lucasmanual.com/mywiki/TurboGears2

I should be done in a week. Please go over it and let me know if you want to add anything, or if I should cover something else as well.


seems good +1 on adding it as an example project.


Jorge Vargas, since I read somewhere that you did write a lot of unit tests for some apps, could you help me finish the unit test for this addressbook? I did the "check if url returns" but I just need to test for widget, and database and I am not sure how I can do that fast.

If I could get some copy paste code I could use that would be great. Thanks, Lucas


Attaching what I have done so far.


Change of address: http://lucasmanual.com/mywiki/TurboGears2/Addressbook


I think this tutorial should live where it is, but that we should link to it in our documentation. This way the TG crew does not bear the burden of maintenance, and the author can still be acknowledged in our docs. Also, the dbmechanic code should be converted over to catwalk/sprox before these docs are accepted.

@pedersen
Copy link
Member Author

Original Author: brondsem, Original Timestamp: 2011-03-14 15:18:55.982000

Original Body:

@pedersen
Copy link
Member Author

Original Author: pedersen, Original Timestamp: 2011-06-11 20:35:03.964000

Original Body: - milestone: 2.2.0 --> 2.1.2

@pedersen
Copy link
Member Author

Original Author: pedersen, Original Timestamp: 2011-08-20 03:56:47.602000

Original Body: - milestone: 2.1.2 --> 2.1.3

@pedersen
Copy link
Member Author

Original Author: pedersen, Original Timestamp: 2011-09-22 02:52:29.054000

Original Body: - milestone: 2.1.3 --> 2.1.4

@pedersen
Copy link
Member Author

Original Author: pedersen, Original Timestamp: 2011-09-22 02:52:29.194000

Original Body: After reviewing the ticket, I'm not sure this tutorial will fit into the book (since, for that, I'm putting together Hiring Pond). And the older style docs will, eventually, be deprecated or even removed.

Moving back to undetermined milestone for now.

  • milestone: 2.1.4 --> Undetermined

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant