<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I agree with Daniel and Chandra. We should wait for stable bootstrap
4 version.<br>
<br>
<br>
<div class="moz-cite-prefix">On 5/24/2016 4:38 PM, Daniel Henrique
Barboza wrote:<br>
</div>
<blockquote
cite="mid:de9c9f1a-b301-1b0f-3732-41abdf1665a4@gmail.com"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<br>
<br>
<div class="moz-cite-prefix">On 05/24/2016 05:58 AM, Chandra
Shekhar Reddy Potula wrote:<br>
</div>
<blockquote
cite="mid:201605240859.u4O8wmN6012164@mx0a-001b2d01.pphosted.com"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 5/23/16 10:30 PM, Samuel
Henrique De Oliveira Guimaraes wrote:<br>
</div>
<blockquote
cite="mid:d35dccff9b8b45d1bc980902f681865d@serv031.corp.eldorado.org.br"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal">Hi team,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US">Last year Twitter
announced the new version of Bootstrap. Wok currently
uses a customized version of Bootstrap 3 Sass / SCSS
files and looking at the Alpha code it seems that
porting Wok to the new version won’t be difficult:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><a
moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://v4-alpha.getbootstrap.com/migration/"><a class="moz-txt-link-freetext" href="http://v4-alpha.getbootstrap.com/migration/">http://v4-alpha.getbootstrap.com/migration/</a></a><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
</blockquote>
Samuel, Thanks for the RFC !!!<br>
For my education, is this official final bootstrap 4 version or
is it still kind of non stable version (alpha sounds like that
to me) ? If so when will be the official bootstrap 4 ?<br>
<blockquote
cite="mid:d35dccff9b8b45d1bc980902f681865d@serv031.corp.eldorado.org.br"
type="cite">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US">-Browser Support:
Ok!<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">-SCSS environment:
Ok!<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">-Dropped glyphicons:
Ok! We already use Font-Awesome<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">- Non-responsive
usage of Bootstrap is no longer supported: Ok!<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">I recognize some
classes from this document and I think that a minor
drawback would be with the Media Queries that were
already implemented throughout the application and some
changes with the classes names. Ginger uses a lot of
“panel-“ classes that were replaced by “cards”, the
“btn-default” button was renamed to “btn-secondary” and
etc.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">The major issue is
with jQuery Bootgrid plugin. It seems that they’re not
planning to port to Bootstrap 4 until it gets stable. I
think we should port our jQuery Bootgrid code to
Datatables.net, since it has a vast documentation and it
already supports Bootstrap 4:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><a
moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://datatables.net/examples/styling/bootstrap4.html"><a class="moz-txt-link-freetext" href="https://datatables.net/examples/styling/bootstrap4.html">https://datatables.net/examples/styling/bootstrap4.html</a></a><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Any comments? </span></p>
</div>
</blockquote>
This will be major concerns as I feel lot of work if we have to
do this.<br>
<br>
When you say "<span lang="EN-US">It seems that they’re not
planning to port to Bootstrap 4 until it gets stable"? Do you
mean until bootstrap 4 not stabilized bootgrid team will not
port or bootgrid itself have stabilization issues and they
would not port until they stabilize </span><span lang="EN-US"><span
lang="EN-US">bootgrid </span>?<br>
<br>
If we have an answer that bootgrid team will wait till
bootstrap 4 get stabilized then I would not hurry in porting
our </span><span lang="EN-US"><span lang="EN-US">jQuery
Bootgrid code</span> to </span><span lang="EN-US"><span
lang="EN-US">Datatables.net</span>, since it will involve
huge effort in porting and at the same time in testing.<br>
</span></blockquote>
<br>
I agree. Perhaps we should wait until Bootstrap 4 is stable too
...<br>
<br>
<blockquote
cite="mid:201605240859.u4O8wmN6012164@mx0a-001b2d01.pphosted.com"
type="cite"><span lang="EN-US"> <br>
So in my opinion, readiness is good idea but at the same time
we have to make sure we are not spending efforts in porting
any of the existing code unless we know that there will be no
support at all !!!<br>
<br>
We have to take conscious decision !!! <br>
</span>
<blockquote
cite="mid:d35dccff9b8b45d1bc980902f681865d@serv031.corp.eldorado.org.br"
type="cite">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Samuel<o:p></o:p></span></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Kimchi-devel mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Kimchi-devel@ovirt.org">Kimchi-devel@ovirt.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/kimchi-devel">http://lists.ovirt.org/mailman/listinfo/kimchi-devel</a>
</pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Kimchi-devel mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Kimchi-devel@ovirt.org">Kimchi-devel@ovirt.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/kimchi-devel">http://lists.ovirt.org/mailman/listinfo/kimchi-devel</a>
</pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Kimchi-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Kimchi-devel@ovirt.org">Kimchi-devel@ovirt.org</a>
<a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/kimchi-devel">http://lists.ovirt.org/mailman/listinfo/kimchi-devel</a>
</pre>
</blockquote>
<br>
</body>
</html>