Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Roadmap for the next versions #175

Open
dpizetta opened this issue May 25, 2019 · 11 comments
Open

Roadmap for the next versions #175

dpizetta opened this issue May 25, 2019 · 11 comments
Assignees
Labels

Comments

@dpizetta
Copy link
Collaborator

Hi guys @ColinDuquesnoy @ccordoba12 @goanpeca. I'm thinking about changing the roadmap a bit as we have changed some points after the contributions from Spyder team started. Also, the v2.7 is getting bigger :)

Word establishments (I'll point this in the docs also):

  • User: the user who will not change the style, but it still be a developer - of his/her software.
  • Developer: the user who will change the style using our developer options.

Thus, we can remark this:

  • v2.7 try to reduce the number of issues important for the user, removing developer ones, thus the users can use the fixed things up to now;

  • v2.8 use only QtPy abstraction + HelpDev for checks, so we can reduce the code, many imports and try's that checks the binding before insert ideas of PR Add pyqt5 support to load_stylesheet() #135. Also we can reduce the number of compiled things - see the case of 'example' in dev version v3.0. However, we keep the same calls!

  • v2.9 insert those skipped issues to this version - more developer changes, change the call slightly as mentioned in PR Add pyqt5 support to load_stylesheet() #135;

  • v3.0 change in the API to use only one call setting the binding using QtPy abstraction.

Also, we can match with the Spyder roadmap to reach its needs for v4.0. If everyone agrees I can create the milestones and distribute the issues. Thank you all

@goanpeca
Copy link
Collaborator

This sounds like a solid plan lets try to commit to it :-)

@marcelomanzo
Copy link

this sounds like a good plan, thanks a lot guys.

@dpizetta dpizetta changed the title Road map for the next versions Roadmap for the next versions May 29, 2019
@dpizetta
Copy link
Collaborator Author

I will apply those milestones :)

@dpizetta dpizetta self-assigned this May 29, 2019
@dpizetta
Copy link
Collaborator Author

dpizetta commented Jun 1, 2019

@goanpeca could you take a look in behavior of the latest version on spyder? I think that is ok about the buttons. So, we can create a new release for v2.7 if it is ok :) Tks

@goanpeca
Copy link
Collaborator

goanpeca commented Jun 1, 2019

Yes i can, doing it now

@goanpeca
Copy link
Collaborator

goanpeca commented Jun 1, 2019

Screen Shot 2019-06-01 at 17 18 11

@dpizetta things are looking good :-p

Only the close in the tabs is a bit too small, but maybe we are adding a custom CSS and that is why

Screen Shot 2019-06-01 at 17 19 05

Also the toolbar buttons inside the dockwidgets are cropped, but it seems to be a MAC thing only (also maybe we add a custom CSS need to check)

Screen Shot 2019-06-01 at 17 19 11

Thanks for working on this :-)

@dpizetta
Copy link
Collaborator Author

dpizetta commented Jun 2, 2019

@goanpeca Tks! Updating to master branch both qdarkstyle and spyder, reseting everything I get this:
I only see some croped parts, but depends on the dock I already reported in spyder tracker.

master-spyder-master-qdarkstyle

I recommend you to test those issues with your example to see if it is from spyder or from mac.

I will create a release for this version, so other people can use from pypi.

@dpizetta
Copy link
Collaborator Author

dpizetta commented Jun 3, 2019

Hi @goanpeca, just to let you know and to keep the repo more organized, I created a new branch "develop" for the latest development. The branch "dev" I will merge with the develop" and then kill it : 0. So we keep the master only for stable versions. Tags will be pushed to master also. We can create temp branches for release too, following gitflow. Suggestions?

@goanpeca
Copy link
Collaborator

goanpeca commented Jun 3, 2019

Sounds good to me :-)

@dpizetta
Copy link
Collaborator Author

@goanpeca I think we are close to releasing v2.8. Most of the bugs were closed and I'm working on the #160.
Could you check mainly the proposed solutions for #188, #184, #183, #174, and discussion of #135. And take care of #169, #191.
Tks

@goanpeca
Copy link
Collaborator

Will do @dpizetta

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants