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

Redo feed builder fix #99

Open
wants to merge 21 commits into
base: master
Choose a base branch
from
Open

Conversation

vbjay
Copy link

@vbjay vbjay commented May 26, 2017

  • upgrade framework version for feedbuilder
  • make feedbuilder responsive
  • load icons from os
  • get human readable file sizes
  • select listview items by typing regex pattern
  • functionality and ui improvements
    Feed builder rework because of of merge conflicts.

@vbjay vbjay force-pushed the RedoFeedBuilderFix branch from 1d25f2f to fe45e60 Compare May 28, 2017 17:20
@vbjay vbjay force-pushed the RedoFeedBuilderFix branch 2 times, most recently from a080ce6 to e9e54ae Compare May 30, 2017 21:51
@vbjay vbjay force-pushed the RedoFeedBuilderFix branch from e9e54ae to eb2e89d Compare May 31, 2017 01:54
@vbjay vbjay force-pushed the RedoFeedBuilderFix branch from eb2e89d to 466a908 Compare May 31, 2017 05:17
@vbjay vbjay changed the title Redo feed builder fix NOT READY Redo feed builder fix May 31, 2017
@vbjay
Copy link
Author

vbjay commented May 31, 2017

Ready to merge

@robinwassen
Copy link
Collaborator

Hi @vbjay!

I appreciate the changes you have done, but it seems like you managed to revert some of the later fixes to the project.

For example:

  • Removing FileLockWait(); in FileUpdateTask.cs and adding the commented wait logic
  • Removing FileSystem.CopyAccessControl(...) in FileUpdateTask.cs

I will go through the changes and see how we can perform the merge gracefully.

@robinwassen robinwassen self-requested a review May 31, 2017 07:18
@robinwassen robinwassen self-assigned this May 31, 2017
@vbjay
Copy link
Author

vbjay commented May 31, 2017 via email

@vbjay
Copy link
Author

vbjay commented Jun 1, 2017

Let me know if there is anything else.

@vbjay
Copy link
Author

vbjay commented Jun 6, 2017

I understand other things taking your time. I had to redo this work because it was ignored the first time. Am i wasting my time with trying to give back to this project?

@robinwassen
Copy link
Collaborator

Hi @vbjay,

It is my ambition to merge this - but it will take some time since I am usually very thorough when reviewing changes and want to understand each line that is changed to determine the impact of the change.

Which makes it take some time when the change is on 2500 LOC.

Regards,
Robin

@robinwassen
Copy link
Collaborator

I have reviewed each commit up to d2a4fc9 this far.

@@ -81,18 +83,9 @@ private void frmMain_Load(Object sender, EventArgs e)
if (!_argParser.ShowGui) Close();
}

private void InitializeFormSettings()
private async Task InitializeFormSettings()
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Marking the method as async does not make it run async per default.

All places that calls InitializeFormSettings() also need to be changed.

Example:

public class AsyncTestClass
{
	// Output:
	// Initialize() done
	// Run() done
	public void Run()
	{
		Initialize();
		Console.WriteLine("Run() done");
	}

	// Output:
	// Run() done
	// Initialize() done
	public void RunAsync()
	{
		Task.Run(Initialize);
		Console.WriteLine("Run() done");
	}


	private async Task Initialize()
	{
		Thread.Sleep(2000);
		Console.WriteLine("Initialize() done");
	}
}

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see that InitializeFormSettings() is called with the await keyword in a later commit, don't understand why it is made async if it is only called sync

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll look again. I knew it was sync in the load of the program. But notice it's different when you load a file. I knew that in load we want it to be sync.

@robinwassen
Copy link
Collaborator

@vbjay Do not worry about the conflict.

Some questions I have:

  • What is the reason that you upgraded to .NET 4.6.2?
  • What is the purpose of including the RX .NET package?

@vbjay
Copy link
Author

vbjay commented Jun 7, 2017

Look at the next commit for why I added Rx.

I upgraded to 4.62 because I wanted framework 4.0 stuff. It also runs on windows 7sp1 and higher. Windows XP support should not be a factor. Microsoft dumped their support for xp in 2014. We should too. O

@robinwassen
Copy link
Collaborator

robinwassen commented Jun 7, 2017

@vbjay Sorry, my mistake about the upgrade. Thought it was from 4.5 -> 4.6.2 which left me puzzling, but 3.5 -> 4.x makes more sense!

Thanks! Everything is a bit more clear now, so I can keep on working with the review and merge.

This was referenced Jun 7, 2017
@robinwassen
Copy link
Collaborator

Most of the refactors and smaller changes has been merged now.

I noticed some more collateral damage in the commits, so I am going through commit per commit and cherry-pick them to the branch feedbuilder-improvements and review all changes in detail.

One comparision is the original commit: af11eac?w=1

My modified: 641e4f2?w=1

This can take a while, but I will get through it :)

@vbjay
Copy link
Author

vbjay commented Jun 8, 2017

@robinwassen I appreciate the work you are doing. It means a lot.

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

Successfully merging this pull request may close these issues.

2 participants