Eric, Thank you, this is what I thought from looking at the code, but I'm always amazed at how easy something things are in OL, because of the OO coding style that I often make things harder for myself than they need to be. It is good to have confirmation that I'm proceeding down the right path.
-Steve Eric Lemoine wrote: > Hi Stephen > > I don't see a more subtle way than implement two classes, one > inheriting from ArgParser, and another inheriting from Permalink. The > former will deal with the routing-related params in the URL. The > latter would extend the updateLink method so that the resulting link > includes the routing params. > > For this I'm afraid you'll have to look at the code of ArgPasses and > Permalink and understand what it does. > > Maybe someone has better ideas... > > Eric > > 2008/11/18, Stephen Woodbridge <[EMAIL PROTECTED]>: >> Hi all, >> >> I'm wondering if anyone has a good example of extending permalink and >> argparser to support additional parameters. What is the best practice >> for doing this? I can rewrite these for what I need to do, but I thought >> there might be a more subtle way to do this that I'm not seeing. >> >> For example, I have a page the integrates with pgRouting and I would >> like to also save the start point, end point, method. Then when the url >> is called, check if these are set and make an ajax call to get the route. >> >> Thanks for any ideas or examples you might be able to offer. >> >> Best regards, >> -Steve >> _______________________________________________ >> Users mailing list >> [email protected] >> http://openlayers.org/mailman/listinfo/users >> _______________________________________________ Users mailing list [email protected] http://openlayers.org/mailman/listinfo/users
