On Mon, Jan 3, 2011 at 10:08 AM, Greg Brown <[email protected]> wrote:
> > I think some people would prefer to use BXML style, but the point here is > Java API based development should be equally well supported.(without > assuming the use of BXML). > > It is. You are not required to use BXML. Anything that can be done in BXML > can also be done in Java or any other JVM language. BXML is just a shortcut > to writing such code by hand. > I think just telling the technological possibility is not good enough to claim Java API based approach is supported.(it similar to claim machine language can support anything) If it can support readable GUI description in Java, we should claim it supports Java API based development. > > > I think Pivot is, in the basic Java oriented approach, more closer to > Vaadin than Silverlight etc. Vaadin explicitly avoid using any form of XML > as basic policy, it emphasizes pure Java based approach. I wonder Pivot > developers have looked at the project.. > > I am loosely familiar with Vaadin. However, I believe Pivot and Vaadin > address different use cases. Pivot (like Flex and Silverlight) runs on the > client, whereas Vaadin runs on the server. To me, Vaadin seems more closely > related to something like Canoo than Pivot. > > Yes, Vaadin is server based stateful session approach. So it has a problem to support cloud based server infrastructure like Google app engine. That was the main reason I was more interested in Pivot. But for GUI developing phase, these difference of deployment approach are not much noticeable. In this sense, I thought Pivot and Vaadin is similar. And I expected Pivot be similar to Vaadin when I start evaluating Pivot. -- Cheers, calathus
