编辑“Gallery:Embedding Development Roadmap”（章节）

==More convenience functions==
'''valiant:''' WPG2, joomla/G2, mediawiki etc. continue to impress by means of fantastic embedding ideas and features. But for some of those features, too much coding is required. We need to try to port those features back to the G2 embedding API or to modules. 
 
'''ozgreg:''' all thanks to you Valiant for the time and effort you spent in the initial API code..

Goal: Integrations should be able to offer such embedded features with much less code and with less work.
===Embedded album / photo browser===
'''valiant:''' Embedded album / photo browser à la mediawiki -> picking images, e.g. for articles / blogs.

'''ozgreg:''' some kind of mini browser on the WPG2 radar, it would make life a LOT easier if instead it was a module in G2 that I could call via API.

'''eads:''' Does this include special themes with javascript that will can do a one-click integration with an article/post?

'''valiant:''' Maybe with special themes, maybe by special module pages or by other means. We'll see.

'''capt_kirk:''' I've modified [http://g2image.steffensenfamily.com/ Gallery2 Image Chooser] so that it no longer requires TinyMCE.  It will still work as a TinyMCE plugin, but you can also call it to insert a link in any browser form.  [http://demo.steffensenfamily.com Here's a demo] of how to write the javascript for using it from any application.

===Better article / blogging support===
'''valiant:''' Powerful support for simplifying picking / showing a single image by name, path, id, or an album etc. -> show images/ albums in blogs / articles of the external application. See mediawiki, wp, mambo, drupal, ...

'''ozgreg:''' WP utilises tags which as a concept works well, the biggest issue we continuous run into is WP and the way it is helpful in cleaning up blog entries :(

===Menu's etc.===
'''valiant:''' Drupal, joomlo, ... offer their own menus for G2 albums etc. e.g. by assembling them from theme variables. We need to offer an API for that or at least document how this can be done.
===Authentication tunnelling===
'''eads:''' The ability to seal off your G2 site from the public via a common authentication mechanism (like HTTP auth) but pass G2 the correct authentication information from the calling app.

'''valiant:''' Not sure if what you want is already implemented. When G2 is embedded, it is accessed through the embedding application. If you deny access to G2 in the embedding application, you can't access G2. Plus, when embedded, G2 trusts the embeddeding application. G2 doesn't do any authentication when embedded, it just accepts the activeUserId.
Regarding apache / HTTP authentication: No, this isn't possible yet (forwarding the user id from apache to G2), but you can block access to G2 in the embedding application by securing the embedding application by HTTP auth.

===Other stuff===
'''valiant:''' What else could be ported to the G2 API side to make the life of integration authors easier?
====More image block options====
'''eads:''' Turn off linking in image blocks.

'''eads:''' Specifying sizes and having them autogenerated in G2.
'''ozgreg:''' I have a RFE already open for this -> 1256288