-
Notifications
You must be signed in to change notification settings - Fork 109
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
Multi project extension #221
Conversation
no changes to Zaso's script.
Header, Tail wrapper () removed
Code Snippet for integrating other plugins with MPE
removed commented functions and @match
IMHO ready to merge |
Contents of |
Does IITC-CE work with Block-Comments? /* and */? |
Sample Code moved to main script DOC removed
You can use multiline comments. Yeah, like you just did. We have documentation (in the doc folder) but I don't like it very much, it should be generated based on comments in the code. |
Pay attention to my two remaining comments https://github.com/IITC-CE/ingress-intel-total-conversion/pull/221/files |
Header fixed, Indentation reduced
Thanks, this PR will be merged into a new release |
I'd rather think about include support of this in IITC core. |
Added MPE-Support for Drawtools.
To test the functionality:
|
Added MPE-Support to current Bookmarks. import to extrenals and disable standard BMRKS-plugin to test
To test: |
|
Bare with me, I am new to GIT, so it seemed to be safer to create a separate draw than to fiddle around in the original draw. At least this way does not break the existing tools and existing extensions to it. When I started porting Zaso's changes it was not clear to me how deep the changes would be. The changes can easily be followed by just renaming DRAW2-beta.user.js to draw-tools.user.js Draw2 and Bkmarks2 is "only" a Draft to show how MPE is working. Due to the same namespace both use with the old Versions, the data is completely compatible. If you find a problem with MPE it is easy to switch back to the old plugins without loosing anything. Also there are many other proposals that need to be reviewed and I think it is easier to add these to a forked plugin and finally just replace the old plugin than to daily send in new contributions. As you wrote earlier we should rather think of adding MPE to the code as "Projects" or "Project-Manager". |
Yeah, but for Better if there were (1) initial (2) changes for MPE
We can play with forked plugins, but I do not think that we should release them as they are. It'd be confusing.
Yes. It is general principle. |
Multi-Project support for Bookmarks and Draw-Tools added. (imported changes from beta)
Changes applied on original files. removed development (beta) files. |
Ok. I will review proposed changes ASAP (but do not expect it to be fast, definitely not earlier than 0.30 release). |
Some general thoughts: MPE allows to group Draws/Bookmarks by related project. I suppose we could improve project idea. |
@@ -0,0 +1,30 @@ | |||
// ==UserScript== | |||
// @id iitc-plugin-font-awesome@Zaso | |||
// @name IITC plugin: Font Awesome |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we include web font - we should include it in core, to make it available out-of-the-box.
(and it is still unclear if should include - #236)
$('<link>') | ||
.prop('type', 'text/css') | ||
.prop('rel', 'stylesheet') | ||
.prop('href', 'https://maxcdn.bootstrapcdn.com/font-awesome/4.7.0/css/font-awesome.min.css') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why use 4.7 instead of current (5.10.1)?
https://fontawesome.com/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No objection to use 5.10.1.
Just not tested it.
MPE is about replacing the complete namespace of a plugin. Sharing parts between different namespaces would require them to be in an additional namespace. |
I still don't get what do you mean. Explain please. |
You asked about sharing parts of draw or bookmarks between projects. |
What about moving this to the core? |
It is planned |
Version alinged with ZasoItems-CE
This is the first and IMHO most important plugin ZasoGD has created.
The script itself is unchanged compared to the original file.
Headers and footers are changed (not sure about the
@match
line)Zaso's startup wrapper has been commented out, although I do not yet understand why.
The script has been tested in IITC-CE - Menu item load.