Thanks Holger
I havent seen notice about the doc pack - look forward to it, or an alpha
release if you want me to test it :-)
the main layout glitch is that the project tabs (import/export/manage) etc
do not show completely or size properly (i.e. showing More...) until you
select a different tab or resize the window,
cheers
Rob
On Sunday, 19 January 2020 05:23:38 UTC+11, Holger Knublauch wrote:
>
> Hi Rob,
>
> On 15/01/2020 17:49, Rob Atkinson wrote:
>
> Love the new 6.3 editor :-)
>
> I've tried looking into code but not getting terribly far trying to work
> out what are the possible values teamwork:defaultLayout
>
> The only value i've found that works so far is "TabularEditor"
>
> When i make this default, the "available layouts" gives me a bunch of
> options who all claim have "default" = false.
>
> I see there is teamwork:defaultForProjectType i could attach to a
> Layout...
>
> I dont see a property equivalent to the deprecated projectEditorClassOption
>
> so a few obvious questions:
>
> 1) what are the range of values available for defaultLayout ?
> 2) how does one add to the list of available layouts (including where
> should one put the declarations if they are not properties of the
> projectType)
> 3) If one saves a layout, how can it be exported so i can package it with
> a custom asset collection as the default layout?
>
>
> The values of teamwork:defaultLayout map to fields of the JS object called
> Layouts. For example, there is
>
> export const TabularEditor = {
> config: {
> content: [
> {
> type: 'row',
> content: [
> {
> type: 'column',
> width: 50,
> title: 'Search',
>
> content: [
> {
> component: 'Search',
> type: 'react-component',
> height: 100,
> },
> ],
> },
> {
> type: 'column',
> width: 50,
> content: [
> {
> component: 'Form',
> height: 100,
> },
> ],
> },
> ],
> },
> ],
> },
> };
>
> The idea is that 3rd party code can add their own constants through
> Layouts.MyLayout = ... and then reference it via teamwork:defaultLayout
> "MyLayout". You can produce the values (nested arrays) either by hand or by
> looking at the saved layouts (which are stored as instances of
> teamwork:Layout in Repositories/urn_x-evn-user-data.xdb).
>
> We are still in the process of rolling out the documentation and starter
> pack for customers to inject their own JavaScript code for 6.3 onwards .
> Did you get informed about that already?
>
>
>
> ( noticed a few tab option layout glitches - is there a patch release
> planned soon?)
>
>
> If you have specific glitches to report, we'd love to hear them to make
> sure we address them in 6.3.1
>
> Holger
>
>
>
> Cheers
> Rob
> --
> You received this message because you are subscribed to the Google Groups
> "TopBraid Suite Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected] <javascript:>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/topbraid-users/2e81f6d2-3bfe-45f2-81fb-5ffeaf7734af%40googlegroups.com
>
> <https://groups.google.com/d/msgid/topbraid-users/2e81f6d2-3bfe-45f2-81fb-5ffeaf7734af%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
>
>
--
You received this message because you are subscribed to the Google Groups
"TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/2474df1f-c5fe-4434-82fe-0e0c5479f56f%40googlegroups.com.
