Hi,
Just continuing from this thread.
I'm currently helping [EMAIL PROTECTED] to get their *secret* project
going. I svn co the gmap contrib with version 1712 and try to migrate
their existing code to use wicket-2.0 and pax-wicket-2.0.
During migration I noticed a couple of bug in gmap
Edward,
Thanks for the patch and hard work, i'll apply the patch right away.
As far as I see the root problem is in the way gmap 1.0 is designed; it
doenst really fit with wicket 2.0 model where we haveto pass the parent as
contructor argument. as you said, porting and issues that appear might
Hi there,
we are playing around with the Gmap wicket extension and would like to
move markers. Is there any plan to implement the GMarkerManager and
GMarkerManagerOptions in order to achive that?
Cheers
/peter
-
Take
hey,
till now there were not much interest for this library; no further plans so
far. but if people are interested i can put some effort into it and add new
features. let's see how feasible it is and how it goes.
/iulian
On 1/29/07, Peter Neubauer [EMAIL PROTECTED] wrote:
Hi there,
we are
Mmh,
yes we would be interested. We have tried GWT for some stuff but the
resulting code looks not very nice and having everything on the client
is not that cool either, so gut feeling that wicket fits best.
It seems that the Gmap API is quite clean and lean, and your
integration looks great,
Hi Peter,
the big thing is that the existing gmap code needs to be refactored a bit in
order to be able to easily integrate new features. right now it is quite
complex and ulgy to implement new/more advanced features. i have to spend
some time to find a nice way to do it, after that i hope to be
