Technical question please about jmesa toolbar

[Hanen Ben Rhouma]

Hello there,

Please I have a question: Is it possible to add another toolbar at the
end of the jmesa table in order to make it easier for users to jump
from one page to another without being obliged to scroll up each time?

Thanks in advance,
Hanen

[AMRAOUI Marouane]

Hello ,

yes its possible.

Step 1 : create new implementation toolbar view class 

1. package com.myapp.view
2. public class BottomToolbarView extends HtmlView {
4. @Override
5. public Object render() {
6. HtmlSnippets snippets = getHtmlSnippets();
8. HtmlBuilder html = new HtmlBuilder();
10. html.append(snippets.themeStart());
12. html.append(snippets.tableStart());
14. html.append(snippets.theadStart());
16. html.append(snippets.toolbar());
18. html.append(snippets.filter());
20. html.append(snippets.header());
22. html.append(snippets.theadEnd());
24. html.append(snippets.tbodyStart());
26. html.append(snippets.body());
28. html.append(snippets.tbodyEnd());
30. html.append(snippets.footer());
32. html.append(snippets.statusBar());
34. html.append(snippets.toolbar());
36. html.append(snippets.tableEnd());
38. html.append(snippets.themeEnd());
40. html.append(snippets.initJavascriptLimit());
42. return html.toString();
43. }
45. }

Step 2 : use this new view in your jmessa table html

1. <jmesa:tableFacade
2. id="tag"
3. .....
4. 
   
5. view="com.myapp.view.BottomToolbarView"
6. >
7. <jmesa:htmlTable
8. caption=""
9. width="1100"
10. >
11. <jmesa:htmlRow uniqueProperty="refUsrAuthTableId">
12. 
    

hope this help you.

--
You received this message because you are subscribed to the Google Groups "JMesa" group.
To post to this group, send email to jm...@googlegroups.com.
To unsubscribe from this group, send email to jmesa+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/jmesa?hl=en.

[Hanen Ben Rhouma]

Hey Folks,

Again having issues with this customization thing: Actually the issue I'm facing now is that the second time we invoke html.append(snippets.toolbar()

);  within the class BottomToolbarView we'll get an append of the previous toolbar with a new one which makes the count to 2 toolbars at the bottom, such issue needs an override of the toolbar() method but adding wrappers everywhere isn't a performant solution and most importantly it's not working.


Any suggestions please..

--

Regards,
Hanen

[Jeff Johnston]

Are you putting the toolbars next to each other in the view? The toolbar will show up where you place it (take a closer look at AMRAOUI example). It might help to look at the snippets class to take the mystery out of what is happening. If it is still happening could you post your view?

-Jeff

[Hanen Ben Rhouma]

No, I'm trying to show two toolbars separately, one at the top the other in the bottom.

What I'm getting is one toolbar on the top and two close to each other in the bottom, and yes I'm following the same example given by AMRAOUI.

What I noticed in the implementation of the method toolbar() is:


 public String toolbar() {

        HtmlBuilder html = new HtmlBuilder();

        HtmlRow row = table.getRow();
        List<Column> columns = row.getColumns();

        String toolbarClass = getCoreContext().getPreference(HtmlConstants.TOOLBAR_CLASS);
        html.tr(1).styleClass(toolbarClass).close();
        html.td(2).colspan(String.valueOf(columns.size())).close();

        html.append(toolbar.render());

        html.tdEnd();
        html.trEnd(1);

        return html.toString();
    }

The toolbar.render() keeps track of the previous toolbars and increment their number each time we invoke it. We need to reinitialize it somehow without loosing the rest of the snippet components.

[Jeff Johnston]

I just tried it out in one of my projects and it worked fine...

What version of JMesa are you using? Do you have other custom code?

The toolbar.render() keeps track of the previous toolbars and increment their number each time we invoke it.

This is not quite right. When you ask the toolbar to render itself it does it each time with no knowledge of previous render attempts.

Can you post your view?

-Jeff

[Hanen Ben Rhouma]

I'm using 2.2.8

[Hanen Ben Rhouma]

I don't know if I can attach a screenshot in here but I'm trying. Please let me know if you can download it.

--

Regards,
Hanen

[Jeff Johnston]

I would not be able to support the 2.2.8 release. You should be able to move to the 3.0.4 release fairly easy though as things that changed were deprecated. If you are using the tags its really easy as you mostly just need to change from using <jmesa:tableFacade /> to <jmesa:tableModel />. If you are using the API you can still use the TableFacade, but the TableModel makes things much easier.

Still, I would only move if you can carve out enough time to do the upgrade. I am sure the upgrade is fairly straightforward, but like anything there may be little things that you need to work through.

-Jeff

[Hanen Ben Rhouma]

Hello again,

Are there any known issues for migrating from 2.2.8 (prototype-based) to 3.0.4 (jquery-based)? I heard they're exclusive so we can't use them in the same project context.

Please clarify.

[Jeff Johnston]

You would have to move everything at once. But, that said, unless you have custom JavaScript you should be able to move to the 3.0.4 release pretty easy. I tried very hard to keep thing backwards compatible. Your best bet is to just take one table and see how it goes.

-Jeff

[Hanen Ben Rhouma]

Too many missing dependencies and conflicts, we're using Maven 2 for build and deployment, seems old for such API. Isn't there any intermediate version which encapsulates the main recent features without having to migrate radically from prototype to jquery and from maven 2 to maven 3, that's a huge time/effort investment that's gonna enlarge our refactoring scope (till now 7 files needed to be modified) as well as several non regression test scenarios.