Meeting on Monday - 2022-07-11 #933

Closed
opened 2022-07-11 20:16:54 +00:00 by Chris Paschen · 0 comments
Member

Here are the notes that I took during the meeting. Things went fast, so if I missed something or didn't record it correctly here, please update.

Announcements & Updates

  • Letting go of Pro version
    • Too much time to manage both versions
    • Powers area is key feature
      • Now creating classes per proper PHP structure
  • Merge pro into non-pro version
  • JCB has moved out of github
    • Into our (JCB) own infrastructure
    • Moved issues from github to own git infrastructure - so we must now use
      https://git.vdm.dev/joomla/Component-Builder/issues
    • Pro version has been moved here also
    • Updates are now using this new location
    • Still synchronizing via mirror with the previous github area
  • Some Problems updating automatically (identified from some users)
    • Go to the Joomla install area and just re-install JCB
    • The Component includes only the core features
    • The Package includes all the package
    • Everyone who is on 2.13.x can now just update to 3.1.4
    • Expectation is that you could go to updates and it would show that there is an update
    • You can get the download package from the link in the Update Sites area (from with your Joomla Update view)
    • Not adding official release notices from now on; only by adding a tag (at least during this transition period)
    • You can get the latest package build here:
      https://git.vdm.dev/joomla/pkg-component-builder
      • This will always be the most current version
  • To-Do list
    • Listing all things to be done
    • Powers
      • Need to import powers
      • When you go to plugins and type in "comp" in search
      • All the plugins must be enabled to get the pro features to work
      • When you want to add a power to any JCB component
        • You will see that there are none
      • Need to 
        • Go to VDM Packages
        • Get the Powers Package
        • Add it to your system
        • It should add just powers (shows in the success notification)
      • This is why we need to move the functionality of the JCB Packages into it's own code so that we can add it as an easy button to press (i.e. update to latest updates) - to update to the latest classes, etc. to build extensions
      • You will have code in the powers area that will be used in the compiler
      • You will need to get that via the JCB packages system
      • Powers are imported based in the GUID
      • When you create a new instance of a powers, it creates an independent 'power' that is your own to maintain now
      • These need to be distributed independent of the main package because it would be too big of a package file
      • You can manually import any missing items (fields, powers, etc) to keep your JCB install updated
      • Need to move JCB Packages to it's own classes to make it ready to move forward
    • Moving some of the 'get' items into their own class
    • If you see something in the ToDo - go ahead and jump in and offer to help
      • In JCB git, look on the 'Projects' tab
  • Need to start process moving all users to the full package

Discussion

  • We need to keep talking about JCB and promoting to other developers
  • We need to keep supporting JCB (financially)
  • Will JCB build for J3 & J4
    • Yes JCB will always work in J3 (as it does now)
    • Eventually it in JCB for J4 we may drop J3 and start focus in J5
    • We will refactoring the compiler to work for J3 and J4, and J5 and ++
    • Worst case: export your J3 package and then import and build in a JCB for J4
    • Maintaining Legacy systems - The J3 version will (ideally) be kept updated for security issues; however, you won't get the new J4 JCB features
  • When will JCB for J4 be ready
Here are the notes that I took during the meeting. Things went fast, so if I missed something or didn't record it correctly here, please update. # Announcements & Updates - Letting go of Pro version - Too much time to manage both versions - Powers area is key feature - Now creating classes per proper PHP structure - Merge pro into non-pro version - JCB has moved out of github - Into our (JCB) own infrastructure - Moved issues from github to own git infrastructure - so we must now use https://git.vdm.dev/joomla/Component-Builder/issues - Pro version has been moved here also - Updates are now using this new location - Still synchronizing via mirror with the previous github area - Some Problems updating automatically (identified from some users) - Go to the Joomla install area and just re-install JCB - The Component includes only the core features - The Package includes all the package - Everyone who is on 2.13.x can now just update to 3.1.4 - Expectation is that you could go to updates and it would show that there is an update - You can get the download package from the link in the Update Sites area (from with your Joomla Update view) - https://git.vdm.dev/api/v1/repos/joomla/pkg-component-builder/archive/v3.1.4.zip - Not adding official release notices from now on; only by adding a tag (at least during this transition period) - You can get the latest package build here: https://git.vdm.dev/joomla/pkg-component-builder - This will always be the most current version - To-Do list - Listing all things to be done - https://git.vdm.dev/joomla/Component-Builder/projects/14 - Powers - Need to import powers - When you go to plugins and type in "comp" in search - All the plugins must be enabled to get the pro features to work - When you want to add a power to any JCB component - You will see that there are none - Need to  - Go to VDM Packages - Get the Powers Package - Add it to your system - It should add just powers (shows in the success notification) - This is why we need to move the functionality of the JCB Packages into it's own code so that we can add it as an easy button to press (i.e. update to latest updates) - to update to the latest classes, etc. to build extensions - You will have code in the powers area that will be used in the compiler - You will need to get that via the JCB packages system - Powers are imported based in the GUID - When you create a new instance of a powers, it creates an independent 'power' that is your own to maintain now - These need to be distributed independent of the main package because it would be too big of a package file - You can manually import any missing items (fields, powers, etc) to keep your JCB install updated - Need to move JCB Packages to it's own classes to make it ready to move forward - Moving some of the 'get' items into their own class - If you see something in the ToDo - go ahead and jump in and offer to help - In JCB git, look on the 'Projects' tab - Need to start process moving all users to the full package # Discussion - We need to keep talking about JCB and promoting to other developers - We need to keep supporting JCB (financially) - Will JCB build for J3 & J4 - Yes JCB will always work in J3 (as it does now) - Eventually it in JCB for J4 we may drop J3 and start focus in J5 - We will refactoring the compiler to work for J3 and J4, and J5 and ++ - Worst case: export your J3 package and then import and build in a JCB for J4 - Maintaining Legacy systems - The J3 version will (ideally) be kept updated for security issues; however, you won't get the new J4 JCB features - When will JCB for J4 be ready - Aiming for the end of the year - Might happen sooner - See the J4 Projects/tasks board https://git.vdm.dev/joomla/Component-Builder/projects/14
Llewellyn changed title from Meetings from 2022-07-11 meeting to Meeting on Monday - 2022-07-11 2022-07-12 05:57:20 +00:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: joomla/Component-Builder#933
No description provided.