apeisa

Ryan: tested this with 4.1RC. Seems to be working great (just remember to clear cache, otherwise lots of empty icons). It also does what it promises: by default it strips away all the elements that are not available from toolbar menu. So most sites are fine with that one setting field you have there already (CKeditor Toolbar). Although we probably don't want to strip links, so we need to make it think PWLink as a link tool. Or then use the allowed content rules: http://docs.ckeditor.com/#!/guide/dev_allowed_content_rules EDIT: Hmm.. some problems with PWImage module. Other than that - I think this will be pretty easy upgrade.

I updated the version number on both, modules directory and github. Does it work? (I myself pull modules directly from github, so not too familiar with modules manager).

What does it require? Updating the version number?

That kind of tweaks (which elements are allowed and which are not) are coming in 4.1.

Oh, and it seems to have a killer feature:

It definitely should have filename: https://github.com/ryancramerdesign/ProcessWire/blob/master/wire/core/ImageSizer.php since it gets it on construct.

Ryan, Phillip: TinyMCE has that right click table toolbar also, just not enabled by default. I still prefer CKeditor tables, but not so much differences than I thought there is. Both have too many options by default (although there are situation where some of those options are really needed). Ryan: Yep, that feature is still missing. I think best way to go currently is forcePasteAsPlainText setting (http://docs.cksource.com/ckeditor_api/symbols/CKEDITOR.config.html#.forcePasteAsPlainText) combined with paste from word (if your client does use word). But it seems 4.1. is just around the corner: http://ckeditor.com/blog/CKEditor-4.1-RC-Released so maybe we should upgrade to it already?

I did had good play with this earlier this weekend - compared to tinyMce - it is just much nicer to use. Less fighting with positioning (text and tables, images inside text etc), less mysterious "if I hit backspace now, I don't have a clue what will happen" -moments and it just looks and feels nicer. Great work Ryan! Glad I could help a little. Also: The inline mode beats the Aloha hands down in my opinion. Of course not much use in backend (unless you need RTE inside repeaters or have lot's of multilang fields) - but if you build front end editing to your sites - don't forget this beauty.

Is there $this->img->imageType property? There definitely should be filename though. Check what kind of object there is coming from $event->object? get_class($event->object);

Thanks Teppo, makes sense to me. I have locally tested this and one earlier pull request (string translations support by boundaryfunctions). All seems to be working fine so I committed them to github. Very happy if you guys can test that everything works as expected.

Nope, there isn't. Repeater is probably closest to that.

Are you after something like this: $pages->get("/desired-rootparent/")->find("other selectors")?

Sorry Marty, I missed your last reply. You can send me access if want to, happy to take a look. Joss: I will try to test this soon with latest dev. Do the problems occur when upgrading or with fresh install too? Have others got this working on latest dev?

More like this:http://processwire.com/talk/topic/3008-module-pages2pdf/#entry29627 Much more usable approach in my opinion.

That is pretty nice way to do it. Usually my sites have lots of metadata pages, so I collect them all under page called /tools/

Yep, just always replace the profile image with selected one.

This will be real timesaver and super useful module, thanks Wanze!

Simple way would be just use page per image (and then choose background with page field): /background-images/ /background-images/first-image/ /background-images/second-image/ /background-images/third-image/ This solution also scales, when your client wants to have different "color scheme" per image etc.

You are crazy genius if you can build site like desk.com in 1-2 days. But wait.. you actually are crazy genius!

I have planning to update the language pack for ages. I do it next week when I get back to office. It would be great to get some contributors. I have avoiding translating the parts that are only for superusers, but using PW that has languages mixed is kind of frustrating. So I think we should aim for 100% coverage. Also, I am open on how to translate certain terms, like template (currently: "sivutyyppi"), name (currently: "sivun nimi osoitepalkissa") etc.. Trying to balance with what is "correct" and what is easy to understand for non-technical person.

Interesting discussion. If "sandwich" type of website (without actually coding it by hand) is what you are building, then CMS like Concrete5 (http://www.concrete5.org/) or Apostrophe Now (http://www.apostrophenow.com/) is probably much better solution than ProcessWire. ProcessWire strengths are definitely in it's data modelling and as a building platform (framework). When it comes to sites where each page should be a little different to each other with totally custom content (no clear templates) - then PW helps you very little out of the box. Of course it would be my weapon of choice, if I would start building simple cms for that need

Would it be nicer/easier to have profile image as a separate image field?

That is prettiest and probably most easy to use/browse calendar in long time. Reno is my designer hero for sure!

Even after two years of PW-development I seem to make things much more complicated than they are (same goes for you Petey-boy ). Thanks Ryan!

Just send you an pull request for PWImage plugin! Thanks again for your work on this. I think CKEditor 4 is super nice. Their default theme will fit nicely on most of the admin themes there is currently available for PW too. Great implementation on inline support too Ryan!