Wishlist - What GWT developers want for Christmas

[Joonas Lehtinen]

We just published all of the 2600+ wishes you guys added to the Future of GWT survey on most important things needed in GWT. Take a look:

https://vaadin.com/gwt/report-2012/wishlist

[Stefan Ollinger]

+1 Keep it moving

> --
> You received this message because you are subscribed to the Google
> Groups "Google Web Toolkit" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-web-toolkit/-/81D5pIYdNQ4J.
> To post to this group, send email to google-we...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-tool...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.

[Jens]

A lot to do for Santa. Must be a large Christmas tree to get all these things ;-)

-- J.

[maticpetek]

Dear Joonas,

   We have couple discussion in this forum about given email address to access survey result. Some people see this as interference between commercial interest of Vaadin and community. I don't think so and I also express my opinion. If some company invest their time & resources to prepare survey and present results - this is good for all community and you can have my email to send me product updates. Ok, I also think you have cool product and I want information from your company.

   But could you please explain me why you need access to my Google Contacts information if I login with my Google Account? Or to my friends lists from Facebook if I login with Facebook connect? What will list of my personal friends, family members and business partners have to do with GWT wishes voting system? Frankly speaking, I think this si very bad sign for feature customers (like I am) for you company product & services. And as I say - you have cool product and I really wish you all the best. 

Regards,

   Matic

------------------

GWT stuff twitter  - http://twitter.com/#!/gwtstuff

[xvik]

Sorry, but dont understand this. 

First report was elegant and structured, but this wishlist.. what feedback you want to receive from this ..sorry.. heap of sentences?

Its overduplicated! From all 2600+ requests there are only about 30 unique.

And when we get rid of out of scope requests, like make it server side, server push support, out of the box widgets like in sencha etc. we will see all the issues mentioned in first report

(compile time ,modularity, dev mode improvements etc)

Everyone know these real important issues.. what's the point of this whishlist, except vaadin marketing?

среда, 12 декабря 2012 г., 1:45:59 UTC+7 пользователь Joonas Lehtinen написал:

[Joonas Lehtinen]

Hi Matic,

Vaadin.com login should only be requesting minimal amount of information from Twitter, Google or Facebook to implement those login options. I do not know the details of the login implementation, but I am sure we do not need, store or use friend list or contacts information. I'll ask the team to check if there is a bug in the implementation (requesting more info than needed).

Thanks for noting!

- Joonas

[Joonas Lehtinen]

We simply did not expect to have this many answers. While we would love to have been able to deliver another edited report on these answers, this tsunami of wishes was so overwhelming that we had two options - either publish the data unedited or not publish it at all. We hope and believe that it could be useful as such for the community.

If anyone other from the community would be willing to step forwards and compose statistics and summary from the wishlist, it would certainly be interesting reading.

[Clint Gilbert]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I imagine they want your contacts for the same reason they want your
email and social network info: to send out marketing spam (or
information, if you see the glass half-full).

There's an easy workaround though: sign up with an address from
Mailinator or another throwaway-email service.

> <https://vaadin.com/gwt/report-2012/wishlist>
>
> --
> You received this message because you are subscribed to the Google
> Groups "Google Web Toolkit" group.
> To view this discussion on the web visit

> https://groups.google.com/d/msg/google-web-toolkit/-/eTea0PDOwtAJ.

> To post to this group, send email to google-we...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-tool...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iEYEARECAAYFAlDHj2UACgkQ5IyIbnMUeTsJbwCfSmWaf7mSQrf0xtV7NiYn9lOP
PjcAn0ihnOM6YZrReS6PSwGjw0GPrz53
=e+m4
-----END PGP SIGNATURE-----

[xvik]

Joonas, thank you for answer.

I hope that it will be useful for community ..somehow.

But please, be more careful in the future, not to be looked like you use gwt just to promote vaadin.

Vaadin is great, i admit (I've used it and I like it), but I care aboout gwt at first place, and report like this, without explanation remark, like in your comment, makes me feel you dont care much of gwt evolution.

I really appreciate all your work with gwt community (finally, gwt start to appear again at d-zone feed),  but just want something more concrete (roadmap draft or issue/feature pool, provided by SC)

Anyway, thank you. 

среда, 12 декабря 2012 г., 2:50:37 UTC+7 пользователь Joonas Lehtinen написал:

[Joonas Lehtinen]

Our team has been buried under Vaadin 7 finalization project. I hope
we are able to start building new features useful for GWT developers
when it is done.

[Joonas Lehtinen]

Looks like our login form is using wrong scope from OAuth API. We'll fix this asap. We are definitely not using contacts (only stored information is persons own email-address).

The wishlist page is quite simple and there is no admin inferface, so there is no be easy way to edit the contents. I think that better than trying to remove duplicates (and for that matter split comments with multiple proposals), you might like to analyze the most important stuff (both by seeing votes and number of similar entries) and publish a blog post about the analysis. This would probably clarify the results.

On Wednesday, December 12, 2012 6:53:09 PM UTC+2, V.B. wrote:

Hello Joonas,
   Thanks for your work on the report and for posting the wishlist.
While I agree with the previous post that the majority of the 2,600 wishlist items are duplicates, there are several other valid items buried in the middle or near bottom of the list, which were not covered in the report. At the moment, these are not getting much attention because most voters stop looking after the first 50 or so items. For example, I found comments from a number of members about bugs that don't get fixed (e.g. some are even 2-3 years old), and patches that don't get accepted. I also saw some very important comments about how GWT needs to be better marketed/publicized in order to attract more developers. I suspect that issues like these would get much more up-voting if they were more visible. Perhaps a member of the community (me, for example) could volunteer to remove duplicates, or perhaps the list could be randomized every time it's viewed. Anything to make sure all the important issues get attention.

On a separate note, I think even more members might log in and vote if not for the Access-to-Contacts requirement.

Thanks again.

[Joonas Lehtinen]

Just to report back. We were able to fix the issue and vaadin.com is no longer asking access to contacts when you signing in with your Google account. 

- Joonas

[darkflame]

"I was unable to find anything generic - I needed to pick an OAuth
(OpenID was out of the question, unfortunately)"

Just curious here as to why? As a developer I often wondered why
OpenID has such a slow takeup relative to Facebook logins. I have only
ever used a OpenID implementation myself for a forum, which was
essentially pre-built, I just made a GUI for it. Is it much harder to
implement then other login methods? Does it have unsuitable
requirements?

> >> viewed. Anything to make sure *all* the important issues get attention.

[Mike Dee]

One thing that I didn't see and I would have as number #1 on the list is better documentation and improved ease of use, particularly for those starting with GWT.  Much of the documentation is written for those already with an understanding of GWT or lack of consideration that a user may be a newbie.  

Some examples:

1) Use of styles in a GWT app is still a mystery.  There are many options: CssResource, local styles in uibinder, obfuscation, etc.  Same can be said for localization.

2) Take a look at some of the sample code in the GWT widget showcase.  Some of it is very dense.  The point is to show how to write a widget, not show one's prowess with Java.