Good idea, Dan.
I haven't tested everything. I know that they made some changes to the validation library to better handle certain data
types, but I can't remember which ones (datetime I think?). Anyway, I am pretty sure that most of it is intact.
I think if you study what they do in a form a little, you can handle it. I just had a situation where I had to place a
question mark image within a DisplayAddForm label attribute, so that when a user clicked on the image, it would launch a
popup window displaying help. (BTW, creating a helpTopic Category in the CMS allows you to create popup help for your
app that you can let selected users modify. This is pretty slick.)
Here is what the tag call looks like:
<cf_DisplayRadioGroup column="Team"
label="Team: <a href=""JavaScript: newWindow =
openWin('#Application.absoluteURLRoot#/chit/help.cfm?helptopic=ChitTeamHelp', 'helpWin', 'width=300,height=200,left=200,
top=100, toolbar=0,location=0,directories=0,status=0,menuBar=0,scrollBars=0,resizable=0' ); newWindow.focus();""><img
src=""#Request.layoutImages#/questionmark.gif"" align=""texttop"" border=""0"" alt=""Team Help""></a>"
required="Yes"
default="AES"
separator=" "
type="varchar(5)">
Well the problem with this approach was that the validation for the fields on the form use the label as the field name,
so I was getting some pretty interesting looking validation messages, that included the js code for the popup. What I
discovered by looking at the generated source, was that they place all of the validation messages in an array. So what I
did was use the standard qForms syntax after the closing </cf_DisplayAddForm> tag to overwrite the label values in the
array (see below).
<!--- Override default field labels descriptions to omit references to the
question mark popups --->
<script type="text/javascript">
objFormChit["Title"].description = "Chit Title:";
objFormChit["Team"].description = "Team:";
objFormChit["Activity"].description = "Preparing Activity:";
objFormChit["Originator"].description = "Originator:";
objFormChit["Phone"].description = "Phone Number:";
objFormChit["Email"].description = "E-Mail:";
objFormChit["Issue"].description = "Problem:";
objFormChit["ProposedSolution"].description = "Proposed Solution:";
objFormChit["Comments"].description = "Comments:";
</script>
I guess we should start writing up some KB articles on some of these.
HTH,
Jeff
_______________________________
Jeff Fleitz
Tekquest, Ltd
Integrated Digital Solutions
http://www.tekquest.com
_______________________________
Dan O'Keefe wrote:
Jeff,
Since PLUM uses qForms, I was wondering if there is an elegant way for
us to manually invoke qForms functionality on a PLUM form. Now I think I
read some where in the docs or an email that PLUM uses a modified form
of qForms or a subset of qForms, not sure of the exact terminology used,
but I wonder if that means functionality was chopped out of the lib. If
I get time tonight I do a winDiff of the lib. I came across an area
recently myself where I was wondering the same thing.
Dan
----- Original Message ----- From: "Jeff Fleitz" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Tuesday, February 08, 2005 11:23 AM
Subject: Re: [plum] Filtered Select - brainfart morning
Hi Tim,
It seems to me that you would want to normalize your database, so I
would go with separate tables. Using Plum shouldn't influence db
design issues, IMO.
On the question of the forms, are you planning on putting 2 select
menus on one form, or on two separate forms (ManufacturerAddForm,
ModelAddform) for instance?
cf_FilteredSelect doesn't support chaining like that at this time,
although I asked for it. Maybe Adam and David will consider it for v
1.1. If you are going for the former option, you will have to do
something like use Nate Weiss' CF_TwoSelectsRelated tag, bracketed
between a <cf_DisplayExtraFormContent> tag pair. I did this on a
project last year, and had to use custom queries to drive it. qForms
supports populating multiple selects, also, so that is another
option. But no native way in Plum to popluate one select dymanically
from another at this point.
HTH,
Jeff
Tim Blankenship wrote:
Alright I know I should be ashamed, well I am, I need a little help.
What I want to do is have a form that lists some info on server
hardware that has a filtered select list on it.Basically I want to
choose a manufacturer (HP, IBM, Dell...) and when I choose the
manufacturer the Models are populated for the specific Manufacturer.
Example I choose HP in a select menu the next select menu is populated
with Proliant 123, Proliant 234, Proliant 345. So inturn what is the
best method for the DB design, a single table like
ID, man_ID, manufacturer, mod_id, model or should I split them
Manufacturer table
man_id, manufacturer
Model table
mod_id, model, man_id
I know this is somewhat simple but I am just having a brainfart this
morning.
For testing and client approval I am making it in Access but
eventually I will recreate this in Oracle.
**********************************************************************
You can subscribe to and unsubscribe from lists, and you can change
your subscriptions between normal and digest modes here:
http://www.productivityenhancement.com/support/DiscussionListsForm.cfm
**********************************************************************
**********************************************************************
You can subscribe to and unsubscribe from lists, and you can change
your subscriptions between normal and digest modes here:
http://www.productivityenhancement.com/support/DiscussionListsForm.cfm
**********************************************************************
**********************************************************************
You can subscribe to and unsubscribe from lists, and you can change
your subscriptions between normal and digest modes here:
http://www.productivityenhancement.com/support/DiscussionListsForm.cfm
**********************************************************************
