|
Hello,
I was just wondering if someone could point me to some documentation for the XML schema used when defining modes. I have found the window system Javadoc... http://bits.netbeans.org/dev/javadoc/org-openide-windows/org/openide/windows/doc-files/api.html ... and while this alludes to the mode XML, it does not go into details of how to define new modes. Many thanks. |
|
Hi,
The easiest way to do this is with the new window layout designer. Have a look at Geertjan's blog post:
Best wishes, Hermien PELLISSIER On Wed, Feb 22, 2012 at 4:46 PM, nwb159 <[hidden email]> wrote: Hello, |
|
In reply to this post by nwb159
On 02/22/2012 03:46 PM, nwb159 wrote:
> Hello, > > I was just wondering if someone could point me to some documentation > for the XML schema used when defining modes. I have found the window > system Javadoc... > > http://bits.netbeans.org/dev/javadoc/org-openide-windows/org/openide/windows/doc-files/api.html > > > ... and while this alludes to the mode XML, it does not go into > details of how to define new modes. > > Many thanks. Gj |
|
In reply to this post by Hermien Pellissier
This looks great - a great feature to complement the platform.
Unfortunately, for the time being, this is not an option as the NB platform application doesn't support 7.1 as yet. Is there an alternative that might work for me in the mean-time? On 22/02/12 14:53, Hermien Pellissier wrote: Hi, |
|
Hi,
I would suggest creating a new platform application to play around with, and see what the output of the wizard looks like. Then you can duplicate the structure in your older application. Note that the mode file(s) are also referenced in the layer file - don't forget to duplicate that too. :) Best wishes, Hermien
On Wed, Feb 22, 2012 at 5:27 PM, nwb159 <[hidden email]> wrote:
|
|
This works to some extent. For instance, I can borrow some modes
from the generated XML files. However, I think there's some
difficulty in using the built in modes. I could over come this by
redefining all the modes, including things like explorer. However,
would I have to do this in all modules that wish to dock top
components into explorer, since the mode XML is imported though a
moudle's layer.
Some documentation of the mode XML would be really helpful, at least to understand what the <constraints> and <path> elements do, since these seem to have the greatest bearing on where the new mode appears. On 22/02/12 15:31, Hermien Pellissier wrote: Hi, |
|
On 02/22/2012 05:25 PM, nwb159 wrote:
This works to some extent. For instance, I can borrow some modes from the generated XML files. However, I think there's some difficulty in using the built in modes. I could over come this by redefining all the modes, including things like explorer. However, would I have to do this in all modules that wish to dock top components into explorer, since the mode XML is imported though a moudle's layer. http://www.netbeans.org/dtds/mode-properties2_0.dtd Gj , at least to understand what the <constraints> and <path> elements do, since these seem to have the greatest bearing on where the new mode appears. |
|
On 02/22/2012 05:29 PM, Geertjan Wielenga wrote:
On 02/22/2012 05:25 PM, nwb159 wrote:This works to some extent. For instance, I can borrow some modes from the generated XML files. However, I think there's some difficulty in using the built in modes. I could over come this by redefining all the modes, including things like explorer. However, would I have to do this in all modules that wish to dock top components into explorer, since the mode XML is imported though a moudle's layer. Plus, an example: https://blogs.oracle.com/geertjan/entry/creating_a_new_split_in Gj
|
|
Cheers guys. A little trial and error later and I have my mode
docking below the built in explorer...
Here are the constraints. <constraints> <path orientation="horizontal" number="20" weight="0.5"/> <path orientation="vertical" number="100" weight="0.5"/> </constraints> I really appreciate all your help. On 22/02/12 16:41, Geertjan Wielenga wrote: On 02/22/2012 05:29 PM, Geertjan Wielenga wrote:On 02/22/2012 05:25 PM, nwb159 wrote:This works to some extent. For instance, I can borrow some modes from the generated XML files. However, I think there's some difficulty in using the built in modes. I could over come this by redefining all the modes, including things like explorer. However, would I have to do this in all modules that wish to dock top components into explorer, since the mode XML is imported though a moudle's layer. |
| Powered by Nabble | See how NAML generates this page |
