![]() ![]() > Thank you very much, tumpio! I've just sent Tab Mix Plus dev a PM and he > I've created my own experiment API for Toolbars. show(toolbarId) - set toolbar visibility to visible. ![]() hide(toolbarId) - set toolbar visibility to hidden. move(toolbarId, moveProperties) - Move toolbar to the position given in moveProperties. getAll() - Get all Toolbars in browser Window. ![]() get(toolbarId) - Get Toolbar (defined below) by toolbar element ID. I haven't yet created any documentation that was requested in the dev-addons mailing list but the api.js implementation is documented extensively. This allows me to convert partially my Toolbar Position Changer to WebExtension. It fulfils two requirements for toolbar based add-ons to be able to control the visibility and the position of toolbars. I've created my own experiment API for Toolbars. * Re-styles one of the existing toolbars, like changes toolbar icon sizes or toolbar height.Īre there any API design decisions made? How great will be the support for the existing toolbar based add-ons? * Adds a vertical side bar panel, like all-in-one sidebar and tab tree add-ons. * Adds multi-row toolbar support for one of the existing toolbars. * Adds toolbar ordering support for all of the existing toolbars. ![]() * Adds toolbar auto-hiding support for one of the existing toolbars. * Adds new toolbar items and content, like Toolbar Buttons add-on. * Enhances and modifies the existing browser toolbars, like Bookmarks and navigation toolbar enhancement add-ons. * Adds a vertical toolbar, like the Vertical Toolbar add-on. * Adds a bottom toolbar, like Status toolbar, Downloads toolbar and Vim like toolbar add-ons. * Creates a new custom toolbar, like search toolbar and additional developer toolbar add-ons. Hello, Firefox should keep supporting the existing Toolbar based add-ons. a predefined set of HTML elements or HTML classes like `ui-toolbar`, `ui-toolbar-button`, `ui-menu`, `ui-menu-item` that could be used in WE-based extensions to compose toolbars consistently using HTML. a predefined set of addon-manifest entries for describing toolbar items and their menus (+ JS API to handle those) ģ. a JS API for creating/removing toolbar items and assigning _standard_ high-level (native-looking, not free-HTML-based) menus to toolbar buttons Ģ. Some of possible ways for that as for toolbars:ġ. There should be a sort of standardized (Firefox-UI-wise) way to create consistent native-looking basic UI. And that's not just about toolbars, that's a general issue of WebExtensions API in its current state. Having a flexibility of creating a free-form custom UI is good in general, but that should be an _option_ when that's _required_ for specific-addon purposes, _not_ the _only_ way to go. in addon options) is harmful and just makes the entire browser UI _inconsistent_ and hurts usability. I believe the “any custom UI is HTML” approach (that we are unfortunately already forced to use e.g. > A toolbar should (in my opinion) just be a HTML and JS page If you still are unable to populate a schedule for the employee, please call the ActiveStaffer office at 91 or send an email to the API Resource Group.(In reply to Andy McKay from comment #6) In other words, you should have either core schedules, schedule preferences or both in the system for your employees. If you did not enter any core schedules nor schedule preferences, this employee will not populate the schedule unless you run the open schedules without preferences scheduling pass. Were there any needs for the activity codes that employee prefers? If not, the system won't schedule them. You can also prioritize the preferences using the up and down arrows on the Schedule Preferences screen. Did you give this person a core/track schedule? If so, did that correctly populate? Did you also give them preferences? Remember, in the employee record you have to put the preferences as check marks on the rotating schedule AND list the activity codes they prefer to work under Schedule Preferences. If that doesn't provide any hints, look at your rotating schedule with preferences. For instance, they could have an expired license or already be scheduled at their approved hours. If so, the error message will clue you in to why they did not receive that schedule. First, try to type in the schedule you think they should have received and see if you get any error messages. ![]()
0 Comments
Leave a Reply. |