Shindig is an open source project so feature choices are only as good as the contributions we get. I try to not break the PHP side of things, but don't know it so well. I'd love to see more PHP contributions, there's plenty of interesting work to be done there...
One good thing is that you can implement portions of your system in Java and portions in PHP. For example do gadget rendering in Java and use PHP to implement the data APIs. On Fri, May 7, 2010 at 1:22 PM, John Hjelmstad <[email protected]> wrote: > My 2c: > > There's no overarching strategy regarding feature set compatibility in PHP > vs. Java Shindig. They tend to be pushed forward by people using them > directly, parties who typically don't have the bandwidth to > double-implement > everything. So a schism is somewhat inevitable. > > --j > > On Fri, May 7, 2010 at 4:17 AM, Evgeny Bogdanov <[email protected] > >wrote: > > > Hello, > > > > I'd like to know if possible what is the Shindig strategy concerning > > java and php code. > > I am using PHP version of shindig. I can see that some things are done > > in java and not yet in php. > > Even more, it seems as php version is far behind the java version (in > > both code and sub-community) > > > > Is there any particular strategy to make them more or less the same or > > it might happen in the near future, > > that java version will go ahead and php version won't ever catch it? > > > > I am asking since for me it seems easier to refresh my java knowledge > > rather then implementing things for php > > that is already done in java :) > > > > Best, > > Evgeny > > > > >
