Cello (web browser)

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

Lua error in package.lua at line 80: module 'strict' not found.

Cello WWW Browser
Cello icon.gif
Cello main page.png
Original author(s) Thomas R. Bruce
Developer(s) Legal Information Institute at Cornell Law School
Initial release 8 June 1993; 31 years ago (1993-06-08)[1]
Last release 1.01a / 16 April 1994; 30 years ago (1994-04-16)
Development status Discontinued
Written in C++,[2] makes "heavy use of Borland Object Windows libraries"[3]
Operating system Windows 3.1 / 3.11, OS/2,[4] Windows NT 3.5[5][6]
Size 325 kb
Available in English
Type Web browser
License Shareware/Proprietary
Website http://www.law.cornell.edu/cello/ (Internet Archive)

Cello was an early graphical web browser for Windows 3.1, developed by Thomas R. Bruce of the Legal Information Institute at Cornell Law School, and released as shareware in 1993.[7][8] While other browsers ran on various Unix machines, Cello was the first web browser for Microsoft Windows, using the winsock system to access the Internet.[9][10][11][12][13][14] In addition to the basic Windows, Cello worked on Windows NT 3.5[5][6] and with small modifications on OS/2.[15][16]

Cello was created because of a demand for Web access by lawyers, who were more likely to use Microsoft Windows than the Unix operating systems supporting earlier Web browsers, including the first release of Mosaic. The lack of a Windows browser meant many legal experts were unable to access legal information made available in hypertext on the World Wide Web.[9][17] Cello was popular during 1993/1994, but fell out of favor following the release of Mosaic for Windows and Netscape, after which Cello development was abandoned.[18][19][20][21][22][23][A 1][24]

Cello was first publicly released on 8 June 1993.[1] A version 2.0 was announced, but development was abandoned. Version 1.01a, 16 April 1994, was the last public release.[25][26] Since then, the Legal Information Institute at Cornell Law School has licensed the Cello 2.0 source code, which has been used to develop commercial software.[26][27][28]

The browser is no longer available from its original homepage.[A 2] However, it can still be downloaded from mirror sites.[A 3]

Development and history

The icon prior to version 1

The development of Cello started in 1992, with beta versions planned for June 1993 and a release for July 1993.[29][30][31] It was publicly announced on 12 April 1993.[32]

The Legal Information Institute at Cornell Law School created the first law site on the Internet in 1992 and the first legal website in 1993. However, at the time, there were no web browsers for the Microsoft Windows operating system, which was used by most lawyers. Thus, to allow lawyers to use their website, the Legal Information Institute developed the first Windows-based Web browser.[33][34][35] This was made possible by a grant from the National Center for Automated Information Research.[A 4]

Although other browsers at the time were based on CERN's WWW libraries called libwww, PCs of the time were not powerful enough to run the UNIX-oriented code.[31] As a result, Thomas Bruce had to rewrite most of the WWW libraries to work on Microsoft Windows.[31] It should also be noted that unlike most commercial browsers at that time, Cello didn't utilize any of Mosaic's source code and thus had a different look and feel.[36][37]

Steven Sinofsky, president of the Windows division at Microsoft wrote in a June 1994 email: We do not currently plan on any other client software [in the upcoming release of Windows 95], especially something like Mosaic or Cello.[38][39][40][41] Nevertheless, on 11 January 1995, Microsoft announced that it had licensed the Mosaic technology from Spyglass, which it would use to create Internet Explorer.[41] On 15 August 1995, Microsoft debuted its own web browser Internet Explorer 1 for Windows 95. While it did not ship with the original release of Windows 95, it shipped with Microsoft Plus! for Windows 95.

Usage

When released in 1993, Cello was the only browser for the Microsoft Windows platform. Shortly after launch, Cello was being downloaded at a rate of 500 copies per day.[42] As such, it achieved a fair amount of use and recognition within the legal community, including a number of PC users with between 150,000 to 200,000 users.[31] In 1994, most websites were visited using either the Cello browser or the Mosaic browser.[43] Despite having fewer features than Mosaic, Cello continued to be used due to its simpler interface and lower system requirements.[44] Cello was praised for being easy to install, because it wasn't necessary to install Win32s or a TCP/IP stack for Windows 3.1.[45] Following the release of Windows 95, which offered a much better TCP/IP interface, Cello fell into disuse and was abandoned.[43][46]

By 1995, Cello, like the Mosaic browser, was overshadowed by two newer browsers: Netscape and Internet Explorer and fell into disuse.[47][48] By 1999, Cello was considered to be a "historical" browser.[49][50]

Cello is considered to be one of the early casualties of the Browser wars.[51]

Features

Cello had the following features:[52]

<templatestyles src="Div col/styles.css"/>

2

Unlike Mosaic, Cello did not have toolbar buttons, and instead commands were accessed through pull-down menus.[36]

Supported Protocols

Cello supported the following protocols: HTTP 1.0, Gopher (not Gopher+), read-only FTP,[58] SMTP mailing, Telnet,[59] Usenet,[60] CSO/ph/qi directly[61] and WAIS, HyTelnet, TechInfo, Archie, X.500, TN3270 and a number of others through public gateways.[8][42][54][59][62][63]

Supported FTP servers

Cello supported the following FTP servers: most Unix servers(including SunOS, System V, and Linux),IBM VM, IBM VM, VMS systems, Windows NT, QVTNet, NCSA/CUTCP/Rutgers PC servers,FTP Software PC server, HellSoft NLM for Novell.[53][58]

Internet Connection

Cello works best with a direct Ethernet connection, but it also supports SLIP and PPP dialup connections through the use of asynchronous sockets.[8] Cello has an integrated TCP/IP runtime stack.[45]

Release history

Cello's splash screen. Note that the image is not that of a cello, but rather a viola da gamba, its aristocratic predecessor
A screenshot of Cello 2.0 in development.

The following versions were released:[1]

16-bit Cello Releases
Version Date Development cycle Size (in kb) Download Notes
0.1[64] 9 June 1993 Beta  ? evolt
0.2[64][65] 14 June 1993 Beta  ?  ? Changelog
0.3[64][66] 16 June 1993 Beta  ?  ? Changelog
0.4[64][67] 18 June 1993 Beta  ?  ? Changelog
0.5[64][68] 24 June 1993 Beta  ?  ? Changelog
0.6[64] 30 June 1993 Beta  ?  ? changelog
0.8[54] 5 November 1993 Beta N/A N/A Changelog (Distinct version discontinued)
0.9[A 5] 12 November 1993 Beta-pre  ? [1]
0.9[A 6] 16 November 1993 Beta  ? [2] Changelog
0.9[A 7] 22 November 1993 WINSOCK alpha r9.2  ? [3]
1.0[53] 17 February 1994 Release  ? evolt
1.01  ? Release  ?  ?
1.01a [69] 17 March 1994 release 521[60] [4], evolt Changelog
2.0 N/A Alpha N/A N/A development ceased

Although Cello 2.0 had been announced, development ceased before a public release.[26]

IBM released a fix for their TCP/IP V2.0 stack so that Cello would work with OS/2 WinOS/2 on 9 February 1994.[70]

Browser Comparison Table

The following table shows how Cello compared to browsers of its time.

Comparison of Web Browsers
Browser Cello NCSA X-Mosaic NCSA Mosaic Netscape Navigator Spyglass Mosaic AIR Mosaic Internetworks Win-Tapestry IBM WebExplorer
Operating System Win UNIX Win Win Win Win Win Win OS/2
Version 1 2.4 .20-alpha 3 1 1.02 3.06 Beta 4 1.67 0.91
proxy No Yes No Yes Partial Yes Yes Partial Partial
extended html No No No Yes No No No No No
Performance
multithreading No No No Yes No No Yes Yes No
dynamic linking No No No Yes No No Yes No No
deferred image No No No Yes No Yes Yes Yes No
multi-pane No No No No No No Yes No No
multi-window No No No No No No No Yes No
Configurability
kiosk mode No No No No No Yes No No Yes
external players Yes No No Yes No No Yes Yes Yes
Integration
d&d to clipboard No No No No No Yes No Yes No
spawnable players No Partial Partial Yes Partial Yes Yes Partial Yes
search engine(Find) Yes No No Yes No No No No No
Navigation
hotlist No Yes Yes No Yes Yes Yes No Yes
bookmark Yes No No Yes No No No Yes No
folders Yes Yes Yes Yes No Yes Yes Yes No
categories (tags) No No No No No No No Yes No
menu/button bar No No Yes No No Yes No No No
import Yes No No Yes No Yes No Yes No
export Yes No No Yes Yes Yes No No No
annotation No Yes Yes Yes No No No Yes No
auto time stamp No No No Yes No No No No No
Source: Lua error in package.lua at line 80: module 'strict' not found.

Derivatives

  • The first edition of BURKS, a project to produce non-profit CD-ROMs of resources for students of Computer Science, was based on Cello.[71]
  • InterAp, by California Software Inc, was based on Cello and featured a web browser with Telnet, FTP, and a Visual Basic-compatible scripting language called NetScripts.[56]
  • A version of Lovelace came integrated with Cello.[72]

Technical

  • While originally Cello required the Distinct runtime stack, following the release of Cello Beta Version .8, Cello dropped support for Distinc, and became exclusively Winsock based.[54][73]
  • Originally, although Cello could run on OS/2, OS/2's implementation of WinSock had bugs that prevented Cello from accessing the Internet.[59] The bug, APAR #PN52335, was later fixed allowing Cello to properly work on OS/2.[59][70]

The user agent for Cello is: LII-Cello/<version> libwww/2.5 so the latest one is LII-Cello/1.0 libwww/2.5[74]

DDE support

Cello featured DDE support. OLE support and DDE client support were planned, but never released.[59]

An example of how to invoke Cello from a Microsoft Word macro.

Sub MAIN
ChanNum = DDEInitiate("Cello", "URL")
DDEExecute(ChanNum, "http://www.law.cornell.edu")
DDETerminate(ChanNum)
End Sub

System requirements

Cello has the following system requirements: [8][75][76]

Criticism

Cello was not very stable and its development halted early.[60]

Cello did not render graphics well and required that the user reload the webpage when resizing the window. Like most browsers at the time, Cello also did not support any web security protocols.[37] It was also said that Cello rendered html "crudely" and pages would appear jaggedly.[36][37][78]

Cello also had sub-par performance in accessing the Internet and processing hypermedia documents.[36][78]

See also

Annotations

<templatestyles src="Reflist/styles.css" />

Cite error: Invalid <references> tag; parameter "group" is allowed only.

Use <references />, or <references group="..." />

References

<templatestyles src="Reflist/styles.css" />

Cite error: Invalid <references> tag; parameter "group" is allowed only.

Use <references />, or <references group="..." />

Bibliography

  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.

Further reading

  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.

External links

  1. ↑ 1.0 1.1 1.2 Lua error in package.lua at line 80: module 'strict' not found.
  2. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  3. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  4. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  5. ↑ 5.0 5.1 5.2 Lua error in package.lua at line 80: module 'strict' not found.
  6. ↑ 6.0 6.1 6.2 Lua error in package.lua at line 80: module 'strict' not found.
  7. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  8. ↑ 8.0 8.1 8.2 8.3 8.4 Lua error in package.lua at line 80: module 'strict' not found.
  9. ↑ 9.0 9.1 Lua error in package.lua at line 80: module 'strict' not found.
  10. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  11. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  12. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  13. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  14. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  15. ↑ 15.0 15.1 Lua error in package.lua at line 80: module 'strict' not found.
  16. ↑ 16.0 16.1 Lua error in package.lua at line 80: module 'strict' not found.
  17. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  18. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  19. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  20. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  21. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  22. ↑ Lua error in package.lua at line 80: module 'strict' not found.(subscription required)
  23. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  24. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  25. ↑ 26.0 26.1 26.2 Lua error in package.lua at line 80: module 'strict' not found.
  26. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  27. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  28. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  29. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  30. ↑ 31.0 31.1 31.2 31.3 Lua error in package.lua at line 80: module 'strict' not found.
  31. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  32. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  33. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  34. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  35. ↑ 36.0 36.1 36.2 36.3 36.4 Lua error in package.lua at line 80: module 'strict' not found.
  36. ↑ 37.0 37.1 37.2 Lua error in package.lua at line 80: module 'strict' not found.
  37. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  38. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  39. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  40. ↑ 41.0 41.1 Lua error in package.lua at line 80: module 'strict' not found.
  41. ↑ 42.0 42.1 Lua error in package.lua at line 80: module 'strict' not found.
  42. ↑ 43.0 43.1 Lua error in package.lua at line 80: module 'strict' not found.
  43. ↑ Winsock Client Software Reviews. Web.archive.org. Retrieved on 2014-03-17.
  44. ↑ 45.0 45.1 Lua error in package.lua at line 80: module 'strict' not found.
  45. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  46. ↑ [5] Archived 5 March 2012 at the Wayback Machine
  47. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  48. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  49. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  50. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  51. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  52. ↑ 53.00 53.01 53.02 53.03 53.04 53.05 53.06 53.07 53.08 53.09 53.10 53.11 53.12 53.13 53.14 53.15 Lua error in package.lua at line 80: module 'strict' not found.
  53. ↑ 54.0 54.1 54.2 54.3 Lua error in package.lua at line 80: module 'strict' not found.
  54. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  55. ↑ 56.0 56.1 Lua error in package.lua at line 80: module 'strict' not found.
  56. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  57. ↑ 58.0 58.1 Lua error in package.lua at line 80: module 'strict' not found.
  58. ↑ 59.0 59.1 59.2 59.3 59.4 Lua error in package.lua at line 80: module 'strict' not found.
  59. ↑ 60.0 60.1 60.2 Lua error in package.lua at line 80: module 'strict' not found.
  60. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  61. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  62. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  63. ↑ 64.0 64.1 64.2 64.3 64.4 64.5 Lua error in package.lua at line 80: module 'strict' not found.
  64. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  65. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  66. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  67. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  68. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  69. ↑ 70.0 70.1 Lua error in package.lua at line 80: module 'strict' not found.
  70. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  71. ↑ 72.0 72.1 Lua error in package.lua at line 80: module 'strict' not found.
  72. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  73. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  74. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  75. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  76. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  77. ↑ 78.0 78.1 Lua error in package.lua at line 80: module 'strict' not found.


Cite error: <ref> tags exist for a group named "A", but no corresponding <references group="A"/> tag was found, or a closing </ref> is missing

Retrieved from "https://infogalactic.com/w/index.php?title=Cello_(web_browser)&oldid=32949"