Re: GWT 2.1 CELL TABLE
Check the content of your .css file. It could cause Deferred Binding problem. I ran into the same issue. After I re-copied CellTable.css into my .css and reran everything was fine. -- 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+unsubscr...@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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: GWT 2.1 cell table paging bug?
If you want the table height to remain consistent, couldn't you wrap the table in a containing element (e.g. div) of a fixed height? That way, if you display the pager directly underneath the table for example, it will always stay in the same spot and just the table itself will shrink. I prefer manstis' (Mike's) fix to the default behavior of AbstractPager. I couldn't agree more with Steve's remarks. To reiterate: when you page over, I would expect to see a new result at the start of the table. Yes, that means the table must shrink, but you can use CSS to deal with that. I also want to reiterate manstis' concern of a second RangeChangeEvent being fired. I would think this behavior to be extremely undesirable as I would imagine most of us are performing a server side call to a database to retrieve more data in onRangeChange(). So a needless call to the server will be made. This is bad! I think that the behavior of AbstractPager should be modified and manstis' implementation of setPageStart() should be the default. Perhaps a boolean configurable (restrictVisibleRowsToPageSize) should be added which allows for the user to utilize the current behavior of setPageStart(). Just in case anyone else comes across this post, it should also be noted (I found it very confusing, at least) that while setting AbstractPager.isRangeLimited via AbstractPager.setRangeLimited() will make the next page and last page buttons behave the same (showing only new data, even if less than pageSize) it is not a solution to this problem because then the next and last page buttons will not be disabled. On Friday, January 6, 2012 7:27:48 AM UTC-5, Emilian Bold wrote: > > I agree. The current GWT pagination seems to be more of a workaround. > They try to avoid having less items on the last page because it might > change the layout and the pager position. > > What should actually happen is that the table should maintain the full > height as if it has all the rows, but display only the few remaining > rows on the last page. > > Basically, the table should have the same height regardless of the > number of rows and the pager component should remain in place when > switching pages. > > I'm surprised there isn't an actual bugreport for this. > > --emi > > On Dec 21 2011, 3:16 am, Steve wrote: > > This behavior deviates from widespread usage of pagination across the > web > > so I don't see how it's desirable to do something unexpected by users > > unless it's clearly superior. > > > > When I navigate from one page to another it's because I want to see the > > next set of results/data and I expect the stuff at the top to be > different > > than what was on the previous page I was on. If it overlaps, then I have > to > > scan down and figure out where to start looking. -- 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+unsubscr...@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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: GWT 2.1 cell table paging bug?
If you want the table height to remain consistent, couldn't you wrap the table in a containing element (e.g. div) of a fixed height? That way, if you display the pager directly underneath the table for example, it will always stay in the same spot and just the table itself will shrink. I prefer manstis' (Mike's) fix to the default behavior of AbstractPager. I couldn't agree more with Steve's remarks. To reiterate: when you page over, I would expect to see a new result at the start of the table. Yes, that means the table must shrink, but you can use CSS to deal with that. I also want to reiterate manstis' concern of a second RangeChangeEvent being fired. I would think this behavior to be extremely undesirable as I would imagine most of us are performing a server side call to a database to retrieve more data in onRangeChange(). So a needless call to the server will be made. This is bad! I think that the behavior of AbstractPager should be modified and manstis' implementation of setPageStart() should be the default. Perhaps a boolean configurable (restrictVisibleRowsToPageSize) should be added which allows for the user to utilize the current behavior of setPageStart(). On Friday, January 6, 2012 7:27:48 AM UTC-5, Emilian Bold wrote: > > I agree. The current GWT pagination seems to be more of a workaround. > They try to avoid having less items on the last page because it might > change the layout and the pager position. > > What should actually happen is that the table should maintain the full > height as if it has all the rows, but display only the few remaining > rows on the last page. > > Basically, the table should have the same height regardless of the > number of rows and the pager component should remain in place when > switching pages. > > I'm surprised there isn't an actual bugreport for this. > > --emi > > On Dec 21 2011, 3:16 am, Steve wrote: > > This behavior deviates from widespread usage of pagination across the > web > > so I don't see how it's desirable to do something unexpected by users > > unless it's clearly superior. > > > > When I navigate from one page to another it's because I want to see the > > next set of results/data and I expect the stuff at the top to be > different > > than what was on the previous page I was on. If it overlaps, then I have > to > > scan down and figure out where to start looking. -- 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+unsubscr...@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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: GWT 2.1 cell table paging bug?
If you want the table height to remain consistent, couldn't you wrap the table in a containing element (e.g. div) of a fixed height? That way, if you display the pager directly underneath the table for example, it will always stay in the same spot and just the table itself will shrink. I prefer manstis' (Mike's) fix to the default behavior of AbstractPager. I couldn't agree more with Steve's remarks. To reiterate: when you page over, I would expect to see a new result at the start of the table. Yes, that means the table must shrink, but you can use CSS to deal with that. I think that the behavior of AbstractPager should be modified and manstis' implementation of setPageStart() should be the default. Perhaps a boolean configurable (restrictVisibleRowsToPageSize) should be added which allows for the user to utilize the current behavior of setPageStart(). On Friday, January 6, 2012 7:27:48 AM UTC-5, Emilian Bold wrote: > > I agree. The current GWT pagination seems to be more of a workaround. > They try to avoid having less items on the last page because it might > change the layout and the pager position. > > What should actually happen is that the table should maintain the full > height as if it has all the rows, but display only the few remaining > rows on the last page. > > Basically, the table should have the same height regardless of the > number of rows and the pager component should remain in place when > switching pages. > > I'm surprised there isn't an actual bugreport for this. > > --emi > > On Dec 21 2011, 3:16 am, Steve wrote: > > This behavior deviates from widespread usage of pagination across the > web > > so I don't see how it's desirable to do something unexpected by users > > unless it's clearly superior. > > > > When I navigate from one page to another it's because I want to see the > > next set of results/data and I expect the stuff at the top to be > different > > than what was on the previous page I was on. If it overlaps, then I have > to > > scan down and figure out where to start looking. -- 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+unsubscr...@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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: GWT 2.1 cell table paging bug?
On Friday, January 6, 2012 7:27:48 AM UTC-5, Emilian Bold wrote: > > I agree. The current GWT pagination seems to be more of a workaround. > They try to avoid having less items on the last page because it might > change the layout and the pager position. > > What should actually happen is that the table should maintain the full > height as if it has all the rows, but display only the few remaining > rows on the last page. > > Basically, the table should have the same height regardless of the > number of rows and the pager component should remain in place when > switching pages. > > I'm surprised there isn't an actual bugreport for this. > > --emi > > On Dec 21 2011, 3:16 am, Steve wrote: > > This behavior deviates from widespread usage of pagination across the > web > > so I don't see how it's desirable to do something unexpected by users > > unless it's clearly superior. > > > > When I navigate from one page to another it's because I want to see the > > next set of results/data and I expect the stuff at the top to be > different > > than what was on the previous page I was on. If it overlaps, then I have > to > > scan down and figure out where to start looking. -- 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+unsubscr...@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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: GWT 2.1 cell table paging bug?
I'd star the issue if some filed one. On Jan 6, 7:27 am, Emilian Bold wrote: > I agree. The current GWT pagination seems to be more of a workaround. > They try to avoid having less items on the last page because it might > change the layout and the pager position. > > What should actually happen is that the table should maintain the full > height as if it has all the rows, but display only the few remaining > rows on the last page. > > Basically, the table should have the same height regardless of the > number of rows and the pager component should remain in place when > switching pages. > > I'm surprised there isn't an actual bugreport for this. > > --emi > > On Dec 21 2011, 3:16 am, Steve wrote: > > > > > This behavior deviates from widespread usage of pagination across the web > > so I don't see how it's desirable to do something unexpected by users > > unless it's clearly superior. > > > When I navigate from one page to another it's because I want to see the > > next set of results/data and I expect the stuff at the top to be different > > than what was on the previous page I was on. If it overlaps, then I have to > > scan down and figure out where to start looking. -- 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. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT 2.1 cell table paging bug?
I agree. The current GWT pagination seems to be more of a workaround. They try to avoid having less items on the last page because it might change the layout and the pager position. What should actually happen is that the table should maintain the full height as if it has all the rows, but display only the few remaining rows on the last page. Basically, the table should have the same height regardless of the number of rows and the pager component should remain in place when switching pages. I'm surprised there isn't an actual bugreport for this. --emi On Dec 21 2011, 3:16 am, Steve wrote: > This behavior deviates from widespread usage of pagination across the web > so I don't see how it's desirable to do something unexpected by users > unless it's clearly superior. > > When I navigate from one page to another it's because I want to see the > next set of results/data and I expect the stuff at the top to be different > than what was on the previous page I was on. If it overlaps, then I have to > scan down and figure out where to start looking. -- 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. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT 2.1 cell table paging bug?
This behavior deviates from widespread usage of pagination across the web so I don't see how it's desirable to do something unexpected by users unless it's clearly superior. When I navigate from one page to another it's because I want to see the next set of results/data and I expect the stuff at the top to be different than what was on the previous page I was on. If it overlaps, then I have to scan down and figure out where to start looking. -- 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/-/NM5Yzzq160MJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT 2.1 cell table paging bug?
On Tue, Feb 1, 2011 at 3:16 PM, zixzigma wrote: > I do not think this is a bug, > and in fact I found the current implementation very desirable. > > your table always shows X number of rows per page, even if its the last > page. > with this implementation your table will always have the same height, and > same number of rows. > and you dont have to deal with cases where there is only 1 or two items in > the last page, > which might make your UI look inconsistent. > Unfortunately the paging mechanism in GWT v2.1 is inconsistent when using the mouse and the keyboard to scroll a paged table. When using the mouse it works the way you describe but when using the keyboard and scrolling down to the last page you will *sometimes* get an 'odd' number of rows. > > I believe making the table to act this way is more difficult than > traditional way of paging, > because you have to do some range manipulation, check if its last page, > and if so, display enough rows for table pageSize to be met. and GWT > CellTable already does this. > Yes, I agree. Jeff > > > > > -- > 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. > To unsubscribe from this group, send email to > google-web-toolkit+unsubscr...@googlegroups.com > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > -- *Jeff Schwartz* -- 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. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT 2.1 cell table paging bug?
I do not think this is a bug, and in fact I found the current implementation very desirable. your table always shows X number of rows per page, even if its the last page. with this implementation your table will always have the same height, and same number of rows. and you dont have to deal with cases where there is only 1 or two items in the last page, which might make your UI look inconsistent. I believe making the table to act this way is more difficult than traditional way of paging, because you have to do some range manipulation, check if its last page, and if so, display enough rows for table pageSize to be met. and GWT CellTable already does this. -- 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. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT 2.1 cell table paging bug?
I encountered the same problem :-(
What's more ominous is that the change in visibleRange also causes a
second onRangeChange event (which is undesirable if nothing else): (1)
For the initial page forward to the last page (with potential unequal
number of rows to pageSize) and (2) For the re-rendering of the last
page with visibleRange set to show pageSize rows but indexed from
display.getRowCount() - pageSize (as noted by OP).
I found a fix however, by overriding setPageStart in SimplePager, as
follows:-
public void setPageStart(int index) {
if ( getDisplay() != null ) {
Range range = getDisplay().getVisibleRange();
int pageSize = range.getLength();
if ( isRangeLimited()
&& getDisplay().isRowCountExact() ) {
pageSize = Math.min( pageSize,
getDisplay().getRowCount()
- index );
}
index = Math.max( 0,
index );
if ( index != range.getStart() ) {
getDisplay().setVisibleRange( index,
pageSize );
}
}
}
This shows the last page with a number of rows less than pageSize if
getRowCount() is less than pageSize * numberOfPages.
I hope it is of use.
Cheers,
Mike
On Dec 5 2010, 6:25 pm, Arnaud wrote:
> I have exactly the same problem than sebrojas, if someone has a
> solution. Would appreciate any help.
>
> Thanks
> Arnaud
>
> On Nov 2, 7:29 pm, sebrojas wrote:
>
> > Yes, is a bug!
>
> > Also, I´m having other problems with celltable paging.
> > When I set the page size to 12 or less, and I click the button next
> > page or last page, and rows away is a picture of charging that is not
> > removed.
> > When I set the page size in 13 or more, and I click the button next
> > page or last page, and then on the previous page shows several rows
> > without values (the first).
> > Please answer, need help
> > I don´t understand why the pager have a setPageSize method and the
> > dell table too??? :s, but it seems to the table method is the one that
> > have effect
>
> > ...
> > ProvidesKey pk = new ProvidesKey() {
> > public Object getKey(Depuracion item) {
> > return item.getId();
> > }
> > };
>
> > final CellTable table = new
> > CellTable(pk);
> > table.addStyleName("tabla");
> > table.setPageSize(8);
>
> > // Create a Pager to control the table.
> > SimplePager.Resources pagerResources = GWT
> > .create(SimplePager.Resources.class);
> > pager = new SimplePager(TextLocation.CENTER,
> > pagerResources, false,
> > 0,
> > true);
> > pager.setDisplay(table);
> > ...
>
>
--
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.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT 2.1 CELL TABLE
My code (files are all in the same directory):
1. Interface
package amdb.client.ui.table;
import com.google.gwt.core.client.GWT;
import com.google.gwt.user.cellview.client.CellTable;
import com.google.gwt.user.cellview.client.CellTable.Resources;
public interface CellTableResource extends Resources {
public CellTable.Resources INSTANCE =
GWT.create(CellTableResource.class);
/**
* The styles used in this widget.
*/
@Source("CellTable.css")
CellTable.Style cellTableStyle();
}
2. CSS file (copy of the original CellTable style sheet, with "cellTable"
appended to every style).
.cellTable {
border: 1px solid #88b0f2;
}
.cellTableFirstColumn {
}
@sprite .cellTableFooter {
gwt-image: 'cellTableFooterBackground';
background-color: #b4d0f8;
border-top: 1px solid #88b0f2;
border-left: 1px solid #88b0f2;
border-right: 1px solid #eef;
padding: 0px 10px;
text-align: left;
color: #4b4a4a;
}
@sprite .cellTableHeader {
gwt-image: 'cellTableHeaderBackground';
background-color: #b4d0f8;
border-bottom: 1px solid #88b0f2;
border-left: 1px solid #88b0f2;
border-right: 1px solid #eef;
padding: 0px 10px;
text-align: left;
color: skyblue;
}
.cellTableCell {
padding: 4px 10px;
}
.cellTableFirstColumnFooter {
border-left: 0px;
}
.cellTableFirstColumnHeader {
border-left: 0px;
}
.cellTableEvenRow {
background-color: red;
}
.cellTableOddRow {
background-color: red;
}
.cellTableHoveredRow {
background-color: green;
}
@sprite .cellTableSelectedRow {
gwt-image: 'cellTableSelectedBackground';
background-color: #628cd5;
color: white;
height: auto;
overflow: auto;
}
3. Call
CellTable itemTable = new CellTable(Integer.MAX_VALUE,
CellTableResource.INSTANCE);
4. Error
[DEBUG] [amdb] - Rebinding amdb.client.ui.table.CellTableResource
[ERROR] [amdb] - Deferred binding failed for
'amdb.client.ui.table.CellTableResource'; expect subsequent failures
[DEBUG] [amdb] - Rebinding
com.google.gwt.dom.client.StyleInjector.StyleInjectorImpl
[WARN] [amdb] - For the following type(s), generated source was never
committed (did you forget to call commit()?)
[WARN] [amdb] -
amdb.client.ui.table.CellTableResource_default_InlineClientBundleGenerator
[ERROR] [amdb] - Unable to load module entry point class amdb.client.AmdbNew
(see associated exception for details)
[ERROR] [amdb] - Failed to load module 'amdb' from user agent 'Mozilla/5.0
(X11; U; Linux i686; en-US) AppleWebKit/534.10 (KHTML, like Gecko)
Chrome/8.0.552.224 Safari/534.10' at localhost:40471
--
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-tool...@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT 2.1 CELL TABLE
Thanks hagar. I followed your instructions with two changes: 1. Added "import import com.google.gwt.user.cellview.client.CellTable.Resources;" the interface in Step 1. 2. I was getting an error regarding unobfuscated class names in my CSS file, so I appended "cellTable" to all the CSS classes (as per the recommendation of the compiler). Now I get the following error: [ERROR] [amdb] - Deferred binding failed for 'amdb.client.ui.table.CellTableResource'; expect subsequent failures [DEBUG] [amdb] - Rebinding com.google.gwt.dom.client.StyleInjector.StyleInjectorImpl [WARN] [amdb] - For the following type(s), generated source was never committed (did you forget to call commit()?) [WARN] [amdb] - amdb.client.ui.table.CellTableResource_default_InlineClientBundleGenerator If anyone has an idea, please let me know. ~Owen -- 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-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT 2.1 CELL TABLE
bradr writes:
>
> To do this, you have to override the CellTable's default style.
> Because CellTable uses a CssResource, which ultimately gets obfuscated
> when you compile, you have to create your own implementation and pass
> it to the CellTable in the constructor.
>
> Here is how I did it:
>
> Step 1) Create your own implementation of the Resource
>
> import com.google.gwt.core.client.GWT;
> import com.google.gwt.user.cellview.client.CellTable;
> import com.google.gwt.user.cellview.client.CellTable.Resources;
> public interface MyCellTableResources extends Resources {
>
> public MyCellTableResources INSTANCE =
> GWT.create(MyCellTableResources.class);
>
> /**
>* The styles used in this widget.
>*/
> @Source("CellTable.css")
> CellTable.Style cellTableStyle();
> }
>
> Step 2) Copy the CellTable.css file into your project (from gwt trunk)
> into the same package as your Resource implementation. Customize the
> css until it meets your style needs.
>
> Step 3) When you create an instance of the CellTable, give it your
> your custom CssResource:
>
>myTable = new
> CellTable(Integer.MAX_VALUE,CellTableResources.INSTANCE);
>
> Hope that helps!
>
> On Oct 29, 11:55 am, bond wrote:
> > Hi,
> > is possibile to remove the box around the single cell that appears
> > when I click on a cell?
> >
> > Thanks very much
> >
> > Best regards
>
Working example, based on bradr note:
1. Create new interface:
--
import com.google.gwt.core.client.GWT;
import com.google.gwt.user.cellview.client.CellTable;
public interface CellTableResource extends Resources {
public CellTable.Resources INSTANCE =
GWT.create(CellTableResource.class);
/**
* The styles used in this widget.
*/
@Source("style/CellTable.css")
CellTable.Style cellTableStyle();
}
2. Copy CellTable.css
from: http://code.google.com/p/google-web-
toolkit/source/browse/branches/2.1/bikeshed/src/com/google/gwt/bikeshed/list/cli
ent/CellTable.css?r=8062
into the same directory (or subdirectory of CellTableResource).
3. Create your CellTable with the resource file:
CellTable table = new CellTable(20,
CellTableResource.INSTANCE);
--
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-tool...@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT 2.1 cell table paging bug?
I have exactly the same problem than sebrojas, if someone has a
solution. Would appreciate any help.
Thanks
Arnaud
On Nov 2, 7:29 pm, sebrojas wrote:
> Yes, is a bug!
>
> Also, I´m having other problems with celltable paging.
> When I set the page size to 12 or less, and I click the button next
> page or last page, and rows away is a picture of charging that is not
> removed.
> When I set the page size in 13 or more, and I click the button next
> page or last page, and then on the previous page shows several rows
> without values (the first).
> Please answer, need help
> I don´t understand why the pager have a setPageSize method and the
> dell table too??? :s, but it seems to the table method is the one that
> have effect
>
> ...
> ProvidesKey pk = new ProvidesKey() {
> public Object getKey(Depuracion item) {
> return item.getId();
> }
> };
>
> final CellTable table = new
> CellTable(pk);
> table.addStyleName("tabla");
> table.setPageSize(8);
>
> // Create a Pager to control the table.
> SimplePager.Resources pagerResources = GWT
> .create(SimplePager.Resources.class);
> pager = new SimplePager(TextLocation.CENTER, pagerResources,
> false,
> 0,
> true);
> pager.setDisplay(table);
> ...
--
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-tool...@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT 2.1 CELL TABLE
Hi Brad,
In Step 3, "CellTable" should be "CellTable",
right?
I'm having some problems. When I follow your code (and my adjustment
to Step 3), I end up with two "Matched CSS Rules" when I inspect my
table in the browser. My custom CSS is there, but so is the original,
and the original is taking precedence over the custom.
I seem to be close... any ideas?
~Owen
On 29 oct, 22:51, bradr wrote:
> To do this, you have to override the CellTable's default style.
> Because CellTable uses a CssResource, which ultimately gets obfuscated
> when you compile, you have to create your own implementation and pass
> it to the CellTable in the constructor.
>
> Here is how I did it:
>
> Step 1) Create your own implementation of the Resource
>
> import com.google.gwt.core.client.GWT;
> import com.google.gwt.user.cellview.client.CellTable;
> import com.google.gwt.user.cellview.client.CellTable.Resources;
> public interface MyCellTableResources extends Resources {
>
> public MyCellTableResources INSTANCE =
> GWT.create(MyCellTableResources.class);
>
> /**
> * The styles used in this widget.
> */
> @Source("CellTable.css")
> CellTable.Style cellTableStyle();
>
> }
>
> Step 2) Copy the CellTable.css file into your project (from gwt trunk)
> into the same package as your Resource implementation. Customize the
> css until it meets your style needs.
>
> Step 3) When you create an instance of the CellTable, give it your
> your custom CssResource:
>
> myTable = new
> CellTable(Integer.MAX_VALUE,CellTableResources.INSTANCE);
>
> Hope that helps!
>
> On Oct 29, 11:55 am, bond wrote:
>
>
>
>
>
>
>
> > Hi,
> > is possibile to remove the box around the single cell that appears
> > when I click on a cell?
>
> > Thanks very much
>
> > Best regards
--
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-tool...@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT 2.1 cell table paging bug?
Yes, is a bug!
Also, I´m having other problems with celltable paging.
When I set the page size to 12 or less, and I click the button next
page or last page, and rows away is a picture of charging that is not
removed.
When I set the page size in 13 or more, and I click the button next
page or last page, and then on the previous page shows several rows
without values (the first).
Please answer, need help
I don´t understand why the pager have a setPageSize method and the
dell table too??? :s, but it seems to the table method is the one that
have effect
...
ProvidesKey pk = new ProvidesKey() {
public Object getKey(Depuracion item) {
return item.getId();
}
};
final CellTable table = new
CellTable(pk);
table.addStyleName("tabla");
table.setPageSize(8);
// Create a Pager to control the table.
SimplePager.Resources pagerResources = GWT
.create(SimplePager.Resources.class);
pager = new SimplePager(TextLocation.CENTER, pagerResources,
false,
0,
true);
pager.setDisplay(table);
...
--
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-tool...@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT 2.1 CELL TABLE
Thanks very much bradr!!
I'll try you suggestions!!
Daniele
On 29 Ott, 22:51, bradr wrote:
> To do this, you have to override the CellTable's default style.
> Because CellTable uses a CssResource, which ultimately gets obfuscated
> when you compile, you have to create your own implementation and pass
> it to the CellTable in the constructor.
>
> Here is how I did it:
>
> Step 1) Create your own implementation of the Resource
>
> import com.google.gwt.core.client.GWT;
> import com.google.gwt.user.cellview.client.CellTable;
> import com.google.gwt.user.cellview.client.CellTable.Resources;
> public interface MyCellTableResources extends Resources {
>
> public MyCellTableResources INSTANCE =
> GWT.create(MyCellTableResources.class);
>
> /**
> * The styles used in this widget.
> */
> @Source("CellTable.css")
> CellTable.Style cellTableStyle();
>
> }
>
> Step 2) Copy the CellTable.css file into your project (from gwt trunk)
> into the same package as your Resource implementation. Customize the
> css until it meets your style needs.
>
> Step 3) When you create an instance of the CellTable, give it your
> your custom CssResource:
>
> myTable = new
> CellTable(Integer.MAX_VALUE,CellTableResources.INSTANCE);
>
> Hope that helps!
>
> On Oct 29, 11:55 am, bond wrote:
>
> > Hi,
> > is possibile to remove the box around the single cell that appears
> > when I click on a cell?
>
> > Thanks very much
>
> > Best regards
--
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-tool...@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT 2.1 CELL TABLE
To do this, you have to override the CellTable's default style.
Because CellTable uses a CssResource, which ultimately gets obfuscated
when you compile, you have to create your own implementation and pass
it to the CellTable in the constructor.
Here is how I did it:
Step 1) Create your own implementation of the Resource
import com.google.gwt.core.client.GWT;
import com.google.gwt.user.cellview.client.CellTable;
import com.google.gwt.user.cellview.client.CellTable.Resources;
public interface MyCellTableResources extends Resources {
public MyCellTableResources INSTANCE =
GWT.create(MyCellTableResources.class);
/**
* The styles used in this widget.
*/
@Source("CellTable.css")
CellTable.Style cellTableStyle();
}
Step 2) Copy the CellTable.css file into your project (from gwt trunk)
into the same package as your Resource implementation. Customize the
css until it meets your style needs.
Step 3) When you create an instance of the CellTable, give it your
your custom CssResource:
myTable = new
CellTable(Integer.MAX_VALUE,CellTableResources.INSTANCE);
Hope that helps!
On Oct 29, 11:55 am, bond wrote:
> Hi,
> is possibile to remove the box around the single cell that appears
> when I click on a cell?
>
> Thanks very much
>
> Best regards
--
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-tool...@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
GWT 2.1 CELL TABLE
Hi, is possibile to remove the box around the single cell that appears when I click on a cell? Thanks very much Best regards -- 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-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
GWT 2.1 cell table paging bug?
AbstractPager uses HasRows#getVisibleRange()#getLength() to obtain the page size. This doesn't seem to be a good idea as you can see in the Showcase exmpale (Cell Widgets/Cell Table [1]). This table gets populated with 250 entries and shows 15 per page. Now click on the "next page" button. You go (correctly) all the way to showing "226 - 240". But the next click switches to "236 - 250". I expect the table to go to "241 - 250" (and thus showing only 10 rows). But it gets worse: If you now start to navigate back, the display range is moved by this offset. So you reach "11 - 25" and then "1 - 15"?! I don't think this behaviour is intentional. At least the "go to last page" and "go to first page" buttons work properly (showing "1 - 15" and "241 - 250"). Bug? Sebastian [1] http://gwt.google.com/samples/Showcase/Showcase.html#!CwCellTable -- 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-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
