FYI, we used to have JNLP links for most of the demos, but we had to take them 
down a few months back because a bug in one of the recent JRE updates caused 
the links to fail. The bug has since been fixed, so we should probably 
re-enable the links now.


On Jan 6, 2011, at 4:22 PM, Greg Brown wrote:

>> The current Pivot samples does not provide good desktop application.
> 
> Sure they do. You can launch any one of them via DesktopApplicationContext.
> 
>> Many example cannot execute without browser unless we write some extra code
>> to provide Application class.
> 
> That is incorrect. In most cases, an Application can be launched either via 
> BrowserApplicationContext or DesktopApplicationContext without any changes.
> 
>> If you want to emphasize such Java desktop usage scenario, it is better to
>> enhance these sample/source/tutorials.
> 
> The tutorial applications are meant to serve as "live" demos within the 
> documentation. We would not be able to do this if they were packaged up as 
> applications - we'd have to rely on screen shots, which is much less 
> effective.
> 
>> Also if desktop application is more focused, the full advantage of Java
>> language, e.g, static type checking, generics, annotation, (some builder
>> style declarative approach) to be employed in Pivot.
> 
> I don't see the distinction. Pivot already takes advantage of these features, 
> and they apply regardless of whether the application is deployed via the web 
> or desktop.
> 
>> Pivot lacks basic CRUD pattern which is supported in other frameworks.
>> As I provided some sample CRUD code using generics, there are potential that
>> Pivot can provide a easiest framework to develop rapid (yet reasonably
>> sophisticated, and maintainable) GUI front-end.
>> If these library are more provided(not just individual features which must
>> be combined to develop actual application), Pivot will be more attractive.
> 
> Pivot is a volunteer-driven effort with limited resources. If you believe 
> that this is a gap that should be filled, please consider submitting a patch 
> for it.
> 
> G
> 

Reply via email to