 |
BorlandTalk.com Borland discussion newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
Peter Zaharkiv Guest
|
Posted: Tue Jun 13, 2006 4:52 am Post subject: dbswing GUI failure |
|
|
jBuilder 2006, Windows XP
I have built several dbSwing panels with corresponding DataModules.
After putting in several hundreds hours into designing panels in the
Designer, I open jBuilder today, and suddenly half my panels show that
the dbswing components don't have a dataset displayed in the properties.
As a result, the entire panel layout is corrupted (incomplete, missing
components) as though there wasn't any datasets attached.
Source code looks fine. Compiling and executing the application,
everything is correct. Just, can't use the Designer to work on the
panels anymore.
I saw this happen in jBuilder 2005 when inheriting jBuilder X
applications. Ended up having to recreate the applications by copy and
pasting the source code from the old project to new files in a new
project one at a time.
Does anyone have any idea what's causing this and how to reverse the
problem? It appears to be an IDE bug, but I can't find anyone else
experiencing this. |
|
| Back to top |
|
 |
Kevin Dean [TeamB] Guest
|
Posted: Tue Jun 13, 2006 5:39 am Post subject: Re: dbswing GUI failure |
|
|
Peter Zaharkiv wrote:
| Quote: | jBuilder 2006, Windows XP
Does anyone have any idea what's causing this and how to reverse the
problem? It appears to be an IDE bug, but I can't find anyone else
experiencing this.
|
Look under "Tools | Event Log". Any exceptions thrown in the designer
should show up there. There may be something in your application
environment (outside of JBuilder) that has changed in a way that is
corrupting the designer.
--
Kevin Dean [TeamB]
Dolphin Data Development Ltd.
http://www.datadevelopment.com/
NEW WHITEPAPERS
Team Development with JBuilder and Borland Enterprise Server
Securing Borland Enterprise Server
http://www.datadevelopment.com/papers/index.html
Please see Borland's newsgroup guidelines at
http://info.borland.com/newsgroups/guide.html |
|
| Back to top |
|
 |
Peter Zaharkiv Guest
|
Posted: Tue Jun 13, 2006 7:16 am Post subject: Re: dbswing GUI failure |
|
|
Thanks for the quick response.
I checked the Event Log as you suggested, but the last event was on 6/7/06. That was dealt with last week, but unrelated to the current problems.
The DataModule Designer is displaying correctly and query tests are all returning Successful.
Whatever it is, it's taking killing the display of every text character, including fields, labels, etc. in the panel.
I can click on where I know a label is. The object is selected and the properties display correctly.
In summary, the obvious attributes of this problem:
a) dbswing objects do not display the dataset that obviously
exists in the source code, without errors.
b) All text in the panels is missing (labels, fields, etc.)
Finally, Dialogs are appearing normal. So, it's not consistent across the entire application.
"Kevin Dean [TeamB]" <NkOdSePaAnM (AT) datadevelopment (DOT) com> wrote:
| Quote: | Peter Zaharkiv wrote:
jBuilder 2006, Windows XP
Does anyone have any idea what's causing this and how to reverse the
problem? It appears to be an IDE bug, but I can't find anyone else
experiencing this.
Look under "Tools | Event Log". Any exceptions thrown in the designer
should show up there. There may be something in your application
environment (outside of JBuilder) that has changed in a way that is
corrupting the designer.
--
Kevin Dean [TeamB]
Dolphin Data Development Ltd.
http://www.datadevelopment.com/
NEW WHITEPAPERS
Team Development with JBuilder and Borland Enterprise Server
Securing Borland Enterprise Server
http://www.datadevelopment.com/papers/index.html
Please see Borland's newsgroup guidelines at
http://info.borland.com/newsgroups/guide.html |
|
|
| Back to top |
|
 |
Kevin Dean [TeamB] Guest
|
Posted: Tue Jun 13, 2006 4:52 pm Post subject: Re: dbswing GUI failure |
|
|
Peter Zaharkiv wrote:
| Quote: | Finally, Dialogs are appearing normal. So, it's not consistent across the
entire application.
|
There have been sporadic problems with the designer in JBuilder 2006.
There are two JBuilder 2006 updates planned for this year and hopefully
the first update will resolve the problem.
What I typically do with complex UI designs (both for code management
purposes and because the designer has had various problems over the years)
is break them up into individual panels that are edited separately. An
order management form may, for instance, have the order header, order
detail, product view, and customer view all on the same form. From a
source perspective, however, I have:
OrderHeaderPanel.java
OrderDetailPanel.java
ProductPanel.java
CustomerPanel.java
all consolidated at run-time into:
OrderForm.java
Is it possible for you to break your forms down into simpler components
like this?
--
Kevin Dean [TeamB]
Dolphin Data Development Ltd.
http://www.datadevelopment.com/
NEW WHITEPAPERS
Team Development with JBuilder and Borland Enterprise Server
Securing Borland Enterprise Server
http://www.datadevelopment.com/papers/index.html
Please see Borland's newsgroup guidelines at
http://info.borland.com/newsgroups/guide.html |
|
| Back to top |
|
 |
Peter Zaharkiv Guest
|
Posted: Tue Jun 13, 2006 11:13 pm Post subject: Re: dbswing GUI failure |
|
|
Thanks for the hints. Now, the problem is what to do. With the amount of
work done already on our large panels, breaking them up into smaller
panels will be a lot of work.
Each of the primary panels include 8 to 10 sub panels. (I know what the
paradigm criticism is going to be, but, in this case, the client rules)
Each of these sub panels will, I presume, require datamodule instances
created, where only one was necessary in the primary panel.
Since many of the sub panels, refer to objects in the parent panel, such
as changing object properties (color, text, content, focus), I'll
probably have to create instances of the parent panel in each sub panel
to affect these objects. (Maybe I'm wrong, but in the last 5 years I
haven't had to do anything like this...convenience and expedience rule
over eloquent style in a production environment)
Further investigation has revealed that this problem is bound within a
project. When switching to other projects in the same run of jBuilder,
frames and panels (smaller than the problem panels) are working fine.
Once it does occur, it effects ALL panels within a project except those
within a dialog. By editing the scope in a dataset query in one
datamodule not related to any panels, suddenly, all the panel GUI's
fail, irreversibly. Definitely a serious jBuilder bug.
Our problem is now in two parts. Short term and long term. I know that
Borland has a history of not revealing when an update is going to be
released, but maybe, since they are selling off (abandoning!) jBuilder,
we could get some hint when the update is coming. Is it weeks, months,
quarters?
If it's many months away, then we have no choice but to entertain
alternate IDE's. At this point, jBuilder 2006 is nothing more than a
bloated source editor for us, since most of our work is in database GUI
interfaces.
In the short term, we have to consider the small fortune in resources
we're going to have to expend to reorganize the panels, test and placate
the client.
Thanks for all the hints. It's a relief to know what is fundamentally
happening and to stop chasing our tails.
Kevin Dean [TeamB] wrote:
| Quote: | Peter Zaharkiv wrote:
Finally, Dialogs are appearing normal. So, it's not consistent across
the entire application.
There have been sporadic problems with the designer in JBuilder 2006.
There are two JBuilder 2006 updates planned for this year and hopefully
the first update will resolve the problem.
What I typically do with complex UI designs (both for code management
purposes and because the designer has had various problems over the
years) is break them up into individual panels that are edited
separately. An order management form may, for instance, have the order
header, order detail, product view, and customer view all on the same
form. From a source perspective, however, I have:
OrderHeaderPanel.java
OrderDetailPanel.java
ProductPanel.java
CustomerPanel.java
all consolidated at run-time into:
OrderForm.java
Is it possible for you to break your forms down into simpler components
like this?
|
|
|
| Back to top |
|
 |
Paul Furbacher [TeamB] Guest
|
Posted: Wed Jun 14, 2006 8:13 am Post subject: Re: dbswing GUI failure |
|
|
Peter Zaharkiv wrote:
| Quote: | Further investigation has revealed that this problem is bound within a
project. When switching to other projects in the same run of jBuilder,
frames and panels (smaller than the problem panels) are working fine.
Once it does occur, it effects ALL panels within a project except those
within a dialog. By editing the scope in a dataset query in one
datamodule not related to any panels, suddenly, all the panel GUI's
fail, irreversibly. Definitely a serious jBuilder bug.
|
It's important that you begin running JBuilder from the command
line and with the -verbose option. This way, you'll get more
input as to what might be going wrong and when. (I don't know
that the event log gives you the same info -- maybe it does, but
I always run in the -verbose mode.)
My guess is that you could quite easily solve this problem by
judiciously applying
if ( ! java.beans.Beans.isDesignTime() ) {
// do querydataset stuff here such as
myComponent.setDataSet(qds);
}
so that you won't be trying to access live data while designing
your UI.
Have you tried this? It's very possible that something is being
instantiated improperly, causing a null pointer exception to be
thrown somewhere in the process of building the view in the
Designer. Once that happens, it may be that no rendering happens.
| Quote: | Our problem is now in two parts. Short term and long term. I know that
Borland has a history of not revealing when an update is going to be
released,
|
Few companies release schedules of future updates. It is not a
Borland-only phenomenon.
| Quote: | but maybe, since they are selling off (abandoning!) jBuilder,
|
Good grief. Borland and "DevCo" have been very clear that the
*tools* are being spun off into a separate company. It is not
just JBuilder. And nothing is being abandoned. They have been
even more clear that roadmaps to future versions are on track
for all IDEs.
| Quote: | we could get some hint when the update is coming. Is it weeks, months,
quarters?
|
If I remember correctly, the published roadmap says there will be
two updates this year. That's all we know. From my experience,
that's a lot more than any other software company has ever published.
If you have discovered a bug with the UI Designer -- meaning you
can write a small test case which isolates the problem --
file a bug report, and if it affects a significant number of people
(i.e., gets a lot of votes) or is found to be a serious flaw with
no work-arounds -- the updates may just be able to provide a fix.
| Quote: | If it's many months away, then we have no choice but to entertain
alternate IDE's. At this point, jBuilder 2006 is nothing more than a
bloated source editor for us, since most of our work is in database GUI
interfaces.
|
I'd say there's a better approach -- it's called the "let's roll up
our sleeves and figure out a work-around for this" approach. I'm
guessing that since it works in simpler examples, you can identify
exactly what it is in your large app which triggers this problem,
and deal with it without that much effort. The sky isn't falling
by any means.
--
Paul Furbacher (TeamB)
Save time, search the archives:
http://info.borland.com/newsgroups/ngsearch.html
Is it in Joi Ellis's Faq-O-Matic?
http://www.visi.com/~gyles19/fom-serve/cache/1.html
Finally, please send responses to the newsgroup only.
That means, do not send email directly to me.
Thank you. |
|
| Back to top |
|
 |
Kevin Dean [TeamB] Guest
|
Posted: Thu Jun 15, 2006 6:10 am Post subject: Re: dbswing GUI failure |
|
|
Peter Zaharkiv wrote:
| Quote: | Each of these sub panels will, I presume, require datamodule instances
created, where only one was necessary in the primary panel.
|
They will each need an instance of the data module, but you can
instantiate it as a global instance in order to minimize the resources.
| Quote: | Since many of the sub panels, refer to objects in the parent panel, such
as changing object properties (color, text, content, focus), I'll probably
have to create instances of the parent panel in each sub panel to affect
these objects. (Maybe I'm wrong, but in the last 5 years I haven't had to
do anything like this...convenience and expedience rule over eloquent
style in a production environment)
|
Actually, it's a lot easier than it appears at first glance. The
getParent() method will give you the parent (master) panel; all you have
to do is cast to the appropriate type. Furthermore, you can access
sibling panels as follows (this is from code that I've been using to do
exactly that for the last four years):
private GamesPanel getGamesPanel() {
return (GamesPanel)WindowHelper.getComponentOfClass(getParent(), GamesPanel.class);
}
| Quote: | Further investigation has revealed that this problem is bound within a
project. When switching to other projects in the same run of jBuilder,
frames and panels (smaller than the problem panels) are working fine.
|
Since it can be isolated, it can be traced as per Paul's post.
| Quote: | Once it does occur, it effects ALL panels within a project except those
within a dialog. By editing the scope in a dataset query in one datamodule
not related to any panels, suddenly, all the panel GUI's fail,
irreversibly. Definitely a serious jBuilder bug.
Our problem is now in two parts. Short term and long term. I know that
Borland has a history of not revealing when an update is going to be
released, but maybe, since they are selling off (abandoning!) jBuilder, we
could get some hint when the update is coming. Is it weeks, months,
quarters?
|
The public roadmap that Borland published on May 16 states that two
JBuilder 2006 updates are planned for this year.
| Quote: | If it's many months away, then we have no choice but to entertain
alternate IDE's. At this point, jBuilder 2006 is nothing more than a
bloated source editor for us, since most of our work is in database GUI
interfaces.
|
I don't know how far away the first update is, but my personal guess with
absolutely no information from Borland is that it will be sooner rather
than later (with a commitment to two updates before the end of this year,
it won't make much sense for them to be close together at the end of the
year).
| Quote: | In the short term, we have to consider the small fortune in resources
we're going to have to expend to reorganize the panels, test and placate
the client.
|
Welcome to the world of development. Whether it's JBuilder, the back-end
database, the Windows subsystem, or a flaky power supply, we've all had to
deal with errant problems. I tore some of my rapidly receding hair out
today fighting with a poorly documented but absolutely necessary feature
in Windows CE.
Once you figure out what it takes to extract one panel into its own class,
the rest should follow along pretty quickly.
| Quote: | Thanks for all the hints. It's a relief to know what is fundamentally
happening and to stop chasing our tails.
|
You're welcome.
--
Kevin Dean [TeamB]
Dolphin Data Development Ltd.
http://www.datadevelopment.com/
NEW WHITEPAPERS
Team Development with JBuilder and Borland Enterprise Server
Securing Borland Enterprise Server
http://www.datadevelopment.com/papers/index.html
Please see Borland's newsgroup guidelines at
http://info.borland.com/newsgroups/guide.html |
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|