On Fri, Jan 7, 2011 at 4:04 AM, Greg Brown <gk_br...@verizon.net> wrote:
> > I would rather compare this with: > > - Ruby on Rails > > - GWT > > - Vaadin(which is using GWT internally) > > - TurboGear > > - ... > > These are all tools for generating HTML. Pivot is a client-side UI library, > much more closely related to the other platforms I mentioned. > The similarity is not technical, but an idea to develop web application without knowing much about html using programming language(ruby,java,python). Since Pivot bypass the most of issues by using Applet, it may not be similar, but the final result is quite similar as long as Pivot supports such DB and client/server communication issue with some CRUD development support. Also if we take restful API approach, there are not much things to do in Pivot side. We can use existing tools like JPA and several tools to support restful API. I think like UNIX tools, loosely coupled tools which address one thing well and can be combined freely(with pipe) is more powerful than tightly coupled framework which we often found in Java world. > > > If Pivot is just an another desktop GUI library, not many people would > not > > be interested in Pivot. > > I have to disagree. As the project home page says, "it combines the > enhanced productivity and usability features of a modern RIA toolkit with > the robustness of the Java platform". The same cannot be said for any of the > other toolkits I mentioned (Flex and WPF are not Java based, and Swing and > SWT are not exactly modern). :-) > > > For me, it was quite refreshing to know such revival of applet. > > When we started Pivot, I was hoping we'd see a revival of the applet, but > it hasn't really materialized - to the contrary, I see a growing anti-plugin > sentiment in the web development community. Also, developers seem to be more > interested in using Pivot to build desktop apps than applets. To me, these > are pretty strong signals that a change in positioning is warranted. > There is one important advantage of using Applet in software deployment, namely security. If we distribute application as desktop application which are downloaded from unsecure sites, we will have the same problem as windows OS has. Running application within browser as applet would be safe. So if application is targeted to general public, there would be a merit of using Applet. > > > Also android is using Java, so there are some revival of Java on client > > side. > > Exactly - and I think we should look to capitalize on that. We need to get > Pivot running on Android. I have been working on that. > Is it a part of Pivot project? I was also thinking it will be interesting to have Pivot in Android. Right now the most mobile devices have small display, but eventually, like Apple's iPad, the screen size will be bigger. So there may not be big difference between mobile app and desktop app. But the important aspect of these mobile application is network connectivity since they would rely on server side applications. > > > I think it is better to reduce dependency for Java on server side since > > another new language(like Go) may take over in following years which can > > fully utilize new CPU design (multi-core). Also traditional session style > > server application will be not favored in cloud based sever system. > > So in this perspective, Pivot would have good chance to play an > interesting > > role in future. > > Yes, that is one advantage of a client-side toolkit like Pivot - it is > server-agnostic. Of course, there are advantages to using the same > technology on both sides - it avoids the heterogeneous approach you > mentioned in your email (which I call "technology sprawl"). Microsoft has > taken a similar approach with .NET, which can also be used on both client > and server. > > > -- Cheers, calathus
