Jump to content

Martijn Geerts

PW-Moderators
  • Posts

    2,769
  • Joined

  • Last visited

  • Days Won

    31

Everything posted by Martijn Geerts

  1. Add fields to the user template. In the templates, filter options, show system templates.
  2. I like this approach. Thank you for sharing !
  3. +3 for making it core.
  4. There's also a highres if the upload is HD and Youtube has processed the video. But you need to check, before using. My experience is that YouTube doesn't always provide every image. If the image is not available, google gives a smaller image back then expected.
  5. You're welcome. For me building tables is always time consuming.
  6. Started a new module for creating <tables> from repeater fields. Feel free to grab it from github, do with it what you want. It only works for simple text based fields inside a repeater. To use it: $table = $modules->get("RepeaterTable"); // initialize $table->thead = true; // (bool) true/false, default = true, will render <th> $table->indent = 3; // (mixed) false/int, where int is the level of indentation, default: false $table = $table->render($page->repeater); // repeaterfield called repeater <!-- output --> <table class="table-repeater"> <thead> <tr> <th class="col-1">Fieldlabel field 1</th> <th class="col-2">Fieldlabel field 2</th> <th class="col-3">Fieldlabel field 3</th> </tr> </thead> <tbody> <tr class="row-1"> <td class="col-1">data for field 1, first repeater item</td> <td class="col-2">data for field 2, first repeater item</td> <td class="col-3">data for field 3, first repeater item</td> </tr> <tr class="row-2"> <td class="col-1">data for field 1, second repeater item</td> <td class="col-2">data for field 2, second repeater item</td> <td class="col-3">data for field 3, second repeater item</td> </tr> </tbody> </table> For the HTML purist, I have added source code indentation where you can set how many tabs you wish to append before each element. Please let me know if I should add this to the modules directory ? Does someone have a good name for this ?
  7. Vote for core, count is 2. Or 3 when I count adrian in.
  8. From that point of view you're right. But I think there are more people then me that always use the HelperFields, no exception. Essentially wished that Ryan will make it core and integrate it better. LIke he has done it with your terrific Language Labels. Still big thanks for that ! <adam>I'm probably missing something based on how confusing I find your last sentence...</adam> The last sentence is a mystery (for most), that was the intension.
  9. I'm by far not an expert at this. But it seems to me that memory limit should at least double your 90Mb. Next to that max_input_time is way to less if you asked me. Our internet connection is not that great. It would take 12 minutes (720 seconds) for us to upload 90Mb if there's no interuption
  10. Can you specify the settings you've done?
  11. Martijn Geerts

    Admin Theme

    'If' Ryan updates the default PW theme, it would be nice that Soma's Helper Field Links was better integrated . I get the warm feeling that I have the Classical love !
  12. If you've had your 10 aha moments, you're gonna realize that even the sky is not a limit anymore.
  13. I read your post several times, but don't understand what you want to achieve.
  14. Took me awhile to understand pocket grid. But instantly get it while looking at the source.
  15. Not sure about the limited browser support. I thought back in the days 56k they told better to use progressive. As it give the the feeling that it loads quicker. ( below some info from wikipedia ) These days, we want to give more more control back to CSS. Old lightbox scripts, first load the whole image, then presenting them to the screen with animation. What I see happen now a days ( more & more ) other of lightbox scripts appear. The animation delivered bij CSS & not by Javascript. And images appear on the screen directly. ( after first byte is loaded ) see magnific lightbox for example. Progressive loading is way nicer then. For mobile progressive is ideal. ---- wikipedia compression : There is also an interlaced "Progressive JPEG" format, in which data is compressed in multiple passes of progressively higher detail. This is ideal for large images that will be displayed while downloading over a slow connection, allowing a reasonable preview after receiving only a portion of the data. However, support for Progressive JPEGs is not universal; when Progressive JPEGs are received by programs that do not support them (such as versions of Internet Explorer before Windows 7)[13] the software only displays the image after it has been completely downloaded. --- Interresting read @horst. Still have to think about it. To be continued !
  16. I wish there was support for progressive JPEG. To control it, set it in the imageSizerOptions array.
  17. @SiNNuT, didn't seen your post about PURE, sorry. A big advantage with PURE is that I can choose which box-sizing model I want. The next project will be content-box.
  18. Last week I found a CSS framework called pure. Although there are plenty of good CSS framework out there, but sometimes those frameworks have just to much. Pure on the other hand is a small collection of css files. I like this approach, think I gonna use it in the next project. Base 1.2KB, Grids 0.9KB, Forms 1.4KB, Buttons 0.8KB, Tables 0.5KB, Menus 1.2KB Take a look: PURE
  19. yep. So name is always unique in a parent to.
  20. Next to this, wrapping block elements in links, can reduce markup, create a bigger click area & you get a styleable container for free This is great!
  21. Please re read kongondo's post. There's everything you need.
  22. Log in in with email address has more overhead so shouldn't be default. Please let the system as it is. ( think ryan won't change it, cause it makes sense ) If your needs for the login with email is that high, write a module for it that hooks in. ( Session authenticate ( not shure about this hook ) ) side note: There are a lot of developers to overcomplicate scripts. (count my self in) Ryan is the gatekeeper of no overhead & simplicity. let it be this way, please
  23. The user is actually a page. This makes him/her unique by default. (no need for scripting) You could log-in users with their email address, but email address is not unique by default. (it needs some scripting) I could be: "martijn (role editor) martijn@domain.nl", but also "admin (role superuser) martijn@domain.nl" Search the forum for login with email and you will find good answers. (use google)
  24. HTML5 specs are different. In HTML5 it's allowed to wrap block level elements with links. this is valid: <a href='/link/to/page.html'> <div> <h1>I'm</h1> <p>Allowed</p> </div> </a>
  25. The multi language input can get very easy out of sync when the list of added children is long. I think when you're building a multi language site it's saver to to just foreach the already created list (childpages) with custom code and provide for every (each) translation a input field. ( easy the write from your template ) I love the module how it is now. I think you shouldn't overcomplicate it. <adrian>PS Excuse the dodgy google translations</adrian> I google it all the time, I can't even write
×
×
  • Create New...