Well, it is close to ready - I now have it successfully generating
* htcommon/defaults.cc
* htdocs/cf_byprog.html
* htdocs/cf_buname.html
* 95% of htdocs/attrs.html
I still need to bundle up the changes - I was thinking of creating
a patch based on 3.2.0b4 and just posting that
On Wednesday, October 16, 2002, at 02:27 AM, Brian White wrote:
* 95% of htdocs/attrs.html
I guess I'm not clear on what 95% means. Does this refer to the markup
that you mentioned before?
I still need to bundle up the changes - I was thinking of creating
a patch based on 3.2.0b4 and
Well, it is close to ready - I now have it successfully generating
Well, first and foremost, it is the first time I express my opinion regarding
this solution and I think it is really efficient and intelligent. Good on
ya, mate Brian! :-)
Having said this, and also taking aknowledgement that I
I'm going to take two separate issues and separate them for the moment:
1) What changes are needed for a solid 3.2.0 release.
2) The mifluz merge (in a separate e-mail).
Please don't take any of my comments as overly critical or flaming.
You're new to the project and attempting to take on some
On Tuesday, October 15, 2002, at 01:37 PM, Neal Richter wrote:
2. The mifluz devel list is near death, and it doesn't look like
anyone
is actually using mifluz, or furthering development.
Fine, but that simply does not mean that prior releases were not made
with active users,
On Wed, 16 Oct 2002, Geoff Hutchison wrote:
On Tuesday, October 15, 2002, at 01:37 PM, Neal Richter wrote:
2. The mifluz devel list is near death, and it doesn't look like
anyone
is actually using mifluz, or furthering development.
Fine, but that simply does not mean that
At 23:25 16/10/2002, Gabriele Bartolini wrote:
Well, it is close to ready - I now have it successfully generating
Well, first and foremost, it is the first time I express my opinion regarding
this solution and I think it is really efficient and intelligent. Good on
ya, mate Brian! :-)
Having
On Wednesday, October 16, 2002, at 07:41 PM, Brian White wrote:
I can use that tool to take a merged version of defaults.cc to produce
a version of defaults.xml. The problem is that a few of the descriptions
will need to be reworked quite heavily by hand to produce valid XML.
OK, that
