All Projects → padraigfl → packard-belle

padraigfl / packard-belle

Licence: MIT license
Windows 98 React Component Library

Programming Languages

CSS
56736 projects
javascript
184084 projects - #8 most used programming language
HTML
75241 projects

Projects that are alternatives of or similar to packard-belle

packard-belle-desktop
Building website with packard-belle UI library and react-rnd
Stars: ✭ 44 (-65.35%)
Mutual labels:  osjs, windows98, reimplementation, web-desktop
win95-winxp icons
default icons from win{95,98,2000,xp}
Stars: ✭ 43 (-66.14%)
Mutual labels:  windows98, windows95
Winxp
🏁 Web based Windows XP desktop recreation.
Stars: ✭ 4,717 (+3614.17%)
Mutual labels:  reimplementation, web-desktop
Os.js
OS.js - JavaScript Web Desktop Platform
Stars: ✭ 5,864 (+4517.32%)
Mutual labels:  osjs, web-desktop
Slide
MasahiroSaito's Slides Repository
Stars: ✭ 12 (-90.55%)
Mutual labels:  remark
Remark
remark is a popular tool that transforms markdown with plugins. These plugins can inspect and change your markup. You can use remark on the server, the client, CLIs, deno, etc.
Stars: ✭ 4,746 (+3637.01%)
Mutual labels:  remark
strip-markdown
plugin remove Markdown formatting
Stars: ✭ 84 (-33.86%)
Mutual labels:  remark
remark-highlight.js
Legacy plugin to highlight code blocks with highlight.js — please use `rehype-highlight` instead
Stars: ✭ 58 (-54.33%)
Mutual labels:  remark
remark-autolink-headings
Legacy remark plugin to automatically add links to headings — please use `rehype-autolink-headings` instead
Stars: ✭ 63 (-50.39%)
Mutual labels:  remark
gatsby-remark-design-system-example
Example page for "gatsby-remark-design-system"
Stars: ✭ 13 (-89.76%)
Mutual labels:  remark
remark-directive
remark plugin to support directives
Stars: ✭ 137 (+7.87%)
Mutual labels:  remark
React Markdown
Markdown component for React
Stars: ✭ 8,047 (+6236.22%)
Mutual labels:  remark
remark-jsx
A simple way to use React inside Markdown.
Stars: ✭ 29 (-77.17%)
Mutual labels:  remark
cache
A cache for @remark-embedder
Stars: ✭ 12 (-90.55%)
Mutual labels:  remark
DreeRally
Death Rally engine reimplementation
Stars: ✭ 68 (-46.46%)
Mutual labels:  reimplementation
unist-util-select
utility to select unist nodes with CSS-like selectors
Stars: ✭ 41 (-67.72%)
Mutual labels:  remark
gatsby-remark-numbered-footnotes
A small plugin to change named footnotes to numbered footnotes in your Gatsby pages using Markdown.
Stars: ✭ 15 (-88.19%)
Mutual labels:  remark
The-Great-Escape-in-C
Classic ZX Spectrum game "The Great Escape" rewritten in portable C
Stars: ✭ 95 (-25.2%)
Mutual labels:  reimplementation
win95
Windows 95 Portfolio built with Vue.js
Stars: ✭ 83 (-34.65%)
Mutual labels:  windows95
nox-decomp
Unofficial Nox (2000) port to Linux using decompiled code from https://playnox.xyz
Stars: ✭ 21 (-83.46%)
Mutual labels:  reimplementation

Packard Belle: A nostalgic component UI

Coverage Status Build Status Maintainability

The primary object of this project is to further my knowledge of various browsers and see how far I can push CSS.

Components previewable at http://packard-belle.herokuapp.com/

Demo site previewable https://packard-belle.netlify.com

Demo site source https://github.com/padraigfl/packard-belle-desktop

Goals

1. To create a CSS framework that mimics my first home computer

A CSS framework primarily because this is mainly a CSS and browser learning experiment. On top of that I suspect the component behaviour can swap out styles to effectively work as skins with minimal additional changes for a fairly wide range of desktop UIs

2. To create a component library which mimics standard desktop behaviours

Following on from 1, the goals of this step are to initially mimic the behaviours of my first computer as close as possible. Where CSS either doesn't work, or provides an unsatisfactory solution (e.g. cursor triggered dropdown menus), the goal is to use the most globally acceptable javascript as I can find to trigger the required changes. For certain components (e.g. select boxes), I'm using quick solutions for now, ain't nobody got the time for that stuff.

Code quality needs improvement currently as the hacking out a working model is largely done.

3. Build a website utilising the components

To be done, I hope to do this in the next few weeks and expand and refine the necessary components as needed.

Scripts

  1. npm run build For building storybook
  2. npm run build:css For exporting CSS framework (needs work)
  3. npm run build:module For building ES and CJS outputs

Indexing

Thanks to @cryiography for the script to autogenerate these

Name Docs Dir Source
Button N/A source dir /Button.js
ButtonForm N/A source dir /ButtonForm.js
ButtonIconLarge N/A source dir /ButtonIconLarge.js
ButtonIconSmall N/A source dir /ButtonIconSmall.js
ButtonNav N/A source dir /ButtonNav.js
ButtonProgram N/A source dir /ButtonProgram.js
ButtonStart N/A source dir /ButtonStart.js
DetailsSection N/A source dir /DetailsSection.js
ExplorerView N/A source dir /ExplorerView.js
FormCheckbox N/A source dir /index.js
FormFakeSelect N/A source dir /index.js
FormInputText N/A source dir /index.js
FormRadio N/A source dir /index.js
FormSelect DOCS source dir /index.js
FormSelectBox N/A source dir /index.js
FormSelectBoxSimple N/A source dir /index.js
FormToggle N/A source dir /index.js
Frame N/A source dir /Frame.js
Icon N/A source dir /Icon.js
IconExplorerIcon N/A source dir /IconExplorerIcon.js
IconListIcon N/A source dir /IconListIcon.js
MenuBar N/A source dir /MenuBar.js
ResizableIconsList N/A source dir /ResizableIconsList.js
StandardMenu N/A source dir /StandardMenu.js
StandardMenuHOC N/A source dir /StandardMenuHOC.js
StartMenu N/A source dir /StartMenu.js
TaskBar N/A source dir /TaskBar.js
Window N/A source dir /Window.js
WindowAlert N/A source dir /WindowAlert.js
WindowExplorer N/A source dir /WindowExplorer.js
WindowProgram N/A source dir /WindowProgram.js

Credits

Build tools largely created with help of https://hackernoon.com/making-of-a-component-library-for-react-e6421ea4e6c7

Font created using http://www.pentacom.jp/pentacom/bitfontmaker2/

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].