#SCB2986 (In progress) Multiple column display for attributes in Issue Editor

*SCB2986 [Enhancement] - Multiple column display for attributes in Issue Editor*

-------------------------------------------------------------------------------
*Reasons for the changes*
-------------------------------------------------------------------------------
  - Added basic support for inline attributes (svn 10803)
  - There is a technical dependency between inlined attributes and visibility, hence these issues are related. Implementation can probably only take place for both issues at once.


-------------------------------------------------------------------------------
*Personnel changes*
-------------------------------------------------------------------------------
  - Assigned to:  dabbous     (New) 


-------------------------------------------------------------------------------
*Attribute changes*
-------------------------------------------------------------------------------
  - Status:  Unconfirmed --> In progress  


-------------------------------------------------------------------------------
*Dependency changes*
-------------------------------------------------------------------------------
  - Link: SCB2987 is related to SCB2986 ()


*Comment Hussayn Dabbous*

I have started with a simple implementation. While i was workiung on it, i detected several problems, which
i need to take care off:

* How can i declare, which attribute shall be "inlined" ?

I made a quick and dirty decision: 
In the issueType editor, where you declare which attributes shall be displayed in which order you can define
a "project-name" for each attribute. There i have added a "name parser" as follows:

{{{
if (the attribute name starts with "append:" )
{
   remove the prependix "append:" and use the trailing characters as the attribute name.
   Instead of placing the attribute into the next line, add it to the current line
}
}}}

* How can i align Attributes ?

Currently you can't. The main problem is because of text area-fields and long single-line fields. Those attributes typically span over the whole screen width. So if i would add table columns for the extra attributes in one line, that would destroy the display of the long width fields, because the <TD></TD> containers won't match. Hence i have decided to add follow-up attributes within <SPAN></SPAN> containers which will be appended as needed to the current line. Now there is a chance to try it with css-declarations, but that needs some additional investigations. It still is not clear to me, how to proceed here. 

To say it in short: don't use that feature, if you don't like it. It does not affect Scarab's standard behaviour.

* There is another issue with "visible only when required attributes" (see follow up issue) which is technically coupled with this issue. Here i need to take care about what happens with such attributes.

-------------------------------------------------------------------------------
Activity generated by Hussayn Dabbous ([email protected]) at 07/16/2009 10:17

[Scarab]: http://www.solitone.org/scarab/issues/id/SCB2986

------------------------------------------------------
http://scarab.tigris.org/ds/viewMessage.do?dsForumId=458&dsMessageId=2371700

To unsubscribe from this discussion, e-mail: [[email protected]].