On Saturday, June 1, 2002, at 09:29 AM, Robert Koberg wrote:
>>> It seems so strange that you hard code these things...
>>>
>>> This should never be a problem. I don't understand the reluctance to
>>> use basic XSLT features, but by referencing the link/menu data
>>> through the document function (or whatever the right way is for
>>> cocoon - strange that it has to be different...) you totally
>>> eliminate this problem. If the link exists it is guaranteed to be
>>> correct. If a link 'links' to something that does not exist, either
>>> do not render the <a href/> (just the text) or wrap it in a span that
>>> has font-color:red or something.
>>
>>
>> Part of the problem, Rob, is that we are dealing with static html
>> files that are merged together. The live site is produced from static
>> html files which result from release branch builds -- also html. We
>> have to take partial results of a release branch build (files and
>> directories) and merge with existing live site cvs files and
>> directories. It's inefficient, yes, but Forrest will address this
>> issue.
>
> Really, how? Last week I tried to figure it out given the constraints
> of not using the XPath document function or include/import. I could not
> figure out how to do it. I raised the issue about hard-coded links on
> the forrest list and only one person took the time to investigate it. I
> gave a concrete example. Then he (Ivelin) posed the question to group
> asking if the thread was helpful. I think Steven responded simply with
> 'yes.'
Give our dear friend Steven a break. Don't you think he had at least one
slightly more important issue to deal with last week? I'm completely
amazed he even has time to read emails, let alone respond.
http://marc.theaimsgroup.com/?l=forrest-dev&m=102235588403970&w=2
Diana
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
