> No problem - just let me know when it's up there and I'll upgrade and
> stat playing with it. The multilanguage stuff is going to be important
> to my customer, but not this weekend ;)
>
> Cheers,
> Tim
>
> --
> Tim Ruppert
> HotWax Media
>
http://www.hotwaxmedia.com <
http://www.hotwaxmedia.com/>
>
> o:801.649.6594
> f:801.649.6595
>
> Hans Bakker wrote:
> > Hi Tim,
> > I have roughly the content and dataResource working in the content
> > component and used the contentList in the hotelbackend.
> >
> > You can edit a website page now, however, i have to add the mutilanguage
> > capability in the hotelbackend..
> >
> > Hans
> >
> > On Friday 26 May 2006 00:45, Tim Ruppert wrote:
> >> Hans, how are things look for new content management organization still
> >> being released this week? I just don't want to spend too much time
> >> laying in content if there's a newly thought out way of doing it coming
> >> out soon.
> >>
> >> Thanks again.
> >>
> >> Cheers,
> >> Tim
> >>
> >> Tim Ruppert
> >> HotWax Media
> >>
http://www.hotwaxmedia.com <
http://www.hotwaxmedia.com/>
> >>
> >> o:801.649.6594
> >> f:801.649.6595
> >>
> >> Hans Bakker wrote:
> >>> Hi Tim,
> >>>
> >>> as you noticed, I am in the process of making this component usefull.
> >>> Let me first emphasize that (as i understood it) about 2 years ago
> >>> David Jones designed and Al Buyers implemented the first version of
> >>> this component.
> >>>
> >>> Since then as you know widgets have appeared and the content component
> >>> was converted to widgets (Andrew?). Although a lot of work was done, it
> >>> was not not completed, that is what i am attempting doing now.....
> >>>
> >>> I am redesigning the backend content part of the opentravelsystem and
> >>> found that the main parts of the content component did not work
> >>> properly so i improved that too.
> >>> if you could wait al least until the end of this week then i will have
> >>> a working backend page editing system using the html editor.
> >>>
> >>> It will be using the content -> dataresource -> electronic text and it
> >>> will be using the multi language feature for text pages.
> >>>
> >>> the connection to the product i do not have yet planned to implement.
> >>>
> >>> -----------------------------------------------------------------------