nikhilbchilwant / gwt-tools Goto Github PK
View Code? Open in Web Editor NEWAutomatically exported from code.google.com/p/gwt-tools
Automatically exported from code.google.com/p/gwt-tools
See subject.
Original issue reported on code.google.com by [email protected]
on 3 Mar 2010 at 3:31
See title.
Original issue reported on code.google.com by [email protected]
on 22 Apr 2010 at 4:11
Since ContactsService is no longer needed, remove it, along with Async
interface and server-side implementation.
Original issue reported on code.google.com by [email protected]
on 3 Mar 2010 at 3:45
See title.
Original issue reported on code.google.com by [email protected]
on 8 Mar 2010 at 8:10
Currently, it's using its own Presenter interfaces. Change to use the
presenter module interfaces.
Original issue reported on code.google.com by [email protected]
on 3 Mar 2010 at 5:46
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
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
Currently if the default view is invoked because something is wrong with
the URL presented to the place service, all the defaults are used and no
further parsing of the URL is attempted.
***Perhaps***, it should still try to parse the rest of the URL, EVEN if
it's just a default place.
Original issue reported on code.google.com by [email protected]
on 17 Mar 2010 at 4:24
1) Rename getCompatibleType to getCompatibleRequestType.
2) Consider removing isCompatibleWith method. Check where it's used right
now first.
Original issue reported on code.google.com by [email protected]
on 2 Mar 2010 at 8:44
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
Requires creating a parent pom for modules.
Original issue reported on code.google.com by [email protected]
on 4 Mar 2010 at 1:54
Place.createPlace should clearly indicate in the Javadoc that state of the
Place instance that method is being invoked on should NOT get affected AT
ALL as a result of invoking the createPlace() method.
Original issue reported on code.google.com by [email protected]
on 17 Mar 2010 at 2:18
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
Add release configuration to the parent pom so that releases can be done in
a organized manner.
Original issue reported on code.google.com by [email protected]
on 4 Mar 2010 at 1:55
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
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
This should include constants like:
DEFAULT_PLACE
NON_DEFAULT_PLACE
ADD_TO_HISTORY
DO_NOT_ADD_TO_HISTORY
The names should be probably be improved but that's the general idea.
Original issue reported on code.google.com by [email protected]
on 2 Apr 2010 at 5:12
Add ability to batch RPC requests, i.e., this would end up making only 1
RPC call to the server.
Original issue reported on code.google.com by [email protected]
on 13 Apr 2010 at 7:45
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
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
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
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
See title.
Original issue reported on code.google.com by [email protected]
on 22 Apr 2010 at 4:13
Changed the name of the bind() method to either bindDisplay() or
bindView(). Probably the 2nd one. Same goes for unbind method.
Original issue reported on code.google.com by [email protected]
on 9 Mar 2010 at 7:29
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
Place interface show() method should not accept a HandlerManager. Instead,
caching the reference to the HandlerManager (eventBus) should be done in
the constructor of that place instance.
Original issue reported on code.google.com by [email protected]
on 8 Mar 2010 at 8:02
Currently, if the host page is under https, then the request will be made
through https, if under http, then the request will be made under http.
Need a way to be able to specify which protocol to use for what.
also, need a way to be able to have some requests trigger JEE security and
some requests not.
Original issue reported on code.google.com by [email protected]
on 2 Apr 2010 at 4:36
Currently, it says this:
/**
* @param List of IDs of contacts to delete.
*/
public void setIds(List<String> ids)
Should be:
/**
* @param ids List of IDs of contacts to delete.
*/
public void setIds(List<String> ids)
Original issue reported on code.google.com by [email protected]
on 5 Mar 2010 at 1:37
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
What steps will reproduce the problem?
1. Trying to save an edit contact information
Throws NPE in EditContactPresenter (contacts2 app)
Original issue reported on code.google.com by [email protected]
on 2 Mar 2010 at 9:37
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
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
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.