tiles-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nathan Bubna" <nbu...@gmail.com>
Subject Re: Problems building the showcase app
Date Thu, 25 Jan 2007 15:34:20 GMT
I'm with Greg on this.   I definitely don't think want to add
dependencies on other frameworks to Tiles itself, but i don't know
that it's a bad thing to have them in our example apps.   It's kind of
nice to be able to show people what Tiles can do in various
situations, including with various frameworks.

Separating the Tiles examples from Tiles itself sounds like a pretty
fair solution.   I think option #1 below is my favorite.  I'd like
them to be releasable, so the sandbox would do it for me.  And i don't
think we should consider #3 until we face actual license issues.

On 1/25/07, Greg Reddin <gredbug@gmail.com> wrote:
> Well the showcase app is one of those grey areas.  It's hard to showcase
> everything that Tiles can do without bringing in some bits from frameworks
> we might hook it up to.  In some ways the showcase app almost looks like a
> sandbox for exploring ideas of how you might use Tiles.
> I definitely don't want Tiles to provide the glue code for other frameworks,
> but I don't see anything wrong with us providing (in some way) a package
> that showcases ways you might use Tiles with other frameworks.  Here are a
> few possibilities:
> 1.  Release the showcase app separately, thus making it possible to build
> Tiles without the external dependencies.
> 2.  Create a sandbox and place things like the showcase app there.
> 3.  Put it somewhere else (like Google Code or SF.net)  We did this over at
> Shale to avoid bringing in incompatible dependencies.
> Greg

View raw message