I don't like iframes either, but it is a lot simpler to set up than xml-rpc. Allthough, I would prefer a xmlrpc solution, or both.<br><br><div><span class="gmail_quote">On 11/20/06, <b class="gmail_sendername">Corey Bordelon
</b> <<a href="mailto:corey.bordelon@gmail.com">corey.bordelon@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
It looks like with the suggestions for XML-RPC calls would allow the modulecheck to be run with the cron hook. That way, everytime an admin looks at their modules page, it wouldn't be a call to <a href="http://drupal.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
drupal.org</a>, like an iframe would. Also, I'm not crazy about iframes, but I could in be a minority on that point.<div><span class="e" id="q_10f05e24736a8697_1"><br><br><div><span class="gmail_quote">On 11/19/06, <b class="gmail_sendername">
Arnab Nandi</b> <<a href="mailto:arnab@arnab.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
arnab@arnab.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">What about simply having an iframe to<br><a href="https://drupal.org/modulecheck/modulename" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
https://drupal.org/modulecheck/modulename</a>, which returns a "You're<br>running the latest version" normally, or a button saying "click here<br>to upgrade" otherwise. The button essentially pionts to the changelog
<br>/ install notes. (later, the button can point to the installer which<br>autoupgrades stuff).<br><br>-Arnab<br><br>On 11/19/06, Bèr Kessels <<a href="mailto:ber@webschuur.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
ber@webschuur.com</a>> wrote:<br>> Op zaterdag 18 november 2006 18:41, schreef Karoly Negyesi:
<br>> > In overall this solution is not enough because you many modules but by far<br>> > not all from contribs, so neither a per module feed or an eat-it-all feed<br>> > won't suffice. So definitely we need more code in project.
<br>><br>> I never said it would be enough. All I said is that, instead of talking for<br>> ages here about that utopian solution, then get into developing some whole<br>> new release-pushing-xmlrpc-system, we can offer a default RSS feed with block
<br>> NOW.<br>><br>> As in: now. Not something in some future after some unknown development cycle.<br>><br>> Bèr<br>> --<br>><br>> Drupal, Ruby on Rails and Joomla! development: <a href="http://webschuur.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
webschuur.com</a> | Drupal hosting:<br>> <a href="http://sympal.nl" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">sympal.nl</a><br>><br><br><br>--<br><a href="http://www.arnab.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://www.arnab.org</a><br></blockquote></div><br>
</span></div></blockquote></div><br><br clear="all"><br>-- <br><br>// Johan Forngren<br><br>/****************************************<br>Email: <a href="mailto:johan@forngren.com">johan@forngren.com</a><br>Site: <a href="http://johan.forngren.com/">
http://johan.forngren.com/</a><br>Skype: forngren<br>MSN: <a href="mailto:johan@forngren.com">johan@forngren.com</a><br>IRC: forngren @ freenode<br>Jabber/GTalk: <a href="mailto:forngren@gmail.com">forngren@gmail.com</a><br>
****************************************/