On Mon, 2011-08-01 at 13:27 +0300, Tyron Madlener wrote:
On Mon, Aug 1, 2011 at 1:04 PM, Rouslan Placella rouslan@placella.com wrote:
On Mon, 2011-08-01 at 09:26 +0300, Tyron Madlener wrote:
On Mon, Aug 1, 2011 at 2:34 AM, Rouslan Placella rouslan@placella.com wrote:
Hi there,
I rewrote the navigation frame resize handler and I'm looking for some feedback and opinions. The new handler keeps navigation frame width synchronised and there is an option to collapse the frame. I made a video [1] that showcases the functionality and there are a few words about it in my blog [2] and of course, it can be seen ion action on my demo site [3].
I would still find it nice to have just one collapse/expand button in the middle, but therefore bigger. Though we might need to check that the expand button doesn't overlap other content too much.
I put the collapse buttons at the top and bottom of the screen exactly for that reason: keeping them out of the way. Let's see what others think about this.
Also having it animated, even if it is a bit laggy, gives a more fluent experience instead of having it flash in and out, imho.
The animation for the frame collapse is _too_ laggy IMO. Most of the time there is too much content in the main frame for a smooth transition. So I animated the buttons instead :D
And lastly, frame resize still doesn't work in Chrome.
Apparently it's a well known bug. Frame resize is only possible on chrome if the frameborder attribute is set to 1. Of course, setting frameborder to 1 makes the navigation look ugly in a every other browser. I guess that we could conditionally set frameborder to 1 for chrome only...
Or maybe it's time to throw away the pma frames altogether :-)
Is it? Getting rid of frames would mean that if JS or ajax is disabled in PMA, then a whole page must be refreshed in order to refresh the navigation or even to browse the navigation tree. Don't get me wrong, I'm the first one to say that frames suck, but I just don't see how we can deliver content efficiently without them.
Rouslan