Re: docweb update [06.25]

> > I think that having things in CVS isn't probably the best idea. As we will > > have a login system, we could use it and have all the info in a DB. > > All language/project specific should be in the DB, IMHO. With this, we can > > have a simple and clear file design. > > I don't like keeping stuff in the DB, since I am very much interested in > seeing changes, in seeing what is going on. With DB based interfaces, we > would need to implement that on our own. And as I have said, we are > better not to reinvent the wheel IMHO :) Those who will write these > pages will have enough expertise to work with CVS (these will probably > be the lead people from the translation and project specific groups). Uhm.... I have to agree with you. The guys who are going to write know how to use CVS. Maybe it should be better ro have those information in each project/language CVS module? As we will have a checkout of phpdoc-all, peardoc, smarty/docs,.... we can extract the information in each project folder. I think this solution is better than having all the info in the main docweb folder? This info can be in XML, or so. Do agree with me??... > > P.S.: I like this new fresh look. (althought IE doesn't display it very > > well...) > > I am glad, that you like it. It has as clean and as small HTML code as > possible. :) I have not been able to test it in IE since I have no > windows currently here, so people are welcome to help out fix possible > CSS bugs. It works quite good for me in Mozilla :)) Yeah, in mozilla it displays right, but IE is very buggy when handling CSS. I'll take a look to this later. I just want the code in CVS soon :) Nuno