Re: Headcount

From: Joseph A. Knapka <[email protected]>
> Samuele Pedroni wrote:
> >
> > From: Magnus Lie Hetland <[email protected]>
> >
> > > Hi!
> > >
> > > It's time we bumped ourselves along and go the first alpha together.
> > > To that end, I'd like to know how many of the developers are currently
> > > available for some programming work. It would be really neat if we
> > > could get alpha 1 out by the end of september, so I guess I'm mainly
> > > interested in whether people can chip in a bit in the next couple of
> > > weeks. Please respond even if you're too busy -- I would just like to
> > > know what the current status is.
> > >
> > > Another issue is the remaining work: In what state are the various
> > > back-ends compared to the 0.1.1 functionality (i.e. how fare are they
> > > from working at all)? How far are they from the goals for the first
> > > alpha (from the TODO file)?
> > >
> > > Some of you have hinted that you might get some time soon to work on
> > > this; if you could scrounge up some of that time now, that would be
> > > great... Because we really need to start moving again. Getting this
> > > alpha out will be a major milestone: We'll have a function version of
> > > the new architecture, and a version of Anygui that is fit for
> > > polishing and stabilising (and expanding, of course ;).
> >
> > Hi, I can help a bit with fixing bugs, especially in javagui but not adding
> > major functionality.
> >
> > Btw I have working version of tk, Wrappers and Proxies using widget = None
when
> > the widget has not been created instead of DummyWidget and exception
trapping.
> >
> > Should I commit it?
>
> IMO, yes. (I hope the changes to tkgui weren't too extensive.)
>

there's a

if not self.widget: return

at the top of all setFoo methods (except setContainer's that trigger widget
creation)

and an assert self.widget...

at the top of all getFoo methods.

I  should check a larger subset of the tests and then it could be committed.

Another question is:    now  proxy.wrapper is kept in state and there's a
comment asking whether it should be that way.

For now I have added a non-in-state _wrapper_set flag that is set to true when
wrapper is set to a concrete wrapper.
I need to check for wrapper presence in push and pull that are called by the
Attrib constructor before wrapper is set
in order to do the right thing, i.e. return without after doing nothing.

Should wrapper be out of state and become _wrapper, then we need a getWrapper
or all occurences of wrapper
in the backends should be renamed _wrapper.

regards.



-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390