Re: Sphinx for "general" use
Dear all, > Alaric Haag schrieb: >> Hello, >> >> The Sphinx page bills it as a tool for documenting Python projects. I >> perceive it to be more of a "document management tool" that uses >> ReST. >> I've barely scratched the surface of using it though. >> >> So, I'm considering using it to make a "lab manual" to document all >> sorts of things we do, mostly NOT related to Python. I like the idea >> that one "document" can serve both as an on-line resource, and as a >> printed "book". >> >> What, if anything, "ties" Sphinx to documenting Python projects, or >> does >> it just _facilitate_ that? > > As Sebastian said, Python is its origin and focus, but there's nothing > that prevents you from not documenting something Python. > q§ Just to add my bit: I am considering to use Sphinx for setting up a web-page that is not documenting a software project or code, but rather represents some more generic kind of webpage (for example for a research group). I have played with rest2www before (and use this for http://www.soton.ac.uk/~fangohr for example), and am currently trying to understand what I can and can't do with sphinx for these kind of applications. (All I need are static webpages, so I didn't go down the Django route yet). If people can recommend any other tools that are similar to rest2www and 'sphinx for generic webpages', I'd be interested about that. Cheers, Hans > I've updated the website to reflect that. (When I'd written that, I > had > not assumed the rather quick success... ;) > > Georg > > > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "sphinx-dev" group. To post to this group, send email to sphinx-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sphinx-dev?hl=en -~--~~~~--~~--~--~---
Re: Version control
> > One nice thing about Bazaar is that they've integrated it with > Tortoise on Windows, so you can do things within the GUI rather than > being forced to use the command line. There is also TortoiseHg (http://tortoisehg.sourceforge.net/). Cheers, Hans > > > On Sat, Nov 1, 2008 at 11:25 PM, Gour <[EMAIL PROTECTED]> wrote: > > "Yarko" == Yarko T <[EMAIL PROTECTED]> writes: > > Yarko> I used to be on the hg end also - but I was participating in > Yarko> projects on Launchpad; that started to erode my > preference I > Yarko> think later (>1.5?) releases of bzr are "snappier"... > > +1 for bzr & LP (coming from DVCS land of darcs), although not being > contributor (yet), but in the process of learning Python... > > > Sincerely, > Gour > > -- > > Gour | Zagreb, Croatia | GPG key: C6E7162D > > > > > -- > Bruce Eckel > > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "sphinx-dev" group. To post to this group, send email to sphinx-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sphinx-dev?hl=en -~--~~~~--~~--~--~---
Re: Version control (was Re: Autosummary)
> >> > alternate possibility to directly take the step to a DVCS. > > So, I'm asking all of you: what would you prefer -- SVN at Google, > with very liberal commit policies, or Mercurial? > While I am not contributing to sphinx, I'd like to support the vote for Mercurial. I have used over the years cvs and svn, then bzr and hg, and found hg most convincing (snappier than bzr, easy for simple things, yet fairly powerful if required). Cheers, Hans > cheers, > Georg > > > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "sphinx-dev" group. To post to this group, send email to sphinx-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sphinx-dev?hl=en -~--~~~~--~~--~--~---
