Canceled and Rejected features should not be displayed in the latest features and in the embeded widget
I'm currently developing a Silverlight- Homepage. Now I wanted to integrate the openversion- widget.
Will it take much effort to get this output also in XML- format? This could be like the following:
<project>
<common>
<title>Vote the next features</title>
<projectURL>http://openversion.com/projects/cod4manager</projectURL>
<proposeURL>http://openversion.com/feature/add/project.id/9</proposeURL>
<numberOfFeatures>7</numberOfFeatures>
</common>
<feature>
<title>IntelliSense Support for Config- Plugin</title>
<featureURL>http://openversion.com/features/intellisense-support-for-config-
-plugin</featureURL>
<proposer>MOnsDaR</proposer>
<proposed>10 days, 23 hours</proposed>
<votes>2</votes>
</feature>
[...]
</project>
By providing such XML- Data a developer could choose by himself which info and which format he wants to display. This could be provided parallel to the existing widget.
(Not every developer wants to invest time in placing a custom widget to his/her homepage, but those who want will be provided any data needed in a handy xml- file.)
Will it take much effort to get this output also in XML- format? This could be like the following:
<project>
<common>
<title>Vote the next features</title>
<projectURL>http://openversion.com/projects/cod4manager</projectURL>
<proposeURL>http://openversion.com/feature/add/project.id/9</proposeURL>
<numberOfFeatures>7</numberOfFeatures>
</common>
<feature>
<title>IntelliSense Support for Config- Plugin</title>
<featureURL>http://openversion.com/features/intellisense-support-for-config-
-plugin</featureURL>
<proposer>MOnsDaR</proposer>
<proposed>10 days, 23 hours</proposed>
<votes>2</votes>
</feature>
[...]
</project>
By providing such XML- Data a developer could choose by himself which info and which format he wants to display. This could be provided parallel to the existing widget.
(Not every developer wants to invest time in placing a custom widget to his/her homepage, but those who want will be provided any data needed in a handy xml- file.)
If there is a request which is already entered (and not recognized by the "Double Entry Check") let the developer merge them together.
There could be another item in the "What do you wanna do with this feature"- Item. There could be a TextBox to enter the IDs.
Another solution would be drag'n'drop. But don't know if it is possible.
There could be another item in the "What do you wanna do with this feature"- Item. There could be a TextBox to enter the IDs.
Another solution would be drag'n'drop. But don't know if it is possible.
Planned
Add some sort of payment feature
I assume that once a feature is implemented, the sponsorship that I already agreed to provide is something that I need to sort out with the developer.
Some sort of payment feature managed by the site itself could come in handy.
Some sort of payment feature managed by the site itself could come in handy.
When someone adds a feature, display all possible duplicates
Previous
| Page 1 |
Next

proposed by