on 4/1/00 8:44 AM, Kevin A. Burton <[EMAIL PROTECTED]> wrote:
> I should have probably officially just done a -0. Wasn't that strong
> but hadn't had my morning coffee yet.
thanks.
> I don't like the way we aren't using cocoon for this. We have an
> official Apache project dedicated to separating the UI from the layout.
> +1024 for MVC design and separating the API/logic from the
> presentation. But lets use our own tools. IMO Webmacro is a dead end
> technology. XML is the future. If you aren't using it you are
> seriously limiting your potential.
I don't see WM as a dead end technology. There are plenty of places where
people are not going to want to write stuff in XML/XSL/X*. WM is brain dead
simple and designers (ie: non programmers) "get it". I'm not convinced of
that yet with X* technologies because they are deadly moving targets. 6-12
months from now, that probably won't be the case, but for now, that is the
fact of life. FYI, PHP is not a dead end technology for this exact same
reason.
> Jetspeed is going down this road. There are currently some impl points
> that Cocoon falls down on. So that is what the point of OSS is that you
> fix them.
Dude...I'm holding off on Cocoon in Turbine exactly for this reason. I'm
watching to see what YOU do with Jetspeed. Sorry, but myself and others just
don't have the time to sit and try and shoot at the moving targets all the
time. You do. I'm happy about that.
> One of the things I was thinking about was an XHTML -> ECS XSLT
> stylesheet. So that you write up your UI in XHTML and then it will
> write out ECS for you. The html2ecs (or whatever is called) is
> currently now recommended but if you did it in XHTML it wouldn't have
> any problems and would be within the "correct" and strict domain of
> XML. The Admin console for Jetspeed is this way sort of. Currently you
> can dock in any Portlet. Right now they are just basic ECS portlets but
> this isn't necessary. You could do a Cocoon Portlet too.
Great ideas. Make it happen. ;-)
> I wanted to see if this model could be integrated into Turbine. The
> problem is that it relies on Portlets so ... yeah. Regardless I want to
> see both paths merge some day.
I want to see it into Turbine as well. I wrote that in my paragraph that I
copy/pasted into my last email. You are the person who is in charge of this
front because you are the most qualified. Make it happen. ;-)
-jon
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
