Re: [wxCode-users] About site reworking

[Francesco M. <f18...@ya...>]

Hi,

> Francesco (I'm assuming you changed index.html/php), please see the
> readme.txt in the the root directory (add to it as as necessary).
I could not found any readme in wxCode or wxCode\components or 
wxCode\website (CVS); do you refer to the readme.txt stored in 
/home/groups/w/wx/wxcode/htdocs ?
I suggest to put that readme.txt in wxCode\website CVS... ;-)


> You have to get the CVS version of the website, edit files locally,
> commit, and then do a checkout at SF using the script wxCode-website
> or just run the parts of it that are necessary for your changes.
ok, perfect.

> Secondly, do we want to have doxygen docs in wxCode's CVS? They're
> pretty large and checking out wxCode is already pretty slow.
sorry for that, I stored doxygen docs for some components in CVS... I'll 
remove them ASAP

> I think
> that just providing a doxygen.cfg file for people to run may be enough
> since doxygen is easy to use. We could also make them available to
> people by putting them up on the website in
> htdocs/doxygen/projectname.
> That way people can refer to them online
> and if they really want a local copy either provide a zipped version
> (also stored in htdocs/doxygen/projectname) or like I said, just ask
> them to run doxygen themselves. Each individual maintainer would add
> these using ssh (probably using scp) as suits them.
I agree, this is a good solution.


> Thirdly, for screenshots, we could create
> htdocs/screenshots/projectname and users put their screenshots there.
good idea; a special folder for the screenshots would make easier to put 
a link to them in the complist but I'm unsure about removing them from 
CVS... they could be very useful to people who just checkout the 
wxCode\components to choose if use/not use that component.
But I understand that if all dev save their screenshots in CVS we'll end 
up with a very heavy CVS repository...

> We could provide a sample template for people to use if they like,
> just so long as they have an index.html it'll work. All the developers
> for wxcode have ssh rights if I understand correctly, so they'll have
> to manage this aspect themselves. Again, I don't think it would be a
> good idea to put these in CVS since they're binary and when you
> download a component you'll have no need or want to have them. (Maybe
> this could be made easier with a wiki, but I don't know anything about
> that.)
Just give me some time to:
1) understand exactly how wxCode website works actually
2) do my PHP experiments ;-)
so I'll be ready to discuss about these site changes better next week ;-)

Francesco Montorsi

PS: I won't make any modifications to wxCode website without first 
mailing it to wxcode-users