[Date Prev][Date Next]
[Thread Prev][Thread Next]
[Date Index] [Thread Index] [New search]
To: Scott Prentice <sp@xxxxxxxxxxxxxx>, Rick Quatro <frameexpert@xxxxxxxxxxxx>
Subject: Re: Apply Default Attribute Values
From: "Lynne A. Price" <lprice@xxxxxxxxxxxx>
Date: Sat, 17 Dec 2005 07:35:12 -0800
Cc: framers@xxxxxxxxxxxxxx, framers@xxxxxxxxx
You're right .. these "default" values that you can define in the EDD, are not as useful as one might hope. They aren't exported to XML and they don't seem to have much purpose. However, the FDK (and I believe the EDD itself) can read the default as a value. So a plugin or structured application may be set up to process all widget elements with the "enabled" attribute set to "on" .. if "on" is the "default", those elements would be processed if the "enabled" attribute has the explicit value of "on" or has no value (<no value>).
It would be nice if there was some read/write rule that allowed you to enable the exporting of "default" values, of some way to make them more real ..
** To unsubscribe, send a message to majordomo@xxxxxxxxx ** ** with "unsubscribe framers" (no quotes) in the body. **