A camliPath can now have a file blob as a target (instead of a
permanode). And when we render these camliPath members as links, since
it can happen that these members haven't been described, we can't know
in advance whether to link them as permanodes or as blobs, so we
always default to permanode. Therefore, it can now legitimately happen
that we end up on the permanode page, while the blobRef is actually
one of a non permanode.
This patch tries to cope with that situation in a bit nicer way.
Context: http://camlistore.org/issue/470
Change-Id: Ic3b728541e164a6e6056d8f275a1d7e76b41e043
-removed redundant "gallery" feature (since container aspect does it)
-> allowed to get rid of blob_item_container dependency.
-removed the whole resolvedMetaData business. If one wants to derive
properties (such as the title) from children blobs/permanodes, just
create a new BlobItem for that child and get the properties with
methods on that child.
-> makes for clearer code, and easier to prevent null errors.
-started making use of search session
Change-Id: Ic706c96e1c05ad5489ab4b14ed21e315a557a8a8
It would be better to support real URLs for these, but I need to
figure out how routing those should work first.
So for now this is maybe less annoying.
Change-Id: I1992d23cb0f94b509f73db23a542b56ca5df7531
Implemented bulk tagging operations via single command 'tag'. Add, Delete, Set, and Clear modes are available (add, del, set, clear). Help on command usage is supplied via -help argument.
basic usage: tag <mode> (args)
tag add 1,2,3
tag del 1,2
tag set 1
tag clear
tag -help
Caveats:
Client will attempt to add/remove tags regardless if the selected permanode contains those values. So it will add a tag multiple times and attempt to delete a tag that is not set.
Change-Id: Ib5c8ccc3d74e49701629c37397de478b95db4fd6
Reorganizes common OAuth2 things into importer/oa2_importers.go
Rewrites CallbackURLParameters to return url.Values.
A controversial workaround for nil context has been left out,
and this may cause panic and will need a proper fix.
Change-Id: I0789f4732412aa559078ec2c6b6797925ab8cd05
Works but only lightly tested.
Could use lots of refactoring with code common with twitter.
Needs a test too.
Change-Id: I07f72d29acbc0226aeeedba0afe0bf7eeeac5ad3
http://imgur.com/Re14XKc,6fYHJqp,39nnQiT#0
Camlistore is built around the idea that every object is a blob,
but blobs can also self-describe themselves as more than a blob.
For example, some blobs are also files, or images, or sets, or
permanodes, or movies, or foursquare checkins. Etc.
Here is an idea for the detail page that reflects that underlying
reality of Camlistore.
Each blob has a single canonical URL in the web UI for its detail
page. Currently this is /?p=<...>, but should ideally be just
/<blobref>.
Within the web UI, many "aspects" register interest in providing
views on blobs. Each time the user navigates to a detail page,
each aspects gets to say whether it can provide a useful view on
the blob.
Aspects are currently rendered (crappily) as tabs along the bottom
of the UI. I'm not sure how they should actually be rendered, this
is temporary.
This patch includes the following aspects:
- image (the old image detail)
- permanode (the old old permanode page)
- blob (the old old blob page)
Change-Id: Idb3cdbb203799a5d9c113d1b37b67a2724040085
mpl