427 comments found.
Is it possible to have normal form controls? i dont want to use the material design form controls. any option ?
Hey! Yes you can use normal form controls beside the material ones. Just use a <input> instead of <material-input-container>. 
Hello, I getting error when i run ‘ng serve’ command
ng serve
Cannot read property 'config' of null
TypeError: Cannot read property 'config' of null
at Class.run (/Users/user/Workspaces/Test/GetDocuments/node_modules/@angular/cli/tasks/serve.js:21:63)
at check_port_1.checkPort.then.port (/Users/user/Workspaces/Test/GetDocuments/node_modules/@angular/cli/commands/serve.js:110:26)
at process._tickCallback (internal/process/next_tick.js:109:7)
My Environment
@angular/cli: 1.2.0 node: 6.10.3 os: darwin x64 @angular/animations: 4.2.5 @angular/common: 4.2.5 @angular/compiler: 4.2.5 @angular/core: 4.2.5 @angular/flex-layout: 2.0.0-beta.8 @angular/forms: 4.2.5 @angular/http: 4.2.5 @angular/material: 2.0.0-beta.7 @angular/platform-browser: 4.2.5 @angular/platform-browser-dynamic: 4.2.5 @angular/router: 4.2.5 @angular/cli: 1.2.0 @angular/compiler-cli: 4.2.5
Please help Thank you.
Ok, I found the solution, ’.angular-cli.json’ is missing in project because i copy code from fury-source folder to my new folder.
but
I found new error when run ‘ng serve’ command isERROR in /fury-source/src/app/demo/apps/chat/chat.component.ts (31,23): Property 'elementRef' is private and only accessible within class 'PerfectScrollbarComponent'. ERROR in /fury-source/src/app/demo/apps/chat/chat.component.ts (31,76): Property 'elementRef' is private and only accessible within class 'PerfectScrollbarComponent'.
Thank.
Great to hear you figured out the issue yourself! Hope you enjoy our template. 
Why in the past two weeks do not answer my question?
Hi, I have a problem with how SidenavService is implemented. How can I implement my own side-nav menu without touching any files in the core folder? I know I can call addItem method on SidenavService to add a menu item but how do I clear all the default menu items without editing SidenavService?
It is important to me that the core files remain untouched in order to have an easy time updating in the future. Let me know if I am missing something here.Why not implement all demo code inside the demo app and leave the core folder without any custom content? That would be a cleaner more maintainable approach in my opinion.
Ok, so it seems I expected contents of ‘core’ folder to be generic with hooks to pass in custom content and configurations but this is not the case. I will just edit the core files directly. It would be much better though if the core files were generic enough to be reused ‘as is’ because it would be much easier to simply overwrite all corefiles whenever there is an update…
It’s not really possible or developer friendly to pass all content to the core, even though this seems like a great idea. We’ll consider this and will see how it works out. Thanks for the feedback! 
My point was, demo menu items are hard-coded in sidenav service without a way to clear / replace them other than to edit the sidenav service in the core… This is the same for other things too. My idea was that core files should be implemented in such a way that there is no need to modify them directly hence making them easier to update… So as an example, you could add this method in sidenav service to allow for removal of default (demo) menu items…
/**
* Remove all menu items
* @param item
*/
removeAllItems() {
this._items = [];
this._itemsSubject.next(this._items);
}
We’ll look into this. Thanks for the detailed explanation!
When will Angular 4 support be ready?
The template IS supporting Angular 4. It’s already updated. 
Thank you! Any incompatibilities and issues between Angular 4 and Angular Material 2 within this theme?
No, nothing! We updated all dependencies, updated the code and everything is working fine! 
Your title says that your theme works on Angular 4, but the description says Angular 2.
Is this Angular 4 or Angular 2?
The theme was initially build with Angular 2, but we updated it to Angular 4. 
In your latest update, please check mail app inbox layouts. When i click on the message to read, the message text and some elements are mixed.
We’ll look into this and provide a fix, thanks for the feedback! 
I am trying to add a dynamic route which has a route of store/{id} with {id} being the id of the store.
Therefore during the sidenav.service looking for a matching URL it doesn’t find a match as I would have to code in all possible id values. Is there anyway for this to work with a more flexible search such as ‘store/*’ or the component pushes a new entry in to the service itself so that the name of the route is dynamic too….i.e. the name of the store
Thanks in advance
Any chance of an answer? I thought once bought it was a 2 day SLA ?
Hey! Thanks for your feedback and sorry for the way too late response! For this to work properly we’ll have to add another attribute to the Sidenav Model and implement some functionality. We’re currently working on the next update, but will try to implement this very soon. I hope this is okay for you and we hope you enjoy the template. If you have any further questions just let us know. 
I just bought Fury, is the source on github?
thanks tony tony@leotta.comYes, we’ll soon provide Github access. 
Hi,
i purchased and using this theme, all works fine, but i stuck with material autocomplete/Typehead control.
can you please guide me how to do the remote data retrieval in the autocomplete/typehead.
something like this. http://plnkr.co/edit/?p=preview
how can i acheive this in Fury theme in material design
Please assist.
Thanks in advance
in app/core/sidenav/sidenav.service.ts
constructor(snackbar: MdSnackBar) { let menu = this;
let dashboard = menu.addItem('Dashboard', 'dashboard', '/', 1);
menu.addItem('Inbox', 'mail', '/apps/inbox', 1, '22', '#7986CC');
menu.addItem('Chat', 'chat', '/apps/chat', 2, '14', '#E15C74');
menu.addItem('Calendar', 'date_range', '/apps/calendar', 3);
// let components = menu.addItem('Components', 'layers', null, 3);
// menu.addSubItem(components, 'Autocomplete', '/components/autocomplete', 1);
// menu.addSubItem(components, 'Buttons', '/components/buttons', 2);
// menu.addSubItem(components, 'Cards', '/components/cards', 3);
// menu.addSubItem(components, 'Dialogs', '/components/dialogs', 4);
// menu.addSubItem(components, 'Grid List', '/components/grid-list', 5);
// menu.addSubItem(components, 'Lists', '/components/lists', 6);
// menu.addSubItem(components, 'Menu', '/components/menu', 7);
// menu.addSubItem(components, 'Slider', '/components/slider', 8);
// menu.addSubItem(components, 'Snack-Bar', '/components/snack-bar', 9);
// menu.addSubItem(components, 'Tooltips', '/components/tooltips', 10);
}
// let forms = menu.addItem('Forms', 'insert_comment', null, 4);
// menu.addSubItem(forms, 'Form Elements', '/forms/form-elements', 1);
// menu.addSubItem(forms, 'Form Wizard', '/forms/form-wizard', 1);
// let tables = menu.addItem('Tables', 'format_line_spacing', null, 5);
// menu.addSubItem(tables, 'Simple Table', '/tables/simple-table', 1);
// menu.addSubItem(tables, 'Fixed Header Table', '/tables/fixed-header-table', 2);
// let maps = menu.addItem('Maps', 'map', null, 6, '3', '#4CAF50');
// menu.addSubItem(maps, 'Google Maps', '/maps/google-maps', 1);
// let icons = menu.addItem('Material Icons', 'grade', '/icons', 7);
// let customPages = menu.addItem('Custom Pages', 'web', null, 8);
// menu.addSubItem(customPages, 'Login Page', '/login', 1);
// menu.addSubItem(customPages, 'Register Page', '/register', 2);
// menu.addSubItem(customPages, 'Forgot Password', '/forgot-password', 3);
// menu.addSubItem(customPages, 'Dashboard v1', '/dashboard-v1', 4);
// let dragAndDrop = menu.addItem('Drag & Drop', 'mouse', '/drag-and-drop', 9);
// let editor = menu.addItem('WYSIWYG Editor', 'format_shapes', '/editor', 10, 'NEW', '#3F51B5');
// let multiLevel = menu.addItem('Multi-Level Menu', 'menu', null, 11);
// let level1 = menu.addSubItem(multiLevel, 'Level 1', '/level1', 1);
// let level2 = menu.addSubItem(level1, 'Level 2', '/level1/level2', 2);
// let level3 = menu.addSubItem(level2, 'Level 3', '/level1/level2/level3', 3);
// let level4 = menu.addSubItem(level3, 'Level 4', '/level1/level2/level3/level4', 4);
// let level5 = menu.addSubItem(level4, 'Level 5', '/level1/level2/level3/level4/level5', 5);
// let dynamicMenuFunctionDemo = () => {
// let dynamicFunction = () => {
// let snackbarRef = snackbar.open('This menu item got added dynamically!', 'Remove item', <MdSnackBarConfig>{
// duration: 5000
// });
// snackbarRef.onAction().subscribe(() => {
// menu.removeItem(dynamicMenu);
// });
// };
// let dynamicMenu = menu.addItem('Dynamic Menu Item', 'extension', dynamicFunction, 12);
// };
// let addMenu = menu.addItem('Add Menu Item', 'add', dynamicMenuFunctionDemo, 99, null, null, 'add-dynamic-menu');
toolbar wil not show up properly , please tell me how to display propely..
Hey! Thanks for getting in touch with us. We are not sure what the issue is here, as you just copied some of the code of the sidenav.service.ts? The code for the toolbar is in the toolbar folder in toolbar.component.ts if that’s your question. If this does not answer your question, please get in touch with us at support@martinsuess.com with a more detailed description of what the issue is and we’ll get back to you. 
i have read many times this theme’s code,i still have some trouble. 1. In sidenav-service,when you use _currentlyOpenSUbject.next(currentlyOpen),in all project,there no observer subscribe to currentlyOpen$.I think it is not necessary to declare the _currentLyOpenSubject . 2.In left sidenav,when i click item named components(it has many subItems),then subItems show.But the click listener named “toggleDropdown” have no code about these. at last, when i debug these,i found you use [style.hight]=”getSubItemsHeight”,but why this methods will be invoked only when a item(has subItems) be clicked? i think this method should be invoked after page inited.In brief,how do you make subItems show and hide? Thanks!
Hey! Answering this is a little too much for a comment here. We’d love to explain you how we’re managing the currently open items in the sidenav, would you mind dropping us a short message at support@martinsuess.com and we’ll explain you detailed how it works. 
I am very angry at your attitude. I have send three email to support@martinsuess.com ,i also arise some issues in github,but i did not get a response!! Your code and service are like rubbish.you are not coder but businessman.so shit!!!!!!
Sorry to hear about your issues. We’re looking to provide the best service possible. We’re currently answering all questions we got over the weekend and will soon get to your issue. Please be aware that on weekends we only handle urgent requests from customers who have issues with production sites or similiar, also can we not prioritize you over any other existing customer and everyone who is in need of supports is equally handled. Thanks for your patience and we hope to be able to satisfy your needs, you should get an answer on your issue today. 
In fact, I still have not been explained. I will not believe you again
fuck!!
Hello, Thank you for a great theme using Angular and Material. I have purchased the theme and could quite easily understand the building blocks because of the well-structured project. I wanted to share some ideas I had that might make the theme even better.
Consider writing strict TypeScript (using the compiler option “strict”=true in tsconfig). I just took me an hour to rewrite it to strict, but it will be painful when I need to merge any updates you might release.
It would also be convenient if you made the core module more of a reusable framework module that you could easily copy to your own app. For this the module should be independent (build without demoapp module). In my opinion, even the App root module should be able to be empty (only have one line of reference in styles.scss and the assets). It would also be nice if all demo-data was moved into the DemoApp instead to keep the core clean. Just my thoughts, even though it is not hard at all to manually copy only the parts you are interested in which might be the intention of use.
Oh, one more thing, I believe some files are missing from assets/img. E.g. 1.jpg and 3.jpg (shows error in console output. E.g. when going to login page)
Thank you! /Michael
Hey Michael! Thanks for your detailed feedback. We’ll look into your suggestions and will try to realize them. As mentioned on the description on the item page, the few backgrounds 1.jpg, 2.jpg, 3.jpg in the demo are not included, but can easily be downloaded and added afterwards, just check the item page description for the link. 
Hello, that sounds great! While you at it you might also want to adhere to the default coding style rules from Angular-CLI’s tslint.json file by running TSLint. If there is a private git repo that one can get access and contribute to, please let me know.
We’re working on this and will soon provide one. Thanks for the feedback! 
When siderbar default:collapsed work?
Yes, it’s also possible to have the sidebar collapsed as default, just change the boolean in icon-sidenav.directive.ts. 
give me example, plz. Sidenav opened by default. need to close (collapsed)
Just set sidenavOpen in /src/app/core/admin/admin.component.ts to false and it will be closed by default. 
do you have sample page?: ,without the Demo directory and stuff that i will not put in production . thank you
You will need to import your components in the CoreModule or you will need to export the Core-Components, like Quickpanel, in the CoreModule, just add a export: [QuickpanelComponent] and afterwards import the CoreModule in AppModule. 
Seems some scss is not complete like _calendar.scss, and this break the style
It’s probably because you are using an updated version of the calendar. We’ll provide an update on this. 
Hello guys! This looks much better than when I bought it, Congrats! Now, one really powerful thing you should add is LAZY LOADING.
You create one module per app and this is Awesome, but you still load all the modules at ones!
Hey! Thanks for the feedback. Adding Lazy Loading should be no problem at all. To “enable” it, you just have to adjust the routes as said in the Angular Documentation and everything will be ready. 
Hi,
This theme looks awesome and i want to buy this but i want the horizontal menu at top as other theme supports. so can this update is available then plz reply me.
you guys did a great job!!!
Thanks, Waiting for your reply!!!
We are working on an update to include a horizontal update, we’ll let you know when it’s released. 
Hi.
Love the template. Was upgrading some of the packages and ran into some issues when running ‘ng test’. “Cannot find name ‘Node’ in testability.d.ts”. I found several related issues that revolve around es6/es5 support. For now I can just revert back to the original package versions.
Question: How often do you anticipate supporting upgrades to the angular libraries (I was testing 4.1.3 w/ 1.1.1 CLI)? I’m not a bleeding edge guy but as you well know this framework has been changing rapidly.
Thanks.
trevor
Side note. The above error occurs if you try and update to latest CLI as well.
Figured I would just add any other bugs I find in this same comment to make it easier for you guys. When building to production the ‘SearchComponent’ won’t compile. It appears that Toolbar->Search is the exact same component and is the one referenced in core.module.ts. I removed the Search folder (keeping Toolbar->Search) and everything builds correctly. Hopefully that component is not needed anywhere.
We do not recommend upgrading the packages manually, unless you know exactly what you are doing. You’ll always have to look for breaking changes between versions. We’re updating the template around every month, which should suffice when someone wants to always have the latest versions. Thanks for the note on the SearchComponent, we’ll see what we can do! 
Hello Sir,
I want to use this template with CodeIgniter 3.0 (PHP). Both the frameworks i.e. Angular 2 and Codeigniter 3.0 have its own routing protocols. Help me to use both simultaneously.
Thanks.