Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Close the gap between WATag, WACompound and WAComponent #237

Open
GoogleCodeExporter opened this issue Mar 25, 2015 · 3 comments
Open

Close the gap between WATag, WACompound and WAComponent #237

GoogleCodeExporter opened this issue Mar 25, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

Several users criticize or complain about the semantic gap between XHTML tags 
(WATag), compound 
(WACompound) tags and components (WAComponent). This issue should investigate 
bringing these 
things closer together, or at least make more clear when to use what.

Original issue reported on code.google.com by renggli on 10 Nov 2008 at 7:20

@GoogleCodeExporter
Copy link
Author

Original comment by renggli on 10 Nov 2008 at 7:23

  • Added labels: Priority-Low, Type-CleanUp
  • Removed labels: Priority-Medium, Type-Defect

@GoogleCodeExporter
Copy link
Author

WACompound's subclasses could probably be implemented as painters or possible 
dropped
entirely.

Original comment by jfitz...@gmail.com on 20 Feb 2009 at 9:10

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

Related to #2: I've registered WADateSelector as an application (WADateSelector 
registerAsApplication: 
'whenDate') then opened it in a browser. When I toggle halos the last field is 
outside the halo. The same thing 
happens with WATimeSelector. What's up with that? This is on 
Seaside2.8a1-lr.578 (and the same on pmm.583 
which is the latest).

Original comment by renggli on 7 Mar 2009 at 8:36

  • Added labels: ****
  • Removed labels: ****

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant