1. Extensible Windows Desktop Utilities Performed By: Alexander Badyan Oren Shalgi Supervisor: Oved Itzhak Winter 2004/5

2. Abstract Computer users have typically a small set of utilities that they need to access very fast. –Taking a quick note. –Finding a phone number. The project goal is to create an extensible framework to contain such utilities.

3. Practical Aspects For that we take advantage of the “Active Desktop” feature of Windows. Create a web based application that lies on the desktop. Now the utilities are accessible by a click on the “Show Desktop” icon. Two Usage Modes –Central server (common for many users) –Personal usage (single user)

4. Requirements Interface needs to be minimal and intuitive. Framework should not take up a lot of desktop space. Provide fast access to utilities.

5. Requirements (cont.) New utility introduction should be simple. Information must not be lost when switching between utilities. Provide comfortable access to a large number of simultaneously active utilities.

6. Developer Concerns Stable system. Support multi-user handling. Framework needs to be general enough to ensure a support for a wide range of utilities. No collisions between utilities. Efficient handling of dynamic utility changes (addition/removal). Handle a large number of simultaneously active utilities.

7. Block Diagram uses implements Desktop Framework IPlugin (interface) Utility

8. DesktopFramework The main framework module. Handles user interaction. Manages and organizes all utilities. Multi-user handling. Is not aware of which utilities are available prior to its activation. Doesn’t "know" what the utilities do even after they are activated.

9. How DesktopFramework works Maintains lists of active and available utilities. Available utilities list can be refreshed to seek for new utilities. User can invoke several instances of the same utility and address them separately. During his work, the user can switch between utilities back and forth.

10. Demonstration 1

11. Demonstration 2

12. IPlugin interface All utilities must implement it. Its role is to connect between the utilities and the main framework. Provides the utility module with information regarding the current panel size. Identifies it as compatible with our application.

13. Scratchpad Often while surfing the internet or talking on the phone you need to take a quick note. A place to write (or paste into) snippets of text. Saving written text to file on the user's computer (not on server). Open selected text as a link in a new browser window.

14. Generic Database A database one can use to store anything. Adding a key-value pair. Searching for a value (using a case- insensitive, partial query). Removing an entry (by key). Changing the value of a key. Clearing the entire database.

15. Implementation Method DesktopFramework is a Web Application. DesktopFramework module is developed using ASP.NET written with C#. Utilities are Web Controls, complied into DLL files.

16. Module Adder Tool Provides an easy-to-use graphical interface for module importing. Intended for the system administrator. Should be run from the server computer.

17. Module Adder Tool - Screenshot

18. Summary The project was an engineering exercise. We learned a lot about design methodologies. We gained valuable experience in C#, web technologies and.NET environments. We would like to thank Oved and the lab staff for the help throughout the project.