What is your recommendation for development environment? I tried to open index.html but am getting cross domain errors due to assets being loaded locally.
The app requires a server since AngularJS perform HTTP requests to load views into the app. You can use apache, iis, node, etc.
This is a simple solution for a basic server setup using nodejs
- Install http-server "npm install http-server -g" (-g installs globally)
- Once it is installed move to the root folder of the theme (where index.html is located) and run
http-server . -a 127.0.0.1
If everything goes fine you can now access to the app at http://127.0.0.1:8080/
i have question about panel tools,
how can i catch event from panel refresh with angular or only with jQuery?
and about translate i try latest translate from bower 2.5.2 version and all working but sidebar not translated... maybe bug in translate, if i use yours (2.3.0) all works ok
How do I dynamically change alert value in the side menu for a menu item?
find your item and change alert value in object
Let us know if you have any question
i replacing footer(ng-include="'app/views/partials/footer.html'") to jade include :)
what's your opinion? what is better? or is on user what way they use
In short, like you did, moving small files to jade include is the best approach.
[07:59:21] Starting 'scripts:vendor:app'...
[07:59:29] Tested 20 tests, 20 passes, 0 failures: PASS
[07:59:29] Finished 'scripts:vendor:base' after 7.28 s
[07:59:37] Tested 74 tests, 74 passes, 0 failures: PASS
But I could not find any unit tests that were written to test your app. These tests are from vendor components?
What am I missing?
We don't include unit testing.
When you return the json string, there's a property with the total and another with the result. If server responds with total: 20 result: 10 items, the table will have automatically two pages, when click on second page, a new request is sent to the server to recover the following items.
If you don't want to trigger a request for each page, you can use a service to store one single request in a cache and then use it in following requests. We will include a demo for this in next update.
Let us know if you have any question.
My company is not completely satisfied with this tamplate.
You added the ngTable, but the paging functions and filter do not work with Ajax. The paging does not work even in your example.
When we use ngTable in other structure, it works perfectly.
When using the flatdoc in the development and test environments, both worked well. However, in the production environment, the flatdoc does not work and the Chrome console gave me the following error:
Uncaught Error: [ng:btstrpd] App Already Bootstrapped with this Element 'document'
The flatdoc statement that I used is:
Can you suggest a way to resolve this problem?
Also, that's a common error depending on the server/framwork your working on (e.g. turbolinks)
Also include the unit and e2e testing packages/configurations to get started on testing the customizations, if possible.
If it gets delayed in getting marketplace version updated, would it be possible to send me the archive directly?
Currently the package includes some demos using ngResource but limited to a single json request. We will take a look to add more demos, we would like to add something like user directory or contacts lists.
Regarding to testing for momento we don't include nothing related to unit testing. Hopefully after some other new features we will take a look on this,
it's great for other integrations
We hope you enjoy it :)
in my app I have different user roles. How do you suggest to restrict some pages to specific user roles?
Of course the server will not give any sensitive info when the user has not the rights, but the views are still opening.
First let me say that the frequent version updates are great and appreciated.
Can you please let us know what is, in your view, the best practice to update existing Agele based project with new version.
I have a project where most of my custom stuff in in other files (controllers, directives). I'm not using the "custom" folder - what is the use for this folder ?
Another better approach is to create a folder for each model in your application.
All files here will be concatenated after all files in the modules/ folder.
Dependencies, see file app.init.js
Routes, see file modules/config.js
Constants, see file modules/constant.js
from readme ;)
We have also included from last version an AngularJS seed project that helps to focus only on main feature when a new update is available
Another approach is like @juniobranco stated, "The changelog states the files that changed. Once you understand the dependencies of the different modules you can update what is required. For example for any CSS change, I did not change anything from the original CSS instead I created a new one that has my custom one's. Ideally this allows me to update the CSS files without concerning with any impact to my custom changes ( although it can break them in some rare cases).
For Angular Directives/Controller/Service changes, I trace back the dependencies of the components that I used, for example any updates on Maps related stuff, I don't need so I won't need to touch anything on my side. Thats the beauty of Angular its suppose to be segregrated!"
We hope this helps
Write a comment
This is a great way to give the seller feedback and ask them questions about their item.
You must sign in to write a comment
|Bootstrap:||Compatible with 4.x|
|Topic:||Internet & Web|
|Labels:||admin, admin template, angularjs, material, meanjs, meteor, mvc, rails, responsive, rtl|
|Released:||4 years ago|
|Updated:||2 months ago|
Need a front-end template?
Bootstrap is designed to help people of all skill levels – designer or developer, huge nerd or early beginner. Use it as a complete kit or use it to start something more complex.
Unlike other front-end toolkits, Bootstrap was designed first and foremost as a styleguide to document not only its features, but best practices and living, coded examples.
Built to support new HTML5 elements and syntax with progressively enhanced components.
Bootstrap is tested and supported in major modern browsers like Chrome, Firefox, and Internet Explorer.
- Latest Chrome
- Latest Firefox
- Latest Safari
- Latest Edge
- Internet Explorer 10/11
- Latest Opera
Features & includes
Bootstrap provides an unparalleled array of features and reusable components that let you hit the ground running: