ng-objects seems like a really nice start. I agree that the multiple update 
would be nice.

I might test ng-object or go the htmx route. Either way it is a major effort.

/Fredrik

> 13 aug. 2025 kl. 23:51 skrev Hugi Thordarson via Webobjects-dev 
> <[email protected]>:
> 
> I've started some work on partial rendering/Ajax functionality for my 
> ng-objects project. Since I want some template-level compatibility between WO 
> and NG, my current plan involves eventually backporting some of the (plain 
> JS) client side stuff to WO, at least for some baseline 
> functionality/elements (like update containers, update links, update 
> triggers, submit buttons and observefields).
> 
> I've considered using htmx (which I love the concept of, and it would be nice 
> to use a known, popular framework). But ng-objects supports updating multiple 
> update containers in a single request (i.e. you can target multiple named UCs 
> and the server will then generate a multipart response with a part for each 
> targeted container) and htmx currently can't handle that. My own 
> proof-of-concept works nicely, although it's primitive and in progress (much 
> like my current client side skills in general).
> 
> https://github.com/ngobjects/ng-objects/blob/87443b590c0943c95d491ede79fb77893ed222e1/ng-appserver/src/main/resources/ng/ng/webserver-resources/ng-js.js#L24-L48
> 
> But apart from ng — I actually think HTMX would be a great fit for an 
> updated/simplified Ajax-framework on the WO side (where the multipart-stuff 
> isn't required/supported).
> 
> Cheers,
> - hugi
> 
> 
> 
>> On 13 Aug 2025, at 11:55, Fredrik Lindgren via Webobjects-dev 
>> <[email protected]> wrote:
>> 
>> Yes, we are using that feature in jQuery. However it seems that prototype is 
>> overriding some features in native javascript that Quill uses (and other 
>> libraries). This brakes those libraries.
>> 
>> Ideal would be to update the Ajax-classes to not use prototype, but I 
>> realise this is a major effort. 
>> 
>> There is a framework that might be used to replace the Ajax komponents, that 
>> is called htmx (https://htmx.org/). That might be a path forward, but to get 
>> the same level of integration as Ajax, there is a lot of work. 
>> 
>> I can probably use the AjaxUtils.ajaxComponentActionUrl(WOContext) to get 
>> the html that should replace a similar update container.
>> 
>> Has anyone tried this approach?
>> 
>> /Fredrik
>> 
>> 
>>> 13 aug. 2025 kl. 10:30 skrev Daniele Corti <[email protected]>:
>>> 
>>> Hi,
>>> A while ago, I did a project using Ajax framewotk, with Bootstrap, using 
>>> jQuery.
>>> 
>>> Fortunately, jQuery is distributed with a function called noConflict(), 
>>> which is precisely for making jquery work with other javascript libraries.
>>> 
>>> Once I found the right call order, I was able to get both the Ajax 
>>> framework and the jQuery and bootstrap functionality working.
>>> 
>>> I think the only option is to check if there is a way for prorotypes and 
>>> the other js libraries you use to coexist.
>>> 
>>> Best regards 
>>> D.
>>> 
>>> Il Mer 13 Ago 2025, 09:43 Fredrik Lindgren via Webobjects-dev 
>>> <[email protected]> ha scritto:
>>> Is there a way to opt out of using prototype.js with the Ajax framework.
>>> 
>>> We are having problems integrating for example the quill editor due to 
>>> conflicts.
>>> 
>>> Anyone have similar problems with a solution?
>>> 
>>> /Fredrik
>>> _______________________________________________
>>> Do not post admin requests to the list. They will be ignored.
>>> Webobjects-dev mailing list      ([email protected])
>>> Help/Unsubscribe/Update your Subscription:
>>> https://lists.apple.com/mailman/options/webobjects-dev/rs.daniele%40vinati.com
>>> 
>>> This email sent to [email protected]
>> 
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Webobjects-dev mailing list      ([email protected])
>> Help/Unsubscribe/Update your Subscription:
>> https://lists.apple.com/mailman/options/webobjects-dev/hugi%40karlmenn.is
>> 
>> This email sent to [email protected]
> 
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list      ([email protected])
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/webobjects-dev/frelin%40timeoff.se
> 
> This email sent to [email protected]

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to