Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

761661 - Need inline help text #406

Merged
merged 2 commits into from
Aug 3, 2012
Merged

761661 - Need inline help text #406

merged 2 commits into from
Aug 3, 2012

Conversation

Pajk
Copy link
Contributor

@Pajk Pajk commented Jul 31, 2012

Forms cleanup by using custom katello form builder.

Advantages:

  • highlighted required inputs
  • consistency
  • lot of things can be modified on one place for all forms
  • more readable views

Tipsy help can be added to each input with :help option.

Now it looks like this http://d.pr/i/eCNT.

This pull request doesn't contain help texts yet, if anyone have an idea which inputs need additional help, write it down here please:
https://fedorahosted.org/katello/wiki/FormsInlineHelp

Rewritten _new forms:
activation_keys
cangesets
environments
filters
gpg_keys
organizations
products
providers
systems
users

Forms cleanup by using custom katello form builder.
Tipsy help can be added to each input with :help option.

Rewritten _new forms:
activation_keys
cangesets
environments
filters
gpg_keys
organizations
products
providers
systems
users
$('.details_container').addClass('scroll-pane');
KT.common.jscroll_init($('.scroll-pane'));
}});

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this snippet would be better suited living in public/javascripts/wdigets/tipsy.custom.js

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

@ehelms
Copy link
Member

ehelms commented Jul 31, 2012

@Pajk I think this is a great addition and am glad you tackled it. My only other comment is in regards to the use of the single name variable to define the form in views. Granted, this may only be me, but I generally dislike single letter variables as they contain no context when reading the line by itself. Also, I found myself confusing where the 'f' stood for form or field when reading through the code and had to keep returning to the top to remind myself what it represented.

@ehelms
Copy link
Member

ehelms commented Aug 1, 2012

This looks great to me. ACK.

Default input size to 30.
Help icon tag changed from span to i.
Javascript moved to tispy.custom.js.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants