We want you for gwtQuery

[Julien Dramaix]

Dear community,

The second release of GQuery is currently out. GQuery is now still
much better than before and includes nice features like jquery Ajax
syntax which enable to access most of the jQuery API.
We are conviced that GQuery can, at certain level, make GWT
developers' life easier. However, there is still lot of work to do and
we have several ideas that we would like to implement towards the
improvements of the quality and the usefulness of GQuery.
Unfortunately, we believe that our current development team is not
enough to deliver you these improvements in an acceptable time frame.
That's why today we request for your help. If you have some free time
and you would like to contribute to GQuery, just let us know.
We have a few tasks that we can assign to you. Some task may take one
hour, other tasks may take several days. They are related to the
different aspect of a project.
e.g. :
- improve documentation and code examples
- write new plugins or port existing jQuery plugins
- improve testing of the library by implementing missing junit tests.
- Enumerate and/or implement the remaining JQuery API methods to
implement
- Give some ideas/tips/snippets in order to improve/enhance/refactor
the library
- Reporting issues and bugs ;)

If you are interested, please send us a mail to Manolo and myself or
reply to this post. Please indicate which tasks you will be interested
to work in.

Cheers,

The GQuery team

[AK]

Hi,

I am interested in helping GQuery.

I have GWT working experience. 

I am interested in 

1. Bug Fixes
2. jUnit Tests
3. Code Examples and Documentation
4. Implement remaining JQuery API

Thanks,

AdK

[Manuel Carrasco Moñino]

Hi AdK, thanks for your offering

Have you read the contribution Faq ?

Have you any idea to start with ?

I think the first two points are good starting points, try to follow and fix some issues and make tests for them.

Cheers
- Manolo

--
You received this message because you are subscribed to the Google Groups "gwtquery" group.

To view this discussion on the web visit https://groups.google.com/d/msg/gwtquery/-/UNa_yrkV2FwJ.

To post to this group, send email to gwtq...@googlegroups.com.
To unsubscribe from this group, send email to gwtquery+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/gwtquery?hl=en.

[Ian White]

I would like use EventBinder with your dnd plugins.

I believe it could be accomplished by simply editing your existing events, such as AbstractDraggableEvent such that they

are boilerplate-less and extend GenericEvent...

E.g. 

public abstract class AbstractDraggableEvent extends GenericEvent {

  private DragContext context;

  public AbstractDraggableEvent() {

  }

  public AbstractDraggableEvent(Element draggable) {

    context = new DragContext(draggable);

  }

 ... remainder unchanged

and 

E.g.

public class DragEvent extends AbstractDraggableEvent {

  public DragEvent(Element draggable) {

     super(draggable);

  }

}

Then in 

  $(".iWantToDrag").as(Draggable).draggable(new DraggableOptions(), handlerManager);

the 2nd arg (handlerManager) would no longer be required.

Am I right in thinking this simple source code changed is all that would be required ?

Shall I make the edits and submit them for approval...

OR HAVE YOU ALREADY MADE THESE CHANGES FOR YOUR NEXT VERSION ?

Ian

[Manuel Carrasco Moñino]

I think GenericEvent is not part of the standard GWT, is it? I think it is part of https://github.com/google/gwteventbinder

The tendency of gquery is not to make it depend on 3party library and force anyone else to use other libraries, but we are opened to different opinions

- Manolo.

--

You received this message because you are subscribed to the Google Groups "gwtquery" group.

To unsubscribe from this group and stop receiving emails from it, send an email to gwtquery+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Ian White]

I suppose you are right - I assume (I hope) it will be part of GWT 3.0.

Would I be correct in thinking that gwt-query will also be an integral part of GWT 3.0 ?

I can't imagine using GWT without it or its plugins these days.

Re - providing help - I will think about how / where I could usefully contribut. I'll be in touch...

Many thanks

--
You received this message because you are subscribed to a topic in the Google Groups "gwtquery" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/gwtquery/PFRWZn5RW14/unsubscribe.
To unsubscribe from this group and all its topics, send an email to gwtquery+u...@googlegroups.com.

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

--
Ian White
h: +61 2 9948 9739
m: +61 404 950 122
skype (home): biancashouse

[Manuel Carrasco Moñino]

On Mon, Mar 3, 2014 at 3:11 PM, Ian White <i...@biancashouse.com> wrote:

I suppose you are right - I assume (I hope) it will be part of GWT 3.0.

Would I be correct in thinking that gwt-query will also be an integral part of GWT 3.0 ?

AFAIK, It is not in the gwt steering committee plans include both, nor include css selectors in the core.

They prefer that this features are in external libraries. But who knows, may be if people demand these features they could consider.

 

I can't imagine using GWT without it or its plugins these days.

Agreed

 

Re - providing help - I will think about how / where I could usefully contribut. I'll be in touch...

You can contribute with gquery in any way you want, you are welcome.

There is a list of features we would to implement. We have written down some of them, so as GSOC students or other people wanting to contribute could pick them up. https://code.google.com/p/gwtquery/wiki/GSOC_Ideas

- Manolo