Every part of it which is documented in http://i3wm.org/docs/ipc.html
will be stable.
On Tue, Sep 9, 2014 at 9:19 PM, Sargrad, Dave
wrote:
> I am building some automation to be used with i3, with an eye towards remote
> management of a suite of i3 desktops.
>
> I am using the latest i3 (4.8). I need to make the design decision to use
> high level tools such as "i3-save-tree", or to build my own "tree
> parsing/manipulation tools".
>
> I would like to understand how stable the tree structure is. If its
> relatively stable, then I think its pretty safe to build my own tools that
> work with the i3 tree. Future changes to the tree would be something that I
> can work with in this case. However if the tree is expected to change a lot
> then perhaps I don’t want to build my own tools that work with the tree
> structure.
>
> In a sense I am wondering if I should treat the tree structure (and
> specification) as a "public" or a "private" spec. Certainly for a given i3
> release I can treat it as public, but I don’t want to create automation that
> will become obsolete with future releases of i3.
>
> Id appreciate any thoughts or recommendations.
> -
> This message is intended only for the addressee and may contain information
> that is company confidential or privileged. Any technical data in this
> message may be exported only in accordance with the U.S. International
> Traffic in Arms Regulations (22 CFR Parts 120-130) or the Export
> Administration Regulations (15 CFR Parts 730-774). Unauthorized use is
> strictly prohibited and may be unlawful. If you are not the intended
> recipient, or the person responsible for delivering to the intended
> recipient, you should not read, copy, disclose or otherwise use this message.
> If you have received this email in error, please delete it, and advise the
> sender immediately.
> -
--
Best regards,
Michael
