Yep, you are right Ramsey, JC is so much better.

D2JC doubly so.

Glad you agree.

Dave

No, it's what you said. You can't take it back now. Everyone here are witnesses.

Even Chuck and Anjo agree. Just ask them.

lalalalalalalalalalalalalalalalala…

(ignore the copious beers I've consumed tonight at the hash - or, if you are Australian, add them to my credibility.)

On Jan 2, 2013, at 11:44 PM, Ramsey Gurley <ramseygurley@gmail.com> wrote:

I thought about AUC, but I figured the viewport would jump around when the container updated. Also, do you reload the entire container each time or are you just appending new results? I would expect a full reload to become increasingly slow after each batch.

With JC, all the interface is done on the client. Doing this server side, I see potentially tricky issues… mainly the back button and forms.

Ramsey

On Jan 1, 2013, at 11:28 PM, Matthew Ness wrote:

Hi Ramsey,

I've built infinite scroll components before using AjaxUpdateContainers, AjaxSubmitButtons, ERXFetchSpecificationBatchIterators, and some JavaScript listening to a couple of view-port/window events.

Not WODisplayGroups, but works really well. :)

Cheers,

Matt



On 02/01/2013, at 3:00 PM, David Avendasora wrote:

Hey Ramsey,

I'm not sure if this is what you mean, or exactly how it is done, but a WO Java Client application automatically faults and transfers data to the client while scrolling a list view. The client gets all the initial EOs that are "visible" in the scroll-view area of the window when it is first displayed, and as the user scrolls or makes the window larger, the client-side app automatically requests additional data from the server-side app depending on what was now "visible" in the client-side window. This made for a very quick initial load, but "required" a fast connection to then server to make it smooth.

Of course a WO JavaClient app has it's own EOF stack and could cache EOs in the client-side EOEditingContext so it didn't have to talk to the server to scroll back up to rows it had already loaded. Not sure how you would deal with that efficiently with a HTML client… maybe with a little choco-hazelnut goodness?

Dave

On Dec 31, 2012, at 11:43 PM, Ramsey Gurley <ramseygurley@gmail.com> wrote:

Has anyone done infinite scroll using WODisplayGroups?

Ramsey

------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122412
_______________________________________________
Wonder-disc mailing list
Wonder-disc@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wonder-disc




—————————————————————————————
WebObjects - so easy that even Dave Avendasora can do it!™
—————————————————————————————
David Avendasora
Senior Software Abuser
Kaiten, Inc.





------------------------------------------------------------------------------
Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery
and much more. Keep your Java skills current with LearnJavaNow -
200+ hours of step-by-step video tutorials by Java experts.
SALE $49.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122612
_______________________________________________
Wonder-disc mailing list
Wonder-disc@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wonder-disc





—————————————————————————————
WebObjects - so easy that even Dave Avendasora can do it!™
—————————————————————————————
David Avendasora
Senior Software Abuser
Kaiten, Inc.