almonk

Thanks Didjee! I've updated the git repo with your fix.

This looks awesome Ryan amazing work! Its input field setup in the page edit process would look just like ryan’s here, showing blocks with the child pages’ fields. The editor could choose from the allowed templates for new child pages. And in templates the field would directly provide the page array like in repeatable elements. Totally agree with this

I love love love this theme. But I'm very particular I've made a branch and simplified it a little further and changed things to my taste. Please feel free to fork yourselves. In short, I've disabled the animation, got rid of the sidebar and changed the fonts back to your standard Arial. Screenshots: http://cloud.alasdairmonk.com/472Y0B1k2r3Q1I472m0X/o http://cloud.alasdairmonk.com/1d1E2s2S2I1t2s163537/o Github Download: https://github.com/almonk/Al-s-Futura-PW-Theme

No plans to support this. But it is open source, please fork and make any enhancements.

Great! Been really looking forward to an improved UI for repeatable elements for a while.

I recently made a few custom modules for a client (sadly not able to share) that required quite an 'app like' environment. While Apeisa is busy working on the updates to his clean admin theme that I have designed, I thought I'd put together a different theme entirely. This theme uses the Twitter Bootstrap framework, which is really nice if you haven't already tried it. There's quite a few nasty hacks that I've had to do to skew PW to fit the framework, but none of it is too apparent to the user. You can fork the code here (git clone into a folder called templates-admin under site): https://github.com/almonk/Bootstrap-admin-theme It's still a wip, but very much usable already. Please fork and improve. Thanks, Al

Looks brilliant Ryan! Will try it out asap.

Hi guys, Had a client recently who needed to be able to turn pages from their Processwire driven site into a PDF. I took a look at how this best might be achieved and present here my rough workings of a 'Pages to PDF' module for Processwire. ** Please note** this is in no way a finished module and is tailored to the developers amongst you (not novice users) as it needs modification per project, but it should be a good starting step if anyone else needs to do anything similar. See the screencast here: http://f.cl.ly/items/3y2g2E0Q060K3G150h0B/Screeny%20Video%2013%20Sep%202011%2009.58.01.mov Fork the code here: https://github.com/almonk/pdfcomposer.module Dependencies: FPDF (included). --- I'd love love love some more contributors to this to help improve it. For example, I'd like to have an ASMselect instead of the page list, but couldn't figure it out in the time I had. Cheers, Al

Thanks for your detailed feedback all! Ryan, I completely understand your hesitation concerning markup generating widgets - their implementation in Wordpress is horrible to use at best, and I definitely don't want to see PW going down that route. BUT, as we've also mentioned, reusable snippets of code to do the same old things (maps, videos, twitter feeds etc) can be a real timesaver. I very much like the idea of supporting Widgets within the core module library - this render() function is something that seems to have eluded me aswell, and looks useful for this kind of functionality. I'll have a shot and see how I get on. Cheers again,

As a sidenote - I really like the widgets implementation in pyro cms http://pyrocms.com/docs/manuals/developers/creating-custom-widgets

Hi all, Thinking aloud here about a feature I'd like to see in Processwire, Widgets (or at least this is the name given to them in Wordpress). Simply put, Widgets are content blocks that the user of the cms can add/rearrange to designated parts of the site. This is really useful for those client who are a little more au fait with computers and want to add little bits here and there. For example, recently I had a client who wanted to add a Facebook 'like' button into the sidebar of his site (built in PW). In the end I made a 'custom html' field and let him just drop some content in there - but a more user-friendly solution would have been nice. I don't have much of an idea if this fits well into the PW philosophy, but here's how I think it could work: 'Widgets' is created as a module and a field which can be added to templates. The developer can add the widgets field to the pages/templates he wants to have the functionality available on. A bunch of 'core' widgets are created (for instance: Youtube video, image, html block etc etc). These widgets can be added once on a page. So, in the example above, the user could edit the Homepage, add a HTML widget and just paste his code in to the settings. I don't know if this sounds like bloat - but in my mind's eye it could work very nicely alongside all the current PW features...

Really interesting discussion. The 'solution' arrived at here is very, very specific to the nature of the content management needs of the business. In a way I love the idea of such a system so perfectly suited to the CM style, but clearly it requires a huge amount of investment of time, money and resources that isn't within the reach of most small-medium businesses.

I think cropping functionality would make sense in PW and would undoubtedly be a useful feature for some. There's a few philosophical reasons that make it slightly harder in PW than other CMSs such as that thumbnails are usually defined in templates and not on the fields but I think this workflow would work: A new fieldtype 'Cropped Image(s)' is created which has the same feature base as the standard Image field but with the extra crop functionality The developer can define the size of the 'thumbnails' or whatever the images are being used for in the field's settings (just like the image fieldtype). Similarly the settings for the crop can be defined here, ie. ratio, dimensions etc When the user uploads an image they are prompted to 'edit this crop' or similar Clicking this link opens a modal window in which the crop can be adjusted When the page is saved the cropped version and original are saved as page attachments The cropped version is available in the api as $page->image->crop or similar Just some thoughts...

I totally agree with Ryan on this. I don't think Aloha is appropriate for 100% of problems, but it doesn't need to be to be useful. As Ryan says, it's a cool little utility that provides a useful function and I personally would love to see support for it.

An inputfield sounds like a tidy solution - would love to see this.