@dbashford morning, is there any mimosa option yet (with or without modules) so I can minify and bundle my css?
(I know about minify-css but I want to bundle it)
mimosa-combine
Awesome, will definitely use it! :)
Anyone having experience with CSS-plugins for REquireJS? Useful/bad idea?
I've never used them. Never really used any of the plugins.
So you have one global stylesheet for all of your application modules? iirc, you use EmberJS or Backbone? (You wanted to check Chaplin/Marionette later)
our apps are ember and backbone yeah
How do you manage modules with styles? Sorry if I ask so directly
we use stylus or sass and we break things up by component, css too. each page gets its own stylesheet and each page is responsible for pulling in the styles it needs via import/include
So you do a full page refresh everytime?
if we, for instance, bundled styles with a component to our local bower repository, then that component would get pulled in, its styles put in stylesheets, and we'd use either stylus imports or mimosa-combine to bring them together
full page refresh for what?
we don't currently have any lazily loaded modules if that is what you mean
Oh okay.
Yes, that'S what I meant.
I'm building a lazyload system with scripts, templates and styles.
So far scripts and templates work, now just missing out the styles.
Trying to find out how to import/inject styles the best way
if you figure it out and there's something that mimosa can do to help let me know
Thinking about adding a link(type) stuff into the page and dynamically add/remove them when modules are loaded. But that can only work outside of Mimosa (at least in the workflow I ahve in mind) after the page has been sent to the client.
The only way Mimosa could be helping me is by caring about RequireJS CSS-files and also put them into the build, which I am not sure sure it will do already. Do you have any information on that?
Hi folks -- just joined this chat. I was perusing the previous conversation and there seems to have been a strong request for 'gulp' style streams ... I just wanted to share my opinion that that doesn't sound like there doesn't seem to be a particularly compelling reason to attempt such a major re-architecting -- I think for essentially the same reasons as stated in this post about the broccoli build system (http://www.solitr.com/blog/2014/02/broccoli-first-release/)namely the gulp stream architecture seems like a semi-decent approach for compilation systems which map each input file to a unique output-- but its going to be really ugly for other types of systems (like stylus,sass, less, css, require-js, es6?) where there are files :
(whoops I hit enter to make a paragraph break by mistake ...)
(going to try that again ...)
Hi folks -- just joined this chat. I was perusing the previous conversation and there seems to have been a strong request for 'gulp' style streams ... I just wanted to share my opinion that that doesn't sound like there doesn't seem to be a particularly compelling reason to attempt such a major re-architecting -- I think for essentially the same reasons as stated in this post about the broccoli build system (http://www.solitr.com/blog/2014/02/broccoli-first-release/)
I was looking forward to seeing a comparison between broccoli and mimosa but the broccoli author didn't make one in his blog post ... I haven't seen any reason that the broccoli folks shouldn't just be using mimosa though ...
Can you see a reason for broccoli @dbashford? Is it 'worth' trying to do a public comparison?
Hi @breathe
Let me take a quick look at your situation.
Hi @anachron -- no situation -- just chatting because I came across the broccoli project and the reasons they listed for why they are not using gulp or the gulp approach reminded me of the github issues I saw where gulp vs mimosa was discussed
personally i'm kind of annoyed the ember folks feel the need to roll their own ... I suspect it will be awhile before they get anything like feature parity with mimosa
Well, brocolli really doesn't support all this requireJS stuff that mimosa does
on a unrelated note @anachron -- I saw you mentioned you are using the semantic-ui css framework -- are you using that library with ember.js?
Also, I am not quite sure they heard about Mimosa yet, they never mention it and Mimosa is not so mainstream.
@breathe nope, I am using it with Backbone + Marionette, which is free and not so hardly coupled like EmberJS or Angular.
SemanticUI is an awesome project and so far my favorite. Foundation 5, Boostrap 3 and UIkit 2 are nothing compared to SemanticUI (1.0 soon).
it looks quite nice and very well organized
You can run a quick startup project with Mimosa, Marionette and SemanticUI here: https://github.com/Anachron/satisfy
I've even included a loader that gets started on pageload and then finishes after your application started.
thanks I'll check it out!
You definitely should! :)
Yesterday I pushed out 0.1.0, I'm happy about any comments.
i'm kind of married to ember at this point -- semantic-ui looks like it wouldn't be any harder to use with ember than bootstrap (possibly easier)
Yeah, I agree, semanticUI is easier after using it for a few days, you keep using the same classes, all that changes is the context, which is pretty smart :) You can keep using EmberJS.
except for maybe cases like dimmer which move dom elements around ...
Fire up the app and you will like what you see, I am quite sure :)
Also its quite small, despite of JQuery, Backbone, Underscore and a few other libs :)
i'm downloading right now -- but i'm somewhere with a verrry slow internet connection
npm is installing all the necessary mimosa modules into my project dir ...
:)
Oh I see, good luck then ... you still need to download the npm modules and maybe some latest bower pushes :P
I hope you also like my asset management :+:
My internet connection sucked the missing "1" from my last smiley ...
@dbashford I wish the best for your kids, how are they now?
@breathe any updates on the Skeleton? Did you take a look?