Bootstrap col-span specifications - twitter-bootstrap-3

I have a specification document which states - Bootstrap
Col Spans -2 (.col-span-2). So does that mean I should use col-xs-2 and col-lg-2 while writing the html class names? Or does that mean I should use col-lg-6?
Also, can I use multiple containers in a single bootstrap html page?

span-2 would be col-md-2. By my experience Span was supported in Bootstrap V2.
http://getbootstrap.com/css/#grid look at the Grid Options of the documentation.
Also how come you would like multiple containers? would it not be feasible to use divs?
(Added answer due to unable to comment) Trying to help instead of providing the perfect answer.
Hope this helps.

Related

silverstripe dynamic backend for flexible frontend

I'm searching for a while, but didn't find a practical answer for the following problem:
An Articlepage in the Frontend can contain different types of sections. For example a block text section and than a text section with left photo an at the end an wallpaper photo.
Now I want to implement this in my backend dynamically, so that I can choose, which type of section and -even more important- how many sections my article should contain.
In my recent project I've solved the problem as an Articlesection with a Dropdown, wich contains the different section styles. And one article hat xy Artilesections as childpages. In the frontend I included all Childpages of the Article - so to speak the Articlesections, where I've checked with if conditions, which sectionsystyle I have in this Section and here I styled the section as I want.
For example Artilce1 has 2 Childpages: Articlesection1 and Artilcesection2.
In AS1 I have choose in the dropdown: right text with left photo and check with if conditions, to style the section. The same with AS2, that is for example a wallpaper photo.
This semiprofessional solution worked, but there are some bugs with displaying the Article correct in the backend, because I have to declare the Articlesections as Includes and not native childpages. And in generell this don't seems like the developers of silverstripe want the users to do it this way..
Are there better ways to implement a dynamically changing backend, so I can decide, which and how much sections I have in the frontend.
Take a look at https://github.com/sheadawson/silverstripe-blocks. There's quite a few addons that offer similar functionality as Blocks such as Elemental. The following blog post might also be useful too - https://www.silverstripe.org/blog/silverstripe-strips/.
Thank you for your reply, but there is a problem, because I don't work a lot with the terminal and the composer. In principle I want to install sheadawsons silverstripe-block. I have installed the composer and run the command:
"composer require sheadawson/silverstripe-blocks" it seems like it installed that correctly, because I became no errors, but what then? With dev/build -to refresh the database- happened nothing and the following instructions in the readmy chanced nothing. Should I copy any files in my Sivlerstripe web folder or what else..? I'm a bit desperate, because there is such a poor documentation.
Tank you

Looking for a Jubula hack / alternative which makes identifying components using XPATH possible

We have plans to use Jubula to test the functionality of our web application but after evaluating Jubula we have run into a problem. We can't make Jubula click fields which have a varying id (generated).
I know that Jubula uses Selenium inside so using XPATH for maching elements in the DOM should not be a problem. Do you know about any Jubula hack or alternative / derivative which makes this possible?
I think it is not that easy to use XPATH directly with Jubula. However, Jubula uses XPATH internally to address components in a web page.
Your problem might be solvable by just ignoring the id's and using context and hierarchy for component mapping. To do this just try setting the names weight to zero in the object mapping editor (on the Configuration View). You may have to adjust the Threshold slider as well.

Does thomas-mcdonald / bootstrap-sass support the use of generators? Getting an error saying cannot find

A simple question. Does this version support generators?
I wanted to test out using it and follow along with Ryan Bates screen cast which I uses a different version.
I've been playing with tables today and want to see how this works using the generator with a scaffold generated model and all its components.
Running rails g bootstrap:themed returns
Could not find generator bootstrap:themed
So I tried to reinstall with rails g install:bootstrap
Error similar which lead me to try to find if it supports these commands.
Thanks
It doesn't need generators for asset files, since we hook into the asset pipeline through the use of a Rails Engine - configuration options are available through the use of variables (use this as a reference, Sass variables are actually $x rather than #x and need to be defined before importing bootstrap), Sass' #extend, and Bootstrap's #makeRow and #makeColumn mixins, along with the other Bootstrap mixins.
Themed scaffold would be interesting but generally would be a pain to maintain - view scaffolding tends to get ripped apart pretty quickly anyway. Perhaps a 'sane' application.html.erb layout generator could be useful.
So yeah, we currently have no generators, don't need an asset one, themed scaffold probably not coming soon unless someone is interested enough to do the work on it, potentially a layout generator in the pipeline.
Checkout
https://github.com/decioferreira/bootstrap-generators
Seems to be what you are asking for.
-Rick

What is the difference between data-dojo-type and dojotype?

There are two kind of type declaration mentioned in dojo documentation. They are data-dojo-type and dojotype.
For example,
dojoType="dojox.grid.DataGrid"
data-dojo-type="dojox.grid.DataGrid"
Both are working fine in all major browser.But i don't understand, What is the difference between data-dojo-type and dojotype?
Where should i use dojoType? and where should i use data-dojo-type?
I think its a new syntax of the same thing, maybe its functionality is slightly different as it is adjusted for html5, you can read more here. Anyway from what i saw its recommended to use data-dojo-type...
From dojo 1.6 documentation:
The dojoType attribute has been deprecated, and will be unsupported in 2.0. Replace all occurrences of dojoType with data-dojo-type, as the behavior is mostly identical, with the following caveats:
when using data-dojo-type, all widget properties must be stashed on a
single attribute: data-dojo-props
See http://dojotoolkit.org/reference-guide/1.9/releasenotes/1.6.html

How to define more than one stylesheet in adf framework

I am facing a problem with adf skining. My style sheet crossed 1800 classes. IE has a limitation of 4000 style classes. While rendering, ADF adds its own classes. So it crosses 4000 and the styles I am referring at the last of my sheet are not working in IE alone. I need to define a new style sheet for same application.
I have tried adding one more skin-family in adf-faces-config.xml. Did not work.
Please help.
Thanks in advance.
I am not 100% sure if creating a separate CSS will resolve your issue, and I do agree that after being used to multiple css definition and only loading a css for a particular page has its own advantages.
One thing that you can do though is organize the CSS, having 1800 classes might not be the appropriate way to go in a WebApp since a webapp should promote consistency in look and feel.
There is a good discussion in oracle forums that might help you on this, especially on the use of an el expression check on your current view to switch your skin on the fly.
Multiple Skin in the same application
I also mentioned in that forum about using skin-addition as well as my reason on taking up skin addition for our app, even though we didn't get to the number of styleClasses that you have, our css is already hitting 3k lines with only 600 lines for component specific and everything else is styleClass. We've also dramatically used the "inhertance" which trinidad skin offers -tr-inherit this really saved us in a lot of coding.
Use of extends property you can use multiple style sheet for same application.
trinidad-skins.xml
<id>skin_1.desktop</id>
<family>skin_1</family>
<extends>simple.desktop</extends>
<render-kit-id>org.apache.myfaces.trinidad.desktop</render-kit-id>
<style-sheet-name>css/stylesheet_1.css</style-sheet-name>
</skin>
<skin>
<id>skin_2.desktop</id>
<family>skin_2</family>
<extends>skin_1.desktop</extends>
<render-kit-id>org.apache.myfaces.trinidad.desktop</render-kit-id>
<style-sheet-name>css/stylesheet_2.css</style-sheet-name>
</skin>
in trinidad-config.xml
<trinidad-config xmlns="http://myfaces.apache.org/trinidad/config">
<skin-family>skyros</skin-family>
<skin-version>v1</skin-version>
<skin-family>skin_2</skin-family>
</trinidad-config>