Quote from: nickf08 at Apr 16, 2012, 06:24 PMI can see that strange behaviour you are talking about in post #49 microcipcip. In Firefox 8.0.1, the resizing is very buggy. The handle is hard to move and once a resize is done, the resize handle remains and the links in the drop down menu cannot be accessed - the hover works but the drop down disappears before you can get to the links.
Yes, that's the problem, but I haven't tried cipa solution yet, that should work.
Quote from: nickf08 at Apr 16, 2012, 06:24 PM
Do you think we need individual resizing of the LHS Site Tree column? I would have thought horizontally proportional changing that adjusts the widths of both the LHS and the RHS column at the same time would be best - so that if the LHS width is increased, the RHS width is decreased by the same amount.
You are right, it is going to work in that way, only horizontal resizing. Now I am just testing so I didn't pay too much attention on the resize plugin configuration options.
Quote from: nickf08 at Apr 16, 2012, 06:24 PM
I really like the option in the current Evo to "minimise" the LHS tree to give more RHS editing space - and then show it by clicking the arrow again. I think that is a great feature.
I agree, I'll add that (it is easy), but first we need to fix this problem, which is more important.
Quote from: nickf08 at Apr 16, 2012, 06:24 PM
Do you think we could save an icon by combining the 2 separate functions for "expand all" and for "collapse all" into the one toggle function with one icon called "Toggle Site Tree" or "Expand / Collapse Site Tree"?
Well that's really easy with jQuery, just an hide/display function.
Quote from: nickf08 at Apr 16, 2012, 06:24 PM
When resizing the LHS tree at the moment, the mid grey horizontal bar underneath the drop down menu no longer looks seamless as one bar - two bars are visible: the LHS bar is shorter and a gap equal to the resize reduction appears between the LHS and the RHS bars.
That's because when we resize the LHS we need to resize RHS as well. This is a secondary problem though, if we cannot resize the iframes without this buggy behaviours, is a problem and I'd have to use frames!
Quote from: nickf08 at Apr 16, 2012, 06:24 PM
What is the thinking by continuing with frames (or iframes). I remember reading the reasoning in one of the posts but can't find it at the moment. Are they still really needed?
1. You can't put a div over a frame, or a dropdown menu like in the example, because a frame is a completely separate window.
2. Frames are deprecated on HTML5 and in the future (near or far, I don't know) will not be supported.
Quote from: nickf08 at Apr 16, 2012, 06:24 PM
Could divs work instead? The top bar could be fixed. And the divs could stack when the screen is resized.
Then you would have to refresh the whole page and not just the tree menu or the page on the right every time you make a change, making it much slower. Another option would be to use A LOT of ajax and that would make it slow like Revolution (I think), AJAX is a great technology but needs to be used wisely.
. I wouldn't be able in any way to make MODX Evo work completely in AJAX, that's a major change. Ask someone which is working on the development side and see what they think.
. You could try to ask about this on "Bringing Evo back to live again" thread.
☆ A M B ☆
