Abstract:
A method for a computer user to share photos electronically begins when the user identifies one or more photos that are stored on a computer as files. Files for each identified photo are uploaded from the computer to a webspace that is controlled by the user. HTML code is generated for an email message to be used for sharing the photos from the user to a recipient of the email message. The HTML code includes a source path instruction for each identified photo as it is stored on the webspace. Due to the source path instruction, the identified photos are not attached to the email message itself. This enables the email message to be of a small, manageable size. The email recipient may read the email message and may access the identified photos using standard email and browser software.

Description:
CROSS-REFERENCE TO RELATED APPLICATION  
       [0001]    This application claims the benefit of U.S. Provisional Application No. 60/467,775 filed May 2, 2003, the contents of which are incorporated by reference. 
     
    
     
       BACKGROUND OF THE INVENTION  
         [0002]    E-mail is a great means of communicating for business, family and friends. As digital cameras are undergoing phenomenal sales growth, sharing digital images through e-mail has become part of our culture. The downside is picture preparation—it is time consuming and tedious. To make matters worse, e-mail applications are closing the door on attachments due to virus concerns.  
           [0003]    Today&#39;s digital cameras provide crystal clear images at the expense of large file sizes. If you have attempted to share one of these images, you most likely found this task nearly impossible. These large images tend to overload e-mail server space as well as your Internet connection due to limited bandwidth.  
           [0004]    The two methods currently used for sharing photos from a PC are as attachments to an email message or by using one of many online photo sharing services. Both of these suffer from several deficiencies, some of which are listed below:  
           [0005]    Attachments  
           [0006]    (1) Email servers were designed to provide text messaging between large numbers of people and not to transfer large attachments. The demands on an email system include indexing, reply, storage and other options that may be available to the subscriber, many times surpassing the demands placed on hosted webservers. A text message file may only be 5 kb and pass through the process of management and delivery efficiently, being forwarded to the recipient&#39;s email server via a manageable number of IP packets where upon request by the recipient is quickly downloaded to his desktop or other device. However an attachment requires large amounts of space by comparison. Thus, a huge number of IP packets are required and the operation must be completed before a time-out, while in addition the file size must not exceed the file size restrictions, this is many times confused with email storage space of which is also unknown by the sender and can be exceeded very easily, other failures are deprived from the fact that Email servers overload and fail when email queues hit peaks.  
           [0007]    (2) Attachments, especially those from new mega-pixel cameras, can be large in file size and cause Internet connection failures or deliberate disconnects from ISP&#39;s  
           [0008]    (3) Attachment file names are the only way to define meaning or association within the message  
           [0009]    (4) A high speed Internet connection does not provide resolution to email failure. It only returns the failure faster, Internet connection speed is independent of the recipients email server.  
           [0010]    (5) Attachments require an additional software application to enable preview. This taxes the PC, requiring more memory as well as additional screen space.  
           [0011]    (6) When attachments are opened on a recipient&#39;s machine, they lose their association to the message.  
           [0012]    (7) When forwarding or responding to a message with an attachment the attachment must be uploaded and downloaded through the email server subjecting the sender and recipient to the problematic issues defined above.  
           [0013]    (8) Attachments require time consuming preparation.  
           [0014]    (9) Attachments in email are being eliminated, email services are restricting size and applications like Microsoft Outlook have already banned 30 file attachment types.  
           [0015]    (10) Attachments carry viruses and can cause damage to a users machine or email server when opened.  
           [0016]    (11) Recipients are reluctant to open attachments  
           [0017]    Online Photo Sharing Services  
           [0018]    (1) Online photo sharing services limit the size and clarity of photo preview and in many cases place text on the photo to prevent a viewer from downloading and printing, Photo Sharing services are in the business to sell printed photos, allowing large photos for preview would eliminate profit.  
           [0019]    (2) While those that advertise the ability to share in email, they only provide a link in the email to their website.  
           [0020]    (3) The people you want to share photos with must join most photo sharing services, providing email addresses or additional personal information  
           [0021]    (4) In order to preview photos on a online photo sharing site viewers are subjected to advertising and popups  
           [0022]    (5) While uploading, if you lose the connection, you must manually reconnect and discern between the photos sent and not sent  
           [0023]    (6) You do not have the ability to collaborate with photos and text between parties  
           [0024]    (7) You must point your browser to an online address and use a user name and password to enable preview  
         SUMMARY OF THE INVENTION  
         [0025]    In one aspect of the present invention, a method for a computer user to share photos electronically begins when the user identifies one or more photos that are stored on a computer as files. Files for each identified photo are uploaded from the computer to a webspace that is controlled by the user. HTML code is generated for an email message to be used for sharing the photos from the user to a recipient of the email message. The HTML code includes a source path instruction for each identified photo as it is stored on the webspace. Due to the source path instruction, the identified photos are not attached to the email message itself. This enables the size of the email message to be small since the message does not include any jpg files, but rather only HTML tags and the text of the message. The email recipient may read the email message and may access the identified photos using standard email and browser software. 
       
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0026]    [0026]FIG. 1 is a flowchart illustrating the general steps of the invention. 
     
    
     DETAILED DESCRIPTION OF THE INVENTION  
       [0027]    [0027]FIG. 1 shows the general steps of one embodiment of the present invention. In this embodiment, the process begins with step  110 , where a computer user may identify one or more photos that the user wants to share via email. These identified photos are uploaded to the user&#39;s webspace at step  120  and HTML is generated at step  130  for an new email message. This HTML includes source path information for each photo stored on the webspace. At steps  140 , the email message is sent to one or more recipients. The recipient may use his/her usual email software to read the email (step  150 ). By clicking on links in the email message, the user may use his/her usual browser software to view the photos.  
         [0028]    These five general steps of the present invention will now be discussed in more detail.  
         [0029]    Identify Photos (Step  110 )  
         [0030]    In one embodiment of the invention, photos are identified (step  110 ) for insertion into the application through Windows XP&#39;s auto load process which uses the operating system to identify an application (such as a software product sold by Applicant, referred here as an “icu software product”) or through menu options that provide a form for photo selections, in either case selected photos are rewritten to provide stamps that appear in a photo viewer, while the original content is saved for content mining at a later point in time.  
         [0031]    After the photos are loaded into the viewer they may be all or individually targeted for email using a single click on select photos or by using the menu action “select all”.  
         [0032]    After selections are made from the viewer, selecting the menu option “Email” opens the film strip form that displays the photo selections for reconsideration&#39;s.  
         [0033]    Upload Photos (Step  120 )  
         [0034]    The upload process (step  120 ) will now be elaborated on by discussing a series of steps taken by one embodiment of the invention, and by referring to portions of relevant source code from U.S. Provisional Application No. 60/467,775.  
         [0035]    Step 1: Selected photos for email are sized and compressed according to preset or default settings. (See module mod 1 _Preparelmages in the provisional application)  
         [0036]    Step 2: If the user has decided to include a copyright, the photos are written when sized and compressed to include such. (See frm_SYS_Properties/C:Copyrite)  
         [0037]    Step 3: The connection type and status is checked using Inet, this is a windows operating service. (See frm_SYS_Properties/H:Connection State Info)  
         [0038]    Step 4: A website is pinged to ensure an Internet connection is established, if one is not the user is prompted to connect. (See frm_Ping_Hidden)  
         [0039]    Step 5: A page (Store_Tableset.htm) is downloaded from icu software that provides marketing material and an insertion point named “@icufilm” for the html code that is to be generated. (See HTML 01 _BuildTableset)  
         [0040]    Step 6: A URL name is automatically defined or the user can define one for usage later in the process  
         [0041]    Step 7: The URL is written to the Store_Tableset whereas in the case of an email recipient does not have html enabled mail, the URL will be exposed to provide the recipient with a path to the online version. (See Function HTML_LinkText( ))  
         [0042]    Step 8: If the User has selected to expose the online version address to recipients, the URL is written to be exposed. (See Function HTML_AddHyperlink)  
         [0043]    Step 9: The user&#39;s preference to use password protection for photos and html stored on the web is checked, if true and enabled, Html is created for file paths in the email message that include the password and username in the URL paths, (See Function HTML_AddHyperlink)  
         [0044]    Step 10: If password protection is true but not enabled, the user is prompted to include in this session the prepared scripts that enable file locking with a unique username and password, if yes scripts are prepared and included in the temp folder for uploading automatically. (See frmSYS_Properties)  
         [0045]    Step 11: If the user has photo locking on, the password and username are included in the future visible email message.  
         [0046]    Step 12: Html is created for photo content that will display in the email message—where as a path to the URL not a link is written. (See Public Sub MailLinkPassword)  
         [0047]    Step 13: Html is written for links to additional pages that will display max, hotspot photos and the online version. (See mod 2 _PrepareHTM)  
         [0048]    Step 14: The above Html is combined and inserted onto the Store_Tableset page at a predefined insertion point. (See mod 2 _PrepareHTM)  
         [0049]    Step 15: Html is created for the display of photo content that is to be viewed through links outside of the email message, this includes hotspots, maximized previews and an email instance copy for website preview.  
         [0050]    Step 16: All files to be uploaded to the unique URL are placed into a local temp folder  
         [0051]    Step 17: A connection is made to the user&#39;s web space (See mod 3 _FTPFilesToServer)  
         [0052]    Step 18: If space is available, the temp folder files are uploaded via ftp to the new URL and deleted from the local temp folder one at a time.  
         [0053]    Step 19: A process form provides the user a view of the process. (See frmFTP_Proccessing)  
         [0054]    Step 20: If the connection is broken, a reconnection process prompts the user to reconnect and send using the automated reconnection process, if the user does not respond, the application reconnects automatically and continues to finish the upload automatically (See frmFTP_Reconnect)  
         [0055]    Step 21: The reconnection process ensures the Internet connection as well as the webspace connection providing successful uploads from portable devices that may be connected using a cell phone transmission tower or satellite, for example transmitting from a traveling plane, car boat or motorcycle.  
         [0056]    Step 22: When the upload process is completed, depending upon the user&#39;s preference, a new email message appears in the icu software application, Microsoft Outlook or is available for pasting into any other html email application like Microsoft Express (See Forms frm_Email &amp; frm_EmailExpress.)  
         [0057]    Generate HTML (Step  130 )  
         [0058]    The HTML generation process will now be elaborated on by discussing a series of steps taken by one embodiment of the invention, and by referring to portions of relevant source code from U.S. Provisional Application No. 60/467,775.  
         [0059]    Step 1: Selected photos for email are sized and compressed according to preset or default settings. (See Module mod 1 _Preparelmages.)  
         [0060]    Step 2: If the user has decided to include a copyright, the photos are written at the time they are sized and compressed to include such. (See Module modR_Routines.)  
         [0061]    Step 3: The connection type and status is checked using Inet, this is a windows operating service.  
         [0062]    Step 4: A website is pinged to ensure an Internet connection is established, if one is not the user is prompted to connect. (See Module modC_CNN.)  
         [0063]    Step 5: In the case where the user has selected to email The a web page called called “Store_Tableset” is returned to the users machine from the icu web server. In the case a user selects to preview, preview/print or save the entire instance to a file, a html page “Local_Tableset” is picked up from the users local files instead of the icu Web Server.  
         [0064]    Step 6: The page “Store_Tableset” provides marketing dependant upon the icu web servers database merchant value. A merchant Id is added to the online database in the case an alliance is made by icu software with an ISP or retailer, in that case the alliances marketing material is written into the Store_Tableset providing an impression for the sender and all recipients. An impression may include merchant information, links and other marketing info. The StoreTableset.htm html can be edited programmatically or manually online to include background effects, marketing and to provide the application with operating information.  
         [0065]    Step 7: The Store_Tableset page is scanned for details that can change the way the application processes or looks for the next Store_Tableset.htm URL (See Function UPDATE_REGISTRY.)  
         [0066]    Step 8: A URL name is automatically defined or the user can define one for usage later in the process (See Form frmlMG_Targeted.)  
         [0067]    Step 9: The URL is written to the Store_Tableset whereas in the case of an email recipient does not have html enabled mail, the URL will be exposed to provide the recipient with a path to the online version. (See Module Mod 2 _PrepareHTML.)  
         [0068]    Step 10: If the User has selected to expose the online version address to recipients, the URL is written to be exposed. (See Function HTML_AddHyperlink.)  
         [0069]    Step 11: The users preference to use password protection for photos and html stored on the web is checked, if true and enabled, Html is created for file paths in the email message that include the password and username in the URL paths, (See Public Sub MailLinkPassword)  
         [0070]    Step 12: If password protection is true but not enabled, the user is prompted to include in this session the prepared scripts that enable file locking with a unique username and password, if yes scripts are prepared and included in the temp folder for uploading automatically.  
         [0071]    Step 13: If the user has photo locking on, the password and username are included in the future visible email message.  
         [0072]    Step 14: Html is created for photo content that will display in the email message—where as a path to the URL not a link is written. (See mod 2 _PrepareHTML.)  
         [0073]    Step 15: Html is written for links to additional pages that will display max, hotspot photos and the online version.  
         [0074]    Step 16: The above Html is combined and inserted onto the Store_Tableset page at a predefined insertion point.  
         [0075]    Step 17: Html is created for the display of photo content that is to be viewed through links outside of the email message, this includes hotspots, maximized previews and an email instance copy for website preview.  
         [0076]    Step 18: All files to be uploaded to the unique URL are placed into a local temp folder  
         [0077]    Step 19: A connection is made to the users web space (See Module mod 3 _FTPFilesTo Server.)  
         [0078]    Step 20: If space is available, the temp folder files are uploaded via ftp to the new URL and deleted from the local temp folder one at a time.  
         [0079]    Step 21: A process form provides the user a view of the process.  
         [0080]    Step 22: If the connection is broken, a reconnection process prompts the user to reconnect and send using the automated reconnection process, if the user does not respond, the application reconnects automatically and continues to finish the upload automatically (See Form frmFTP_Reconnect.)  
         [0081]    Step 23: The reconnection process ensures the Internet connection as well as the webspace connection providing successful uploads from portable devices that may be connected using a cell phone transmission tower or satellite, for example transmitting from a traveling plane, car boat or motorcycle.  
         [0082]    Step 24: In the case of menu option, email, when the upload process is completed, depending upon the users preference, a new email message appears in the icu software application, Microsoft Outlook or is available for pasting into any other html email application like Microsoft Express. In the case of menu options—Preview, Print or Save—the new Store_Tableset page html points to local files for it&#39;s supporting files and opens in a Preview form or is saved to a location the user defines. (See Forms frmEmail &amp; frmEmailExpress)  
         [0083]    Send Email and Read (Steps  140  and  150 )  
         [0084]    In one embodiment of the invention, after the photos selections are sized and compressed and html is created and uploaded to a web space, an email message version is provided to the user within the built in email application, Microsoft Outlook or available on the clipboard for pasting into any html capable email application.  
         [0085]    The email message is html and displays the photos in the message body, the photos display due to the fact their coded paths point to the web unique web space where the supporting files have been uploaded, this provides an email message that is the size of the amount of text and html tags, regardless of the number of photos to be shared with the email message. This means that the email message is quite manageable by Outlook and other standard email viewing programs as the message is generally like most other email messages—it is made up of the user&#39;s text message along with some HTML to format the message and to show the linked photos. The small email file size is what provides the abilities to pass through email servers. The fact that the photos live on the server allows the user to share large photo file sizes created from the mega-pixel cameras used today.  
         [0086]    The email message also provides other selective options the user has included, such as Maximize buttons or hotspots on images, these links upon selection, open the senders or recipients default browser and open the path to the html located on the web that provides the photo that is also located on the web space.  
         [0087]    If the file protection is enabled at the time of email creation, the email message provides an image of a lock and the instances username and password that are required to open the link. The Internet Browser provides the user the forms for password entry and the user simply needs to look at the email message for the username and password that is included through automation. The photos that appear in the email message look at the locked folder that requires password and username, however the password and username is included in the photo path, providing the folder to be unlocked automatically so the photos can display without user interaction.  
         [0088]    If hotspots are created on photos prior to sending from within the Image Editor (See Form frmlMG_Editor and Module mode_Editor.), the photos selective content will also appear in the users browser. The selective content was deprived from the original photo at the time of the email instances creation and provides a maximized view of the subject material. (See Module mod 2 _PrepareHTML.)  
         [0089]    A sender can also send to a list of recipients using an address book within the icu mail application or other application of choice, the process allows any selection of recipients at one time without additional uploads. (See Form frmAddrBk.)  
         [0090]    A recipient upon receiving an email using this process is not subjected to extended waiting time, images are downloaded into the message from the webserver instead of a slow email server.  
         [0091]    A recipient may add comments to each photo and respond instantly without any upload because the message file size remains the weight of the text.  
         [0092]    The foregoing description addresses embodiments encompassing the principles of the present invention. The embodiments may be changed, modified and/or implemented using various types of arrangements. Those skilled in the art will readily recognize various modifications and changes that may be made to the invention without strictly following the exemplary embodiments and applications illustrated and described herein, and without departing from the scope of the invention, which is set forth in the following claims.