Ivan Gretsky

@teppo, just in case you are in doubt what is that what you can gift to the world this New Year, I am quite sure the world will be delighted with the new Wireframe version with themes support)) Well, maybe not the whole world, but certainly some minor parts of it))) I do not know how do to say "happy upcoming New Year" in English or Suomi, so I'll put it here in Russian: "С наступающим!"

The only one that comes to my mind is User Activity of ProDevTools suite. This is of course a Pro module, but it is the only one of the kind that I have worked with. I hope I understood right what you have been asking about)

I have done this. Hope it will get some more deserved attention to PW. And this post is supposed to bring this pinned topic up in the recently updated list for those who, like myself, read the news there. And to get some more ⭐⭐⭐⭐⭐ for us on github)

Good day, @kongondo! Have you managed to get it to work? P.S. I have managed to make it work both for web and cli. The only thing that I still cannot figure out is how to launch a specific php file (see an example without ddev below). Still can't find out how to start it not with php but with ddev exec php. { "name": "Launch test.php", "type": "php", "request": "launch", "program": "${workspaceFolder}/test.php", "cwd": "${workspaceFolder}", "port": 0, "runtimeArgs": [ "-dxdebug.start_with_request=yes" ], "env": { "XDEBUG_MODE": "debug,develop", "XDEBUG_CONFIG": "client_port=${port}" } } I have tries adding "runtimeExecutable": "ddev exec php", but it didn't work for some reason: Error: spawn ddev exec php ENOENT at ChildProcess._handle.onexit (node:internal/child_process:285:19) at onErrorNT (node:internal/child_process:483:16) at process.processTicksAndRejections (node:internal/process/task_queues:82:21) { errno: -2, code: 'ENOENT', syscall: 'spawn ddev exec php', path: 'ddev exec php', spawnargs: [ '-dxdebug.start_with_request=yes', '...', '...' ] }

Thanks for an interesting perspective and for the commendation @Alexander! As you already mentioned your new open source thing, expand on it for everybody. We are in the Pub anyway))

Ok. Now I got it better, I think. Now I have _init.php prepending wireframe.php that generates settings array, that I then pass to wireframe->render(). Some absolutely general settings I pass down with setting() function. If we had composers, we could move all my code in _init.php and wireframe.php to a dedicated class. Where would these composers be in places if file structure? How would we access data from them in views?

(Deleted)

Great! Looking forward to see it in Wireframe! Thanks for your work and talent!

Yes. But I think there could be an option to either use parent's features or to indicate that this one is yet to be implemented in a theme (through an error or warning).

I mean pull request in the module repo - https://github.com/kongondo/MenuBuilder/pulls Thanks for the code! I've seen it. But didn't try yet. A github pull request is just an easier way to deal with code change proposals.

Great! Did you create a PR, so we can like it and make it easier for @kongondo to fix this for all of us?

Good day @teppo! Another question from me) I am building a solution based on PW and Wireframe, that needs the theming functionality. That is switching theme (default views) for all the views and components. Layouts and partials probably too. Is there an easy way to achieve this with current code? Maybe a couple of hooks? I can see two ways how it could work. Put `alternative-default.php` everywhere the `default.php` files are and somehow tell Wireframe to use those prefixed files. If there is another view except the default one, the prefix should work as well. Like `alternative-json.php`. Probably an option should be available whether to fallback to defaults without the prefix or not. Create an overrides or theme folder somewhere and have somehow point Wireframe to use views from there. For my personal need the 1st approach seems to be a better one. But just maybe it is easy enough to provide possibility for both? Thanks!

Thanks for sharing. I am still wrapping my head around the concept. I it passing variables to a specific view... seems like it. But I am not sure I quite understand what problem does it solve. If you would like to discuss it, a real-world example would help)

How are you doing, @kongondo! Your module is a blast! Still finding some really cool ways to use it to control how menus could be controlled from the admin. The thing that really worries me is that the module seems to be not fully compatible with newer versions of php. https://github.com/kongondo/MenuBuilder/issues/48 https://github.com/kongondo/MenuBuilder/issues/54 Is there a chance you could find some time to upgrade it anytime soon? Or are you willing to accept PRs with fixes? I can see one that is not dealt with yet, so curious if me or someone else should try to come up with solutions with compatibility problems? Thanks!

Good day, @Robin S! Thanks for the module! I've used it with a great pleasure on my single-language sites. But now I need to set things up for the ML site. How would you suggest to do that? I think I would need both language-dependant labels AND urls. Is it better to handle this with hooks, or there could be a way to do it from the UI?

They need to get us used to some more obscure syntax before they introduce the next logical step - mandatory compilation. So be happy they are boiling the frog slowly and we still have a few more happy years just scripting.

Good day @teppo! How is it going? I am using Wireframe as a basis for almost all sites I work with. So really hope you're doing fine) Are there any new great plans for this module? There is a function to create Wireframe folder structure from admin. I was wondering could it be done via API? Need this for a setup script. I know it is not hard to create folders in cli, but a one liner using API would be just neat.

Hey @olivetree! You can use Remote development plugin for VS Code. This way you can work on your staging (or prod if you like cowbow coding)) from a locally installed VS Code via ssh. It install VS Code server on a remote machine and connects to it. So you do not need to have anything but VS Code locally. There is similar thing in PhpStorm I know nothing more about)

In case you really need to build tailwindcss without node and running npm install for whatever reason you can use this https://tailwindcss.com/blog/standalone-cli. Just download a binary, put it somewhere and call with proper arguments. To make it easy in VS Code create a task.

Thanks for a great explanation (as always). I guessed almost everything) I also place the source scss/js in templates/static. Before that I used to put the sources in site/static-src and put the generated files in templates/static. I guess, resources could be a better name for the sources. At least it is a standard place to have them as I use Wireframe (and love it).

So I am here thinking about this again, @teppo. Didn't find an explanation anywhere still. Could you please explain your idea behind those folders?

Hi! 'columnWidth' should do that. You can look up these here.

Glad you're having a good time on our continent, Ryan! Nice choice! It is so cool you are about to celebrate your first half of a century! Seems like you're having a great life so far. But you didn't have all those 50 years to work on PW pitifully, as you had to spend time on childhood and etcetera. Your next half centuries you won't have this excuse))) So waiting for the things to come! Congratulations to @Robin S! Your modules really make the ecosystem a place to thrive! Thank you!

It seems that you're seeing the main problem in those plants' pages presentation in admin. You do not want to see all those 10 thousand pages in a tree. I can relate to that. One possible solution would be to use Page Lister. This way you would see all those pages in a list no matter where they are in a tree. You would be able to search those pages by any their fields. Basic version is included in the core (see the screenshot below). A more powerful Pro version is a cool thing to have though and 100% worth its money. You can still have the pages in the tree hierarchy, or have all the plants under one common parent and linked to categories via page reference fields.

Good day @horst! I've tried to fix the issue, bit with no luck. Did you have a chance to look into it? For now I will try some another module. Maybe it will fix the issue in this case. Or if it doesn't we will know the problem is elsewhere.