Hey pganda,

thank you very much for your comment.

For sure, you can use this template for your frontend because it contains static pages you can customize on your own. But you cant compare it with a real frontend template or WordPress theme which were focused on public frontends.

But if you also like it to use as a public frontend: You can use it, why not?

Thanks again,
Simon

Wow, thank you so much for your comment, Anthony! I really appreciate it!

Hey alciato,

thanks for your purchase and rating, I appreciate it!

To your issue: Thats because the jquery.event.move.js was not saved as regular UTF-8 by the author of the plugin. You can simply save it as UTF-8 with your favourite texteditor or write me an Email via my profile page and I’ll send you the file with correct UTF-8 byte sequence.

Regarding the rolodex-plugin: Have you any specific use-case in mind for this?

Thanks,
Simon

Hey dreadlord41,

you can see the examples I use for the charts in assets/js/demo/charts/*. Simply replace my demo-data with yours. If you want to update an existing chart, just call it again with $.plot() (example in assets/js/demo/charts/chart_selection_zooming.js).

It could be that this totally doesn’t answers your question because unfortunately, I don’t know what you exactly mean. Can you please restate it with more informations, if this doesn’t answered your question?

Thanks,
Simon

Hi Simon,

Thanks for the reply. It helped me actually. And the webpage is awesome. Great job!

Regards, Deenath

Great to hear that it helped a bit! Thanks Deenath.

Thank you so much for your compliment and rating, I really appreciate it.

1. You’re right, I did my own styling for the navbars, so the navbar-fixed-bottom is not working out of the box. I’ll implement this feature into the next update. If you’re interested in it right now, please follow these instructions.

Remove the top: 0; from the main.css in .navbar (line 287). If you’re using the LESS-files, open /_less/general/navbar.less and remove top: 0; from line 16. This should fix it.

2. Great idea for the form-groups, added onto my todo-list. You can already use smaller inputs with adding the class .input-sm. Example:

<input type="text" name="foobar" class="form-control input-sm">

Thanks,
Simon

Thank you very much CorsoUK!

First of all, you need to learn (if you haven’t already) a programming language for the backend, like PHP. Then you can modify the template according to your needs. You can store your information for example in a MySQL-database and then read your database with PHP.

There are a lot of tutorials in the Internet you’ll find at Google or use Envato’s Nettuts+.

When you already rule PHP and such, I can recommend you a MVC-framework like Laravel.

If you need further information, don’t hesitate to open a new thread at my support forum.

Regards,
Simon

Hi – thanks for the reply. Yes I am familiar with PHP and MySQL but no expert. I was hoping you could give me just one example that I can then use to learn from..?

Well, thats pretty hard because everyone has other needs. As I said, I would to entrust you to Laravel. Nettuts+ has an own category for Laravel.

If you don’t want to use Laravel, here is a good example for server-side processing with DataTables.

Hey colle28,

danke für dein Kommentar.

Du kannst die “Text Customisation Hooks” vom FullCalendar benutzen. Ein Beispiel:

$('#calendar').fullCalendar({
    //localize the month names to German
    monthNames: ['Januar','Februar','März','April','Mai','Juni','Juli','August','September','Oktober','November','Dezember']

    //...
})

Für die ganzen Standardwerte kannst du dir die defaults.js anschauen.

Wenn du weitere Hilfe benötigst, erstelle doch bitte nächstes Mal einen neuen Thread in meinem Support Forum.

Danke,
Simon

Danke

Hello Xander,

thank you for your comment.

At this time, it’s the expected behaviour that the header top navigation bar on the left side gets hidden on smaller screens, because it has the classes hidden-xs and hidden-sm. You can remove it to show the links even on smaller screens.

If you aren’t satified with this solution because you’re using a lot of these links, please open a new thread in my support forum where you’re referencing to this comment and I’ll work on a solution for you.

Yours sincerely,
Simon

Hey Andy,

thanks for your comment.

I just contacted you via Email.

Regards,
Simon

Hey c0py,

thank you!

Ohh, I forgot to update the link from underscore.min.js to lodash.compat.min.js. And yes, the ie8.css is currently not in use but the link is there for possible later use.

Regards,
Simon

Thanks for informing me about this issue!

You can fix this issue with replacing the handleCheckableTables()-function in assets/js/app.js with this: http://pastebin.com/c3JL4iWU

Regards,
Simon

Thanks Ednaldo! Yeah, thats right… but I think every knows that these are static pages…

Hugs back from Germany.

Hey Fabrizio,

thanks for your comment.

It is possible to hide/ show columns on responsive tables, but it only affects columns that have no data-hide-attribute. But the responsive datatables follow another approach. When there is not enough space, you can specify in the HTML, which columns should be hidden and where the expand-icon should be displayed to show the hidden columns: http://screenshots.stammtec.de/2013-09-14_09-58-54.png

Or do you want something else?

Have a great weekend,
Simon

Thanks so much besotico, I really appreciate your purchase and 5-star rating!

If you have any questions, don’t hesitate to open a new thread in my support forum.

Hello gijohnson,

yes, all the LESS files are included and the documentation says, which files need to be recompiled.

I’ll add it into the product page, thanks for the idea!

Regards,
Simon

Hey ingenuitor,

thanks for your comment.

I would appreciate it, if you could open a thread in my support forum with the IE8-issues you found, so I can fix them.

In addition, the author of the DataTables plugin recommend to users with large data sets to use server side processing. But a FooTables version is also a good idea, it’s noted.

Thanks,
Simon

I already setup a FooTables version, that was super easy, yet I have not worked out the checkboxes yet, FooTables is so much faster. Now I’m trying to workout the jQuery Lightbox Evolution, that does not work at all with your admin. Seems to conflict with the menu or something. Not sure yet, will have to try removing scripts one by one until things work, then see which one is the conflict. Can’t wait to see how things progress with this framework template. So many tools and so little time, more to be added I’m sure. Will post more as I keep digging (o;

You can see my function which handles the checkable tables in /assets/js/app.js around line 446 called “handleCheckableTables()”.

Why do you choosed jQuery Lightbox Evolution? I think you can pretty easy include the Bootstrap Lightbox (BS3-branch). But if you open a new thread in my support forum with the messages in your JavaScript console, I’ll try to help you with your plugin to make it compatible.

I appreciate your further digging, but a new thread for this would be better for the overview instead at these little comments.

Thanks,
Simon

Hey andreywis,

these are two great ideas. The form wizard is already planned, just waiting for a popular plugin that it’s updating for Bootstrap 3.

Draggable boxes is noted!

Thanks,
Simon

Thanks for your comment, I’ll try to upload the update this weekend.

So is that update coming out lol really excited for it!

Hey zachstarnes,

I released the update yesterday at 21:15 GMT+1. You can simply redownload Melon now for the updated version.

Ahhh you’re awesome! Incredible that you remembered this despite the fact that it’s one year ago. Well… maybe you were my unwanted inspiration for the name, who knows.

And thanks for your warm words.

Ah okay, sorry that I misunderstood you. I have in the app.js a single line, which checks, if the header is fixed. If yes, it will add a class to the #container. Without the class, the breadcrumb is overlapped by the header. To add this class manually, you can do it like this:

<div id="container" class="fixed-header">

Then the breadcrumb will be visible even if JavaScript is disabled.

Regarding to the tabs: This is definitely the expected behaviour, so that each tab is easily accesable for the user with a small monitor (or phone). You can see, also Bootstrap by itself does it like that: http://screenshots.stammtec.de/2013-09-10_20-38-16.png

Ok, thanks on the breadcrumbs. That makes more sense.

On the tabs. I expect that they wrap, however, the text when they wrap makes it hard to tell if it is part of the first tab or another tab that has wrapped under the first tab. The layout also breaks because the first tab separates from the box.

Could I add the CSS to maybe shrink the font on smaller devices maybe to prevent it from wrapping as soon?

Yes, this is a good idea, you can do this if you want. If you need instructions, on how to do this, simply create a new thread in my support forum.

Have a great day, rnewcom!