Stories with Tag Icons

• What were the MS-DOS programs that the moricons.dll icons were intended for?

  permalink

  Posted: 2025-05-13 11:06:58

  Verbose tl;dr

  The moricons.dll file in Windows contains icons originally designed for Microsoft's abandoned "Cairo" operating system project. These icons weren't repurposed from existing applications but were newly created for Cairo's planned object-oriented filesystem and its associated utilities. While some icons depict generic concepts like folders and documents, others represent specific functionalities like object linking and embedding, security features, and mail messaging within the Cairo environment. Ultimately, since Cairo never shipped, these icons found a home in various dialogs and system tools within Windows 95 and later, often used as placeholders or for functionalities not explicitly designed for.

  Raymond Chen's blog post, "What were the MS-DOS programs that the moricons.dll icons were intended for?", delves into the historical mystery surrounding a set of 16x16 pixel icons found within the moricons.dll file, a component of older versions of Windows. These icons, depicting various graphical elements like scissors, a pencil, an airbrush, and musical notes, never seemed to appear anywhere in the Windows user interface, prompting the question of their intended purpose.

  Chen's investigation begins by acknowledging the community speculation that these icons were potentially destined for an unreleased or abandoned project. He explains that Windows 95 and its contemporaries allowed MS-DOS programs to specify custom icons within their program executable files. However, a common challenge was the limited disk space available on floppy disks, the primary distribution medium for software at the time. Including many icons, especially color icons, could significantly increase the size of a program's executable, making distribution on floppy disks more difficult.

  To address this, Microsoft developed the concept of shared icon libraries. These libraries, like moricons.dll, would store collections of icons that MS-DOS programs could reference, thus avoiding the need to embed the icons directly within their executables. An MS-DOS program could then specify the desired icon by referencing its index within the shared library, keeping the program's size smaller.

  Chen highlights how the Windows 95 resource compiler, the tool used to create program resources like icons, facilitated this process. Developers could define an icon resource and point it to the shared library, specifying the icon's index within the library. This mechanism enabled MS-DOS programs to utilize visually rich icons while minimizing their footprint.

  However, the mystery of the unused moricons.dll icons deepens with the realization that the icons appear to be specifically designed for multimedia applications, a domain not typically associated with MS-DOS programs. Chen postulates that these icons were likely created in anticipation of, or perhaps in conjunction with, a multimedia-focused extension or shell for MS-DOS. This hypothetical extension might have leveraged these icons to provide a more graphical interface for interacting with multimedia content under MS-DOS.

  Despite the lack of concrete evidence, the blog post concludes that the most plausible explanation is that these icons were indeed intended for such a multimedia extension or shell for MS-DOS. While the exact nature and fate of this potential project remain unknown, the icons serve as a tantalizing glimpse into a possible, yet unrealized, direction for the evolution of the MS-DOS environment. They stand as a testament to the rapidly changing technological landscape of the time and the various paths explored by Microsoft in the early days of Windows.

  • MS-DOS
  • moricons.dll
  • Icons
  • Windows 95
  • Windows
  • Operating Systems
  • History
  • Software
  • programming
  • Raymond Chen
  • The Old New Thing
  • Microsoft
  • DLLs
  • resources

  Summary of Comments ( 61 )
  https://news.ycombinator.com/item?id=43971616

  Verbose tl;dr

  Hacker News users discuss the mystery surrounding the unused icons in moricons.dll, speculating about their purpose and the development process at Microsoft. Some suggest the icons were placeholders for future features or remnants of abandoned projects, possibly related to Cairo or object linking and embedding (OLE). One commenter links to a blog post claiming the icons were for a "Mac-on-DOS" environment called "Cougar," intended to make porting Macintosh software easier. Other comments focus on the general software development practice of leaving unused resources in code, attributing it to factors like time constraints, changing priorities, or simply forgetting to remove them. A few users recall encountering similar unused resources in other software, highlighting the commonality of this phenomenon.

  The Hacker News post "What were the MS-DOS programs that the moricons.dll icons were intended for?" generated a moderate amount of discussion, with several commenters providing insights and speculation.

  One of the most compelling threads revolved around the purpose of these icons and why they seemed somewhat out of place for MS-DOS programs. Several commenters suggested that these icons were likely intended for a hypothetical or planned GUI environment for MS-DOS, which never fully materialized. They pointed to other similar initiatives from Microsoft around that time, like the short-lived "DOS Shell," as evidence that Microsoft was exploring graphical interfaces even before Windows 3.0 gained widespread adoption. This theory was supported by the more modern and detailed appearance of the icons compared to the simpler, character-based graphics typical of MS-DOS applications.

  One commenter specifically hypothesized that the icons might have been intended for a "Windows-like" file manager for MS-DOS, perhaps even a precursor to the later Windows File Manager. This idea resonated with others, who noted the resemblance of some icons to later Windows icons.

  Another user posited that these icons might have been utilized within the "MS-DOS Editor," suggesting they could have represented different file types or actions within the editor itself. However, this theory didn't gain much traction, with no other users confirming seeing icons in this context.

  A few commenters focused on the technical aspects, discussing the format of the icons and the tools used to extract them. They mentioned the resource hacker utility and the internal structure of DLL files. This discussion, while technical, offered insight into how these icons were discovered and examined.

  Finally, some comments simply expressed appreciation for the historical curiosity of the topic, enjoying the glimpse into a potential alternative path in the evolution of personal computing. They reflected on the rapid pace of technological change during that era and how these seemingly forgotten artifacts can offer fascinating glimpses into what might have been.

  While there wasn't a definitive answer regarding the intended use of the moricons.dll icons, the prevailing theory pointed towards a planned, but ultimately abandoned, graphical interface for MS-DOS. The comments collectively offered a blend of technical analysis, historical context, and informed speculation, painting a picture of Microsoft's experimentation in the transition from the command-line world of MS-DOS to the graphical world of Windows.

• Icônes

  permalink

  Posted: 2025-04-27 00:30:42

  Verbose tl;dr

  Icônes is a customizable, open-source icon family featuring over 1,500 icons designed for web, mobile, and desktop applications. It offers various styles (filled, outlined, bulk), sizes, and formats (SVG, PNG, font), allowing developers to tailor the icons to their specific project needs. The project emphasizes ease of use with simple integration via CDN, NPM, or direct download, and provides tools for generating custom icon sets and optimizing performance. Icônes is free to use under the MIT license, encouraging community contributions and ensuring its long-term availability.

  The web resource located at icônes.js.org presents itself as a meticulously curated assemblage of open-source icons, specifically designed and optimized for utilization within digital interfaces. It distinguishes itself from other icon repositories through a rigorous emphasis on both aesthetic quality and technical excellence. This commitment to high standards manifests in several key features. Firstly, each icon within the collection adheres to a consistent visual style, ensuring harmonious integration within a variety of design systems. This cohesive visual language contributes to a polished and professional appearance across applications employing these icons.

  Furthermore, the icons are crafted with an acute awareness of performance considerations. They are available in multiple formats, including SVG, optimized for scalability and crisp rendering across different screen resolutions and sizes. This attention to detail ensures that the icons remain visually appealing and performant regardless of the context in which they are deployed. The availability of various formats also provides developers with flexibility in integrating the icons into their projects, catering to different technical requirements and workflows.

  The website itself facilitates easy browsing and discovery of the extensive icon library. It features a search functionality enabling users to quickly locate specific icons based on keywords or visual similarity. This streamlined search process accelerates workflow and reduces the time spent searching for appropriate visual elements. Additionally, the website provides comprehensive documentation and usage guidelines, empowering developers to seamlessly integrate the icons into their projects. This supportive documentation ensures clarity and minimizes potential integration challenges.

  In essence, icônes.js.org positions itself as a comprehensive and meticulously curated resource for high-quality, open-source icons, placing a strong emphasis on both visual consistency and technical performance. The project aims to provide developers with a readily accessible and easily integrable library of icons, contributing to the creation of visually appealing and performant digital interfaces.

  • javascript
  • Icons
  • SVG
  • vector graphics
  • icon library
  • Web Development
  • Frontend Development
  • UI
  • UX
  • design
  • Open Source

  Summary of Comments ( 25 )
  https://news.ycombinator.com/item?id=43808443

  Verbose tl;dr

  Hacker News users generally praised Icônes for its simplicity, open-source nature, and customizability. Several commenters appreciated the lightweight design and the ability to easily copy SVG code. Some discussed the benefits of SVG over icon fonts, citing sharper rendering and better accessibility. A few users suggested potential improvements, like adding a search bar and improving the organization. One commenter pointed out the similar project, Feather Icons, and initiated a brief comparison of the two, with others weighing in on their respective strengths and weaknesses, particularly concerning style and license. Overall, the reception was positive, with many expressing interest in using Icônes for their projects.

  The Hacker News post for "Icônes" (https://icones.js.org/) has generated a modest number of comments, primarily focusing on the practicality and value proposition of the tool.

  Several commenters appreciate the simplicity and ease of use of Icônes for creating and customizing SVG icons. They highlight the benefit of having a single, lightweight tool that handles all aspects of icon generation, from choosing a base icon to tweaking its appearance and exporting it in various formats. The browser-based nature of the tool is also praised for its accessibility and convenience.

  Some users discuss the potential use cases for Icônes, such as creating custom icon sets for web projects or generating icons for personal use. The ability to fine-tune details like stroke width and corner rounding is seen as a valuable feature for achieving precise control over the final icon's appearance.

  A few commenters compare Icônes to other icon-related tools and libraries, noting its strengths and weaknesses. While Icônes may not offer the extensive library of pre-made icons found in some larger resources, its focus on customization and ease of use is viewed as a differentiating factor.

  There's a brief discussion on the technical implementation of Icônes, with one commenter mentioning the use of Preact and mentioning that the source code is readable. However, no in-depth technical analysis or critique is present in the comments.

  While generally positive, some commenters express reservations or suggest improvements. One commenter points out the lack of an option to specify the viewbox size, which can impact how the icon scales in different contexts. Another user mentions that the color picker is a bit too opaque.

  Overall, the comments paint a picture of Icônes as a handy and user-friendly tool for creating custom SVG icons, particularly for users who value simplicity and control over a vast library of pre-made assets. While some minor limitations are noted, the overall reception is positive.

• Iconography of the PuTTY tools

  permalink

  Posted: 2025-03-12 19:29:41

  Verbose tl;dr

  The PuTTY iconography uses a stylized computer terminal displaying a kawaii face, representing the software's friendly nature despite its powerful functionality. The different icons distinguish PuTTY's various tools through color and added imagery. For instance, PSCP (secure copy) features a document with a downward arrow, while PSFTP (secure file transfer protocol) shows a pair of opposing arrows, symbolizing bi-directional transfer. The colors roughly correspond to the traffic light system, with green for connection tools (PuTTY, Plink), amber for file transfer tools (PSCP, PSFTP), and red for key generation (PuTTYgen). The overall design prioritizes simplicity and memorability over strict adherence to real-world terminal appearances or symbolic representation.

  Simon Tatham, the author of PuTTY, provides a comprehensive explanation of the design choices behind the suite's various application icons. He begins by acknowledging the common confusion surrounding the seemingly arbitrary assignment of icons to specific tools. He then details the deliberate thought process that went into crafting each icon, emphasizing a systematic approach rooted in visual symbolism and the desire for clear differentiation.

  The core concept revolves around representing each tool's function through metaphorical imagery related to its purpose. For example, PuTTY itself, being a terminal emulator, is symbolized by a computer terminal window, albeit an abstract and simplified one to accommodate the small icon size. This window motif is then modified and augmented to represent the related but distinct functions of the other tools. PuTTYgen, used for key generation, adds a golden key to the basic window icon, signifying its role in creating cryptographic keys. Pageant, the key agent, features a tiara superimposed on the window, symbolizing its function as a "king" or manager of keys. PSCP, the secure copy tool, incorporates a document with a prominent downward-pointing arrow, visually depicting the action of copying files to a destination. PSFTP, the secure file transfer tool, uses a similar document icon but with upward and downward arrows, representing bidirectional file transfer. PLink, the command-line connection tool, displays a lightning bolt over the window, symbolizing its fast and direct connection capability.

  Tatham further elaborates on the practical considerations that influenced the icon design. He highlights the constraints imposed by limited resolution and the need for icons to be readily distinguishable, even at small sizes. This led to the adoption of simple, bold shapes and contrasting colors. He specifically addresses the choice of a yellow or gold color for elements representing security and encryption, aiming for a clear visual cue associated with these crucial functions. He also explains the deliberate use of distinct, easily identifiable shapes for each icon to prevent confusion among users.

  Finally, Tatham acknowledges the subjective nature of aesthetics and the potential for differing interpretations of the iconography. While acknowledging that the chosen symbolism might not be universally intuitive, he defends the internal consistency and logical basis of the design decisions, emphasizing the importance of having a clear and reasoned rationale behind the visual representation of the PuTTY tool suite.

  • PuTTY
  • ssh
  • Telnet
  • Terminal Emulator
  • Icons
  • Iconography
  • Software
  • Computer Networking
  • network tools
  • Simon Tatham
  • Free Software
  • Open Source
  • Windows
  • Linux
  • macOS
  • unix
  • Graphical User Interface
  • GUI

  Summary of Comments ( 82 )
  https://news.ycombinator.com/item?id=43346816

  Verbose tl;dr

  Hacker News users discuss Simon Tatham's blog post explaining the iconography of PuTTY's various tools. Several commenters express appreciation for Tatham's clear and detailed explanations, finding the rationale behind the choices both interesting and amusing. Some discuss alternative iconography they've encountered or imagined, while others praise Tatham's software and development style more generally, citing his focus on simplicity and functionality. A few users share anecdotes of misinterpreting the icons in the past, highlighting the effectiveness of Tatham's explanations in clarifying their meaning. The overall sentiment reflects admiration for Tatham's meticulous approach to software design, even down to the smallest details like icon choices.

  The Hacker News post "Iconography of the PuTTY tools" discussing Simon Tatham's blog post about the design of PuTTY's icons generated a moderate number of comments, mostly focusing on appreciation for Tatham's work and the quirky nature of the icons.

  Several commenters express admiration for Simon Tatham's technical skills and the impact of his software, with PuTTY being frequently mentioned as a vital tool. The whimsical, almost amateurish quality of the icons is a recurring theme, with some appreciating the charm and others finding them mildly irritating. The discussion touches upon the difficulty of creating distinct icons for closely related tools, acknowledging Tatham's attempt to provide visual differentiation.

  One commenter highlights the "hand-drawn" aesthetic of the icons, contrasting them with more polished, professional iconography. This sparks a brief side discussion about the evolution of computer graphics, with another user reminiscing about the early days of computing and the prevalence of simpler, less refined visuals. The limitations and constraints of earlier operating systems and display technologies are mentioned as a possible influence on the icon design.

  Another thread emerges around the functionality of PuTTY itself. Commenters share their experiences and preferences regarding SSH clients, with some expressing ongoing loyalty to PuTTY despite the availability of alternatives. The discussion briefly touches on the evolution of SSH clients and the enduring relevance of PuTTY.

  A few comments delve into the specific design choices of individual icons, attempting to decipher the logic behind them. The "network cable draped over a computer" interpretation of the PSCP icon is mentioned, as is the confusion surrounding the Pageant icon. The conversation underscores the challenge of creating intuitive and easily recognizable icons, especially for abstract concepts like network protocols or security tools.

  Overall, the comments reflect a mixture of nostalgia, technical appreciation, and mild amusement towards the idiosyncratic iconography of the PuTTY suite. The discussion demonstrates the lasting impact of Tatham's work and the continued relevance of PuTTY in the world of system administration and network engineering. There's a subtle undercurrent of respect for the software's functionality overshadowing any critique of its somewhat unconventional visual presentation.