In an effort to reduce duplicate projects, this project should be merged into http://dgo.to/bootstrap.

Please see how to proceed with this task in #1594508-22: Merge in other d.o Bootstrap projects. We need project maintainers like you to help with this task.

Comments

Sorry Mark, but I don't think that Tweme is duplicate project.

It's a kind of lightweight integration of Twitter Bootstrap to Drupal with several UX enhancements, not more.
Meanwhile Bootstrap provides deep integration and overrides dozens of native Drupal behaviors and implementations.

Tweme is just theme, Bootstrap is a framework.
Just compare their sizes: 26 KB and 160 KB accordingly.

I think that sometime I will inherit Tweme from Bootstrap.
But 100% it will never be the same as Bootstrap.

If you need any help with Bootstrap - I'm glad to contribute.
But please don't ask me to merge Tweme into Bootstrap.

Can I second this? Please never merge tweme with bootstrap - I don't want all that crap to contend with, I appreciate the light integration provided here.

Thanks for this theme,

Pobster

Status:Active» Closed (won't fix)

Ok pobster. I will not. Cheerfully ;)

Status:Closed (won't fix)» Active

@tonystar: Please read Joining forces with others and co-maintaining projects. Please also read: #1594508-23: Merge in other d.o Bootstrap projects.

This theme is a duplication.

@pobster:

I appreciate the light integration provided here

They both have "light integration" and work out of the box, just because the ZIP file is bigger doesn't mean that it runs any less efficiently or drupal_bootstraps() any slower.

This theme claims to have "minimum theming overrides" compared to Bootstrap, that is also false. It also implements it's own version of jQuery, which is also probably a really bad idea... see: #1846736: Remove jQuery CDN setting in favor of using jQuery Update module, specially the comment explaining why this is: #28-1846736.

@Mark Carver of course I agree with you. As developer, as themer, but not as end user.

Imho, Tweme has very transparent concept, it just makes 3 things:

1. 20% - Connects Twitter Bootstrap to Drupal in some proper way
2. 50% - Bridges some BS features with Drupal features (i.e. BS carousel with Drupal blocks system)
3. 30% - Provides a minimal CSS to use Tweme out of the box

So, yes there is a duplication. But maximum in 20% of code.

So, no - Tweme shouldn't be merged into Bootstrap. Why? Because Tweme is not a framework, it is not aimed to merge everything from Bootstrap and to support anything in Drupal. It just makes the basic things easier. It is well for blogs, small documentation sites, home pages, and so on. But not for heavy web portals for example.

I repeat, I agree with you and may be later I will inherit Tweme from Bootstrap and get rid of 20% of code. But now I'm working on new features and trying to make Tweme as simple, handy and straightforward as possible.

  1. 20% - Connects Twitter Bootstrap to Drupal in some proper way
  2. 50% - Bridges some BS features with Drupal features (i.e. BS carousel with Drupal blocks system)
  3. 30% - Provides a minimal CSS to use Tweme out of the box
  1. Duplicate - the d.o Bootstrap base-theme has been using the BootstrapCDN for a while now, before you... so not sure how this counts.
  2. The carousel is probably the main "feature" of this theme, which is what needs to be merged or moved to a module.
  3. Duplicate - the d.o Bootstrap base-theme provides minimalistic overrides as well.

Tweme is not a framework, it is not aimed to merge everything from Bootstrap and to support anything in Drupal. It just makes the basic things easier.

Neither is the d.o Bootstrap base-theme. It is VERY lightweight (and works) out of the box. Providing only the necessary injection of classes to take advantage of the alright loaded (via BootstrapCDN) styles. It would be pointless to not utilize the large CSS framework that the browser loaded (ie: unused styles).

So, yes there is a duplication. But maximum in 20% of code.

You're really missing the point. Duplication isn't just code, it can be concept and functionality too. While yes, some of the code maybe similar, this project can end up confusing people in the long run. Not to mention there is only you behind it. Instead of maintaining your own fork of Bootstrap for a small percentile, create a patch in the main d.o Bootstrap issue queue to ADD the functionality that's missing/you desire. Everyone will be better off for it.

We have enough duplication on d.o.