in reply to Feature idea for code tags

I think an acceptable solution that doesn't change the syntax of <code> tags is to use a filename of the form $node_id . "_" . $index_of_code_tag.

That proposed filename can be sent with the appropriate Content-Disposition HTTP header.

That way no node author has to invent names, and when you save multiple code tags from one node you don't have to rename them manually to avoid name clashes.

Replies are listed 'Best First'.
Re^2: Feature idea for code tags
by goibhniu (Hermit) on Dec 02, 2007 at 20:08 UTC

    I leave implementation details to PMDev of course; I only have an idea. But the intent of my idea was to have the savename="" attribute be optional so that no one who didn't want to would have to use it.


    I humbly seek wisdom.