Posted by Ole Martin on June 14, 2010 at 1:21pm
3 followers
Jump to:
| Project: | Arrange Fields |
| Version: | 6.x-1.0-beta1 |
| Component: | Documentation |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (works as designed) |
Issue Summary
Field positions will not change the node view page for the created content. That information will still be displayed the traditional way (straight down the page). This may be something that gets fixed in the future.
We have this one:
http://drupal.org/project/nd
Comments
#1
That's a good one to check out.
What I meant though is I plan to have my module try to keep the same relative positions (in css) for the outputted form data as the form fields themselves (for one thing, so they print nicer). It may not be possible, though, because users could enter, say, 5 paragraphs of text into a text field, which would throw off the positioning.
#2
Hi,
First, arrange_fields is great: thank you! When a node has many fields it makes it much nice to edit.
The grid based layout it just fantastic.
Yes, the next thing would be to handle the display of the node too.. and if possible in this module as opposed to a new one (as the nice grid layout arrange_fields does is more intuitive than ns/ds for me..)
#3
I'll test this when I get a little more time. My pages that I use with Node Display are not showing correct in Safari, Crome and Opera, and my members that use MAC has also problems with the Node Display, so maybe this is the solution?
#4
I'll test this when I get a little more time. My pages that I use with Node Display are not showing correct in Safari, Crome and Opera, and my members that use MAC has also problems with the Node Display, so maybe this is the solution?
#5
----Some thing get wrong with my connection---
#6
Thanks!
I have been thinking about it-- the only way I can think of ensuring that the node display both matches the edit page, as well as keeps the text from one element from overrunning the ones under it or next to it, would be to place everything in precisely sized scrollable div's.
That presents two problems, though: #1, it might look kind of ugly. #2, it wouldn't print nicely. As in, when you go to print, you wouldn't see all of the text in a scrollable div, you'd only see what was visible at the time.
This might be the kind of thing which you can optionally enable on a per-content type basis.
What do you (or anyone else) think? Sound plausible, or is there a better way?
Richard
#7
Personally I'd go for two displays (if conceivable): one for editing one for viewing.
The audiences are different, and may fields may be hidden for normal users in the view mode.
As you note the viewmode might also be laid out to allow easier printing too.
If many other screens like contact forms, user registration, comments could laid out - that it would be just incredible in terms of improving usability. But I don't want to overrun you :-)
Sean
#8
You make a good point.
As far as the other forms (registration, etc), yes, those can theoretically be arranged as well. The code will actually work with any form, not just CCK or Webform (including custom forms which a developer might program himself). I considered coming up with some kind of system for letting the admin user just state the form_id of the form they'd like to be able to arrange.
I will have to do some poking around to see how hard it would be.
Thanks
Richard
#9
Just wanted to let you know-- in the latest release, alpha7, you can arrange the fields of any arbitrary form in Drupal (so long as the structure is not too complex). Just go to admin/settings/arrange-fields, and from there you have a "settings" tab, where you can add any form_id you want to be able to arrange.
Also in the new version, you get a snazzy jquery dialog box for editing properties for each field, including whether or not the label appears inline (also makes radio buttons and checkboxes appear inline).
Richard
#10
@richardp : I've played more with ds/nd - its good, and to me it would make more sense if you try ds/nd also and help out the author of that with your expertise?
If fields arrange concentrates on the node entry form, it covers a specific need - let ds/nd do the node display bit?
If one compares http://drupal.org/project/usage for both projects, ds is much more widely known.
Just my 10 cents and thanks again.
#11
I'll confess that I haven't really had the time to work on this issue, or give nd the time necessary to see if our two approaches are compatible. My impression, though, is that our two approaches wouldn't really work together. As in, I don't think there's any patch I could write which would let nd and arrange_fields share the same data, since they are using regions to set field positions, and I am using CSS relative top and left values, which do not translate to region positions.
Of course, I could be totally wrong. I will download it in the near future and experiment with it. I certainly don't mind handing off the display functionality to another module. And even if I do attempt to tackle the display functionality in arrange_fields, I will definitely make it so it can be disabled (so other modules can have a go at it instead).
Thanks for the 10 cents ;)
Richard
#12
(closing issue)