[
https://issues.apache.org/jira/browse/OFBIZ-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux closed OFBIZ-297.
---------------------------------
Resolution: Not A Problem
Assignee: Jacques Le Roux
Nobody cares, closing
> Have screen widgets render <a name=""> for in-page links
> --------------------------------------------------------
>
> Key: OFBIZ-297
> URL: https://issues.apache.org/jira/browse/OFBIZ-297
> Project: OFBiz
> Issue Type: New Feature
> Components: framework
> Affects Versions: Trunk
> Reporter: Marco Risaliti
> Assignee: Jacques Le Roux
> Priority: Minor
> Attachments: proposed-anchorScreenWidget.patch
>
>
> Copy of http://jira.undersunconsulting.com/browse/OFBIZ-753 from Leon Torres.
> ============================================
> Some pages can be very long, so it would be extra helpful to have a way to
> jump to a particular part of the page using the HTML anchor tags <a
> name=""></a>.
> For instance, if the screen widget allowed,
> <anchor name="ListOrders"/>
> <label style="header">This is a List of Orders</label>
> <include-form name="ListOrders"/>
> And the ListOrders form had a header-link with #ListOrders as part of the
> target, it would jump back to the location of the anchor.
>
>
> All Comments Work Log Change History Sort Order:
> Comment by Leon Torres [17/Feb/06 07:20 PM] [ Permlink ]
> Here's an update to the screen widget system that allows the use of <anchor
> name=""/> to render <a name=""></a>.
> Not sure if the tree widget or anything else needs it or not, please double
> check.
> Comment by David E. Jones [26/Feb/06 01:15 AM] [ Permlink ]
> I'll have to think about this a bit more... It probably does make the most
> sense to put it in the screen widget, but this seems right now to me to be a
> little too close to HTML and not generic enough for use in non-HTML rendering
> of screens. We don't have anything to do this right now, but it is very much
> part of the intent to keep this direction open and explicit.
> If you have any ideas along these lines let's discuss them, and I'll think
> about it as well. Perhaps just an element like this is generic enough... but
> there is probably something more generally applicable we could do.
> Comment by Si Chen [27/Feb/06 08:56 AM] [ Permlink ]
> David,
> I see what you mean. DocBook also has an "anchor" tag:
> http://www.docbook.org/tdg/en/html/anchor.html
> Do you think that qualifies it as a "universal" or "generic" document format
> concept?
> Si
> Comment by David E. Jones [12/Mar/06 10:23 PM] [ Permlink ]
> Si,
> Yes, and I guess even more significantly HTML has such a concept (I'm
> guessing there's still a lot more HTML being generated through the screen
> widget than DocBook). That's what concerns me the most: it's a very document
> oriented concept and not something that you find as much in applications, or
> in "screens".
> Still, I think it's a useful concept and perhaps one that would be nice to
> have as a special screen widget element because if I understand correctly
> what you're shooting for it is to have a reference point for the beginning of
> different sections of a screen.
> And if it is really for the beginning point of a section of a screen... we
> already have a nice place that would fit in: the section element. We could
> just change the HTML generation to create an anchor (<a name=""/>) for the
> start of each section if the section has a name associated with it...
> Does that sound like it would hit more or less the goal you are shooting for?
> Comment by Leon Torres [16/Mar/06 04:39 PM] [ Permlink ]
> David,
> I don't like the idea of using section element names for two reasons:
> 1) I would have to wrap each block that needs such an anchor in a <section>
> and then a <widgets>, creating additional lines of code. While it would be
> nice to reuse the <section> code and not introduce more form elements, in
> reality it would just shift additional code to the user the form-widget.
> 2) Anchors are important elements of many UI applications which work with
> complex documents. For example, the Eclipse IDE, like most editors, allows
> you to click on a method name and then scrolls your code to the line where
> the method is defined. Thus, the method name could be thought of as an
> anchor.
> So I still think we should have an anchor tag.
> - Leon
> Comment by Si Chen [22/Mar/06 07:58 AM] [ Permlink ]
> David,
> So do you not like this patch? If not, just let us know, and I'll close out
> the issue, and we'll do it some other way.
> Thanks,
> Si
> Comment by Marco Risaliti [13/Sep/06 04:27 PM] [ Permlink ]
> What to do here, close it or move it.
> Thanks
> Marco
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
