Skip to content

Additional options and/or changes of bootstrap_plugin? #40

@kukrik

Description

@kukrik

@spekary! I have some questions. I would like to hear your suggestions and tips. Your bootstrap_plugin is very good. I admit that I have to learn alot. I know more about how to use older versions of QCubed. I have to learn to use it a new way.

My client didn’t liked standard (small and blue) radio and checkbox. I was searching most friendly options from Google for Bootstrap and found a link: http://flatlogic.github.io/awesome-bootstrap-checkbox/demo/. I changed it, below you will see my template:

ekraanitommis

Bootstrap’s standard HTML output (radio or checkbox):

<!-- Begin QCubed\Plugin\Bootstrap\Checkbox  id:c6 -->
  <div class="checkbox">
    <label>
      <input id="c6" type="checkbox" name="c6" value="true" />…
    </label>
  </div>
<!-- End QCubed\Plugin\Bootstrap\Checkbox  id:c6 -->

But I need to change it (individual solution???)

<div class="checkbox checkbox-orange checkbox-inline">
<input id="c6"  type="checkbox" class="checkbox-container" name=”c6” value="true">
<label for="c6">...</label>
</div>

I have some thoughts. These are my suggestions…

  1. Default $blnExchange (or $blnReversed or etc) = false;
    If, for example, to turn on $this->lstCheckbox (or lstRadio)->Excange = true;
    Then tags exchange their places (<div><label><input> ... </label></div> to <div><input><label> ... </label></div>).

  2. Secondly - definitely need to add other classes (if necessary) <div class = "checkbox (or radio)" for example "checkbox-orange, checkbox-inline, radio-orange, radio-inline etc". A solution might be that it is necessary to add a function. After you can simply add $this->lstCheckbox (or lstRadio)->DivCssClass = "checkbox-orange checkbox-inline etc";

They make the work much easier for webmasters. Also, it gives a lot of flexibility for Bootstrap’s other (clients) themes.

@spekary, here are two possibilities: either to add these additional options in “bootstrap_plugin” or you have to write special solutions in the folder "app_includes"?

What are your thoughts, suggestions or tips?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions