2009/8/13 Deryck Hodge <email address hidden>:
> I have some questions about the implementation and differences of style
> between the two screenshots already.
>
> * Since this is a pure two-column page -- the main content and the sidebar --
> do I need to use any of the yui-g/yui-u or top-portlet classes? I didn't use
> any of those classes in this interation.
>
> * The sidebar portlets lack the styling of their use throughout the current
> bugs pages because there isn't a leading portlet id. Should the subscriber
> and search portlets look the same as they do now? Do I add this wrapping
> div? Or is there a way to achieve this already?
I think that the side bar should go, and this page can be converted to
a very simple single column form. Again, this is only going to be used
as a boomerang alternative for inline editing, and as long as it's
easy to go back (using the cancel link or the bread crumbs) I think
that the best thing to do is to keep it very simple.
2009/8/13 Deryck Hodge <email address hidden>:
> I have some questions about the implementation and differences of style
> between the two screenshots already.
>
> * Since this is a pure two-column page -- the main content and the sidebar --
> do I need to use any of the yui-g/yui-u or top-portlet classes? I didn't use
> any of those classes in this interation.
>
> * The sidebar portlets lack the styling of their use throughout the current
> bugs pages because there isn't a leading portlet id. Should the subscriber
> and search portlets look the same as they do now? Do I add this wrapping
> div? Or is there a way to achieve this already?
I think that the side bar should go, and this page can be converted to
a very simple single column form. Again, this is only going to be used
as a boomerang alternative for inline editing, and as long as it's
easy to go back (using the cancel link or the bread crumbs) I think
that the best thing to do is to keep it very simple.