Jump to content
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 5

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 😉 )

  • Like 1

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 4

Share this post


Link to post
Share on other sites
11 hours ago, MilenKo said:

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 😉 )

OK, in the next few days I will send you a copy. Thanks! 🙂

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 jploch
      Hey folks,
      for a module (a pagebuilder based on PageTable) I need to save some settings as JSON. The values are saved for each page table item (a pw page). It's working well, but I am looking for ways to improve the structure I have. As I'm not that experienced with JSON, maybe someone more experienced can take a look and tell me if my approach is good practice. 

      My goal is to make all the items accessible by page id, without looping over them (using objects instead of arrays):
      // access from template with pw page var $jsonObject->items->{$page}->cssClass; Her is an example of my JSON structure:
      { "items": { "3252": { "id": "3252", "cssClass": "pgrid-main", "breakpoints": { "base": { "css": { "grid-column-end": "auto", "grid-row-end": "auto", "grid-column-start": "auto", "grid-row-start": "auto", "align-self": "auto", "z-index": "auto", "padding-left": "60px", "padding-right": "60px", "padding-top": "60px", "padding-bottom": "60px", "background-color": "rgb(255, 255, 255)", "color": "rgb(0, 0, 0)" }, "size": "@media (min-width: 576px)", "name": "base" } } }, "3686": { "id": "3686", "cssClass": "test_global", "breakpoints": { "base": { "css": { "grid-column-end": "-1", "grid-row-end": "span 1", "grid-column-start": "1", "grid-row-start": "auto", "align-self": "auto", "z-index": "auto", "padding-left": "0px", "padding-right": "0px", "padding-top": "0px", "padding-bottom": "0px", "background-color": "rgba(0, 0, 0, 0)", "color": "rgb(0, 0, 0)" }, "size": "@media (min-width: 576px)", "name": "base" } } }, "3687": { "id": "3687", "cssClass": "block_editor-3687", "breakpoints": { "base": { "css": { "grid-column-end": "span 2", "grid-row-end": "span 1", "grid-column-start": "auto", "grid-row-start": "auto", "align-self": "auto", "z-index": "auto", "padding-left": "0px", "padding-right": "0px", "padding-top": "0px", "padding-bottom": "0px", "background-color": "rgba(0, 0, 0, 0)", "color": "rgb(0, 0, 0)" }, "size": "@media (min-width: 576px)", "name": "base" } } }, "3696": { "id": "3696", "cssClass": "block_editor-3696", "breakpoints": { "base": { "css": { "grid-column-end": "span 2", "grid-row-end": "span 1", "grid-column-start": "auto", "grid-row-start": "auto", "align-self": "auto", "z-index": "auto", "padding-left": "0px", "padding-right": "0px", "padding-top": "0px", "padding-bottom": "0px", "background-color": "rgba(0, 0, 0, 0)", "color": "rgb(0, 0, 0)" }, "size": "@media (min-width: 576px)", "name": "base" } } } }, "breakpointActive": "base", "breakpointActiveSize": "@media (min-width: 576px)" }  
    • By jploch
      Fieldtype Page Table Grid
      This is a sneak preview of a side project I've been working on for quite some time now. A lot of work and thought has gone into this, so I will most likely release this as a commercial module at some point in the near future. 

      As a designer (and developer) I get the appeal of a WYSIWYG editor. After playing around with some WYSIWYG page builder tools, I always felt something was wrong about them. So I decided to build my own PW version based on PageTable.

      Here is a small demo (using AdminThemeCanvas, but its working with other admin themes as well) :
      There is also a complete website that I built for a friend of mine using this module and some custom blocks.
      Concept
      This fieldtype shares a lot of features with PageTableExtended: it's also an extension of PageTable and renders the block templates in the backend and frontend (native PW templates and fields). You can also add your own css via module settings.
      The difference is, this fieldtype also gives you the ability to rearrange and resize elements in a visual way as well as enable inline editing for text, ckeditor and file fields. Similar (and promising) attempts have been made, but I wanted something based on native CSS grid instead of a CSS framework...so I built my own version. Most CSS frameworks are based on flexbox, which is great for layouting elements horizontally. With CSS grid, you can place elements horizontally and vertically, allowing for layouts that were not previously possible with CSS. Similar to webflow, this fieldtype uses javascript (in the backend) to let you manipulate CSS grid in a visual way to design fully responsive websites (or parts of them). It should still be possible to include a CSS framework if you like (just add the classes to your block markup and include the CSS via module settings).
      The CSS grid layout manipulations are saved in a single field as a JSON array and used to generate a dynamic stylesheet that you simply include in your main template (no inline styles). The styles are saved within the breakpoint you select and cascade down to smaller breakpoints. That means you can specify just the basic breakpoint and adjust other breakpoints if needed. The exception is the mobile breakpoint which will display everything in one column as a default (you can change the layout here too).
      The fieldtype also comes with an optional style panel to manipulate some additional CSS properties directly on the page. You can customize the panel or disable it completely from the module settings (and just use a CSS file that you include via module settings). The style panel is based on inputfields (nothing is saved to the database). This means that you just have to install the module and all fields are available to all blocks automatically (this can be customized). It also has the benefit that your installation is not flooded with fields; this module only installs one field.
      Don't want to give your customer all that power? Design features can be disabled for certain roles. The grid editor role can just edit the content and use the inline editing feature to edit content quickly. You can then also grant access individually to the style panel, resize or drag functionality.
      Features
      Blocks are just pages Blocks are defined by native PW templates and fields Manipulate CSS grid in a visual way to design fully responsive websites (or parts of them) Design features can be disabled for certain roles Inline editing of text, ckeditor and file fields The layout is 100% CSS grid (very small css file size) Simply drag and resize to manipulate grid items directly inside the backend Manipulate grid columns and rows directly on the page (use any number of columns you want) All style manipulations are saved as JSON and used to generate a dynamic stylesheet that you just include in your main template (no inline styles) Nested groups/grids (child pages of nested blocks are created under group parent) Global blocks work with page reference field (changes on one page, changes all blocks on all pages) Manual and auto placement of grid items Define custom icons for your blocks via native template settings (template -> advanced -> icon) Option to load lazysizes in the backend to enable lazy loading of assets with class lazyload Works with all default and ui-kit based admin themes If you have any questions or feedback, let me know.
    • By bernhard
      I built this module because I needed a versatile solution to replace tags and simple if-blocks in some E-Mails and PDF documents.
      If you only need to replace static tags (no if-conditions), then you can use default PW api and need no module:
      $str = "My favourite color is {color}."; $texttools = $sanitizer->getTextTools(); echo $texttools->populatePlaceholders($str, ['color' => 'red']); // output: My favourite color is red. Usage:
      See the two example Files in the folder /replacements

       
      Methods:
      replacementsTable()
      Renders an overview of all available replacements (see the example in the Module's config file:
       
      Create new Replacements:
      Simply copy the sample file and adopt to your needs.
       
      Download:
      https://gitlab.com/baumrock/RockReplacer
    • By bernhard
      DEPRECATED
      I'm using this module in several projects, but it will likely not see any updates in the future. I'm not happy with it and I'm looking for ways to develop better solutions. RockTabulator was my first try, but I'm also not 100% happy with that. The tabulator library is great, but my module implementation is not. I hope to get a good solution soon, but it will be a lot of work...
      ---
      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/FieldtypeRockGrid
      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
      German Translation File: site--modules--fieldtyperockgrid--fieldtyperockgrid-module-php.json
      Changelog: https://gitlab.com/baumrock/FieldtypeRockGrid/raw/master/changelog.md
       
      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 (please contact me via PM).
       
      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 Paul Greinke
      Hi there. I wrote a custom module for one of my projects. In fact I maybe want to use my module in other projects too. In order to be variable and customizable  I need to implement some custom hooks into my module. So I can afterwards hook into the my functions in order to modify them to match the needs of the new project.
      I tried simply defining functions with the '__' prefix. But that did not work. I'm imagining something like the following:
      <?php class MyClass { public function ___someFunction() { // Do something } } // ready.php $this->addHookBefore('MyClass::someFunction', function($event) { // some customization }); Is there a way to accomplish that? 
×
×
  • Create New...