Split out jeet grid system about jeet HOT 4 CLOSED

Hey Jeff!

We're actually dumping all our efforts into J3's new grid system which is going to be bad-fucking-ass and the Stylus flavor will probably be done and tested by early next week and the SCSS/SASS version will be done by late next week.

The tools and stuff are part of the allure of Jeet (IE7+, jQuery, etc. out of the box) so I doubt we're going to get rid of them. It might be a better idea for you to fork Jeet for Roots anyway since we regularly do a lot of changes and stuff to the system itself which might throw some of your users for a loop.

I'm big on "cutting edge > user experience" (at least until I get to a point where I'm happy with it) so that causes a lot of problems. XD

from jeet.

Ah awesome! Where is development happening for that? Would love to keep up with it.

I wasn't suggesting that you drop the tools, I was just suggesting that you separate out the grid to it's own repo, then include it in base jeet. So you'd have the jeet grid, then the jeet build system. Na'mean? Just keeping things modular, not dropping anything.

I agree that it's important to have it like you want, which is why you can use semver for these types of things, which allows you to move quickly but also notify your users when there are updates that might break their code. If you properly version your code and keep track of changes, not only can you stay on the cutting edge, but your users will be able to upgrade intelligently without having all their shit break with no warning when you push new stuff : )

from jeet.

#54

A friggin' animator for LA Noire and Saints Row 4 just surprised me one morning with a metric ton of complicated math that helps keep consistent gutter sizes as you nest columns. We've been working on it ever since trying to make sure it's clean and as usable as possible. I think we're getting close and he's supposed to be putting the finishing touches on it this weekend.

I'm awfully lazy and probably won't port it to it's own repo. To be honest I just don't want to separate it from the rest of the framework in case someone is actually Downloading the Zip manually, and I don't want to maintain a separate fork of it and I'm a fussy butt who needs a nap and has a billion things to do. :'(

The semver thing is pretty sweet though. I'm definitely going to pay attention to version control and the npm package and all kinds of other crap with Jeet 3.

Keep in mind, Jeet 3 won't officially be launching for a while (few weeks). I want to make some really nice/flexible UI stuff for it so people don't keep resorting to Bootstrap and it's ilk, but rather go, "Holy crap, have you seen that Jeet framework? You have 10 different button styles and can feed it button colors/radius like so: btn(blue, 5px, flat)." (note: it already has this specific ability but I'm just going to beef up the entire UI kit including forms and all kinds of good defaults instead of Normalize's crappy typography.

from jeet.

Wow, that is insane. Looks great, super exciting. I totally agree with the rest, that's been my goal with axis from the start. We can continue this discussion in static-dev/axis#80 though since we already have so much text and a bunch more people : )

from jeet.