| WM 3.0b7-7.1
|
- fixed icon size/placement for the sidekick-supplied app icon in the sidekick manager
- moved the sidekick worksInChrome beta-parameter to sidekick.flags.worksInChrome
- updated the sidekick tutorial script to show some of the enhanced options
- fixed (again) an issue with icon sheet segments being displayed poorly
- fixed flag/state issues on posts that caused excluded posts to be processed
- posts no longer use flags, and post.state is no longer of value
- added a few new functions to the common library and updated others
- rule.action.setColor now shows in all display modes
- marking a post failed/accepted/timeout now properly removes the collect tag
- app filter icons are now drawn with the 'crisp' drawing style as in WM2, however I am still not sure its working correctly.
- fixed issue with sidekick manager apps not staying disabled/enabled on reload
- fetching posts now remembers which feeds have already reached their older limit and does not try to fetch them again
- the Graph library now returns some status details about its last failure
- rule.action.fetchNewer and fetchOlder were backwards
- rule.actions are now all function wrapped to prevent bleeding over
- feeds manager is now like the rest of the pages and contains a lot more data and functions
- specific feeds and feed filters can now be disabled if needed, including your own home feed or profile wall
- specific feeds and feed filters can now be made to fetch posts
- fixed issue with collection page resizing to zero
- added some cosmetic improvements, mainly color, font size and layout indentation
- fixed issue with disabled manager elements not showing as disabled until refresh
- fixed issue with some manager element changes not saving
- custom dropdown elements are now locked so you cannot type in the text field
- posts now have a button to add the poster to your feed manager, which allows faster fetching of that person's posts
- rules can also add the poster to your feed manager
- fixed issue with rule moveUpLevel mangling rules
- dynamic grabber now looks like other manager pages and has been visually upgraded
- you can now convert single dynamic tests to rules from the upgraded dynamic grabber, in addition to being able to convert them all at once from the rules manager. As in beta6, conversion does not remove old grabber tests; you need to do that manually when you are sure you no longer want them.
- dropped old wm forms library and its huge css footprint, migrating to the growing JS forms library
- rule.validator.matchRegExp now uses regexp.exec instead of string.match, which will allow you to capture matched substrings as originally intended. Insertion point implementation still differs between grabber tests and 3.0's rules in that {%1} in a grabber test generally matches up to {%0} in a rule, and that rules can also capture substring matches starting with {%1} and allow you to use the registered expression non-remembering brackets. For example: /(?:color )(red|green|blue)/ could have a {%0} of 'color red' and a {%1} of 'red' because while the non-remembering brackets did cause the match (the {%0}), the substring matches do not include that portion of the expression.
- hopefully fixed issue with invisible posts on redraw and apparent cleaning of wanted posts, which was an illusion
- added a global interval that all rules can access called onHeartbeat which can be used to make rules more active and useful. The heartbeat interval time can be set in the options menu under Rules Manager>Heartbeat
fixed rule.resetLimit button and the resetLimit rule action
- dev display mode is now more like a manager page, which should allow for easier finding of data devs want, without the unintentional clicking taking you to another page
- rules and grabber tests now have import/export abilities so you can backup and share your rules and tests
- moved the post.onTimeout and onFailed events so they register better and separately from each other
- rules can now be activated by: posts, apps/sidekicks, the rule itself, feeds, and specific feed filters, as well as the global heartbeat interval
- rules can now draw data from many more sources depending on the activating object type
- the onHeartbeat event can be toggled for every rule-activating object type. Default is off for all types, so only main/console and current rule queries can be made onHeartbeat. Activate the other object types and you get more alive post and app macros, or you could even make macros for specific app post fetching.
- because of all the mayhem multiple activators on a single rule could cause, rules can now use the 'activatorType' query to limit the objects that can activate events on a rule.
- status text about already processed posts is now displayed correctly on refresh
- rule.resetAllLimits no longer asks for confirmation on EVERY rule, just once for all rules
- Posts now have a 'create rule from post' button which allows you to create a new rule based on that post. The rule manager immediately creates a new disabled rule with a few of the most likely validators already filled in. In addition, until the browser is refreshed, the rule remains linked to that post object. While linked, validators on that rule can import data from the post part(s) for which they perform validation. By default, a based-on-post rule also contains an action to set the post type to 'dynamic' which causes generic collection.
- The option to filter images in classic mode had spilled over into short mode, making posts unclickable. I have changed it so that you can choose to not load online images for posts in short mode, however a placeholder icon will still exist so you can see stuff in short mode.
- Option menu branches now show a new item count in the header. New items are marked by sidekick devs, so they only represent what is correctly marked. Newitem counts are determined by the newitem flag on each config field. Items colored or marked by different methods are not counted.
- Rules can now use the {%appID} insertion point in 3-parameter actions. Because bonus types (a post's 'which' value) are prefixed by that app's ID, this will make using predefined bonus types easier. For example, a Pioneer Trail horse has a 'which' of "266989143414horse", not just "horse", so if you have a need to use the setWhich rule action, you can then supply "{%appID}horse" in the 3rd parameter and get the expected result.
- Rules can now attempt to comment on a post. Instead of using the predefined auto-comments, rules use a third parameter where the user supplies a single specific comment. !! This is not working !!
- You can now sort the collection window by more fields
- You can now group the collection window posts by the same fields you could use for sorting. Groups are collapsible, which will persist across display mode changes.
- Fixed an issue with rules that were disabled still affecting objects
Users can now create user defined bonus types in the sidekick manager. Each type simply needs an ID and a Name, like "horse":"A Horse". These user defined types can be accessed anywhere bonus types are used, including grabber tests and rules. You can even overwrite pre-existing bonus types to give them a new name, modify the text to suit your language, or make other adjustments. One note: if you do not want dropdown lists to prefix your text with 'get' or 'send', add a '*' to the front of your type text (not your type id).
- Anywhere bonus type dropdowns are found, the list is now sorted in order of base text. For example, the base text of both 'sendhorse' and 'horse' happens to be 'Horse', so in the dropdown list, Get Horse and Send Horse will appear next to each other. Special types that begin with a '*' will be on top. Anomalous entries, such as those that start with a space, will appear before special entries.
- Cleaned up classic display mode so that smaller screens or zoomed-in or shrunken browsers don't have such ugly layouts.
- Fixed some minor bugs with redrawing posts: posts recompile visual parts on re-id. posts properly position themselves hopefully every time they redraw.
- In classic display mode, you can now show posts in up to 4 columns.
- Added initial stuff to the Sidekick object in the common library which allows sidekicks to supply a skType parameter. Default is 0, which tells WM that the sidekick is to be the main sidekick for that app. Consider this parameter a parking spot number. Any sidekick that has a skType of 1 takes spot 1, 2 takes 2 and so on. You can only have one sidekick per parking spot. I leave it up to secondary sidekick devs to furnish a unique number for their script. If you want your sidekick to dock no matter what, I suggest passing the current timeStamp() as the skType. Future versions may have internal functions for certain number ranges. For instance, type 0 loads all of a sidekick's abilities, where other types do not need all their parts.
- Expermental parts now exist for an auto-comment feature. In addition, you must now specifically enable auto-like and auto-comment separately with new checkboxes. See your options menu under Host Options > Feedback. As with auto-like, be very careful auto-commenting at high speed. I suspect the possibility of getting comment-blocked is much higher than getting like-banned. I suggest that you use multiple messages in the provided comment box. The more variation, the less bot-like you look. I also ask that you do not advertise the wall manager via your comments. I really don't want people hating WM before they even know what it is. !!Currently auto-comment is NOT working due to fb doing their damnedest to prevent such. !!
- Fixed autolike again!
beta7.1: added linkText and linkHref into the post parts dropdown so if it was unclear what 'link' meant before, you can start using these new disambiguated queries.
|