RE: Source Evaluation?

["Joe Teff" <JoeTeff@xxxxxxxxxxxxx>]

You could mimic the Java AWT/Swing model. Define a widget
class that is the parent of all HTML output types. Then
create classes to generate each specific type of output
text, input fields, tables, etc.).

A table (for instance HTMLTableWidget is just another
class with methods to add rows, set headers, set
properties. The toString() method would generate a
String with all of the appropraite tags along with the
data.

Joe

-----Original Message-----
From: owner-java400-l@midrange.com
[mailto:owner-java400-l@midrange.com]On Behalf Of Joe Pluta
Sent: Friday, February 09, 2001 7:35 PM
To: JAVA400-L@midrange.com
Subject: RE: Source Evaluation?


I realize that, Joe.  I was just thinking out loud.  Part of the reason I
was thinking about the categories concept was the ability to have multiple
sets of properties in one file (each in a different category), and then
easily switch between by changing one setting.

I haven't thought the whole idea through, but I just thought I'd get some
feedback.  You'll hear more from me as I begin to implement some other
things.  For example, I want to be able to set up default styles for
different widgets.  I'll also have support for style sheets, but in the
cases where I don't want to use a style sheet, it would be nice to have some
default properties.  At the same time, there are different properties for
different widget types:

  [TableHeader]
  font=12pt Arial bold
  background=blue
  color=white

  [TableCell]
  font=10pt Arial
  color=#4040FF

As you can see, it would be nice to have use the same property names, just
in different categories.

Joe

+---
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: joe@zappie.net
+---