ok, sounds good thanks
Eric On Fri, Jan 28, 2011 at 3:51 PM, Christian Ledermann <[email protected]> wrote: > Hi Eric, > > collective.flexitopic was not designed with extensibility in mind :( > but this is about to change. > Right now collective.flexitopic and collective.geo.flexitopic use a > monolithic page template. > (I had to get something out fast) > > I will split this into a simplified template with viewlet managers. > > 1) will hold the viewlets for > * description > * the subtopic tables > * and in case of geo.flexitopic the map > > 2) will hold a viewlet for the form > > 3) will hold the results table > > 4) will probably be a manger to insert the javascript > > > as a side effect this will decrease the lines of code in > collective.geo.flexitopic > there i only have to define the viewlet to display the map instead of having a > amended copy of the flexitopic page template :) > > This way one can easily add or remove functionality/parts of the page. > > I think i will get something out next week so we can take it from there. > > On Fri, Jan 28, 2011 at 3:51 PM, Eric Bréhault <[email protected]> wrote: >> ok good ! >> we are going to study collective.geo.flexitopic to see how it is structured >> and we keep you informed >> >> eric >> >> On Fri, Jan 28, 2011 at 12:04 PM, Christian Ledermann >> <[email protected]> wrote: >>> Hi Eric, >>> >>> On Fri, Jan 28, 2011 at 1:05 PM, Eric Bréhault <[email protected]> wrote: >>>> hello Christian, >>>> >>>> very nice integration between collective.geo and flexitopic ! >>>> >>> >>> Thanks :) >>> >>>> for your information, we (Makina Corpus) have created >>>> collective.geo.mapcontent and we are currently working on a new >>>> feature that provides the reversed mechanism compared to yours: >>>> by zooming or moving on the map, we get a dynamic list of all the >>>> contents belonging to the current bounding box >>>> >>> >>> I am going to need that 8-) >>> >>> >>>> we do not plan to use flexitopic to render this list, it is supposed >>>> to be something quite simple and light in term of ergonomy, so just a >>>> list of clickable items in a portlet, not a table with columns, >>>> sorting and so on >>> >>> Yes sounds perfectly reasonable, keep it small and simple. >>> >>> >>>> but I think the 2 features could be combined (your scalar filtering >>>> could be refined with a spatial filtering, and vice-versa) >>> >>> Yes, I think that would be awesome >>> >>>> maybe it could make sense to merge them and also offer optional widgets: >>>> for instance, someone may not need the slider, but need the flexitopic >>>> rendering, another might want a basic html display but with a slider, >>>> or display the list in a portlet, etc. >>>> >>> >>> maybe this could be done the way I did it with >>> collective.geo.flexitopic and collective.flexitopic. >>> A new product that glues the functionality together, that way the base >>> products can be kept small >>> and there is less feature creep in the base. >>> >>>> maybe the different widgets could be provided as macros, and as far as >>>> we make sure they provides an accurate JQuery behaviour, the widget >>>> should be able to interoperate >>> >>> yes either macros or viewlets. >>> > > > -- > Best Regards, > > Christian Ledermann > > Nairobi - Kenya > Mobile : +254 729495789 > > <*)))>{ > > If you save the living environment, the biodiversity that we have left, > you will also automatically save the physical environment, too. But If > you only save the physical environment, you will ultimately lose both. > > }<(((*> > _______________________________________________ > Community mailing list > [email protected] > http://lists.gispython.org/mailman/listinfo/community > _______________________________________________ Community mailing list [email protected] http://lists.gispython.org/mailman/listinfo/community
