[geojquery] Playing with the prototype GeojQuery Widget

[Christian Wygoda]

Great writeup, Anne!

Everyone can probably agree on two facts:
* jQuery-UI's factory is to be used for all visible widgets (what's an
invisible widget? :-)) except the core OL map widget.
* which factory or API-Style to use for the core map widget is an essential
question.

Pro UI-factory: It's already there and would offer the same API-Style as all
the other great widgets we will code...
Con: Added dependency with all drawbacks for a simple core map - no CDN for
customized dependency libs, etc., etc. Were set for the UI-style API.

If we want to steer off jQuery-UI's factory code then we need to decide on
an API style. As much as I understand Volker's thoughts on that topic, I
would like to point out that going down his proposed road would mean having
to learn two basic API styles for one project if it uses more than the basic
map... I urge to not go down that road as it probably would impact project
acceptance.

As much as I understand feelings about minimizing required download size -
should it be a concern that early on? API style is more important, right? Or
is it just me?

Ok, I'll try to successfully reach my final station tonight while Deutsche
Bahn tries to do anything against it... more time to think about
geojquery... :)
Am 2010 9 24 17:47 schrieb "Volker Mische" <volker.mische at gmail.com>:

> On 09/24/2010 11:06 AM, Anne Blankert wrote:
> > Hello list,
> >
> > I do like how the ui-widgets work, ...
> To clearify things a bit. I'm +1 for using the jQuery UI factory for
> normal widgets that operate on DOM. But geoMap() is something different.
> This is the part we were refering to as geojquery-core. It doesn't
> return a DOM/jQuery object, therefore we don't need the strange
> geoMap('function-name', options) convention. It returns a geoMap object.
> We can add layers to the object and so on. We can just call functions
> directly on the object (like geoMap(...).layer(...)) [1].
>
> Therefore I proposed that we don't use the jQuery widget factory for it,
> as it adds the dependency on it and we don't need the full feature set
> (like automatic getters, setters, the special trigger etc. (see the link
> Anne posted above)).
>
> [1] http://gitorious.org/geojquery/pages/Api
>
> Cheers,
>   Volker
>
>
> _______________________________________________
> Geojquery mailing list
> Geojquery at lists.osgeo.org
> ht...
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/mapquery/attachments/20100924/8b4fc032/attachment.html