Jump to content

kongondo

PW-Moderators
  • Posts

    7,374
  • Joined

  • Last visited

  • Days Won

    139

Everything posted by kongondo

  1. Hi @Spinbox, Just acknowledging that I have seen this. I'll get back to you with a detailed answer. There's various ways to approach this (all easy πŸ˜ƒ).
  2. @Spinbox You are the boss πŸ˜„! Thank you so much for the detailed response! I've heard great things about the C2. This guy has some helpful tips on screen splitting (PowerToys FancyZones, Aquasnap and Groupy). Was 2x 1080p your previous setup? Thanks again for the detailed answers!
  3. Hi @sebibu, Yes. I am hoping to do so soon πŸ˜ƒ. I'll post an update later this week. Yes, sorry, this (see bit about shop):
  4. https://www.cognition-labs.com/introducing-devin Well I guess that's it then. It was nice riding with you folks. I am out...πŸ˜’ Oh, wait a minute. There's still hope. I just need to learn ML... πŸ˜ƒ
  5. Thanks for looking into this. Looks like they gave a response for an 8K TV πŸ˜„.
  6. Thanks. It was one of the first ones I watched πŸ˜„. I've watched at least a dozen, maybe more. I have watched some that are like a series...now, 6 months later, 2 years, later, etc! Some people have gone back to PC monitors, others have stuck it out, others have gone for smaller TVs, etc. Like you said, there's quite a lot of factors to take into account as well as end use of the thing. Gamers, for instance, seem to like the LG C series a lot.
  7. Anyone using a 4K TV as a computer monitor? What has your experience been? Primary use would be coding and video editing (not gaming or graphics or for smart TV features). 43 inch, maybe LED or QLED (not OLED). What I've found out so far: Distance from screen! Anything bigger than 50 inch is asking for trouble (ergonomics). QLED best for bright rooms. OLED best for darker rooms but... OLED burn-in! and pricey! Eye strain + possible headaches (see #1). Refresh rate (not important for coding?). Auto dimming. Font aliasing (reverse RGB to BGR if possible). One big screen might be better than two smaller ones (central focal point) - YMMV! Thoughts? Thanks.
  8. Hi everyone. Padloper 009 is ready! The release has been delayed by issues with my site. It is currently offline as I work on upgrading it. I hit a number of issues which I am currently resolving. I am hoping this won't extend beyond two weeks. I request your patience please, thanks. Best.
  9. November 2023 (version 1.85) Floating editor windows Finally this πŸ‘†!
  10. Working on the installer (to handle the new features). I'm hoping to finish by next week and release 009 beta. Hopefully we are in for a Christmas treat πŸ˜„.
  11. Hi @alexm, Sorry, I saw this late. Yes, that's the easiest way to do do it. You could also have done this programmatically but much easier at the DB level especially if you don't have many line items. A third way would have been to recreate the whole order manually in the backend using Padloper but this would have meant creating a new order. As you have found out the hard way, manual order creation and frontend orders are not compatible (for now) πŸ˜€.
  12. I didn't know this! Where does this code go, ready.php or init.php? Or in config.php?
  13. No worries πŸ™‚. I didn't for once consider it that way πŸ˜„. Everything you said was spot on and constructive. I am just frustrated at myself that I have not been able to bring the docs to a reasonable standard (yet). I take your point and will consider this. My plan has been to make short (5 minutes maximum) video. Thanks.
  14. Hi @joe_g, Apologies for the very late reply. I have been away. First, thanks for your continued interest in Padloper despite the difficulties you have previously encountered. The docs are still not great, sorry. I am currently working on releasing version 009 of Padloper after which I'll introduce a soft feature freeze and solely focus on working on documentation and bug fixes. I decided to focus on video documentation rather than written ones at the moment. You are right. I focused on using htmx since that was the easiest way I could illustrate how to build a shop using ajax. It was my intention to quickly follow this up with other examples using jQuery and non-ajax examples. Apologies that I never got round to this but my plan for the video documentation is to start from scratch with very simple examples, first without ajax, then with ajax and subsequently cover more advanced techniques. I take full responsibility for this misconception. Padloper does not produce any markup except for a checkout form which you don't have to use. Perhaps my (complicated) htmx examples created the impression that the markup was coming from Padloper. Padloper closely aligns with the ProcessWire approach; it gets out of your way but is always on hand to assist you with its powerful API. I don't know what your timescales are but I think this would be a great opportunity to learn how to use Padloper's API. I know the video docs are not ready but perhaps your project could help shape my video documentation? Please let me know. Thanks.
  15. Hi @gornycreative, I have been away so just picking up messages now. Thanks for your interest in Dynamic Selects. I'll respond to your questions ASAP. There might be a delay as I settle in after a long absence, thanks.
  16. Hi @MrSnoozles, all. Sorry I have been awfully quiet. I have been very busy with a number of projects. This has caused a delay regarding MM Next work. I am going to be away this week for about 2 weeks without access to the internet. This will quieten down a bit then with the other projects and I'll be able to continue with MM Next. Apologies for this!
  17. Hi both, Actually, this was supposed to be last week! I was hoping to release version 009 of Padloper which is packed with a number of new features including discounts but life got in the way! I am now going to be unavailable from this week for a number of weeks (at least 2) without access to internet. Hope to finish this quickly when I get back. Nice work all the same!
  18. Hi @ank, Sorry I missed this! Currently we use the ProcessWire Lister inbuilt InputfieldSelector. This is on my TODO list to make more intuitive and at least relevant to the current view (products, orders, etc). Screenshots Add filters Select sort Select sort criteria Doe this work for you for now? Thanks.
  19. Hi @Guido, Glad you are enjoying Padloper! πŸ˜€ Can't wait to see the showcase πŸ˜€. Apologies again for the delay in getting back to you. I'll have a think about how best to achieve this and get back to you by tomorrow. There is a new version of Padloper coming soon, hopefully in a fortnight or 3 weeks. It has more order statuses as well as other stuff. I'll base my solution on this latest version of Padloper. This means, if you don't mind, I might request you to please test the solution on the latest Padloper (beta) which I'd send to you separately before releasing to all users. I hope this is OK. Thanks.
  20. Floating Windows Long standing open request https://github.com/microsoft/vscode/issues/10121 Workarounds: Duplicate Workspace WARNING: CAREFUL WITH THIS ONE! CAN EASILY WIPE YOUR CHANGES IF YOU ARE EDITING ON BOTH WINDOWS! Autosave onFocusChange
  21. Hi @thibaultvdb, Thanks for your interest in Padloper 2. I have moved your question to its own topic. Yes, it should be possible to do this with Padloper 2, although the feature is not available out of the box. There are at least two approaches I can think off. Let me sleep on it. I'll give you a better response tomorrow. Thanks.
  22. Hi @ank, Apologies for the late response. Below are examples of 'add to cart' buttons without page reload. Ajax is used to submit the request and handle the response from the server. There are two examples: jQuery ajax Vanilla JavaScript ajax In both cases, the server (Padloper) returns a JSON response. This is unlike in htmx in which case the server will return markup as the response. Hence, in the examples below, we need to handle the response ourselves. I have given some examples but you can choose to handle the response however you wish. The most important thing is the submission aspect of the code, i.e. what form inputs you send to the server. I'll explain these below before I get to the examples. In future, I will add the examples below to the demos repository. I will also be adding the explanations below to the docs. Add to Cart Endpoint You need to send a POST request to the address /padloper/add/. Padloper listens to requests sent there using URL Hooks. INPUTS Required Product ID (integer) Your request must contain the ID of the product you want to add to the cart. Please note that this applies to both a product without variants or a variant. I.e., in case of a variant, you only need to send its ID. Its ID will be its product ID. The input name must be: product_id Optional Quantity (integer) This tells Padloper how many of the given product/product variant to add to the cart. If this is not specified, it defaults to 1 item. The input name must be: padloper_cart_add_product_quantity Redirect Page (string | integer) This is only applicable for non-ajax requests! This tells Padloper where to redirect the user to after they add an item to the cart. It is useful in cases such as 'add to cart and checkout'. The value can be a string representing the URL to redirect to or a page ID whose URL to redirect to. The input name must be: padloper_cart_redirect EXAMPLES Notes These examples assume you are using a delayed output template strategy. Otherwise, if using a direct output you just need to echo $content. Please also note that form markup can be added to any page. You don't need a special page to add an item to the cart. Padloper products pages live under the admin hence cannot be accessed directly from the frontend. One way to show a product in the frontend is to access it via a URL Segment, e.g. /products/my-nice-product/ OR /products/1234/ where 1234 is the ID of the product. You can then use $padloper->get("id=1234") OR $padloper->get("name=my-nice-product, template=product"). We are using Tailwind CSS in our examples. For the jQuery example, you will need to link to jQuery script somewhere in your <head> or <body>. In this examples, we don't show how to use the values in the JSON in the server response. They are self-explanatory though. If not, let me know. The JavaScript handlers code was not thoroughly tested. They are intended as a quick illustration. jQuery Example Template File (PHP) JavaScript Vanilla JavaScript Example Template File (PHP) JavaScript Server Response { "productId": 1895, "variationId": 0, "productTitle": "Printed Ghanain Skirt", "quantity": 1, "totalQty": 85, "numberOfTitles": 5, "totalAmount": "\u00a313,425.45" } Please note that the variationId is a legacy response value that is no longer needed in Padloper. It will be removed in the next release. Screenshots Please note that in my testing, I combined the code for jQuery and Vanilla JavaScript into one template file. Demo Product Page Dev Console: Ajax Request Dev Console: Ajax Response Hope this helps. Otherwise, give us a shout. Cheers
  23. Hi @Stefanowitsch, I totally agree with your sentiments. The state of Padloper documentation is not good at all. I don't want to make excuses. Written documentation was at the top of my list but other things came up. I then decided to instead create video documentation. I started on those but again was sidetracked. Great! Happy to help you with this. This doesn't mean I won't be working on the video documentation; I'll still work on that. Technically, this is incorrect. Although there are a lot of new features and a new API, some aspects of Padloper 1 remain, e.g. 'padloper templates' to customise markup, e.g. summary of order line items in the basket, etc. Actually, you can. For instance, stuff like 'add to cart', 'checkout form', etc. are near identical. I am entirely to blame for this. As stated, the docs are not nearly good enough. They are actually still in an interim location. The plan has been to move them to the padloper domain. True. Again, I am to blame for this state. I will be covering this in the video docs. It is quite easy to create categories and products. Meanwhile, I can grant you backend access to the demo site to visualise how things work. Zero fields are required πŸ˜€. Padloper ships with its own custom fields in many cases. It also utilises a few in-built ProcessWire fields such as title and rich text area (for product descriptions). Padloper creates all fields for you during installation. At installation, you choose the features you want. For instance, if you don't want the feature 'category', Padloper will not install its related template(s) and fields. If you installed the feature 'tags' and later changed your mind, Padloper will remove this cleanly for you. Most features are optional. The core features include order and product. This is how I have planned the video docs. I.e., several short videos covering installation, setting up the backend, creating your first product, displaying products in the frontend, checkout, extending Padloper, etc. I understand your frustration. I agree, the docs need to provide this information. The video docs will do this. Meanwhile, I need to update the demo repos to indicate their incompleteness. This is a great suggestion, thanks! Somebody else mentioned this recently. My plan now is to include an option during installation to install a demo shop. This would match the features that you have selected for install. I also plan (not sure about the timeline for this) an integrated JavaScript driven backend demo of how things work in the backend, basically a click-through thing. Apologies the docs are not clear. Now that you point this out I see how they can be misleading and how they are incomplete. The above instructions are only for the demos. You don't need those templates for Padloper to work. You don't need to create any fields. For frontend use, the only thing that is required is a checkout page. Using the Padloper API ($padloper), you can access and display any Padloper items in the frontend wherever you like. You don't need a products page or a categories page, etc. For instance, you could display all your products on the homepage, etc. You could add items to your cart in a modal, or in a dedicated page, or however you want. At the end of the day, things are just ProcessWire pages. Technically, you can access things using ProcessWire API but $padloper saves you a few steps. I hope I have addressed all your queries. The above responses are not a substitute for good, quality documentation. Video documentation and better demo repos are still a high priority for me. Thanks for honestly pointing out the current shortcomings and your frustrations. Whether or not you decide to use Padloper, I genuinely value your opinion πŸ™‚. Thanks!
  24. Tailwind Connect 2023: Recap of our first in-person event https://tailwindcss.com/blog/2023-07-18-tailwind-connect-2023-recap
  25. Hi @ank, Padloper can handle both ajax (no page reload) and non-ajax (page reload) requests. Please see the example projects in this repo: https://github.com/kongondo/Padloper2Starter With respect to ajax, Vanilla JS and jQuery examples are not complete. However, the htmx (Demo 1, etc.) examples are complete. Please have a look and let me know how you get on. I am planning to add some simpler examples some time soon. Thanks.
Γ—
Γ—
  • Create New...