RE: Float-over help on inactive widgets ??? -Reply

Question

Jason de Cean
Genisys Team
Lumley Technology Limited
Level 8, 55 Sussex St
Sydney, Australia (+61)
Ph. 02 9248 1321
-----Original Message-----
From: Steven Barnes [SMTP:[email protected]]
Sent: Friday, 19 March 1999 6:01
To: [email protected]
Subject: Float-over help on inactive widgets ??? -Reply
If I remember my help file correctly, FieldWidgets with a state of
FS_INACTIVE do not respond to any events (ie. AfterFocusGain,
MouseEnter, etc). So, it's my guess that that is what is killing the
help
items. They may very well depend on 'MouseEnter' type events. Try
FS_VIEWONLY. The users will be able to click on & even highlight text,
but they can't change anything. (and the float over help should still
work).
I'm not sure about the status bar text. I haven't used it much.
Steven Barnes
LRS
RACZ 03/19/99 05:16am >>>
From: "Attila R*cz" <[email protected]>
Hi!
I set the State attribute of a DataField to FS_INACTIVE.
Why can't I see the float-over and status line help for
this DataField?
I think this is the same for any other FieldWidget.
But why???
Thanks in advance for any response...
Attila
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive
<URL:http://pinehurst.sageit.com/listarchive/>-
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Answer 1

Since you are publishing your results on the net , it will be a better idea to use JSP?Servlet/Beans architecture instead of swing
I will propose a architecture as follows:
Client : Standard Browsers, IE and NS
Middle Tier: Java Webserver/Application Server
This will depend on your budget. If u have a fat allowance go for weblogic/websphere . If u are operationg on shoe string budget try for apache , etc
In the server tier code your application in the follwing architecture
JSP for presentation: Distillation towers picture, input boxes .. etc
Servlets for business logic invocation and routing requests: Your JSP submits input values to servlets, which does the processing using Java Bean Components. Since you have a lot of Logic written in C I would suggest to encapsulate these in JavaBean components using JNI technology and reuse the code.
After processing the servlet again forwards the response to another JSP for output
Advantages:
1.Your clients can be thin as most of the processing is done at the server
2. Thread Management is taken care of by your webserver, which otherwise would be a headache
3. Writing this through low level socket programming will be much more difficult as you will write your own protocol for communication this will be error prone and not scalable
If you still decide to go for traditional client server programming using swing, use RMI for communication as I insist that socket programming is very very cumbersome...using your own protocols
hope this helps
Shubhrajit