× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



>See, here's the main problem.  Why do you insist that I must hardcode in my 
>CGI programs?  Until you can get past the fact that just because it's RPG I 
>have to hardcode everything, there's no reason to continue this discussion 
>because you're arguing in circles.  sure, I hardcode things like "<td>" but 
>I don't hardcode classnames. 

1. I don't even hardcode <td>.  That comes from the decorator class.  If I want 
a different tag language syntax, I simply attach a different decorator class.

2. Where does the class name come from?  I wouldn't flog the horse if you'd 
answer the question.  How, in your scenario, do I put four different widgets on 
a page?  As far as I can tell, there are two ways:

A. Call a single CGI program that outputs all four widgets.

B. Call four CGI programs that output widgets.

In either case, how are the class names assigned?  How do you ensure that they 
don't collide?  Because if the class names are the same, then the stylesheet 
will assign the same styles to different widgets.

And what about the issue of separating fields from one widget into two to be 
placed elsewhere on the screen?  Do you indeed have to create another CGI 
program?  If so, where does the new CGI program get its class names?

I'm not railing against the design, just trying to understand.  I was torn 
between the idea of assigning style names or inline styles, and so in good 
object-oriented fashion I support either one.  This is specifically to avoid 
style collisions.  I'm just wondering how you do the same.  On of my goals of 
course is to illustrate the strengths of JSP and OO design as opposed to CGI, 
but if you've got a creative way of dealing with this issue, then I'd love to 
see it.

Of course, you could use the query string - then you'd just need an API that 
could parse out the required parameters from the query string.  At that point, 
you'd be very close to the functionality of a good component widget, albeit 
without the backend processing.

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
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.