Closed (duplicate)
Project:
Drupal.org CVS applications
Component:
new project application
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
4 Nov 2009 at 18:50 UTC
Updated:
18 Sep 2019 at 07:02 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
vgarvardt commentedHere is my module for review.
Comment #2
avpadernoComment #3
avpadernoSee the Drupal coding standards to understand how a module code should be written.
Comment #4
vgarvardt commentedSorry for this omission.
Fixed all code formatting and added some comments.
Also checked module with coder module - it shown no warnings.
Uploading updated code.
Comment #5
evlad commentedvery interesting project.
go go go!
subscribing
*привет с Хабра
Comment #6
avpadernoThat is not how the coding standards say to write the code.
I think that the FAPI allows to create a select form field.
That string should be removed.
Considering that by default, all modules have a weight set to 0, the code could be simpler.
It is preferable to use
variable_del()to remove Drupal variables.Comment #7
vgarvardt commentedI need to do this manually because I'm adding class attribute to every option and FAPI does not allow this.
All another issues will be fixed today.
Comment #8
vgarvardt commentedFixed all notices except the 2nd one - please see comment above.
Moved part of html code generation to template and added theme that utilizes this template.
Here is updated module version.
Comment #9
avpadernoNot using the form API to built the form field would probably render it differently from the form field as generated from the FAPI.
To make an exemple, the form field shown for below is rendered by the following HTML code:
I am not sure if being able to set different HTML attributes for each select option is worth the fact the form field could not be rendered differently from the other form fields of the same type rendered through the form API.
Comment #10
vgarvardt commentedThis element should be simple select form element and takes all styles that current Drupal theme applies to select elements.
If user is going to override theme_select with something that is not html select (e.g. some JS component that behaves like html select) then my component behavior can be broken (if it will be overriden with something that behaves like html select, but it's not real html select). If my component will have completely different look'n'feel than user's theme, then developer can implement new block theme and plug it in to my module (it has hooks for plugging in new providers and themes).
Comment #11
avpadernoThat depends from the theme being used; the form field created from the form API has the CSS class , and it is contained in a tag DIV with CSS class .
Comment #12
vgarvardt commentedHere is updated module. I added here one more theme called Default and set it as default theme. This theme almost the same as Dropdown theme but uses FAPI to create all form fields. As FAPI can't add attributes to option elements there are no icons in select for this theme.
Also refactored code a little to move some repeating code to functions.
Comment #13
avpadernocheck_plain()is not thought to be used with a domain name; if you want to be sure the input passes is a true domain name, then you need to use a different function.Comment #14
vgarvardt commented- removed
check_plain()from LiveJournal OpenID URL generation- added validation for LJ OpenID URL, so now Drupal handles user input validation with
valid_url()- added support for myOpenID provider
Comment #15
avpadernoThere is already a module for the same purpose: http://drupal.org/project/comfortid.
Comment #16
vgarvardt commentedcomfortid module:
- no public releases
- last commit was more than a year ago (August 11, 2008)
- only 1 dev version released more than a year ago (August 11, 2008)
- code does not match Drupal coding standards
Comment #17
avpadernoThose are still no reasons to create a duplicate of a module that already exists in Drupal.org.
Comment #18
vgarvardt commentedThank you for your time. It was great experience for me for contributing a Drupal module.
For the last month I refactored lots of code, added some features to the module and finally stuck because of unsupported module "duplication". There is a good proverb in Russia about this situation. I don't know how to translate it without loosing its meaning, but the main idea is - if you are The First One everything else does not matter at all.
As I don't see any prospect for this module on drupal.org so you may decline my CVS application and close this issue.
PS: maybe you should change your review stages order and start from finding duplicates - it will take much less time both for you and modules authors and will not require code review.
PPS: I wonder how much time it takes for reviewing really big modules of the same "weight category" as Views and CCK.
Comment #19
avpadernoAs per previous comment, I am marking the report as .
Comment #20
esteewhy commentedIt's pity to see Your work is not on drupal.org still. Anyway, could You please host it on Google Code or elsewhere?
Comment #21
vgarvardt commentedIf someone is interested - module is hosted on GitHub now http://github.com/vgarvardt/Extenal-Login
openid_ext branch is for the v1.0 of the module I tried to post here.
master branch is for v2.0 - Facebook and VKontakte is going to be added there.
Comment #22
jenesis commentedIt Supports vkontakte (the biggest russian social network) and "Comfortable OpenID Login Box" doesnt.
"Comfortable OpenID" is abandoned its clear that nobody will use it.
Comment #23
avpadernoThere is nothing to review; see the comments from #15 to #18.
Comment #24
nleo commentedhttp://drupal.org/project/comfortid
Maintenance status: Abandoned
Opposite vgarvardt have begun develop in Oct 2009. Latest release have date July 05, 2010
Don't understand why you not allow this module. marasmus
Comment #25
avpadernoSee comment #18, and previous ones.
Comment #26
avpaderno