For a temporarily workaround:

You can add a Gadget to a Googlecode wiki page that mimics the old
'Updates' page. You don't need to be owner, so you can have several
projects in one wiki page

For an example how such 'Updates' looks like, see
http://code.google.com/p/bullet/wiki/Updates

Just copy and paste the following lines in a Googlecode Wiki and
replace "bullet" with your project name.

<wiki:gadget url="http://bulletphysics.org/~erwincoumans/com1.xml";
up_projectName="bullet" width="800"  height="100"/>
= Updates to All Issues (including closed/fixed issues) =
<wiki:gadget url="http://bulletphysics.org/~erwincoumans/gc23.xml";
up_projectName="bullet" width="800"  height="250"/>
= Detailed Updates to Open Issues =
<wiki:gadget url="http://bulletphysics.org/~erwincoumans/t6.xml";
up_projectName="bullet" width="800"  height="250"/>

Not perfect, but better than nothing.
It is best to copy and modify the XML and Javascript files to tweak
the output (I will not keep those files hosted long):

http://bulletphysics.org/~erwincoumans/com1.xml
http://bulletphysics.org/~erwincoumans/com1.js
http://bulletphysics.org/~erwincoumans/gc23.xml
http://bulletphysics.org/~erwincoumans/j10.js
http://bulletphysics.org/~erwincoumans/t6.xml
http://bulletphysics.org/~erwincoumans/s3.js

They are originally from 
http://google-code-project-hosting-gadgets.googlecode.com/svn/build/prod/issueupdates
, with some minor updates.

Hope this helps,
Erwin



On Mar 2, 10:08 am, "silviu.cpp" <[email protected]> wrote:
> Without that update page Google code sucks ! Probably a lot of
> projects will switch to Github.
>
> On Mar 2, 4:22 pm, Rene <[email protected]> wrote:
>
>
>
>
>
>
>
> > I got here because the issue 
> > athttp://code.google.com/p/support/issues/detail?id=24324&colspec=ID%20...
> > was closed for comments but somehow Google wants to keep up the
> > conversation by directing us here. The last comment said:
>
> > > Of course if you have anything to add I welcome you
> > > all to join the existing thread on our Google Group
>
> > What should we add? I think everything has been said but it might be
> > required to summarize it a little bit.
>
> > * The updates page was removed from all projects including the
> > activity meter.
>
> > * Many people complained about that within a few hours.
>
> > * Nobody understood the reason why the page has been removed.
>
> > * The issue has been starred by more than 300 people which puts it
> > into the top 5 issues (within 3 days).
>
> > * The use case is also very clear: There are many users who want to
> > see if a project is active or not so that they do not download
> > software that is badly supported later. And there are many users who
> > want to see at a single glance what happened in the project to react
> > to comments etc.
>
> > * A few work arounds have been suggested but none can fully replace
> > the updates page.
>
> > In my opinion, everything has been said. I am now waiting to get some
> > new information from your side (you = Google). If there is anything
> > that you (Google) want to know, just ask. Otherwise I think it is time
> > for some well-founded explanations or even better a decision to bring
> > the old updates page back or a new one.
>
> > Best regards!
>
> > René

-- 
You received this message because you are subscribed to the Google Groups 
"Project Hosting on Google Code" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-code-hosting?hl=en.

Reply via email to