Go Down

Topic: Need a list of changes as they are implemented (Read 4254 times) previous topic - next topic

Robin2

Nov 05, 2014, 10:53 pm Last Edit: Nov 06, 2014, 11:01 am by Robin2
Over the past few days a number of issues that we have complained about have been fixed - which is great.

For example, first the Code Box had no limit, then it was small and could not be extended and now AFAIK it can be extended. (EDIT to add - not yet, it can't - 06 Nov 2014)

It is important that the Arduino Team should publish details of these changes as they are made. If not the details of them will all be forgotten the next time an upgrade is needed.

There is also a need to publish the exact specifications of a change - for example (with made-up numbers) the Code Box default max size is 9 lines and it can be extended to 100 lines.

The reason for publishing these details is that they give users a chance to spot silly things that the team may not be conscious of.

If it is more practical for the team to manage this list in Github that is fine with me. I just want a system where the changes are publicly recorded as they are made. And I do appreciate that there will be security changes which should not be made public.


...R
Two or three hours spent thinking and reading documentation solves most programming problems.

UKHeliBob

Quote
and now AFAIK it can be extended.
Not here using Windows 7 and Chrome
Please do not send me PMs asking for help.  Post in the forum then everyone will benefit from seeing the questions and answers.

nickgammon

For example, first the Code Box had no limit, then it was small and could not be extended and now AFAIK it can be extended.
Not in Australia it can't be.
Please post technical questions on the forum, not by personal message. Thanks!

More info: http://www.gammon.com.au/electronics

Robin2

Humble apologies for the confusion folks.
I've just realized I was playing with a very small code box - which can be extended to the 9-line max.

I hope this doesn't detract from the principal message of this Thread.

...R
Two or three hours spent thinking and reading documentation solves most programming problems.

UKHeliBob

Please do not send me PMs asking for help.  Post in the forum then everyone will benefit from seeing the questions and answers.

Robin2

http://forum.arduino.cc/index.php?topic=274511.msg1950456#msg1950456 May be of interest
Not sure what that has to do with keeping a public record of the changes that are implemented ?

...R
Two or three hours spent thinking and reading documentation solves most programming problems.

UKHeliBob

Quote
Not sure what that has to do with keeping a public record of the changes that are implemented ?
Nothing, but it has everything to do with the ability to change the size of the code box.  My fault for not quoting reply #2
Please do not send me PMs asking for help.  Post in the forum then everyone will benefit from seeing the questions and answers.

nickgammon

It is important that the Arduino Team should publish details of these changes as they are made. If not the details of them will all be forgotten the next time an upgrade is needed.
This should be happening on the GitHub issues list (however as we noticed in this thread that does not always happen).
Please post technical questions on the forum, not by personal message. Thanks!

More info: http://www.gammon.com.au/electronics

TomGeorge

Hi, I am finding the number of new forum members who do not know about the code tags a pain in the a???, along with small font.

Hows about making the code tags icon BIGGER and DARKER in color and WRITE IN IT    CODE TAG, the same for all the other icons.

Even I have trouble finding it and I know about it, sorry guys but EVERYTHING has been made smaller, instead of READABLE,\.
We don't have 100cm computer monitors.
Please, the guys that are developing the forum code, go back to basics, use a 14inch laptop with NO BELLS and whistles and make it work.
[soapbox]
As I said, make everything readable and usable.
Mobile phones originally started to get smaller and smaller, they are now bigger then ever, do you wonder why, I understand you can't read what somebody has said about you on facebok or twister on and old phone.
[/soapbox]

Tom........ :)
Everything runs on smoke, let the smoke out, it stops running....

Robin2

Hi, I am finding the number of new forum members who do not know about the code tags a pain in the a???, along with small font.
I agree with you. But what has that got to do with this Thread?

Why not start a new FEATURE REQUEST thread?

...R
Two or three hours spent thinking and reading documentation solves most programming problems.

TomGeorge

Hi, there are too many threads already about forum programming , this is a series of problems that should have a direct address to the programmers, just like Report to Moderator, just that they have enough to do, another thread and another thread for each problem found would not be fruitful.

Tom...... :)
Everything runs on smoke, let the smoke out, it stops running....

floresta

I agree with you too but I don't agree with you tacking your request for a one specific improvement onto a thread that is dealing with how bugs etc are reported and tracked.

Your well founded request is more likely to be missed by those who are more interested in changes  rather than in a list of changes.

Don

nickgammon

#12
Nov 08, 2014, 04:22 am Last Edit: Nov 08, 2014, 04:23 am by Nick Gammon
I emailed Luca Cipriani (who is mastrolinux on this forum) who responded that he preferred suggestions on the GitHub site (presumably make a new "issue" per suggestion): https://github.com/arduino/forum-issues/issues/

Failing that, if you prefer to use this forum, make a thread per suggestion, with "SUGGESTION:" in the title to make it stand out.
Please post technical questions on the forum, not by personal message. Thanks!

More info: http://www.gammon.com.au/electronics

Robin2

I emailed Luca Cipriani (who is mastrolinux on this forum) who responded that he preferred suggestions on the GitHub site (presumably make a new "issue" per suggestion): https://github.com/arduino/forum-issues/issues/

Failing that, if you prefer to use this forum, make a thread per suggestion, with "SUGGESTION:" in the title to make it stand out.
In view of Luca's reply to me here I am surprised by the first part of your comment. I had the clear impression that what you have in your second part would be the principal way of getting suggestions considered. This is what he said, but you probably need to look at the Thread to see the context.
Quote
Robin2 I agree with you, we should have discussion here and github just for exact tasks and easy manage of issues.
I would also have discussion here for every issue.
I will repeat my objection (as stated in the other Thread) to duplication between Github and the Forum. I want to see the Github list as "read only" for regular Forum users like me.

...R
Two or three hours spent thinking and reading documentation solves most programming problems.

Robin2

with "SUGGESTION:" in the title to make it stand out.
I have already made 2 suggestions with the words "FEATURE REQUEST" in the title.

Should I change that to "SUGGESTION" ?   (serious question)

...R
Two or three hours spent thinking and reading documentation solves most programming problems.

Go Up