Hello,
It looks like we need to talk about what compatibility could mean for
Tobago. We are compatible to JSF since Tobago runs on top of MyFaces
and the Sun RI. We invested some time to be compatible to Facelets. Most
of the Shale stuff works with Tobago, too.
Other compatibility issues are:
- using Tobago controls on Tomahawk pages (an HTML page with Tomahawk
and standard HTML controls)
In general there are issues with renderkit ids if I remember correctly.
Tobago is not (only) a HTML renderkit. On a normal JSF page a Tobago
control is missing its layout and theme context. It should be possible
to provide this -- using a theme which fits to the rest of the page and
giving Tobago a rectangular area to layout within.
- using Tomahawk controls (or controls from other renderkits) on Tobago
pages
Again I think we have problems with different renderkit ids.
Additionally Tobago needs to know about the size of the control and
needs some means to adapt the size for layouting. And the page developer
needs to customize the CSS of the control which fits to the Tobago
theme. Making the included control respond to theme changes might be
pretty complicated.
Best regards,
Arvid
Martin Marinschek wrote:
+1 from me for a release of Tobago.
In any case - are there any new efforts to make Tobago more compatible
to the rest of the JSF world?
We've all put a bit of effort into compatibility in tomahawk and impl,
and I'd like to see some effort in the tobago code base as well...
regards,
Martin
On 9/13/06, Mike Kienenberger <[EMAIL PROTECTED]> wrote:
Is this intended to be a Java 1.5-only release for examples?
I get this error when trying to run the examples under java 1.4.2.
java.lang.UnsupportedClassVersionError:
org/apache/myfaces/tobago/webapp/TobagoServletContextListener
(Unsupported major.minor version 49.0)
On 9/13/06, Bernd Bohmann <[EMAIL PROTECTED]> wrote:
> Hello,
>
> you can download the tobago examples from
>
>
http://people.apache.org/builds/myfaces/nightly/myfaces-tobago-example-1.0.8-SNAPSHOT-bin.tar.gz
>
> the 1.0.8-SNAPSHOT is the next release
>
> Mike Kienenberger wrote:
> > See this thread:
> >
> >
http://mail-archives.apache.org/mod_mbox/myfaces-users/200604.mbox/[EMAIL PROTECTED]
> >
> >
> > On 9/13/06, L Frohman <[EMAIL PROTECTED]> wrote:
> >> I was wondering the same thing, why isn't Tobago being "merged"
into
> >> Tomahawk?
> >>
> >> -----Original Message-----
> >> From: Mike Kienenberger [mailto:[EMAIL PROTECTED]
> >> Sent: Wednesday, September 13, 2006 8:34 AM
> >> To: MyFaces Development
> >> Subject: Re: [VOTE] Release Apache Tobago 1.0.8
> >>
> >> On 9/13/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
> >> > FWIW, this is the kind of thing that motivates "a MyFaces
committer is
> >> > a MyFaces committer", as opposed to trying to segregate folks
only
> >> > interested in Tobago. On the other hand, the fact that only a
small
> >> > number of folks in the MyFaces committer community seem
interested in
> >> > Tobago is a danger signal.
> >>
> >> I wasn't around with Tobago joined up, but my experience so far is
> >> that it's
> >> almost impossible to be both a Tobago and a Tomahawk
user/developer.
> >>
> >> I can't speak for anyone else, but I don't have time to work
with two
> >> incompatible frameworks.
> >>
> >> I tried to start a dialog a while back on merging Tobago and
Tomahawk
> >> (or at
> >> least making them more compatible) but nothing really came of it.
> >>
> >> If Tobago and Tomahawk aren't going to be made compatible with each
> >> other, I
> >> think perhaps that Tobago should become its own top-level project.
> >>
> >> Yes, there are some parts that overlap (like the proposed
commons jar for
> >> non-rendering code), but not enough that I feel qualified as a PMC
> >> member to
> >> vote on a Tobago release.
> >>
> >>
> >
>
