{#} Replies are directed back to [EMAIL PROTECTED]
{#} To reply to the author, write to David Remahl <[EMAIL PROTECTED]>
Hi again!
As I have not followed the Fire project very closely in the past, I have a
qeuestion about what your strategy is with plugins. The reason I ask, is
that I find the recently added file importing functions a bit misplaced. I
think that importing ICQ lists, should be placed in the ICQ service bundle,
ie through an update of the Service protocol. That would help us later
if/when we decide to make it up to the user which plugins are used (there
are 1 or two feature requests at sourceforge for this, I noticed). This is
what I propose:
- (NSArray)importFormats;
Would return an array of for example dictionaries representing the different
formats (for example a dictionary with one key for a unique format string,
and one for the display name that the app will use in the menuitem).
Upon the selection of one of those items that the application generated for
the particular service/format, it would call the following:
- (NSArray*)importBuddiesFromFormat:(NSString)uniqueFormatString;
That would leave it up to the plugin to take appropriate action, for example
to present a file-selection dialog, or connect to a database, or whatever it
chooses. It would then either return an array of BuddyItem's representing
the imported ppl. Alternatively, by some convention, it would return nil, to
signal that it wants to postpone the final stage of the importion, and then
call some agreed-upon method in a delegate of some kind.
This is not the only place where the core application could be further
slimmed, delegating responibility to the independent bundles.
Is this the direction you entend the project to go, or is there no intention
to get an architecture where the user selects services relevant to him/her?
/ David
{#} ----------------------------------------------------+[ fire ]+---
