Re: There was an old thread about Ajax...
Re: There was an old thread about Ajax...
- Subject: Re: There was an old thread about Ajax...
- From: Jesse Tayler via Webobjects-dev <email@hidden>
- Date: Tue, 29 Oct 2019 09:08:32 -0400
Yes, I recall something about show/hide but it’s fuzzy now.
I did however, conclude that we are all hosed!
The value of things like the AJAX list panel that can load up new batches or a
tab panel that reloads like magic?
These old Ajax frameworks have tricks to override rules in D2W so simply adding
the framework inserts itself into the interface frameworks beautifully.
Then I went into the AJAX frameworks to trace the code and found the group of
them to be deeply intertwined, and the code depends on long hierarchies of
those too-long-inheritance chains that we’ve all seen arise over time. You just
keep going into superviews and different WOD bindings until you are lost.
I strongly sense we’d have to quite literally rewrite a batch of related
frameworks -- and we’d have to be able to use the same code/D2W trickery to
make the new frameworks ride on top of our apps seamlessly.
However, it IS possible to do!
I wish I had a solution to this problem.
> On Oct 29, 2019, at 8:57 AM, René Bock <email@hidden> wrote:
>
> Well, you may use both frameworks, prototyps.js and jQuery if you use jQuery
> in non-conflict mode (because both frameworks defines the variable $ as
> shortcut)
>
> We had some additional issues when using the bootstrap framework, as
> prototypes.js add functions like show, hide, toggle to each element.
>
>> Am 29.10.2019 um 12:55 schrieb Jesse Tayler via Webobjects-dev
>> <email@hidden>:
>>
>> I have trouble with this as well, the older code conflicts with newer jQuery
>> based stuff.
>>
>> So bad, that it will eventually stop your work because some bugs are
>> critical and you’ll not be able to work around them.
>>
>> I’ve found that the code way back in those Ajax frameworks is indeed amazing
>> but also unreadable and unmaintainable.
>>
>> In fact, I believe there is no way with our current resources that WO folks
>> will overcome this critical issue — our legacy is dragging us down.
>>
>> If anyone can figure this out, or even has ideas or wants to try — I’m up
>> for it, but I’ve found myself that the weight is impossibly heavy.
>>
>>
>>
>>> On Oct 29, 2019, at 3:18 AM, Jérémy DE ROYER via Webobjects-dev
>>> <email@hidden> wrote:
>>>
>>> Hello,
>>>
>>> Log time ago (10/2014), there was an old thread around migrating ajax from
>>> prototype to jquery as :
>>> - prototype is out of date
>>> - we « all » use jQuery to deal with ajax-front-end-requests
>>>
>>> There was a link to the work made by johnny miller
>>> https://github.com/johnnykahalawai/wonder
>>>
>>> To deal with ajax-back-end-requests, we currently use :
>>> - AjaxModaDialog
>>> - AjaxUpdateContainer
>>> - AjaxUpdateLink
>>> - AjaxObserveField
>>> - AjaxSubmitButton
>>> - AjaxLongResponse
>>>
>>> How do you deal with Ajax ? Still use wonder with prototype ? Any new idea ?
>>>
>>> Jérémy
>>> _______________________________________________
>>> 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
>
> Mit freundlichen Grüßen
>
> René Bock
>
> --
> Telefon: +49 69 650096 18
>
> salient GmbH, Lindleystraße 12, 60314 Frankfurt
> Telefon Zentrale: 069 / 65 00 96 - 0 | www.salient-doremus.de
>
_______________________________________________
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