Jump to content

netcarver

PW-Moderators
  • Posts

    2,241
  • Joined

  • Last visited

  • Days Won

    47

Everything posted by netcarver

  1. Hi Alan, Right, I see. Sounds like they must have spellcheck="false" on that textarea/iframe or whatever it uses. Isn't there an TinyMCE plugin for spellchecking?
  2. I think diogo is right -- this is a browser feature. If you are using firefox see this, chrome see this.
  3. Update: I now have PW running on nginx. It took a little longer than expected & I'll post more when I've investigated it further.
  4. Hi Teppo, I wouldn't consider it 100% stable just yet, and I've not touched it for about a month. That said, most of the features are fixed because the DSL takes its shape from HTML syntax and, if anything, there will be additions of helper functions rather than changes to existing ones. There are some major portions that need work and there is no upload ability in there yet. If you are thinking of putting this into a client site I'd err on the side of caution. You can also ask Apeisa for his experiences with it as I know he started using it recently.
  5. Since Ryan posted that his prototype idea for a PW form builder I've not done much in this area. Rather than have the code sat under-utilized in a private repo I've now posted it as the fxForm repo under my github account in case anyone is interested. Currently you need the controller-element branch to get the latest code.
  6. How about a simple to-do list widget?
  7. Coincidentally, I started looking at this last night and found these... .htaccess to nginx rules convertor Wordpress performance server I hope to try PW out on nginx in a virtual machine tonight.
  8. LOL! There was me thinking that Darth Vader could only eat grated (shredded) vegetables or cheese Antti, do you want this thread to be about kids stuff in particular -- or just any great recommendations?
  9. How about a module repository -- and code that allows PW installations to scan the repository for new modules & updates?
  10. Thanks for posting that Alan, I've also updated the opening post to make it a little clearer too.
  11. Alan, You got it! Yes, PW's default .htaccess file prevents web access to directories starting with a period. Also, like Soma said above, all of the flourish classes need to be in that .flourish directory, not some sub-directory of it, if you want the class loader I posted to work out of the box. Have fun!
  12. Ryan, actually, I think Pete was the first person in here to mention using Flourish with PW, but I didn't know that when I started posting about it.
  13. Just wanted to say that it was nice to meet a few new people in #processwire today. Hope to see you again and that you find the channel useful.
  14. Hi evanmcd, My next site will probably be a web application -- and I've got both ProcessWire and Flourish on my radar for it. Just like PW, Flourish has some great features out of the box including a good access control model (using levels and/or ACLs.) Both products are different and have their own advantages. PW has an amazing API, community and admin UI out of the box, whilst Flourish has better DB and cache support (imo.) The DB layer in Flourish allows you a wide choice of DB products, and even if you only want to use MySQL, it allows you to use the InnoDB engine which may be important if your web app needs transactions. PW only supports the MyISAM engine at the moment but Ryan has talked about extending this to other DBs (InnoDB under MySQL, Postgres, SQLite etc) now that more of them support full-text indexing. The second area where Flourish has some great features is caching. It has good cache abstraction and you can very simply apply caching to things like sessions too. BTW, it is possible to use PW and Flourish together.
  15. Thanks to Soma's online tutoring I now have this.
  16. Re-posting "The Architecture of Open Source Applications" from the Textpattern forum as it looks like a very interesting resource.
  17. Is this any better?
  18. Thanks for all the replies folks. I was hoping not to use an image -- but that's probably easier than spending hours trying to get the kerning looking good across different browsers, or learning a new set of JS. On balance I'll try an image covering the h1.
  19. Yes, they sure do. Actually I'm trying to do this now with some spans in the h1 title. I can get it looking way better in FF or in Chromium -- but I'm having trouble getting it looking good in both. Is there any way to target different letter-spacings based on the browser?
  20. Cool. FWIW, I'm working on a new TLD home for textile now (at last!). I'm no designer, but I hope it will be useful to folks.
  21. Hi Soma, Right. Actually, the updated regex I gisted does allow for an optional "/" before the "?v=" part, but I agree, if Alan can make his examples all conform to a single standard, that would be way easier.
  22. Alan, Did you see this. I think your first link example is broken anyway. Shouldn't your first example be... https://www.youtube.com/watch/?v=pbDn_Np3Pfw ...if you want a link to YT that actually works. If that is the case, then could you try my gist again (I just updated it). You can also try the online regex tester at http://osteele.com/tools/rework/ in cases like this to tweak things.
  23. Hang on Alan, isn't that first example malformed? Shouldn't it be https://www.youtube.c.../?v=pbDn_Np3Pfw instead of https://www.youtube.c...\?v=pbDn_Np3Pfw
  24. Alan, Thanks for the update. Yes, your second example won't match using the regex Ryan posted as it is a different format and the regex will need some adjusting to cater for it. In the meantime, can you try this gist as a possible fix for your first example.
×
×
  • Create New...