Dave, Why did you give up? Obviously Tea House functions without a hitch as well as test xml files not submitted to the theme directory in test scenarios. It would appear to be an issue with the submission form rather then compatibility since the messages align with the search bar not the bottom of the header. And said messages will go away after clicking undo or close. I don't see how you could claim a glitch in the header sizes when Tea House is still in the directory and is one of the most popular themes due to all the details it has, which is also due to the large amount of space it is allowed. My theme could use a little more room since I'm trying to get the effect of being underwater as well as have things happen above it. Sounds complex but I plan for it to be very simplistic but still have a dynamic trait of time or day (I haven't decided which). It also didn't sound like making this a feature request would work out however I'm not completely sure where exactly i should submit the issue. If I could possibly get support on that or if someone could just fix this part of the theme submission process to allow header.height, I and I'm sure everyone who is trying to make a theme similar to the details and story arch of tea house, will appreciate.
The theme I want to have a large header on: http://www.google.com/ig?skin=http://deepseawhale.googlecode.com/files/openocean.xml I may update it to be exactly how I want it and then ask about this again with a clear example of what I want to do with the extra space. Right now the theme is waiting approval to be put in the themes directory so it fits the standards of the API, not what I wish I could do. -Phil On Apr 22, 8:01 pm, BlueQuoll <[email protected]> wrote: > Thanks Rob, > > I won't pursue this one, as I can see that Google might need the > certainty of a fixed header height to be able to introduce other > messages/features in the iGoogle header from time to time. > > It's interesting, however, that space for messages or constraints of > program policies didn't seem to apply when Google attempted > (unsuccessfully) to force truncation of the header area on smaller > displays several months back. Low-height headers specifically designed > for smaller displays would have been a more acceptable option at the > time. > > Dave > > On Apr 22, 7:19 pm, Rob Russell <[email protected]> wrote: > > > > > Hi Dave, > > I've passed along your feature request internally. It sounds like a nice > > feature (as you pointed out it's used by some popular themes) but it appears > > to be a special case for the few themes that use it. > > > One difficulty I can see in making this generally available is keeping the > > same space for the messages that appears occasionally, for example when > > users add and remove gadgets. The dimensions could also affect the Program > > Policies since we use pixel measurements in there. These are just a couple > > considerations off the top of my head of course. > > > I don't think it's too likely someone will take up the feature request but > > it is possible. Feel free to file an issue on the public issue tracker as a > > place for others to show their interest in the feature. > > > Rob Russell > > Google Developer Relations > > > On Sat, Apr 17, 2010 at 2:47 AM, BlueQuoll <[email protected]> wrote: > > > Rob, > > > > An update would be appreciated — or does your comment that "iGoogle > > > Themes are still in labs" mean that there is actually no active Google > > > support for the Themes API? > > > > Thanks > > > Dave > > > > On Mar 23, 5:53 pm, BlueQuoll <[email protected]> wrote: > > > > Thanks, Rob, I'd appreciate some advice on this feature. > > > > > I'd really like to use it, as there appears to be some call for > > > > smaller theme headers for users with limited display size. > > > > > Dave > > > > > On Mar 23, 5:36 pm, Rob Russell <[email protected]> wrote: > > > > > > Hi, > > > > >iGoogleThemesare still in labs (http://code.google.com/labs/), so some > > > > > features available may not be complete or may be removed unexpectedly. > > > I > > > > > don't know if that's the case with header.height but I can look in to > > > it. > > > > > > Regards, > > > > > Rob Russell > > > > > Google Developer Relations > > > > > > On Mon, Mar 22, 2010 at 11:01 PM, BlueQuoll <[email protected]> > > > wrote: > > > > > > Any way to get a Google response on this issue? > > > > > > > On Mar 8, 11:47 am, BlueQuoll <[email protected]> wrote: > > > > > > > I omitted to mention that the reduced heightthemesdisplayed in > > > > > > >iGooglewithout any problems using theiGoogletest URL: > > > > > >http://www.google.com/ig?skin=[URL] > > > > > > > > On Mar 7, 9:09 pm, BlueQuoll <[email protected]> wrote: > > > > > > > > > In an attempt to cater for users who have smaller displays, I > > > decided > > > > > > > > to develop someiGooglethemeswith half-height headers, using as > > > > > > > > a > > > > > > > > guide popularthemeslike "Tea House" and "Solar System", which > > > > > > > > include the attribute "header.height" in the XML. > > > > > > > > > When I tried to submit thethemes, I got an error message > > > > > > > > "Unknown > > > > > > > > attribute header.height". I can't see how this can be an > > > > > > > > "unknown > > > > > > > > attribute" when it is used in some of the most > > > populariGooglethemes > > > > > > > > of all time. > > > > > > > > > There is obviously some level of demand forthemeswith smaller > > > > > > > > headers, as evidenced by Google's recent abortive attempt to > > > truncate > > > > > > > > the header area on smaller displays. > > > > > > > > > Why is the "header.height" attribute not accepted on theme > > > submission, > > > > > > > > even though it is in use and supported? > > > > > > > -- > > > > > > You received this message because you are subscribed to the Google > > > Groups > > > > > > "iGoogleDeveloper Forum" group. > > > > > > To post to this group, send email to > > > [email protected]. > > > > > > To unsubscribe from this group, send email to > > > > > > [email protected]<google-gadgets-api%[email protected]> > > > <google-gadgets-api%[email protected]<google-gadgets-api%[email protected]> > > > > > > > . > > > > > > For more options, visit this group at > > > > > >http://groups.google.com/group/Google-Gadgets-API?hl=en. > > > > -- > > > You received this message because you are subscribed to the Google Groups > > > "iGoogle Developer Forum" group. > > > To post to this group, send email to [email protected]. > > > To unsubscribe from this group, send email to > > > [email protected]<google-gadgets-api%[email protected]> > > > . > > > For more options, visit this group at > > >http://groups.google.com/group/Google-Gadgets-API?hl=en. > > > -- > > You received this message because you are subscribed to the Google Groups > > "iGoogle Developer Forum" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group > > athttp://groups.google.com/group/Google-Gadgets-API?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "iGoogle Developer Forum" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group > athttp://groups.google.com/group/Google-Gadgets-API?hl=en. -- You received this message because you are subscribed to the Google Groups "iGoogle Developer Forum" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/Google-Gadgets-API?hl=en.
