What is this, a webapp for ants?!
It has to be at least three times as styled!
Topcoat – CSS for clean and fast web apps
71–80 of 101 posts
Re: Topcoat – CSS for clean and fast web apps
#72I realize we're all in our early 20s with 20/15 vision, but this trend of microscopic fonts is really unfriendly to the old guys who sometimes want to read things on the web.
Hell I'm 25 and struggled with some of those font sizes. I probably do need to get my prescription altered, however.
Re: Topcoat – CSS for clean and fast web apps
#73Your "slide switch", "toggle buttons", "tabs", etc all suffer from the same big problem: hard to tell which one is selected (especially if there's 1 "on", 1 "off").
Those don't seem to be implemented yet.
Re: Topcoat – CSS for clean and fast web apps
#74I find it kind of odd and off putting that Adobe makes you sign something to contribute to the project. I think the only proper way to do switches is by using checkboxes and CSS transformations [0] - their javascript solution is not desirable.
Re: Topcoat – CSS for clean and fast web apps
#75Is it just me, or is the proliferation of CSS frameworks and JS frameworks/libs redundant now?
Yeah. The plague of javascript libraries and CSS frameworks is becoming rather tiresome.
Re: Topcoat – CSS for clean and fast web apps
#76Earlier quoted context omitted.
I think this is exactly what Skeleton tries to be. http://www.getskeleton.com/ I will say though that Foundation is much easier to customize styles for than Bootstrap, which is one of the primary reasons we now use Bootstrap for internal apps or side projects which we don't intend to implement a custom design, but Foundation for all sites which we plan on designing.
I'm using Foundation on a project as well and I still find it a big pain to override the styles. I end up writing more CSS to override styles I don't want than I would if I just wrote everything from scratch.
Really? We've implemented completely custom designs on top of Foundation for several sites now and haven't had any problems. Then again, we work to get the layout the way we like it with Foundation before we start designing, maybe that's why.
For us, things like buttons required a ton of overriding with Bootstrap when we customized the button design, but Foundation didn't. We found this largely to be the case because Foundation makes less assumptions about how buttons are styled to begin with. For example, buttons are pretty basic with square corners. If you want rounded corners, you just add the "round" class. If you want buttons with a different radius, you just create your own new class with a specific border radius and add that. Different color? Create a new class with a background color and add that.
What in Foundation did you experience pain trying to override?
Re: Topcoat – CSS for clean and fast web apps
#77One of topcoat's goals is to be highly performant CSS (especially on mobile, it's hard to deliver fast UI). To this end they're using the Chromium Telemetry project to benchmark the performance of their CSS continually. Basically CSS Performance Regression Testing. See http://bench.topcoat.io/ and http://bench.topcoat.io/v2/view/results?date=30& ; (metrics for time spent in recalc styles, layout, paint, composite…
See that's the kind of sentence that should be on the homepage!
Re: Topcoat – CSS for clean and fast web apps
#78I'm finding it hard to think up ways that this differentiates itself enough from Foundation or Bootstrap to be useful -- and your website isn't providing me any reason why as well. Compare to http://twitter.github.io/bootstrap/ and http://foundation.zurb.com/ , which list some benefits right on the page -- you need people to instantly understand why they should use your framework over another css framework. Also, mak…
this framework should be seen more as a lightweight alternative to jquerymobile. While making hybrid apps with phonegap/cordova, too many people are relying too heavily on large javascript libraries which hurts performance,a small css framework like topcoat or ratchet, and a js library for architecture like angularjs, backbone.js and emberjs is a more ideal approach for hybrid apps than just throwing all of bootstrap, foundation or the sometime buggy jquerymobile
I still think jquerymobile is a good approach for hybrid apps because it is easy to learn and a full-stack framework and works on a large range of devices, one can only hope that webkit renders faster in the future
Re: Topcoat – CSS for clean and fast web apps
#79Earlier quoted context omitted.
One thing to keep in mind is that Skeleton has not seen a single commit in the past year, so it's not clear if the framework is going to be supported long-term. It's probably better as a blueprint for one's own homebrew minimalistic CSS framework.
So a framework needs to update every 6 months just because that would make you feel better about it? Also, your statement is factually incorrect. There was a single commit in the past year. If you had said that next month, you might have been correct. The author is on twitter...
1) Nitpick about 11 months vs 12 months. Are you adding any value to the conversation?
2) The author being on Twitter doesn't affect the 31 outstanding pull requests and the 52 issues filed against the GitHub repository. Again, I'm not clear what you're getting at.
Re: Topcoat – CSS for clean and fast web apps
#80Earlier quoted context omitted.
My problem with your question is the evergrowing lack of critical thinking on HN. I think even PG has eluded to it. What's the difference from Bootstrap? Why don't you view its source? Read through the framework's documentation? For one the default styling is significantly different than Bootstrap. The one thing I fondly miss about Slashdot is people would liberally tell you to RTFM when you asked something obvious t…
Then go back to slashdot and be rude there.
Suggesting someone to apply critical thinking is anything but. Your confrontational attitude is though. Another thing becoming of HN.