Jump to content
tpr

AdminOnSteroids

Recommended Posts

Hey @tpr - you have been busy while I have been away :) I haven't played with it yet, but it looks awesome - do you feel like another feature request?

https://processwire.com/talk/topic/13041-pw-3015-new-quick-tree-debug-view-panels-and-more/?p=118514

Not sure how easy this would be to do in your module, but thought I'd throw it out there!

Share this post


Link to post
Share on other sites

I hope Ryan plans to add such features to the panels you requested. I guess some features could be implemented easily, like auto width, position next to content, etc. I'll see.

  • Like 2

Share this post


Link to post
Share on other sites

Ever got lost in asm field(set) hell? This might help:

post-3156-0-46179900-1465626292_thumb.gi

  • Like 6

Share this post


Link to post
Share on other sites

Just uploaded v019 with the collapsable asmSelect fields update. The screenshot in the previous post was updated because there's always an icon in the beginning of the row to make the hierarchy easier to see (there was only a "+" icon beforehands). Double-clicking on the ending item also collapses the section.

The update does not contain the ctrl+s CKEditor feature, I need to think it through how to organize.

  • Like 2

Share this post


Link to post
Share on other sites

hey tpr,

one thing that i find annoying some times is that multi-column-fields are stacked on mobile but also set to have the same height. on desktop that makes sense so that it is a proper grid, but on mobile the fields are stacked to 1 column and therefore it would be great if every field had only the height itself needs.

but maybe that should be more a fix of the core than an "enhancement" via your module. what do you think?

Share this post


Link to post
Share on other sites

I think the admin is meant to be used on desktop but I'll see if there's an easy fix to this, maybe setting height: auto or similar is enough. Could you show an example scenario where this happens? (what field to add with what settings)

Edit: try adding this to AdminOnSteroids.css and see if it helps:

.maxColHeightSpacer {
    display: none;
}
  • Like 1

Share this post


Link to post
Share on other sites
@media screen and (max-width: 767px) {
  .maxColHeightSpacer {
    display: none;
  }
}

that fixes the problem on the standard theme

what do you think? i think this should be fixed in the core.

Share this post


Link to post
Share on other sites

Seems OK to me - google shows that this was already on the table in PW forums:

https://processwire.com/talk/topic/10802-issues-with-javascript-setheight-function-in-pw-admin/

AOS v02 is just uploaded, with some AsmTweaks fixes and a feature to move the delete button to the left on Asm fields. I use a wide screen monitor and this bugged me a lot :)

  • Like 1

Share this post


Link to post
Share on other sites

Great addon! Have been using it and I like how it tweaks the admin. 

This feels like when I found out about HelperFieldLinks. Maybe one day all of this will go into "power user mode" module.

Share this post


Link to post
Share on other sites

Thanks! Glad to hear that. I also use it on my sites and it speeds up navigation and feels better, but of course that can be because it's tailored to my likings.

What submodules are you using?

I've also thought about adding edit links to fields/templates like HelperFieldLinks do, but without the info popup.

v021 is uploaded to GitHub:

  • sticky admin tabs when compact sticky header is enabled
  • stickyCKEditorToolbar fix for multilanguage fields
  • module submitted to modules directory
  • CSS fixes

The tabs are sticked to the header so when the site is scrolled down they are still visible, no need to scroll up.

aos-stickytabs.png

  • Like 2

Share this post


Link to post
Share on other sites

Another commit today containing the new Hotkeys submodule. This enables saving page on ctrl+s, even from within CKEditor. What's more, it works on various page types, eg. when editing templates, fields, roles, etc. As there was no general rule I could apply to save pages, I had to manually add the enabled ones, so if you find a page type which doesn't work but should, please report.

If enabled, the submodule will disable the default browser Save dialog on all admin pages. I think that dialog has no function in the admin but correct me if I'm wrong.

On save there's a white overlay with a fancy css3 animated floppy icon, to  indicate something's happening:

aos-save.gif

  • Like 7

Share this post


Link to post
Share on other sites

Updated to v025, here are the latest changes:

0.2.5 (2016-06-28)

  • new RenoTweak: miniScrollbar for main content and sidebar (using perfect-scrollbar.js)
  • added Language Translator page to the supported hotkey save pages

0.2.4 (2016-06-26)

  • remove ctrl+click feature to activate all language tabs of the same language (core feature from ProcessWire 3.023)
  • FireFox fix for clearing filterbox

miniScrollbar in action:

aos-customScrollbar.gif

  • Like 5

Share this post


Link to post
Share on other sites

@bernhard Just noticed that before you wrote, glad it's fixed.

AOS v026 is uploaded with two tiny update: allow ctrl+s on the first step of Add new page + adding sequential tabindices to inputs (textareas, selects). The latter solves the issue that often TABbing doesn't jump to the next input because there are other inputs in between. This solution isn't perfect but it's very simple, and it would do in most cases. Also works with ajax-loaded fields/tabs.

  • Like 1

Share this post


Link to post
Share on other sites

Great module tpr. Some really great features.

I just had an idea and wasn't sure if a module or feature request existed already? or wether it should belong here or in the core?

I like the minimalistic and ease of use by Processwire and mods your module offers and was thinking would be great to have an option to hide all notes for all fields, or the option to have these converted to an icon near the field title (such as a question mark icon), for fields which have them, and on hover to then show any notes set to the field. 

I think this would save a lot of screen real estate as users who are more frequent with the use of the CMS, tend to not require to see the notes after a while.

Not sure how hard this would be though? :)

Anyway, thanks for the great module!

  • Like 1

Share this post


Link to post
Share on other sites

I only occassionally use description and notes but I agree that it could save some space.

@bernhard I saw that topic earlier, thanks. At first I'll see if I can do it CSS only, that would be more lightweight and unobtrusive. Here is a quick demo of the first mockup (written in dev tools):

aos-css-tooltip.gif

Update: the double coffee worked :)

aos-css-tooltip-1.gif

aos-css-tooltip-2.gif

  • Like 5

Share this post


Link to post
Share on other sites

Just added two screencaps to the post above. On the last one the tooltip occupies the whole field area, I'm curious what do you think about that. It's better in dev POV because there are no z-index issues (in some cases the tooltip got cut by other elements). Or the tooltip could go to the right of the icon, with its arrow pointing leftwards.

  • Like 1

Share this post


Link to post
Share on other sites

Wow. What kind of coffee you drinking?! I didn't expect something so soon. :)

I like the last one too. Looks good!

  • Like 1

Share this post


Link to post
Share on other sites
31 minutes ago, grimezy said:

Wow. What kind of coffee you drinking?!

corporate :)

Here is the basic tooltip-version that have notes and description fields. On double-click the tooltip stays visible, to enable copying text. There is a hack to tackle IE and if the content has html, that's also covered.

aos-css-tooltip-3.gif

  • Like 5

Share this post


Link to post
Share on other sites

Well done.  

I was going to suggest something previously, such as a click to keep things visible for copying, but didn't want to push my luck!!

  • Like 1

Share this post


Link to post
Share on other sites

v027 is up with the Tooltips submodule. The CSS got a bit complicated but hopefully everything will be fine forever so I don't have to dive into it again :)

You can switch whether to use it for field descriptions and/or notes, and whether to use the "overlay" style.

  • Like 6

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Gadgetto
      Status update links (inside this thread) for SnipWire development will be always posted here:
      2019-08-08
      2019-06-15
      2019-06-02
      2019-05-25
      If you are interested, you can test the current state of development:
      https://github.com/gadgetto/SnipWire
      Please note that the software is not yet intended for use in a production system (alpha version).
      If you like, you can also submit feature requests and suggestions for improvement. I also accept pull requests.
      ---- INITIAL POST FROM 2019-05-25 ----
      I wanted to let you know that I am currently working on a new ProcessWire module that fully integrates the Snipcart Shopping Cart System into ProcessWire. (this is a customer project, so I had to postpone the development of my other module GroupMailer).
      The new module SnipWire offers full integration of the Snipcart Shopping Cart System into ProcessWire.
      Here are some highlights:
      simple setup with (optional) pre-installed templates, product fields, sample products (quasi a complete shop system to get started immediately) store dashboard with all data from the snipcart system (no change to the snipcart dashboard itself required) Integrated REST API for controlling and querying snipcart data webhooks to trigger events from Snipcart (new order, new customer, etc.) multi currency support self-defined/configurable tax rates etc. Development is already well advanced and I plan to release the module in the next 2-3 months.
      I'm not sure yet if this will be a "Pro" module or if it will be made available for free.
      I would be grateful for suggestions and hints!
      (please have a look at the screenshots to get an idea what I'm talking about)
       




    • By apeisa
      Update 31.7.2019: AdminBar is now maintained by @teppo. Modules directory entry has been updated, as well as the "grab the code" link below.
      ***
      Latest screencast: http://www.screencas...73-ab3ba1fea30c
      Grab the code: https://github.com/teppokoivula/AdminBar
      ***
      I put this Adminbar thingy (from here: http://processwire.c...topic,50.0.html) to modules section and to it's own topic.
      I recorded quick and messy screencast (really, my first screencast ever) to show what I have made so far. You can see it from here: http://www.screencas...18-1bc0d49841b4
      When the modal goes off, I click on the "dark side". I make it so fast on screencast, so it might seem a little bit confusing. Current way is, that you can edit, go back to see the site (without saving anything), continue editing and save. After that you still have the edit window, but if you click "dark side" after saving, then the whole page will be reloaded and you see new edits live.
      I am not sure if that is best way: there are some strengths in this thinking, but it is probably better that after saving there shouldn't be a possibility to continue editing. It might confuse because then if you make edits, click on dark side -> *page refresh* -> You lose your edits.
      ***
      When I get my "starting module" from Ryan, I will turn this into real module. Now I had to make some little tweaks to ProcessPageEdit.module (to keep modal after form submits). These probably won't hurt anything:
      if($this->redirectUrl) $this->session->redirect($this->redirectUrl); if(!empty($_GET['modal'])) $this->session->redirect("./?id={$this->page->id}&modal=true"); // NEW LINE else $this->session->redirect("./?id={$this->page->id}");   and...
      if(!empty($_GET['modal'])) { $form->attr('action', './?id=' . $this->id . '&modal=true'); } else { $form->attr('action', './?id=' . $this->id); // OLD LINE }  
    • By Mike Rockett
      Jumplinks for ProcessWire
      Release: 1.5.54
      Composer: rockett/jumplinks
      Jumplinks is an enhanced version of the original ProcessRedirects by Antti Peisa.
      The Process module manages your permanent and temporary redirects (we'll call these "jumplinks" from now on, unless in reference to redirects from another module), useful for when you're migrating over to ProcessWire from another system/platform. Each jumplink supports wildcards, shortening the time needed to create them.
      Unlike similar modules for other platforms, wildcards in Jumplinks are much easier to work with, as Regular Expressions are not fully exposed. Instead, parameters wrapped in curly braces are used - these are described in the documentation.
      Under Development: 2.0, to be powered by FastRoute
      As of version 1.5.0, Jumplinks requires at least ProcessWire 2.6.1 to run.
      View on GitLab
      Download via the Modules Directory
      Read the docs
      Features
      The most prominent features include:
      Basic jumplinks (from one fixed route to another) Parameter-based wildcards with "Smart" equivalents Mapping Collections (for converting ID-based routes to their named-equivalents without the need to create multiple jumplinks) Destination Selectors (for finding and redirecting to pages containing legacy location information) Timed Activation (activate and/or deactivate jumplinks at specific times) 404-Monitor (for creating jumplinks based on 404 hits) Additionally, the following features may come in handy:
      Stale jumplink management Legacy domain support for slow migrations An importer (from CSV or ProcessRedirects) Feedback & Feature Requests
      I’d love to know what you think of this module. Please provide some feedback on the module as a whole, or even regarding smaller things that make it whole. Also, please feel free to submit feature requests and their use-cases.
      Note: Features requested so far have been added to the to-do list, and will be added to 2.0, and not the current dev/master branches.
      Open Source

      Jumplinks is an open-source project, and is free to use. In fact, Jumplinks will always be open-source, and will always remain free to use. Forever. If you would like to support the development of Jumplinks, please consider making a small donation via PayPal.
      Enjoy! :)
    • By nbcommunication
      I've spent the last while experimenting with srcset implementation - and PageimageSrcset is the result:
      PageimageSrcset
      Provides configurable srcset and sizes properties/methods for Pageimage.
      Overview
      The main purpose of this module is to make srcset implementation as simple as possible in your template code. It does not handle images rendered in CKEditor or similar fields.
      For an introduction to srcset and sizes, please read this Mozilla article about responsive images.
      Pageimage::srcset()
      // The property, which uses the set rules in the module configuration $srcset = $image->srcset; // A method call, using a set rules string // Delimiting with a newline (\n) would also work, but not as readable $srcset = $image->srcset("320, 480, 640x480 768w, 1240, 2048 2x"); // The same as above but using an indexed/sequential array $srcset = $image->srcset([ "320", "480", "640x480 768w", "1240", "2048 2x", ]); // The same as above but using an associative array // No rule checking is performed $srcset = $image->srcset([ "320w" => [320], "480w" => [480], "768w" => [640, 480], "1240w" => [1240], "2x" => [2048], ]); // Use the default set rules with portrait images generated for mobile/tablet devices $srcset = $image->srcset(true); // Return the srcset using all arguments $srcset = $image->srcset("320, 480, 640x480 768w, 1240, 2048 2x", [ "portrait" => "320, 640", ]); // The set rules above are a demonstration, not a recommendation! Image variations are only created for set rules which require a smaller image than the Pageimage itself. On large sites this may still result in a lot of images being generated. If you have limited storage, please use this module wisely.
      Portrait Mode
      In many situations, the ratio of the image does not need to change at different screen sizes. However, images that cover the entire viewport are an exception to this and are often the ones that benefit most from srcset implementation.
      The main problem with cover images is that they need to display landscape on desktop devices and portrait when this orientation is used on mobile and tablet devices.
      You can automatically generate portrait images by enabling portrait mode. It is recommended that you use this in combination with Pageimage::focus() so that the portrait variations retain the correct subject.
      The generated variations are HiDPI/Retina versions. Their height is determined by the portrait ratio (e.g. 9:16). Variations are always generated, regardless of whether the original image is smaller. Upscaling is disabled though, so you may find that some variations are actually smaller than they say they are in their filename.
      The sizes attribute should be used when portrait mode is enabled. Pageimage::sizes will return (orientation: portrait) and (max-width: {maxWidth}px) 50vw by default, which handles the use of these images for retina devices. The maximum width used in this rule is the largest set width.
      Pageimage::sizes()
      There is no option to configure default sizes because in most cases 100vw is all you need, and you do not need to output this anyway as it is inferred when using the srcset attribute. You can use the method for custom sizes though:
      // The property $sizes = $image->sizes; // Returns 100vw in most cases // Returns '(orientation: portrait) and (max-width: {maxWidth}px)50vw' if portrait mode enabled // A method call, using a mixture of integer widths and media query rules // Integer widths are treated as a min-width media query rule $sizes = $image->sizes([ 480 => 50, "(orientation: portrait) and (max-width: 640px)" => 100, 960 => 25, ]); // (min-width: 480px) 50vw, (orientation: portrait) and (max-width: 640px) 100vw, (min-width: 960px) 25vw // Determine widths by UIkit 'child-width' classes $sizes = $image->sizes([ "uk-child-width-1-2@s", "uk-child-width-1-3@l", ]); // (min-width: 640px) 50vw, (min-width: 1200px) 33.33vw // Determine widths by UIkit 'width' classes $sizes = $image->sizes([ "uk-width-1-2@m", "uk-width-1-3@xl", ]); // (min-width: 960px) 50vw, (min-width: 1600px) 33.33vw // Return the portrait size rule $sizes = $image->sizes(true); // (orientation: portrait) and (max-width: {maxWidth}px) 50vw // The arguments above are a demonstration, not a recommendation! Pageimage::render()
      This module extends the options available to this method with:
      srcset: When the module is installed, this will always be added, unless set to false. Any values in the formats described above can be passed. sizes: Only used if specified. Any values in the formats described above can be passed. uk-img: If passed, as either true or as a valid uk-img value, then this attribute will be added. The srcset attribute will also become data-srcset. Please refer to the API Reference for more information about this method.
      // Render an image using the default set rules echo $image->render(); // <img src='image.jpg' alt='' srcset='{default set rules}'> // Render an image using custom set rules echo $image->render(["srcset" => "480, 1240x640"]); // <img src='image.jpg' alt='' srcset='image.480x0-srcset.jpg 480w, image.1240x640-srcset.jpg 1240w'> // Render an image using custom set rules and sizes // Also use the `markup` argument echo $image->render("<img class='image' src='{url}' alt='Image'>", [ "srcset" => "480, 1240", "sizes" => [1240 => 50], ]); // <img class='image' src='image.jpg' alt='Image' srcset='image.480x0-srcset.jpg 480w, image.1240x640-srcset.jpg 1240w' sizes='(min-width: 1240px) 50vw'> // Render an image using custom set rules and sizes // Enable uk-img echo $image->render([ "srcset" => "480, 1240", "sizes" => ["uk-child-width-1-2@m"], "uk-img" => true, ]); // <img src='image.jpg' alt='' data-uk-img data-srcset='image.480x0-srcset.jpg 480w, image.1240x640-srcset.jpg 1240w' sizes='(min-width: 960px) 50vw'> // Render an image using portrait mode // Default rule sets used: 320, 640, 768, 1024, 1366, 1600 // Portrait widths used: 320, 640, 768 // Original image is 1000px wide // Not possible to use portrait mode and custom sets or portrait widths in render() // Sizes attribute automatically added echo $image->render(["srcset" => true]); // <img src='image.jpg' alt='' srcset='image.320x569-srcset-hidpi.jpg 320w, image.640x1138-srcset-hidpi.jpg 640w, image.768x1365-srcset-hidpi.jpg 768w, image.jpg 1024w' sizes='(orientation: portrait) and (max-width: 768px) 50vw'> Configuration
      To configure this module, go to Modules > Configure > PageimageSrcset.
      Set Rules
      These are the default set rules that will be used when none are specified, e.g. when calling the property: $image->srcset.
      Each set rule should be entered on a new line, in the format {width}x{height} {inherentwidth}w|{resolution}x.
      Not all arguments are required - you will probably find that specifying the width is sufficient for most cases. Here's a few examples of valid set rules and the sets they generate:
      Set Rule Set Generated Arguments Used 320 image.320x0-srcset.jpg 320w {width} 480x540 image.480x540-srcset.jpg 480w {width}x{height} 640x480 768w image.640x480-srcset.jpg 768w {width}x{height} {inherentwidth}w 2048 2x image.2048x0-srcset.jpg 2x {width} {resolution}x How you configure your rules is dependent on the needs of the site you are developing; there are no prescriptive rules that will meet the needs of most situations. This article gives a good overview of some of the things to consider.
      When you save your rules, a preview of the sets generated and an equivalent method call will be displayed to the right. Invalid rules will not be used, and you will be notified of this.
      Portrait Mode
      Set Widths
      A comma limited list of widths to create HiDPI/Retina portrait variations for.
      Crop Ratio
      The portrait ratio that should be used to crop the image. The default of 9:16 should be fine for most circumstances as this is the standard portrait ratio of most devices. However, you can specify something different if you want. If you add a landscape ratio, it will be switched to portrait when used.
      Any crops in the set rules ({width}x{height}) are ignored for portrait mode variations as this ratio is used instead.
      UIkit Widths
      If your website theme uses UIkit, you can pass an array of UIkit width classes to Pageimage::sizes to be converted to sizes. The values stored here are used to do this. If you have customised the breakpoints on your theme, you should also customise them here.
      Please note that only 1- widths are evaluated by Pageimage::sizes, e.g. uk-width-2-3 will not work.
      Remove Variations
      If checked, the image variations generated by this module are cleared on Submit. On large sites, this may take a while. It makes sense to run this after you have made changes to the set rules.
      Image Suffix
      You will see this field when Remove Variations is checked. The value is appended to the name of the images generated by this module and is used to identify variations. You should not encounter any issues with the default suffix, but if you find that it conflicts with any other functionality on your site, you can set a custom suffix instead.
      Debug Mode
      When this is enabled, a range of information is logged to pageimage-srcset.
      PageimageSrcsetDebug.js is also added to the <head> of your HTML pages. This will console.log a range of information about the images and nodes using srcset on your page after a window.onresize event is triggered. This can assist you in debugging your implementation.
      The browser will always use the highest resolution image it has loaded or has cached. You may need to disable browser caching to determine whether your set rules are working, and it makes sense to work from a small screen size and up. If you do it the other way, the browser is going to continue to use the higher resolution image it loaded first.
      UIkit Features
      This module implements some additional features that are tailored towards UIkit being used as the front-end theme framework, but this is not required to use the module.
      Installation
      Download the zip file at Github or clone the repo into your site/modules directory. If you downloaded the zip file, extract it in your sites/modules directory. In your admin, go to Modules > Refresh, then Modules > New, then click on the Install button for this module. ProcessWire >= 3.0.123 is required to use this module.
×
×
  • Create New...