Oh OK, may be I was mistaken. Anyways, as mentioned in the other email, I've started implementing the remove object methods for services.
It'll take a while, but i'll have the GameVersion related ones done soon. On Wed, May 18, 2011 at 11:01 PM, Jens Pfau <[email protected]> wrote: > The problem with the top bar is that it wouldn't look nice when an error > message spans multiple lines. > > We could just create a new div in Mugle.html above the main-panel div. > > Gmail shows messages at a similar spot and not in the top bar. > > > > On Wed, May 18, 2011 at 10:56 PM, Prageeth Silva > <[email protected]>wrote: > >> OK my mistake. I think the one Jens mentioned was was another >> error-display message used by the initial popup window. I can't remember why >> i ended up removing this particular one using Mugle.java. >> >> May be we can use this for error messages. Do you want me to go ahead and >> implement it? If so, which would the perfect spot be? I personally like the >> top bar because we already have allocated space at the top. >> >> Where as, the top of the contents panel would mean that there can be cases >> that the message appears on top of (z-index increased) other objects, OR we >> may have to push them down. >> >> Another reason I don't like having it there is that, we should always be >> able to clear the whole contents panel at any given time and not have to >> think of the common divs that should be regenerated. >> >> However, I may be wrong; so let me know what exactly needs to be >> implemented. >> >> >> On Wed, May 18, 2011 at 10:44 PM, Matt Giuca <[email protected]>wrote: >> >>> That may be true, but we don't *have* to remove it. Just hide it (either >>> with CSS display: hidden, or some GWT method for hiding objects) and bring >>> it back when an error occurs. >>> >> >> >> >> -- >> *Prageeth Silva* >> > > -- *Prageeth Silva*
-- Mailing list: https://launchpad.net/~mugle-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~mugle-dev More help : https://help.launchpad.net/ListHelp
