mindplay.dk

I would think twice before using anything that new - other WYSIWYG's have had years and years to learn (and work around) all the endless cross-browser issues, and problems with editable HTML in general, the list is endless...

But what's the alternative? WYSIWYG's all suck - we're probably just going to end up with a different set of problems...

I'm having some bad problems with the TinyMCE input-field under Chrome. Basically, I'm seeing this (thought not in Finnish, heh.) This is a known bug in TinyMCE, apparently - but it seems to only affect a few people. It only occurs when you have enough content to make the vertical scroll-bar appear, and only when you scroll upwards. The bug has been recorded in the TinyMCE bug tracker, but they don't seem to be doing anything about it - looks like they have 1,200 or so other bugs to attend to. It has also been mentioned in this post on StackOverflow. Using that, I came up with this (horrible) work-around: $('iframe').get(0).contentwindow.onscroll = function() { var el = this.document.body; el.style.backgroundColor = '#fffffe'; this.setTimeout(function(){ el.style.backgroundColor='#ffffff' }, 1); }; No solution, just demonstrates a possible work-around - it basically just forces Chrome to repaint. Obviously, this bad, bad, terrible work-around will only work if your body background is white. I would be really grateful if others could help find a better solution to this problem, since I can't really throw this at our customers - it's unusable as-is...

It would no longer be obvious that the navigation exists - I don't think you want users to have to "search" for it. It's may be a little "over-animated" this way, but there's something to be said for usability too, not just for design... (just my $.02) @diogo - having them still showing with opacity just makes things look muddy to me - I prefer to keep the UI clean. (this, on the other hand, is a design consideration, so perhaps just my personal preference) Given all these very personal pros and cons, perhaps I was wrong - perhaps it is better to just keep this in your own admin theme?

Looks fine to me, How about findRandomSeed() or findRandomSeeded() ? ... it's not really limited to time periods, you can seed it with whatever.

I personally also added a rule that hides the PageListActions for expanded Pages - so that the buttons display only when you hover over an item. That may be taking it too far for some people's taste, but I find that it minimizes the amount of noise on the page greatly - I don't need a screen full of buttons. That may be more of a personal matter though

Care to elaborate? In my opinion, it makes every page look like it's a folder - which the majority of pages are not. So in that sense, the convention favors the minority. I also don't think the trailing slash looks "right" on printed matter or other public links - you don't want to make people type in an extra slash. And of course, you can leave it off - but then the server needs to do a redirect, in which case why do we need the slash in the first place? I think it's an odd convention. I understand PW needs it for the admin pages, and that's fine, but I can't think of a single reason why you would want trailing slashes on all your public URLs. Why do you favor that convention?

It really seems to me that this is a technical limitation, or implementation artifact - not something users should have to deal with on a case-by-case basis.

Yes, this would be generally useful in PageArray, good point. As for the method-name, good question... would it make sense to just have this as an optional argument on getRandom() ?

This is just a tiny, one-line tweak - but it really makes a huge difference in terms of ease and speed in working with the Page List. I've added this to my admin theme, but I really think this belongs in the core. in "ProcessPageList/ProcessPageList.css": /** * When an item is open, this style ensures that the PageListActions become visible * */ .PageList .PageListItemOpen > ul.PageListActions, .PageListItem:hover > ul.PageListActions, /* <-- add this line! */ .PageListSelectHeader .PageListActions { display: inline !important; } You now have direct access to "new", "edit", etc. - just by hovering over an item in the Page List. Give it a try - you will most likely never want to go back!

@Ryan I'm also looking to turn off the slashes by default, was that ever implemented?

Perhaps even better: /** * Select random pages from a PageArray * * If no $seed is provided, today's date is used to seed the random number * generator, so you can use this function to rotate items on a daily basis. * * @param PageArray $pages the list of Page object to select from * @param int $amount the amount of items to extract from the given list * @param int|string $seed a number used to see the random number generator; or a string compatible with date() */ public function randomPages(PageArray $pages, $amount=1, $seed='Ymd') { if (is_string($seed)) { $seed = crc32(date($seed)); } srand($seed); $keys = $pages->getKeys(); $selected = new PageArray(); while (count($keys) > 0 && count($selected) < $amount) { $index = rand(0, count($keys)-1); $key = $keys[$index]; $selected->add($pages[$key]); array_splice($keys, $index, 1); } return $selected; } Now you can seed with a date()-compatible string, so you can rotate weekly (for example) using "YW", or monthly using "Ym", etc.

WireArray::getRandom() can be "too" random for my taste - I wanted some Page items to rotate randomly on a daily basis, rather than every page load, so I came up with this: /** * Select random pages from a PageArray * * If no $seed is provided, today's date is used to seed the random number * generator, so you can use this function to rotate items on a daily basis. * * @param PageArray $pages the list of Page object to select from * @param int $amount the amount of items to extract from the given list * @param int|null $seed a number used to see the random number generator */ public function randomPages(PageArray $pages, $amount=1, $seed=null) { if ($seed === null) { $seed = crc32(date('Ymd')); } srand($seed); $keys = $pages->getKeys(); $selected = new PageArray(); while (count($keys) > 0 && count($selected) < $amount) { $index = rand(0, count($keys)-1); $key = $keys[$index]; $selected->add($pages[$key]); array_splice($keys, $index, 1); } return $selected; } I thought I would post it here for others to use. I wonder if this is useful enough that it (or something similar) should be part of the core? I personally find that "totally random" is rarely useful or desirable in real life - for one, pages that change on every request may harm your search-engine ranking. For another, users may find it confusing that your site changes all the time - "hey, what was that thing I just saw" doesn't work for the person who goes back to the front-page to see "that other thing" he just saw, when you constantly swap things out between every page view... Just my opinion, for what it's worth

Every other major player on the social web has moved to OAuth2 - I'm pretty confident that a major platform like Twitter will soon follow suit.