|
From: Tim R. <ti...@my...> - 2000-11-29 16:58:08
|
He he... yes, the things you mentione are definitely ones we've run across.
The Flash objects with the transparency parameter on the OBJECT tag enabled
actually allow for drag events on the parts of the DIV behind the Flash
object that are not obscured by the Flash object itself. Also, though, the
mouseup *does*, as you suggest, become a problem in that if not triggered,
the flash object suddenly becomes affixed to teh mouse cursor, driving
people batty. I rather liked it myself, it was fun to watch the testers
during that phase. :)
That's why I wanted a "drag" solution right in the Flash object, since it
tended to 'eat' the mouse messages when the cursor was over it. If Flash
started the drag, perhaps Flash would be better at *ending* the drag.
Fortunately, if I can't make it worth well enough, I'm gonna drop the
feature entirely.
The Flash stuff could probably be replaced with DHTML, but it has one HUGE
advantage over DHTML for the specific purpose we've chosen it for: it can
make calls for data to the server without having to refresh the entire page.
So my headlines flash object can be sent a parameter (say, 'NBA'), and
silently make a call to the server to retrieve the headlines for the nba
without reloading anything. It makes my server requests for that content
under 2K, and cuts down on bandwidth...
To accomplish that task on DHTML, I'd have to make a DynLayer or a component
based on a Dynlayer, but associate it with a hidden IFRAME or LAYER. I'd
need to make a call to the server in that hidden frame that retrieved
headlines, and then returned client side javascript commands on the
returning page to the hidden IFRAME that then manipulated the visible
headlines DynLayer properties. Achievable, but a tad more messy (and
verbose).
Personally, I hate Flash. Always have. I've always figured people should do
as much within the confines of the native browser logic as possible. But I'm
forced to admit that when it comes to download size for complex animation,
smoothness of animation, and the issue above of tiny dynamci updates to
Flash files, it does hold its own in given circumstances. And the clincher:
we have one web developer, a misplaced database developer playing out of
position (me. :) ), and one Flash dude. Gee, what to do. :)
But I still hate Flash. Most of all, I hate sites that are all Flash and no
substance. Chuckle.
Thanks for the comments.
Tim
-----Original Message-----
From: dyn...@li...
[mailto:dyn...@li...]On Behalf Of Raymond
Smith
Sent: Wednesday, November 29, 2000 3:44 AM
To: dyn...@li...
Subject: Re: [Dynapi-Dev] Faking Events
Flash embedded in a layer, moves with the layer....
It just ignores Z relationships as it is moved. It also blinds drag event
handlers and can cause havoc if the main doc misses a 'mouseup' that happens
over the swf movie.
Which, in general is why flash needs to be subrogated to some obscure part
of your page or managed very carefully, i.e... if this dynlayer moves, that
swf (dom violating) layer;setVisible=false.
Personally, I think as libraries like this evolve you will see flash
dissolve more and more into a 'background' roll that serves very explicit
and temporal functions... SWF will never be about interface in the
long-run. Though integrated SVG may.
Besides... planet earth grows tired of the 'wiggling line' already. It was
vogue, it became soooo pervasive that it's vogue not to have it now.
Cheers
----- Original Message -----
From: "Jordi 'IlMaestro' Ministral" <jmi...@or...>
To: <dyn...@li...>
Sent: Wednesday, November 29, 2000 1:39 AM
Subject: Re: [Dynapi-Dev] Faking Events
> If you only want to drag the Flash place keep a pair of variables inside
your
> Movie.
>
> oldX oldY
>
> and then, when you detect movement inside the movie and the mouse is
pressed:
>
>
GetURL("javascript:myHolder.moveBy("+(_xmouse-oldX)+","+(_ymouse-oldY)+")")
> oldX = _xmouse
> oldY = _ymouse
>
> It should do the trick. I think
>
> I hope my Flash knowledge doesn't get me banned from the project :)
>
> Tim Royal wrote:
>
> > Howdy howdy.
> >
> > Anyone have an idea how to create an event and pass it to an object
through
> > the DynAPI events stuff? Here's what I'm trying to do. I have draggable
> > layers that can be moved around and set by the user. There are three
layers.
> > Each one has a Flash object imbedded in it (hence, moving around Flash
> > objects on the screen). We used Flash because of its smoother animation
and
> > its smaller size.
> >
> > The problem is that as we drag, the mouse moves over the Flash object
and
> > the events are no longered triggered by the browser (instead, the Flash
> > object itself 'eats' the event). This makes dragging a tricky, not so
fun
> > process.
> >
> > What I'd *like* to happen is to have the user be able to click on the
Flash
> > file background, and when the mouse moves (with the LMB depressed), have
the
> > Flash object send out a message to a function which creates a drag event
on
> > the housing DynLayer and moves the Flash object.
> >
> > Any thoughts?
> >
> > Thanks!
> > Tim
> >
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
>
_______________________________________________
Dynapi-Dev mailing list
Dyn...@li...
http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
|