I hesitate to use CSS to make up for a framework limitation. Sure it would work, but it just strikes me as wrong.
--Steven On 7/25/05, Robert Zeigler <[EMAIL PROTECTED]> wrote: > Ah, then, that /does/ complicate things quite a lot. :) > what about using css to accomplish the trick? > > <h3 style="position: absolute; top: 15px;">Name</h3> > Or something like that? If you use absolute positioning, > then everything that comes below it will be shifted up as if > it wasn't there... the feasibility of this depends a lot on > how things are being laid-out, but... > You also might be able to use relative positioning and negative > margins/positioning (or, if you have nested div's, etc., then you could > use also use absolute positioning in this fashion...) > > Robert > > Steven Wisener wrote: > > Well, I simplified my example a bit. There are actually two forms on > > the page, both with the orderId hidden field. Also the first form > > isn't always rendered, since it is only available to users with > > administrative rights. I could certainly accomplish it with some hairy > > conditional logic. I think a more elegant solution is to just wait for > > one of the hidden components to render and then render the Insert. > > > > I'll take a look at the Body component and see if there's anything > > useful. Thanks for the suggestion! > > > > --Steven > > > > On 7/25/05, Robert Zeigler <[EMAIL PROTECTED]> wrote: > > > >>can't you just move your form and hidden component? > >>So, instead of: > >><h3><span jwcid="@Insert" value="ognl:order.name"/></h3> > >><form jwcid="@Form"> > >> <hidden.../> > >> > >>You'd have: > >><form jwcid="@Form"> > >> <hidden.../> > >><h3><span jwcid="@Insert" value="ognl:order.name"/></h3> > >> > >>It's hard to say without seeing more information about your template, > >>but, you can certainly put the form and hidden tags wherever they make > >>the most sense on the page, and keep the rest of the form components > >>where they belong. :) > >>Or, you can move the name of the order via css to an appropriate location... > >>Or, you could create a wrapper component that buffers it's input (take a > >>look at the body component code for how to accomplish that, in detail).. > >>. it involves the use of nested writers, but I've never used the > >>technique, personally. > >> > >>Robert > >>Steven Wisener wrote: > >> > >>>My problem seems pretty simple. I've got an order/line item type > >>>situation. The order page links to the line item listing page with a > >>>DirectLink with the orderId as a parameter. The line item listing page > >>>has a form for editing each line item (with a ListEdit component). The > >>>line item form remembers the orderId with a Hidden component in the > >>>form. > >>> > >>>Now here's the issue: I want to display the order name ABOVE the form. > >>>The order cannot be retreived until the listener method of the Hidden > >>>component populates the order. Is there any way to defer rendering of > >>>the order name Insert component until the Hidden field in the form is > >>>rendered? Or perhaps there's an easy way around this that I'm missing? > >>> > >>>Thanks, > >>> > >>>--Steven > >>> > >>>--------------------------------------------------------------------- > >>>To unsubscribe, e-mail: [EMAIL PROTECTED] > >>>For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > >>--------------------------------------------------------------------- > >>To unsubscribe, e-mail: [EMAIL PROTECTED] > >>For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
