[Module] QuickEdit

Quote from: rthrash at Oct 05, 2005, 09:08 AM

Adam, where are the CSS attributes assigned and written for the various pieces? I’ll take a peek at it too.

All of the in-page stuff in is /assets/modules/quick_edit/styles/output.css

Thanks for the help.

Sorry, I meant where are they set in the code that assigns them in the first place (not the stylesheets).

Okay, all the PixelHick issues I mentioned should be solved in the updated download

It was completely my fault. I was trying to do a comparison with a single = (too much VB as of late). So the toolbar hover was messing with a lot of elements that it should not have been messing with.

Very nice work Adam! Looks great and behaves properly! I made some minor tweaks to the CSS to prevent jumping of the menu items and to put a "hover zone" around the menu for errant mousing. This messes up the dropdowns a bit though. Let’s get that straightened out or remove the dropdowns grows ... or move the effect to the top hover ... or somehting... lol.

What do you think about toning down the pulsate effect – maybe swapping with highlight would work – on show / hide links?

Question:

Why are we using assets/js and not manager/media/scripts?

I think the scriptaculous libs should be stored inside the system (manager) folders. It’s going to be part of the core

The way I see it, Scriptaculous will be frequently updated and used on individual sites. The version we might or might not distribute might or might not work with a particular sites’ needs. This will keep site-specific things inside the assets folder making upgrades much easier IMHO.

Then again, this will all change in the very near future with TP4... right now nothing in the manager uses scriptaculous. If it did, then the logic would be different.

The way I see it, Scriptaculous will be frequently updated and used on individual sites. The version we might or might not distribute might or might not work with a particular sites’ needs.

I don’t think we should allow users to update code that will be made a part of the core in TP4. The other think is that we might even need to distribute a modified version of the lib in order to get it to do specific stuff.

Are we talking about TP3.3 or TP4? That’s two totally different beasts in my mind.

For most users TP4 will be an upgrade from TP3.3