On Dec 13, 2007, at 10:46 AM, Morgen Sagen wrote:
On 12/13/07, Travis Vachon <[EMAIL PROTECTED]> wrote:
+1 +1 +1
Heck, I know enough Python + CMP that it's conceivable that Travis
Clause could drop this off over the holiday season.
Morgen: is there a bug in bugzilla for this?
You know, I looked through Bugzilla but couldn't find one. To really
do this would require adding a field to the accounts dialog for email
address (so that account activation email can work), and also fields
for first/last name on the account. All the new fields would need to
be added to the Chandler data model so they can be persisted in the
repository,
Would we really need to persist the name/email address in the desktop
client, or could this information only be available during the signup
process? Not saving it would allow us to avoid the issue you mention
below...
as well as to the export/reload model so that they can be
exported to .chex files. Next you'll need to make sure the HTTP
request happens on a background thread as to not block the UI, and add
UI affordances for showing progress as well as success/failure
explanations (server unreachable/account name in use/illegal account
name/etc).
Now if the user later changes their email address or first/last name
on either the client or server, do we keep those in sync? If so, we
need to do a CMP request or two whenever the account dialog is
displayed.
See above. Even if we do want to save this information in the ideal
solution to this problem, is this a potential simplification we could
make to expedite this feature?
Thanks! I'll file a bug once we nail down these details.
-Travis
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
