<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<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:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">So I’ve switch to using the name step attribute as a sort of title for each build step and it looks a lot nicer. I’ve also cleared the two description attributes because I’m not sure what they add. Maybe it’s
best to let the base classes put info in there? Still feels like these should be in a metadata attribute to me.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">-Greg<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> users [mailto:users-bounces@buildbot.net] <b>On Behalf Of
</b>Greg MacDonald<br>
<b>Sent:</b> Wednesday, February 03, 2016 1:54 PM<br>
<b>To:</b> users@buildbot.net<br>
<b>Subject:</b> [users@bb.net] metadata properties<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hi Everyone,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">For the build UI page I don’t understand why the a class property is used as the main line for the build step. My users don’t care that it’s a p4 step or a shell command, they’d rather see something like, “Generating Meshes” and pretty
much only that with some timing info and status. They also don’t care about build properties. But I need that info while I work with the system. Same goes for the skip/hide properties. I’m setting some properties to large lists which end up printing text all
over the screen in a very ugly manner. I could hide it, but I need that info.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">So I’m going to have to rewrite this for our purposes, which is fine. I’m really starting to enjoy coffeescript and angular. But it leads me to think that perhaps visual properties like step descriptions, skips, and hides should be kept
separate from the main system. Someone could rewrite the entire UI and then those properties end up being unnecessary. I think some separation of concerns might be good. How about we add an optional metadata property which contains a dictionary? The web pages
could pick it up and use it for whatever they needed. It decouples things and allows third party UI to have their users add per step properties, or any of the objects in the data model.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">On a related note the issue I had with builder names being restricted to 20 characters with the dataService api wouldn’t matter so much. And having an internal terse name makes it easier for me to develop as well, saving the flowery more
verbose stuff for the visuals.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">-Greg<o:p></o:p></p>
</div>
</body>
</html>