From 25+ years of cfml, I'd finally like to see

language proposals
1

Just warming up here:

  • Event triggers throughout the server for everything that moves, than can be logged, can have scheduled tasks fire

With Admin

  • Admin roles ( admin / develop / test whatever with access permissions - like security – access but as a role with name you can put a user against)
  • Extension Builder Wizard, creates component with ui to test it using tesbox tests, and then submit for internal testing / inclusion
  • move all admin to rest api
    • makes it easier to build alternative admins
    • could allow for a mobile app admin (hybrid or native)
    • would like to have a electron native app on win/osx to manage admin of one or more servers, or group of servers (cluster, or just group under load balancer) - also gives access to ‘developer’ part of admin (new section which has access to logs/email queues/etc stuff to dev, not admin server)
  • Better Scheduled tasks interface, and cron like time entry addition
  • Update regional to feed locale functions/tags (create locale-based validations - retire eurodate/usdate/zipcode validations) - make ALL date and time functions based on default locale and timezone of the server, an option on that page to ‘always store dates as 0 GMT’
  • rename Mail to Email, move Email - move to extension
  • update ‘note’ extension to be ‘sticky note’ and allow it to float on the page to be a useful reminder (with context - currentpage/everypage/frontpage).
  • Logs Extension: ability to convert all logs to your preferred type
  • new sms extension (with twilio, cellcast, globalsms, etc providers)
  • new web push extension ( with openairship, direct to google/apple, etc providers )
  • stable git functionality to use repos to update apps, etc

Extensions:

  • new auth extension (with oauth, jwt, webauthn providers)
  • new ai extension (with openAI, github copilot, etc proviers)
  • new lightweight api extension (with rest/graphapi) that can be hooked up with configuration or through an object or datasource table.
  • new secrets store extension that allows you to use secretstore=“” instead of username/password for ANYTHING that has a username/password

  • Move to extensions (out of core) or have a ‘settings’ page that can DISABLE or UNLOAD the functionalies we dont need:

    • AI
    • Event Gateway
    • Cache
    • Datasource
    • ORM
    • Search
    • (E)Mail
    • Tasks
    • Scheduled Tasks
    • SSL Certificates
    • Rest
    • Custom tags
    • CFX tags

Introduce a whole new extension catalog, (not applications, that’s a horrific word for an extension when you have already an ‘appliation’ concept.) There should also be a category, subcategory for each along with tags, and a new concept called ‘providers’ which allow you to add providers to extensions (aka a mssql provider for database extension, or a postmark provider for the email extension.

New AI functionality
Would love to see AI implemented as an extension, with allowances to create providers, and have some common ones available out of the box for activation, then once activated, this then drops configuration options into admin for using ai in debugging, and other stuff, that seemlessly appears (and disappears) from admin config options when this extension (or provider) is unconfigured.

API Manager
Would love to see a basic api manger in the ‘administrator’ (need to find a better word and allow multiple role based ‘panels’ (rather than admins) to access functionalities based on your role (as stated above)

Then for example the email extension could also be used for the configuration of the mailgateway. filtering out any email servers that dont have pop3 or imap or (other type like api)… email api provider extension should be also able to retrieve and/or send, but abstracted away, so then email gateway should just then call retrieveEmail() instead of having it hard wired to imap/pop3 (thanks for the imap update btw - killer)

or a mysql or mariadb or percona provider for database extension

So many ideas… you sure you want them all?

2 Likes
2

Aka with moving out extensions, I should be able to fire up Lucee with almost no extended functionality but core functions/methods.

Some use cases:

Small static data api senario (with event bus)

  1. Api (rest) extension ( with rest configuration by convention provider )
  2. Event Bus Extension (with hookdeck provider)
  3. Caching Service (with Valkey provider)

Bulk Email scheduler instance (with event bus)

  1. Email Service
  2. Event Bus Extension
  3. Amazon SES provider

Webhook service with local logging

  1. api (rest) extension ( with webhook provider )
  2. Event Log Extension

AI-powered FAQ or documentation responder: (aka local hockey association rules question asker chat)

  1. Api (rest) extension
  2. API extension with any ai provider (doesn’t need to be self-hosted ollama as using public docs in this case)
  3. event bus extension
  4. email extension (for sending chats if requested)

could go on…

1 Like
3

loving all the passion on display here, would you consider getting your hands dirty and contributing?

One thing which would really help the Lucee community is diving into https://docs.lucee.org/ and rationalising / updating a lot of the pages, there’s lot of old, duplicate content on there

@micstriit has been putting a lot of working with adding Lucee Recipes :: Lucee Documentation lately

Would be great to review and delete some of the older pages, merging them into single documents

The best way to work on the docs is to checkout the code and run up a local Lucee 7 instance

1 Like
4

I did attempt getting into the docs once before, but got into a massive mess trying to understand how everything went together.

I think I might have another go, would prefer to start with a completely empty docs tho and add content in that needs to stay.

I’m at the end of a massive cfml framework rebuild (v7 centric), so have been super busy, could definitely look at it in detail in June timeframe, will have to look again at how it all works, but think best way forward is empty build, then add useful content in, then also having a version drop down for docs in future.

Using a diff script could also be good for ‘whats new’ pages also. Is this what the ide docs/tags/functions configs are built off also? (central point of truth)?

5

we already have changelog for tags and functions?

surfacing the newly added content is something I’d like to do, it’s a bit horrible trying to parse the git commit log performance wise, I have looked into it

6

Where is that generated from?

Be nice to have a dot version ‘roundup’ (which I could do myself), or be able to just say, tell me every new and/or modified function since version x…

How could I do that?

7

you could just grab the lucee cfdocs style json schema zip file as described here

that’s all working of the .tld and .fld from core and the extensions, using getFunctionList and getTagList and then getFunctionData and getTagData

1 Like