Jump to content
owzim

Inputfield ACE Extended

Recommended Posts

A highly configurable and flexible ACE editor input field.

This module is sponsored in part by Nibiri, aka forum member Macrura which was a great jump start. So many thanks to him. :frantics:

See this short screencast to get an overview:

Get it from Github or the Modules Directory.

Roadmap

  • add full screen mode
  • expose a jQuery api for resizing, setting row count etc.
  • add image handling like in Adam Kiss' version
Edited by Nico Knoll
Added the "module" tag and removed it from title.
  • Like 25

Share this post


Link to post
Share on other sites

Nice one Owzim! Great screencast too.

Can't wait to experiment with this.

Share this post


Link to post
Share on other sites

yeah this is so awesome - owzim's work on this goes beyond expectations!

  • Like 7

Share this post


Link to post
Share on other sites

Really looking forward to experiment with this! I always liked ACE since I use Textile a lot. I've seen the roadmap and full screen would be awesome.

Another thing you might consider is image handling. Something like this done by Adam.

Thanks and great work.

  • Like 2

Share this post


Link to post
Share on other sites

arjen, did not know of this feature, looks great. Added it to the roadmap.

To all: Feature requests and bug reports very welcome!

  • Like 2

Share this post


Link to post
Share on other sites

Nice. I can redirect everyone here now, instead of fiddling with my own :D

FYI, image upload was really really hacky, but the relevant coffee script is here:

- event: https://github.com/adamkiss/InputfieldAceEditor/blob/image-upload/_coffee/modules/editor.coffee#L50-L59

- method: https://github.com/adamkiss/InputfieldAceEditor/blob/image-upload/_coffee/modules/editor.coffee#L73-L94

  • Like 2

Share this post


Link to post
Share on other sites

looks great!

can you also render the content of your field in frontend templates with code highlighting?

Share this post


Link to post
Share on other sites

can you also render the content of your field in frontend templates with code highlighting?

Code highlighting is done by javascript, to theres no simple "echo $page->codeHighlighted". I'd also think it's better to leave the choice for a highlighting library to the user.

Share this post


Link to post
Share on other sites

@BernhardB - i think you would simply do that by using a <pre> tag and then having css to render the look you want;  You can include source code pro on your frontend for a nice mono font

Share this post


Link to post
Share on other sites

of course, but i thought maybe there's a simple way to take use of the code highlighting that comes with this module. something like

$ace = $modules->get('ace...');

<script src="<?= $ace->gethighlightjs() ?>"></script>

<div class="php">

   <?= $page->phpcode ?>

</div>

Share this post


Link to post
Share on other sites

I don't think you could use the highligher standalone, as is has to work different for a editor enviroment compared to a more-or-less static <pre> tag.

Share this post


Link to post
Share on other sites

@Bernhard

this is the exact way for your example:

https://highlightjs.org/usage/

important question would be -> have we API access to the setting of the language from the backend...so you could set easy the <pre> class for the language to show...

regards mr-fan

Share this post


Link to post
Share on other sites

Guys, this thread gave me the impulse I needed to finish an idea that I started long ago. So, here is a new module for using image fields inside textarea using the same markup language that you are using in that same text area https://github.com/ocorreiododiogo/pw-image-fields-markup

edit: still testing and work in progress, so I'm not submitting to the directory yet

  • Like 4

Share this post


Link to post
Share on other sites

fyi for anyone testing this out today, ace extended won't work if the initial field is set to collapsed only when blank..

  • Like 1

Share this post


Link to post
Share on other sites

diogo, looks great. Will try that later. Why not a separate forum post?

Share this post


Link to post
Share on other sites

diogo, looks great. Will try that later. Why not a separate forum post?

Sure, I'll do it :)

Share this post


Link to post
Share on other sites

I've added and changed a lot of things on the dev branch. It'd be cool if you guys could test the current state to spot issues I have not encountered yet, so I can call it 1.0.0, merge it into master, and then publish it to the modules directory. Thanks!

Changes, since the first post:

0.6.x - 0.12.x

  • use noconflict version of ace
  • implement possibility to add built-in extensions, by default emmet is enabled
  • apply major PHP code refactoring

0.5.x

  • enable field to be instantiated via API
  • add interval check on editor.renderer.lineHeight and only initalize everything via callback when it is available
  • add option to enable/disable localStorage
  • make advancedOptions use the the Inputfield itself, INCEPTION!

Regarding built-in extensions: They are sparsely documented, there are only two examples here. I have no idea what they all do. Some might even need additional libs, like emmet, which needs the core parser, that I included in this module.

  • Like 3

Share this post


Link to post
Share on other sites

Now you only have to convince Ryan to use this for Hanna Code, so we don't need to have two big ace installations :)

  • Like 3

Share this post


Link to post
Share on other sites

i think hanna code does need it's own version of ace, since a lot of people won't use this module;

unless it is a really simple one, i mostly do hanna codes as files on the server, so the hanna code just includes the file (thx to soma for this idea);

would be cool if i Nico's template editor module could have a setting somewhere to select the inputfield type and then one could set it to use this if it is installed;

the use cases for the backend ace editor are many though - definitely people wanting to have a markdown editor could use this... I'm also doing YAML settings field with this.

  • Like 2

Share this post


Link to post
Share on other sites

No one has complained about issues, 1.0.0 it is.

Merged into master, submitted to the directory and updated original post. I might not have the necessary time to tackle the road map for now, but if issues arise, I surely can fix them.

  • Like 1

Share this post


Link to post
Share on other sites

it's all working well here, got it on 3 live sites, and have tried various different configurations and it looks great

  • Like 1

Share this post


Link to post
Share on other sites

@Nico, been meaning to ask you if we could have your template editor check for this module installed and then have a setting or something to use ace extended for template editing; i'm actually already using this with your template editor, but i hacked your module hardcoded to use this inputfield

  • 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 MoritzLost
      This is a new module that provides a simple solution to clearing all your cache layers at once, and an extensible interface to perform various cache-related actions.
      The simple motivation behind this module was that I was tired of manually clearing caches in several places after deploying a change on a live site. The basic purpose of this module is a simple Clear all caches link in the Setup menu which clears out all caches, no matter where they hide. You can customize what exactly the module does through it's configuration menu:
      Expire or delete all cache entries in the database, or selectively clear caches by namespace ($cache API) Clear the the template render cache. Clear out specific folders inside your site's cache directory (/site/assets/cache) Refresh version strings for static assets to bust client-side browser caches (this requires some setup, see the full documentation for details). This is the basic function of the module. However, you can also add different cache management action through the API and execute them through the module's interface. For this advanced usage, the module provides:
      An interface to see all available cache actions and execute them. A system log and logging output on the module page to see verify what the module is doing. A CacheControlTools class with utility functions to clear out different caches. An API to add cache actions, execute them programmatically and even modify the default action. Permission management, allowing you granular control over which user roles can execute which actions. The complete documentation can be found in the module's README.
      Beta release
      Note that I consider this a Beta release. Since the module is relatively aggressive in deleting some caches, I would advise you to install in on a test environment before using it on a live site.
      Let me know if you're getting any errors, have trouble using the module or if you have suggestions for improvement!
      In particular, can someone let me know if this module causes any problems with the ProCache module? I don't own or use it, so I can't check. As far as I can tell, ProCache uses a folder inside the cache directory to cache static pages, so my module should be able to clear the ProCache site cache as well, I'd appreciate it if someone can test that for me.
      Future plans
      If there is some interest in this, I plan to expand this to a more general cache management solution. I particular, I would like to add additional cache actions. Some ideas that came to mind:
      Warming up the template render cache for publicly accessible pages. Removing all active user sessions. Let me know if you have more suggestions!
      Links
      https://github.com/MoritzLost/ProcessCacheControl ProcessCacheControl in the Module directory

    • By joshua
      This module is (yet another) way for implementing a cookie management solution.
      Of course there are several other possibilities:
      - https://processwire.com/talk/topic/22920-klaro-cookie-consent-manager/
      - https://github.com/webmanufaktur/CookieManagementBanner
      - https://github.com/johannesdachsel/cookiemonster
      - https://www.oiljs.org/
      - ... and so on ...
      In this module you can configure which kind of cookie categories you want to manage:

      You can also enable the support for respecting the Do-Not-Track (DNT) header to don't annoy users, who already decided for all their browsing experience.
      Currently there are four possible cookie groups:
      - Necessary (always enabled)
      - Statistics
      - Marketing
      - External Media
      All groups can be renamed, so feel free to use other cookie group names. I just haven't found a way to implement a "repeater like" field as configurable module field ...
      When you want to load specific scripts ( like Google Analytics, Google Maps, ...) only after the user's content to this specific category of cookies, just use the following script syntax:
      <script type="optin" data-type="text/javascript" data-category="statistics" data-src="/path/to/your/statistic/script.js"></script> <script type="optin" data-type="text/javascript" data-category="marketing" data-src="/path/to/your/mareketing/script.js"></script> <script type="optin" data-type="text/javascript" data-category="external_media" data-src="/path/to/your/external-media/script.js"></script> <script type="optin" data-type="text/javascript" data-category="marketing">console.log("Inline scripts are also working!");</script> The type has to be "optin" to get recognized by PrivacyWire, the data-attributes are giving hints, how the script shall be loaded, if the data-category is within the cookie consents of the user. These scripts are loaded asynchronously after the user made the decision.
      If you want to give the users the possibility to change their consent, you can use the following Textformatter:
      [[privacywire-choose-cookies]] It's planned to add also other Textformatters to opt-out of specific cookie groups or delete the whole consent cookie.
      You can also add a custom link to output the banner again with a link / button with following class:
      <a href="#" class="privacywire-show-options">Show Cookie Options</a> <button class="privacywire-show-options">Show Cookie Options</button> This module is still in development, but we already use it on several production websites.
      You find it here: https://github.com/blaueQuelle/privacywire/tree/master
      Download: https://github.com/blaueQuelle/privacywire/archive/master.zip
      I would love to hear your feedback 🙂
      Edit: Updated URLs to master tree of git repo
       
    • By David Karich
      Admin Page Tree Multiple Sorting
      ClassName: ProcessPageListMultipleSorting
      Extend the ordinary sort of children of a template in the admin page tree with multiple properties. For each template, you can define your own rule. Write each template (template-name) in a row, followed by a colon and then the additional field names for sorting.
      Example: All children of the template "blog" to be sorted in descending order according to the date of creation, then descending by modification date, and then by title. Type:
      blog: -created, -modified, title  Installation
      Copy the files for this module to /site/modules/ProcessPageListMultipleSorting/ In admin: Modules > Check for new modules. Install Module "Admin Page Tree Multible Sorting". Alternative in ProcessWire 2.4+
      Login to ProcessWire backend and go to Modules Click tab "New" and enter Module Class Name: "ProcessPageListMultipleSorting" Click "Download and Install"   Compatibility   I have currently tested the module only under PW 2.6+, but think that it works on older versions too. Maybe someone can give a feedback.     Download   PW-Repo: http://modules.processwire.com/modules/process-page-list-multiple-sorting/ GitHub: https://github.com/FlipZoomMedia/Processwire-ProcessPageListMultipleSorting     I hope someone can use the module. Have fun and best regards, David
    • By dimitrios
      Hello,
      this module can publish content of a Processwire page on a Facebook page, triggered by saving the Processwire page.
      To set it up, configure the module with a Facebook app ID, secret and a Page ID. Following is additional configuration on Facebook for developers:
      Minimum Required Facebook App configuration:
      on Settings -> Basics, provide the App Domains, provide the Site URL, on Settings -> Advanced, set the API version (has been tested up to v3.3), add Product: Facebook Login, on Facebook Login -> Settings, set Client OAuth Login: Yes, set Web OAuth Login: Yes, set Enforce HTTPS: Yes, add "https://www.example.com/processwire/page/" to field Valid OAuth Redirect URIs. This module is configurable as follows:
      Templates: posts can take place only for pages with the defined templates. On/Off switch: specify a checkbox field that will not allow the post if checked. Specify a message and/or an image for the post.
      Usage
      edit the desired PW page and save; it will post right after the initial Facebook log in and permission granting. After that, an access token is kept.
       
      Download
      PW module directory: http://modules.processwire.com/modules/auto-fb-post/ Github: https://github.com/kastrind/AutoFbPost   Note: Facebook SDK for PHP is utilized.


×
×
  • Create New...