text:
US9002380B2 - Proximity-based notifications in a mobile device - Google Patents
Proximity-based notifications in a mobile device Download PDF
Alessandro F. Sabatelli
Ronald K. Huang
2012-06-08 Application filed by Apple Inc filed Critical Apple Inc
2012-12-12 Assigned to APPLE INC. reassignment APPLE INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: HUANG, RONALD K., SABATELLI, ALESSANDRO F.
238000009963 fulling Methods 0 claims description 3
230000000875 corresponding Effects 0 claims 6
230000002093 peripheral Effects 0 description 8
230000001960 triggered Effects 0 description 2
239000000835 fiber Substances 0 description 1
H04W4/021—Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences
H04W4/206—
H04W4/20—Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
H04W4/21—Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel for social networking applications
Methods, program products, and systems for proximity-based notifications are described. A proximity-based notification system can receive a request to be notified when a contact's mobile device is in proximity to a user's mobile device, obtain permission to receive information associated with the contact, receive the information associated with the contact, detect that the contact's mobile device is in proximity to the user's mobile device based on the information associated with the contact, and notify the user that the contact's mobile device is in proximity to the user's mobile device.
This disclosure relates generally to proximity-based notifications in a mobile device.
A user can configure a mobile device to notify the user that a task needs to be performed or an event is going to happen. Each task or event can be associated with a date. As the date approaches, the device can provide a notification to the user, for example, by presenting an alert dialog box.
Methods, program products, and systems for proximity-based operations of a mobile device are disclosed. A user's mobile device can receive input specifying that a notification be presented when a contact's mobile device is in proximity to the user's mobile device. When the user's mobile device detects that the contact's mobile device is in proximity to the user's mobile device, the user's mobile device can present a notification to the user.
Proximity-based notifications can be implemented to achieve the following advantages. Compared to conventional notifications, proximity-based notifications can give a user more options when setting up a notification. For example, a user can set up a notification that is triggered when the user meets a contact, without specifying a date or a time for the notification.
The details of one or more implementations of proximity-based notifications are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages will become apparent from the description, the drawings, and the claims.
FIG. 1 is a diagram that provides an overview of an exemplary system for proximity-based notifications.
FIGS. 2-4 illustrate exemplary systems for determining proximity of mobile devices.
FIG. 5 illustrates an exemplary process for providing proximity-based notifications to a user of a mobile device.
FIG. 6 is a block diagram of an exemplary system architecture for implementing the features and operations of proximity-based notifications.
FIG. 7 is a block diagram of an exemplary implementation of a mobile device.
DETAILED DESCRIPTION Exemplary System for Proximity-Based Notifications
FIG. 1 is a diagram that provides an overview of an exemplary system 100 for proximity-based notifications. The system 100 can include a user's mobile device 102 and a contact's mobile device 104. The mobile device 102 or 104 can be, for example, handheld computers, personal digital assistants, cellular telephones, smart phones, enhanced general packet radio service (EGPRS) mobile phones, media players, navigation devices, or a combination of any two or more of these data processing devices or other data processing devices.
The mobile device 102 or 104 can communicate with one or more wired and/or wireless networks 110. For example, the mobile device 102 or 104 can communicate with a cellular network using a cellular tower transceiver 112. The cellular network can provide communication access to a wide area network (WAN) 114, such as the Internet, by use of a gateway (not shown). The mobile device 102 or 104 can receive and store network information, such as the cell ID of the cellular tower transceiver 112 (e.g., transceivers on GSM masts), associated with the cellular network.
Similarly, the mobile device 102 or 104 can communicate with an access point transceiver 118, such as an 802.11g wireless access device. The access point transceiver 118 can provide communication access to the wide area network 114. The mobile device 102 or 104 can receive and store network information, such as the access point transceiver ID of the access point transceiver 118 (e.g., a Media Access Control (MAC) address), associated with the access point.
The mobile device 102 or 104 may include circuitry and sensors for supporting a location determining capability, such as that provided by a Global Positioning System (GPS). In some implementations, a positioning system, such as a GPS receiver, can be integrated into the mobile device 102 or 104 to provide access to location information. The mobile device 102 or 104 can communicate with a GPS satellite 106 through the GPS receiver to determine its position, location, or geographic area.
The mobile device 102 or 104 can communicate with a proximity-based notification system 130 over the one or more wired and/or wireless networks 110. The proximity-based notification system 130 can provide user interfaces for configuring or presenting notifications to the user of the mobile device 102. The mobile device 102 or 104 can provide network information and/or location information to the proximity-based notification system 130. Although depicted as a separate entity, the proximity-based notification system 130 can, in some implementations, be part of the user's mobile device 102.
There are a variety of ways in which the proximity-based notification system 130 can facilitate the determination of proximity of mobile devices. In some implementations, the proximity-based notification system 130 can determine whether the contact's mobile device 104 is in proximity to the user's mobile device 102. In some implementations, the proximity-based notification system 130 can provide the contact's network and/or location information to the user's mobile device 102, and the user's mobile device 102 can use the contact's network and/or location information to determine whether the contact's mobile device 104 is in proximity to the user's mobile device 102.
The mobile devices 102 and 104 can establish direct communication with each other. For example, the mobile devices 102 and 104 can establish a peer-to-peer connection 120, such as a personal area network connection, by use of one or more communication subsystems, such as a Bluetooth communication device. The user's mobile device 102 can use the peer-to-peer connection 120 with the contact's mobile device 104 to determine that the contact's mobile device 104 is in proximity to the user's mobile device 102. Other communication protocols and topologies can also be implemented.
Exemplary Systems for Determining Proximity of Mobile Devices
FIGS. 2-4 illustrate exemplary systems for determining proximity of mobile devices. FIG. 2 illustrates a system 200 for determining proximity of mobile devices based on the mobile devices being connected to the same transceiver. FIG. 3 illustrates a system 300 for determining proximity of mobile devices based on the mobile devices establishing a connection directly with each other. FIG. 4 illustrates a system 400 for determining proximity of mobile devices based on the geographic locations of the mobile devices being within a "geo-fence" that is generated based on context of the user or the contact.
FIG. 2 illustrates a system 200 for determining proximity of mobile devices based on the mobile devices being connected to the same transceiver. In FIG. 2, the system 200 includes a user's mobile device 202, a contact's mobile device 204, and a transceiver 210. The transceiver 210 may be, for example, the cellular tower transceiver 112 or the access point transceiver 118 of FIG. 1. The transceiver 210 is associated with a communication range 250.
The user's mobile device 202 is within the communication range 250 of the transceiver 210 and is in communication with the transceiver 210. The user's mobile device 202 receives network information associated with the transceiver 210, such as a transceiver ID. The user's mobile device 202 provides the network information to a proximity-based notification system, and the proximity-based notification system stores a temporal identifier for the user or the user's mobile device and the network information.
Initially, the contact's mobile device 204 is located at location A and is in communication with a transceiver 230. Location A is outside the communication range 250 of the transceiver 210, and the contact's mobile device 204 is not in communication with transceiver 210. The contact's mobile device 204 receives network information associated with the transceiver 230. The contact's mobile device 204 provides the network information to the proximity-based notification system.
In response to receiving the network information associated with the contact's mobile device 204, the proximity-based notification system compares the network information associated with the contact's mobile device 204 with the network information associated with the user's mobile device 202 and determines that the network information associated with the contact's mobile device 204 does not match the network information associated with the user's mobile device 202. Based on this comparison, the proximity-based notification system determines that the contact's mobile device 204 is not in proximity to the user's mobile device 202.
When the contact's mobile device 204 moves to location B, the contact's mobile device 204 is within the communication range 250 of the transceiver 210 and establishes communication with the transceiver 210. The contact's mobile device 204 receives network information associated with the transceiver 210, such as a cell ID of a cellular tower transceiver (e.g., transceivers on GSM masts) associated with a cellular network or an access point transceiver ID of the access point transceiver (e.g., a Media Access Control (MAC) address) associated with an access point. The contact's mobile device 204 provides the network information to the proximity-based notification system.
In response to receiving the network information associated with contact's mobile device 204, the proximity-based notification system compares the network information associated with the contact's mobile device 204 with the network information associated with the user's mobile device 202 and determines that the network information associated with the contact's mobile device 204 matches the network information associated with the user's mobile device 202. Based on this comparison, the proximity-based notification system determines that the contact's mobile device 204 is in proximity to the user's mobile device 202.
FIG. 3 illustrates a system 300 for determining proximity of mobile devices based on the mobile devices establishing a connection directly with each other. In FIG. 3, the system 300 includes a user's mobile device 302 and a contact's mobile device 304. The mobile devices 302 and 304 can establish direct communication with each other. For example, the mobile devices 302 and 304 can establish a peer-to-peer connection 320, such as a personal area network connection, by use of one or more communication subsystems, such as a Bluetooth communication device. The user's mobile device 302 is associated with a direct communication range 350.
Initially, the contact's mobile device 304 is located at location A. Location A is outside the direct communication range 350 of the user's mobile device 302, and the user's mobile device 302 and the contact's mobile device 304 cannot establish a direct connection with each other. When the contact's mobile device 304 moves to location B, the contact's mobile device 304 is within the direct communication range 350 of the user's mobile device 302. The user's mobile device 302 discovers the presence of the contact's mobile device 304 within the direct communication range 350 and determines that the contact's mobile device 304 is in proximity to the user's mobile device 302. The user's mobile device 302 can measure the signal strength of the connection with the contact's mobile device 304 to determine a distance between the user and the contact.
FIG. 4 illustrates a system 400 for determining proximity of mobile devices based on the geographic locations of the mobile devices being within a geo-fence that is generated based on context of the user or the contact. A geo-fence may be a virtual perimeter for a real-world geographic area. A geo-fence may be dynamically generated around a current location of a user of a mobile device.
In FIG. 4, the system 400 includes a user's mobile device 402, a contact's mobile device 404, and a positioning system 406. The positioning system 406 can include, for example, satellite based positioning systems, such as GPS, cellular network positioning based on cellular tower IDs, WiFi positioning technology based on WiFi networks, or any other technology that can be used to provide the actual or estimated location of a mobile device.
The user's mobile device 402 determines its current geographic location by communicating with the positioning system 406. The user's mobile device 402 provides its current geographic location to the proximity-based notification system. The proximity-based notification system stores a temporal identifier for the user or the user's mobile device 402 and the user's current location. Based on the user's current location and other context information associated with the user, the proximity-based notification system generates a geo-fence 450 to include the user's current location and an area surrounding the user's current location. The proximity-based notification system may monitor the user's movements and changes in context, and adjust the geo-fence 450 based on the user's movements and changes in context.
Initially, the contact's mobile device 404 is located at location A. The contact's mobile device 404 determines its current geographic location by communicating with the positioning system 406. The contact's mobile device 404 provides its current geographic location to the proximity-based notification system.
In response to receiving the contact's current location, the proximity-based notification system determines that the contact's current location is not within the geo-fence 450. The proximity-based notification system may determine whether to adjust the geo-fence 450 to include the contact's current location based on context information associated with the contact or the user. In the scenario of FIG. 4, the user's mobile device 402 or the proximity-based notification system determines not to adjust the geo-fence 450 to include the contact's current location. The user's mobile device 402 or the proximity-based notification system determines that the contact's mobile device 404 is not in proximity to the user's mobile device 402.
As the contact's mobile device 404 moves from location A to location B, the contact's mobile device 404 may periodically provide an update of its current location to the proximity-based notification system. In some implementations, the proximity-based notification system determines that the contact's mobile device 404 is in proximity to the user's mobile device 402 when the proximity-based notification system detects that the contact's mobile device 404 has entered the geo-fence 450 based on the contact's updated location. In some implementations, the proximity-based notification system determines that the contact's mobile device 404 is in proximity to the user's mobile device 402 when the proximity-based notification system determines to adjust the geo-fence 450 to include the contact's updated location based on context information associated with the contact or the user.
The geo-fence 450 may be generated based on context of the user or the contact or both. The geo-fence 450 can be dynamically adjusted according to changes in the context of the user or the contact or both. The geo-fence 450 can be generated, stored, and modified by the proximity-based notification system.
Context of an individual can include any conditions or circumstances associated with the individual. The individual's mobile device may provide information associated with the context to the proximity-based notification system to facilitate creation and modification of a geo-fence. Information associated with the context can include device or network related information, such as the individual's device or network configuration, capabilities, or status. The information can include location related information, such as the individual's current location, population density associated with the user's current location, property boundaries associated with the user's current location, or the distance between the individual's current location and another location. The information can include travel related information, such as the individual's direction of travel, speed of travel, travel destination, or available travel routes between the individual's location and another location. In general, the context information can include any information related to the conditions or circumstances associated with the individual.
The proximity-based notification system may analyze the context information of the user to generate or modify the geo-fence around the user. For example, the geo-fence may include a smaller area around the user when the user is at a location associated with a high population density and a larger area around the user when the user is at a location associated with a low population density. Similarly, the geo-fence may include smaller area when the user is moving at a slow speed, e.g., a speed indicative of walking, and a larger area when the user is moving at a fast speed, e.g., the speed of a moving car. As another example, the geo-fence may lie along property boundaries if the user is located on or in a property with boundaries, such as a building, an amusement park, a shopping center, an airport, etc. Similarly, the geo-fence may lie along metropolitan area boundaries, such as a neighborhood boundary, a community boundary, a city boundary, a county boundary, or a state boundary. As yet another example, the geo-fence may include an area along and near the user's travel route.
The proximity-based notification system may analyze the context information of the user and the contact to generate or modify the geo-fence around the user. For example, the proximity-based notification system may monitor the movements and context of the user and the contact over a period of time. Based on the movement and context information, the proximity-based notification service may determine that the user and the contact reside within five miles of each other. The proximity-based notification system may adjust the geo-fence as the user moves around the area near his home so as to not include the contact's home.
As another example, the proximity-based notification system may determine the available routes and distance between the user and the contact based on the user's and the contact's current locations. If the available routes and the distance are such that the user and the contact could meet within a certain period of time, the proximity-based notification system may generate or adjust the geo-fence to include the contact's current location and determine that the contact is in proximity to the user.
Exemplary Process for Providing Proximity-Based Notifications
FIG. 5 illustrates an exemplary process 500 for providing proximity-based notifications to a user of a mobile device. Process 500 can be performed by a proximity-based notification system, e.g., the proximity-based notification system 130 in FIG. 1, that is incorporated into a system having the architecture described in reference to FIG. 6 or a user device having the architecture described in reference to FIG. 7.
The proximity-based notification system can receive a request to notify a user when a contact's mobile device is in proximity to the user's mobile device (502). The request may be in the form of an input by the user specifying that a notification be presented when the contact is in proximity to the user. The request may be received from an application. For example, the user may create a task using a calendar application and configure the task to be triggered by the proximity-based notification system detecting that the contact is in proximity to the user. As another example, the user may record a reminder using a voice recorder application and configure the reminder to be played back to the user when the proximity-based notification system detects that the contact is in proximity to the user.
In some implementations, the proximity-based notification system can request and obtain permission from the contact to monitor the contact's context and location, and the contact's mobile device network connections (504). To request permission, the proximity-based notification system may cause the contact's mobile device to present a prompt or message to the contact. The message may indicate that a user is requesting to be notified when the contact is near the user and may include the identity of the user. The message may provide selections for the contact to configure what type of information, e.g., context, location, or network information, to share with the proximity-based notification system. The message can provide selections for the contact to give permission or not give permission to the proximity-based notification system to monitor the contact's activities.
The proximity-based notification system can receive information associated with the user (506) and information associated with the contact (508). The information can include context information, location information, or network information. In some implementations, a mobile device may constantly provide the information to the proximity-based notification service while the device is running a proximity-based notification application. In some implementations, a mobile device may push the information to the proximity-based notification system when the device detects a significant event, such as a user logging into a proximity-based notification application, a user entering or exiting an area covered by a transceiver, a user changing a travel route, etc. In some implementations, the proximity-based notification system may periodically pull the information from a mobile device at predetermined time intervals, e.g., thirty seconds, one second, one minute, etc.
The proximity-based notification system can generate or adjust a geo-fence around the user based on the information (510). In some implementations, the geo-fence may include the area within the maximum communication range of a peer-to-peer communication subsystem, such as a Bluetooth communication device, in the user's mobile device. In some implementations, the geo-fence may include an area within the communication range of a transceiver that is in communication with the user's mobile device. In some implementations, the geo-fence may be generated or adjusted based on location and/or context information associated with the user. The proximity-based notification system can repeatedly receive information and adjust the geo-fence around the user based on the information.
The proximity-based notification system can detect that the contact is in proximity to the user (512). In some implementations, the proximity-based notification system determines that the contact is in proximity to the user when the user's mobile device detects the presence of the contact's mobile device through a direct connection, such as a Bluetooth connection. In some implementations, the proximity-based notification system determines that the contact is in proximity to the user when the user's mobile device and the contact's mobile device are connected to the same transceiver, e.g., a cellular tower transceiver or an access point transceiver. In some implementations, the proximity-based notification system determines that the contact is in proximity to the user when the contact's current location is within the geo-fence generated based on information received from the user's mobile device and the contact's mobile device.
In response to detecting that the contact is in proximity to the user, the proximity-based notification system provides a notification to the user (514). The notification may be, for example, an alert box dialog, an audio notification (e.g., a ringtone or a pre-recorded message), or a vibration alert. The notification may present a message to the user to notify the user that the contact is nearby. The notification may present a reminder to the user to perform a task when the user meets the contact.
The notification may include a map that displays the area within the geo-fence, the current location of the user, and the current location of the contact. The map may adjust to the area defined by the geo-fence as the geo-fence is generated or modified. The map may include an indicator indicating a travel route from the user to the contact. The travel route can be indicated, for example, by a line from the user to the contact.
Exemplary System Architecture
FIG. 6 is a block diagram of an exemplary system architecture 600 for implementing the features and operations of proximity-based notifications. Other architectures are possible, including architectures with more or fewer components. In some implementations, architecture 600 includes one or more processors 602 (e.g., dual-core Intel® Xeon® Processors), one or more output devices 604 (e.g., LCD), one or more network interfaces 606, one or more input devices 608 (e.g., mouse, keyboard, touch-sensitive display) and one or more computer-readable media 612 (e.g., RAM, ROM, SDRAM, hard disk, optical disk, flash memory, etc.). These components can exchange communications and data over one or more communication channels 610 (e.g., buses), which can utilize various hardware and software for facilitating the transfer of data and control signals between components.
The term "computer-readable medium" refers to any medium that participates in providing instructions to processor 602 for execution, including without limitation, non-volatile media (e.g., optical or magnetic disks), volatile media (e.g., memory) and transmission media. Transmission media includes, without limitation, coaxial cables, copper wire and fiber optics.
Computer-readable medium 612 can further include operating system 614 (e.g., Mac OS® server, Windows® NT server), network communications module 616, and proximity-based notification module 620. Proximity-based notification module 620 can be programmed to receive an input for a proximity-based notification. Operating system 614 can be multi-user, multiprocessing, multitasking, multithreading, real time, etc. Operating system 614 performs basic tasks, including but not limited to recognizing input from and providing output to devices, keeping track and managing files and directories on computer-readable media 612 (e.g., memory or a storage device), controlling peripheral devices, and managing traffic on the one or more communication channels 610. Network communications module 616 includes various components for establishing and maintaining network connections (e.g., software for implementing communication protocols, such as TCP/IP, HTTP, etc.). Computer-readable medium 612 can further include a database interface. The database interface can include interfaces to one or more databases on a file system. The databases can be organized under a hierarchical folder structure, the folders mapping to directories in the file system.
Architecture 600 can be included in any device capable of hosting a database application program. Architecture 600 can be implemented in a parallel processing or peer-to-peer infrastructure or on a single device with one or more processors. Software can include multiple software components or can be a single body of code.
The described features can be implemented advantageously in one or more computer programs that are executable on a programmable system including at least one programmable processor coupled to receive data and instructions from, and to transmit data and instructions to, a data storage system, at least one input device, and at least one output device. A computer program is a set of instructions that can be used, directly or indirectly, in a computer to perform a certain activity or bring about a certain result. A computer program can be written in any form of programming language (e.g., Objective-C, Java), including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, a browser-based web application, or other unit suitable for use in a computing environment.
Suitable processors for the execution of a program of instructions include, by way of example, both general and special purpose microprocessors, and the sole processor or one of multiple processors or cores, of any kind of computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor for executing instructions and one or more memories for storing instructions and data. Generally, a computer will also include, or be operatively coupled to communicate with, one or more mass storage devices for storing data files; such devices include magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and optical disks. Storage devices suitable for tangibly embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, such as EPROM, EEPROM, and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, ASICs (application-specific integrated circuits).
To provide for interaction with a user, the features can be implemented on a computer having a display device such as a CRT (cathode ray tube) or LCD (liquid crystal display) monitor for displaying information to the user and a keyboard and a pointing device such as a mouse or a trackball by which the user can provide input to the computer.
The features can be implemented in a computer system that includes a back-end component, such as a data server, or that includes a middleware component, such as an application server or an Internet server, or that includes a front-end component, such as a client computer having a graphical user interface or an Internet browser, or any combination of them. The components of the system can be connected by any form or medium of digital data communication such as a communication network. Examples of communication networks include, e.g., a LAN, a WAN, and the computers and networks forming the Internet.
The computer system can include clients and servers. A client and server are generally remote from each other and typically interact through a network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
Exemplary Mobile Device Architecture
FIG. 7 is a block diagram 700 of an exemplary implementation of a mobile device. A mobile device can include memory interface 702, one or more data processors, image processors and/or processors 704, and peripherals interface 706. Memory interface 702, one or more processors 704 and/or peripherals interface 706 can be separate components or can be integrated in one or more integrated circuits. Processors 704 can include one or more application processors (APs) and one or more baseband processors (BPs). The application processors and baseband processors can be integrated in one single process chip. The various components in a mobile device, for example, can be coupled by one or more communication buses or signal lines.
Sensors, devices, and subsystems can be coupled to peripherals interface 706 to facilitate multiple functionalities. For example, motion sensor 710, light sensor 712, and proximity sensor 714 can be coupled to peripherals interface 706 to facilitate orientation, lighting, and proximity functions of the mobile device. Location processor 715 (e.g., GPS receiver) can be connected to peripherals interface 706 to provide geopositioning. Electronic magnetometer 716 (e.g., an integrated circuit chip) can also be connected to peripherals interface 706 to provide data that can be used to determine the direction of magnetic North. Thus, electronic magnetometer 716 can be used as an electronic compass. Motion sensor 710 can include one or more accelerometers configured to determine change of speed and direction of movement of the mobile device. Gravimeter 717 can include one or more devices connected to peripherals interface 706 and configured to measure a local gravitational field of Earth.
Camera subsystem 720 and an optical sensor 722, e.g., a charged coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) optical sensor, can be utilized to facilitate camera functions, such as recording photographs and video clips.
Communication functions can be facilitated through one or more wireless communication subsystems 724, which can include radio frequency receivers and transmitters and/or optical (e.g., infrared) receivers and transmitters. The specific design and implementation of the communication subsystem 724 can depend on the communication network(s) over which a mobile device is intended to operate. For example, a mobile device can include communication subsystems 724 designed to operate over a CDMA system, a WiFi™ or WiMax™ network, and a Bluetooth™ network. In particular, the wireless communication subsystems 724 can include hosting protocols such that the mobile device can be configured as a base station for other wireless devices.
Audio subsystem 726 can be coupled to a speaker 728 and a microphone 730 to facilitate voice-enabled functions, such as voice recognition, voice replication, digital recording, and telephony functions.
I/O subsystem 740 can include touch surface controller 742 and/or other input controller(s) 744. Touch-surface controller 742 can be coupled to a touch surface 746 (e.g., touch screen or pad). Touch surface 746 and touch surface controller 742 can, for example, detect contact and movement or break thereof using any of a plurality of touch sensitivity technologies, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen 746.
Other input controller(s) 744 can be coupled to other input/control devices 748, such as one or more buttons, rocker switches, thumb-wheel, infrared port, USB port, and/or a pointer device such as a stylus. The one or more buttons (not shown) can include an up/down button for volume control of speaker 728 and/or microphone 730.
In one implementation, a pressing of the button for a first duration may disengage a lock of the touch surface 746 (e.g., a touch screen); and a pressing of the button for a second duration that is longer than the first duration may turn power to a mobile device on or off. The user may be able to customize a functionality of one or more of the buttons. The touch surface 746 can, for example, also be used to implement virtual or soft buttons and/or a keyboard.
In some implementations, a mobile device can present recorded audio and/or video files, such as MP3, AAC, and MPEG files. In some implementations, a mobile device can include the functionality of an MP3 player. A mobile device may, therefore, include a pin connector. Other input/output and control devices can also be used.
Memory interface 702 can be coupled to memory 750. Memory 750 can include high-speed random access memory and/or non-volatile memory, such as one or more magnetic disk storage devices, one or more optical storage devices, and/or flash memory (e.g., NAND, NOR). Memory 750 can store operating system 752, such as Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or an embedded operating system such as VxWorks. Operating system 752 may include instructions for handling basic system services and for performing hardware dependent tasks. In some implementations, operating system 752 can include a kernel (e.g., UNIX kernel).
Memory 750 may also store communication instructions 754 to facilitate communicating with one or more additional devices, one or more computers and/or one or more servers. Memory 750 may include graphical user interface instructions 756 to facilitate graphic user interface processing; sensor processing instructions 758 to facilitate sensor-related processing and functions; phone instructions 760 to facilitate phone-related processes and functions; electronic messaging instructions 762 to facilitate electronic-messaging related processes and functions; web browsing instructions 764 to facilitate web browsing-related processes and functions; media processing instructions 766 to facilitate media processing-related processes and functions; GPS/Navigation instructions 768 to facilitate GPS and navigation-related processes and instructions; camera instructions 770 to facilitate camera-related processes and functions; magnetometer data 772 and calibration instructions 774 to facilitate magnetometer calibration. The memory 750 may also store other software instructions (not shown), such as security instructions, web video instructions to facilitate web video-related processes and functions, and/or web-shopping instructions to facilitate web shopping-related processes and functions. In some implementations, the media processing instructions 766 are divided into audio processing instructions and video processing instructions to facilitate audio processing-related processes and functions and video processing-related processes and functions, respectively. An activation record and International Mobile Equipment Identity (IMEI) or similar hardware identifier can also be stored in memory 750. Memory 750 can include proximity-based notification instructions 776. Proximity-based notification instructions 776 can be a computer program product that is configured to cause the mobile device to perform operations of configuring or presenting proximity-based notifications.
Each of the above identified instructions and applications can correspond to a set of instructions for performing one or more functions described above. These instructions need not be implemented as separate software programs, procedures, or modules. Memory 750 can include additional instructions or fewer instructions. Furthermore, various functions of the mobile device may be implemented in hardware and/or in software, including in one or more signal processing and/or application specific integrated circuits.
A number of implementations of the invention have been described. Nevertheless, it will be understood that various modifications can be made without departing from the spirit and scope of the invention.
1. A computer-implemented method comprising:
receiving a request from a first mobile device to be notified when a contact's mobile device is in proximity to the first mobile device;
obtaining permission to receive information associated with the contact; receiving a first location corresponding to a current location of the first mobile device;
receiving a second location corresponding to a current location of the contact's mobile device;
estimating, based on the first location and the second location, an amount of time needed for the first mobile device to travel to a location of the contact's mobile device;
determining that the contact's mobile device is in proximity to the first mobile device, including: defining a gee-fence based on a current location of the first mobile device, a speed of travel associated with the current location of the first mobile device, a direction of travel associated with the current location of the first mobile device, a distance between the first mobile device and the contact's mobile device, and a travel route of the first mobile device, and detecting that the contact's mobile device is within the geo-fence when the amount of time is less than a threshold period of time; and
notifying the first mobile device that the contact's mobile device is in proximity to the first mobile device.
2. The method of claim 1, wherein the information associated with the contact comprises at least one of location information, device information, or context information.
3. The method of claim 1, comprising estimating, based on a distance between the first location and the second location, an amount of time needed for the first mobile device to travel to a location of the contact's mobile device based on available routes connecting the first mobile device to the contact's mobile device.
4. The method of claim 1, comprising estimating, based on a distance between the first location and the second location, an amount of time needed for the first mobile device to travel to a location of the contact's mobile device based on a distance between the first mobile device and the contact's mobile device.
5. The method of claim 1, wherein the proximity is based on a direction of travel of the contact's mobile device.
6. The method of claim 1, comprising estimating, based on a distance between the first location and the second location, an amount of time needed for the first mobile device to travel to a location of the contact's mobile device, wherein, detecting that the contact's mobile device is within the geo-fence comprises:
determining that the amount of time is less than a threshold period of time.
7. The method of claim 1, wherein defining the geo-fence based on the current location of the first mobile device comprises:
defining the geo-fence based on at least one of a population density associated with the current location of the first mobile device or property boundaries associated with the current location of the first mobile device current location.
8. The method of claim 6, wherein defining the geo-fence based on
the speed of travel associated with the current location of the first mobile device comprises determining that the speed is indicative of walking or of a moving car.
9. The method of claim 1, wherein notifying the first mobile device that the contact's mobile device is in proximity to the first mobile device comprises:
presenting a map that includes the first location and the second location.
10. The method of claim 1, wherein notifying the first mobile device that the contact's mobile device is in proximity to the first mobile device comprises:
presenting an indication of a travel route from the first location associated with the first mobile device to the second location associated with the contact's mobile device.
11. A non-transitory computer-readable medium storing instructions executable by a data processing device to perform operations comprising:
receiving a request to be notified when a contact's mobile device is in proximity to a first mobile device;
obtaining permission to receive information associated with the contact; receiving a first location corresponding to a current location of the first mobile device; receiving a second location corresponding to a current location of the contact's mobile device;
determining that the contact's mobile device is in proximity to the first mobile device including:
defining a geo-fence based on a current location of the first mobile device, a speed of travel associated with the current location of the first mobile device, a direction of travel associated with the current location of the first mobile device, a distance between the first mobile device and the contact's mobile device, and a travel route of the first mobile device, and detecting that the contact's mobile device is within the gee-fence; when the amount of time is less than a threshold period of time; and
providing a notification that the contact's mobile device is in proximity to the first mobile device.
12. The medium of claim 11, wherein the information associated with the contact comprises at least one of location information, device information, or context information.
13. The medium of claim 11, the operations comprising estimating, based on a distance between the first location and the second location, an amount of time needed for the first mobile device to travel to a location of the contact's mobile device.
14. The medium of claim 11, comprising estimating, based on a distance between the first location and the second location, an amount of time needed for the first mobile device to travel to a location of the contact's mobile device based on available routes connecting the first mobile device and the contact's mobile device.
15. The medium of claim 11, wherein the proximity is based on a direction of travel of the contact's mobile device.
16. The medium of claim 11, comprising estimating, based on a distance between the first location and the second location, an amount of time needed for the first mobile device to travel to a location of the contact's mobile device, wherein, detecting that the contact's mobile device is within the geo-fence comprises:
17. The medium of claim 11, wherein defining the geo-fence based on the current location of the first mobile device comprises:
18. The medium of claim 16, wherein defining the geo-fence based on
the speed of travel associated with the first mobile device comprises determining that the speed is indicative of walking or of a moving car.
19. The medium of claim 11, wherein providing the notification that the contact's mobile device is in proximity to the first mobile device comprises:
21. A system, comprising:
one or more computers; and
computer-readable medium coupled to the one or more computers having instructions stored thereon which, when executed by the one or more computers, cause the one or more computers to perform operations comprising:
estimating, based on the first location and the second location, an amount of time needed for the first mobile device to travel to a location of the contact'˜mobile device;
determining that the contact's mobile device is in proximity to the first mobile device, including:
defining a geo-fence based on a current location of the first mobile device, a speed of travel associated with the current location of the first mobile device, a direction of travel associated with the current location of the first mobile device, a distance between the first mobile device and the contact's mobile device, and a travel route of the first mobile device, and detecting that the contact's mobile device is within the geo-fence; when the amount time is than a threshold period of time; and
US13/492,759 2012-06-08 2012-06-08 Proximity-based notifications in a mobile device Active US9002380B2 (en)
US13/492,759 US9002380B2 (en) 2012-06-08 2012-06-08 Proximity-based notifications in a mobile device
PCT/US2013/044644 WO2013184990A1 (en) 2012-06-08 2013-06-07 Proximity-based notifications in a mobile device
US14/679,947 Continuation US9420420B2 (en) 2012-06-08 2015-04-06 Proximity-based notifications in a mobile device
US13/492,759 Active US9002380B2 (en) 2012-06-08 2012-06-08 Proximity-based notifications in a mobile device
US20140164420A1 (en) * 2012-12-11 2014-06-12 Melissa Data Corp. Systems and Methods for Clustered Matching of Records Using Geographic Proximity
US10044790B2 (en) * 2005-06-24 2018-08-07 Microsoft Technology Licensing, Llc Extending digital artifacts through an interactive surface to a mobile device and creating a communication channel between a mobile device and a second mobile device via the interactive surface
US20130311336A1 (en) * 2012-05-17 2013-11-21 Subbu Srinivasan Price negotiation from user device
US9800532B2 (en) * 2012-06-04 2017-10-24 International Business Machines Corporation Intelligent presentation of multiple proximate audible alerts
US9042827B2 (en) * 2012-11-19 2015-05-26 Lenovo (Singapore) Pte. Ltd. Modifying a function based on user proximity
US20140171116A1 (en) * 2012-12-14 2014-06-19 Anthony G. LaMarca Location-aware mobile application management
US9565526B2 (en) * 2013-02-25 2017-02-07 Dell Products L.P. System and method for dynamic geo-fencing
US10499192B2 (en) * 2013-03-14 2019-12-03 T-Mobile Usa, Inc. Proximity-based device selection for communication delivery
EP2973295A4 (en) * 2013-03-15 2016-11-16 Proximity Concepts Llc Systems and methods involving proximity, mapping, indexing, mobile, advertising and/or other features
US9462437B2 (en) * 2013-03-29 2016-10-04 Nokia Technologies Oy Method and apparatus for adjusting device functionalities based on location, movement, and/or noise
US9119201B2 (en) * 2013-05-02 2015-08-25 Nokia Technologies Oy Method and apparatus for signal strength based connection parameters adjustment
US9432807B2 (en) * 2013-05-23 2016-08-30 Honeywell International Inc. System and method with automatic radius crossing notification for global positioning system (GPS) tracker
US9730163B2 (en) * 2013-08-27 2017-08-08 Life360, Inc. Apparatus and method for conservation of battery power of mobile devices within a location-based group
CN103458365A (en) * 2013-09-09 2013-12-18 百度在线网络技术(北京)有限公司 Method and device for providing contacts based on geographic position
US20150087263A1 (en) * 2013-09-24 2015-03-26 Bennett Hill Branscomb Methods and Apparatus for Promotions and Large Scale Games in Geo-Fenced Venues
US10277536B1 (en) * 2014-03-25 2019-04-30 United Parcel Service Of America, Inc. Concepts for providing notifications for events of interest
US9918351B2 (en) 2014-04-01 2018-03-13 Belkin International Inc. Setup of multiple IOT networks devices
CA2896406C (en) 2014-07-08 2018-03-06 The Toronto-Dominion Bank Systems and methods for providing sensor-based location proximity detection and notification
US9426285B2 (en) * 2014-07-31 2016-08-23 Google Technology Holdings LLC Method and electronic device for individualizing ringtones
US9872240B2 (en) 2014-08-19 2018-01-16 Belkin International Inc. Network device source entity triggered device configuration setup
US9210192B1 (en) * 2014-09-08 2015-12-08 Belkin International Inc. Setup of multiple IOT devices
US9668121B2 (en) * 2014-09-30 2017-05-30 Apple Inc. Social reminders
US10231111B2 (en) * 2014-10-03 2019-03-12 Daniel Ursitti System and method for establishing a user connection
US9706519B2 (en) * 2014-10-03 2017-07-11 Daniel Ursitti System and method for establishing a user connection
US9326242B1 (en) * 2014-10-07 2016-04-26 Verizon Patent And Licensing Inc. Reducing power consumption on location reference devices
US10117166B2 (en) * 2014-10-29 2018-10-30 Blackberry Limited Application assisted band scanning method to reduce network acquisition time
US10154374B2 (en) * 2015-03-13 2018-12-11 Aircam Inc. Proximity-based geofenced universal URL
US10091317B2 (en) * 2015-03-13 2018-10-02 Aircam Inc. Proximity-based content sharing scheme
US9672725B2 (en) 2015-03-25 2017-06-06 Microsoft Technology Licensing, Llc Proximity-based reminders
EP3448755A2 (en) 2016-04-29 2019-03-06 United Parcel Service Of America, Inc. Unmanned aerial vehicle pick-up and delivery systems
US10514752B2 (en) * 2016-07-07 2019-12-24 Google Llc Methods and apparatus to determine objects to present in virtual reality environments
US9961493B1 (en) 2017-09-08 2018-05-01 Aircam Inc. Geofenced universal URL
WO2019143056A1 (en) * 2018-01-19 2019-07-25 Samsung Electronics Co., Ltd. Apparatus and method for determining calibration timing for blood pressure measurement in electronic device
US10440509B1 (en) * 2018-04-16 2019-10-08 Walgreen Co. Technology for managing location-based functionalities for electronic devices
US6618593B1 (en) * 2000-09-08 2003-09-09 Rovingradar, Inc. Location dependent user matching system
US20040198398A1 (en) * 2003-04-01 2004-10-07 International Business Machines Corporation System and method for detecting proximity between mobile device users
US20040198379A1 (en) * 2002-08-28 2004-10-07 Magee Stephen D. Method for authorizing location services
US20050130634A1 (en) * 2003-10-31 2005-06-16 Globespanvirata, Inc. Location awareness in wireless networks
US20060148532A1 (en) * 2003-10-30 2006-07-06 Schnurr Jeffrey R System and method of wireless proximity awareness
US20080182591A1 (en) * 2006-12-13 2008-07-31 Synthesis Studios, Inc. Mobile Proximity-Based Notifications
US20080318561A1 (en) * 2007-06-20 2008-12-25 Verizon Data Services, Inc. Apparatus, system and method for automated communication forwarding
US20090005040A1 (en) * 2004-02-09 2009-01-01 Proxpro, Inc. Method and computer system for matching mobile device users for business and social networking
US20090030999A1 (en) 2007-07-27 2009-01-29 Gatzke Alan D Contact Proximity Notification
WO2009101629A2 (en) 2008-02-13 2009-08-20 Ron Ishai A system and methods for positioning information from a plurality of users
US20100057481A1 (en) * 2008-08-28 2010-03-04 Gene Fein Real-time geo-location based contact service system
US20100203901A1 (en) * 2009-02-11 2010-08-12 Dinoff Robert K Location-Based Services Using Geofences Generated from Learned Patterns of Movement
US20100233999A1 (en) * 2009-03-13 2010-09-16 Telcordia Technologies, Inc. System and method for privacy-enabled mobile locator services with dynamic encounter horizon
US20110238755A1 (en) 2010-03-24 2011-09-29 Hameed Khan Proximity-based social networking
US20120008526A1 (en) * 2010-07-07 2012-01-12 Hooman Borghei Ad Hoc Formation and Tracking of Location-Sharing Groups
US20120088524A1 (en) 2010-10-06 2012-04-12 Connectquest System and method for facilitating interpersonal contacts and social and commercial networking
US20120252498A1 (en) * 2009-09-30 2012-10-04 Telecom Italia S.P.A. Method and system for notifying proximity of mobile communication terminals users
US20120281686A1 (en) * 2011-04-21 2012-11-08 Empire Technology Development Llc Locative social networking using a mobile device
US20120289254A1 (en) * 2011-05-11 2012-11-15 Microsoft Corporation Proximity-based task notification
US20120296984A1 (en) * 2011-05-19 2012-11-22 Research In Motion Limited Presenting instant messaging contacts listed by proximity to set location
US20130046602A1 (en) * 2011-08-17 2013-02-21 Bank Of America Corporation Method of providing an offer based on proximity to a point of sale transaction
US7289814B2 (en) 2003-04-01 2007-10-30 International Business Machines Corporation System and method for detecting proximity between mobile device users
International Search Report and Written Opinion of the International Searching Authority, PCT Application Serial No. PCT/US2013/044644, Sep. 27, 2013, 16 pp.
US9563677B2 (en) * 2012-12-11 2017-02-07 Melissa Data Corp. Systems and methods for clustered matching of records using geographic proximity
US9071701B2 (en) 2015-06-30 Using wireless characteristic to trigger generation of position fix
US7035647B2 (en) 2006-04-25 Efficient location determination for mobile units
JP5770933B2 (en) 2015-08-26 monitoring of geofence exit
EP2580924B1 (en) 2017-10-18 Pre-fetching information based on location
KR20090024835A (en) 2009-03-09 Geographical location information sharing among wireless devices
US9237421B2 (en) 2016-01-12 Method and apparatus for reducing transmission of location information
US20050012611A1 (en) 2005-01-20 Method of and service architecture for reminding a user subscribed to a communication network
JP5603432B2 (en) 2014-10-08 Determining the location of a mobile device using a location database
JP5722408B2 (en) 2015-05-20 Management of location database of positioning system based on network
KR101702800B1 (en) 2017-02-06 proximity fence
US9544721B2 (en) 2017-01-10 Address point data mining
US9596565B2 (en) 2017-03-14 Location monitoring feature of a mobile device for activating an application subsystem
KR101861345B1 (en) 2018-05-28 System and method for automatically posting user-location information to a social network
JP2014523665A (en) 2014-09-11 Selecting a wireless access point for geofence monitoring
US9451035B2 (en) 2016-09-20 Push-based location update
US20090005018A1 (en) 2009-01-01 Route Sharing and Location
US9843895B2 (en) 2017-12-12 Location-based services for calendar events
US8868104B2 (en) 2014-10-21 Multi-tier geofence detection
KR101430300B1 (en) 2014-08-14 Space and time based device customization
KR101418640B1 (en) 2014-07-14 Identifying and locating users on a mobile network
US9743234B2 (en) 2017-08-22 Monitoring a mobile device en route to destination
US8660541B1 (en) 2014-02-25 Provision of location-based venue information
US8369837B2 (en) 2013-02-05 Task management based on travel distance
AU2014275203B2 (en) 2017-08-24 Modeling significant locations
US20130225196A1 (en) 2013-08-29 Geo-Fence Generation and Updating Based on Device Movement Patterns
Owner name: APPLE INC., CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SABATELLI, ALESSANDRO F.;HUANG, RONALD K.;REEL/FRAME:029451/0521


text:
Q: Jquery Datatable export to excel I have used export to excel functionality of Jquery. Its working fine. I am able to see all the columns with proper data. In the excel sheet i am having one date columns in that the date values are coming as belows
1/02/2014
3/05/2014
.#######
.#######
7/07/2014
But when i expand the excel column i am able to see the date in below format(there are some spaces before the dates)
1/02/2014
3/05/2014
  4/05/2014

  7/05/2014

7/07/2014
So my question is that, is there any way to align the text in excel sheet using JQuery datatable.
Please suggest.

A: Excel shows ######## when the column is too narrow to display a number (dates are numbers). It seems that some html formatting carries over to Excel.
Since Excel already shows the dates correctly, you can remove any formatting from the column (Home ribbon > Clear Formats and re-apply your favorite date format.

redpajama_set_name: RedPajamaStackExchange


text:
Hawaii News | Top News
Feds spurn COVID-19 testing held on H-3 freeway
By Timothy Hurley thurley@staradvertiser.com
Video by Cindy Ellen Russell; courtesy video Hawaii COVID-19 Joint Information Center
For several hours, state and city officials shut down both sides of the H-3 freeway on Tuesday for drive-thru COVID-19 surge testing in an effort to test as many Oahu residents as possible.
CINDY ELLEN RUSSELL / CRUSSELL@STARADVERTISER.COM
H-3 Freeway was closed Tuesday for COVID-19 surge testing.
Cars entered H-3 Freeway at 8:30 a.m. Tuesday for COVID-19 surge testing in the Tetsuo Harano Tunnel.
Thousands were tested for COVID-19 Tuesday during Oahu's unprecedented surge testing event on the H-3 freeway.
But Hawaii officials acknowledged facing the potential loss of federal transportation funding after the Federal Highways Administration denied the state's request to use the freeway for the event.
Ed Sniffen, state Highways Division deputy director, said the state was informed of the FHA's denial in a letter that arrived just hours before the testing was set to begin but after the freeway had been shut down at 5 a.m. and personnel were beginning to move into place.
The reasons given by the federal agency: the impact on traffic, commerce, safety and Marine Corps Base Hawaii in Kaneohe.
Sniffen said he discussed the letter with Gov. David Ige.
"We decided it's way too important for the public for us not to move forward with this testing today," he said at a news conference just outside the H-3 tunnel, the epicenter of Tuesday's testing.
"We believe this is a safer testing site," Ige said.
>> PHOTOS: COVID-19 testing held on H-3
Sniffen said he was to blame for not giving federal officials enough information about the gravity of the situation. He said the fact that Hawaii is hitting consistent triple-digit daily COVID-19 cases is "phenomenally huge."
"I didn't get that across to them," he said. "I didn't give them enough information for them to understand the big impacts."
The state receives $180 million for projects from the FHA each year, Sniffen said, and the agency could choose to withhold some of the money.
A spokesman of the FHA in Washington, D.C., declined to discuss the situation with the Honolulu Star- Advertiser but he did issue this statement:
"The Federal Highway Administration communicates directly with our State partners and Hawaii DOT is aware of the agency's position. We look forward to working with the State to identify alternative options."
However, Sniffen said the state is still planning to hold the second scheduled surge testing on the H-3 freeway on Thursday.
Meanwhile, state Department of Health officials on Tuesday said they recorded four new coronavirus- related deaths and 181 new cases, bringing the statewide totals since the start of the pandemic to 74 fatalities and 8,653 cases.
The deaths included three Oahu residents and a man over the age of 80 who lived at the Yukio Okutsu State Veterans Home in Hilo, the third COVID-19-related death tied to a cluster there.
The Oahu victims were described as a man and a woman in their 70s and a man over the age of 80. All of them were hospitalized before dying, and they had underlying medical conditions.
No other information was provided.
More than 4,000 people were tested for Tuesday's case tally, with a positivity rate of 4.5% — a lower daily rate than the state has seen in recent weeks.
"That's good news," said Lt. Gov. Josh Green, an emergency room doctor. "That means the virus will begin to subside."
Green cautioned, however, that he anticipates cases will continue to surge and be active for the next 10 days before the epidemic calms down. That's when "we'll be able to reopen the state," he said.
Over at the H-3 freeway, there was a steady line of cars before noon coming from town. The wait time was estimated to be as long as 45 minutes.
On the other side of the Koolau mountains, the traffic for testing was light to nonexistent other than during the first hour. At 11:30 a.m., no cars were lined up outside the tunnel on the Windward side, and only about 50 cars were inside for testing and registration.
Honolulu Fire Department Capt. Jeff Roache said pre-registration for Tuesday's surge testing had dipped, with only 1,700 people signing up by 7 a.m.
By the midday news conference, he was imploring people to come out for an afternoon COVID-19 test.
"It's a beautiful view," Roache said in the sunshine. "I don't think you'll ever get this opportunity to see the H-3 the way you can see it today."
The operation appeared to be running smoothly, but the experience wasn't perfect for everyone.
One woman said she waited for over 45 minutes before reaching the tunnel and getting the test kit in a bag. But she was told to stay in the left lane. Workers kept waving her along — right back onto the open highway. She ended up leaving without getting her test completed.
Regarding the dispute with the Federal Highways Administration, Sniffen said his staff had been working with the agency for nearly a week trying to obtain permission for use of the freeway "for nontransportation purposes."
State officials also heavily publicized the event for days, saying it was the ideal way to conduct mass testing without causing traffic disruptions in surrounding neighborhoods. They said they believed the green light from the feds would come.
Sniffen said he would continue to seek permission in advance of Thursday's event from 9 a.m. to 2 p.m. on the H-3.
He said he hopes to explain that traffic has lessened dramatically during the 14-day Oahu lockdown, with 40,000 fewer trips between Honolulu and the Windward side and easy alternate routes.
Safety concerns are also minimized, he said, with more than 300 personnel on the scene, including 50 health care workers, 100 firefighters, 100 Air National Guard troops and 50 Honolulu police officers for traffic control.
"To shut down the entire freeway, we needed the numbers, so we brought in those numbers," Roache said.
The total budget for the event was over $10 million, which came from the state's allotment of federal CARES Act emergency coronavirus money, he said.
Hawaii Kai residents asked to conserve water during repairs
FaceTiming with his family kept Mark Mothersbaugh alive during battle with COVID-19
More Coronavirus Outbreak
Hawaii visitors in 2022 down 11% from pre-pandemic level
U.S. population center trending toward South this decade
COVID vaccines targeting omicron should be standard, panel says

redpajama_set_name: RedPajamaCommonCrawl


text:
Meet the officer helping to keep South Leeds clean, tidy and running smoothly
On 7 January 2020 7 January 2020 By Jeremy Morton
For the last three months the wards of Beeston & Holbeck and Hunslet & Riverside have had a dedicated Civil Enforcement Officer. I met up with Joanne (not her real name*) to find out about her role.
She has legal powers to tackle illegally parked cars by issuing Penalty Charge Notices (PCNs); and dog fouling and littering by issuing Fixed Penalty Notices (FPNs). Whilst these issues are her priorities she also reports other issues, such as fly tipping to members of her wider team in the Council.
Joanne sees her role as helping to have an impact on the area and improving life for local people. For example by reducing problem parking and making it easier for traffic to flow, making access easier for mechanical street sweepers and refuse lorries and making it safer for children going to school.
The post has been funded by the Inner South Area Committee and it's the ward members who are setting the agenda, responding to feedback from residents, rather than wider Council priorities.
"I'm not working to targets to issue tickets and I'm certainly not on commission" explains Joanne.
With such a big area to cover, she can't cover every issue, but she makes sure she visits the priority areas and hotspots on a daily basis. These include parking on Tempest Road, Dewsbury Road and Beeston Hill as well outside schools.
"It seems to be getting easier as people realise I'm staying in the area. I've noticed on Tempest Road for example, it was really bad with people parking on the zig-zags at the zebra crossing, but it's not as bad now.
"It's the same on Beeston Hill near the traffic lights. I still go there daily and issue PCNs to vehicles but it is getting better."
Most people accept a ticket, but quite a lot get into their car and drive away. Whether it's embarrassment or trying to avoid the fine, it doesn't bother Joanne. It just means the ticket gets issued by post, rather than in their hand. If people do get aggressive, Joanne has a body-cam and is in radio contact with her base for back up.
Joanne's focus is to resolve issues, not to punish people, so she always tries speak to people, explain the issue and change their behaviour.
One recent case involved a motor business on Barkly Road in Beeston. Cars in various states of disrepair and apparently abandoned were left outside the garage. Joanne worked with the garage owner to get the vehicles off the street.
The owner co-operated and worked hard to remove them, or move them into the grounds of the garage.
"It was good to get positive feedback from Councillors that it has made a difference" says Joanne. "I praised the garage owner, but said I'll still be back to check!"
Joanne also carries out joint patrols with PCSOs in Beeston and in Holbeck every two weeks.
"We cover their priority streets and my priority streets together because the Police have powers I don't have and vice versa, so between us we can sort most things out."
Another bugbear in Beeston is matchday parking. Joanne explains that there is a dedicated team of 6-8 officers from Parking Services patrolling every matchday, so she tries to deal with issues a bit further away from the ground on those days.
The post is a one year pilot and will be reviewed at the end of 12 months. If its success carries on the Community Committee will look to continue funding it, helped by the income from fines, which returns to their budget.
Cllr Mohammed Iqbal (Hunslet & Riverside) commented:
"We are very pleased to have this Civil Enforcemrnt Officer between the two wards, I think it will bring a lot of positives in the area in terms of cleaner neighbourhoods and parking issues.
"Refuse vehicles have had a lot of obstructions which have resulted in a backlog of missed bin collections. In turn that's led to a lot of dumping issues and fly tipping. Hopefully we'll see a lot of change now and I'm sure the public will be pleased with that."
If you have any issues you want to report please call the Council's contact centre on (0113) 222 4444 or via the website: my.leeds.gov.uk
*We have changed the officer's name because a few disgruntled people have tried to harass her on social media.
Photo: Cllr Gohar Almass
Beeston Cottingley Header Carousel Section Holbeck HunsletCivil Enforcement OfficerCllr mohammed IqbalLeeds Ciity Council
PREVIOUS POST Previous post: Eat Green at White Rose This Veganuary
NEXT POST Next post: On The Beat: Safer roads
3 Replies to "Meet the officer helping to keep South Leeds clean, tidy and running smoothly"
Paul Wray says:
The employment of a local Civic Enforcement Officer is making a difference to local people in Hunslet and Riverside Ward. Residents asked us to take enforcement seriously, and we have. She is doing a great job so far.
Judith tempest says:
No mention of her patrolling "hunsle t and riverside" just usual places ie Tempest road and Beeston Hill only places councillors seem to have any interest in
Hi Judith. I didn't write this but she is definitely doing work in the Hunslet Moor, Hunslet Green, Hunslet, and Hunslet Carr areas of the ward as I keep sending her work and putting he rin touch with residents and business with complaints.


text:
Zvenygora (Звени́гора) è un film del 1928, diretto da Oleksandr Petrovič Dovženko.

Trama
Alle pendici del monte Zvenigora giace da tempo immemore, disseminato e sepolto in terra, il prezioso e sfuggente tesoro della nazione ucraina. Già dai tempi dei Variaghi e degli Sciti il "nonno" lo ha difeso dagli attacchi degli avidi nemici, e nello stesso tempo ha tentato di impossessarsene, quand'anche a nome del popolo, e nonostante il fatto che il tesoro fosse custodito da una sorta di spaventoso spirito maligno.

In un'ampia carrellata di scene e situazioni che si rifanno alla storia e alla quotidianità ucraine, attraverso diversi secoli, il nonno è molte volte presente, spesso coi suoi due nipoti, Timoch e Pavel, che alternativamente si impegnano in varie cause inerenti alla nazione: dall'arruolamento nei cosacchi, alla collaborazione con la repubblica ucraina di Petljura o viceversa nell'Armata Rossa. Anche la giovane Oksana figura variamente, o come protagonista di idilliche scene pastorali ai bordi del lago, o come efferata traditrice della patria.

L'azione si focalizza infine in tempi più (per l'epoca) recenti: Pavel, nel periodo della rivoluzione d'ottobre e della susseguente guerra civile, vuole convincere il nonno a piazzare una carica esplosiva sui binari di un treno che trasporta passeggeri bolscevichi in territorio ucraino. Pavel dice al nonno che, come spesso nel corso della storia del paese, i bolscevichi vorrebbero impossessarsi del tesoro di Zvenigora.

Il nonno, fedele custode del tesoro, inizialmente cede alle insistenti preghiere del nipote. Poi, ad un più attento esame, decide di fermare il treno e di sventare l'attacco; finisce per montare sul treno stesso, accolto dai passeggeri benevolenti, e, messe da parte le riserve, si dirige su di esso verso il luminoso avvenire.

Voci correlate
 Storia dell'Ucraina
 Cinema russo d'avanguardia
 Repubblica Socialista Sovietica Ucraina

Altri progetti

Collegamenti esterni

(EN) Zvenyhora, su vufku.org

Film ambientati in Ucraina

redpajama_set_name: RedPajamaWikipedia


text:
https://sixerswire.usatoday.com/2022/05/02/doc-rivers-explains-why-sixers-will-continue-to-start-deandre-jordan/
Doc Rivers explains why Sixers will continue to start DeAndre Jordan
May 2, 2022 10:45 pm ET
MIAMI — The Philadelphia 76ers had themselves a tough night in Game 1 against the Miami Heat on Monday to open up the Eastern Conference semifinals where they trailed by as many as 21 in a 106-92 loss.
Without Joel Embiid, the Sixers turned to DeAndre Jordan in his place. The 14-year veteran did some good things in terms of catching lobs, but he had a hard time on the glass and he was bad on the defensive end. He finished as a minus-22 in only 17:17 of playing time.
In Jordan's defense, the entire starting lineup wasn't good in this one. He also gave the team a boost a bit to start the third quarter in order to give Philadelphia a cushion, but overall, it's hard to justify starting him going forward.
However, coach Doc Rivers and the Sixers are going to continue going to him.
"We talked to our guys," said Rivers after the loss. "They wanted a big roller and I thought in the second half, that's how he has to play every night. Those first four or five minutes were great from him. That's what we need. We love Paul (Reed), but we don't need Paul in foul trouble and that's why you don't wanna start him."
Heading into Game 2, Rivers did reveal that the Sixers will continue to go to the veteran out of Texas A&M.
"We like DJ," Rivers added. "We're gonna keep starting him whether you like it or not. That's what we're gonna do because our guys believe in him. At halftime, we asked our key guys because we were thinking about it because I thought Paul Millsap gave us some decent minutes, and to a man, that's where they wanted to go."
Doc Rivers: "We like DJ. We're gonna keep starting him whether you like it or not." #Sixers
— Ky Carlin (@Ky_Carlin) May 3, 2022
Game 2 against the Heat is set for Wednesday in Miami. While Jordan had himself a tough night, Reed did have five fouls in 13:03 and Millsap had a few bad moments on defense. Without Embiid, there really isn't much Rivers can do.
As they move forward in this series, Jordan may very well just be the guy.
This post originally appeared on Sixers Wire! Follow us on Facebook!
Sixers vs. Heat series preview: X-Factors, matchups, prediction
Matisse Thybulle has the support of Doc Rivers as Sixers prep for Heat
Paul Reed ready to do more for Sixers with Joel Embiid sidelined
Doc Rivers credits Heat's Pat Riley for influencing him to be a coach
More 76ers


text:
A First Date with a Good PickUp Line
Monday - August 19, 2013 by Henry E. (Hank) Scott | 1 Comment
WeHo is a wonderfully weird little city.
How many places could launch a free party bus (sorry, "entertainment shuttle"), unabashedly use sexual innuendo to promote it and get the whole town buzzing? The Creative City certainly can.
It's not just WeHo'ans being seduced by the PickUp Line—we're happy to play along with the innuendo — but the media, too. Press from all over L.A. turned up for Friday's launch event and the PickUp's first official night out on the town. The PickUp is getting almost as much ink as that giant tube that's proposed to take us to San Francisco and New York at lightening speeds.
I was among the writers eager to get "picked up" for the PickUp's maiden voyage on Friday night. I set out from my eastside abode toward WeHo on an L.A. city bus. The bus was crowded, the ride was bumpy and there was a lot of yelling when the driver passed someone's stop. My regular transportation squeeze has set up the newcomer PickUp to look good.
And the charming new suitor looks very good. The bright yellow exterior has comic book-style imagery. A trolley-inspired interior includes wood benches and big, low windows. Besides its vintage look, the shuttle is set apart from other buses by its music, a mix programmed by West Hollywood DJ Derek Monteiro.
The question is, will the party show up for the party bus?
I embarked on the ride with notebook in hand. Here's a log from my journey:
[hr_dotted]
8 p.m. –I see one of the PickUp's two buses set out with lots of press on board. Across the street, I get on the other bus. This one is empty except for three guys who are talking to Laura Biery, economic development analyst with the city.
8:20 p.m. – A couple of groups have come aboard and the song "Thrift Shop" is playing. One tells Laura that the bus would be a great setting for a music video. Lady Gaga has been hanging around WeHo lately.
I'm thinking the party may be getting started, but most of the riders aren't on long. Soon it's quiet again, so I ask Laura some questions about the PickUp and its social media presence.
There's been talk of adding an onboard photo booth, but that component isn't set up. Laura tells me that the city is still looking at bids; apparently the first bids came in higher than expected. To explain what they have in mind, Laura tells me how one of the proposed setups would have worked. Riders would have posed for pics, then entered their information on a touch screen. Then, the photos would be sent to them via text message—and then they could share via social media (tagging @WeHoPickup on Twitter and Facebook).
The photo booth may or may not pan out, but Laura tells me there are social media "ambassadors" who are taking photos and doing social media posts. (You can see some of our favorite posts from and about The PickUp in our Storify item.) I try to shoot some photos during my ride, but it turns out to be a bit tricky to snap photos on a moving bus without dropping something or tumbling over.
8:30 p.m. – We reach the end of the 30-minute route. Instead of continuing the loop, we pull over. Since there are two shuttles doing the same loop, the buses run 15 minutes apart as long as they are in sync. The other shuttle, which apparently made some extra stops for photo ops, is running behind. We have to wait for it to catch up so that the timing is right. I wonder if it's time to pull out the book I brought along.
8:45 p.m. – Things are picking up on the PickUp. It's not packed, but there's a steady stream of riders. Several notice that I'm scribbling away in my notebook—not exactly standard Friday night partying gear—and ask what I'm working on. Another marked difference from a standard bus, where strangers rarely engage me in friendly chats. Either WeHo's just a friendly place, or Friday night revelry and the novelty of the new shuttle are putting folks in a great mood.
I'm not actively interviewing, just observing and journaling, but one rider asks me if I want a quote. I tell him to fire away. I'm interested to hear if riders think the bus lives up to its hype. This rider thinks it does; he calls it friendly, fun, free and smart.
Another rider boards and loudly says, to no one in particular, "This is great!" When he gets off a few blocks later, it's not clear if he's mostly sincere or largely sarcastic as he raves, "This is great! We would never have had dinner here if we hadn't had this! I'm so excited to have dinner on this side of town!"
9:15 p.m. – I meet a go-go dancer who works at several area clubs. Tonight he's working in Silver Lake, and he's using the PickUp for a segment of his commute. He hopes that the shuttles will spread business around in WeHo by making it easier for partiers who hit the strip of clubs near Santa Monica and San Vicente to also check out WeHo clubs that are farther east.
9:30 p.m. – Cute as they are, the bus benches aren't designed to be comfortable for extended rides. I'm also hungry, and I'm curious whether the other bus is still full of press. I get off to grab a snack, take a break and then catch the other bus.
10 p.m. – As shuttle No. 2 approaches, I see it's jam-packed. When it pulls up to my stop, though, most passengers get off. It turns out to be one big group, the WeHo Dodgeball players. With them is Jon Viscott, WEHOville's freelance photographer, who's been shooting pics.
I don't see any other press when I step onto the bus, but soon there are plenty of riders. One woman gets on and says "party!" and another rider says "yeah!" and makes a lasso motion as he makes his entrance.
10:15 p.m. – The crowd is getting rowdier, and the music is getting louder. The fun of WeHo nightlife is spreading to the shuttle.
"Goodbye, trolley!" says one disembarking rider. "We love you!"
By 11 p.m., the stream of passengers is steady and the mood is jovial. No one's more apt to get excited about an idea than a crowd that's well-primed with cocktails.
Although I haven't had libations, I have climbed aboard the bandwagon. I wish I could take this seductive new trolley home — but with its limited route that's not an option. It's back to the old squeeze.
I spend an hour waiting for an eastbound L.A. bus. One finally comes along just as I'm on the verge of opting for a cab instead. The ride is uneventful; there's no music, no chatting and there are no friendly neighborhood go-go dancers. The faded fabric on the seats and the bright yellow poles are no competition for the PickUp's smooth style, enthusiastic riders and love for double-entendre.
I'm glad I got "picked up." Stay quirky, WeHo.
Click here to see what everyone had to say about the PickUp on social media.
Tags: party bus, pickup bus, pickup line, weho pickup bus, west hollywood party bus
About Henry E. (Hank) Scott
Henry E. (Hank) Scott is the former publisher and editor of WEHOville.com
The PickUp's Ridership Is Increasing. But So Are Its Costs
The PickUp Offers Free Shuttle on St. Patrick's Day
WeHo PickUp Trolley Campaign a Finalist for Major PR Award
WeHo Shuttles Will Provide Free Pride Weekend Transport
Kathy O'Neal
Great article Stevie!


text:
- International Celebrity Site dedicated to dirty gossip, leaked photos & video.
Lindsay Pulsipher Nude
Lindsay Pulsipher
Lindsay Pulsipher (born May 6, 1982) is an American actress. She has had several roles in film and television, and is known for her series regular role as Rose Lawrence on A&E Network's The Beast (2009). She joined the third season of HBO's True Blood (2010), playing were-panther Crystal Norris and love interest to Jason Stackhouse. Wikipedia
Born: 6th May, 1982, Salt Lake City, Utah
Height: Height Unknown
Claim to Fame: True Blood
Click To See Lindsay Pulsipher Uncensored
Lindsay Pulsipher Photos
Lindsay Pulsipher Videos
DAILYMOTION: Lindsay Pulsipher at H-Couture 2012: The Future of Fashion - Arrivals
DESNUDA: Samantha Harris BIKINI
From Hot Video
DESNUDA: Mary-Kate Olsen Naked
From Latest Video
DESNUDA: Shalom Harlow PICS
From Behind Scene
DESNUDA: Eva Marcille SexTape
From Most Popular
DESNUDA: Sandra McCoy PHONE
From Top Video
Lindsay Pulsipher nude - sexy pics & vids! 22 January 2020
Cottonwood High School is a public high school located in Murray, Utah. It is based on Elmore Leonard's short story "Fire in the Hole". Timothy Olyphant portrays Raylan Givens, a tough U.S. The third season of the television series True Blood premiered on June 13, 2010 simultaneously on HBO and HBO Canada. True Blood is an American television drama series produced and created by Alan Ball. The Beast is an American crime drama starring Patrick Swayze and Travis Fimmel. The Rambler is a 2013 comedy drama film written and directed by Calvin Reeder. The Oregonian is a 2011 horror film directed by Calvin Reeder. A 13 year old is kidnapped and locked in a basement by a scary couple with their younger son.
The movie premiered at the 2011 Sundance Film Festival and was given a limited release beginning on June 8, 2012, partially as a result of a successful Kickstarter campaign. It was Swayze's final acting performance before he died from pancreatic cancer in 2009. Justified is an American television drama series developed by Graham Yost. The season premiered on June 26, 2011. Dead to the World is the fourth book in Charlaine Harris's series The Southern Vampire Mysteries, released in 2004. Founded in 1970, by Tyson Burton after the Granite School District condemned the property and obtained the land from farmers, who bought the land from Native Americans. The 14th season of Law & Order: Special Victims Unit debuted with a two-part premiere episode on September 26, 2012, at 9:00 pm on NBC, which was the show's weekly time slot. Lindsay Pulsipher is an American actress.
The series, which only ran for one season, debuted on A&E Network. During there incarceration in the basement the two children develop a special relationship and try and get through the night. Summer Solstice tells a story set in coastal Maine, a reflective coming-of-age tale starring George Fivas as Joshua Ballard, a brilliant but aimless and misunderstood college student who finds solace in composing music and writing. The ninth and final season of the American dramatic television series Touched by an Angel aired CBS from September 28, 2002 through April 27, 2003, spanning 26 episodes. The fourth season of the television series True Blood contains 12 episodes, bringing the series total to 48. It's the true American story of a legendary family feud—one that spanned decades and nearly launched a war between Kentucky and West Virginia.
Tonya Suzanne Holly is a casting director who studied theater at University of North Alabama. It concluded its run on September 12, 2010 and contained 12 episodes, bringing the series total to 36. She has had several roles in film and television, and is known for her series regular role as Rose Lawrence on A&E Network's The Beast.
Monica Farro
Lorena Rojas
Diane Fleri
Ricki-Lee Coulter
© 2015 Desnuda.Top - All Rights Reserved


Despite colder weather elsewhere in the United States, warmer weather this year to date in the West has resulted in lower natural gas demand, according to the U.S. Energy Information Administration.
This has left more natural gas storage in the region and translated into lower natural gas prices, according to the agency.
"Seven states -- California, Idaho, Nevada, Oregon, Utah, Washington, and Wyoming -- have reported average temperatures for the month of January in the top 10 warmest on record, with cumulative [heating degree days] since the beginning of the year totaling 922," EIA said in a weekly report. That is 25 percent fewer than normal and stands in stark contrast to the 2,200 cumulative heating degree days east of the Rockies for the same period.
Western spot prices have been near or below Henry Hub prices, which averaged $2.88/MMBtu between Jan. 1 and Feb. 20. Prices in the Northeast, by comparison, are four or more times higher than those in the West. The average spot price for PG&E CityGate for that period was $3.10/MMBtu, while Sumas natural gas averaged $2.54/MMBtu.
Working gas in storage reached 1,938 Bcf as of Feb. 20, according to EIA estimates, a net decrease of 219 Bcf from the previous week. Storage levels are now 42.3 percent greater than a year ago and 1.5 percent less than the five-year average.
Natural gas values rose in Thursday-to-Thursday trading, with Henry Hub gas spot values up 13 cents since Feb. 19 to trade Feb. 26 at $3.10/MMBtu. Western natural gas prices rose between a cent and 36 cents by the end of trading. El Paso-Permian natural gas gained the most, jumping 36 cents to end at $3/MMBtu. It was one of several hubs trading at or above $3 this week.
Western peak power prices moved nominally in the Feb. 20 to Feb. 27 trading period. California-Oregon Border values added 25 cents in trading, while South of Path 15 lost $1. Average daytime prices ranged from $23.60/MWh at Mid-Columbia to $33.90/MWh at SP15.
Northwest nighttime power values jumped $7 on average, with Mid-C posting the greatest gains, up $7.85 to $20.05/MWh. Average off-peak prices Friday ranged from $20.05/MWh at Mid-C to $29.75/MWh at SP15.
Peak demand on the Cal-ISO grid reached 28,596 MW Feb. 23, which should be the week's high. Northwest Power Pool demand reached the week's high of 56,902 MW that same day [Linda Dailey Paulson].


8) - Mermaids live in the ocean. I like mermaids. They are beautiful and I like their shiny tails, but how on earth do mermaids get pregnant? Like, really?
OMG...so funny...my sides are hurting from laughing too hard!
LOL...glad you ladies enjoyed. I got a kick out of them, too.


Beef jerky is one of the simple joys in life and few do it better than Three Jerks. Emmy winning TV show Shark Tank first introduced the world to the company, who bucked the jerky establishment by making this cured snack out of uber fancy filet mignon. After scoring a deal with FuBu creator Daymond John, their small-time jerky company launched to new levels. We've already told you why you should be eating their product, but now we have another reason: a tasty new flavor called Veri Veri Teriyaki.
Originally, Three Jerks cooked up their meaty treats in 4 flavors: Original, Chipotle Adobo, Memphis Brand BBQ and Maple Bourbon Churro. They later added Hamburger Jerky to their repertoire but they never strayed East like most jerky brands by offering a teriyaki flavor. That is, until now.
The guys at Three Jerks formed a partnership with the good people at sauce makers Soy Vey to create this newest flavor. It's the first time Soy Vey has ever teamed with another food brand and it seems like a perfect partnership, as both of these teams consist of best friends who just love making tasty food. And this new flavor sure does sound delicious.
The jerky makers are heading back to their roots to launch this new flavor by creating a Kickstarter campaign. So, not only can you pick up this new flavor by donating, but you can also score some cool rewards by doing so (if helping bring this tasty flavor to the world isn't reward enough). One of which is a personalized video from Shark Tank star Daymond John. Furthermore, the guys at Three Jerks are giving back to the entrepreneurial world by matching 5% of their Kickstarter proceeds to help support 5 other unique Kickstarter campaigns.
We've been lucky enough to try the new flavor for ourselves and you can check out our review here. Honestly, it may just be our new favorite and we can't wait for the rest of the world to try Three Jerks' newest creation!


This is one of those highly sought after Mitchell Lumitone lamp / radio.
It's nickname is The Rocket. Great machine age bakelite case , housing a tube radio. Radio and lamp both work great.
There's a hairline crack in the plastic shade (see pics) but it in no way affects the cool look of this vintage piece.


text:
import { EditModeHelper } from './../shared/Utilities/edit-mode.helper';
import { Observable } from 'rxjs/Observable';
import { errorIds } from './../shared/models/error-ids';
import { Component, OnDestroy, Output, EventEmitter, ViewChild, ViewChildren, ElementRef, Input, QueryList, OnInit } from '@angular/core';
import { PortalService } from '../shared/services/portal.service';
import { BroadcastService } from '../shared/services/broadcast.service';
import { BroadcastEvent } from '../shared/models/broadcast-event';
import { GlobalStateService } from '../shared/services/global-state.service';
import { TranslateService } from '@ngx-translate/core';
import { PortalResources } from '../shared/models/portal-resources';
import { Subject } from 'rxjs/Subject';
import { MonacoEditorDirective } from '../shared/directives/monaco-editor.directive';
import { MonacoHelper } from '../shared/Utilities/monaco.helper';
import { FunctionAppContext } from 'app/shared/function-app-context';
import { FunctionAppService } from 'app/shared/services/function-app.service';
import { ErrorableComponent } from '../shared/components/errorable-component';

@Component({
    selector: 'host-editor',
    templateUrl: './host-editor.component.html',
    styleUrls: ['./host-editor.component.scss']
})
export class HostEditorComponent extends ErrorableComponent implements OnInit, OnDestroy {
    @ViewChild('container') container: ElementRef;
    @ViewChild('editorContainer') editorContainer: ElementRef;
    @ViewChildren(MonacoEditorDirective) monacoEditors: QueryList<MonacoEditorDirective>;
    @Output() changeEditor = new EventEmitter<string>();

    public configContent: string;
    public isDirty: boolean;
    public disabled: Observable<boolean>;
    public context: FunctionAppContext;

    private functionAppContextStream: Subject<FunctionAppContext>;
    private _originalContent: string;
    private _currentContent: string;

    constructor(
        private _portalService: PortalService,
        broadcastService: BroadcastService,
        private _globalStateService: GlobalStateService,
        private _functionAppService: FunctionAppService,
        private _translateService: TranslateService) {
        super('host-editor', broadcastService);
        this.isDirty = false;

        this.functionAppContextStream = new Subject<FunctionAppContext>();
        this.functionAppContextStream
            .do(() => this._globalStateService.setBusyState())
            .switchMap(context => {
                this.context = context;
                return this._functionAppService.getHostJson(context);
            })
            .subscribe(hostJson => {
                const hostJsonResult = hostJson;
                if (hostJsonResult.isSuccessful) {
                    this._originalContent = JSON.stringify(hostJson.result, undefined, 2);
                    this._currentContent = this._originalContent;
                    this.disabled = this._functionAppService.getFunctionAppEditMode(this.context).map(r => r.isSuccessful ? EditModeHelper.isReadOnly(r.result) : true);
                } else {
                    this.disabled = Observable.of(true);
                }
                this.cancelConfig();
                this.clearDirty();
                this._globalStateService.clearBusyState();
            });
        this.onResize();
    }

    ngOnInit() {
        this.onResize();
    }

    @Input() set functionAppInput(value: FunctionAppContext) {
        this.functionAppContextStream.next(value);
    }

    contentChanged(content: string) {
        if (!this.isDirty) {
            this.isDirty = true;
            this._broadcastService.setDirtyState('function');
            this._portalService.setDirtyState(true);
        }

        this._currentContent = content;
    }

    cancelConfig() {
        this.configContent = '';
        setTimeout(() => {
            this.configContent = this._originalContent;
            this.clearDirty();
        }, 0);
    }

    saveConfig() {
        if (this.isDirty) {
            try {
                this.configContent = this._currentContent;
                this._globalStateService.setBusyState();
                this._functionAppService.saveHostJson(this.context, JSON.parse(this.configContent))
                    .subscribe(() => {
                        this._originalContent = this.configContent;
                        this.clearDirty();
                        this._globalStateService.clearBusyState();
                    });

                this._broadcastService.broadcast<string>(BroadcastEvent.ClearError, errorIds.errorParsingConfig);
            } catch (e) {
                this.showComponentError({
                    message: this._translateService.instant(PortalResources.errorParsingConfig, { error: e }),
                    errorId: errorIds.errorParsingConfig,
                    resourceId: this.context.site.id
                });
                this._globalStateService.clearBusyState();
            }
        }
    }

    ngOnDestroy() {
        this._broadcastService.clearDirtyState('function');
        this._portalService.setDirtyState(false);
    }

    private clearDirty() {
        if (this.isDirty) {
            this.isDirty = false;
            this._broadcastService.clearDirtyState('function');
            this._portalService.setDirtyState(false);
        }
    }

    onResize() {
        MonacoHelper.onResize(this.container, this.editorContainer, this.hostEditor);
    }

    private get hostEditor(): MonacoEditorDirective {
        return MonacoHelper.getMonacoDirective('host', this.monacoEditors);
    }
}

redpajama_set_name: RedPajamaGithub


Featuring free WiFi throughout the property, Beautiful Belleville Hôtel & Hostel offers accommodation in Paris. There is a 24-hour front desk at the property and Buttes Chaumont Park is 400 metres away.
All rooms at Beautiful Belleville Hôtel & Hostel are serviced by a lift. Most of them have a private bathroom with a shower.
Marne-la-Vallée is 30 km from Beautiful Belleville Hôtel & Hostel, while Versailles is 20 km from the property. Orly Airport is 16 km away.
This room is accessible for people with reduced mobility.
Rate: € 90.00 ... € 120.00; select dates below to get current rates.
This room offers a private bathroom.
Rate: € 31.39 ... € 120.00; select dates below to get current rates.
This room is a mixed dormitory with a private en suite bathroom. It features free WiFi.


The M5 mobile spectrum analyser solution is a specially designed vehicle mountable device featuring enhanced technology for analysing the areas spectrum at very low cost.
The M5 mobile spectrum analyser is vehicle mountable to a steel surface via its ruggedised anti-wobble Magnabase and is supplied with a 24Vdc PoE injector and 20 meters of network cable attached.
SIL-MOB-M5 (Single Radio), 1 x Radio (Built in Antenna), 1 x PSU 24vDC PoE Injector.