Yama, I can remove the frames, I don't like them, but who's going to integrate a frame-less version of the Manager? Also, wouldn't that make the tree slower like it is happening for example on Revo?
For example, if I save a page or change page, is it going to reload the whole tree with the page?
Yes, I've already seen Silverstripe, very nice.
Removing the frames is not a problem for me, but is there anyone with the skills and the experience necessary to integrate an AJAX solution? If there is anyone that can contribute on this, please let me know and I'll change the theme accordingly.
A frameless design is definitely more usable and more accessible (for example it could be used with smartphones, the current manager is not that simple to use on a mobile phone).
-
☆ A M B ☆
- 1,231 Posts
OK, I examine method. I make a sample if I can do it.
Ok, let me know how it goes.
Microcipcip and Yama,
A few years ago (2009) I contracted a programmer to ajaxify the front end of my band's Evo website (with hash in the url etc) so that you could click through the site without disrupting the audio player and still have browser back functionality / bookmarking / graceful degradation with js off etc. He did it with a custom php file in the root directory and some custom javascript. Not sure if this is relevant at all to what you are talking about re ajax and hashes but if it is even remotely, I can supply the php and js file to you.
I have long lost contact with that programmer and that code would need updating by someone who knows what they are doing to run with the latest jquery and for programming advances etc.
At the time of building we could not work out how to get template variables and snippets to update when refreshing the content area so iframes were used for the ditto news on the home page and the eform forms on the contact page - and the LHS submenus were changed manually per page in the content area of each page rather than dynamically on each ajax page load. Someone who knows MODx Evo intimately could probably make TVs and snippets work properly.
The other thing is if anyone is interested in turning that into an Evo snippet, let me know and I will supply the original code but bear in mind I am no coder and I have no idea how it works - I just knew what I wanted and am happy for it to be shared if someone in the community would like to take it on.
[ed. note: nickf08 last edited this post 14 years, 4 months ago.]
Building an AJAX back-end is a complex project. Why not going this in steps? The first step is to use jQuery. And even that one is a big step and a lot of work.
But with the switch to jQuery we have a start in the right direction, and I hope some people, that will know how the back-end is working. This would help to the further steps, ajaxifying the back-end.
We've got so many jobs to do, let's take one after the other. We won't get anywhere, otherwise.
Gone away and found a better place to stay
-
☆ A M B ☆
- 24,524 Posts
The only really tricky part of "Ajaxifying" the back-end is the Tree. Once a practical Tree is developed, then it's fairly easy to use AJAX on it. A draggable, resizable overlay would be nice.
http://jqueryui.com/demos/draggable/
The tedious part is modifying all of the actions scripts to be proper php scripts, gathering data to use in placeholders, applying a separate HTML template file, and returning the finished forms. Again, it's not terribly complicated to use AJAX to fetch the forms as needed.
.
