Re: [Codestriker-user] Feature request (codestriker: message 7 of 20)

[Marc S. <mar...@gm...>]

As of now, I did a simple modifications in the links for all open
topics to push states 0,3.

I will look into adding a new variable @open_states. That would be an
interesting features.

Marc.

On 7/28/05, Dan Prince - dp...@In...
<+codestriker+jafs+abe3cb3e1a.dprince#Int...@sp...>
wrote:
> Comments below...
>=20
> David Sitsky wrote:
> > On Thu, 28 Jul 2005 00:26, cod...@sp... wrote:
> >
> >>It would be nice to have in the config file a value to set the valid
> >>open states, so that when I click on List all open topics, it would
> >>list all valid open states.
> >
> >
> > Have you seen the @readonly_states config variable?  In some sense, wha=
t
> > you are asking for is the inverse of this.
> >
> >
> >>Do you think that feature would be useful to other? As of now, I
> >>modified the template to put [0, 3] to display all open topics.
> >
> >
> > Maybe you can make the code check if the state is not in @readonly_stat=
es,
> > to get the same/similar effect?
>=20
> This would certainly be possible, but I'm not sure it is what everyone
> would want.  Some installations (probably ours, for one, though it's
> probably not a big deal) would want the 'List open topics' link to list
> only topics in state 'open' and not ones in state 'Reviewed', even
> though both are not 'read-only' states (i.e. topics in either state can
> be edited).
>=20
> >
> > Failing that - perhaps you could defined a @open_states config variable=
.
> >
>=20
> I would vote for this option.  I'm assuming it would control only the
> states that get displayed when you click the 'List open states' link,
> and would be different from @readonly_states.
>