Yes, I mean the book / pdf. On Thu, Dec 18, 2008 at 11:32 PM, Iceberg <[email protected]> wrote:
> > Agree with Yarko about at least we should emphasize TAG in document. > And one more comment, when you talking about "section x.x", do you > mean The Manual (http://www.amazon.com/Web2Py-Manual-Massimo-DiPierro/ > dp/0470432322<http://www.amazon.com/Web2Py-Manual-Massimo-DiPierro/dp/0470432322>)? > Just do not forget the users who only read the free > online document. :P I mean http://mdp.cti.depaul.edu/examples/default/api > > On 12月19日, 上午11时43分, "Yarko Tymciurak" <[email protected]> wrote: > > I think I agree with you on this - TAG could have a more prominent place > in > > documents - it's not mentioned at the top of the section on HTML Helpers, > > and yet is the "catchall / make-your-own".... it would be good to mention > at > > the beginning of section 5.2 (separate from how you fall on "LEGEND" as > > a desirable standard helper). Instead of getting billing at the intro > or > > section 5.2 on p. 118, it get's hidden at the end of the section under > > "Custom Helpers". > > > > On Thu, Dec 18, 2008 at 8:38 PM, Iceberg <[email protected]> wrote: > > > > > It seems LEGEND does not qualify for either of the excluding criteria > > > mentioned by Massimo. So I think it should be in. > > > > > Denesl's solution is cool and helpful, I did not know that trick, > > > really thanks! But, IMHO, TAG.LEGEND(...) is not intuitive to > > > beginners of web2py. I mean, come on, who will go over API document > > > (http://mdp.cti.depaul.edu/examples/default/api) and notice LEGEND is > > > NOT there? Besides, the usage of TAG is not mentioned in API document > > > nor in example section. Sorry if it is in somewhere but I missed it. > > > > > On Dec 18, 9:13 pm, mdipierro <[email protected]> wrote: > > > > We tried to list the most common ones excluding those that should not > > > > be used (like FONT) and those that can be mimicked by other tags > using > > > > CSS. Not sure this qualifies a logic behind our choice. Definitively > > > > we do not want to have a comprehensive set of tags, in particular > > > > since TAG was implemented. > > > > > > Massimo > > > > > > On Dec 18, 5:24 am, mmstud <[email protected]> wrote: > > > > > > > What is the logic defining some html element classes and not > defining > > > > > some anyway? I have created my own library of html elements, that i > > > > > use on web2py, which at least tries to follow standard html > > > > > specification. > > > > > > > -Marko > > > > > > > On 17 joulu, 17:42, DenesL <[email protected]> wrote: > > > > > > > > You can create it using the TAG helper. > > > > > > > > t=TAG.LEGEND('a','b',_c='d') > > > > > > t.xml() produces > > > > > > '<LEGEND c="d">ab</LEGEND>' > > > > > > > > On Dec 17, 9:55 am, Iceberg <[email protected]> wrote: > > > > > > > > > Hi Massimo, > > > > > > > > > Why there is a definition of FIELDSET in html.py, but there is > not > > > a > > > > > > > LEGEND? They usually show up together. Would you please append > this > > > in > > > > > > > next version of web2py? > > > > > > > class LEGEND(DIV): tag='legend' > > > > > > > > > Regards, > > > > > > > Iceberg > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" 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/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
