Re: [e4-dev] Lessons from Vista

[yves.yang@xxxxxxxxxxx]

In e4 home wiki page, there are three aims:
  - Simplify the Eclipse programming model
  - Enable the platform for use on emerging web-based runtime technologies
  - Broaden participation in development of the platform

>From the users' perspective, there are in fact two: 1st and 2nd. The first
is development benefit and the second is runtime one. So we need to really
focus our communications on the two aims.

As for "Simplify the Eclipse programming model", I think we should promote
more about declarative UI (including declarative Style - CSS), which is
well known programming model in web environment. But is not well known in
eclipse. And this programming model simplifies a lot application
development by providing a unified declarative language, which separates
UI specification and implementation, and allows all tools to work
together.

Best regards
Yves YANG
> All,
>
> I came across this interesting blog post which discusses some of the
> mistakes made and lessons learned from Windows Vista...many of which
> likely
> apply to e4.
>
> The lesson which resonated most with me was the first one: "Make sure the
> product has clear user benefits...". As developers, we always spend a lot
> of
> time talking about features and technology. But for e4 to be successful, I
> believe we need to talk more about the benefits that users and adopters
> will
> gain.
>
> Enjoy!
>
> [1]
> http://blogs.forrester.com/consumer_product_strategy/2009/09/lessons-from-th
> e-windows-vista-era.html
>
> Mike Milinkovich
> Office: +1.613.224.9461 x228
> Mobile: +1.613.220.3223
> mike.milinkovich@xxxxxxxxxxx
>
>
> _______________________________________________
> e4-dev mailing list
> e4-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/e4-dev
>