Scott Cantor wrote:
> At a minimum, I'd suggest some minor fixes needed so the code will build
> cleanly on the latest MS compiler (VS 2005), which I can supply for the
> no-xalan build, at least. Also optionally check in some project files for
> that version instead of forcing people to convert the 7.0 projects files,
> although that mostly works fine.
Yup - already working on it. I tend to do most of my work on Linux and
VC 6.0 and then when it's all looking OK build up the other
compilers/platforms. Otherwise I waste a lot of cycles doing point
fixes to projects.
>
> There were some new source files not added to the MS project in svn as well,
> but that's easy to fix also.
>
> I'd also suggest copying some more of the Xerces version header machinery
> into the XMLSec one. That makes it easier for people to do autoconf version
> checks, and since 1.3 has some good new APIs, I know I at least need to
> check for it.
Hmm. Good idea. Will have a look-see.
>
> Most of the rest of my thoughts center on a bit of reworking of the whole
> document management approach, the XSECProvider concept, and some of that,
> but I haven't had a chance to really formally propose anything, so I'd say
> do a 1.3 and then maybe look at that stuff later if anybody is so inclined.
Most interested to hear thoughts. I have been wanting for a while to
head back to DSIGSignature and rework that into more of a factory
approach than currently exists but I think you mean more than that?
Cheers,
Berin
