Difference between revisions of "Issues:006"

From its-wiki.no
Jump to: navigation, search
Line 58: Line 58:
 
|Response Date=2015/10/21
 
|Response Date=2015/10/21
 
|Response By=Josef.Noll
 
|Response By=Josef.Noll
 +
}}
 +
{{Response Template
 +
|Response=Hi Josef.
 +
 +
We can salvage the free text that is currently captured by using a replace text regex to assign it to a new field in the template. I suggest we call the new field "Item Text" to replace the free text element.
 +
 +
I am working on the new user page. I'll let you know when it's in a state to demo.
 +
|Response Date=2015/10/28
 +
|Response By=Neill
 
}}
 
}}

Revision as of 09:15, 29 October 2015

Go to Issue Log page
Headline "Free form" normal text input before search elements
Status Accepted
Issue ID 006
Issue Type Enhancement
Priority Normal
Description I'd like to build up pages where some "semantic information" comes first, then I'll have space for free text input, and then the rest of "semantic information".

Taking the user page, like Josef Noll. I'd like to have

  • name, contact info, picture, and tag cloud first
  • The the free input, e.g. About, references...
  • Then information like project leadership, participation in meeting,

Currenlty the page is define through Template:User, where a lot of semantic queries are added. All of these queries are shown prior to the information "About the user".

Page Link Josef Noll
Screenshot Screen Shot 2015-09-10 at 21.14.26.png
Created By Josef.Noll
Date Added 2015/09/10


Response If we switch to using forms and templates for content pages, then this is entirely possible. The dev sites I gave you access to show how you can add sophisticated layouts to pages if templates are used across the site.
Page Link
Responded by Neill
Response Added 2015/10/06


Response Hi Josef.

Would you like me to come up with a new user page design using a form and template? We could also have it so they are auto created when a new user is added.

Page Link
Responded by Neill
Response Added 2015/10/15


Response Hei Neill,

1) yes, please go ahead with a new user page design. I am currently using "Template:User" and "Form:User" for these pages, thus I suggest you rename them to "User_2014" and start from scratch. The user pages are already autocreated, see "All" or "All participants".

2) Could you do a quick fix with the Form:IoTSec_AI and Template:IoTSec_AI, used in creating ActionItems from the IoTSec.no page? 3) while doing so, can you check why cols=1 (or cols=10) does not work for the User field in the action items? Every new action item has a long field for Action Items

Page Link http://cwi.unik.no/wiki/IoTAdmin:AI-001
Screenshot Screen Shot 2015-10-18 at 11.53.03.png
Responded by Josef.Noll
Response Added 2015/10/18


Response Hi Josef.

Unfortunately Free Text is always shown after the template content. I never use SF's Free Text because you have absolutely no control over it's styling. It would be better to use a form/template field to capture and display this text (it doesn't have to be stored in a property). We can probably use a cunning replace text regex to take the existing free text content and convert it into a field.


I have sorted out the size of the User field and Title field. SF now defaults to input type of textarea for text fields. So I have told it that the Title field is input type text which then obeys the size parameter. The User is an array type so needed the size parameter rather than rows and cols :) I'll look at the CSS to sort out the ugly alignment of the dates.

Page Link
Responded by Neill
Response Added 2015/10/19


Response Hi Neill,

perfectly okay to omit the "free text" input. What do you suggest we use? We can start from Scratch for Users, as almost no user has information about himself on the page (some might). Thus, please provide me with an example for a new "User" page. Do you recommend to move them into the "Namespace User:Josef_Noll"?

Page Link
Responded by Josef.Noll
Response Added 2015/10/21


Response Hi Josef.

We can salvage the free text that is currently captured by using a replace text regex to assign it to a new field in the template. I suggest we call the new field "Item Text" to replace the free text element.

I am working on the new user page. I'll let you know when it's in a state to demo.

Page Link
Responded by Neill
Response Added 2015/10/28