OK, thanks for your answer. I will split the files, migrate and merge back.
Sebastian Werner wrote:
>
> Not using one class per file I problematic. It will break a lot of stuff
> e.g. things like the API viewer, the include sort system, the file
> tracer (to find out the name of a class and
Not using one class per file I problematic. It will break a lot of stuff
e.g. things like the API viewer, the include sort system, the file
tracer (to find out the name of a class and its requirements). I would
say it by far easier to split files up than to support such things in
our build syst
Hello David,
> Hi,
>
> Is there a technical reason why the migration is only possible when I have
> one class for one file?.
>
qooxdoo always had the concept of one class per file and for the python
patch file, which transforms the old classes into the new class
definition assumes exactly that
Hi,
Is there a technical reason why the migration is only possible when I have
one class for one file?.
As a Java programmer I think this is a good convention, and also for a
general purpose lib like qooxdoo, where each user selects what he wants, and
can create custom builds.
But in my case, e
