Needs review
Project:
Comment driven
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
2 Apr 2010 at 10:24 UTC
Updated:
4 Apr 2010 at 14:53 UTC
Jump to comment: Most recent file
Comments
Comment #1
arhak commentednot quite sure what you're requesting
lets take for instance the screenshot you provided at #758086-13: Support workflow states
http://drupal.org/files/issues/works_perfectly_with_6.14_0.png
the schedule time has its description as well as the comment, both of them provided by workflow
are you requesting to add a description to a form element which currently doesn't have it?
if so, it would be either:
- a request to workflow module to provide a description (whether configurable or not)
- or a request to your developers to make a tiny custom module to add such description in a form_alter
or it is something else you're asking for?
Comment #2
arhak commentedBTW, if I understood properly, then this issue would be a "won't fix"
since this module won't afford touching/altering what is not expressly required to perform the intended functionality (otherwise bug reports and feature requests would be endlessly)
think that whatever you might wan't to achieve can be done to node_form (via hook_form_alter) and automatically it will be reflected by comment_driven if it is exposed as an enabled driven property
Comment #3
arhak commentedEDIT: removed (double posted)
Comment #4
Takafumi commentedYes, it is easily solvable by myself.
But if it is supported by driven module, I thought that it is more useful.
Would you reconsider?
Comment #5
arhak commentedlets wait to heard what other users have to say
Comment #6
Takafumi commentedFYI, when a property already has description, I think it is useful to override it.
Because, description which is different in node creation and comment post could be given.
Comment #7
arhak commentedHere you have a couple of working modules
(one is the driven property behavior and the other one is the one altering descriptions for comment driven)
I'm still skeptical to include these into Driven API and Comment driven respectively
users' votes will have the last word
I hope you'll enjoy them,
I also would recommend you to read the code (150 lines altogether)
so you can learn how easy can be a behavior (Driven API) done and how to use it (in this case for onto comment_driven, but it can be on anything related to a node_form, another example would be Node Edition Policy)
Comment #8
arhak commentedfixed a minor imperceptible misnamed default value,
but relevant if you intend to extend these module's functionality later
Comment #9
Takafumi commentedThank you so much, arhak!
I'll enjoy with these modules for a while, and then learn Driven API with your code :)