I think things that are marked private should not appear in the schema. If you need to poke at private things, then you should:

a) Discuss with the designer why these things are private and if they should be public instead b) Have to jump through a hoop (like adding a manual override) because you are poking at a private API

Because of that, I would say you should file a bug to back out your changes and make a change to the test instead.

On 2008-07-17, at 10:42EDT, Henry Minsky wrote:

I think we need the schema to include everything that might need to
have "override" added automatically by the
tag compiler.  I guess we do support  a manual "override" attribute on
methods in LZX that users are supposed to be able to useif they need
to force an override on a method, but it would be nice to do this
automatically
whenever possible.





On Thu, Jul 17, 2008 at 10:35 AM, Donald Anderson <[EMAIL PROTECTED]> wrote:
Approved.
Do we want the new schema builder to include nonpublic events
(and methods and attributes)?  If it's helpful, we could have a
access="...."
attribute in case you want to distinguish.
- Don
On Jul 16, 2008, at 8:34 AM, Henry Minsky wrote:

Change 20080716-hqm-m by [EMAIL PROTECTED] on 2008-07-16 08:32:32 EDT
  in /Users/hqm/openlaszlo/trunk4/WEB-INF/lps/schema
  for http://svn.openlaszlo.org/openlaszlo/trunk/WEB-INF/lps/schema

Summary: make schema more accurate; add some events for LzDataElement

New Features:

Bugs Fixed:

Technical Reviewer: pbr
QA Reviewer: dda
Doc Reviewer: (pending)

Documentation:

Release Notes:

Details:

Some more events on datanode (that aren't really public, but I wanted to
add handlers for for testing) needed to be declared in the schema


Tests:

test/lfc/data/alldata
smokecheck

Files:
M      lfc.lzx

Changeset: http://svn.openlaszlo.org/openlaszlo/patches/20080716-hqm-m.tar


--
Don Anderson
Java/C/C++, Berkeley DB, systems consultant

voice: 617-547-7881
email: [EMAIL PROTECTED]
www: http://www.ddanderson.com







--
Henry Minsky
Software Architect
[EMAIL PROTECTED]

Reply via email to