The present embodiment relates to email messages and in particular, a method for presenting an attachment in an email message of a portable electronic device.
It is becoming increasingly popular to send photographs, scanned documents, slide shows, PDF documents and other types of attachments in email messages. Each attachment is provided with a filename and is linked to an email message in a manner that is well known in the art. Often, a single email message may contain multiple attachments.
Attachments are generally opened when an email message first arrives and subsequently stored along with the message in a recipient's inbox. At a later time or date, the email message is typically re-opened by the recipient so that attachments may be filed, forwarded and/or deleted, for example. It is unlikely that the recipient will recall the contents of every attachment and since the character length of attachment filenames is limited, it is not always easy to determine the contents of an attachment from its filename. Therefore, it is often necessary for the recipient to re-open every attachment in order to determine its contents. This process can be very time consuming, particularly in the case where an email recipient is searching for a specific attachment.
The embodiment will be better understood with reference to the following Figures in which like numerals denote like parts and in which:
a is screen shot of the portable electronic device of
b is another screen shot of the portable electronic device of
Referring to
It will be appreciated that the portable electronic device 12 is movable within the coverage area and can be moved to coverage areas defined by other base stations. Further, as will be understood by one of ordinary skill in the art, wireless networks include GSM/GPRS, CDPD, TDMA, iDEN Mobitex, DataTAC networks, EDGE or UMTS and broadband networks such as Bluetooth and variants of 802.11.
A server 18 handles wireless client requests from the portable electronic device 12. A firewall, or proxy server, 16, is provided between the server 18 and the Internet 14. The server 18 further operates as an attachment server. The attachment server communicates with an email client and an attachment viewer to allow a user to view files that are received in email messages. The attachment server may alternatively be a separate server.
Referring now to
The portable electronic device 12 is based on a microcomputer including a processor 20 connected to a read-only-memory (ROM) 22 that contains a plurality of applications executable by the processor 20 that enables each portable electronic device 12 to perform certain functions including, for example, PIN message functions, SMS message functions and cellular telephone functions. The processor 20 is also connected to a random access memory unit (RAM) 24 and a persistent storage device 26 which are responsible for various non-volatile storage functions of the portable electronic device 12. The processor 20 receives input from various input devices including a keypad 28. The processor 20 outputs to various output devices including an LCD display 30. A microphone 32 and phone speaker 34 are connected to the processor 20 for cellular telephone functions. The processor 20 is also connected to a modem and radio device 36. The modem and radio device 36 is used to connect to wireless networks and transmit and receive voice and data communications through an antenna 38. A content store 40, which is generally a file storage system for the portable electronic device 12, is also provided. The content store 40 stores email message attachments locally on the portable electronic device 12 after the attachments have been viewed using the attachment viewer.
Referring now to
As shown in
Request/view functionality for an attachment is provided by the attachment viewer and the attachment server. The attachment viewer, which is an application that is run by the processor 20 of the portable electronic device 12, displays images that correspond to attachments. Referring to
Referring also to
The attachment server supports both image and non-image formats. Images, which have file formats such as JPEG, GIF, BMP, PNG and TIFF, for example, are converted directly to JPEG files at the attachment server, encapsulated in UCS data and returned to the attachment viewer, where the images are displayed in JPEG format.
Non-image file formats, such as Microsoft PowerPoint™ PPT, for example, are rendered in order to produce a bitmap file at the attachment server. In the case of a PPT file, for example, an empty bitmap is created in memory and then an image representation of a first slide, or cover page, as it would appear on a normal desktop computer, is stored therein. The off screen bitmap is also referred to as a memory bitmap since the image is not actually viewed by a user but produced at the attachment server. Once produced, the bitmaps are converted to JPEG format, encapsulated in UCS data and returned to the attachment viewer, where the images are displayed in JPEG format. Any non-image file format may be rendered. Types of renderable formats include: Microsoft Office™ formats including PowerPoint™, Word™ and Excel™, as well as other formats, such as WordPerfect™, Adobe Acrobat™ and Corel™, for example. The rendering process is disclosed in co-pending U.S. patent application Ser. No. 11/395,798 filed on even date herewith entitled “Method for viewing non-image attachments on a portable electronic device”, which is herein incorporated by reference.
The attachment server further resizes the images before the JPEG images are encapsulated into UCS data and sent to the attachment viewer. By performing the re-size operation on the attachment server, bandwidth and portable electronic device 12 memory usage are minimized. The attachments are re-sized from their original width and height to fit the display 30 of the portable electronic device 12. During the re-size operation, the aspect ratio is maintained as follows. If the width and height of the original image exceeds the width and height of the display 30 of the portable electronic device 12, the image is re-sized to match the display 30. For example, a scanned TIFF attachment having a resolution of approximately 1700×2100 pixels is re-sized to fit on the display 30, which has approximately 240×160 pixels. In this example, the image height is greater than the image width, therefore, the height is selected as the base dimension for scaling and the aspect ratio of the original image is maintained so that the content of the resulting image is smaller than the display 30.
If the width and height of the original image is less than or equal to the width and height of the portable electronic device display 30, no re-size operation is performed. If the width of the original image exceeds the width of display 30 and the height of the original image is less than or equal to the height of the display 30, then the original image is re-sized to the width of the display 30 and the height of the original image is adjusted according to the image aspect ratio. Finally, if the height of the original image exceeds the height of display 30 and the width of the original image is less than or equal to the width of the display 30, then the original image is re-sized to the height of the display 30 and the width of the original image is adjusted according to the image aspect ratio.
Referring to
As shown, at step 74, the user opens an email message having at least one attachment. For each attachment, the messaging application notifies the attachment viewer client, as indicated at step 76. The attachment viewer receives the notification to update an attachment portion 45, or display field, of the message body 44 in which each attachment is presented, as indicated at step 80. At step 82, the attachment viewer determines if the attachment has been previously viewed. If the attachment has not been previously viewed, no image is returned to the messaging application and the messaging application displays the email message on the display 30 of the portable electronic device 12, as indicated at step 78.
If the attachment has been previously viewed, the attachment viewer then determines whether the attachment is an image and, if not, the attachment viewer determines whether the attachment is renderable, as indicated at step 84. The attachment viewer determines if an attachment is an image by checking the attachment type. If the attachment type is not an image, the attachment viewer then determines if the previously viewed attachment is renderable. The attachment viewer checks for renderable Document Object Model (DOM) identifiers inside a server descriptor, which is returned to the attachment viewer when the attachment is first opened and a DOM corresponding to the attachment is created. Graph based DOM structure is disclosed in U.S. Patent Application No. 2006/0055693, which is herein incorporated by reference. If no renderable DOM identifiers are found, the attachment viewer determines that the previously viewed attachment is not renderable and is therefore unable to return an image to the messaging application. The messaging application then displays the email message, as indicated at step 78.
If the attachment has been previously viewed and is an image or is renderable, the attachment viewer retrieves the image from the content store 40 of the portable electronic device 12 at step 86. At step 88, the image is resized to 25% of its size and then the image is added to the display field below the attachment filename 46, as indicated at step 90. The email message is then displayed to the user of the portable electronic device 12, as indicated at step 78.
The size of the thumbnail 48 varies for different attachments since the size of each image that is returned from the attachment server and saved in the content store 40 varies based on the aspect ratio of the original image. It will therefore be appreciated by a person skilled in the art that the thumbnail 48 is not limited to being resized to 25%. The thumbnail 48 may be resized to occupy between 15% and 40% of the display 30 or alternatively may be of any size that allows the user to quickly determine the contents of the attachment.
In operation, the user receives an email message through the messaging application of the portable electronic device 12 and opens the email message, which has a similar format to the email message that is shown in
A specific embodiment of the present embodiment has been shown and described herein. However, modifications and variations may occur to those skilled in the art. For example, although the portable electronic device 12 has been described having cellular telephone capabilities, the described embodiment is not limited to portable electronic devices having both cellular telephone and email capabilities. A portable electronic device having email capabilities but not cellular telephone capabilities may also be used. All such modifications and variations are believed to be within the sphere and scope of the present embodiment.
Number | Name | Date | Kind |
---|---|---|---|
5903723 | Beck et al. | May 1999 | A |
6360252 | Rudy et al. | Mar 2002 | B1 |
6915333 | Delia et al. | Jul 2005 | B2 |
7242493 | Hall et al. | Jul 2007 | B2 |
7359947 | Kelley et al. | Apr 2008 | B2 |
7511723 | Sylthe | Mar 2009 | B2 |
7536440 | Budd et al. | May 2009 | B2 |
7606837 | Shields et al. | Oct 2009 | B2 |
7812852 | Sylthe | Oct 2010 | B2 |
8108404 | Sylthe et al. | Jan 2012 | B2 |
20010025307 | Venkatraman et al. | Sep 2001 | A1 |
20010051007 | Teshima | Dec 2001 | A1 |
20020016818 | Kirani et al. | Feb 2002 | A1 |
20020062396 | Kakei et al. | May 2002 | A1 |
20020137544 | Myojo | Sep 2002 | A1 |
20020161796 | Sylthe | Oct 2002 | A1 |
20030177444 | Sunata | Sep 2003 | A1 |
20040073873 | Croney et al. | Apr 2004 | A1 |
20040172453 | De Mendonca et al. | Sep 2004 | A1 |
20040183817 | Kaasila | Sep 2004 | A1 |
20040184072 | Jacobsen et al. | Sep 2004 | A1 |
20040229656 | Takahashi et al. | Nov 2004 | A1 |
20040246523 | Moriwaki | Dec 2004 | A1 |
20050193074 | Garland | Sep 2005 | A1 |
20050231648 | Kitamura et al. | Oct 2005 | A1 |
20050232581 | Karasawa | Oct 2005 | A1 |
20050234864 | Shapiro | Oct 2005 | A1 |
20060031336 | Friedman et al. | Feb 2006 | A1 |
20060033809 | Farley | Feb 2006 | A1 |
20060055693 | Sylthe et al. | Mar 2006 | A1 |
20060056604 | Sylthe et al. | Mar 2006 | A1 |
20060156240 | Lemay et al. | Jul 2006 | A1 |
20060225001 | Sylthe et al. | Oct 2006 | A1 |
20060268100 | Karukka et al. | Nov 2006 | A1 |
20070011258 | Khoo | Jan 2007 | A1 |
20080028335 | Rohrabaugh et al. | Jan 2008 | A1 |
20080102887 | Sylthe et al. | May 2008 | A1 |
20080307455 | Praest | Dec 2008 | A1 |
20080309795 | Mitsuhashi et al. | Dec 2008 | A1 |
20080316225 | Sylthe et al. | Dec 2008 | A1 |
Number | Date | Country |
---|---|---|
1071029 | Jan 2001 | EP |
Entry |
---|
Yu Chen; Xing Xie; Wei-Ying Ma; Hong-Jiang Zhang; , “Adapting Web pages for small-screen devices,” Internet Computing, IEEE , vol. 9, No. 1, pp. 50-56, Jan.-Feb. 2005 [retrieved from IEEE database on Feb. 25, 2012]. |
Research in Motion; “Attachment Service”; Oct. 1, 2004; http://web.archive.org/web/20040807081104/www.blackberry.com/knowledgecenterpublic/livelink.exe/fetch/2000/7979/278390/Attachment—Service.pdf?nodeid=322231&vernum=0. |
Number | Date | Country | |
---|---|---|---|
20070233791 A1 | Oct 2007 | US |