Question RC02 | threads layout: 1. Numbered topic only all? | 2. No title post subject?

Reading the forum with threads is important for me, in some cases even the most important.
A clear and complete view of threads can running hot conversations with many participants without a great number of quotations which sometimes kills the reading. Many forums have still not coped with this problem. Kunena with a few modifications (sorry, according to a layman ...) To achieve complete success.
According to me, in the current version of threads, the forum can not read at least comfortably.
In particular, a description of the spoiler is indicated in the illustration.

So I reported this as a bug.

I understand that there is so much work, that this can be considered as a future option than an error.

Please transfer it topic of your choice.

Best Regards!

I agree that bad usability issues can be thought of bugs. I also agree that this issue should be fixed. But what I don't agree is that we should fix this before Kunena 2.0 gets out.

We cannot afford postponing Kunena 2.0 anymore as it has hundreds of fixes and improvements over Kunena 1.7.2. That's the main reason we decided to remove many of the new features which are already mostly implemented (but not well tested or missing small parts) -- like our new template. Another reason to release stable now is to get all 3rd party migrations updated.

All usability issues are considered as either features or bug fixes for Kunena 2.1 and later. We aren't fixing any old usability issues in the old template as it's already deprecated. Fixing usability issues in Blue Eagle would mean duplicating our efforts, which would mean considerable delay in our development and public releases.

I think your team is very, very creative group of people consistent great enthusiasm and approach to work.

I have seen many different ideas that have a great idea but the contractor break down like children when the project came out of the shadows. Looking at your work organization and the progress you are certainly not in danger.

Therefore wieli respect and understanding for you and your team. You'll want to look at it and add something from yourself.

Or something like that does not discourage applicants, but not overworking and stressing the Kunena team.
It's always possible that it is better known . It is important that progress is still at work and there is hope for the future.

Perhaps such a solution like this better ordered influence and recurring themes?
enough to be solved as such entry:

www.kunena.org/forum/119-Feature-Request...pic-as-solved#126213

"Yes, we see the problem. Thank you for reporting we have added it to realization. Completion date is not known today. We try to as soon as possible."
Or
"No. I'm sorry but I do not see this issue. This requires further discussion. We will follow the development of this topic in our forum."

In addition to possibly Support forum section divided into the following categories. (since the introduction of key words is probably a big deal?):
General Settings |->Solved
Functionality |->Solved
Layout |->Solved
User Detail |->Solved
Monitoring |->Solved
Uploads |->Solved
BBCode |->Solved
Security |->Solved

Solved Topics automatically move and close?

Once again I apologize for the "know everything". Certainly it is not. I have great respect for your work.

Now I do not know whether to write on your comments? If so, where? Where to find information if my case is already reported by someone before?

I know this is detail... but often it is they who decide about our choices.

Please think about the change of button "Reply Topic". According to me it's worth doing.


Regards!

sozzled wrote:

MarioMari wrote: The solution seems to be adding a new button "Reply to the topic" next to "Reply" ... I suggest modifying the post editing window, so as to enforce proper operation.

I disagree with ... these suggestions. [This] category is for reporting things broken or defective in testing K 2.0. I am not sure if there is something broken. Suggestions for improving Kunena should be made in the Feature Request category. We do not have time to fix this problem in the ways you have suggested but thank you for your suggestions.

We have nothing further to add to our earlier response at this time.

And so much is done. Tank You!

So it may come in handy once more:
www.kunena.org/forum/119-Feature-Request...?limitstart=0#126322