Release Plans

After much monotony and testing, spawned by today's release of Firefox 1.0.3, I think I've managed to remove most of the WebFX buttons from the manager.

Files that changed:
+ Most of the files in /manager/actions/ (dynamic and static)
+ /manager/includes/accesscontrol.inc.php
+ /manager/media/style/MODx/site.css and coolbuttons.css
+ /manager/index.php

They're really ugly now folks, but they (should) work without the need for any javascript. I'm going to make graphical replacements for all these, which will be handled via the stylesheet and one image in the next day or so.

The buttons were created as CSS-stylable buttons in the format of:


The class="button" is what the general button states come from (for uniform padding and margins and base images), and the id is what will enable me to position the background image of each button to make them graphically appealing.

Please beat it up!

The new files

Up next, cleaning up the CSS files for the manager and changing away from the stock Etomite color scheme. We need to get this thing out ASAP, folks!

FYI, that only leaves the tree menu as the stumbling block for working in Safari... the following URL would allow us to use a tree menu that WOULD work in Safari, as well as Firefox and IE:

http://gazingus.org/html/DOM-Scripted_Lists_Revisited.html

I haven't been brave enough to stare this down yet, but I think most of the tree menu comes from /manager/frames/3.php (with a smattering of 5 and 6, and maybe 10).

Working in Safari would be a VERY big deal, even if we don't get WYSIWYG editing.

HOWEVER, when coupled with Apple's recent addition (Saturday) of supporting contentEditable like IE's proprietary support, and we might just be able to make it really cool and get the guru-celebrity-designers REALLY excited.

This is a big deal if we can pull that off.

Raymond and I played around some more tonight. We're close to having the tree menu functional in Safari. It renders, there's just some bugs with the context menu that lead to crashing browsers and bad styles.

But man, it's a heck of a start!

Here's the changed files

Raymond and I played around some more tonight. We're close to having the tree menu functional in Safari. It renders, there's just some bugs with the context menu that lead to crashing browsers and bad styles.

But man, it's a heck of a start!

Here's the changed files

And it also works in Opera 7.11!

Ok, the "save snippet" processor works now. I wasn't sure if the references to the "plugin" field in the queries were supposed to be there or not, or if the "plugin" field was supposed to be in the database.

One thing I've done is to change the text in the english.inc.php file for Manage snippets, Manage templates, etc to just one word, Snippets, Chunks, etc, so they don't enlarge the tabs to the point they have to drop down to a second row. After all, I already know that it's the management page!

Very interesting...it really works in Safari; I even see the WYSIWYG text, although no toolbar, for the tinymce editor. For HTMLarea, I get a warning message that it probably won't work, and it doesn't, but I do get the raw text editor. Some of the CSS is flaky, but the document tree does work, even the right-click menu works! Fantastic!

Here's yet another set of file changes. From Raymond:

Here are my recent changes. This should fix the
mozillainnerhtml.js bug

+ remove ieemu.js and mozillainnerhtml.js (from /manager/media/scripts/)
+ added support for Safari,Opera 7+, and fix bug in
FireFox 1.0.3

From what I've test so far the manager will work in
even Netscape 6.2+, Mozilla 1.0+, Opera 7+, IE and
Safari?

I still occasionally get random crashes when right-clicking a tree menu item in Safari. I also get some weird rendering of it as well. But it's much better than before (not even a tree menu viewable!).

Think we could get some broader testing done today?

FYI, I posted a status update here.

Other than the Safari crashing and context menu goofiness, are there any other show stoppers you guys and gal see preventing us from finally giving the folks some files?

Ok, the "save snippet" processor works now. I wasn't sure if the references to the "plugin" field in the queries were supposed to be there or not, or if the "plugin" field was supposed to be in the database.

The plugin field is no longer used inside snippets

One thing I've done is to change the text in the english.inc.php file for Manage snippets, Manage templates, etc to just one word, Snippets, Chunks, etc, so they don't enlarge the tabs to the point they have to drop down to a second row. After all, I already know that it's the management page!

Cool! I like the idea and have also rearrange the tab layout templates, template variables, chunks, snippets, plugins, keywords, etc

Very interesting...it really works in Safari; I even see the WYSIWYG text, although no toolbar, for the tinymce editor. For HTMLarea, I get a warning message that it probably won't work, and it doesn't, but I do get the raw text editor. Some of the CSS is flaky, but the document tree does work, even the right-click menu works! Fantastic!

I'll leave the the clean up stuff to you mac guys

Susan, can you give me a hand in figuring out how to make Safari look and behave right? I'm having a feeling the crashing is due to the widely reported Java issues with the 10.3.9 update. Investigating that now...

On further investigation, I can confirm that the manager does not crash Safari prior to the one that ships with 10.3.9. It's an Apple bug!