text editors'; I've attached a small screen shot portion
that's much better than the ASCII and that's a sample of the lower set of
three images. Note that the page horizontal centerline should run between
the two adjacent playing cards.
I now have this UiBinder layout for the lower images
Hi Jens,
Great, it works exactly as I want! Such a simple approach as well, it
should be part of GWT though.
David
On Thursday, February 2, 2012 1:23:57 AM UTC+1, espinosa_cz wrote:
Hi guys,
I manage to put my context panel to the middle of the browser page in
Vaadin. Seem my
Hi,
Maybe you should file a bug report, a center layout or something would be
great! Or indeed support for Alignment.MIDDLE.
I'm in the progress of updating and old code base to standards compliant
mode and centering widget on the window is used all over the place.
Before I could just set
I'm in the progress of updating and old code base to standards compliant
mode and centering widget on the window is used all over the place.
Before I could just set the height of a table to 100% and using 3 columns,
and let the browser figure out row distribution, but this no longer works
as the
build system (instead of Ant). I'm also about to reboot GWT+Maven
integration (more to come by the end of the week, stay tuned).
As part of this effort, I'm wondering which project structure to use as
the default, standard layout for GWT projects using Maven? I'm
particularly looking for advice
On Mon, Feb 25, 2013 at 4:47 PM, dparish dpar...@gmail.com wrote:
I think a major goal should be to cooperate with other container plugins,
specifically Jetty. I've been struggling with getting the Jetty plugin to
fully cooperate w/ the gwt plugin and am astounded at how hard it is to:
1.
of this effort, I'm wondering which project structure to use as
the default, standard layout for GWT projects using Maven? I'm
particularly looking for advice/preferences for GWT library projects (such
as GWT itself, mgwt, Errai, GXT, etc.), not much for GWT applications (the
one you run the GWT
Inline.
On Sun, Feb 17, 2013 at 2:12 PM, Thomas Broyer t.bro...@gmail.com wrote:
Hmm, there's
https://github.com/tbroyer/gwt-sandbox/blob/master/user/gwt-user-core/pom.xml
but
this is work in progress, and unnecessary complicated in some places. This
is ongoing work to moving GWT itself
(more to come by the end of the week, stay tuned).
As part of this effort, I'm wondering which project structure to use as
the default, standard layout for GWT projects using Maven? I'm
particularly looking for advice/preferences for GWT library projects (such
as GWT itself, mgwt, Errai, GXT
On Sunday, February 17, 2013 6:37:38 PM UTC+1, Rich wrote:
Thomas,
Thanks very much for the response.
First, is there any way you can share a POM from one of your projects --
or ideally point me at an entire open source project that uses it?
Hmm, there's
of the week, stay tuned).
As part of this effort, I'm wondering which project structure to use
as the default, standard layout for GWT projects using Maven? I'm
particularly looking for advice/preferences for GWT library projects
(such
as GWT itself, mgwt, Errai, GXT, etc.), not much for GWT
layout for GWT projects using Maven? I'm
particularly looking for advice/preferences for GWT library projects (such
as GWT itself, mgwt, Errai, GXT, etc.), not much for GWT applications (the
one you run the GWT Compiler on).
NOTE: this poll is cross-posted to the GWT and gwt-maven-plugin groups
wondering which project structure to use
as the default, standard layout for GWT projects using Maven? I'm
particularly looking for advice/preferences for GWT library projects
(such
as GWT itself, mgwt, Errai, GXT, etc.), not much for GWT applications
(the
one you run the GWT Compiler
of my main layout
and then, at the end, I make a call on .show() method of the layout class:
I have changed my code removing calls to .draw() subclasses and inserting a
call of .draw() method of my main layout class (instead of using a call to
.show() method);
3) I use always this. marker
method
to the page that I want to close (i.e. I call destroy method on Layout
object) and I launch a custom event in order to load the new page. The
problem is that sometimes (I was not able to find a predefined pattern) the
method MyCurrentLoadedLayout.destroy(), called from my current loaded
with the screensize, I have
read that the best way
is to use the DockLayoutPanel.
I have also read following article:
https://developers.google.com/web-toolkit/doc/latest/DevGuideUiPanels
In this articel it's also recommended to use Layout Panels for better
standard mode support
that the best way
is to use the DockLayoutPanel.
I have also read following article:
https://developers.google.com/web-toolkit/doc/latest/DevGuideUiPanels
In this articel it's also recommended to use Layout Panels for better
standard mode support.
Therefore I have build a very easy example to test
Hello,
I have a widget that sometimes has its LabelElement's field equal to **(maybe
it is the same that saying it is equals to null ?).
I initialize the content of this LabelElement with setInnerText().
But then my layout's alignement change (widgets are not yet aligned) and I
have
Use nbsp; instead.
-- J.
--
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/-/UBQyrMlfRNIJ.
To post to this group, send email to
Am Freitag, 16. November 2012 21:08:16 UTC+1 schrieb Thomas Broyer:
Le 16 nov. 2012 17:59, Daniel Kurka kurka@gmail.com javascript:
a écrit :
Hi Thomas,
I have been out on devoxx and haven`t had time to cast a vote yet.
I think its a good idea to go with a separate package
+1, and integrate well with eclipse too if have this files in src/main/java
2012/11/19 Joseph Lust lifeofl...@gmail.com
In multi module projects, it is quite nice to have the Java sources and
*.gwt.xml files in a single package in src/main/java. Spreading it out into
the resource folder
That's true. But I do not have to edit both Java files and GWT module
descriptors at the same time very often. More often that's the case for
UIBinder/CSS and Java files.
I have multi module projects with several hierarchy levels either but still
prefer the *src/main/resources* option(s).
, and that's the layout I've used for years.
When I ask myself what a truly mavenish layout should be though, I
rather put them in src/main/resources. But what matters most is that
both work and you're free to choose what works best for you (keeping
in mind that if you need/want filtering, then using src/main
On Fri, Nov 16, 2012 at 1:56 AM, Brian Slesinsky bslesin...@gmail.com wrote:
It will be more convenient for Google if all Java code and Java resources
(that is, things in the classpath) are contained in directories named either
java or javatests, and the path from there is where the file should
of view may already know, I'm porting GWT to use Maven as the
build system (instead of Ant). I'm also about to reboot GWT+Maven
integration (more to come by the end of the week, stay tuned).
As part of this effort, I'm wondering which project structure to use as
the default, standard layout
project structure to use as
the default, standard layout for GWT projects using Maven? I'm
particularly looking for advice/preferences for GWT library projects (such
as GWT itself, mgwt, Errai, GXT, etc.), not much for GWT applications (the
one you run the GWT Compiler on).
NOTE
layouts. And because of that,
I think in the long-run in makes more sense for us to try to be as similar
to what a standard Maven project would look like, rather than some weird
mutant layout that no one's happy with.
Of course, that's just my 2c and might be fueled by naive optimism from
having just
Le 16 nov. 2012 17:59, Daniel Kurka kurka.dan...@gmail.com a écrit :
Hi Thomas,
I have been out on devoxx and haven`t had time to cast a vote yet.
I think its a good idea to go with a separate package like src/main/super
for super sourcing.
Why are we thinking of moving resources out of
Oops, my mistake! Carry on.
On Friday, November 16, 2012 12:00:57 AM UTC-8, Thomas Broyer wrote:
The scope of this poll is however not about GWT itself actually (we'll
see if we can apply the outcome to GWT or not; I'd love to do it so
that GWT can serve as a reference, but if it's
I am not quite sure why super-sources should / must be treated differently?
Back i am probably lacking experience and knowledge here
I like the notion the *gwt.xml files are actuallly part of the sources and
not resources for gwt libraries.
So that would be Option 1, without
by the end of the week, stay tuned).
As part of this effort, I'm wondering which project structure to use as
the default, standard layout for GWT projects using Maven? I'm
particularly looking for advice/preferences for GWT library projects (such
as GWT itself, mgwt, Errai, GXT, etc.), not much
I vote for alternative 1, as it complies with maven convention and I had no
problem at all with this structure.
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To view this discussion on the web visit
On Wednesday, November 14, 2012 11:16:11 AM UTC+1, Nader wrote:
I vote for alternative 1, as it complies with maven convention and I had
no problem at all with this structure.
The question is about whether *in a library* *.gwt.xml and the likes should
be seen as sources or resources, so
I agree with Stefan Ollinger. +1 for second alternative.
--
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/-/uP_fDPSjRkcJ.
To post to this group,
, standard layout for GWT projects using Maven? I'm particularly
looking for advice/preferences for GWT library projects (such as GWT
itself, mgwt, Errai, GXT, etc.), not much for GWT applications (the one you
run the GWT Compiler on).
NOTE: this poll is cross-posted to the GWT and gwt-maven
Hi,
I would prefer alternative 2, since it follows the Maven standard
project layout. Personally I sometimes put the .ui.xml and .gwt.xml
files in the src/main/java folder, since it allows for faster
navigation in Eclipse. I guess that is mainly a tooling issue and should
not have any
It comes without saying (for me at least) that Java sources would go into
src/main/java and public resources (i.e. the things within **/public/**,
e.g. the CSS and image files from the themes) into src/main/resources
I agree with this.
everything in src/main/java
super-sources in
On Tuesday, November 13, 2012 5:18:15 PM UTC+1, Abraham Lin wrote:
Placing the super-sources in src/main/resources may also cause
filter-related surprises.
Ah, good catch!
Also feel free to propose a fourth alternative.
I'd propose keeping non-super sources in src/main/java, public
This is option 3 then (you agreed that It comes without saying (for me at
least) that Java sources would go into src/main/java, and I suppose that
by public resources you mean not only **/public/** but also *.ui.xml and
the like)
Ah sorry, I had misread your definition of everything to
I am have memory leak issues with LayoutPanels. I tested it with 2.5.0-
rc2. See my example below. Little description. I created a vertical
panel, added a button and Layout panel with 200 labels in this. Click
of the button clears the vertical panel(not layout panel), creates
the layout panel
description. I created a vertical
panel, added a button and Layout panel with 200 labels in this. Click
of the button clears the vertical panel(not layout panel), creates
the layout panel with 200 labels and adds it on the vertical panel.
Every click causes the leak of memory. Changing Layout
I want to use the DecoraterPanel inside a Layout Panel (DockLayoutPanel) .
The problem is that there is no DecoratorLayoutPanel implementation and
therefore if I want to use
this panel inside a Layout Panel, all childs will loose the resize events
because the resize-chain is broken through
Hello,
I am trying to build my first user interface using UIBinder and I am having
problems with the layout. It looks like this:
https://picasaweb.google.com/104334857964624808900/21September2012?authuser=0feat=directlink
(The ui.xml is attached below.)
The red area on the right has a fixed
Hello,
I simplified the layout as follows, but the fluid DecoratorPanel still gets
damaged when resizing the window.
I hope someone can help, because I am crazy about using UIBinder now... :-)
Magnus
-
!DOCTYPE ui:UiBinder SYSTEM http://dl.google.com/gwt/DTD/xhtml.ent;
ui:UiBinder
On Friday, September 21, 2012 2:10:42 PM UTC+2, Magnus wrote:
Hello,
I simplified the layout as follows, but the fluid DecoratorPanel still
gets damaged when resizing the window.
DecoratorPanel uses a 9×9 table, and it looks like the first and last
columns are resizing.
Try
Hello,
sorry for posting my learning curve! :-)
I found that DecoratedPanel caused the problems. But I also found that
there is CaptionPanel, which much more suits my needs!
The layout below is nearly perfect for me. Just two things are missing:
- The orange textbox should horizontally grow
Hello Thomas,
thank you! When I used DecoratorPanel, I did not know CaptionPanel. But
CaptionPanel is exactly what I want: group similar widgets. My last layout
with CaptionPanel is currently the one that best works for me. There are
just two issues...
Magnus
Am Freitag, 21. September 2012
Thx for the answer but my problems described in my post are not solved with
your solution.
One more thing to be clear, with Layout Panels I don't mean just the
LayoutPanel.class but
all the classes described here:
https://developers.google.com/web-toolkit/doc/latest/DevGuideUiPanels
article:
https://developers.google.com/web-toolkit/doc/latest/DevGuideUiPanels
In this articel it's also recommended to use Layout Panels for better
standard mode support.
Therefore I have build a very easy example to test the Layout Panels.
In my GwtTestDock.java example I have created a empty
Thanks Thomas for this hint, also HeaderPanel was new for me.
Maybe for better understanding I have added a screenshot with some remarks
of GwtTestDockFilled.class
My background is plain Java, therefore it's easier for me to have
less CSS,HTMLPanel I think. ;-)
I still have no idea whats the
On Wednesday, September 19, 2012 1:11:31 PM UTC+2, Antoine Lever wrote:
I'm using a split layout panel to add a west and north panel. But, I only
want the west panel to resize and NOT the north. Any ideas?
Use a DockLayoutPanel for the north/center non-resizeable separation
PM UTC+2, Antoine Lever wrote:
I'm using a split layout panel to add a west and north panel. But, I
only want the west panel to resize and NOT the north. Any ideas?
Use a DockLayoutPanel for the north/center non-resizeable separation and a
SplitLayoutPanel for the west/center resizeable
is a ProvidesResize, and all layout
panels implement both interfaces (and, for instance, DataGrid is a
RequiresResize but not a ProvidesResize, as it's not a container). If you
break that ProvidesResize/RequiresResize chain, you have to explicit set
the dimensions of the RequiresResize widget
How do you do that? I was under the impression that you could only add one
layoutPanel via RootLayoutPanel.get(). Would you have a code fragment I
can look at - thank you very much.
It's like:
RootLayoutPanel
-- DockLayoutPanel
-- NORTH: header
-- CENTER: SplitLayoutPanel
It works perfectly! Thank you!
On Wednesday, 19 September 2012 16:16:47 UTC+1, Jens wrote:
How do you do that? I was under the impression that you could only add one
layoutPanel via RootLayoutPanel.get(). Would you have a code fragment I
can look at - thank you very much.
It's like:
In this articel it's also recommended to use Layout Panels for better
standard mode support.
Therefore I have build a very easy example to test the Layout Panels.
In my GwtTestDock.java example I have created a empty application skeleton
with Layout Panels.
In GwtTestDockFilled.java I have filled
LayoutPanel can handle all use cases. For example, for your design you can
do something like this (use Ui:Binder). It will keep the height of three
layers constant, while one of the layers will take all the available space.
Now, when a user clicks on one of the menu options, you call
hi guys
I am working on GWT and i have something like
public class QuickSearch extends Canvas
{
private HLayout mainBodyLayout = new HLayout(); //the main layout
containing other layouts.
//button layout
private Layout getButtonLayout()
{
//here i want to check IF mainBodyLayout already
Hie
Can someone help on
http://stackoverflow.com/questions/12397288/automatic-resize-of-the-tab-panel-based-on-contentsplease?
Thankx and Regards
Vik
Founder
http://www.sakshum.org
http://blog.sakshum.org
--
You received this message because you are subscribed to the Google Groups
Google Web
On Tue, Sep 11, 2012 at 3:04 AM, Aneliya Tincheva atinch...@google.com wrote:
Hi,
On Mon, Sep 10, 2012 at 6:16 PM, t.bro...@gmail.com wrote:
Reviewers: atincheva,
Message:
Note: I only applied the suggested fix (after checking the WAI-ARIA
spec), I haven't tried it with a screenreader
Reviewers: atincheva,
Message:
Note: I only applied the suggested fix (after checking the WAI-ARIA
spec), I haven't tried it with a screenreader (actually, it's so
straightforward I haven't tried it at all).
Description:
Add aria-hidden state to layout panel rulers.
Issue 7646
Please review
Adding Brian as reviewer, as discussed with Unnur.
https://gwt-code-reviews.appspot.com/1820807/
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
For example, the solution posted by Jens works perfectly in isolation, but
when I put it into a LayoutPanel it didn't work at all.
Really? For me it works. Copy the example UiBinder xml and put it into a
RootLayoutPanel:
!DOCTYPE ui:UiBinder SYSTEM http://dl.google.com/gwt/DTD/xhtml.ent;
the only empty DIV I see is the label, and it's empty because the label
does not contain text.
Right, and that's why it has zero height as you observed.
Do you agree to the statement posted in this thread that the GWT's layout
panels should be used for the overall page layout
Most modern browsers are pretty consistent with CSS2 and even CSS3. There are
still some differences, but in a few instances where I ran into them, GWT could
not help me. Sometimes you have to specify -moz or -webkit specific rules in
your CSS file. In some situations (e.g. vertical-align in
Sorry, I meant to say that I would love GWT to drop support for IE 7, an maybe
even IE 8, if it allows to greatly simplify the library, reduce the generated
code size, significantly reduce compilation time, and speed up development of
new features.
--
You received this message because you are
by the browser as
an element with zero height. It's not a problem with GWT per se; if
anything, the problem is that your expectations don't match those of the
framework.
It's also worth noting that while GWT offers fairly reliable abstractions
for some things (e.g. basic layout, scripted behaviors
Hi Abraham,
the only empty DIV I see is the label, and it's empty because the label
does not contain text.
Do you agree to the statement posted in this thread that the GWT's layout
panels should be used for the overall page layout (defining the main areas
of a page) and that the small layouts
and it works great. I also
think that it's ok if you have to try and figure out solutions for minor
issues. But I would like to have a general rule how to integrate these
minor solutions into the overall layout, e. g. into a surrounding
LayoutPanel?
For example, the solution posted by Jens works
to be two different worlds coming together when making GUIs in
GWT:
On the one hand. there is the outer layer, the overall page layout, that
you can build using the GWT layout system including the set of powerful
layout panels.
On the other hand there is the inner layer, the widgets, controls
browsers...
See the simplified code for the composite widget (TournamentField), and
also the code for the surrounding layout (OverallLayout) (which is not a
real world example but shows how the TournamentField is inserted).
I believe that the inner widget would work, if it wasn't placed
Am Montag, 3. September 2012 10:09:45 UTC+2 schrieb Ümit Seren:
How about using nested LayoutPanels? Or if you don't want to use
LayoutPanels all the way but need resizing in one of the inner widget you
could wrap it in a
browsers...
See the simplified code for the composite widget (TournamentField), and
also the code for the surrounding layout (OverallLayout) (which is not a
real world example but shows how the TournamentField is inserted).
I believe that the inner widget would work, if it wasn't placed
When you add a widget to a LayoutPanel, it automatically takes the entire space
within that LayoutPanel, unless you use .setWidgetTopHeight or similar methods
to specify which part of the LayoutPanel this widget should occupy. If your
FlowPanel has size 0, this means that your LayoutPanel has
Hi Andrei,
I can verify that the LayoutPanel is not zero sized! It's about 400px x
60px. It's only the label that gets height 0, not the button.
I would be glad I could copy the generated HTML from the Firefox inspection
panel, but this is not possible.
However, I tried the following:
I
Hi,
I managed to copy the generated HTML code with chrome. The outer div is the
AbsolutePanel that acts as the intermediate panel between the LayoutPanel
and the widget:
div style=position: relative; overflow: hidden; border: 1px solid rgb(0,
255, 0); cls=AbsoluteInCell
div style=border:
, September 2, 2012 12:09:28 AM UTC+2, Magnus wrote:
Hi,
since I use GWT I have a fundamental problem with implementing a
predictive layout. I did many resize operations using the onResize method.
This method is called whenever a widget is resized. This is fine.
However, it is only possible to react
You can build any layout in GWT that you can build with plain HTML and CSS,
i.e. any layout you like. I build very complex UIs in GWT, and I very rarely
use resize handlers or getOffsetWidth()/getOffsetHeight() methods, because:
(a) I use a layout panel for page structure, an it resizes
Am Montag, 3. September 2012 14:08:27 UTC+2 schrieb Andrei:
Maybe if you can give a specific example of a problem you face, we can
suggest a solution.
Hello,
I actually need a composite panel TournamentField that consists of two
widgets, a label and a button at the right of the label. I
Am Montag, 3. September 2012 10:09:45 UTC+2 schrieb Ümit Seren:
How about using nested LayoutPanels? Or if you don't want to use
LayoutPanels all the way but need resizing in one of the inner widget you
could wrap it in a
Are you changing the sizes of the layoutPanels dynamically? Because if
you don't it should work out of the box.
If you are changing it dynamically then you might run into this bug
(http://code.google.com/p/google-web-toolkit/issues/detail?id=7188). I
found following code snippet in one of my
In pure HTML I would do it like:
http://jsfiddle.net/EHCGu/
you can drag the vertical splitter to change the size of the result and the
label div fills all the space while the button is float:right. No need to
use any onResize() JavaScript as the browser takes care of the size. Maybe
you can
you have to call force layout to calc sizes in the new space.
k
Sent from my iPhone
On Sep 1, 2012, at 6:09 PM, Magnus alpineblas...@googlemail.com wrote:
Hi,
since I use GWT I have a fundamental problem with implementing a predictive
layout. I did many resize operations using
smaller (layout panels
produce a lot of HTML), and your pages will reflow much faster.
You don't need to worry about the height: a FlowPanel will expand automatically
to accommodate its contents. If you want, you can fix its height, or you can
use min-height and/or max-height CSS rules. You can
care of the
size. Maybe you can omit the div that clears the float:right.
You should use as much CSS as you can, so you don't have to worry about
resizing your widgets. Let the browser do it.
Hi Jens,
this looks good. I often read about letting the browser do most of the
layout
is wider than the button. That's it. Your generated code will be 10 times
smaller (layout panels produce a lot of HTML), and your pages will reflow
much faster.
You don't need to worry about the height: a FlowPanel will expand
automatically to accommodate its contents. If you want, you can fix its
Hi,
since I use GWT I have a fundamental problem with implementing a predictive
layout. I did many resize operations using the onResize method. This method
is called whenever a widget is resized. This is fine.
However, it is only possible to react on a resize event if one knows the
new sizes
After add the px unit, FF can show the image correctly.
image1.setSize(String.valueOf(clientWidth * 0.1) + px,
String.valueOf(clientHeight * 0.1) + px);
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To view this discussion on the
Rather than using any existing layout panel I would suggest you to use
uiBinder by using HTMLPanel widget to design your root lay out and create
the place holder using uifield which you can manipulate through your
respective class of uibinder. That way you get a flexibility of having html
How about the LayoutPanel?
The advantage of LayoutPanel is that it can animate smoothly between states.
On Tuesday, June 12, 2012 7:10:19 AM UTC+2, Santosh wrote:
We wanted to design a layout in GWT which has quite a lot of small
small sections on screen. Basically it has a left menu, header
states.
On Tuesday, June 12, 2012 7:10:19 AM UTC+2, Santosh wrote:
We wanted to design a layout in GWT which has quite a lot of small
small sections on screen. Basically it has a left menu, header,
footer, main content area with lot of sub sections which can be closed
by user
is that it can animate smoothly between
states.
On Tuesday, June 12, 2012 7:10:19 AM UTC+2, Santosh wrote:
We wanted to design a layout in GWT which has quite a lot of small
small sections on screen. Basically it has a left menu, header,
footer, main content area with lot of sub
are
built
On Jun 12, 3:35 pm, Thomas Broyer t.bro...@gmail.com wrote:
How about the LayoutPanel?
The advantage of LayoutPanel is that it can animate smoothly between
states.
On Tuesday, June 12, 2012 7:10:19 AM UTC+2, Santosh wrote:
We wanted to design a layout in GWT which has
We wanted to design a layout in GWT which has quite a lot of small
small sections on screen. Basically it has a left menu, header,
footer, main content area with lot of sub sections which can be closed
by user in case if he does not want to see them. Then remaining
content section should get
and secondBasicPanel underlying the same
layout system RootPanel are supposed to behave predictably,
respectively firstLayoutPanel and secondLayoutPanel underlying
RootLayoutPanel.
Would thirdLayoutPanel underlying the different layout system
RootPanel or thirdBasicPanel underlying RootLayoutPanel stirs
Need help in SmartGUI layout issue mentioned below:
Why don't you try http://forums.smartclient.com/ ???
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com
Hi everyone,
Need help in SmartGUI layout issue mentioned below:
In my project , i have the requirement of creating a form having tabs
on it and this form has
a ComboBox. TextBox and a Button on it,
Unable to make it using SmartGWT drag and drop GUI facility in
Eclipse.
I have made
Hello,
I think create a web interface for creating invitations (
http://www.bebe-cards.com style), from models created with the Adobe
InDesign software (based on the exchange format IDML -InDesign Markup
Language-).
The principle is to allow the user to choose a model already made on
On Friday, April 13, 2012 8:05:50 AM UTC+2, tong123123 wrote:
In fact, if using pure html + css, if table layout is fixed, the column
content will penetrate the next cell, but not truncate, but in gwt, I found
that the content will really be truncated, so strange.
This is because TDs
in gwt developer guide, it said
In order to gain fine-grain control over the width of columns, you must set
the table layout to fixed by passing true into CellTable.setWidth(String,
boolean)http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/user/cellview/client
101 - 200 of 697 matches
Mail list logo
