Google Web Toolkit

Friday, March 28, 2014

Re: Development Mode will not be supported in Firefox 27+

Hello James,

after replace ui.xml by pure javadoes the application compile faster? I thought ui.xml views increment a lot the compiler time.

Juan

2014-03-27 23:58 GMT-03:00 James Wendel <jmwendel@gmail.com>:

My company got screwed by using GXT2 with gxt-uibinder library that broke with GWT 2.5 due to compiler changes. We've been stuck on GWT 2.4 for that reason as we had 100+ .ui.xml files to convert to pure java. We finally did the work, but it was definitely a painful lesson.

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: fullscreen and popuppanels

On Friday, March 28, 2014 3:07:20 PM UTC+1, Vassilis Virvilis wrote:

Hello,

I am playing with the fullscreen capability of newish browsers. It works fine for my GWT widget but the PopupPanels are not visible when in fullscreen mode.

They are not visible because the popup panels are children at the body element of the html and this is not visible anymore. You see my widget resides in a div and this div is promoted to fullscreen. Everything else not belonging to that div are not visible.

The problem is even bigger with submenuItems which are also popups. Assuming I am creating my custom MyPopupPanel which does not belong to RootPanel I would still have to fork MenuBar and MenuItem to make them use MyPopupPanel.

Any ideas?

https://code.google.com/p/google-web-toolkit/issues/detail?id=3855 is marked as PatchesWelcome ;-)

Note that https://code.google.com/p/google-web-toolkit/issues/detail?id=8538 gives a workaround, but of course it wouldn't work for menus. If PopupPanel supported custom parent elements, then submenus should just use the same parent element as their parent (recursively up to the MenuBar)

fullscreen and popuppanels

Hello,

I am playing with the fullscreen capability of newish browsers. It works fine for my GWT widget but the PopupPanels are not visible when in fullscreen mode.

They are not visible because the popup panels are children at the body element of the html and this is not visible anymore. You see my widget resides in a div and this div is promoted to fullscreen. Everything else not belonging to that div are not visible.

The problem is even bigger with submenuItems which are also popups. Assuming I am creating my custom MyPopupPanel which does not belong to RootPanel I would still have to fork MenuBar and MenuItem to make them use MyPopupPanel.

Any ideas?

Vassilis Virvilis

Re: How to style a Row of CellTable when user click on a Cell (GWT)?

redraw() will generate some HTML and inject it with innerHTML, so your getRowElement() no longer exists after redraw().

Are you trying to re-implement SelectionModel and DefaultSelectionEventManager's createWhitelistManager or createCheckboxManager?

On Friday, March 28, 2014 2:47:21 PM UTC+1, Tom wrote:

I want that when user click on a Cell belonging to a row of CellTable, then it will style the row.

So I tried:
 myColumn.setFieldUpdater(new FieldUpdater<String[], String>(){ @Override public void update(int index, String[] object, String value){ if(mycondition){ myCellTable.getRowElement(index).addClassName(getView().getRes().css().blueText()); myCellTable.redraw(); } } }); 
As stated in the above code, we can capture the index of the row, so row no is not the problem, but why nothing happened.

So How to fix it?

How to style a Row of CellTable when user click on a Cell (GWT)?

I want that when user click on a Cell belonging to a row of CellTable, then it will style the row.

So I tried:

       myColumn.setFieldUpdater(new FieldUpdater<String[], String>(){              @Override              public void update(int index, String[] object, String value){                  if(mycondition){                      myCellTable.getRowElement(index).addClassName(getView().getRes().css().blueText());                      myCellTable.redraw();                  }                }          });

As stated in the above code, we can capture the index of the row, so row no is not the problem, but why nothing happened.

So How to fix it?

Re: Only subset of HTML supported by HTML class?

Thanks. That was helpful. I checked through Chrome Developer Tools. The HTML is correctly getting to the browser. Turns out GXT's reset.css neutralizes much of HTML. Presumably this is done for a reason and I can't just get rid of it. Working around it is beyond me at the moment.

Thanks!

Blake

On Fri, Mar 28, 2014 at 4:05 AM, Nicolas Weeger <nicolas@nekoko.fr> wrote:

Hello.

Using GWT 2.5.0, I just tried that:

final VerticalPanel panel = new VerticalPanel();
panel.add(new HTML("abcde hello

emphisizedthe break bold
text<ol><li>aaaaa</li><li>bbbbbb</li></ol>",true));

and it renders as expected.

Can you check using eg Firebug or some developers tools whether the tag
is actually present? Is there any chance you have a CSS which resets em/strong
without giving a font-weight or font-style thus leading you to think they
don't work?

Hope this helps

Kind regards

Nicolas

Le vendredi 28 mars 2014 02:02:45, Blake McBride a écrit :

> Greetings,
>
> I am trying to render some HTML. I am using:
>
> RootLayoutPanel rlp = RootLayoutPanel.get();
> rlp.clear();
> rlp.add(new HTML("abcde hello emphisized
> the break bold text<ol><li>aaaaa</li><li>bbbbbb</li></ol>",
> true));
>
>
> The and work. All the rest is ignored. Why is only a subset
> supported? I don't understand why it wouldn't just insert what I specify.
> Is there a way for me to add arbitrary html?
>
> Thanks.
>
> Blake

Re: Development Mode will not be supported in Firefox 27+

Could you elaborate on how you have your POM setup? I'm trying to make the switch to SDM but I get errors running run-codeserver. Your setup seems ideal I'd like to know how you have both of those things configured. Not sure it matters but I use IntelliJ instead of Eclipse...DM worked great.

-Dave

On Tuesday, March 4, 2014 2:36:41 PM UTC-7, Joseph Lust wrote:

I'm surprised more folks are not excited to jump ship to SuperDevMode.

I'd argue Eclipse DevMode is more pain than it's worth. Certainly, it is very cool to have your backend and frontend breakpoints set and hit on the same screen. Yet I've spent a lot of time trying to all of the Run Configurations setup properly. Have a multi-module project? Have an OSGi project? Trying to debug a remote server? Working with JSO's? It's a bit of trial and error and not always possible. Startup is slow. Recompile is even slower and it's a memory hog, crashing with OutOfMemory more than I'd like. Plus, you need a ring of chicken blood around your computer to ward of breakages with new browser upgrades.

Enter SDM. I open one console type mvn tomcat7:run-war. I open a second and run mvn gwt:run-codeserver. No need for configuration settings windows and embedded Jetty's. No need to even have an IDE at all! Personally I find simpler, imperative tooling much easier to use and troubleshoot. Add to this Chrome Dev Tools will be a full fledged IDE soon at the rate they're adding features and FF Dev Tools have also come a very long way since FireBug.

Finally, don't we want the GWT team to spend their time building new features rather than keeping old tooling alive in the ICU? I think GWT's hit an inflection point where dumping IE everything and DevMode would free up a lot of resources. Many projects never make such painful decisions and become dinosaurs for it. I hope GWT does not.

Sincerely,
Joseph