I'm not crazy about it. I'm not sure if the typical user of Designer cares about
that file or even knows one exists inside a VDB. But you can correct me on that one. It
seems silly to have that tab if you can't edit it. And if you do allow editing, as
stated below, it complicates the editor quite a bit. Not only the framework to sync
editors would be needed, but editor validation and a way for the user to overwrite with an
auto-generated file may also be needed. I'm just not sure the cost/benefit is worth it
right now.
----- Original Message -----
From: "Ramesh Reddy" <rareddy(a)redhat.com>
To: "John Doyle" <jdoyle(a)redhat.com>
Cc: "teiid-designer-dev" <teiid-designer-dev(a)lists.jboss.org>
Sent: Monday, March 22, 2010 1:41:28 PM GMT -06:00 US/Canada Central
Subject: Re: [teiid-designer-dev] VDB configuration
I like it. The only issue is whether you want to let the users edit it
or not. If you do, then syncing is the issue.
Ramesh..
On Mon, 2010-03-22 at 13:21 -0400, John Doyle wrote:
I've been working on the VDB UI to stub out the changes for Teiid
7 and wanted to float an idea. How about adding an additional tab to the VDB editor view
that showed the configuration.def file in a raw XML view? This seems like a pretty
standard eclipse paradigm and I think plays into the way the typical JBoss user expects to
interaction with their tools.
~jd
_______________________________________________
teiid-designer-dev mailing list
teiid-designer-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/teiid-designer-dev
_______________________________________________
teiid-designer-dev mailing list
teiid-designer-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/teiid-designer-dev