Comments (9)
Thanks for the love, I am on it.
What I want to know: what should a basic example should include?
It is clear that elbow and the grid has to be explained.
But there are always so many details to be solved and thought of.
I would really love get input from you guys out there.
Live long and prosper!
from lcars.
from lcars.
Two illustrations I'd like to see. Maybe seperate or maybe they can be done in one demo. Lots of comments in the code would help.
-
My main question is about how to lay things out (the grid, as you say). Avoiding the included header, footer (and maybe container classes) would be helpful in this instance, to see how the components behave in more varied scenarios. Any fundamental rules of layout that are worth mentioning would be helpful, for example; it seems that the top level (inside ) should be lcars-row and lcars-column elements, which will contain the components. The elbow could be an advanced illustration in this demonstration.
-
A demo of all the other / more exotic components compenents in action; I see lcars-element-addition and lcars-element-decorator but I can't figure out how to make them work.
Keep up the good work. I'm finding lots of fundamental flaws in my code and reworking it. Eventually I'll be in a position to make some nice applications with this libarary. I'm commited.
Qapla' ! :)
from lcars.
Everyone has made good suggestions here, and #13 and #19 inform the discussion further, I think. I propose:
First defining the standard basic/typical layouts, and then creating a templateX.html file for each. These should be clean and well commented inside to illustrate the way rows and columns work, and how to nest correctly, which CSS classes are too-specific to use in all situations, etc. The highlights of these source comments might be summarized and placed in the content of the project's main index.html/documentation page.
Lastly, build off of the work done in the standard templates to create the more complex example. Again, a little source embedded comments to show where you had to add some styling or where special considerations for order of nesting and so on.
For the initial basic standard template set, I refer to "The LCARS Frame" section of The LCARS Manifesto . I illustrate, and (add a fifth type) here:
_ _________________ _
(_| |_________________| |_)
Type 1 Template
_ _________________ _
(_| |_________________| |_)
_____________________ _
/ _________________| |_)
/ /
| |
| | Type 2 Template
| |
| |
| |
\ \_________________ _
\____________________| |_)
___
| | Type 3 Template
\ \_______________________
\__________________________|
__________________________
/ ______________________|
/ /
| |
| |
| |
|___|
_____ _______________
| \ / |
|____ \ / _______________|
\ | | /
| | | | Type 4 Template
| | | |
| | | |
| | | |
| | | |
____/ | | \______________
|______/ \________________|
_________________
/ |
/ _______________|
| /
| | Type 5 Template
| |
| |
| |
| |
_______/ |
|_________/
from lcars.
I have done some quick templates for types 1 and 2.
templates.zip
For the others, I think the file lcars.css would need to be modified.
from lcars.
Done template type 3
from lcars.
@physnoct I took a quick look at type1 and it looks really good to me. Very clean on the inside, scroll and resize behavior is what I would expect. Really nice. Tested on chrome on Windows.
I wonder what you and what @joernweissenborn think about possibly including so called "responsive" css class changes for the grid size. What I mean is: when screen is pretty big, maybe lcars-u-5 should be replaced with lcars-u-8 (automagically with javascript).
Perhaps, @physnoct, you would like to fork the repository and put your templates thus far into a Pull Request? I'd like to see type 3 as well.
from lcars.
Here is the type 3 template
type3.html.gz
from lcars.
@physnoct I just tried type 3 and it looks really nice overall, but I found that content I was putting into the main container is up underneath the header area. Maybe there is a class missing ? Or some kind of spacer needed?
from lcars.
Related Issues (20)
- lcars-title class should have character glyphs same height as parent bar element, visually HOT 7
- Automatic audio wireup selector makes omissions, demo/doc page example missing button class
- Gulpfile configured for older version HOT 1
- Simplify Audio section documentation
- Short filenames HOT 2
- Audio module bugs
- elements / buttons in thin/horizontal elbow-bars
- brackets to support text content HOT 5
- Questions about rows and columns HOT 3
- Input HOT 15
- Documentation request: How do I incorporate this project? HOT 20
- Need good default styling for html tables
- Rename `master` to `main` HOT 9
- Demo/doc left-hand side-bar navigation has too many buttons HOT 3
- Compiled CSS contains a few unnecessarily long floating point representations of irrational numbers
- Simple Red Alert effect
- Expand contributing section of readme
- Is it possible to have a tutorial to realize something like www.thelcars.com template? HOT 3
- Getting LCARS to work with React HOT 3
- Documentation - Areas for improvement
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from lcars.