<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#333333" bgcolor="#FFFFFF">
Thank you, I absolutely agree with you and I added some reactions
below quotes.<br>
<br>
<div class="moz-cite-prefix">On 3.8.2012 19:40, Matt Wagner wrote:<br>
</div>
<blockquote
cite="mid:20120803174047.GB24323@mawagner-desktop.usersys.redhat.com"
type="cite">
<pre wrap="">On Fri, Aug 03, 2012 at 05:42:13PM +0200, JaromÃr Coufal wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hey guys,
I just wrote some information on wiki-page about UI tasks regarding
form unification:
<a class="moz-txt-link-freetext" href="https://www.aeolusproject.org/redmine/projects/aeolus/wiki/Consistent_forms_in_Conductor_UI">https://www.aeolusproject.org/redmine/projects/aeolus/wiki/Consistent_forms_in_Conductor_UI</a>
My main question is about using tools like Simple Form and Bootstrap
(they are *not* alternatives). I reviewed some advantages,
disadvantages, provided links, so you can look for further
information if you want to and if anybody has something to add /
discuss, you are more than welcome :)
</pre>
</blockquote>
<pre wrap="">
I think this task is overall a really fantastic thing to do. As you
noted previously, we're not even _close_ to consistent right now.
I've worked with formtastic in the past; it looks like simple_form
builds on that. The only downside I ran into is the difference in names
for many field types, which isn't really that big of a deal. If it makes
our lives easier, I'm all for it.</pre>
</blockquote>
Actually I don't know formstatic project, but as for Simple Form,
there is quite a rich library of field types to use and looking over
them I guess that names match pretty well to their types
(<a class="moz-txt-link-freetext" href="https://github.com/plataformatec/simple_form/#mappingsinputs-available">https://github.com/plataformatec/simple_form/#mappingsinputs-available</a>)
so it looks that they fixed this issue. Or did you mean something
else?<br>
<blockquote
cite="mid:20120803174047.GB24323@mawagner-desktop.usersys.redhat.com"
type="cite">
<pre wrap="">I think you are already doing this, but for the sake of stating the
obvious, we should probably work with Katello to define a common
pattern for forms between apps. As you state on the wiki page, we can
probably use simple_form without requiring them to do the same (though
things like the login page might become special cases), but I think a
styling guide for forms that's consistent between projects would be
great.
</pre>
</blockquote>
Even obvious things are worth to be said, you never know :) And
actually this is really great point. I already had a call with Eric
Helms and Jason Rist about forms in Converge-UI (and this means also
in Katello) and it appears that they don't use any specific tool. I
also told them about my intention to work on forms and contributing
to the library, so I will stay in close cooperation with these guys
in order to ensure that the result is usable across projects.<br>
<br>
As for the library use, I would like to see Converge-UI working in a
way to:<br>
1) define how the structure of HTML elements should look like (and
let implementation details on project itself)<br>
2) provide CSS styles which ensure that forms (or in the future any
element) appear the same way across all projects<br>
... (excluded some specific sections, as login, which are special
cases)<br>
<br>
So as you stated, I agree that it would be better to keep Simple
Form just for us and let Katello to decide how they will implement
forms.<br>
<blockquote
cite="mid:20120803174047.GB24323@mawagner-desktop.usersys.redhat.com"
type="cite">
<pre wrap="">
-- Matt</pre>
</blockquote>
Thank you<br>
<pre class="moz-signature" cols="72">--Jarda
</pre>
</body>
</html>