GithubHelp home page GithubHelp logo

gwt-tools's People

Watchers

 avatar

Forkers

johnnny333

gwt-tools's Issues

Update PlaceService interface to have a getHistoryTokenParser() method.

Add getHistoryTokenParser() method to the PlaceService interface.
Currently, when creating place instances inside the AppController, the
AppController needs to be passed a separate instance of HistoryTokenParser.
It would be cleaner and more proper if the HistoryTokenParser would be
wrapped up inside the PlaceService.

Original issue reported on code.google.com by [email protected] on 8 Mar 2010 at 7:14

Wrong URL encoding/decoding methods used

DefaultHistoryTokenParser uses URL.encode and URL.decode. These methods are 
used to encode/decode an entire URL, NOT just the query string. Therefore, they 
leave '/' and other valid URL characters un-encoded when they should be 
encoded. 

These methods invocations need to be replaced with: encodeQueryString and 
decodeQueryString from:
http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/http/
client/URL.html

In DefaultHistoryTokenParser, these calls are roughly on lines 70 and 156.


Original issue reported on code.google.com by [email protected] on 12 Jul 2011 at 4:06

Generated JARs should include source

1) Add the same type of configuration to the pom as the rpc-service has to
include sources.

2) Change the way the place-service includes sources, i.e, through the
gwt-maven-plugin. Use the <resouces> instead.

Original issue reported on code.google.com by [email protected] on 3 Mar 2010 at 3:28

Investigate combining autodiscoverers of handlers

See if it's possible and beneficial to be able to allow clients of
rpc-service to define both, a Spring auto discovery and Standard auto
discovery mechanisms at the same time.

One idea is to make sure the Spring one runs first and registers the
Spring-enabled components and then the standard one would run and register
only those components not yet registered by the Spring auto discovery.

Original issue reported on code.google.com by [email protected] on 19 Mar 2010 at 3:40

Provide auto-discovery of Spring-enabled RPC request handlers

1) This is the same issue as issue 7, but this time a easy and
straightforward way of auto-discovering Spring-enabled RPC request handlers
needs to be coded.

2) Create contacts3 as an example of using Spring-enabled beans as RPC
request handlers.

Original issue reported on code.google.com by [email protected] on 16 Mar 2010 at 6:45

Keep all IDs as Strings everywhere

Since the original Contacts application defined contact ID as a String,
keep it as a String everywhere... This includes RPC requests, Places, etc.

When trying to create a place based on a history token with an ID, try to
convert it to an 'int' just for demo purposes.

Original issue reported on code.google.com by [email protected] on 2 Mar 2010 at 9:06

Add ability for a Place to update history token in browser without navigation

Currently, if a PlaceChangedEvent is fired, the View/Presenter/etc that the
place controls/represents will be either recreated or refreshed somehow.

There are a lot of times when a PlaceChangedEvent doesn't denote a real
navigation to a different view, but state change in the current view. The
way things are implemented right now, this will cause the entire view to be
re-created. This is still done on the client (browser), but it's not as
good as not doing it at all, but just updating the browser history token
and that's it.

I believe, this can be accomplished by introducing another flag into the
Place interface which would indicate if the Place is really to be "shown",
i.e., real navigation, OR if the Place simply needs to update the URL,
i.e., the URL representation of the state of the view.

By default, this flag should indicate that the place is a real navigation
event. This way, if a presenter decides to update its history state, it
would have to specify explicitly (through the constructor of the place) and
it would be a conscious decision on the part of the developer NOT to cause
a real navigation event by firing a PlaceChangedEvent with that particular
Place instance. 

Original issue reported on code.google.com by [email protected] on 17 Mar 2010 at 2:12

Create RpcServiceAsync in the entry point

Currently, the concrete implementations of Place have to use a static
reference to the RpcServiceAsync. 

Instead, they should be created with that reference to begin with. This
requires RpcServiceAsync to be created in the entry point class and pass it
to the AppController which will pass it to the constructors of Places.

Original issue reported on code.google.com by [email protected] on 8 Mar 2010 at 7:33

GwtTests either hang or break

What steps will reproduce the problem?
run mvn clean install without -DskipTests

Tests run very long on Windows 7 and finish successfully sometimes and
sometimes not. Not yet sure what needs to be done for this to be fixed.

These same tests run just fine in Eclipse and pass.



Original issue reported on code.google.com by [email protected] on 3 Mar 2010 at 5:49

Convert regular exceptions into RpcServiceException

Investigate creating a more automated way to convert regular exception into
RpcServiceException so that the client side code will be guaranteed that
only Java-translated-into-Javascript exception shows up in the client code
as a result of invoking the execute method of the RPC handler class.

Original issue reported on code.google.com by [email protected] on 23 Apr 2010 at 1:53

Provide a mechanism for auto-registering handlers

1) Right now, the client application has to create its own way to register
the handlers with the RpcRequestHandlerRegistry. Usually, this is done with
a ServletContextListener (as in the example contacts2 app).

Provide a mechanism where the client application would be able to just
annotate an RpcRequestHandler implementation and the rpc-service would
automatically find it based on some starting package name to search.

This includes to not only find the handlers, but also initialize them in at
least the simple way (just new it up) or the Spring way (instantiate them
through some spring context, etc).

2) Update contacts2 application to use that mechanism.

Original issue reported on code.google.com by [email protected] on 3 Mar 2010 at 4:35

Mavenize the base contacts application

The base Contacts application provided by Google should part of the
gwt-tools modules as the base example of MVP. This example is from the
Google MVP tutorial.

The contacts1 and contacts2 applications are stages of using place-service
and rpc-service/presenter respectively.

Original issue reported on code.google.com by [email protected] on 4 Mar 2010 at 2:20

Figure out how to better automate history token showing in URL

Currently, the show() method needs to manually checked if
isToBeAddedToBrowser history is true and than use a utility method to add it.

It should really happen automatically. At the very least, PlaceServiceUtil,
should figure out from the Place instance it's being passed, if it needs to
be added, so no check is needed for that inside the show() method.

However, automating the whole whole thing such that even a call to
PlaceServiceUtil is not needed would be even better.

Original issue reported on code.google.com by [email protected] on 18 Mar 2010 at 3:58

PlaceService's registerPlace - javadoc correction

In the JavaDoc of the registerPlace() method, it says that the default
place must be fully populated to be executed, which is not true. Since the
concrete place instance may depend on the RpcService or some such, not all
of the information is required for the default place to be a valid default
place.

Also, take a look at how the EditContactPlace is created in the
AppControler as it might be wrong to initialize it with a nonsense value
(null) for the contact ID, instead, a different constructor should be provided.

Original issue reported on code.google.com by [email protected] on 8 Mar 2010 at 8:49

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.