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

Use placeholders for cached portals #1042

Closed
wants to merge 55 commits into from

Conversation

MNoelJones
Copy link

This change does two things - firstly, use the accessor functions to get at the portal information (cached or otherwise), secondly, use default (placeholder) text for elements that haven't yet been retrieved for cached portals.

Further mods I'd like to make are to refresh the portal data as it becomes available (particularly when you select a link for an "UNCACHED" portal name, it would be nice to have it re-populate the portal list with the retrieved data)

ATXadam and others added 17 commits August 7, 2015 15:10
Simple avoidance of errors when trying to access cached portals
Moved in-progress modifications to branch
	Grammar correction (!)
modified:   code/hooks.js
  Realigned names for readability
new file:   plugins/chat-hooks.js
  Begin to add generic chat-hooks. WIP!
Fix LinkedList
Add text to chathook type hash
Fix order for adding event to list
Add test code;
Reorder handlePublicData to generate newEvent on the initial pass.
chat-hooks-test triggers on resonator deploy/destroy as well as portal
link to draw circles to a layer.
Added commented out code to chat-hooks for potential upgrade to using
sync.
@@ -67,9 +69,13 @@ window.plugin.portalslist.fields = [
title: "Level",
value: function(portal) { return portal.options.data.level; },
format: function(cell, portal, value) {
var level_text = "L?";
Copy link
Contributor

Choose a reason for hiding this comment

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

Perhaps a ternary might be neater here?

var level_text = "L" + (value ? value : "?")

Copy link
Author

Choose a reason for hiding this comment

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

How obvious :D
Will change that when I get a chance.

@mxxcon
Copy link

mxxcon commented Apr 12, 2016

It seems like this PR contains too many unrelated changes..

@MNoelJones
Copy link
Author

Hmm. Something odd's going on here; probably a misunderstanding on my part... I'll try and sort it all out and re-create the PR.

@MNoelJones MNoelJones closed this Apr 14, 2016
@mxxcon
Copy link

mxxcon commented Apr 14, 2016

You created this PR from your master. So while you were adding more commits to your repo, they were automatically imported here. What you should've done is created a separate feature branch and make a pull request from it.

@MNoelJones
Copy link
Author

Yes, I can see that, now! I had expected the pull to be taken at a particular revision.

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