adrian

Tracy Debugger

Recommended Posts

Hey @bernhard and anyone else who might be interested. Following up on my thoughts over here: 

Here's my first test:

cN2HuqqpHQ.gif.2dd012031f190c034de37754f9aaa2f0.gif

 

This comes from a new file which currently contains:

var getCodeSnippets = function() {
    return [
        {
          content: 'd(\\$pages->find("template=\${1:basic-page}")->each("\${2:title}"));',
          name: 'find-pages',
          tabTrigger: 'pwfind'
        }
    ]
};

 

I feel like there needs to be some thought put into how these should work and what the tabTrigger text should be. As you can see this one is about directly d() 'ing, but I am not sure whether it would be more versatile without that wrapping d(). Perhaps we could have both versions?

Maybe we also want something that simply returns:

foreach($pages->find("template=basic-page") as $p) {
    d($p);
}

 

I am really not sure what approach to take here.

Also, do you guys want to contribute snippets to the Tracy core, or would you prefer being able to define your own in a file or in the config settings?

Any thoughts?

Thanks!
 

  • Like 1

Share this post


Link to post
Share on other sites
Quote

or would you prefer being able to define your own in a file or in the config settings? 

Wouldn`t defining your own in a file or in the config settings not be more versatile ? e.g. cross editor compatible

Share this post


Link to post
Share on other sites
15 minutes ago, pwired said:

Wouldn`t defining your own in a file or in the config settings not be more versatile ? e.g. cross editor compatible

Sorry, not sure I understand how this makes things cross editor compatible. 

Honestly I think that all these should probably be in the core. After-all we have the actual snippets panel for you to define and use your own custom ones that others may not find useful.

  • Like 1

Share this post


Link to post
Share on other sites

ACE also comes with a bunch of predefined PHP snippets.

image.png.ff88750ba4cf40080afb8b4e82a77212.png

image.png.034b9b67403a561f549ec843b0c891f3.png

This will all be available in the next release of Tracy.

  • Like 1

Share this post


Link to post
Share on other sites
19 hours ago, bernhard said:

Maybe tracy could even be built a little differently to support 3rd party modules. Just like you did recently with the admin actions module (https://processwire.com/talk/topic/14921-admin-actions/?do=findComment&comment=173496). I'm not requesting this, I'm just thinking out loud here.

Hey @bernhard - sorry I forgot to respond to this before. This is certainly a possibility if there is demand. The advantage of course is that panel authors can maintain the codebase for their panel completely without relying on me to handle PRs etc. The downside is that new Tracy users needs to hunt around to find third-party panels so if we take this approach we'll want to make sure to list them all on a dedicated page on the docs site.

Let me know if anyone out there is interested in this.

Share this post


Link to post
Share on other sites

OK, just released a major new version: 4.12.0

 

1) New Title/View link in Dump tabs, so ID is edit link and title/name is view link

image.png.4e3e74a1eccf862d03727692811409e6.png

 

2) New PagePermissions section added to PW Info panel:

image.png.e67e362f0c591f22edc76a11e9600723.png

 

3) New PHP and custom PW autocomplete snippets added to the Console and File Editor panels. Here's one example, but there are others in the posts prior to this one showing general PHP snippets.

Currently there are two custom PW snippets: pwforeach and pwfind - I'd love to hear what you guys want to see here. If you have new snippet ideas, please take a look at: https://github.com/adrianbj/TracyDebugger/blob/master/scripts/code-snippets.js and feel free to send PRs with new additions.

UPmNZ6c7kf.gif.d0b9e73ed018e3e68fff9876f1e89159.gif

 

4) Ability to dynamically resize the font in the Console and File Editor panels with:

Increase: CTRL + +/=
Decrease: CTRL + -/_
Reset: CTRL + 0

 

5) Changes to the way the Console panel divs are structured and resized - please let me know if you see any issues with the results panel protruding beyond the bottom of the panel or any other issues. It's still not perfect, but it's breaking my brain 🙂

 

6) Some minor Tracy core updates and also general cleanup of many of the custom panels.

 

Please let me know if you have any problems with this new version, or ideas for improvements!

  • Like 5

Share this post


Link to post
Share on other sites
Quote

New PHP and custom PW autocomplete snippets added to the Console and File Editor panels

Thanks fly out for it. Going to edit some of my pages with this and report back.

  • Like 1

Share this post


Link to post
Share on other sites

Great additions as always! Thanks for the tutorial on building panels, I'll try that when I have an idea for something 🙂

9 hours ago, adrian said:

Also, do you guys want to contribute snippets to the Tracy core, or would you prefer being able to define your own in a file or in the config settings?

Any thoughts?

IMHO the best would be to have one shared file in the core and one file specific to each user, because habits are different so I think not all snippets will be helpful to everybody. On the other side it would be great (not to say necessary) to be able to define those snippets somewhere shared across multiple installs of tracy, so that we always have all our snippets available.

I think the best option would be to define a web-url (eg github snippet url to a raw file) and pull this file into the pw cache regularly. Everybody could then just push a new snippet to his git account (or on his webserver) and all tracy installations referencing this file would always be up to date with this file.

If you are happy with that idea I can try to implement that feature and do a PR

  • Like 2

Share this post


Link to post
Share on other sites
17 minutes ago, bernhard said:

I think the best option would be to define a web-url (eg github snippet url to a raw file) and pull this file into the pw cache regularly. Everybody could then just push a new snippet to his git account (or on his webserver) and all tracy installations referencing this file would always be up to date with this file.

I was actually thinking along those lines as well, but I do want to encourage PRs to main file that comes with Tracy as well.

But yeah if you want to add support for pointing to a Github gist URL, or any other URL I suppose, I think that would be a nice addition.

Share this post


Link to post
Share on other sites

I think we should be careful with those snippets. One might find a snippet helpful, another one might find it annoying. If we bloat tracy with snippets it might be counterproductive. I'll see when I find time to dig into that!

  • Like 3

Share this post


Link to post
Share on other sites

Ok, I have implemented the ability to link to your own custom snippets file:

image.thumb.png.8034531982094be4c2829ecdd88a205d.png

If you're using a Github Gist, make sure you use the https://rawgit.com/ service because the raw file from Github is served without the correct mime type and won't work. 

The format of the custom snippet file is like this. Note the getCustomCodeSnippets() compared with the core snippets file which uses getCodeSnippets()

var getCustomCodeSnippets = function() {
    return [
        {
          name: "pwfind",
          content: "d(\\$pages->find(\"template=\${1:basic-page}\")->each(\"\${2:title}\"));",
          tabTrigger: "pwfind"
        },
        {
          name: "pwforeach",
          content: "foreach(\\$pages->find(\"template=\${1:basic-page}\") as \\$p) {\n\td(\\$p);\n}",
          tabTrigger: "pwforeach"
        }
    ]
};

At the moment the custom snippets file is PHP only. I don't think we will ever need other languages for this.


I have also added in the ACE core snippet files for other web related languages so if you use the File Editor panel for JS, CSS, etc, there will now be a bunch of useful snippets for those languages as well.

If you want to peruse the available ACE core snippets, the best way is probably here: https://github.com/ajaxorg/ace/blob/master/lib/ace/snippets/php.snippets 

You can also check out the snippets for other languages in the parent folder of that file.

 

  • Like 3

Share this post


Link to post
Share on other sites

What do you guys think of me adding things like this:

nbGRfETAFW.gif.5e256568ee3fdda068c118c2b5bbfa18.gif

  • Like 1

Share this post


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

What do you guys think of me adding things like this:

To be honest, I would not care too much about it (I guess). I'll have to think of it during further usage of the console. If you implement them, then I'd suggest you implement them in a way that they pull the current api and are always up to date (no idea how hard that would be). Otherwise you'd get plenty of requests to keep everything up to date, I'm afraid. But maybe others think differently...

What annoys me, though, are suggestions like this:

A11PnOr.png

Would it be somehow possible to prevent those suggestions of php functions when I actually want to access an object property/method? Thx

  • Like 1

Share this post


Link to post
Share on other sites
8 hours ago, bernhard said:

If you implement them, then I'd suggest you implement them in a way that they pull the current api and are always up to date (no idea how hard that would be).

Yeah, already done on my dev copy - all PW variables are automatically added to the autocomplete.

bFDXXA2w3E.gif.227e25a80f2a945998748d7021bdadb8.gif

 

8 hours ago, bernhard said:

What annoys me, though, are suggestions like this:

Agreed - I am working on this - I don't necessarily want to disable php autocompletions completely, but trying to tweak the triggering so it's not invasive when you don't want it.

  • Like 2

Share this post


Link to post
Share on other sites

Or perhaps this is even cleaner for the plain PW variables when they are not actually snippets:

3c5rQ1tTEV.gif.9e18aa018f149a4cd18347660d1d104d.gif

Share this post


Link to post
Share on other sites

Also just got this working, all generated automatically from the currently PW install, so it's always up-to-date.

Do you guys think you'd make use of this?

image.png.dfcf093aecb0c631d236908f56df4209.png

  • Like 6

Share this post


Link to post
Share on other sites
Quote

One might find a snippet helpful, another one might find it annoying. If we bloat tracy with snippets it might be counterproductive.

I agree with Bernhard there. The editor should focus on basic and speed. I think that is what is most loved when editing code.

I noticed that this editor has much lesser lag compared to other editors I use who update edited code through ftp. I like the update speed of this editor when you click on save. I also like that it shows hidden formats like empty space and new line to spot any other format that might got in when copying and pasting code from your own snippets.

The Increase: CTRL + works very nice to increase editors font size.

Also like it a lot that the editors window can sticky float anywhere in the backend window.

Quote

I have also added in the ACE core snippet files for other web related languages so if you use the File Editor panel for JS, CSS, etc, there will now be a bunch of useful snippets for those languages as well.

I saw it in action when I was editing some css. I even noticed a little red box with a white cross that indicates typos made when editing. That is just great.

I have been looking a bit for the css where I could change the background of the editor. I assume it is inside the style.css in the module folder. Would also like to style <?php and ?> in blue and bold.

 

Share this post


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

I agree with Bernhard there. The editor should focus on basic and speed. I think that is what is most loved when editing code.

Agreed - I don't want either the Console panel or FileEditor panel to slow down at all - I'll make sure that any autocomplete/snippet stuff I add doesn't cause any slowdown.

Glad that in general you enjoy using these tools.

13 hours ago, pwired said:

I have been looking a bit for the css where I could change the background of the editor. I assume it is inside the style.css in the module folder. Would also like to style <?php and ?> in blue and bold.

The best way to change the editor color is to use the built in themes. I actually haven't included any other themes with the Tracy package, but I could easily add these and create a new module config setting so you can choose the theme - there are a lot of options - check out the kitchen sink demo (https://ace.c9.io/build/kitchen-sink.html) and try out the Theme dropdown.

  • Like 1

Share this post


Link to post
Share on other sites
Quote

check out the kitchen sink demo (https://ace.c9.io/build/kitchen-sink.html) and try out the Theme dropdown.

Hi,

I have been fiddling around in the ace-editor folder inside the TracyDebugger module folder
to find a way to change the theme and font size, but without success.

In the kitchen-sink, for the TracyDebugger editor, how can I change the theme-tomorrow_night into IPlastic with font-size 17 ?

 

image.png.8e0a7250d5554c759a66237fa74e97d1.png

 

 

Share this post


Link to post
Share on other sites
3 hours ago, pwired said:

I have been fiddling around in the ace-editor folder inside the TracyDebugger module folder
to find a way to change the theme and font size, but without success.

In the kitchen-sink, for the TracyDebugger editor, how can I change the theme-tomorrow_night into IPlastic with font-size 17 ?

I haven't packaged the other themes with Tracy yet, but I can do so if you guys are interested. I initially went with just one theme (my favorite) because I wasn't sure how much use the Console and File Editor panels would get, but given their popularity I think it probably makes sense to include all the themes so you guys can choose what you prefer.

I guess the next question is to figure out whether you guys want to be able to adjust all ACE editor settings via a textarea with key:value pairs or whether I should provide the key settings I think you might want to adjust as dedicated fields in the module settings like I have with the tab size, type and show invisibles settings. What does everyone think?

  • Like 1

Share this post


Link to post
Share on other sites

Is this going too far having the doc comment displayed? It's a good learning tool. Maybe make it optional, or do you guys think just leave it out completely?

qtY05Agimd.thumb.gif.d6c3a62727ebce59e8d27b2ae00efdfa.gif

  • Like 1

Share this post


Link to post
Share on other sites
Quote

I haven't packaged the other themes with Tracy yet, but I can do so if you guys are interested.

The TracyDebugger editor can sticky float anywhere and has a full screen toggle which makes it very practical,
so I guess more people are going to pick it up.
Would be nice to have a few themes because everybody experiences different colors as hard colors for the eyes to work with.
Is it difficult to port an Ace theme to TracyDebugger ? Maybe I can help with something ?

  • Like 1

Share this post


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

Is it difficult to port an Ace theme to TracyDebugger ? Maybe I can help with something ?

Thanks but it's super easy. Just before I do I need to decide how to facilitate the various Ace settings like I mentioned above. 

  • Like 1

Share this post


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

I haven't packaged the other themes with Tracy yet, but I can do so if you guys are interested.

It doesn't look like they are massive (size), so, maybe yes, one or two more. I'm happy with the dark theme, so I am biased 🙂.

  • Like 3

Share this post


Link to post
Share on other sites
Quote

It doesn't look like they are massive (size), so, maybe yes, one or two more.

I think Kongondo has a point there. To prevent bloat creeping in, maybe it would be an idea to leave it up to the user which theme to get inside the ace-editor folder ?

In the ace-editor folder I noticed the file: theme-tomorrow_night.js

Just the possibility to let users change this file manually into another one e.g. theme-iplastic.js, and also manually edit font size, maybe that would be a bloat free solution ?

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: