Thread: [Vxl-maintainers] vxl book?

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

G'day All,

The web site that hosts the book (paine.wiau.man.ac.uk) seems to be
down and has been for at least a day or two ...

-- 
Cheers,

Brendan

It seems to have been down for some time. I had sent a message a long time
ago.
Maybe the texi processing is too fragile?

-----Original Message-----
From: vxl...@li...
[mailto:vxl...@li...] On Behalf Of Brendan
McCane
Sent: Tuesday, January 08, 2008 3:04 PM
To: vxl-maintainers
Subject: [Vxl-maintainers] vxl book?

G'day All,

The web site that hosts the book (paine.wiau.man.ac.uk) seems to be
down and has been for at least a day or two ...

-- 
Cheers,

Brendan

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Vxl-maintainers mailing list
Vxl...@li...
https://lists.sourceforge.net/lists/listinfo/vxl-maintainers

Hmm. OK, who looks after that site? Ian? There is quite a bit of
useful information for new users in the vxl book - perhaps we should
look at hosting it on sourceforge if the current server isn't that
reliable?

On 10/01/2008, Joseph Mundy <mu...@le...> wrote:
> It seems to have been down for some time. I had sent a message a long time
> ago.
> Maybe the texi processing is too fragile?
>
> -----Original Message-----
> From: vxl...@li...
> [mailto:vxl...@li...] On Behalf Of Brendan
> McCane
> Sent: Tuesday, January 08, 2008 3:04 PM
> To: vxl-maintainers
> Subject: [Vxl-maintainers] vxl book?
>
> G'day All,
>
> The web site that hosts the book (paine.wiau.man.ac.uk) seems to be
> down and has been for at least a day or two ...
>
> --
> Cheers,
>
> Brendan
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> _______________________________________________
> Vxl-maintainers mailing list
> Vxl...@li...
> https://lists.sourceforge.net/lists/listinfo/vxl-maintainers
>
>

-- 
Cheers,

Brendan

I'll look into doing the documentation on SourgeForge when I'm back in 
the office on Monday.

I was going to suggest that we change the doc hosting scheme sometime 
soon anyway.

The current scheme at on paine.man.ac.uk generates the doc in place, so 
when something goes wrong, there is no existing copy the system can 
display instead. The system also spews vast amounts of diagnostic output 
into hundreds of files, making it rather hard to track down the errors 
in the texi or c++/doxygen source that cause the build to fail.

I run a manual documentation build inside imorphics occasionally. I 
would be happy to run a full documentation build for VXL every time 
there is a release. I can tar it up, and send it to anybody who is 
willing to host it.

If there is a simple way to publish it on SF then we can do that. 
However, I don't want to put all the doxygen and texi output into the 
CVS repository, which is how we currently mange the SF website. There is 
somewhere between 100 and 300Mb of documentation, and minor changes to 
the documentation control files or doxygen versions can result in every 
html file needing to be stored in full.

Ian.

Amitha Perera wrote:
> I'll look into doing the documentation on SourgeForge when I'm back in 
> the office on Monday.
> 
> 
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> _______________________________________________
> Vxl-maintainers mailing list
> Vxl...@li...
> https://lists.sourceforge.net/lists/listinfo/vxl-maintainers

Ian Scott wrote:
> If there is a simple way to publish it on SF then we can do that. 
> However, I don't want to put all the doxygen and texi output into the 
> CVS repository, which is how we currently mange the SF website. There is 
> somewhere between 100 and 300Mb of documentation, and minor changes to 
> the documentation control files or doxygen versions can result in every 
> html file needing to be stored in full.

sf.net provides 100Mb of project space.  If the core documentation part 
fits within this limit[*], then we can generate the documentation 
somewhere and rsync it to the sourceforge space.  If the rsync process 
only runs when the documentation generation process successfully 
completes, sourceforge will always contain an accessible copy of the 
documentation.

Right now, we are using a little bit of the 100Mb for the webpages.  I 
can't tell exactly how much because I'm having trouble logging into the 
sourceforge shell.

Amitha.

[*]  We could also request a space increase.

Amitha Perera wrote:
> sf.net provides 100Mb of project space.  If the core documentation part 
> fits within this limit[*], 

Well I have just finished a build of the documentation for vxl-1.10, and 
it is 362Mb.

Does anyone else want to volunteer to host it. If so you can find it in 
the VXL file release system. If not, I will ask SF if we can more quota.

Ian.

Kitware is willing to host the vxl documentation.  I'll sort out the 
details and post back within the week.

Amitha.

I've set up the VXL documentation on a Kitware server.

(a) http://kitware.com/vxl/
(b) http://kitware.com/vxl/doxygen/release/
(c) http://kitware.com/vxl/doxygen/development/

I invite comments on the following:

1. Shall we move the "main" VXL pages from SourceForge to Kitware 
(http://kitware.com/vxl)?  We can make vxl.sourceforge.net automatically 
redirect.

2. Link (b) is the generated documentation for the latest vxl release, 
and will be updated on each release.  Link (c) is the generated 
documentation from the CVS tree, and will be updated much more 
frequently (most likely nightly).  Both will be *copies* of an off-line 
generation, so that if a particular nightly build fails, the web pages 
will still be available but slightly out of date.  Does this seem 
reasonable?

3. I'd like to set (b) and (c) as "the" documentation pages, with the 
Manchester and Brown pages labelled mirrors.  Thoughts?

4. The "search this documentation tree" needs to be updated.  I'll look 
at that.

Amitha.

> I've set up the VXL documentation on a Kitware server.
> 
> (a) http://kitware.com/vxl/
> (b) http://kitware.com/vxl/doxygen/release/
> (c) http://kitware.com/vxl/doxygen/development/

Great! Seems like a very reasonable setup.

> 1. Shall we move the "main" VXL pages from SourceForge
> to Kitware (http://kitware.com/vxl)?

I wouldn't do that.
Depends of course on the ease of maintaining one or the other.

> 3. I'd like to set (b) and (c) as "the" documentation pages, with
> the Manchester and Brown pages labelled mirrors.

Agreed.

--	Peter.

--

      __________________________________________________________
Låna pengar utan säkerhet. Jämför vilkor online hos Yahoo!
http://shopping.yahoo.se/c-100390123-lan-utan-sakerhet.html?partnerId=96915014

I second Peter's comments.  Everything is fine with me except moving
the VXL main page to Kitware.  I don't have a problem with kitware
hosting the pages, but that URL give the false impress that Kitware
somehow "owns" VXL.

Also, what about the VXL Book?  I thought part of the reason for this
move was to get the book back online.  Will Kitware host that too?

--Matt

On Jan 18, 2008 1:36 PM, Peter Vanroose <pet...@ya...> wrote:
> > I've set up the VXL documentation on a Kitware server.
> >
> > (a) http://kitware.com/vxl/
> > (b) http://kitware.com/vxl/doxygen/release/
> > (c) http://kitware.com/vxl/doxygen/development/
>
> Great! Seems like a very reasonable setup.
>
>
> > 1. Shall we move the "main" VXL pages from SourceForge
> > to Kitware (http://kitware.com/vxl)?
>
> I wouldn't do that.
> Depends of course on the ease of maintaining one or the other.
>
>
> > 3. I'd like to set (b) and (c) as "the" documentation pages, with
> > the Manchester and Brown pages labelled mirrors.
>
> Agreed.
>
> --      Peter.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> --
>
>
>       __________________________________________________________
> L=E5na pengar utan s=E4kerhet. J=E4mf=F6r vilkor online hos Yahoo!
> http://shopping.yahoo.se/c-100390123-lan-utan-sakerhet.html?partnerId=3D9=
6915014
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Vxl-maintainers mailing list
> Vxl...@li...
> https://lists.sourceforge.net/lists/listinfo/vxl-maintainers
>

I too have mild objections to the main page moving to kitware - mostly
because I usually update the main page every time I do a new release
and it's convenient to have it under the same csv as the source code.
Further, it gives more flexibility if someone else decides to take
over making releases. No problems with the documentation, although it
would be good to get the vxl book back up ...

Cheers,

Brendan.

On 19/01/2008, Matt Leotta <mat...@gm...> wrote:
> I second Peter's comments.  Everything is fine with me except moving
> the VXL main page to Kitware.  I don't have a problem with kitware
> hosting the pages, but that URL give the false impress that Kitware
> somehow "owns" VXL.
>
> Also, what about the VXL Book?  I thought part of the reason for this
> move was to get the book back online.  Will Kitware host that too?
>
> --Matt
>
> On Jan 18, 2008 1:36 PM, Peter Vanroose <pet...@ya...> wrot=
e:
> > > I've set up the VXL documentation on a Kitware server.
> > >
> > > (a) http://kitware.com/vxl/
> > > (b) http://kitware.com/vxl/doxygen/release/
> > > (c) http://kitware.com/vxl/doxygen/development/
> >
> > Great! Seems like a very reasonable setup.
> >
> >
> > > 1. Shall we move the "main" VXL pages from SourceForge
> > > to Kitware (http://kitware.com/vxl)?
> >
> > I wouldn't do that.
> > Depends of course on the ease of maintaining one or the other.
> >
> >
> > > 3. I'd like to set (b) and (c) as "the" documentation pages, with
> > > the Manchester and Brown pages labelled mirrors.
> >
> > Agreed.
> >
> > --      Peter.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > --
> >
> >
> >       __________________________________________________________
> > L=E5na pengar utan s=E4kerhet. J=E4mf=F6r vilkor online hos Yahoo!
> > http://shopping.yahoo.se/c-100390123-lan-utan-sakerhet.html?partnerId=
=3D96915014
> >
> >
> > -----------------------------------------------------------------------=
--
> > This SF.net email is sponsored by: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio 2008.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > _______________________________________________
> > Vxl-maintainers mailing list
> > Vxl...@li...
> > https://lists.sourceforge.net/lists/listinfo/vxl-maintainers
> >
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Vxl-maintainers mailing list
> Vxl...@li...
> https://lists.sourceforge.net/lists/listinfo/vxl-maintainers
>

--=20
Cheers,

Brendan

Amitha,
I am in agreement with Brendan and Matt. I think it is great if Kitware =
can
host the book. I appreciate your stepping into the breach. Maybe we can
evolve to something a bit less cumbersome than texi.=20

However, I think we need to maintain an appearance of neutrality as to =
the
ownership of vxl.=20
This neutrality is best guaranteed by keeping the vxl webpage served =
from
sourceforge.
Joe

From: vxl...@li...
[mailto:vxl...@li...] On Behalf Of =
Brendan
McCane
Sent: Saturday, January 19, 2008 10:20 PM
To: Matt Leotta
Cc: vxl-maintainers; Amitha Perera
Subject: Re: [Vxl-maintainers] vxl documentation

I too have mild objections to the main page moving to kitware - mostly
because I usually update the main page every time I do a new release
and it's convenient to have it under the same csv as the source code.
Further, it gives more flexibility if someone else decides to take
over making releases. No problems with the documentation, although it
would be good to get the vxl book back up ...

Cheers,

Brendan.

On 19/01/2008, Matt Leotta <mat...@gm...> wrote:
> I second Peter's comments.  Everything is fine with me except moving
> the VXL main page to Kitware.  I don't have a problem with kitware
> hosting the pages, but that URL give the false impress that Kitware
> somehow "owns" VXL.
>
> Also, what about the VXL Book?  I thought part of the reason for this
> move was to get the book back online.  Will Kitware host that too?
>
> --Matt
>
> On Jan 18, 2008 1:36 PM, Peter Vanroose <pet...@ya...>
wrote:
> > > I've set up the VXL documentation on a Kitware server.
> > >
> > > (a) http://kitware.com/vxl/
> > > (b) http://kitware.com/vxl/doxygen/release/
> > > (c) http://kitware.com/vxl/doxygen/development/
> >
> > Great! Seems like a very reasonable setup.
> >
> >
> > > 1. Shall we move the "main" VXL pages from SourceForge
> > > to Kitware (http://kitware.com/vxl)?
> >
> > I wouldn't do that.
> > Depends of course on the ease of maintaining one or the other.
> >
> >
> > > 3. I'd like to set (b) and (c) as "the" documentation pages, with
> > > the Manchester and Brown pages labelled mirrors.
> >
> > Agreed.
> >
> > --      Peter.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > --
> >
> >
> >       __________________________________________________________
> > L=E5na pengar utan s=E4kerhet. J=E4mf=F6r vilkor online hos Yahoo!
> >
http://shopping.yahoo.se/c-100390123-lan-utan-sakerhet.html?partnerId=3D9=
69150
14
> >
> >
> >
-------------------------------------------------------------------------=

> > This SF.net email is sponsored by: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio 2008.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> > _______________________________________________
> > Vxl-maintainers mailing list
> > Vxl...@li...
> > https://lists.sourceforge.net/lists/listinfo/vxl-maintainers
> >
>
> =
-------------------------------------------------------------------------=

> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Vxl-maintainers mailing list
> Vxl...@li...
> https://lists.sourceforge.net/lists/listinfo/vxl-maintainers
>

--=20
Cheers,

Brendan

-------------------------------------------------------------------------=

This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Vxl-maintainers mailing list
Vxl...@li...
https://lists.sourceforge.net/lists/listinfo/vxl-maintainers

I hear all of you on the preceived ownership ownership issue.  That 
wasn't my intent, but I can see how it could be interpreted that way. 
So, let's leave the main pages at sourceforge, updated via CVS, and the 
generated doxygen can be hosted at Kitware and anywhere else that wants 
to (but see the note below).  At Kitware, the updated links are

(a) http://public.kitware.com/vxl/doc/release/
(b) http://public.kitware.com/vxl/doc/development/

The books are generated in there too.  Right after this email, I'll 
commit changes to the main webpages to change links appropriately.

Note, however, that the Kitware hosted webpages are Kitware branded. 
This is a side effect of hosting on the public webserver, and is 
difficult to avoid.  If this is a problem, someone else should host the 
documentation.

I've removed the Brown mirror from the main documentation too, since it 
seems to be down as well.  Hopefully someone can get that set up.

I've also removed links to the search functionality until I've figured 
out the best way to get a search into just the vxl documentation.

Amitha.

Looks good to me Amitha. Thanks muchly for doing that.

Cheers,

Brendan.

On 22/01/2008, Amitha Perera <am...@th...> wrote:
> I hear all of you on the preceived ownership ownership issue.  That
> wasn't my intent, but I can see how it could be interpreted that way.
> So, let's leave the main pages at sourceforge, updated via CVS, and the
> generated doxygen can be hosted at Kitware and anywhere else that wants
> to (but see the note below).  At Kitware, the updated links are
>
> (a) http://public.kitware.com/vxl/doc/release/
> (b) http://public.kitware.com/vxl/doc/development/
>
> The books are generated in there too.  Right after this email, I'll
> commit changes to the main webpages to change links appropriately.
>
> Note, however, that the Kitware hosted webpages are Kitware branded.
> This is a side effect of hosting on the public webserver, and is
> difficult to avoid.  If this is a problem, someone else should host the
> documentation.
>
> I've removed the Brown mirror from the main documentation too, since it
> seems to be down as well.  Hopefully someone can get that set up.
>
> I've also removed links to the search functionality until I've figured
> out the best way to get a search into just the vxl documentation.
>
> Amitha.
>

-- 
Cheers,

Brendan

Amitha

The hosting looks good. Glad you were able to get those scripts to work. 
Thanks for your efforts here. It is good to see the doc pages up again.

To run a search, you could create a form that constructed a google 
search along the lines of

inurl:vxl inurl:release inurl:doc site:public.kitware.com vnl_vector

or

http://www.google.co.uk/search?q=inurl%3Avxl+inurl%3Arelease++site%3Apublic.kitware.com+vnl_vector

It looks like google hasn't crawled the pages yet, but it should work in 
a day or two.

Ian.

Amitha Perera wrote:
> I hear all of you on the preceived ownership ownership issue.  That 
> wasn't my intent, but I can see how it could be interpreted that way. 
> So, let's leave the main pages at sourceforge, updated via CVS, and the 
> generated doxygen can be hosted at Kitware and anywhere else that wants 
> to (but see the note below).  At Kitware, the updated links are
> 
> (a) http://public.kitware.com/vxl/doc/release/
> (b) http://public.kitware.com/vxl/doc/development/
> 
> The books are generated in there too.  Right after this email, I'll 
> commit changes to the main webpages to change links appropriately.
> 
> Note, however, that the Kitware hosted webpages are Kitware branded. 
> This is a side effect of hosting on the public webserver, and is 
> difficult to avoid.  If this is a problem, someone else should host the 
> documentation.
> 
> I've removed the Brown mirror from the main documentation too, since it 
> seems to be down as well.  Hopefully someone can get that set up.
> 
> I've also removed links to the search functionality until I've figured 
> out the best way to get a search into just the vxl documentation.
> 
> Amitha.
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Vxl-maintainers mailing list
> Vxl...@li...
> https://lists.sourceforge.net/lists/listinfo/vxl-maintainers

Ian Scott wrote:
> To run a search, you could create a form that constructed a google 
> search along the lines of
[...]

Yes.  But there may be more local search options; I need to do a little 
more digging.  (I'm still new here, is my excuse.)

Amitha.

Doxygen has a built-in search engine, enabled with this command in the
doxygen config file.

 SEARCHENGINE =3D YES

This uses apache mod_php.  On an internal FreeBSD machine I use
/usr/ports/lang/php5/.

Fred

-----Original Message-----
From: vxl...@li...
[mailto:vxl...@li...] On Behalf Of
Amitha Perera
Sent: Tuesday, January 22, 2008 9:13 AM
To: Ian Scott
Cc: 'vxl-maintainers'
Subject: Re: [Vxl-maintainers] vxl documentation

Ian Scott wrote:
> To run a search, you could create a form that constructed a google=20
> search along the lines of
[...]

Yes.  But there may be more local search options; I need to do a little
more digging.  (I'm still new here, is my excuse.)

Amitha.

------------------------------------------------------------------------
-
This SF.net email is sponsored by: Microsoft Defy all challenges.
Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Vxl-maintainers mailing list
Vxl...@li...
https://lists.sourceforge.net/lists/listinfo/vxl-maintainers

Just a heads up: the actual server will be public.kitware.com, not 
www.kitware.com (or kitware.com); the latter is for the commercial side 
of Kitware, and the former for the open source side.

I'll send an updated link set when I've moved the files.

Amitha.

Hi Folks,
Strictly I'm responsible for that server, as Ian is now at imorphics.
My colleague David Cristinacce has been looking into it, but isn't yet =
familiar enough with the set up to guarantee a quick fix.

I'll keep you posted on progress.

Tim

Tim Cootes                                  Professor of Computer Vision
Imaging Science and Biomedical Engineering  tel   (+44) 0161 275 5146
The University of Manchester                fax   (+44) 0161 275 5145
Manchester M13 9PT , UK                     mailto:t.c...@ma...
                                            =
http://www.isbe.man.ac.uk/~bim

-----Original Message-----
From: vxl...@li... on behalf of Amitha =
Perera
Sent: Thu 1/10/2008 4:09 AM
To: Brendan McCane
Cc: Joseph Mundy; vxl-maintainers
Subject: Re: [Vxl-maintainers] vxl book?
=20
I'll look into doing the documentation on SourgeForge when I'm back in=20
the office on Monday.

-------------------------------------------------------------------------=

Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketpl=
ace
_______________________________________________
Vxl-maintainers mailing list
Vxl...@li...
https://lists.sourceforge.net/lists/listinfo/vxl-maintainers