Closed
Bug 571293
Opened 14 years ago
Closed 13 years ago
clarify file-related functionality in the url module
Categories
(Add-on SDK Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: dietrich, Unassigned)
Details
from myk in bug 564524: >+<code>url.**toFilename**(*url*)</code> ... >+<code>url.**fromFilename**(*path*)</code> Note: regarding the file module (not this bug! just thinking aloud), perhaps what makes the most sense is for URL objects to have a "file" property that is null if the URL does not represent a local file and is a File object with a path property if it does represent a local file, so the way to get a file path from a URL would be: URL("...").file.path. And conversely, the file module would provide a File constructor, to which one can pass a local file path, that returns a File object with a url property, so one can do File("...").url to get the URL from the file path. Alternately, we could make URL objects also be File objects via object composition, but that could get tricky (f.e. dealing with the two different meanings of "path").
Comment 1•14 years ago
|
||
The Add-on SDK is no longer a Mozilla Labs experiment and has become a big enough project to warrant its own Bugzilla product, so the "Add-on SDK" product has been created for it, and I am moving its bugs to that product. To filter bugmail related to this change, filter on the word "looptid".
Component: Jetpack SDK → General
Product: Mozilla Labs → Add-on SDK
QA Contact: jetpack-sdk → general
Version: Trunk → unspecified
Comment 2•13 years ago
|
||
Doesn't seem to be bothersome enough to leave a bug open to track the decision whether or not to do it.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•