Moving Components towards Down

[Meena]

Hi,

I have created a login page,which contains the Text boxes,i can't
move that boxes after certain place towards down,I have used <spacer
width="...">within the <vgroup>too,but its not helpful,How can i move
those boxes towards down.

Thanks in Advance,
Meena

[Dawn Wolthuis]

<spacer height=... might do the trick. --dawn

--
Dawn M. Wolthuis

Take and give some delight today

[Meena]

Hi Dawn,

Thanks a lot,Its working fine.

Meena

On Oct 28, 7:04 pm, Dawn Wolthuis <dw...@tincat-group.com> wrote:
> <spacer height=... might do the trick.  --dawn
>

[Derek Day]

One can also use layout='none' on group tags to avoid generating extra tables and then use css positioning to control certan types of layouts. Done by someone who knows CSS well this can lead to much simpler and better performing page layouts--done badly of course this can be worse than a GOTO!

The following rules help me, even if they aren't strictly true =)

Derek

--use tables when you want tables--
--use position: absolute for relative positioning--
--use position: relative for absolute positioning--
--use position: fixed with great care, IE is broken mostly--
--its not confusing, just convoluted--
--you have to undestand the box model if you want pages to not look boxy--
--yes I know, these are fantastic oxymorons--

[Meena]

Derek

Thanks,you gave more ideas to us

Meena

> > Take and give some delight today- Hide quoted text -
>
> - Show quoted text -

[Derek Day]

**In regards to my rule below --use tables when you want tables--, I
always try layout="none" in as many groups as possible (particularly
vgroups, since they are usually equivalent to default flow.

I just wrote up the following for a WRC Investigation log entry, and
since I've been promising this information for a while and it is
appropriate for this thread, here it is. This is all based on
documentation and Eric Meyers book and websites/blogs and so on, as well
as information gleaned from the ie7-js project
(http://code.google.com/p/ie7-js/). Maybe we can recruit Eric to join
the Zen Community, or to write an O'Reilly book on Zen CSS!

=====

Zen Applications may be converted to use non-quirks mode with browser
independent layouts. I have used the following approach to create
layouts that work for IE 6,7,8, FF 3, 3.5 (why bother with older FF
versions since the FF user base is able to upgrade?), Safari, and
Chrome. So with the caveat, that many of the built-in components assume
browser quirks modes and use some user agent sniffing, and will
therefore break, the following may be used for your "killer" pages.

The technique involves removing all spacer tags, and using layout="none"
or layout="customClass:layoutMethod" everywhere that you do not actually
want an extra HTML table, and using the HTMLDTD page parameter (to
trigger non-quirks mode). The server-side layout manager horizontal and
vertical layouts use html tables, so the easiest way to rid yourself of
these is to use layout="none" or use custom group components that
override the default value of this attribute.

I use the document.compatMode JavaScript property to debug the page to
find errors that cause browsers to go into quirks mode, but from here it
becomes an exercise in standard CSS techniques. From non-quirks mode and
without extra tables, the only CSS Hacks that I use are conditional
comments from IE LT 7; for this I use css expressions(dynamic
properties), due to the fact that IE 6 does not support resolving
competing position constraints. [The expressions are not too difficult]

The trick of course involves any custom components or %ZEN library
components that use tables extensively, it may be necessary to rewrite
some of these or fall back to quirks mode for some pages. With
non-quirks mode, however it is generally easier to grab certain public
widgets or widget libraries and adapt them for use in Zen. And when
rewriting any library component to use no or fewer tables.


~Derek

Meena wrote (10/30/09 10:04 AM):

[Dawn Wolthuis]

This is great, Derek! We are committed to using (with extensions)
delivered components to the extent feasible, so I am hopeful that you
will also be rewriting components in the future to get us out of
quirks mode? Are there plans for this in 2010.1?

[As an aside, if there will be rewritten components for non-quirks
mode, it would be great if the new components were written with
server-side javascript rather than COS so they are more easily
subclassed (with method overrides) by those for whom COS is an nth
language.]

Cheers! --dawn

[Bill McCormick]

There are no plans to change our components in this manner. We are
adding components at times that remove the need to tables as an
alternative


Bill McCormick
Product Manager
Development Technologies
+1 617 621 0600
bill.mc...@intersystems.com

[Derek Day]

This is a very good thing, most components do fine with positioning when layout="none", the use of tables internal to the controls does not generally cause a problem when proper css selectors are used.

New components will make it easy to use more lightweight implementations when they become available from either InterSystems development or the community!

~Derek

________________________________________
From: intersys...@googlegroups.com [intersys...@googlegroups.com] On Behalf Of Bill McCormick [bill.mc...@intersystems.com]
Sent: Tuesday, November 03, 2009 09:05
To: intersys...@googlegroups.com
Subject: [InterSystems-Zen] Re: Non-Quirks Mode: CSS Positioning of Zen Components

[Dawn Wolthuis]

Yes, it sounds like a very good thing. I understand if previous
components are not converted, but new ones take their place instead.
Either way, we will look for components that do not use tables for
layouts and see what it will take to move toward non-quirks mode in
the future.

We are not savvy enough (and have too few hours) to write a bunch of
new components to replace existing ones. Is there an easy way to
determine which components work great with layout="none" and a DOCTYPE
on the document and which ones really can't be used handily that way?
My question might not exactly be the right one -- I'll look at what
this can do for us because I would really like to have a doctype after
we get past a few more hurdles. Thanks. --dawn

[Derek Day]

I just posted this example to the Community Articles section. Enjoy!
http://groups.google.com/group/intersystems-zen/web/example-using-non-quirks-mode-to-create-a-browser-independent-layout