[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [sc-dev] general question about the GUI helpfiles
Technically, I see no reason why we can't have an examples folder. The
stub generator would look in there, and if there is a file of the same
name, then the that is loaded and provides the basic creation scheme and
However, I'm a bit overloaded with getting all these EZ things the
unified. I don't know when the next 3.3 alpha or even beta is supposed
to happen, nor the final release. And I haves some work coming in again
soon, which I have to prepare for.
Remember, this involves copying over at least 45 example files,
adjusting them, and testing each example against swing. maybe it's not
too bad, since most can be fixed with search and replace.
In the end, it might be better, if someone copied the new help files to
swing, and made swing adjustments (any eager grad students out there?) .
Right now, swing users will be calling the stub, and then using the sc
help files for their main info, and going to the j files to find the
exceptions. Ideally both file collections would be up to date, and we
could have that key command, I once talked about:
cmd-d for basic help shft-cmd-d for more help, if there is any, defined
by a class method, moreHelp
cmd-y for a class, shift-cmd-y for redirects, or whatever, defined by a
class method, moreWhy ;-)
Julian Rohrhuber wrote:
>> We need to be able to auto generate the redirect stubs, since their
>> links must point to different paths. The only way to do this is to put
>> the examples in yet another file, and have that auto included by the
>> stub generator.
>> This starts to get complicated. I also don't relish the task of making
>> all those example cross platform compatible.
>> Some definitely already are not.
> I didn't want to complicate things, rather to avoid complications.
> My suggestion would be to use, wherever possible, platform independent
> code. Usually, code examples are just copied and pasted, so not using
> the redirectors means incompatible code.
> e.g. in SCPen helpfile, one example
> // Pen is a view redirector and returns SCPen in CocoaGUI:
> Pen.new // SCPen
> after this, all examples should be using Pen, not SCPen, I think. But
> maybe there are better arguments against this?
>> Julian Rohrhuber wrote:
>>> Wherever the view redirectors are to be compatible with different
>>> implementations, shouldn't the examples be moved to the redirects?
>>> This would encourage platform independent code. Sorry, I may have
>>> missed some of the discussion.
>> sc-dev mailing list
>> info (subscription, etc.):
>> archive: https://listarc.bham.ac.uk/marchives/sc-dev/
>> search: https://listarc.bham.ac.uk/lists/sc-dev/search/
sc-dev mailing list
info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml