1 / 24

Window.Box Software for Schools

Window Box offers industry-standard technology solutions for schools, with over 50,000 installations in primary schools. The software allows for secure and controlled user environments, customized desktops, and network sharing abilities. ClassMate Overview includes features for user-specific views, software organization, and robust security measures. Application development tips focus on user interface, paths, and configurable applications to ensure optimal performance in the educational setting.

chrissyc
Download Presentation

Window.Box Software for Schools

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Application Software andRM Window Box

  2. Window Box • A family of solutions: • Curriculum PC - Window Box • Entry level networking - Window Box SchoolShare • Server based networking - Window Box Connect • Designed for schools • Industry standard technology – independent of RM hardware

  3. Window Box • Over 50,000 installed in primary schools • Current version: Window Box 8 (Windows 98) • Variety of predecessors - mix of • Windows 3.1 • Windows 95 – July 1996 onwards • RM Classmate also available separately • Used by schools on various other PCs

  4. It’s Windows!

  5. Secure environment Multiple user environment ClassMate Overview • What is its purpose? • A solution for education • Provides:

  6. ClassMate Overview • User’s Desktops • Present user specific view of computer - time on task, few distractions • Software grouped together, according to category, CD, software company, or any other grouping you can think of • Restrictions - more later • Physically: Profiles in the Windows folder • ALL the software is there on the machine; the desktops allow the Manager to choose which is available to any child or group of children

  7. ClassMate Overview • Manager’s desktop • password protected • “non-configured” Windows • Can run all software • Can customize Users, or add new ones • Registry editing controlled by password

  8. ClassMate Overview • Security part 1 • Logon screen • Password protection • Limited Start Menu • No access to Settings (Control Panel, Printers, etc.) • Cannot run Find Files • No Shut Down option • Cannot run Explorer

  9. ClassMate Overview • Security part 2 • No right-click on common dialogs • No User desktop help • Maintenance Mode on User desktops • Registry editing controlled by password

  10. ClassMate Overview • Classmate Manager • Customize and add new Users according to: • Individual needs • Project Work Groups • Staff Members • Internet Users • Resource Cupboard • A store for all shortcuts to applications to be added to Users’ desktops • Desktop Layout and Design

  11. RM SchoolShare • Included with ClassMate • “Plug and go” peer to peer networking • Sharing access to the Internet • Sharing access to printers • A simple solution: primary school IT co-ordinators do not need the time or expertise to get to grips with networking • Can be used to set up file sharing & Intranets but not the default • Over 2,000 schools set up networks by using it

  12. Application Issues and Development

  13. Typical Application Issues • Do not recognise network drives as viable locations for installation • Do not record from which drive they were installed - assume CD is in drive D • Do not allow change to default save • Colour and / or screen resolution dependence • Insistence on a port name, e.g. LPT1 causes a problem with networks

  14. Application Development • General Issues • User Interface • Registry information • Path information • Configurable Applications

  15. Application Development • 32-bit applications • Porting from DOS-based applications is difficult • Best to re-write completely • Universal Naming Code (UNC)

  16. Application Development • User Interface • Microsoft guidelines • http://msdn.microsoft.com/ui/default.asp • Keyboard shortcuts • Multiple levels • Screen resolution (800x600). Colour Depth (16bit) • The education market requirements are different to home and business markets

  17. Application Development • The Registry • No specific considerations for the Window Box / ClassMate • Use the Registry, not INI files • HKEY_CURRENT_USER for user specific information • HKEY_LOCAL_MACHINE for station specific information

  18. Application Development • Paths • Don’t hard-code paths in your application • Store the path information in the registry, or look for the locations as stored by Windows • The following paths should be considered: • My Documents: • HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders • :\Windows and :\Windows\System • GetWindowsDirectory ( ) GetSystemDirectory API calls will return these. Or use the FileSystemObject, new to VB6.0

  19. Application Development • Paths, continued • C:\ drive. • Never hard-code this. The user may have a different PC setup • Application location • It may not be on the C:\ drive! • Save and Open folders • Store a default location in the user registry, and allow it to be configured • More applicable to Window Box Connect today • Printers and CD-ROM drives • These may not be on LPT1, or D:

  20. Application Development • Configurable Applications • Configuration allows flexibility to adapt the application to work on different kinds of system • Allows different levels to be customised according to users’ needs • Allow the following to be configured: • Paths (save/open folder, etc) • Toolbars • Default Fonts • Application features

  21. Installing software on a Window Box • Avoid “DLL Hell” • Microsoft term for the mess made by putting all DLLs in Windows/System! • put the DLLs in the program executable folder • If you must install to system, be very careful about replacing existing DLLs: VB run-time DLLs are a particular minefield • Be careful about changing file associations • Ask the user if they want to make the changes • Avoid making the user restart the machine • In our experience, customers get confused when they have to do this • Allow the user to choose the program location

  22. Summary • Window Box environment • Application development • Installation Considerations

More Related