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

document new configuration interface #124

Open
GoogleCodeExporter opened this issue Mar 25, 2015 · 12 comments
Open

document new configuration interface #124

GoogleCodeExporter opened this issue Mar 25, 2015 · 12 comments

Comments

@GoogleCodeExporter
Copy link

The new configuration interface must be documented.

Examples:
http://www.seaside.st/community/development/seaside29/WARequestContext

the migration documentation must be updated as well:
http://www.seaside.st/documentation/migration

Original issue reported on code.google.com by [email protected] on 31 Aug 2008 at 9:21

@GoogleCodeExporter
Copy link
Author

Original comment by [email protected] on 1 Sep 2008 at 10:11

  • Added labels: Documentation
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

Original comment by [email protected] on 21 Sep 2008 at 5:48

  • Added labels: Milestone-2.9alpha
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

Original comment by [email protected] on 7 Oct 2008 at 5:02

  • Added labels: Priority-Medium
  • Removed labels: Priority-Critical

@GoogleCodeExporter
Copy link
Author

Original comment by [email protected] on 18 Oct 2008 at 5:04

  • Added labels: ****
  • Removed labels: Milestone-2.9alpha

@GoogleCodeExporter
Copy link
Author

These Documentation issues do not need to be assigned to me just because I
wrote the code. I know they need to be done, just like all the other issues
in here, and will undoubtedly get to them at some point but that needn't
prevent anyone else from taking a stab at documenting them in the meantime.

Original comment by [email protected] on 1 Nov 2008 at 4:59

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

Issue 272 has been merged into this issue.

Original comment by [email protected] on 7 Jan 2009 at 8:55

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

Original comment by renggli on 8 Sep 2009 at 7:09

  • Added labels: Version-Seaside3.0
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

Original comment by renggli on 8 Sep 2009 at 7:10

  • Added labels: ****
  • Removed labels: Version-Seaside2.9

@GoogleCodeExporter
Copy link
Author

What's the documentation format? and where will it appear.
I'm up for this if anyone can put some guidelines before I begin.

Original comment by [email protected] on 4 Sep 2010 at 4:06

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

The Seaside book (book.seaside.st) is a likely place for it at this point 
(unless it's already documented in there, in which case this could be closed). 
Otherwise, we can put it somewhere on the website.

Original comment by [email protected] on 5 Sep 2010 at 11:48

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

How do you write contents for the book?
Looks like it's generated from a Seaside application, where can one get it and 
commit changes?

Original comment by [email protected] on 24 Jan 2011 at 2:54

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

It's a simple Pier application, it's documented here 
http://book.seaside.st/system/howto
It's best to first write your article "offline" and then add it in one go. 
Lukas can give you an account.

Original comment by [email protected] on 25 Jan 2011 at 6:29

  • Added labels: ****
  • Removed labels: ****

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