[dev] Ansel Gallery IDs vs. Names

[Michael Rubinsky]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ben Klang wrote:
| On Feb 20, 2008, at 10:49 AM, Michael Rubinsky wrote:
|
|> | So I'm stuck.  I think it's clear that the galleryExists() API
|> | documentation needs to be amended to reference the gallery ID
|> instead
|> | of a name.  But does it cause any problems to restore the old API
|> | functionality of allowing the gallery ID to be specified via the API
|> | rather than forcing a random ID?  Why was this option removed?
|>
|> Unfortunately, that's not possible since the gallery id is the key for
|> the gallery in the gallery table.
|>
|> Maybe if you outline your specific needs/use case we can work to
|> get the
|> ~ functionality you need into the current api structure...
|>
| What I'm doing is creating a module for social networking.  One of
| the features is to allow per-user photo galleries.  It occurs to me
| that perhaps instead of gallery IDs I can now use the gallery slugs.
| I need two functions basically:
|
| 1) Check whether a gallery already exists for this particular user
| ($app is set to the profiles app and not Ansel so it should be a
| private set of galleries)
| 2) If the gallery is determined not to exist, automatically create a
| gallery for the user.

Why not list galleries by user then? This would give you back the
gallery ids of all the galleries owned by the user...if there are none
returned then you know you need to create it?


- --

Thanks,
mike

The Horde Project (www.horde.org)
mrubinsk at horde.org

"Time just hates me. That's why it made me an adult." - Josh Joplin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHvFaxTW0K6bINYV4RAhq8AJ45nGJqT6htwX/kFGGT8I4Vt6pGUgCcCkFU
B2n1SehFbXkvhfZGY3Qtx5E=
=+yVB
-----END PGP SIGNATURE-----