Commenting "unsupported" functions (as well as supported functions)

Justin Obara obara.justin at
Mon Dec 13 16:29:00 UTC 2010

I took a look over Harris and my changes, and none of them seem to have created any functions that should be marked as unsupported. Golam's changes to FLUID-3391 may be a different situation and you should probably check in with Antranig on this.


On 2010-12-13, at 11:01 AM, Justin Obara wrote:

> Looked through progress, I don't think there is anything there that needs to be marked as unsupported. I'll take a look a reorderer since harris isn't here.
> Thanks
> Justin
> On 2010-12-13, at 10:32 AM, Cheetham, Anastasia wrote:
>> One of the remaining tasks before release is to identify any "public" functions/methods/instance variables/options that we don't actually want users to use, and comment to that effect in the code:
>> I have some sense of different areas of the code in which these comments are needed, and I'll be pinging people about it once I've had a quick look over the code. Likely suspects:
>> Antranig: framework changes
>> Mike: Inline Edit (this isn't actually for 'unsupported' things, but descriptions of newly public functions that are supported)
>> Justin: Progress
>> Colin/Mike: Uploader
>> Harris: Reorderer
>> There may be more, I'll know once I check the code.
>> -- 
>> Anastasia Cheetham     Inclusive Design Research Centre
>> acheetham at            Inclusive Design Institute
>>                                       OCAD University
>> _______________________________________________________
>> fluid-work mailing list - fluid-work at
>> To unsubscribe, change settings or access archives,
>> see

More information about the fluid-work mailing list