adrian

Tracy Debugger

Recommended Posts

The new Console panel fullscreen mode now has keyboard shortcuts to collapse the code or results panes quickly.

Here you can see me toggling all code, all results, and the split of both.

Shortcuts are:

CTRL+SHFT+ 

Up arrow - collapses code pane
Down arrow - collapses results pane
Left arrow - to restore split to what it was before you initiated any pane collapses.

Hopefully you'll find this a really quick way to get to the view you need.

rlLAPv47u9.gif.0f3c122f4c276e2f3833fd9971ed6d46.gif

  • Like 4

Share this post


Link to post
Share on other sites

New version fixes a few bugs in the last release, especially regarding the keyboard shortcuts on Windows. Along these lines, I have also changed the shortcuts for the History Stack - they are now ALT+PageUp and ALT+PageDown. This means there is no longer the need to use the meta key (CMD or WIN key) for this which was conflicting on some systems. If you're on a Macbook without PU and PD keys, just use: fn + ALT + PageUp/Down

A big thanks to @Robin S for helping with all the Windows testing on this!

I think this is really starting to work really nicely now - I almost want to use it over my code editor 🙂

Anyway, please let me know if you find any issues.

  • Like 2

Share this post


Link to post
Share on other sites

Hi Adrian,

Does the "User dev template" feature do anything with _main.php if using the delayed output strategy?

If not, what do you think about adding a feature where _main.php is replaced with _main-dev.php if that file exists? Of course the relevant file names would depend on what is defined in $config->appendTemplateFile and the Tracy "User dev template suffix" setting. And to round things out I guess do the same for $config->prependTemplateFile (_init.php).

Share this post


Link to post
Share on other sites
13 hours ago, Robin S said:

Hi Adrian,

Does the "User dev template" feature do anything with _main.php if using the delayed output strategy?

If not, what do you think about adding a feature where _main.php is replaced with _main-dev.php if that file exists? Of course the relevant file names would depend on what is defined in $config->appendTemplateFile and the Tracy "User dev template suffix" setting. And to round things out I guess do the same for $config->prependTemplateFile (_init.php).

Hey @Robin S - it didn't, but now it does 🙂

I have also implemented this for the User Bar Page Versions feature and the Template Path panel. These three things do almost the same thing, but for different users in different scenarios.

I am going to PM you a copy of this new version to take a look at. I have some other things I am working on and I want to commit altogether.

  • Like 1

Share this post


Link to post
Share on other sites

Various significant updates today.

As per @Robin S's suggestion above, the User Bar Page Versions, User Dev Template and Template Path panel features now support automatic swapping out of the files included via `$config->prependTemplateFile` and `$config->appendTemplateFile` to use the same suffix at the replaced template, eg `_init-dev.php` or `_main-dev.php` if you are on the home page and using a home-dev.php template file replacement.

Robin also helped me track down a critical bug that was introduced to Page Versions and User Dev Templates some time ago - thanks for that!

If you haven't checked out any of these features in Tracy before, they can be very handy for testing changes (especially on a live site). In particular, giving your clients access to choose from a dropdown of template options can be a very easy way to get their feedback on various options.

I have also made several improvements to the new Console panel fullscreen editing experience and also updated the way the results pane scrolls when new items are added. Previously it always scrolled to the bottom of the pane. Now it scrolls to the top of the recently added section, so if you are using Clear & Run, then it will alway be at the top, but if you just Run to add new items, it will scroll down to the top of the new items. Hopefully you'll all find this a nice improvement and will help to reduce your scrolling.

I recently noticed some nasty issues with the Console panel in Safari, especially the new fullscreen editing mode, but also when trying to manually resize the panel. Everything looks/works great on Chrome, Firefox, and Opera. I'll take another look and see what I can do about getting Safari to play nicely, but sometimes I feel like Safari is the new IE 🙂

 

  • Like 3

Share this post


Link to post
Share on other sites

Ok, I officially hate Safari more than I already thought I did 🙂

I have fixed a whole range of issues I had never noticed previously (mainly because I rarely use it).

Detailing here in case they are useful for your development in general.

 

1) You can't resize panels smaller than their initial size on page load

I did however fix the internals of the Console not expanding to match a larger panel if you size larger.

The issue is that Webkit browsers will not let you use the CSS "resize" property to resize an element to make it smaller, only larger (in both dimensions): https://css-tricks.com/almanac/properties/r/resize/

Man it took me a long time to figure out why that wasn't working - I thought there was some min-height / min-width type thing going on that was only affecting Safari.

Thank goodness Chrome no longer uses the Webkit engine!

 

2) Safari doesn't play nicely with position: fixed when elements are outside document.body

The Tracy core adds its elements to document.documentElement so the only way I could figure around this was to move the Console panel to document.body when clicking the new fullscreen toggle and then back again when restoring to the panel size. This was also really difficult to track down and I never found any reference to this issue online anywhere - fun times 🙂 

Because the parent element is changed, I had to change the parent element of several css selectors. I can't find anything broken as a result, but please keep an eye out and let me know if you see anything amiss.

 

3) Fix missing inner scrollbar in code editor pane

This one looks to be a long standing Ace Editor bug, but someone else figured out a simple workaround: https://github.com/ajaxorg/ace/issues/2872

 

4) Fixed some keyboard shortcut bugs due to missing e.preventDefault()

Please let me know if you find any other issues like this

 

Anyway, I think I am done with Safari tweaks for now. I am not sure how many of you are even using it for regular development so I don't want to put too much more time into it, but please do let me know if you find anything I missed.

 

  • Like 3

Share this post


Link to post
Share on other sites
2 hours ago, adrian said:

using it for regular development

Are you kidding? 😉

Thanks a million, btw!

  • Like 1

Share this post


Link to post
Share on other sites

One more quick update. In addition to the existing shortcut keys for toggling the size of the code and results panes in the Console panel, I have added a new one:

CTRL + SHFT + → 

Which resizes the code pane to the height of all the lines of code:

EycZvBSDZG.gif.1fa6a8dac547b943637cf06a069a21fa.gif

  • Like 4

Share this post


Link to post
Share on other sites

One more shortcut 🙂

CTRL + SHFT + ENTER will toggle the Console in and out of fullscreen.

 

Totally random, but a little tip about the Console panel - not only is it great for testing the PW API and PHP in general, it's also pretty nice for testing JS code out. Take this example of:

  • calling an external API
  • populating an element in the Console results pane with a property from the returned JSON
  • logging the result to the browser dev console

ctN9oBrlFD.thumb.gif.598b9cab370b2ba85cdc2f10919f3669.gif

 

Why use this over the browser console, or CodePen, JSFiddle etc? Well, notice that the API call is grabbing a PW field from the current page:

'https://represent.opennorth.ca/postcodes/<?=$page->postcode?>/'

 

Also, if you are a fan of the output of the Browser dev console, don't forget about Tracy's fl() option to dump objects direct to this.

Anyway, hope there is something useful there if you hadn't thought about it before 🙂

  • Like 3

Share this post


Link to post
Share on other sites

Hi,

I have installed TracyDebugger on a live website, enabled it, set output mode to Development, and enabled File Editor

but I cannot find the FileEditor e.g. to edit the online template files. What do I have to do to find it ?

 

tracy.jpg

Share this post


Link to post
Share on other sites

My bad sorry. I found the File Editor.

But when I select a template file on the left, the editor window on the right does not update. The editor window on the right stays the same.

Double clicking on a template file on the left does not make a difference, the editor window on the right always shows the same.

tracy-2.jpg

  • Like 1

Share this post


Link to post
Share on other sites
1 minute ago, pwired said:

But when I select a template file on the left, the editor window on the right does not update. The editor window on the right stays the same.

Double clicking on a template file on the left does not make a difference, the editor window on the right always shows the same.

Works for me. Can you please check for JS errors in the browser dev console.

Any difference in another browser?

  • Like 1

Share this post


Link to post
Share on other sites

Is it necessary to have debug = on for the file editor to work ?

I am using FireFox, will try Chrome

Share this post


Link to post
Share on other sites
Just now, pwired said:

Is it necessary to have debug = on for the file editor to work ?

Nope!

  • Like 1

Share this post


Link to post
Share on other sites

Ok the problem must be in my FireFox browser

Edit:
The File Editor is working perfectly in my Chrome browser,
and also in my Opera browser (45.0)

Thanks Adrian

 

Edited by pwired
Tried Opera Browser
  • Like 1

Share this post


Link to post
Share on other sites
Just now, pwired said:

Ok the problem must be in my FireFox browser

The File Editor is working perfectly in my Chrome browser

Good to hear - I'll take a look here with Firefox on Mac and see if I can reproduce and fix it.

Share this post


Link to post
Share on other sites

I am using FireFox Quantum ver 61.0.1 (64bit)

Maybe it has become messed up after so many weeks of heavy use. Will do a clean install and check again.

Share this post


Link to post
Share on other sites

@pwired - I could reproduce with Firefox on MacOS and I have pushed a fix in the latest version. Please let me know how it goes at your end.

New version also removes the keyboard shortcut text from the top of the Console panel and adds a new toggleable popup info table of all shortcuts:

cValA8pRkk.thumb.gif.961039bee582b637e21d26e082f5e677.gif

  • Like 2

Share this post


Link to post
Share on other sites

Hi,

I uninstalled the previous version 4.11.32 and installed the latest version 4.11.34

I can confirm: now it is working in FireFox,

 

Record_2018_09_19_04_41_44_238.gif

 

Thanks, all good.

  • Like 1

Share this post


Link to post
Share on other sites

Another round of tweaks, bug fixes and new features.

1) File Editor revamp to improve layout and adds a new fullscreen editing mode (like the one added to the Console panel), also with the same CTRL + SHFT + Enter shortcut for toggling in and out of that fullscreen.

2) More tweaks and code cleanup for the Console panel.

3) Some nice enhancements and cleanup for the SnippetRunner panel.

4) New "Open" option for the "Goto Page ID" feature in the PW Info panel - this opens the page's branch in the page tree. I find this entire feature very useful when working on sites where the templates make heavy use of IDs instead of paths for querying pages. If you haven't tried, give it a go. 🙂

5) Various bug fixes in the module and also in the Tracy core.

There are quite a lot of changes in this version, so please let me know if you find any issues.

 

 

  • Like 4

Share this post


Link to post
Share on other sites

Another round 🙂

1) I have revamped the fullscreen / halfscreen buttons that are on many of the panels. They have been replaced by a single Maximize / Restore button which I think it much more useful. Hope you guys agree!

2) I have removed the "open in window" link from all panels - I never used this feature and it was painful to get the layout of some of the more complex panels to work in this mode. If others are finding they miss it, let me know and I'll see about reinstating it.

 

  • Like 4

Share this post


Link to post
Share on other sites
11 minutes ago, adrian said:

Hope you guys agree

I did agree a week ago or two too 🙂

Nice updates btw.

  • Like 1

Share this post


Link to post
Share on other sites
1 minute ago, tpr said:

I did agree a week ago or two too 🙂

Nice updates btw.

I know, it was your suggestion that prompted me to make the change 🙂

Sometimes I am slow on coming around to a good idea 🙂

 

  • Haha 1

Share this post


Link to post
Share on other sites

Hey @tpr - sorry I just realized it was a bit rude of me to not acknowledge that change as your idea when I posted about it above.

Sorry about that!

  • Like 1

Share this post


Link to post
Share on other sites

No you haven't, don't take it too seriously 🙂

  • Like 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Robin S
      Another little admin helper module...
      Template Field Widths
      Adds a "Field widths" field to Edit Template that allows you to quickly set the widths of inputfields in the template.

      Why?
      When setting up a new template or trying out different field layouts I find it a bit slow and tedious to have to open each field individually in a modal just to set the width. This module speeds up the process.
      Installation
      Install the Template Field Widths module.
      Config options
      You can set the default presentation of the "Field widths" field to collapsed or open. You can choose Name or Label as the primary identifier shown for the field. The unchosen alternative will become the title attribute shown on hover. You can choose to show the original field width next to the template context field width.  
      https://github.com/Toutouwai/TemplateFieldWidths
      https://modules.processwire.com/modules/template-field-widths/
    • By horst
      Croppable Image 3
      for PW 3.0.20+
      Module Version 1.1.16
      Sponsored by http://dreikon.de/, many thanks Timo & Niko!
      You can get it in the modules directory!
      Please refer to the readme on github for instructions.
       
      -------------------------------------------------------------------------
       
      Updating from prior versions:
       
      Updating from Croppable Image 3 with versions prior to 1.1.7, please do this as a one time step:
      In the PW Admin, go to side -> modules -> new, use "install via ClassName" and use CroppableImage3 for the Module Class Name. This will update your existing CroppableImage3 module sub directory, even if it is called a new install. After that, the module will be recogniced by the PW updater module, what makes it a lot easier on further updates.
      -------------------------------------------------------------------------
       
      For updating from the legacy Thumbnail / CropImage to CroppableImage3 read on here.
       
      -------------------------------------------------------------------------
       
    • By MoritzLost
      UPDATE: I have published a stable version of this module!
      Discussion thread:
      Github: https://github.com/MoritzLost/TextformatterPageTitleLinks
      ---
      Hello there,
      I'm working on a tiny textformatter module that searches the text for titles of other pages on your site and creates hyperlinks to them. I'm not sure if something like this exists already, but I haven't found anything in the module directory, so I wrote my own solution 🙂
      It's not properly tested yet and is still missing some functionality I would like to implement, so at the moment it should be considered in BETA. Features include limiting the pages that will get searched by template, and adding a custom CSS class to the generated hyperlinks. As I'm writing this I noticed that it will probably include unpublished and hidden pages at the moment, so yeah ... it's still in development alright 😅
      You can download the module from Github:
      https://github.com/MoritzLost/TextformatterPageTitleLinks
      There's some more information in the readme as well.
      Anyway, let me know what you think! I'm happy about any feedback, possible improvements or ideas on how to improve the module. Cheers.
    • By blad
      Hi guys!
      I just uploaded a module to explore files based on elFinder. By default it will show the "Files" folder.
      Screenshots:

      Video:
       
      To do:
       More options To fix:
       The function of rotating or scaling an image fails  Image editors V 1.01 (view issue)
      Fixed the bug working with the Multi-Language support ( translation of folders ). Fixed the name of elfinder.en  Github:
      https://github.com/LuisSantiago/ProcessElFinder/
      I hope you like it.
    • By BitPoet
      I'm really in love with FormBuilder, but the one thing missing to match all my end users' expectations were repeatable field groups. Think repeaters, in ProcessWire terms. Our primary application of PW is our corporate intranet, so "lines" of fields are quite common in the forms I build. We have all kinds of request forms where the information for a varying number of colleagues needs to be entered (from meal order to flight booking request) and where it is simply impractical to send a form for each, and I don't want to clutter my forms with multiple instances of fields that may only get used ten percent of the time.
      That's why I started to build FormBuilderMultiplier (link to GitHub).
      What it does:
      Adds an option to make a regular Fieldgroup repeatable Lets you limit the number of instances of a Fieldgroup on the form Adds an "Add row" button the form that adds another instance of the Fieldgroup's fields Adds a counter suffix at the end of every affected field's label Stores the entered values just like regular fields Makes the entered values available in preview and email notifications Supports most text based fields, textareas and selects (really, I haven't had enough time to test all the available choices yet) What it doesn't do (yet):
      Support saving to ProcessWire pages (i.e. real Repeaters) I haven't tested all the validation stuff, Date/Time inputs etc. yet, but since I'm utterly swamped with other stuff at work, I didn't want to wait until I have it polished. Any feedback is welcome. There might also be some issues with different output frameworks that I haven't encountered yet. The forms I work with mostly use UIKit.
      Status:
      Still alpha, so test well before using it in the field.
      Known issues:
      When rows are added, the form's iframe needs to be resized, which isn't completely clean yet.
      How it works:
      The Fieldgroup settings are added through regular hooks, as is the logic that adds the necessary field copies for processing the form and displaying previews.
      "Multiplied" field instances are suffixed with _NUM, where NUM is an incremental integer starting from 1. So if you have add two fields named "surname" and "givenname" to a fieldgroup and check the "multiply" checkbox, the form will initially have "surname_1" and "givenname_1" field (I'm still considering changing that to make the risk to shoot oneself into the foot by having a regular "surname_1" field somewhere else in the form less likely).
      When a "row" is added, the first row is cloned through JS and the counter in the fields' IDs, names and "for" attributes as well as the counter in the label are incremented before appending the copies to the Fieldset container in the form.
      To keep backend and frontend in sync, a hidden field named [name of the fieldset]__multiplier_rows is added to the form. Both the backend and the frontend script use this to store and retrieve the number of "rows".
      ToDo:
      Naturally, add the option to store the data in real repeaters when saving to pages. Do a lot of testing (and likely fixing). Make a few things (like the "Add row" button label etc.) configurable in field(set) context. Add a smooth API to retrieve the multiplied values as WireArrays. The mandatory moving screenshot: