Hi,
is there anyway to ensure that 1 part is also 1 built part?
So if i change my config automatically to include only the "newly updated"
part. Then i build the project. I would be able to copy only the changes
(and the main build) to the production. And in this case leave all the other
plugins
Defero wrote
> Hi,
>
> in this case your project has to be recompiled everytime for the changes
> to appear?
>
>
> Regards,
> Defero
Yes, beacause the generator needs to resolve all the dependencies ... So in
the sense of your original question, yes, you will need their source to
create the com
Hi,
in this case your project has to be recompiled everytime for the changes to
appear?
Regards,
Defero
--
View this message in context:
http://qooxdoo.678.n2.nabble.com/How-to-make-parts-independent-tp7587856p7587859.html
Sent from the qooxdoo mailing list archive at Nabble.com.
--
When qx.ui.table.Table has set alwaysUpdateCells property, it highlights
selected row on second click. It happens every time when table gets focus.
--
___
qooxdoo-devel mailing
Hello,
I had a similar problem trying to implement plugins via the parts
architecture. I've been told that this was not what the parts system had
been designed for, so it is kind of a hack. But it works:
Since the part loader system depends on static code analysis, you need to
name the parts expl
Hi,
for a while now we were using parts in our applications, which work well
when we're the one defining these parts.
But soon, alot of external programmers will start using the communication
(and some ui) layers that we setup.
So my question is, is there any flexibility in the way the applicatio
