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

Refactor of qgis2leaf_exec #29

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Refactor of qgis2leaf_exec #29

wants to merge 1 commit into from

Conversation

NathanW2
Copy link

This request does a major refactor on the qgis2leaf_exec method. Changes are as follows.

  • Break method into functions for each part.
  • Only open the index file once
  • Write files at end only
  • Use templates rather then string concat
  • Only loop the layers once. Filter vector layers at the start.

Note: This is not mergeable yet or fully working. Needs some more testing but more to show you what has been done so far.

- Break method into functions for each part.
- Only open the index file once
- Write files at end only
- Use templates rather then string concat
- Only loop the layers once. Filter vector layers at the start.
@riccardoklinger
Copy link
Contributor

Hi Nathan . Thank you for this major update. As I am new in handling merges and github: what needs to be done next? Shall i embed your given guideline in a new major release by copying manually?

Thanks for your guidance. Best regards, Riccardo

@NathanW2
Copy link
Author

Don't do anything yet. I will get it into a state where you can just press merge here on github and it will bring everything in for you.

@riccardoklinger
Copy link
Contributor

That sounds cool! In my last commit I added some more base layers, and some minor changes in the UI. But I'll take care of those changes!

@riccardoklinger
Copy link
Contributor

@NathanW2 Can I go on with development for other issues or is it better to wait for your pull request?!

@NathanW2
Copy link
Author

Go on. I will bring yours into my changes when I have some time. Should be
in a day or so.

On Wed, Apr 30, 2014 at 5:49 PM, Riccardo Klinger
notifications@git.luolix.topwrote:

Can I go on with development for other issues or is it better to wait for
your pull request?!


Reply to this email directly or view it on GitHubhttps://github.com//pull/29#issuecomment-41769391
.

@tomchadwin
Copy link
Contributor

Did this ever get committed/merged? I am working off current master, but guess it will be fundamentally changing once this is merged.

@NathanW2
Copy link
Author

No I never got time to come back to it and don't have a lot of time now.
On Jun 18, 2014 9:13 PM, "tomchadwin" notifications@github.com wrote:

Did this ever get committed/merged? I am working off current master, but
guess it will be fundamentally changing once this is merged.


Reply to this email directly or view it on GitHub
#29 (comment).

@tomchadwin
Copy link
Contributor

@NathanW2 I'd like to try to improve the current code's string handling, as per this PR. As a Python beginner, can I ask one question?

What is the difference between:

"A string with a {name}".format(name = var_name)

and:

Template("A string with a {name}").substitute(name = var_name)

In other words, what does the Template substitute() method offer over and above the simple string format() method?

@Kessir
Copy link

Kessir commented Jun 23, 2015

Hi Everyone. Is this ever going to be merged?

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

Successfully merging this pull request may close these issues.

4 participants