joshuag

Designme - Visually Layout Your Edit Screens - Preview

Recommended Posts

Hello!

The kind of thing I will really like to use!

  • Like 1

Share this post


Link to post
Share on other sites
1 hour ago, mel47 said:

Hello!

The kind of thing I will really like to use!

Great! I would like to finish it so I can give it to you. 

  • Like 1

Share this post


Link to post
Share on other sites

Looks very polished. Are the animations very slow or is that the video framerate? Looking great so far! 

  • Like 1

Share this post


Link to post
Share on other sites

WOW!! This looks awesome, @joshuag!! Seems very useful, especially for speed up the creation of complex templates!!

  • Like 1

Share this post


Link to post
Share on other sites
4 hours ago, Tom. said:

Looks very polished. Are the animations very slow or is that the video framerate? Looking great so far! 

it's actually super smooth in real life. I don't know why it looks all jaggy on the video ūüôā

  • Like 1

Share this post


Link to post
Share on other sites

Oh man, that looks amazing! Great times being a part of the PW Community!

  • Like 1

Share this post


Link to post
Share on other sites

Wow, I waited so long for something like this. I think this could push ProcessWire really forward. When do you plan to release? And will it be a paid module or a free one?

Thank you for creating this.

  • Like 3

Share this post


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

Wow, I waited so long for something like this. I think this could push ProcessWire really forward. When do you plan to release? And will it be a paid module or a free one?

Thank you for creating this.

It's coming along quite nicely. I do not have a firm release/completion date yet, although working towards it as fast as possible.¬†As soon as I can¬†I will answer all your questions about Designme. Hopefully by the end of this week I will be able to show you guys some more features that I didn't include in the preview video. ūüôā

  • Like 4

Share this post


Link to post
Share on other sites
On 7/8/2018 at 2:46 AM, joshuag said:

It's coming along quite nicely. I do not have a firm release/completion date yet, although working towards it as fast as possible.¬†As soon as I can¬†I will answer all your questions about Designme. Hopefully by the end of this week I will be able to show you guys some more features that I didn't include in the preview video. ūüôā

Really nice! Good Job

  • Like 1

Share this post


Link to post
Share on other sites

I've been thinking PW could do with something like this for a long time but your implementation is way better than anything I had imagined - great work! ūüėÄ

  • Like 3

Share this post


Link to post
Share on other sites
3 minutes ago, Pete said:

I've been thinking PW could do with something like this for a long time but your implementation is way better than anything I had imagined - great work! ūüėÄ

Thanks a lot. I think the biggest challenge so far has been to try to make Designme feel like a natural extension of using PW instead of an additional layer of complexity.  

  • Like 1

Share this post


Link to post
Share on other sites

Is it dynamically creating a custom template on-the-fly? Just quickly thinking how it works, though it doesn't really matter. Quite slick indeed.

Share this post


Link to post
Share on other sites

Awesome.

I also like @theo's "preview / page-grid" module a lot. I realize they don't do the same stuff, but just imagine if you had both functionalities available!

Share this post


Link to post
Share on other sites
1 hour ago, BrendonKoz said:

Is it dynamically creating a custom template on-the-fly? Just quickly thinking how it works, though it doesn't really matter. Quite slick indeed.

In this demo video, it is working from the existing 'home' template. All Ajax requests are going directly to the existing ProcessPageEdit url. there are no 'dynamic templates', but very shortly, you will have the ability to create templates on the fly from the page tree and start editing directly in Designme to speedup template/data model creation. So you can start with a completely blank template/editscreen and start throwing in fields as fast as possible. (hope this makes sense). 

  • Like 6

Share this post


Link to post
Share on other sites
1 hour ago, dragan said:

Awesome.

I also like @theo's "preview / page-grid" module a lot. I realize they don't do the same stuff, but just imagine if you had both functionalities available!

@dragan¬†&¬†@theo¬†‚Äď very interesting concept. Thanks for showing this to me, I hadn't seen it before now. I am excited to see how it evolves. visual building is always very exciting!¬†

  • Like 1

Share this post


Link to post
Share on other sites

This is 

AMAZING!!!

It will revolutionize Processwire! 

Will this be a commercial module or free of charge?

  • Like 3

Share this post


Link to post
Share on other sites
1 hour ago, dreerr said:

This is 

AMAZING!!!

It will revolutionize Processwire! 

Will this be a commercial module or free of charge?

Thanks ūüôā

I will post an update video later today or tomorrow showcasing additional features. I have not decided the best option for releasing this module, but I have some interesting ideas. 

  • Like 2

Share this post


Link to post
Share on other sites

Posted update video in the original Post. ūüôā¬†

I really value your feedback. Let me know what you think.  Thanks in advance.

  • Like 1

Share this post


Link to post
Share on other sites

Joshuag, from the videos I can tell that the work of your team is a masterpiece. It would be great to test the functionality in real whenever you are ready for a release. Keep up the good work. That is why I signed up for ProcessWire - because of its super creative and extremely supportive community.

If you need some testers, you can count on me. I am just starting a new project and a module like yours would help me get more efficient while at the same time I would make sure to report any issues spotted or share ideas of improvement (if any ofcourse ūüėȬ†)

Share this post


Link to post
Share on other sites

When removing a field from Page Edit, is the user removing that field from the associated template? Does that happen on the fly or Is there some sort of "Apply" step that happens at the end with the normal warnings about the loss of data that will occur? If it happens on the fly is there an undo feature? I'd be a bit nervous about accidentally clicking on the field remove button otherwise.

  • Like 3

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 Noel Boss
      Admin Theme Boss
      A light and clear theme based on Uikit 3
      Features
      Three unique color options Beautiful typografy using Roboto Condensed Extended breadcrumb with edit links Extends AdminThemeUikit, you can continue using all AdminThemeUikit features Option to activate theme for all users Color Variants:
      ProcessWire Blue

      Vibrant Blue

      Dark Black

      Requirements
      Requires AdminThemeUikit installed and activated.
      $config->defaultAdminTheme = 'AdminThemeUikit'; Installation
      Make sure the above requirements are met Go to “Modules > Add New“ Open “Add Module from URL“ and past the following url: https://github.com/noelboss/AdminThemeBoss/archive/master.zip Click “Download“ Click “Install“ on the “AdminThemeBoss“ Module

      Install manually
      Make sure the above requirements are met Download the theme files from¬†GitHub¬†or the¬†ProcessWire Modules Repository. Copy all of the files for this module into /site/modules/AdminThemeBoss/ Go to ‚ÄúModules > Refresh‚ÄĚ in your admin Click ‚ÄúInstall‚Äú on the ‚ÄúAdminThemeBoss‚Äú Module ¬†

    • By dreerr
      TemplateEnginePug (formally TemplateEngineJade)
       
      This module adds Pug templates to the TemplateEngineFactory. It uses https://github.com/pug-php/pug to render templates.
      doctype html html(lang='en') head meta(http-equiv='content-type', content='text/html; charset=utf-8') title= $page->title link(rel='stylesheet', type='text/css', href=$config->urls->templates . 'styles/main.css') body include header.pug h1= $page->title if $page->editable() p: a(href=$page->editURL) Edit Project on GitHub: github.com/dreerr/TemplateEnginePug
      Project in modules directory: modules.processwire.com/modules/template-engine-pug/
       
      For common problems/features/questions about the Factory, use the TemplateEngineFactory thread.
       
    • By tpr
      ProcessNetteTester
      Run Nette Tester tests within ProcessWire admin.
      (continued from here)

      Features
      AJAX interface for running Nette Tester tests, in bulk or manually display counter, error message and execution time in a table run all tests at once or launch single tests show formatted test error messages and report PHP syntax errors stop on first failed test (optional) hide passed tests (optional) display failed/total instead passed/total (optional) re-run failed tests only (optional) auto scroll (optional) include or exclude tests based on query parameters start/stop all tests with the spacebar reset one test or all tests (ctrl+click) https://modules.processwire.com/modules/process-nette-tester/
      https://github.com/rolandtoth/ProcessNetteTester
    • By bernhard
      Some of you might have followed the development of this module here: https://processwire.com/talk/topic/15524-previewdiscussion-rockdatatables/ . It is the successor of "RockDataTables" and requires RockFinder to get the data for the grid easily and efficiently. It uses the open source part of agGrid for grid rendering.
       
      WHY?
      ProcessWire is awesome for creating all kinds of custom backend applications, but where it is not so awesome in my opinion is when it comes to listing this data. Of course we have the built in page lister and we have ListerPro, but none of that solutions is capable of properly displaying large amounts of data, for example lists of revenues, aggregations, quick and easy sorts by the user, instant filter and those kind of features. RockGrid to the rescue ūüėȬ†
       
      Features/Highlights:
      100k+ rows Instant (client side) filter, search, sort (different sort based on data type, eg "lower/greater than" for numbers, "contains" for strings) extendable via plugins (available plugins at the moment: fullscreen, csv export, reload, batch-processing of data, column sum/statistics, row selection) all the agGrid features (cell renderers, cell styling, pagination, column grouping etc) vanilla javascript, backend and frontend support (though not all plugins are working on the frontend yet and I don't plan to support it as long as I don't need it myself)  
      Limitations:
      While there is an option to retrieve data via AJAX the actual processing of the grid (displaying, filtering, sorting) is done on the client side, meaning that you can get into troubles when handling really large datasets of several thousands of rows. agGrid should be one of the most performant grid options in the world (see the official example page with a 100k row example) and does a lot to prevent problems (such as virtual row rendering), but you should always have this limitation in mind as this is a major difference to the available lister options that do not have this limitation.
      Currently it only supports AdminThemeUikit and I don't plan to support any other admin theme.
       
      Download: https://gitlab.com/baumrock/RockGrid
      Installation: https://gitlab.com/baumrock/RockGrid/wikis/Installation
      Quikckstart: https://gitlab.com/baumrock/RockGrid/wikis/quickstart
      Further instructions: https://gitlab.com/baumrock/RockGrid/wikis/quickstart#further-instructions
       
      Module status: alpha, License: MIT
      Note that every installation and uninstallation sends an anonymous google analytics event to my google analytics account. If you don't want that feel free to remove the appropriate lines of code before installation/uninstallation.
       
      Contribute:
      You can contribute to the development of this and other modules or just say thank you by
      testing, reporting issues and making PRs at gitlab liking this post buying me a drink: paypal.me/baumrock/5 liking my facebook page: facebook.com/baumrock hiring me for pw work: baumrock.com  
      Support: Please note that this module might not be as easy and plug&play as many other modules. It needs a good understanding of agGrid (and JavaScript in general) and it likely needs some looks into the code to get all the options. Please understand that I can not provide free support for every request here in the forum. I try to answer all questions that might also help others or that might improve the module but for individual requests I¬†offer paid support for 60‚ā¨ per hour.
       
      Changelog
      180711 bugfix (naming issue) 180630 alpha realease  
      Use Cases / Examples:
      Colored grid cells, Icons, Links etc. The Grid also has a "batcher" feature built in that helps communicating with the server via AJAX and managing resource intensive tasks in batches:

      Filters, PW panel links and instant reload on panel close:

      You can combine the grid with a chart library like I did with the (outdated) RockDataTables module:

    • By tpr
      Update 2018-07-09: ProcessNetteTester module is available in the Modules Directory and on GitHub.

      This is a short tutorial on how to use Nette Tester with ProcessWire.
      As you will see it's very easy to setup and use and it's perfect for testing your code's functionality. With bootstrapping ProcessWire it's also possible to check the rendered markup of pages using the API, checking page properties, etc. It's also a great tool for module developers for writing better code. 
      While there will be nothing extraordinary here that you couldn't find in Tester's docs this can serve as a good starting point.
      Prerequisites: PHP 5.6+
      01 Download Tester
      Go to https://github.com/nette/tester/releases and download the latest release (currently 2.0.2). Download from the link reading "Source code (zip)". You can use composer also if you wish.
      02 Extract Tester files
      Create a new directory in your site root called "tester". Extract the zip downloaded here, so it should look like this:
      /site /tester/src /tester/tools /tester/appveyor.yml /tester/composer.json /tester/contributing.md /tester/license.md /tester/readme.md /wire ... 03 Create directory for test files
      Add a new directory in "/tester" called "tests". Tester recognizes "*.Test.php" and "*.phpt" files in the tests directory, recursively. 
      04 Create your first test
      In the "tests" directory create a new "MyTest.php" file.
      The first test is a very simple one that bootstraps ProcessWire and checks if the Home page name is "Home". This is not the smartest test but will show you the basics.
      Add this to "/tester/tests/MyTest.php":
      <?php namespace ProcessWire; use \Tester\Assert; use \Tester\DomQuery; use \Tester\TestCase; use \Tester\Environment; require __DIR__ . '/../src/bootstrap.php'; // load Tester require __DIR__ . '/../../index.php'; // bootstrap ProcessWire Environment::setup(); class MyTest extends TestCase {     // first test (step 04)     public function testHomeTitle()     {         $expected = 'Home'; // we expect the page title to be "Home"         $actual = wire('pages')->get(1)->title; // check what's the actual title Assert::equal($expected, $actual); // check whether they are equal     }     // second test will go here (step 06)     // third test will go here (step 07) } // run testing methods (new MyTest())->run(); I've added comment placeholders for the second and third tests that we will insert later.
      05 Run Tester
      Tester can be run either from the command line or from the browser. The command line output is more verbose and colored while in the browser it's plain text only (see later).
      Running from the command line
      Navigate to the "/tester" directory in your console and execute this:
      php src/tester.php -C tests This will start "/tester/src/tester.php" and runs test files from the "/tester/tests" directory. The "-C" switch tells Tester to use the system-wide php ini file, that is required here because when bootstrapping ProcessWire you may run into errors (no php.ini file is used by default). You may load another ini file with the "-c <path>" (check the docs).
      If the title of your Home page is "Home" you should see this:

      If it's for example "Cats and Dogs", you should see this:

      Running from the browser
      First we need to create a new PHP file in ProcessWire's root, let's call it "testrunner.php". This is because ProcessWire doesn't allow to run PHP files from its "site" directory.
      The following code runs two test classes and produces a legible output. IRL you should probably iterate through directories to get test files (eg. with glob()), and of course it's better not allow tests go out to production.
      <?php ini_set('html_errors', false); header('Content-type: text/plain'); echo 'Starting tests.' . PHP_EOL; echo '--------------------------' . PHP_EOL; $file = __DIR__ . '/PATH_TO/FirstTest.php'; echo basename($file) . ' '; require $file; echo '[OK]' . PHP_EOL; $file = __DIR__ . '/PATH_TO/SecondTest.php'; echo basename($file) . ' '; require $file; echo '[OK]' . PHP_EOL; echo '--------------------------' . PHP_EOL; echo 'Tests finished.'; exit; Navigate to "DOMAIN/testrunner.php" in your browser to execute the file. If every test succeeds you should get this:

      If there are failed tests the execution stops and you can read the error message. If there were more tests (eg. ThirdTest), those won't be displayed under the failed test.

      06 DOM test
      This test will check if a page with "basic-page" template has a "h1" element. We will create the page on the fly with ProcessWire's API. To keep things simple we will add the new test as a new method to our MyTest class.
      Add this block to the MyTest class:
      public function testBasicPageHeadline() {     $p = new Page();     $p->template = 'basic-page';     $html = $p->render();     $dom = DomQuery::fromHtml($html);     Assert::true($dom->has('h1')); } This will most likely be true but of course you can check for something more specific, for example "div#main". Note that we have used the DomQuery helper here (check the "use" statement on the top of the file).
      07 Custom function test
      You will probably want to make sure your custom functions/methods will work as they should so let's write a test that demonstrates this.
      I don't want to complicate things so I'll check if the built-in "pageName" sanitizer works as expected. Add this to the myTest class:
      public function testPageNameSanitizer() {     $expected = 'hello-world';     $actual = wire('sanitizer')->pageName('Hello world!', true);     Assert::equal($expected, $actual); } This should also be true. Try to change the expected value if you are eager to see a failure message.
       
      08 Next steps
      You can add more methods to the MyTest class or create new files in the "tests" directory. Check out the range of available Assertions and other features in the docs and see how they could help you writing more fail-safe code.
      Once you make a habit of writing tests you'll see how it can assist making your code more bulletproof and stable. Remember: test early, test often ūüôā
      If you find out something useful or cool with Tester make sure to share.