Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation on 12/28/19 in all areas

  1. If an object implements many interfaces it handles many responsibilities and not only a single one (SRP). You can use aggregation and delegation of those interfaces.
  2. Wow. After so many years of working with Delphi I have just noticed that you can paste code into the watch list 🤪 Or did I install some experts?
  3. Alberto Miola

    New section for native apps

    I have been talking with Yaroslav Brovin recently (the creator of FGX native) and this project is going to be in public beta at the beginning of 2020. Would it be a good idea to make a section for it? If not now at least when the beta starts. FGX native will be an add on for the Delphi IDE This is a webinar unfortunately only in Russian; btw this will work for Android only at the beginning, iOS will come later. I attach some pictures of the documentation. More info on FGX are here: http://fire-monkey.ru/forum/370-native-fgx/ (use https://translate.yandex.com/ which is a good russian-english translator)
  4. Dmitriy M

    paste into watch list

    Another non-obvious trick is that you can drag&drop selected identifier/expression (double click to select) into the watch list.
  5. Even trivial changes consume project resources and resources are finite. Implementing a low priority change takes resources away from higher priority changes and unless there's something wrong with way changes are prioritized I can't really see how one can justify that. The really hard part is weighing all the different factors when calculating the priority. Giving a ticket priority just because it's old doesn't make much sense. But if the age will cause enough customer dissatisfaction that it ends up having economical consequences then it might make sense. Apart from that I don't think age should be a factor. Each time we go through our ticket list we look at it fresh: At this point in time, what is the most important change for us to focus on. In my projects it's common for trivial but very low priority changes to be rejected. I think it's better to let the requester know that there's minimal chance their request will ever be granted, given that there will always be more important changes to work on, than to give them false hope.
×