something like this, if this looks
good,
I'll make the required changes.
The layout of API Reference on the Site:
*OFBiz API Reference*
- *Trunk API Reference*
- *Release 17.12 API Reference*
- *Next Release API Reference*
t; > Le 16/07/2020 à 11:43, Pawan Verma a écrit :
> > > > Thanks, Jacques, All for the response.
> > > >
> > > > Yes, Makes sense. So, It will look something like this, if this looks
> > > good,
> > > > I'll make the required changes.
> > > >
> > > > The layout of API Reference on the Site:
> > > > *OFBiz API Reference*
> > > >
> > > > - *Trunk API Reference*
> > > > - *Release 17.12 API Reference*
> > > > - *Next Release API Reference*
> > > >
> > >
> >
>
; > Jacques
> >
> > Le 16/07/2020 à 11:43, Pawan Verma a écrit :
> > > Thanks, Jacques, All for the response.
> > >
> > > Yes, Makes sense. So, It will look something like this, if this looks
> > good,
> > > I'll make the required changes.
> &g
> good,
> > I'll make the required changes.
> >
> > The layout of API Reference on the Site:
> > *OFBiz API Reference*
> >
> > - *Trunk API Reference*
> > - *Release 17.12 API Reference*
> > - *Next Release API Reference*
> >
>
+1
Jacques
Le 16/07/2020 à 11:43, Pawan Verma a écrit :
Thanks, Jacques, All for the response.
Yes, Makes sense. So, It will look something like this, if this looks good,
I'll make the required changes.
The layout of API Reference on the Site:
*OFBiz API Reference*
- *Trunk API
Thanks, Jacques, All for the response.
Yes, Makes sense. So, It will look something like this, if this looks good,
I'll make the required changes.
The layout of API Reference on the Site:
*OFBiz API Reference*
- *Trunk API Reference*
- *Release 17.12 API Reference*
- *Next Release API
Hi Pawan,
Indeed, next is for now more an internal concept.
But, like it's now clear for stable - thanks to the demo, we could explain this concept to users. It's simple: the next branch to be released. This
would prevent to have to modify (and often forget) the real reference, ie R18 for now.
Hi Jacques,
Yes, seems like a good idea to expose the next API too. But I am not fully
aware of the next API and curious about the label means Next API Reference,
wouldn't it be confusing for the user?
--
Thanks & Regards
Pawan Verma
Technical Consultant
*HotWax Systems*
*Enterprise open source
After thought: why not expose the next API too?
Jacques
Le 15/07/2020 à 10:19, Olivier Heintz a écrit :
+1 to the 2nd option
Le 15/07/2020 à 09:58, Devanshu Vyas a écrit :
+1 to the 2nd option.
Thanks & Regards,
Devanshu Vyas.
On Wed, Jul 15, 2020 at 10:56 AM Pritam Kute
wrote:
I am
+1 to the 2nd option
Le 15/07/2020 à 09:58, Devanshu Vyas a écrit :
> +1 to the 2nd option.
>
> Thanks & Regards,
> Devanshu Vyas.
>
>
> On Wed, Jul 15, 2020 at 10:56 AM Pritam Kute
> wrote:
>
>> I am also inclined to 2nd option.
>>
>> Thanks, Pawan for pointing this.
>>
>> Kind Regards,
>>
+1 to the 2nd option.
Thanks & Regards,
Devanshu Vyas.
On Wed, Jul 15, 2020 at 10:56 AM Pritam Kute
wrote:
> I am also inclined to 2nd option.
>
> Thanks, Pawan for pointing this.
>
> Kind Regards,
> --
> Pritam Kute
>
>
> On Wed, Jul 15, 2020 at 1:24 AM Jacques Le Roux <
>
I am also inclined to 2nd option.
Thanks, Pawan for pointing this.
Kind Regards,
--
Pritam Kute
On Wed, Jul 15, 2020 at 1:24 AM Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:
> Thanks Pawan,
>
> The 2nd options looks like a good idea to me.
>
> Jacques
>
> Le 14/07/2020 à 15:38, Pawan
Thanks Pawan,
The 2nd options looks like a good idea to me.
Jacques
Le 14/07/2020 à 15:38, Pawan Verma a écrit :
Hello Devs,
Since Oliver has refactored documentation with new directories structure
with the trunk, next and stable API Reference link becomes stale.
Question: What should be
Hello Devs,
Since Oliver has refactored documentation with new directories structure
with the trunk, next and stable API Reference link becomes stale.
Question: What should be the API Reference link on the site?
Possible Solutions:
#1: We can use the link for stable APIs for Site as suggested
14 matches
Mail list logo
