Mark Lybarger <[EMAIL PROTECTED]> writes:

>Hopefully I've fixed the encoding issue if that was the problem.

>I'm sorry that I didn't provide enough information in the original post.  I
>would like to use Java Applets (javax.swing.*) for the user interface.  I
>guess it's not that common, I would just like the ability to have a more
>robust user interface than web forms.

Ah, ok, so you want to run the View on the browser in applet classes
(sorry, was my fault, I read "applet" and thought "servlet").

Haven't done this yet, so I can't really help you here.

        Regards
                Henning




>> -----Original Message-----
>> From: Henning P. Schmiedehausen [mailto:[EMAIL PROTECTED]
>> Sent: Friday, March 14, 2003 7:29 AM
>> To: [EMAIL PROTECTED]
>> Subject: Re: using alternative views
>> 
>> 
>> Mark Lybarger <[EMAIL PROTECTED]> writes:
>> 
>> >Is it possible to use java applets as the view portion of my 
>> TDK web app?
>> >Know where I could find a good start on some reading material on the
>> >subject?
>> 
>> Well, sort of. If you don't want to use "Java applets" but java
>> classes, then Turbine can help you.
>> 
>> If you don't configure a template service (or even if you do :-) ),
>> you can back every screen, layout and page with a java class which
>> gets called if you request a certain template. There you can put java
>> code to generate your output.
>> 
>> Try putting
>> 
>> modules.packages = org.apache.turbine.modules, com.yourcompany.modules
>> 
>> into your TR.properties and then write a class
>> 
>> package com.yourcompany.modules.screens;
>> 
>> import org.apache.turbine.modules.Screen;
>> 
>> public class Myscreen extends Screen
>> {
>>   public ConcreteElement doBuild(RunData data)
>>   {
>>     ConcreteElement ce = new StringElement();
>>     ce.addElement("Hello World");
>>     return ce;
>>   }
>> }
>> 
>> and request
>> 
>> ...your turbine url../screen/MyScreen
>> 
>> which should execute the doBuild() of that class above and render
>> it in a (possible Template) layout.
>> 
>> If you don't run a template service at all (remove it from TR.props),
>> you might need a page class which could extend DefaultPage and maybe a
>> layout class (if you don't have one, the page class will render the
>> screen directly).
>> 
>>      Regards
>>              Henning
>> 
>> (Hm, we might want to have a default page and layout class which is
>> used if we don't use a template service but want to render the output
>> of a class.)
>> 
>> -- 
>> Dipl.-Inf. (Univ.) Henning P. Schmiedehausen          INTERMETA GmbH
>> [EMAIL PROTECTED]        +49 9131 50 654 0   http://www.intermeta.de/
>> 
>> Java, perl, Solaris, Linux, xSP Consulting, Web Services 
>> freelance consultant -- Jakarta Turbine Development  -- hero for hire
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>> 
>> ---
>> Incoming mail is certified Virus Free.
>> Checked by AVG anti-virus system (http://www.grisoft.com).
>> Version: 6.0.459 / Virus Database: 258 - Release Date: 2/25/2003
>>  
>> 

>---
>Outgoing mail is certified Virus Free.
>Checked by AVG anti-virus system (http://www.grisoft.com).
>Version: 6.0.459 / Virus Database: 258 - Release Date: 2/25/2003
> 

>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]

-- 
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen          INTERMETA GmbH
[EMAIL PROTECTED]        +49 9131 50 654 0   http://www.intermeta.de/

Java, perl, Solaris, Linux, xSP Consulting, Web Services 
freelance consultant -- Jakarta Turbine Development  -- hero for hire

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to