on 12/7/2000 6:37 AM, "David S. Faller" <[EMAIL PROTECTED]> wrote:
> I see what you mean. My problem is about the way your standard Context
> reference works:
> Jetspeed's Navigation classes directly use DynamicURI without any
> VelocityScreen I could extend.
> There are many other references to your DynamicURI I don't want to change...
Ok, so you are saying that because Jetspeed did something stupid, we should
modify Turbine to do something even lamer? I don't think so. Fix Jetspeed.
> Besides that, the main issue is the HTML style: If this class produces the
> URIs for $link it is simply bad style to always return absolute URLs. The
> portal with its HTML code is not flexible enough to be used in more complex
> environments as we use it.
That is complete BS. Using absolute URI's is not bad style if they are
auto-generated. This code has been this way for almost 4 years now. It isn't
going to change now.
Fix Jetspeed to use Turbine correctly.
thanks,
-jon
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
