Jump to content

renobird

PW-Moderators
  • Posts

    1,699
  • Joined

  • Last visited

  • Days Won

    14

Everything posted by renobird

  1. renobird

    Processwire.net?

    OK, well I'd be glad to assist if needed. My thought would be to get it shipped and tweak along the way.
  2. Just as Soma mentioned, use the FieldSet field type to create your columns, and then set their width so they float next to each other. In my case I made 3 FieldSet columns. (column_1, column_2, column_3) — although I only used 2 columns in the screenshot above. I didn't want to change how the admin looked anywhere other than within these columns, so the only thing I changed about the default theme was a few lines of CSS that are specific to these columns. You can grab the CSS here
  3. Hey Antti, Not a theme (yet) - just a few CSS tweaks I made. Nico has seen it and keeps encouraging me to make a theme out of it.
  4. Hey Mike, Great post, I think there are a lot of non-coders using Processwire, so it's nice to have a mix of tutorials. Glad to see you are getting along well with PW already.
  5. Thanks Ryan, I managed to sort this out by sticking with the repeater option, but instead of using a repeater as a singular method for date entry, I used it for "additional dates". That way, the majority of events are entered with a typical start/end date, but events with more complicated schedules can use the repeater. I set the ready fields to 2, that seems like a good place to start. I think this will be less confusing to the people entering events — at least I hope. See attached. (note: tweaked the admin via FieldSet to create 2 columns for calendar entry, I love how flexible PW is.)
  6. renobird

    Processwire.net?

    This is Adam's baby? @Adam, I'm willing to contribute if you are into the idea.
  7. renobird

    Processwire.net?

    I'd be glad to contribute to the front-end dev.
  8. Great work!
  9. Hi Ryan, That's what I have now, but when I tested it today with a group of users, they were confused by it. They didn't understand that they needed to save before the next set of fields would show up. (I know it says that clearly — not sure why they didn't seem to get it.) Once I showed them that, they were still not thrilled. This was a group of interns who will be managing the calendar. I can see their point, if an event has like 15 dates that a scattered through the month. Just dreaming of other solutions.
  10. I'm in the process of building a pretty intense calendar with PW. A lot of our events are recurring, usually on different days with different times, but otherwise they are exactly the same. For example, we may have performance in Theatre that happens on 10/18 @ 6pm 10/19 @ 8pm 10/20 @ 8pm 10/21 @ 4pm All other details of the event are the same. I'm dreaming of a version of the datepicker that would allow you to pick multiple dates/times for an event. Usage: Click on a day in the datepicker and set the time for that day, then click another date and set the time, etc... So it's just like the current date picker, except you can add more than one date/time. The values would be stored comma separated. I found this JQuery plugin for multiple date selection, but it doesn't do time as well. http://multidatespickr.sourceforge.net I have no idea if this is even feasible to implement, just throwing it out there.
  11. Hey Marty, Great work as always! One small critique: I think the "pillars" are a bit confusing. The arrow makes me think there is a dropdown there. I also feel like the entire thing should be a link, or somehow clarify that the "section-heading" text is a link? Rock on.
  12. Hi Marc, If you save the events/announcements submissions to PW pages, then you have complete access to the API and can build a front-end editor for user to be able to edit their submissions. Ryan posted this is the form builder forums as a way to save which user submitted a form. You can access the User pages from the API, just like any other page, so creating a front-end profile editor is fairly straight forward. I can post more detail here later if you need a place to start.
  13. *flaming hoops* Yeah, that's not gonna work.
  14. Probably not and ideal scenario, but that would work for me.
  15. Thanks Ryan, I realized a little bit ago that it needed to be all lowercase, and that was indeed the issue. *doh!*
  16. Hi Ryan, When I try to embed a form using the easy embed code I get this where the form should be. "This page is not intended for direct access." Perhaps I'm overlooking something? PS: I just downloaded the form-builder today, and it shows version number 0.1.4. (thought 0.1.5 was the latest?) PW version 2.2.9
  17. {insert_cheer}
  18. I'm in a perpetual state of waiting on the next end of the world.
  19. *amazing!*
  20. What I meant was if the OEM license was purchased to make a module that integrates with Processwire, but doesn't ship with it.
  21. Could it just be a non-core module that is free? In that case it doesn't ship with PW, but it's still "integrated" and should fall under their license. Sounds too simple, someone please come and crush my logic here.
  22. Interesting. You're right, once it's inserted it seems to have a fixed location. Not very intuitive to delete and reinsert. So far, that's the only issue I see.
  23. Apeisa, In the demo on the home page, click the image and change the position from the dropdown.
  24. votes submitted again.
×
×
  • Create New...