inline editor styles

master
Garrett Mills 3 years ago
parent 17793dfd7b
commit cbde363531
  1. 5
      app/assets/dash_v1.css
  2. 2
      app/views/dash_v1/use/api.pug
  3. 2
      app/views/dash_v1/use/ecma.pug
  4. 2
      app/views/dash_v1/use/main.pug
  5. 2
      app/views/dash_v1/use/node.pug
  6. 2
      app/views/dash_v1/use/php.pug

@ -85,6 +85,11 @@ pre {outline: 1px solid #ccc; padding: 5px; margin: 5px; }
z-index: 0;
}
#editor.inline {
height: auto;
min-height: 200px;
}
/* New Theme Styles */
body {
margin:0;

@ -2,7 +2,7 @@ extends ../template
block content
h3 DevBug supports anywhere within the reach of your network.
p You can use DevBug in any language that supports sending multipart/form-data POST requests. This is accomplished via the DevBug API. This is the same procedure the native DevBug clients use. The API is fairly simple to use and contains a single endpoint. The snippet below details how to use it:
pre#editor #{devbug.code.api}
pre#editor.inline #{devbug.code.api}
block scripts
script(src="https://cdnjs.cloudflare.com/ajax/libs/ace/1.4.5/ace.js")

@ -6,7 +6,7 @@ block content
p This function is similar to logging data. It stores data to be outputted to DevBug. The first parameter should be a string with a brief description of the data, and the second is the data to be outputted. Note that the info string should be unique and multiple outputs with the same name will overwrite their predecessors. It's important to note that calling this function doesn't actually <i>send</i> any data to DevBug. Instead, it stores it to be sent.
h4 <code>breakpoint(<i>continue = false</i>, <i>name = ""</i>)</code> - send the outputted data to DevBug
p This is the magic of the operation. When this function is called, any data that has been passed to the output function will be sent to the DevBug server and stored under the configured project. There are several things you can change about this function. The <code>continue</code> parameter determines whether or not program execution continues, or if the interpreter's exit method is called. The <code>name</code> parameter allows you to change the name of the breakpoint. This can be useful to help distinguish multiple breakpoints in the DevBug dashboard. Note that the continuation parameter is non-functional in browser-based ECMAscript.
pre#editor // Run the following as early in your application as your can:&#10;devbug_url="http://localhost:8000/";&#10;project_api_key="CHANGEME";
pre#editor.inline // Run the following as early in your application as your can:&#10;devbug_url="http://localhost:8000/";&#10;project_api_key="CHANGEME";
block scripts
script(src="https://cdnjs.cloudflare.com/ajax/libs/ace/1.4.5/ace.js")

@ -25,7 +25,7 @@ block content
ul
li New navigation theme with sticky navigation bar to make the display cleaner
li Separate "editor mode" layout for views using Ace.js
li Out viewer now uses editor mode.
li Out viewer and snippet editor now use editor mode.
h4 v0.5.1 - Use Ace.js for Outputs
ul

@ -6,7 +6,7 @@ block content
p This function is similar to logging data. It stores data to be outputted to DevBug. The first parameter should be a string with a brief description of the data, and the second is the data to be outputted. Note that the info string should be unique and multiple outputs with the same name will overwrite their predecessors. It's important to note that calling this function doesn't actually <i>send</i> any data to DevBug. Instead, it stores it to be sent.
h4 <code>breakpoint(<i>continue = false</i>, <i>name = ""</i>)</code> - send the outputted data to DevBug
p This is the magic of the operation. When this function is called, any data that has been passed to the output function will be sent to the DevBug server and stored under the configured project. There are several things you can change about this function. The <code>continue</code> parameter determines whether or not program execution continues, or if the Node.js exit method is called. The <code>name</code> parameter allows you to change the name of the breakpoint. This can be useful to help distinguish multiple breakpoints in the DevBug dashboard.
pre#editor #{ devbug.code.node }
pre#editor.inline #{ devbug.code.node }
block scripts
script(src="https://cdnjs.cloudflare.com/ajax/libs/ace/1.4.5/ace.js")

@ -6,7 +6,7 @@ block content
p This function is similar to logging data. It stores data to be outputted to DevBug. The first parameter should be a string with a brief description of the data, and the second is the data to be outputted. Note that the info string should be unique and multiple outputs with the same name will overwrite their predecessors. It's important to note that calling this function doesn't actually <i>send</i> any data to DevBug. Instead, it stores it to be sent.
h4 <code>breakpoint(<i>continue = false</i>, <i>name = ""</i>)</code> - send the outputted data to DevBug
p This is the magic of the operation. When this function is called, any data that has been passed to the output function will be sent to the DevBug server and stored under the configured project. There are several things you can change about this function. The <code>continue</code> parameter determines whether or not program execution continues, or if the PHP exit method is called. The <code>name</code> parameter allows you to change the name of the breakpoint. This can be useful to help distinguish multiple breakpoints in the DevBug dashboard.
pre#editor #{devbug.code.php}
pre#editor.inline #{devbug.code.php}
block scripts
script(src="https://cdnjs.cloudflare.com/ajax/libs/ace/1.4.5/ace.js")

Loading…
Cancel
Save