[
Lists Home |
Date Index |
Thread Index
]
Hi Anthony,
It is a little difficult to answer your comments because you are not
providing much detail. but...
From one of your previous question about having a great of duplicate
information - should you code it all up in the final delivery format? I
would say no.
Say you have a great many user polls. You could mark it up like:
<poll>
<question>Do you have a grasp on what you are trying to
accomplish?</question>
<answers type="yes-no"/>
<!--
<answers>
<answer>Yes</answer>
<answer>No</answer>
</answers>
-->
</poll>
You could use XSL to transform it out to a dynamic template
representation so that it is formated in the look and feel you want. the
transform adds radio button inside a form if the user has not responded.
Or, it presents poll result if the user has taken it. Something like:
#if (hasTakenPoll($userID))
show poll formated to dispplay results
#else
show poll formatted as a form to be submitted
#end
-Rob
Peter Hunsberger wrote:
> On 2/27/06, Anthony Ettinger <aettinger@sdsualumni.org> wrote:
>
> <snip/>
>
>>>Perhaps if you can tell us the general requirements someone may have
>>>specific recommendations for meeting them. Is this intranet,
>>>internet, extranet? What kind of data volumes? What kind of back-end
>>>interfaces? What kind of user population? Any built in hardware or
>>>software assumptions (eg. Oracle, MS, Linux, Sun, SAS or whatever)?
>>>How much customization? How many pages?
>>>
>>
>>L10N support, large-scale public web sites, accessible on multiple
>>platforms.
>
>
> Targetting 10,000's or millions of users? Lots of content (CMS)?
> Forms? Ecommerce (back end databases)? Any target deployment
> platforms biases (Windows, Linux)?
>
|
