Hey.

Oh thank you for the info. Easy to fix, i’ll upload a quick update tomorrow including other improvements.

Thanks

Hey.

I’ve included approximate changes in files, what part was changed. But if you have any difficulties, let me know please what file you already changed and i’ll guide you what needs to be changed in there.

Thanks

Hi.

Nope, i didn’t add this example, but i think there won’t be any issues if you place a form with components inside modal body and add submit button which will validate the form. The only difference can be closing modal only is validation passed. For this functionality you can try to use:

$("#form").validate({
    submitHandler: function(form) {
        $('#modal').modal('hide'); // hide modal after submit 
        form.submit(); // submit form
    }
});

where submitHandler is a callback for handling the actual submit when the form is valid.

Thanks

Hi.

Of course, you can find it in the documentation – “Changelog” page.

Thanks

It lists the changes, but not the actual files edited/added/deleted. How do you recommend updating from the older version without the specific code changes? Thanks

Hey,

Changelogs in live preview and documentation are different – live preview includes a list of changes only, in documentation it has the same list, but below it there are 3 additional tables with all files that were added and updated.

It depends on the complexity. Example – select2 plugin was completely changed in the latest version, so all styles were created from the scratch and they are completely different from the previous version. In this case the best way is to replace files and re-compile your less files.

In most cases i try to specify what exactly needs to be changed in specific files, sections or class names.

In future releases i will try to provide more details about what, where and how.

Thanks!

Hey.

Yes definitely, planned for the next update: list of emails, reading and writing.

Thanks

Hah, didn’t even see that bullet Will be fixed as well, thank you!

Yes, this is a confirmed minor bug, appears on inline elements. As i understood from BS issue tracker, you need to attach tooltip to the most parent container of your inline links to avoid adding block element dynamically to inline elements.

I fixed the problem using the solutions from the issue tracker thread. Thanks for such a fast response, really appreciate it! Also, really good job with the theme, loving it

You are always welcome. Thanks

Hi.

Thank you for reporting. There is a wrong checkbox style, where checkmark is added by default, not to selected state only. Will be fixed asap.

Thanks!

Hey.

All the data from dashboard is stored in dashboard.js file, located in assets/js/pages/ folder.

Streaming sparklines with auto update don’t have any specific data in demo preview, this is a randomly generated data with timeout function. But you can use any type of data actually, like json/csv/tsv formats. It really depends on what you want to show there.

Also, it is a native D3.js library chart built from the scratch. You might want to check available options and documentation of D3.js, because this is not a reusable charts library. It’s not that easy to build a graph, but once you understand what and where, you can easily build any type of chart with a very specific functionality (calendars, score card, tree view, heatmaps etc etc).

Let me know please if you have any questions about charts.

Thanks

Awesome, thanks!

Oh yeah, forgot to ask. Any idea on when the update with this will be?

Hey.

I hope it will be out in the middle of January after holidays. I’ve pushed an update today, it doesn’t include this option because this was a quick update with bug fixing, nothing new was added.

I’m working on a huge update that will include 2 new layouts and a lot of different additions. Responsive tables will be added to it as well.

Thanks

Hi.

I haven’t tested these components working together, but i really don’t know about any possible conflicts. Could you please be more specific about them? I mean what kind of conflict or errors would you get?

I can help you of course to get it to work, but i’ll try to test the use case you’ve described on monday.

Thanks

Yeah I know, time is missing that’s why I don’t wait for the next updates to work on my own material / polymer use but I think these could represent a great added value for your work !

Your challenge is one update per month right?

Yeah right, the next one i believe would be delayed a bit because of holidays. I’m going to add 2 new layouts, including material style. And other features of course

Perfect !

Hello.

Ohh, tell me.. For the same reason i didn’t update Typeahead extension, because the part of typeahead was completely re-written and some of the components simply don’t work with a new version.

Yeah i know it doesn’t work in Editable, didn’t have a time to find a workaround so i would be really appreciated if you can email the file to e.kopyov[at]gmail.com. I’ll test it in different use cases and if all good include it to the update.

Thank you very much!

Just sent you an email regarding this issue. Hopefully you can make heads or tails out of it

Hey.

Yes, received, will review everything on Monday. Thank you very much!

Hey.

Thanks for reporting, i didn’t check a version of this plugin yet. I’ll take a look into it next week – update plugin locally and update Less file for styling, let you know afterwards.

Thanks!

Cool. I think really all I would need is the less files…. The updated plugin works out of the box, but it just quite doesn’t look right

Understood, just need to set up, test in different use cases and change default styles to match general template style. Should be ready next week.

Thanks

Hey.

I think you can use Bootbox modal extension for alert/confirm/prompt dialog replacement. But i am not sure about how you can use it without linking it to an element.

Also, what do you mean by hardcoded? As i understood, you don’t want to include html markup, but initialize it via JS. In this case you’ll need to use some general selector to attach the dialog.

Thanks

Hi,

I’ve been thinking about writing a custom js function I could call from my page. But is it possible to call a hidden modal that way? Now you can call a modal by adding this to a button (for example) ‘data-toggle=”modal” data-target=”#modal_removeFile”’, can this be done through js? That way I only need to render one hidden modal, write a custom js function that takes parameters so it can change some content in the modal.

With the hardcoded I mean that, lets say I have a list with 50 items. With two options I want a modal to show up. That would mean I have to make my view render 100 hidden html modals… I’m not sure but browsers can’t be happy with that sort of things?

Hi,

Yes, according to Bootstrap Modal docs, you can initialize modal component via Javascript by using

$('#myModal').modal(options);

but it still requires an id. I think the best to achieve your functionality is to use 1 modal dialog markup with 1 id and 1 specified functionality, but change it’s content dynamically via jquery load(). No need to create a modal for every item, you can dynamically change the content inside 1 modal.

If you need a simple confirmation dialog with 2 buttons – yes/no and some text, i’d suggest to use sweet alerts or bootbox, because they are a perfect tools for alert/confirmation/prompt dialog replacements that don’t require too much code.

Thanks

Hello,

Oh yes, you are right! Sorry, my bad, will re-upload in a couple of days, want to wait a bit if something else will come up to fix all at once.

Thank you!

Great, sounds good. For the time being, I should be good to go then?

Yes sure, I’ll change path to files in the table, not a location

Thanks

Hey.

Yes, it’s in review queue, should be available shortly

Thanks

Hi.

Sweet alert library is updated in the upcoming release, so this issue should be fixed. A new release will be available after passing the review process – depending on the queue today or tomorrow morning. You’ll get an email when approved.

Thanks

Hey.

Actually charts are very easy to use. You just need to define what charts you want to use and search for the code in demo chart setups located in assets/js/charts/ folder.

Native D3.js charts are different. They need a custom configurations as they are not re-usable, so each chart built with native D3.js library needs a single JS file with chart setup. D3.js provides a very detailed documentation and it’s very powerful thing, you can actually create any kind of visualization with it.

Echarts – each js file used on demo pages include example configs for ALL charts available on the page. To use a single chart, you need to remove all other inits or pull out config for a single chart you need. This was made because echarts use modular file import, so it is loaded once.

All other charts use single file with a setup for 1 chart only.

I’d suggest to always track errors in console, if you get them – you’re trying to initialize the chart and attach it to the element, that doesn’t exist.

If you are still confused, please send me an email and let me know what you are trying to add and i’ll describe everything in details.

New update – yeah, should be available for download today when the review process is done.

Thanks