> that's one of the reasons i'm insisting on bringing this up. even if
> you don't want to include my soap contrib in the mainstream qooxdoo
> package, you should be ready to do so *before* freezing the api.
>
> eg. remember how it was VerticalBoxLayout and now it is layout.VBox ?
> the same thing applies here, there has to be:
>
> qx.io.rpc.Json,
> qx.io.rpc.Soap,
> qx.io.rpc.Xml etc.,
>
> and not
>
> qx.io.Rpc
> qx.io.Soap
> qx.io.XmlRpc etc.
Wait, this is more far reaching then just adding another API. You want
to re-structure the existing classes.
>
> i guess this point this merits an enhancement bug. i can file a bug
> report if you think i should.
I'm not the right one to judge this. Maybe others like Andreas or Fabian
can comment on this.
> i can say that this code doesn't derive from mateo casati's client
> anymore, it's rewritten. there are code fragments here and there, but
> the logic is completely different.
Then why do you maintain the copyright notices in the code and readme?!
> well, as i did not get any feedback about the current state of the
> soap api, i can't freeze it, and i won't write documentation for an
> unfrozen api.
I think you're wrong here. Documentation is not something nice and extra
which you add as an icing at the end of the development cycle. We don't
follow the waterfall model anyway. Documentation is an intrinsic part of
any piece of software, at any stage of its life cycle. Documentation is
necessary to convey what the software is about and how to use it. You
write a piece of software and the docs at the same time (and the tests,
if you're really into it). If you change the software, you change the docs.
Docs are an important inroad to your API if you want other people to
evaluate it. You complain you don't get feedback, but maybe one reason
is because your contrib is not in good shape. Ever considered this?!
> as for the whitespace, the moment this code is reformatted to respect
> qooxdoo style, it stops being my concern -- i despise qooxdoo coding
> style. (seriously guys, are you using 16:9 monitors vertically or
> something? i can see the frikkin "members : {" line, there's no point
> in announcing it with an ugly 9-line comment block!)
Well, you don't have to like it. But you have to handle it. As I said,
the attractivity of your API for the framework also depends on how easy
it is for others to see how it fits in. If you just throw bits and
pieces around, it's much harder to assess their merrit.
T.
>
>
>
>> HTH. Maybe Andreas can comment better on this.
>>
>>
>
>
> thanks for your time thomas, appreciated. i now have a better image of
> your expectations.
>
> best regards,
> burak
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
------------------------------------------------------------------------------
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
