Hello,

As provided in the Materializecss documentation, it should be possible to initialize an input with autocomplete data, but this option doesn't seems to exists in this package, is it normal ?

Thanks a lot in advance !

Seems the chips functionality hasn't been brought over to scss, maybe there's something I don't know about how to import it into Meteor.

Steps to recreate:

git clone https://github.com/Cypher1/Chips_test
or

1. Create a new meteor project
2. Copy and paste the code from http://materializecss.com/chips.html into a template.

Then
3. Run meteor and check out the root page, the chips currently don't load with the following error.

TypeError: $(...).material_chip is not a function
    at Blaze.TemplateInstance.<anonymous> (main.js:6)
    at blaze.js?hash=983d07a…:3341
    at Function.Template._withTemplateInstanceFunc (blaze.js?hash=983d07a…:3687)
    at fireCallbacks (blaze.js?hash=983d07a…:3337)
    at Blaze.View.<anonymous> (blaze.js?hash=983d07a…:3430)
    at blaze.js?hash=983d07a…:1783
    at Object.Blaze._withCurrentView (blaze.js?hash=983d07a…:2214)
    at blaze.js?hash=983d07a…:1782
    at Object.Tracker._runFlush (tracker.js?hash=9f8a0ce…:539)
    at onGlobalMessage (meteor.js?hash=e3f53db…:401)

please update the included font with the new material icons. Example: https://design.google.com/icons/#ic_delete_forever.

Or make it possible to overwrite the font path because when adding the font to the head it is overwritten after code hot push.

   While determining active plugins:                                                                                                                       
   error: conflict: two packages included in the app (angular2-compilers and fourseven:scss) are both trying to handle *.scss                              
   error: conflict: two packages included in the app (angular2-compilers and fourseven:scss) are both trying to handle *.sass

After re installing my app on another env I do have conflicts.

Any hint on how to solve this ? I do need angular2-compiers too.

From your Docs:

// If you want to override materialize sass variables you can uncomment the following:
@import "{poetic:materialize-scss}/sass/components/_color.scss";
$primary-color: color("blue", "lighten-2");

It is not working, I added it to my main.scss.

Hi after install, i've got this error message:

poetic_materialize-scss.js?hash=e807c00…:253
Velocity is already loaded. You may be needlessly importing Velocity again; note that Materialize includes Velocity.

installed (after remove materialize:materialize):

Changes to your project's package version selections:

fourseven:scss added, version 3.4.3
poetic:materialize-scss added, version 1.97.6_1

poetic:materialize-scss: Materialize (official): A modern responsive front-end framework based on Material Design

I can't seem to find a good description of the @import directive anywhere that explains the meaning of the { } construct?

For example, lines that you specify like:
@import "{poetic:materialize-scss}/sass/materialize.scss";

Or
@import "{}/client/_mycustom.scss";

Seem to work - but throw Errors when committing in my Webstorm editor like this:
Error:(6, 10) Cannot resolve import into sass/scss file

I assume the mean "root" directory of the projects.. but can't find any documentation to that effect.

Hello there.

I've started a meteor 1.3.1 app with your package and everything seems to work perfectly.

I've been trying to change the main colors of my app using the example:

/* Palette generated by Material Palette - materialpalette.com/teal/lime */

// If you want to override materialize sass variables you can uncomment the following:
@import "{poetic:materialize-scss}/sass/components/_color.scss";
$primary-color: color("blue", "lighten-2");

// $primary-color-dark:   #00796B;
// $primary-color:        #009688;
// $primary-color-light:  #B2DFDB;
// $primary-color-text:   #FFFFFF;
// $accent-color:         #CDDC39;
// $primary-text-color:   #212121;
// $secondary-text-color: #727272;
// $divider-color:        #B6B6B6;

// import main scss file
@import "{poetic:materialize-scss}/sass/materialize.scss";

Note that I have tried adding custom colors.

I added a background color with blue class to see if it changes the hex color but just gives me the same one after uncommenting the lines to override materialize variables.

How does exactly changing the default variable color works?

Thanks!

edit

Also, I added the normal buttons like this:

<div class="card-action">
  <a class="waves-effect waves-light btn">Login</a>
  <a class="waves-effect waves-light btn-flat">Register</a>
</div>

the login one appears with the teal color still and not the primary one. I'm not sure if this is the normal behavior

the package is not auto includin or initializng js to the project. When i include the script tag to the project it works, but shows dupicity.

Velocity is already loaded. You may be needlessly importing Velocity again; note that Materialize includes Velocity.

I've isolated a problem in my mobile navbar not displaying to be a result of upgrading to version 1.97.6_1. Screen opacity changes but nothing else. Downgrading to 1.97.5_2 solves this issue.

https://github.com/poetic/meteor-materialize-scss/blob/meteor/sass/components/_variables.scss

I'm trying to change the input background color

// If you want to override materialize sass variables you can uncomment the following:
@import "{poetic:materialize-scss}/sass/components/_color.scss";
$primary-color-dark:   #0288D1;
$primary-color:        #03A9F4;
$primary-color-light:  #B3E5FC;
$primary-color-text:   #FFFFFF;
$accent-color:         #FF5722;
$primary-text-color:   #212121;
$secondary-text-color: #727272;
$divider-color:        #B6B6B6;
$secondary-color:      white;
$input-background: black;

// import main scss file
@import "{poetic:materialize-scss}/sass/materialize.scss";

All of the variables seem to work, but trying to change the input-background doesn't work.

Also, I'm confused since the inputs background default says that it's suppose to be white (#fff) but they are showing transparent.

Hi, how do materialize parallax work with meteor? Do i need to import the plugin?

when @import "{poetic:materialize-scss}/sass/materialize.scss";, the styles are loaded twice in browser.

fourseven:scss seems to bundle in all of the Materialize SCSS. When adding the @import "{poetic:materialize-scss}..." statements to the last loaded SCSS file, the (mostly) same styles get bundled again.
Is this an issue with fourseven:scss? Is there a way to specify that we only want the Materialize SCSS explicitly loaded via an @import statement?
Thanks in advance!

I'm using angularjs for a project, I've notice that this function CharacterCounter() already gets executed when refreshing the current page, but when I browser states in my app, when I go back to that input it doesn't have the CharacterCounter.

I tried executing manually the function when entering that state and it works, but when I refresh the page with the input (with my manual CharacterCounter() initialization function) it gets executed twice, resulting in a weird character counter render.

Is there a way to make CharacterCounter() not get executed when you first visit the app and only execute if I initialize it?

Thanks!

New materializecss version was released a few days ago, would be nice if it was updated. Thanks

Hi New materializecss version was released last month, would be nice if this package could be updated to V0.97.7. Thanks :)

Whenever I try to do it, it forks from the Materialize repo, not your (probably because your repo is itself a fork), and I lose all your changes.

I have followed all steps to install this package and also imported using this
client/main.scss
@import "{poetic:materialize-scss}/sass/materialize.scss";

but it seems materialize is not working or loading. Please review.

I'm not entirely sure why I'm getting this. I've taken source code from a working project and copied it to a newly created meteor project. Not sure what to do with it.

While processing files with fourseven:scss (for target web.browser):
/client/pages/loading/loading.scss: Scss compiler error: File to import: {poetic:materialize-scss}/sass/materialize.scss not found in file: ../../app.scss

Changing over to this package from materialize:materialize I ran into an issue. I happen to be importing an app-specific scss partial called _global.scss, from a directory called components. Obviously this conflicts directly with the materialize namespace. I was getting wierd clobbering issues, and it took me a little while to figure out the collision.

Which brought this to mind: It might cool to try to detect namespace collisions during compilations and let the user know. Might not be a feature for this package, maybe one for fourseven:scss? Dunno, just mentioning it. Thanks for the package!

Every time the sidenav menu is displayed a set of two divs is generated (sidenav-overlay and drag-target). When removing the menu, they are not removed properly, they stack up with every call.
It needs several clicks before underlying elements can respond to events.