Difference between revisions of "User:H1manshu/GSoC2022/Log"

From BRL-CAD
(Updated details for 6 and 7 June)
(Updated for 8th June)
Line 1: Line 1:
 
==Dev Log==
 
==Dev Log==
 
(newest first)
 
(newest first)
 +
* '''8 June''': I created a new [https://github.com/BRL-CAD/arbalest/pull/21 pull request] where I added icons for menu items and icon color for both light & dark theme.
 
* '''7 June''': I created a new commit to remove the absolute color of hover for QToolButton. Also, I am currently testing out which color will be best suitable for icons in menu items for both light and dark themes.
 
* '''7 June''': I created a new commit to remove the absolute color of hover for QToolButton. Also, I am currently testing out which color will be best suitable for icons in menu items for both light and dark themes.
 
* '''6 June''': I created a [https://github.com/BRL-CAD/arbalest/pull/20 pull request] to remove border and add padding. I also added '''hover background-color''' to '''QToolButton'''
 
* '''6 June''': I created a [https://github.com/BRL-CAD/arbalest/pull/20 pull request] to remove border and add padding. I also added '''hover background-color''' to '''QToolButton'''

Revision as of 09:31, 9 June 2022

Dev Log

(newest first)

  • 8 June: I created a new pull request where I added icons for menu items and icon color for both light & dark theme.
  • 7 June: I created a new commit to remove the absolute color of hover for QToolButton. Also, I am currently testing out which color will be best suitable for icons in menu items for both light and dark themes.
  • 6 June: I created a pull request to remove border and add padding. I also added hover background-color to QToolButton
  • 5 June: Done nothing as I came back from a different state of my country where I went for to appear the exam.
  • 4 June: Done nothing as today is my entrance exam.
  • 3 June: Done nothing as I am preparing for my upcoming entrance exam.
  • 2 June: I wrongly applied $Color-IconView for QToolButton. It should be different colors for different QToolButton. I created a new commit and pushed the changes for the same.
  • 1 June: I created a pull request to remove QPushButton and add QToolButton so that the QAction objects for file, view, and ray trace can be used as one single unit. And I mentioned this pull request with an issue
  • 30 May: Discussed with mentor for what to choose between QToolButton and QPushButton. Also I got to know that QAction can be assigned to QToolButton which will be better because once object of QAction is created then we can assign it to QToolButton.
  • 29 May: Started working on the issue where I saw QAction and QPushButton have been defined for the same New and similarly I found more like that.
  • 28 May: Done nothing as I couldn't get time because I went to see my father.
  • 27 May:
    • Learnt about arbalest QMainWindow but only by far, I covered Menu bar. I found all the QAction * buttons are missing icons but code was already written to set icons for each QPushButton *. So I opened an issue. I will work on it tomorrow.
    • I also created a pull request for minor changes to main.cpp of arbalest.
    • I will cover Central Widget of arbalest which is the most important of this project because this is the area where the mouse support feature will be added. I will try to cover it from tomorrow during this community bonding period. Here an outline is taken from Qt docs of QMainWindow just for reference:
      QMainWindow Outline
  • 26 May
    • Created workspace where I built brlcad and rt-cubed. Set path for Qt 5.14.2 so that arbalest could be run to check if it is running without errors.