wasabee-project/wasabee-iitc

ENL DrawTools and Op Management

wasabee-iitc's Issues

Remove denormalizations in the JSON

We added some places in the JSON where both GoogleID and IngressName is passed (markers, links). This is dumb. Pass just the GoogleID, resolve in the code. Functions exist for this. Use them.

Once this is complete in both the app and IITC plugin, remove from server.

marker.completedBy is the ugliest, passes name but no GoogleID, will require a coordinated change.

Bulk assign Outbound links....

When assigning outbound links via the Portal Marker on draws, its assigning that marker to All links.. be it Inbound or Outbound.

Slight reformatting of Button Layout

The Quick Draw Mouseover should be called Fielding Options. The side menu being Quick Draw (Current functionality), MultiMax, Fanfield, and the other fielding Types.

Add Links would become a standalone option for now (unless there's other types of links someone could think of....)

Railroad Flip Flop Fan Field

In Fielding:
Railroaded Flip Flop Fans
Same as Above, BUT

• Anchor1 - Where the FIRST Fan is thrown From,
• Anchor2 - Same
• Anchor3 - Same
• S1 = Anchor1, s2-s10 - These are the Spine portals. Where you can Flip the previous one and throw from this portal with NO crossed links.

Mechanics are the same as Flip Flop, but has to check if throwing from each of the spines would put that portal in a different "cell" of the fields. (This results in some portals that will NOT be used, but could throw for all But one of the S anchors.

Throw order would be same as Flip Flop fan fields, but after Anchor1 is complete, VIRUS Anchor1, and throw same as Anchor 1 at S2-S10.

Translation: Dialog box buttons for OK and Cancel

I think they should also have translations

Why does checkAllLinks() add itself on layer add?

Seems like we should only call window.map.on("layeradd"...) once, not every time the function is called.

Add Links Dialog: Translation texts

"from" and "to" translation
Buttons should have translations for this dialog

mobile friendly UI (small dialogs, short buttons)

which ones?

Ops Dialog: Translation Text

"Operation Name: " should have translation
"Operation Color: " should have translation
I'm contemplating if colors should have translated text as well
"Clear blah blah" button should have translation
"Duplicate Operation" button should have translation

Audit UI for things which should not be shown if not logged in

"assign all outbound links" on anchor marker should not be visible if not logged in.

find all such things and wrap in if (WasabeeMe.isLoggedIn()) { ... }

Provide an indication when links in the op cross other links in the op

It would be a nice feature to see if you have unintentionally created crossing links.

trawl lanes

trawl lanes looking for blockers (load tiles under drawn items)

Audit event propagation

Liberally sprinkle

.on(a, "click", L.DomEvent.preventDefault)
.on(a, "click", L.DomEvent.stopPropagation)

to L.DomEvent. calls.

agent/marker popups need styling

css is bad

Cobweb Fields

Fielding >> Cobweb
https://www.youtube.com/watch?v=yvvrHEtkxGc

• Anchor1 outside
• Anchor2 outside
• Anchor3 outside

Looks at and figures for all portals Inside them.

Possibly with being able to go to each anchor area(save the portal GUID and location) and figure for larger areas in that fashion.

Generalize per-language images

make it so that every language can have its own icons/etc, not just the SECONDARY_LANGUAGE...

0.18

Remove qBin sharing - fix export/import

People will need to share ops without using the server, so make sure export/import works.

The legacy qbin (simple share/sharing links) can go away though.

Wasabee plugin does not work on IITC

The Wasabee plugin v.0.13.0 don't works or don't show the panels on IITC CE v0.29.1.20190315.122355.

assign task to multiple agents

requires a lot of work, including in the mobile app

Add Marker Dialog: Translation texts

Destroy and Marker should have translated text
Add Marker button should have translated text

capsule hand-off

track key movement from agent to agent

Audit context passing and replace with ....call(this) style.

Learn something new, undo bad ways of doing stuff.

Team dialogs cleanup

Get non-team stuff out of the team menu
"send location" can go to settings
"about" needs a home, but I don't know where.

need the ability to create a team join link in IITC.

assign src/dest portals to link task

seems redundant with drawn links but ok

Add Links Dialog

For each item (From, Set1, Set2), add a Clear which clears just that single portal.

Could also add a Clear All at the bottom as well which clears all in this menu.

Support Touch events, not just faked "click"

For this to be truly mobile friendly, we have to rework some of the UI to use touch events.

Key List Formatting

It would be nice to see variation in the Key List box if you are Short, correct, or Long in the keys on hand (Assuming they're already put in)

i.e If I have 5 keys and Need 6 for a draw, the background of On Hand could go pale yellow. If there's 0 on hand, it goes Red to indicate None available(right now). If I change around the draw(swap links , etc... )and the above mentioned needing 6 ends up dropping to 5 or below, the background (or entire row) could go Green to easially show Keys are available.

Course when Assigning, a New Column could be added to indicate they're "In the right place" or with the thrower.

Cross Draw detection...

Can there be an alert(popup or else) to alert the user when drawing layers( Non Max or Fan fields) when one drawn layer would "block" another drawn layer. Similar to Cross-link detection, but instead for Live links, be for the Drawn links.

This could even be in the "Blockers Dialog" but would be exempt of the automark box.

Time between agent and target

implement in server, add IITC calls

Feature Request: Watch portal marker type

Any portals marked with this marker would be added to a list dialog showing
last activity
name
level
mods
charge level
link level (?)

Future plans for storing/sharing historical data if possible.

Need a set of marker icons (cw?)

requested by AxForest

draw tools style drawing

click one portal, click next portal, click next portal... don't auto-draw layers or anything, just links.

Login Dialog: Texts

Settings spelled incorrectly
Immediate - "i" must be Capitalized

Split languages into individual JSON files

Crystalwizard (ENL L16 AZ), [06.04.20 15:23]
I have a concern btw - each language has so many keys that translations.json is going to get huge, fast. should we be thinking about multiple translations files?

deviousness (Scot 🐢 D/FW Ԙ13), [06.04.20 15:24]
Yes.

Crystalwizard (ENL L16 AZ), [06.04.20 15:24]
okay so how about this, then - a directory called translations and each language in its own json file

deviousness (Scot 🐢 D/FW Ԙ13), [06.04.20 15:24]
exactly.

deviousness (Scot 🐢 D/FW Ԙ13), [06.04.20 15:24]
import them in static.js

Crystalwizard (ENL L16 AZ), [06.04.20 15:25]
okay. I'll start working on changing that structure

deviousness (Scot 🐢 D/FW Ԙ13), [06.04.20 15:25]
thanks!

Crystalwizard (ENL L16 AZ), [06.04.20 15:25]
sure :)

deviousness (Scot 🐢 D/FW Ԙ13), [06.04.20 15:25]
we can probably do an "english only" build for those who want to save space, and a "all the languages" build for everyone else.

Crystalwizard (ENL L16 AZ), [06.04.20 15:26]
that would be cool, too

Wasabee plugin does not work if it is loaded prior to IITC

To reproduce: In Tampermonkey, move Wasabee to the top of the load list and refresh.

Expected behavior: Wasabee plugin should still work and be loaded by IITC when it finally loads.

Actual behavior:
Uncaught TypeError: Cannot read property 'extend' of undefined
at eval (webpack:///./src/code/leafletDrawImports.js?:6)
at Module../src/code/leafletDrawImports.js (:1178:3)
at webpack_require (:808:32)
at eval (webpack:///./src/code/quickDrawLayers.js?:3)
at Module../src/code/quickDrawLayers.js (:1310:3)
at webpack_require (:808:32)
at eval (webpack:///./src/code/addButtons.js?:6)
at Module../src/code/addButtons.js (:1094:3)
at webpack_require (:808:32)
at eval (webpack:///./src/code/init.js?:9)

Notes: Do not try to use any Leaflet features until the setup() function is called, to guarantee they do actually exist.

Import Wasabee Draw Dialog: Texts

"Get Existing blah..." - suggested "Get drawn DrawTools" or "Get current DrawTools Drawing"

Export Dialog: Translations

"Select all and ..." should have translation

Prevent duplicate markers from being assigned to the same portal

There is a need to be able to put multiple markers of different types on a portal, but wasabee should not allow 2 markers of the same type to be assigned to the same portal. Right now there is no limit to the number of duplicate markers that can be assigned (5 destroy, 7 capture, etc)

Open lanes from agent to wasabee-d keys

agent -> their blocker-keys links on a new layer, checking crosslinks w/ both drawn and real (can I block from here?)

Wasabee-D - list my recorded keys

just a dialog

Track cross-links

save cross-links in the JSON format, store in database, so zoom level doesn't impact op planning... something like TRACE in Arc.

tweaking the code for flyout buttons on mobile devices

adjusting the base code for size and text, then adding additional code to deal differently with iOs than android.

Add all portals to Key Lists

Reason to do this is if an agent is able to load keys they're throwing From and you are short on one end, but long on the other, the link Direction could be swapped to change the key need.

This could Also be used as an ADHOC "Rechargers" List for people to alert when the portal comes under attack(If able to at the time of course)

Display Portal Comment/Hardness values

somewhere, somehow.... probably the popup?

assign task to squad

requires assign task to multiple agents

remove overflow menu

remove it with fire

Flip Flop Fan Fields

In Fielding:
Flip Flop Fan Fields.

• Max Links - 8,24,40 (Dropdown for the values) If 24, then "Requires 2 SBUL". If 40, then "Requires 2 agents and 2 SBUL each"
• Anchor1 - Where everything throws FROM
• Anchor2 - Base Link to Anchor3
• Anchor3 - Base Link from Anchor2

*Mechanics:

1. ONLY Portals inside all three anchors are checked.
2. Base link from Anchor2 to Anchor3. <<LIST: Flip_List>> Adds each portal to the list for the Anchor1 Throw order
3. Closest portal to the Base link on the Anchor1 Side, throws to Anchor2 and 3. <<LIST: Flip_List>>
4. On each of the just created links, the closest portal is selected and thrown to the Previous and second previous(or outside) Link.
5. Repeat 3 and 4 until Either 24 or 40 Total portals are worked through.
6. Goto Anchor1, and throw Outbound To the portals in the order as shown on the <<LIST: Flip_List>>.

Ability to have different Icon/UI packs hosted outside the main build

I still don't know why we need to embed the icons in the javascript at all, but we should allow hosting images on the servers so we don't need to keep them tiny to keep the script small.

Homogeneous Fielding ops

In Fielding, new option of Homogeneous Field.

Homogeneous Fielding Ops.

• Anchor1
• Anchor 2
• Anchor 3

considers ONLY the portals INSIDE

*Mechanics:
Counts all portals
splits them into 3 equal groups
Draws 2nd layer to those groups
Splits each group in 3, and draws a layer inside each area.

Continues to a MAX of 6 Layers, OR until there is a inner field that does NOT have a portal inside it. If not 6, then it message pops up " Only 5 Homogeneous layers available here."
As Reference:
https://www.youtube.com/watch?v=0xoQsG3-vLA on Homogeneous fielding Ops.

Marker Colors are bad

We've not used the marker colors until now. They are bad and need work.

defined in static.js

visible in marker popups.

Metadata Block

I have some suggestions about metadata improvements

// ==UserScript==
// @id           wasabee
// @name         IITC Plugin: Wasabee Draw Tools
// @namespace    http://tampermonkey.net/
// @version      0.13.1-deviousness
// @updateURL    http://server.wasabee.rocks/static/dev/wasabee.meta.js
// @downloadURL  http://server.wasabee.rocks/static/dev/wasabee.user.js
// @description  Wasabee is not for dating. Period.
// @category     Draw
// @author       Wasabee
// @include      https://*.ingress.com/*
// @include      http://*.ingress.com/*
// @match        https://*.ingress.com/*
// @match        http://*.ingress.com/*
// @include      https://*.ingress.com/mission/*
// @include      http://*.ingress.com/mission/*
// @match        https://*.ingress.com/mission/*
// @match        http://*.ingress.com/mission/*
// @grant        none
// ==/UserScript==

Docs are here: https://wiki.greasespot.net/Metadata_Block
What is important:

• @id is not standard property.
  And it's not about 'uniqueness'. In fact it should correspond to filename.
• @name now begins with IITC Plugin: , it's rather convention, but most of scripts have 'plugin' in low case (IITC plugin: Wasabee Draw Tools)
• @namespace is important for updating, together with @name they define uniqueness of plugin.
  It can be any string, but better pick some domain under your control.
  Definitely not http://tampermonkey.net/
• @updateURL, @downloadURL - must have https, otherwise updating will not work.
• @include and @match are synonyms.
  Currently single definition is enough
  for all cases: // @include https://intel.ingress.com/*
  Or @match, that would be equal in our case.