Magic-Mirror/gecko-dev
1
0
Fork 0
mirror of https://github.com/mozilla/gecko-dev.git synced 2024-10-09 11:25:00 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

The first ContactMethod, namely Email.

Browse Source
This commit is contained in:
ian%hixie.ch 2001-09-19 18:56:05 +00:00
parent 703de85362
commit 49d7b16b9e
1 changed files with 55 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

55
webtools/PLIF/PLIF/Service/ContactMethod/Email.pm Normal file
View File

@ -0,0 +1,55 @@
# -*- Mode: perl; tab-width: 4; indent-tabs-mode: nil; -*-
#
# This file is MPL/GPL dual-licensed under the following terms:
#
# The contents of this file are subject to the Mozilla Public License
# Version 1.1 (the "License"); you may not use this file except in
# compliance with the License. You may obtain a copy of the License at
# http://www.mozilla.org/MPL/
#
# Software distributed under the License is distributed on an "AS IS"
# basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See
# the License for the specific language governing rights and
# limitations under the License.
#
# The Original Code is PLIF 1.0.
# The Initial Developer of the Original Code is Ian Hickson.
#
# Alternatively, the contents of this file may be used under the terms
# of the GNU General Public License Version 2 or later (the "GPL"), in
# which case the provisions of the GPL are applicable instead of those
# above. If you wish to allow use of your version of this file only
# under the terms of the GPL and not to allow others to use your
# version of this file under the MPL, indicate your decision by
# deleting the provisions above and replace them with the notice and
# other provisions required by the GPL. If you do not delete the
# provisions above, a recipient may use your version of this file
# under either the MPL or the GPL.
package PLIF::Service::ContactMethod::Email;
use strict;
use vars qw(@ISA);
use PLIF::Output::Generic::Email;
@ISA = qw(PLIF::Output::Generic::Email);
1;
# XXX This inherits from PLIFF::Output::Generic::Email, which is silly
# (or is it?). Should it instead be a pure service, but install the
# Email output service? Should this just be a part of the output
# service? (No, output services cannot be allowed to know about users
# as anything more than sessions.) Should this entire module just be
# done by the application registering the right contact methods?
sub provides {
my $class = shift;
my($service) = @_;
return ($service eq 'user.fieldRegisterer' or
$class->SUPER::provides($service));
}
# user.fieldRegisterer
sub register {
my $self = shift;
my($app, $fieldFactory) = @_;
$fieldFactory->registerField($app, 'contact', 'email', 'string');
}