Re: [jira] [Commented] (OFBIZ-11094) Buildbot RAT for releases branches
No worries, all is OK now: https://ci.apache.org/projects/ofbiz/site/stable/rat-output.html https://ci.apache.org/projects/ofbiz/site/next/rat-output.html https://ci.apache.org/projects/ofbiz/site/trunk/rat-output.html Jacques Le 09/06/2020 à 17:51, ASF subversion and git services (Jira) a écrit : [ https://issues.apache.org/jira/browse/OFBIZ-11094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17129419#comment-17129419 ] ASF subversion and git services commented on OFBIZ-11094: - Commit 42cb119cf3324d7cf3c2867d2092c72932aa6526 in ofbiz-tools's branch refs/heads/master from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-tools.git;h=42cb119 ] Fixed: Buildbot RAT for releases branches (OFBIZ-11094) Adds themes/common for R17 Buildbot RAT for releases branches -- Key: OFBIZ-11094 URL: https://issues.apache.org/jira/browse/OFBIZ-11094 Project: OFBiz Issue Type: New Feature Components: BuildBot Affects Versions: Release Branch 16.11, Release Branch 18.12, Release Branch 17.12 Reporter: Jacques Le Roux Assignee: Jacques Le Roux Priority: Minor For the moment, only the trunk is verified by RAT (Apache Creadur). The initial idea was that once valided in trunk there should not be issues in releases branches, but better be safe than sorry! -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: OFBiz-GraphQL Webinar Recording on YouTube
Hi Eugen The Webinar was an attempt to discuss the ongoing OFBiz-GraphQL implementation with the community and showcase what had been done on that front. Thanks for taking interest in the implementation. I will plan to have series of more sessions by breaking it down and covering only specifics to cut short the duration. In the meantime, please let me know if you have any questions or concerns or have any suggestions on the current implementation. Best Regards, Girish Hotwax Systems On Mon, Jun 8, 2020 at 9:03 PM Eugen Stan wrote: > Thanks for the webinar. I watched it full as an API on top of Of Biz is > of interest to me. > > I have some feedback which I believe you are already aware of: > > - the audio is of poor quality and hard to understand in some points > > - the video is very long and could use some editing to remove the silent > / dead parts. > > - If editing is not an option, I think it's easy to add "skip this > section" buttons on youtube. > > Please share future videos in this direction. > > Regards, > > Eugen > > La 08.05.2020 18:10, Pranay Pandey a scris: > > Here is the direct URL: https://youtu.be/VK0o0OBAS1I > > > > Best regards, > > Pranay Pandey > > > > > > On Fri, May 8, 2020 at 8:39 PM Pranay Pandey < > > pranay.pan...@hotwaxsystems.com> wrote: > > > >> Hello OFBiz Devs, Users > >> > >> OFBiz-GraphQL webinar recording is now available for everyone's > reference > >> on YouTube. > >> > >> Thank you Girish Vasmatkar for this doing this webinar and providing the > >> recording for upload. > >> > >> Best regards, > >> Pranay Pandey > >> > -- > Eugen Stan > +40720 898 747 / netdava.com > >
Re: buildbot success in on ofbizNextFrameworkRat
Hi, I was right to create OFBIZ-11094 and INFRA-20148 we have few 3 license issues in R18: https://ci.apache.org/projects/ofbiz/site/next/rat-output.html We certainly forgot to backport from trunk OK, I'll now do the same for stable and hopefully that's it Thanks to Olivier to initially works on INFRA-20311 Jacques Le 09/06/2020 à 10:52, build...@apache.org a écrit : The Buildbot has detected a restored build on builder ofbizNextFrameworkRat while building . Full details are available at: https://ci.apache.org/builders/ofbizNextFrameworkRat/builds/11 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: asf945_ubuntu Build Reason: forced: by IRC user (privmsg): forces manual build after INFRA-20148 Build Source Stamp: HEAD Blamelist: Build succeeded! Sincerely, -The Buildbot
Chapter 3 : promoting decorator
Hello devs, This mail introduce the last Chapter of our story that describe in which context we created some new decorators. First, we want to recall the common-theme effort objectives : The common-theme component is the default theme that define every screens that are available for theme surcharge, without technology information (css/html, vuejs or something like that). Every theme is based onto this common-theme that structure the application. Any theme can empower this structure its way, using it’s one technology. The idea is simple, isolating screen definition from technology syntax, let the technology implementation to the theme. Xml Screen and form definition must only be description of the structure. The “how it is render” is defined by default by the common-theme, and might be overloaded by a chosen theme. From these objectives arise the need to list structural descriptive decorator that exists or are added by our effort : The *FindScreenDecorator* : is the existing search screen decorator in OFBiz, it is composed in three sections : * A menu (party creation for instance : menu-bar) * Search criteria (search-option) * Results (search-results) The new *DetailsScreenDecorator* : is a new decorator to show a sum up of an object and its related data. Composed in five sections : * A menu (menu-bar) * A tab menu : to give access to related data into details section (tab-bar) * A summary that display main data of the object (summary) * An action menu (object modification, duplicate or specific actions : actions) * The detail : area that will display related data (details) This structure, in addition to give the display control to the theme, offer the developer not to think about the area to use when he wants to display more data concerning the object. Moreover, when performing actions, the developer do not need to know about the area to refresh, since the screen-engine has been improved to manage it for him. The new *EmbeddedScreenDecorator* : is a new decorator used to inject in an structure page area a specific screen. Its goal is to define what kind of data the screen will have to render to allow the theme to adapt the technology for data rendering. The sections are : * A menu (menu-bar) * An action menu (search filtering, history display…) * single : display of a single form * content : display a content (Image or document) * list : display a list of data Those can be loaded by functional decorator that take charge of basic data retrieval : As an example : *EmbeddedProductCategoryScreenDecorator* That is a specific decorator that implements the *EmbeddedScreenDecorator* and do the data retrieval of productCategory object : This avoid for every embedded screen using productCategory code duplication in data retrieval. The same logic can be applied to *DetailsScreenDecorator*. To see all that in action we are working into a simple demo, in a classical theme and an simple improved theme, we currently are creating a sum-up presentation with illustration and more details like code/video. I hope we will be able to share it with you soon enough. Best Regards signature.asc Description: PGP signature
