== Quote from Rory Mcguire (rjmcgu...@gm_no_ail.com)'s article > dsimcha wrote: > > == Quote from BLS ([email protected])'s article > >> On 19/07/2010 00:01, BLS wrote: > >> > On 18/07/2010 22:36, dsimcha wrote: > >> >> heat maps > >> > > >> > Sorry for my ignorance, > >> > What are heat maps good for ? > >> > > >> > Since I am more biz software guy, here my question. > >> > > >> > Let's say I have this relation > >> > >A Project can have several Cost Centers. > >> > >A Cost Center can have several cost items. > >> > > >> > I our sample . Project -P- has say, 10 cost centers. > >> > Cost Center no 1 takes already 60 percent. > >> > The other cost centers (2-10) just take between 10 (blue) and 20 > >> > (green) percent. > >> > > >> > -- So I want to color cost center no 1 related items in red.. . and the > >> > max percentage item in cost center no 2 dark red. > >> > CC No 1 = {5,20,20,15} > >> > > >> > Is this what a heat map is made for ? > >> > > >> > and sorry , best example I am able to give atm.. > >> > bjoern > >> My guess was okay, Heat maps are also made for this use case. so no need > >> to answer. > >> Since Tree maps are not that different from Heat maps, do you have any > >> plans to implement them too ? > > > > I didn't have any plans to implement them, as I didn't know about them > > until I > > looked them up on Wikipedia just now. I'll consider implementing them, > > but I'm not sure if it will happen soon. > > > >> Next, Do you have any ideas about zooming ? (zooming a plotting region) ? > > > > This can already be done programmatically (see Figure.xlim() and > > Figure.ylim()), > > but is not exposed yet via the default plot window GUI. This will be > > exposed when > > I decide how I want to expose it. The most obvious answer is dragging, > > but the question then becomes, how do you zoom back out? > I don't think that you should hard code something like user interaction, > just provide the methods for interaction such as: > zoom on reqion(x,y,w,h), user input could be dragging a rectangle > zoom to(here%), user input could be scrolling, ctrl scrolling or a input box > move view(x,y), user input could be scrolling, or holding MMB > -Rory
The point isn't to hardcode this directly into the Figure object. What you suggest can already be done by calling xLim() and yLim() and then redrawing. However, Plot2Kill has the concept of a default plot window, which is displayed by showAsMain() and returned by getDefaultWindow(). The point of this is so that if someone wants to put up a quick plot, they don't need to set up a window manually. At the default plot window level, I don't see either how to avoid hard-coding this or why hard-coding it would be bad.
