the module gets it's data from the project vote smart API, which is exposed
in XML and JSON, meaning that we don't need a drupal backend (or any back
end) to consume it - we can consume it on the client-side (in javascript)
and display it there. this is reasonably easy stuff, and i doubt we'd need
to store any of the data coming out of that API in our back-end.
/dust
On Sun, Mar 20, 2011 at 4:30 PM, Adam Sheesley <email address hidden> wrote:
> Ah, I didn't catch the module at the bottom of the API page. I've got a
> wee bit of experience ripping apart and putting together Drupal modules, so
> if it needs modification I can handle that.
>
>
> On Sun, Mar 20, 2011 at 1:01 AM, Joshua Utter <email address hidden>wrote:
>
>> My understanding of the Drupal module is that it was developed with
>> limited features for the 2008 elections, and it hasn't seen much action
>> since then.
>>
>> --
>> You received this bug notification because you are a member of OSDF Dev
>> Team, which is subscribed to Open Source Democracy Foundation.
>> https://bugs.launchpad.net/bugs/738483
>>
>> Title:
>> Incorporate Project Vote Smart Widget/API
>>
>> Status in Open Source Democracy Foundation:
>> New
>>
>> Bug description:
>> A breakdown of the API can be found here:
>>
>> http://www.votesmart.org/services_api.php
>>
>> and the widget here:
>>
>> http://www.votesmart.org/services_widgets.php
>>
>> One of these would be extremely useful for aiding our contact
>> campaigns, and for general research. My thought is that the widget
>> would be nice, but the more feature-rich API would be preferred for
>> best results. Being that I am not coding anything on the site, I hope
>> someone else weighs in on which would be best and why.
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~osdf-devteam
>> Post to : <email address hidden>
>> Unsubscribe : https://launchpad.net/~osdf-devteam
>> More help : https://help.launchpad.net/ListHelp
>>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~osdf-devteam
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~osdf-devteam
> More help : https://help.launchpad.net/ListHelp
>
>
the module gets it's data from the project vote smart API, which is exposed
in XML and JSON, meaning that we don't need a drupal backend (or any back
end) to consume it - we can consume it on the client-side (in javascript)
and display it there. this is reasonably easy stuff, and i doubt we'd need
to store any of the data coming out of that API in our back-end.
/dust
On Sun, Mar 20, 2011 at 4:30 PM, Adam Sheesley <email address hidden> wrote:
> Ah, I didn't catch the module at the bottom of the API page. I've got a /bugs.launchpad .net/bugs/ 738483 www.votesmart. org/services_ api.php www.votesmart. org/services_ widgets. php _______ _______ _______ _______ _______ _____ /launchpad. net/~osdf- devteam /launchpad. net/~osdf- devteam /help.launchpad .net/ListHelp _______ _______ _______ _______ _______ _____ /launchpad. net/~osdf- devteam /launchpad. net/~osdf- devteam /help.launchpad .net/ListHelp
> wee bit of experience ripping apart and putting together Drupal modules, so
> if it needs modification I can handle that.
>
>
> On Sun, Mar 20, 2011 at 1:01 AM, Joshua Utter <email address hidden>wrote:
>
>> My understanding of the Drupal module is that it was developed with
>> limited features for the 2008 elections, and it hasn't seen much action
>> since then.
>>
>> --
>> You received this bug notification because you are a member of OSDF Dev
>> Team, which is subscribed to Open Source Democracy Foundation.
>> https:/
>>
>> Title:
>> Incorporate Project Vote Smart Widget/API
>>
>> Status in Open Source Democracy Foundation:
>> New
>>
>> Bug description:
>> A breakdown of the API can be found here:
>>
>> http://
>>
>> and the widget here:
>>
>> http://
>>
>> One of these would be extremely useful for aiding our contact
>> campaigns, and for general research. My thought is that the widget
>> would be nice, but the more feature-rich API would be preferred for
>> best results. Being that I am not coding anything on the site, I hope
>> someone else weighs in on which would be best and why.
>>
>> _______
>> Mailing list: https:/
>> Post to : <email address hidden>
>> Unsubscribe : https:/
>> More help : https:/
>>
>
>
> _______
> Mailing list: https:/
> Post to : <email address hidden>
> Unsubscribe : https:/
> More help : https:/
>
>