Re: prototype.js
Re: prototype.js
- Subject: Re: prototype.js
- From: Hugi Thordarson via Webobjects-dev <email@hidden>
- Date: Wed, 13 Aug 2025 21:51:25 +0000
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@hidden> 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@hidden>:
>>
>> 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@hidden> 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@hidden)
>> Help/Unsubscribe/Update your Subscription:
>>
>> This email sent to email@hidden
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
References: | |
| >prototype.js (From: Fredrik Lindgren via Webobjects-dev <email@hidden>) |
| >Re: prototype.js (From: Daniele Corti via Webobjects-dev <email@hidden>) |
| >Re: prototype.js (From: Fredrik Lindgren via Webobjects-dev <email@hidden>) |