Re: remote_import - what to do with duplicate gallery names?

Quoting Chuck Hagenbuch <[email protected]>:

> Quoting Michael Rubinsky <[email protected]>:
>
>> ...another idea I had was to make these scripts more like how xp   
>> publish works in some ways. Right now, IIRC, you can already  
>> specify  the gallery id or slug name of a gallery to use instead of  
>> having it  create a new one. What if, if no gallery is specified on  
>> the command  line and no --create or similar, you have a list of  
>> galleries  displayed to choose from - and maybe once a selection is  
>> made, it's  saved in a .ansel_id file as suggested in my previous  
>> email.  It might  be a little tricky on the command line with  
>> larger gallery lists, or a  really nested structure, but it's  
>> another idea to toss around.
>
> That seems like a good idea with a graphical frontend, but I think  
> it's a bit too smart for a command line tool.

Yea, I thought so. What about the previous idea of just placing a  
.ansel_id file in the directory? Still too smart?


Thanks,
mike

--
The Horde Project (www.horde.org)
[email protected]

"Time just hates me. That's why it made me an adult." - Josh Joplin

--
ansel mailing list - Join the hunt: http://horde.org/bounties/#ansel
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: [email protected]

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQBIxTkqTW0K6bINYV4RAtDdAKDKKsUUXfX5X7BpCMJlRhainO0pAACggRtj
ry6W8yN8KGcNQOhazF24948=
=SAng
-----END PGP SIGNATURE-----