just a simple dijkstra ... On 23 Jun., 22:55, giuseppe la scaleia <[email protected]> wrote: > A question what do you use for route on map?? Regards giuseppe > > Inviato da iPhone di Giuseppe La Scaleia > > Il giorno 23/giu/2010, alle ore 22.13, newnoise <[email protected] > > ha scritto: > > > and when i wrote service again, i totally meant servlet. its been a > > looong day ... > > > On 23 Jun., 22:11, newnoise <[email protected]> wrote: > >> sorry i meant service. > > >> i try to explain the problem more precisely: > >> i got a map. users can, for example, use the app to calculate a > >> route- > >> advise. if the user did so he may want to print the route. but the > >> map > >> is nearly fullscreen, so if he justs prints it like that it looks > >> pretty bad. so what i do is to open a new browser window with a > >> smaller map. and now in this new window the route must be newly > >> calculated, because you cant give a java object to the new window, > >> right? > > >> what i want now is that the print page uses the routing servlet of > >> the > >> main app. what i dont want is that the print page needs all the same > >> server code again. but i dont get it working. because if i merge the > >> projects the web.xmls clash. > > >> thanks a lot! > >> tom > > >> On 23 Jun., 21:47, Blessed Geek <[email protected]> wrote: > > >>> "service"? > > >>> Printing thro web service that all/any window could call with a > >>> single > >>> url? Why would you need to duplicate code when you can call it > >>> with a > >>> single url? > > >>> Or did you mean you have a specialised GWT window written to handle > >>> printing and you wish to route all printing to that GWT window? And > >>> you wish to deal with the occasionally asked question of how to > >>> perform inter-frame communication for GWT? I don't remember now, but > >>> there is a google code project to expose GWT objects to javascript. > >>> Coupled with GWT Dictionary API, I wonder if that will help. > > >>> Of course, you do realise that for two frames to communicate, they > >>> should have the same root Window parentage so that one frame could > >>> refer to another thro the frame hierarchy. > > >>> GWT team should seriously look at providing a comprehensive facility > >>> for interframe communication, rather than having us perform > >>> algorithmic contortions and acrobatics - like having to scratch your > >>> own nose thro the route of bending your hand behind your head. > > > -- > > You received this message because you are subscribed to the Google > > Groups "Google Web Toolkit" group. > > To post to this group, send email to [email protected] > > . > > To unsubscribe from this group, send email to > > [email protected] > > . > > For more options, visit this group > > athttp://groups.google.com/group/google-web-toolkit?hl=en > > .
-- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
