It's not an issue of conflicting element names. It's an issue because all of the widget XML files expect to have only one schema. If you have screens, forms, and menus all in one file, then you need to support multiple schemas.
I have it basically working - I just need to figure out a validation error. The existing schemas don't have a TargetNamespace defined, which causes an error. If I add a TargetNamespace, then I get a different error saying it was expecting it to be empty. ::scratches head:: I'll post a patch on Jira, maybe an XML expert can figure it out. -Adrian --- On Sat, 1/1/11, David E Jones <[email protected]> wrote: > From: David E Jones <[email protected]> > Subject: Re: Discussion: Support Screen Widget Namespaces > To: [email protected] > Date: Saturday, January 1, 2011, 2:39 PM > > What are the conflicting element names you are seeing that > would require the use of namespaces? > > -David > > > On Jan 1, 2011, at 10:15 AM, Adrian Crum wrote: > > > The current system of having separate XML files for > screens, menus, and forms lends itself well to some types of > projects. In some cases, it might be preferable to have all > related widgets (screens, forms, menus) in a single XML > file. > > > > Adding support for multiple widget types in a single > file would require a small change to the widget factory > code. The "compound widget" XML file would require the use > of namespaces - but the added complication is minimal. > > > > Would there be any interest in that? > > > > -Adrian > > > > > > > > > > > >
