Skip to content

Why are we not using bootstrap > 3.1.1? #379

Closed

Description

@Martii

Just for grins I updated bootstrap dev locally to 3.2.0 and it appears in a quick scan to be okay to use e.g. my normal testings it appears to be okay... not fully tested though.

This question is primarily directed towards @Zren

Activity

  1. added
    questionA question has been encountered by anyone and has remained unanswered until cleared.
    team bizThis is similar to a meta discussion.
    on Oct 20, 2014
  2. changed the title [-]Why are we not using boostrap 3.2.0[/-] [+]Why are we not using boostrap 3.2.0?[/+] on Oct 20, 2014
  3. Martii commented on Oct 20, 2014

    @Martii
    MemberAuthor

    I also haven't updated bootswatch to 3.2.0 which I assume is needed to match at some point with boostrap?

  4. Zren commented on Oct 20, 2014

    @Zren
    Contributor

    Reasons not to:

    • Effort spent merging requires re familiarizing myself with bootswatch.

    Reasons to:

    • Fix bugs no one has mentioned (that are bootstraps fault).
    • Maybe get new css rules/js components.
    • Be up to date.

    There's really not much I can see worth mentioning in Bootstrap's changelog. Similarly for Bootswatch's CSS changes mentioned in #223.

    Also, you shouldn't be editing bootstrap-custom.css by itself. It's a compiled file.
    https://github.com/OpenUserJs/OpenUserJS.org/commits/master/public/css/bootstrap-custom.css

  5. Zren commented on Oct 20, 2014

    @Zren
    Contributor

    And the only new feature we might use is

    #12204: Visibility and hidden classes for block, inline-block, and inline elements.

    Which we already solved here.

  6. Martii commented on Oct 20, 2014

    @Martii
    MemberAuthor

    Also, you shouldn't be editing bootstrap-custom.css by itself. It's a compiled file.

    Interesting... although #223 may supersede this ... basically the target objective will be to load their bootstrap.css and cascade with our changes in our own file and referencing both in the views I believe when 3.2.0 is implemented... this will solve the just recently notified that anyone shouldn't be editing the bootstrap-custom.css.

  7. Martii commented on Nov 18, 2014

    @Martii
    MemberAuthor

    Any significant changes in 3.3.1?

  8. Zren commented on Nov 18, 2014

    @Zren
    Contributor

    Do we need to upgrade you mean? No. This will be the same answer for every new version until a bug requires us to update or a new feature is desired.

  9. Martii commented on Nov 18, 2014

    @Martii
    MemberAuthor

    This needs to stay open.

  10. reopened this on Nov 18, 2014
  11. changed the title [-]Why are we not using boostrap 3.2.0?[/-] [+]Why are we not using boostrap > 3.1.1?[/+] on Nov 23, 2014
  12. added a commit that references this issue on Jan 15, 2015
    028898f
  13. 11 remaining items

  14. reopened this on Jan 16, 2015
  15. Martii commented on Jan 20, 2015

    @Martii
    MemberAuthor

    @Zren

    A few questions come to mind to help me understand bootstrap a little better

    All manual changes to...

    Including your changes or just mine?

    Probably best to pull away from bootswatch...

    Using the default theme of bootstrap itself there is no coloration for our current site colors. Is that included in your gist? If so how exactly are we supposed to read in the JSON? (Remember grunt is currently way back on the burner and manual understanding is a must here... I've been twiddling with less and "myVars" and there's some reference to JSON with this link)

    General question of ... Why is there bootstrap.css and bootstrap-theme.css in the downloaded zip file from http://getbootstrap.com/customize/?id=03a4640ed537c1b0c92c ? (This is also present in the dist folder of bootstrap... I understand the website whittles down what we don't use but when are we supposed to apply our own theme? common.css of course is loaded afterwards so I might plan on moving Squada One there at some point)

  16. Zren commented on Jan 20, 2015

    @Zren
    Contributor

    Including your changes or just mine?

    Yours. All of mine are from modifying the .less files and not the .css file itself.

    General question of why is there bootstrap.css and bootstrap-theme.css

    Because you need to include both bootstrap.css and bootstrap-theme.css. Bootswatch combined the two files into a single file. The first is the default bootstrap file, the second is a file that overrides all the previous rules with the different variable values. You'll also need to put https://github.com/Zren/bootswatch-OpenUserJS.org/blob/theme/custom/bootswatch.less into a 3rd file or dump it into the top of common.css.

  17. changed the title [-]Why are we not using boostrap > 3.1.1?[/-] [+]Why are we not using bootstrap > 3.1.1?[/+] on Feb 7, 2015
  18. self-assigned this
    on Feb 7, 2015
  19. added
    CODESome other Code related issue and it should clearly describe what it is affecting in a comment.
    migrationUse this to indicate that it may apply to an existing or announced migration.
    on Feb 7, 2015
  20. added a commit that references this issue on Feb 7, 2015
    2e13ba8
  21. removed their assignment
    on Feb 8, 2015
  22. locked as resolved and limited conversation to collaborators on Apr 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    CODESome other Code related issue and it should clearly describe what it is affecting in a comment.migrationUse this to indicate that it may apply to an existing or announced migration.

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions