Code for print tools in Release ArcGIS Viewer for Silverlight

[LeeGraham]

Any chance you guys provide the code for the two print options you provide in the Release Viewer. It is working well across domains and am curious to see what you are doing because the layouts of your sample suck - happy to fix that but mainly want to see the code just for those tools.

[KatherineDalton]

Lee,

We've had requests for the code for several of the tools, so we will add your request to our list. We're still in the planning and feasibility stages of this though, so no guarantee right now.

Katy

[LeeGraham]

Printing has always been the weak link in every single web project for mapping that ESRI has ever produced (and I have used every single one), so anything you guys can do to assist would be great. Like most developers, I am not 100% happy not having the full source code for the viewer like we had to the Flex viewer. While I can see ESRI's arguments for not providing the code, I can't see at all what the problem would be for providing code for tools.  I have already developed lots of custom tools using extensibility/SDK and have been able to manipulate the provided layouts to do lots of things. I can see that I could also likely manipulate the crappy layouts that are provided for printing, but it would be useful to be able to pass parameters and such to it to manipulate the titles and such.

[DerekLaw]

Hi Lee,

Printing has always been the weak link in every single web project for mapping that ESRI has ever produced (and I have used every single one), so anything you guys can do to assist would be great.

FYI, ArcGIS for Server 10.1 has a new PrintingTools service - which is a geoprocessing service that makes printing from web applications much easier and better. You can read more here:

Printing in web applications

... I can't see at all what the problem would be for providing code for tools.

As Katy indicated, we're still working on providing some of the Viewer's tools' source code in the future. Similar to other developer API/SDK materials, the "raw" source code needs to be properly documented and formatted in the best way possible to share with our developer community. We are working on this request.

Hope this helps,