GWT issues while waiting for gwtproject ?

[stuckagain]

Hi,

Are we allowed to add bugs in the bugtracking in the middle of the migration to gwtproject ?

I recently added a few and I hope that sometimes they will be sorted out.

My last one was a performance bottleneck on HTMLPanel with many widgets being added 

(due to the very inefficient WidgetCollection implementation).

https://code.google.com/p/google-web-toolkit/issues/detail?id=8105

After looking at my reported bugs, I can see that most of my bug reports never made it to being implemented or even accepted or rejected (one got fixed quickly since I contributed the change)

I hope that the gwtproject will improve on this - it is a really frustrating feeling and makes me wonder if I should stick on using GWT and reorient to non google technologies instead (Axing Google Reader will probably drive me over the edge if I don't find a decent alternative pretty soon). 

David

[Ümit Seren]

Any reason for not using CellWidgets instead of HTMLPanels ? 

[Jens]

You can still file bugs to the tracker. I guess its just missing men power to keep the tracker up-to-date and verify/triage issues. Also the tracker is pretty huge and issues can be missed easily, especially if they are not up-voted. 

Regarding Google Reader: I switched to feedly and it works pretty well.

-- J.

[stuckagain]

Hi,

The HTML that is being put in the HTMLPanel is generated and inserted as one big HTML string.

The HTML can either be generated in Javascript or on the server.

If CellWidgets are an alternative then I am certainly interested in checking them out, but I though they were only useful in CellTable and CellTree.

David

[stuckagain]

Jens,

That would be an understatement :-) 

I am still positive that the bug triage disaster gets fixed because that is fundamental to the success of opensource. And I saw in the gwt-steering news group that they are going for some interesting roadmap, so I live in hope.

I would love to contribute, but only if I can be sure that it will get accepted (most of the time).

I can not keep on defending the usage of GWT to my boss/company if we don't get some minimal feedback and support. I need to do a technology assessment right now, and I really don't know how to defend the choice right now.

Some people have talked about AngularJS, Dart and other interesting technologies, but that is Google tech as well, so potentially subject to be scrapped much faster than what we like.

As for Feedly: it does not work in IE. I need Chrome, iOS and IE support for a feed reader. But let's not dwell on this subject in this newsgroup. 

David

[Jens]

That would be an understatement :-) 

I am still positive that the bug triage disaster gets fixed because that is fundamental to the success of opensource. And I saw in the gwt-steering news group that they are going for some interesting roadmap, so I live in hope.

I would love to contribute, but only if I can be sure that it will get accepted (most of the time).

In fact if GWT would have a really good issue tracker then the issue tracker itself would give you a pretty good picture about the roadmap (excluding "features" that are not related to source code). 

I think the GWT team is happy about all contributions and if they pass the code review I don't see an issue with accepting contributions. If an issue isn't noticed but you have a patch ready then you should just "ping" on the contributors group.

 

I can not keep on defending the usage of GWT to my boss/company if we don't get some minimal feedback and support. I need to do a technology assessment right now, and I really don't know how to defend the choice right now.

Some people have talked about AngularJS, Dart and other interesting technologies, but that is Google tech as well, so potentially subject to be scrapped much faster than what we like.

Totally understandable.  Especially if your boss asks "How many open issues does GWT have?" and you must answer "~2600" :-) Maybe its worth it to kick the current issue tracker, create a new one and asking people to resubmit their issues if they feel its worth it and the GWT version isn't too old. Issues you loose that way will be resubmitted sooner or later by others. Cleaning up the current issue tracker is probably to much work. 

-- J.

[Thomas Broyer]

On Monday, April 15, 2013 4:18:33 PM UTC+2, stuckagain wrote:

Hi,

Are we allowed to add bugs in the bugtracking in the middle of the migration to gwtproject ?

We have no plan to move the issue tracker. At least not in the near-future.

[Ümit Seren]

Well you can use a CellWidget (http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/user/cellview/client/CellWidget.html). 

The nice thing is that you can actually create a custom cell that you can use inside a DataGrid/CellTable/CellList/CellTree and also use it outside of these via a CellWidget.

[stuckagain]

I glanced at the CellWidgets and Cell.Context class and it does look too much row/column based to me.

I am still not convinced that this is what I need, but I will try and setup some proof of concept to use CellWidgets. On the other hand, this is really mostly a client side technology, while I need the ability to also render serverside, used for reporting or for slower browsers.

I'm rendering a form defined in a XSD, the XSD can be a few megabytes big, so we are talking about huge forms here. And the layout needs to be flexible, not constraint to row/column positioning like in a table or tree. Although a tree does come very close to what I need, so if I can finetune the CellTree maybe I can get close to what I want. if only we had a CellTreeTable with scrolling, resizeable columns, ... etc. 

David

[Ümit Seren]

You can actually use a CellWidgets and render any HTML content you like (divs, spans,etc).  You are not bound to row/column like representations. For example I used CellWidgets to create "information cards" (containing some text and a picture and some links). 

You can then drop the CellWidgets anywhere you like. 

Or you can also implement your own CellTableBuilder to create your own representations that doesn't rely on tables/td/trs

--
You received this message because you are subscribed to a topic in the Google Groups "Google Web Toolkit" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/jsnYj0LkLgE/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to google-web-tool...@googlegroups.com.
To post to this group, send email to google-we...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.