Ok, currently working on it.
> >I have most of the dialog and spelling
> >window coded.
>
> Great! Do you have a screen shot of what you've done so far?
>
http://argus.itg.uiuc.edu/~shack/abisource/options.gif for a current picture
> >What is the process for checking in files? I assume anoncvs does not allow
> >checkins. Do we sent patches, or apply for CVS access?
>
> Yeah, we don't allow anonymous commit access to our live tree (for obvious
> reasons). This means that the developers who *do* have write access wind up
> spending a portion of their time applying patches submitted by other
> contributors.
>
> trust. Just show us the code. It pretty much speaks for itself. :-)
I can handle this method.
Have some quick questions...
I have some questions about the internal storage. These options, most of them
if not all, will be appPersistant. Where will the information be stored? I
know that the AppPers class takes care of initializing one instance and such.
But, my question is, is their some global repository of configurations data?
or should I query the dialog (yuck)?
I've not looked around too much as of yet, but i'll be needing some place to
start.
And on a different note...
Is there a running features/wish list with the priorities?
I heard that there are vi keybindings? Any help pointing me in the right
direction.
Thanks
-shack
