gwtbootstrap / gwt-bootstrap

A GWT Library that provides the widgets of Bootstrap, from Twitter.

This is no longer maintained. Use it at your own risk.

---

GWT-Bootstrap

Based on Bootstrap., GWT-Bootstrap Bootstrap provides simple and flexible components representing Bootstrap components, styles, and plugins. In other words, it's a front-end API for faster, more beautiful GWT web development.

Links

• Showcase
• Javadoc
• Google Group
• Maven project site
• Maven Repository

Donate

Help us to improve and continue working on GWT-Bootstrap. Do pull-requests and/or donate.

Thanks to

gwt-bootstrap's Issues

Make Maven generate a .jar file

Make Maven generate a .jar file for the devs who will use this.

Compatibility with Native GWT components

What happens if we combine GWT components with Bootstrap components without manually remove the GWT styles?

I think it will break some CSS styles.

We have to test it, and then, fix, if it occurs.

Add support for tables

http://twitter.github.com/bootstrap/base-css.html#tables

Add support for Subnav Bar?

The Bootstrap documentation features a subnav bar that gets fixed on top once you scroll past it.

It's not included in bootstrap but can be found at http://twitter.github.com/bootstrap/assets/css/docs.css.

Implement ScrollSpy.

http://twitter.github.com/bootstrap/javascript.html#scrollspy

Clean Remote Project

Right Now,gwt-bootstrap project has some auto genarate files in git repository.

• .settings
• .classpath
• .gwt
• src/main/webapp/WEB-INF/deploy
• src/main/webapp/bootstrap

Auto generate files is not needed in repository.
Maven can create .settings and .classpath files by maven-eclipse-plugin.
What do you think?

Implement Popover.

http://twitter.github.com/bootstrap/javascript.html#popovers

Fix color of Buttons with links.

Because Buttons are Anchor elements, they are colored blue if they have their href property set.

Showcase

When we finish the basic porting, we have to write a cool showcase, just like the bootstrap showcase, and put it in AppEngine or Heroku.

Let users override widget's default settings.

This can be done in the configuration module. Every widget gets its default settings (button type, size, ...) from an interface that can be overridden in the configurator.

Showcase should be reponsive

The showcase (including navbar) should be responsive, if the user resolve to test it in a mobile device.

Add onClose/onHide function to Modal.

Right now there is no way to get notified when a Modal is being closed.

Let GWT handle style names.

I'm not sure we want this but I think we should talk about it:

Right now we add Strings of all the bootstrap style names to the Widgets. There will be conflicts if the user has a similarly named style. The solution would be to let GWT handle the style names and refer to them via CSSResource (https://developers.google.com/web-toolkit/doc/latest/DevGuideClientBundle). I think we would have to deactivate obfuscation because bootstrap.js probably relies on the correct names.

In this case it should also be easier to deal with changes in bootstrap because we would probably get compile time errors if a referenced style is not in the css file.

What do you think?

test

just a task test :)

Write javadocs

We need to write the javadocs for the components.

Browser Events seem not to work inside a Modal.

I'm using a Cell Widget once on my regular page and once in a Modal. In the Modal, onBrowserEvents is never called. I tried to sink the events in the body of the Modal but it still doesn't work :-(.

I have no idea what's going on here. I had to change the superclass of DivWidget from our own ComplexWidget to FlowPanel to get the events working on the main site. It seems that they were not passed through the DivWidgets. But I don't unerstand why it's working with the FlowPanel. FlowPanel and ComplexWidget are very similar...

Support LESS configuration files

As discussed in issue #9.

Support responsive design.

Right now, a responsive design via bootstrap-responsive.min.css has to be implemented manually. We should change that.

Check Tab Plugin implementation.

http://twitter.github.com/bootstrap/javascript.html#tabs

We already support tab toggle, but options and settings are still missing.

Disabled Button should not be clickable.

from #12

Bootstrap.gwt.xml do not need Junit inheritment.

for #10.
Bootstrap.gwt.xml do not need <inherits name='com.google.gwt.junit.JUnit' />

Finish implementing forms.

http://twitter.github.com/bootstrap/base-css.html#forms

Implement Breadcrumbs.

http://twitter.github.com/bootstrap/components.html#breadcrumbs

Create Maven Repository.

Right Now,We can create jar file by maven.(Run mvn package)
I think We should create maven repository for maven , gradle and ivy and more users.

maybe we should make repository git repository at gwtbootstrap organization.
When this will be created,I add repository setting to pom.xml.

Find a versioning system.

I would like to call releases like this: Twitter Bootstrap release number plus our own one. Example: The first release would be 2.0.2.1. In this way, the user always knows which Bootstrap version we provide. Other suggestions?

Unit tests

Create unit tests for "validations" in components.

e.g.: A buttongroup can only have buttons inside it.

Support user provided CSS.

What happens if the user wants to provide his/her own CSS file, maybe with different colors? Is there a way to do that now or will the injected CSS overwrite the one of the user?

Add support for responsive utility classes.

http://twitter.github.com/bootstrap/scaffolding.html#responsive

I'll add them to DivWidget and other classes.

Stylesheet doesn't work correctly.

Im having a very weird problem. From time to time, the stylesheet doesn't work. I get a raw html site without any formatting.

Implement Carousel

http://twitter.github.com/bootstrap/javascript.html#carousel

Release Process

Right Now,I think about release process.

Maybe we shoud do,
1.Delete -SNAPSHOT from pom.xml version tags.
2.Commit pom.xml
3.Run git tag //mark relase Tag
4.Run git push
5.Deploy jars to maven repository as a Release Version
6.Upload jars to github download page
-- finish release
-- create next version snapshot
7.Increment Version and Write -SNAPSHOT to version tags in pom.xml
8.Commit pom.xml
9.Run git push

maybe I can use maven-release-plugin.
maven-release-plugin automation above process.

How do you think about this process and about use maven-release-plugin?

Create a logo

I think this was already mentioned by @caarlos0 somewhere.

Move showcase to another directory or project

for #10.

We can choose how to do it.

1. create showcase directory and add that to classapth (use maven-build-helper-pugin).
   • similar to bootstrap4gwt style. (https://github.com/nyao/bootstrap4gwt)
   • Maybe it's generate fat pom.xml. but easy.
2. create gwt-bootstrap-showcate project.(and create gwt-bootstrap-parent project)
   • maven style.
3. other more.

Which do you choose or Do your have more idea?

Collapse ResponsiveNavbar on Window resize.

Right now an open ResponsiveNavbar is not automatically collapsed when the window gets resized so it twice as high as it should be. A collapsed Navbar resizes perfectly.

Clean pom.xml

for #10.
Clean pom.xml.
gwt-bootstrap does not depend to gwt-servlet.

Modal error in UiBinder

A cryptic error is thrown in the following case (our demo):

The main application adds a UiBinder widget containing a Modal to a panel before the panel was added to the RootPanel.

Possible reason: The Modal constructor (see #23) adds the Modal to the RootPanel. When it is then added to another panel it has to be attached to something not yet added. Does that make sense?

Implement Typeahead

http://twitter.github.com/bootstrap/javascript.html#typeahead

Change Maven Site Skin

So little task.
We use bootstrap.
I want change maven site skin to bootstrap style.
I see http://maven.apache.org/skins/maven-fluido-skin/ .
I want use it.

Implement Thumbnails.

http://twitter.github.com/bootstrap/components.html#thumbnails

Fix Dropdowns in ResponsiveNavbar.

Dropdowns don't work in the ResponsiveNavbar. We might need the Collapse Plugin. But I don't think so, because the Navbar itself does collapse. Or is this due to jQuery?

Fix Navbar spacing problem.

Because of all the GWT divs that ensure a "proper" layout, there seems to be no easy way to get 50 px of space for the Navbar. One way is to use LayoutPanel. But if we do that, we force the user to change his main main panel if he wants to use the Navbar. ..

Implement Collapse.

http://twitter.github.com/bootstrap/javascript.html#collapse

(see also #33).

Changing settings in Modal doesn't work.

Changing the Backdrop in the Modal doesn't work. Changing the default setting does work.

This is probably related to #58.

Implement Tooltips

http://twitter.github.com/bootstrap/javascript.html#tooltips

Add datepicker.

This datepicker is not official but it looks pretty good. Does anyone mind if I add this? We can always remove/replace it once there is an official version.

Test Cases

We have to define the use cases and etc.. and them, write test cases for each user case :)

Some CodeBlocks run prettyPrint several times,But maybe should one.

Right now,CodeBlock class calls PrettyPrintHelper.configure method on CodeBlock is loadded.
and PrettyPrintHelper runs prettyPrint as javascript native method.
But prettyPrint should be run once.

If we setup some CodeBlock.linenums = true ,we'll happen design break.

But ummm......
Maybe we should modify pretty.js.
Because pretty.js applies style to all CodeBlock tags prettyprint method is called each time.

we have to modify or create prettyprint(element).

Trigger doesn't work in Tooltip/Popover.

Does anyone know why the trigger doesn't work in those two classes (implemented in a common superclass)? When I set it to "focus", nothing happens. Even if I click on the link (see demo).

Add Button Plugin.

http://twitter.github.com/bootstrap/javascript.html#buttons

Maven repository will be deleted by build process in now

I finished make jar and deploy process by maven.
But it's process has problem.
If we run mvn clean site without deploy goal ,remote maven repository is deleted ........

Right now,our maven deploy process is

1. Create jars (core sources javadocs)
2. Deploy to local directory target/site/maven/snapshots or target/site/maven/release
3. Make maven site to local directory target/site
4. Push maven site from target/site to gwt-boostrap/gh-pages git repository as a github pages.
   and it's can run mvn -PforGithubDeploy clean deploy site {github auth options} in one command.

But if we run mvn clean site without deploy goal, clean goal delete all under the target directory,
and In site goal process,Push maven sites without maven repository.

I'm thinking about this problem now.
Maybe,We should make maven repository in github.
and add to gwt-bootstrap git repository as a nested git directory(maybe this path is gwt-boostrap/maven).

Modify deploy precess 2.-4.

from
2. Deploy to local directory target/site/maven/snapshots or target/site/maven/release
3. Make maven site to local directory target/site
4. Push maven site from target/site to gwt-boostrap/gh-pages git repository as a github pages.

to
2. Deploy to local directory maven/snapshots or maven/release
3. Git Push maven/* to git maven repository's gh-pages branch.

I'll try it modify into few days.
In the meantime,modify process,I don't deploy our jars to maven repository.
But I upload jars to our download pages.