Hi, thanks for report this.

Seems to be a round problem with the line-height. A fix for FF breaks on chrome so as a quick solution you can do the following

Using LESS, edit file input-group.less, scroll to line 137 and append height: @input-height-base; to > .btn {

Using CSS (in case you are using only the compiled version) use the following rule

.input-group-btn > .btn {
  height: 41px;
}

As you can see, both solution forces the height of the button when used in a markup for input-group

Hope this helps,
Regards

Hi Geedmo,

regarding this:

That should be simple, add an input and in the script call the function setColor using the keyup event. Like this

$(‘input’).on(‘keyup’, function() { var color = this.value; setColor(color); })

You can also find a snippet to validate the hex format before calling setColor.

I placed that script after this:

$('input.input-switcher').on('keyup', function() {
                var color = this.value;
                setColor(color);
            })

$('input#minicolor').minicolors({
                defaultValue: '#50a846',
                position: 'bottom right',
                change: function(color) {
                    setColor(color);
                }
            });

And this is my input box:

var themeswitcher = $('<div />').attr('id', 'themeswitcher').html('<p><strong>{L_SELECT_COLOR}</strong></p><div class="input-group"><span class="input-group-addon">#</span><input type="text" class="form-control input-switcher" placeholder="Hex color code"></div><div class="space10" />')

But nothing happens.. Any help on how to get this to work would be really appreciated (i’m not scripting savy :-/ )

$(document).on('keyup', 'input.input-switcher', function() {
                var color = this.value;
                setColor(color);
            })

Never mind. It did work with your first code. I forgot to enter the sign ”#” before the value. I guess I’ll use the placeholder as example so the ”#” is not missed. Thanks again for your time.

Hi, yes, I’m currently working on this skin. I have planned to finish it this weekend.

Thanks for ask,
Regards

Hi geedmo,

Any progress on updating the skin?

Hi, yes, it’s been updated to 3.1.0 last week

Hello, its no possible because gravity form is explicitly for wp and has custom styles that don’t match with the bootstrap css. I mean, their custom styles go beyond a bootstrap skin.

Hi, no, there’s no shopping cart widget. This item is only the css/js to change the look&feel of any bootstrap based website. A shopping cart widget will require a backend to handle item in the cart.

Regards

Thanks so much Ronald6x!

Hi, thanks!

1. I think is possible but you will need two images (the original divided in two) and set one part as top and the other half as bottom. I guess the problem will be synchronize every part of the image when the page is resized.

2. No, unfortunately I couldn’t find a fix for the iframe bug. So actually on safari mobile browsers the homepage links directly to the demo page instead of showing the iframe and that’s why there’s no back button. The back button only shows when the homepage script handles the iframe load, with a direct link is just a new page load.

The iframe solution is simple just to show the product demo, but the same behavior could be achieved requesting the new content via ajax, a bit more complicated (not too much) but surely it should work and you avoid iframe issues.

Hope this helps,
Regards.

And by the way, this is a really good skin… great job on this one..

Hi, the UI kit used for Doppler is based on BS components but they have some extras classes (e.g vertical alignment, etc) that is needed and it’s included with Dropper. Because of that, the sample page will not work automatically if you put it in Sesamo.

Let me know if you have any question
Regards

Thanks philtem.
Currently I don’t have in plans to add the extras to Sesamo because both skins was built with different approaches. Anyway, if want to implement some components from Droppler in Sesamo, you need only to add the necessary less files to the bootstrap.less and compile it, depending on the component and due to the styles differences you may need to add/remove some rules but since both structure are similar, they should require a few minor changes.
As I said before at ringmastr’s question, if you find any difficult, please feel free to ask.

Regards

Bought it! Gonna try my best at adding some Dropper extras to Sesamo yet I’m glad to hear that you will help in case I can’t make it work

Thank you.

Hi, thanks for let me know you’ve solved it.
To change the font path you edit the bootstrap.css file looking for the @font-face directive or by editing the FA LESS files and then compile it.

Regards

Hey geedmo, thanks for the reply. Another thing: I realised that when I view your demo on my iPhone 4 (vertical orientation), the green icons on the upper left did not appear when I tap on either Bootstrap 2 or Bootstrap 3.

The URL I was viewing:

geedmo.com/codecanyon/sesamo/

Is this intended?

Thanks!

That’s right honeybadger.
The demo works using iframes but due to an iframe scroll bug on safari when you click con bs2/3 button, instead of load the framework preview on an iframe the script will redirect you to the demo page instead. You can take a look at the demo.js file if you want to see it works

Regards

To install this skin you just need to replace your bootstrap files (css and js). For the extra features like elements animation you have the documentation.
Bootstrap standard component will work automatically, other extra components may need some customization.

Regards.

Hi,

both skin extends the bootstrap features. You can mix them but you need to dig into the less files in order to include from one skin into another. Both file structure are similar, if you find any difficult, please feel free to ask.
These days I’m a bit delayed with support, but I’ll do my best to assist you.

Your rock @geedmo. You’re gifted.

Thanks!

Hi,

I don’t have enough experience with RoR, but I can suggest you some basic ideas
1- Replace and make sure your css files are the skin version
2- Find in your app bootstrap.less file, if found, may your app compiles everything on the fly, so try replacing all less files with the skin version (backup first)
3- Refresh all your caches, browser and app. Perhaps your app have some cache folder, if so, simply delete it. Also if is possible, a restart could help.

Regards

thanks

Hi,
The boostrap 3 version I’ve used is the final release.
You’re right, BS3 dropped the classic accordion css in favor of panel style. But, I’ve included the accordion because from the first release, I designed it with a different style from the panel accordion. You can see in demo that both (accordion and panel) works with the collapse plugin. So you can use any of them.
Even, I’ve edited the collapse plugin in this skin in order to support both components as accordion. There’s no two plugin, just the same as in final release, with 25 extra characters.
If you don’t need the accordion code and want to remove it, I can send you a custom build without the accordion. But, if you work with LESS you can simply remove the accordion.less from bootstrap.less and compile it again.

I give you full warranty that the code is based on BS 3 Final release, anyway feel free to ask whatever you need.
Regards

Thanks for the quick reply. I was using the CDN version of Bootstrap and I noticed the accordion did not work. Thank you for the clarification. I understand what you did now.

Because I want to use the hosted CDN version of Bootstrap, for speed purposes, I’ll go ahead and find the changes you made and just create a separate CSS file – that should solve my issue.

Again thank you for the clarification and I’ll work on customizing my setup.

To anyone thinking of purchasing this skin, don’t think twice just go for it. The code is solid and as you can see the included support is top notch!

In your case, if you want to improve load time, I suggest you to use a subdomain as a CDN for your project, instead of find the changes in the skin files. I mean, you can but will be more easy for your case.
Also, if you create an extra stylesheet with just the skin styles, you will be adding many extra rules to override defaults in Bootstrap, and so, you decrease your load time with a cdn but you increase it adding more resources to download. Just an idea.

Regards.

Thanks!