Aeroviewr source code?

[Jose]

Is the source for the demo Aeroviewr available?
I'd love to learn from it.

Thanks!

[Dimo]

Hello Jose,

I am afraid that currently the source of the AeroViewr is not publicly available. The application was built as a concept few months before we rolled out the Kendo UI beta. We are considering updating it at some point and then we may provide the source.

Kind regards,
Dimo
the Telerik team

[Ken]

Just for fun, i'll throw a vote in for this and/or a few demo apps (say Instagram then) so there is demo source with how KendoUI would structure a working web app, fully set as a case study.  thanks… ken

[Matt]

I agree that it would nice to see the source of how Kendo UI can be used to do something like aeroviewr. It's not clear to me that Kendo is capable of this type of image viewer. What other tools are needed to accomplish this? Why not show it so we can see how its done?

[Ken]

btw, frankly i * would not * post demos on your site, using your tools unless your fully prepared to also offer full source, downloadable code with documentation.   it's a first for me to see this.  even Microsoft and Apple offer full source to their demo code for explaining the dev tools.  that's just plain wrong, not to do.

beyond AeroViewr (assuming you cannot, or will not) share that code.  it would be greatly appreciated if you could offer a few decent demo projects, with full source and documentation so that it's proper "manufacturer approved" technique and methods (e.g.  directory structure, etc), could be viewed for educational purposes.  

frankly, i don't care about AeroViewr, it can be another altered app for FlickR, Instragram or YATF (yet another twitter feed).  it's the concept of a full (demo) project, with documentation as a baseline to ensure a healthy start to using KendoUI.

thanks, ken

[Sebastian]

Hello guys,

Indeed we do not offer a separate source code download for the Aeroviewr demo because it is contains heavily customized code adopted to work with the Flickr API. It also does not utilize widgets from which it can take full advantage of. We apologize if this causes you any hassle.

We will have an internal team discussion this week during which we will decide either to:

•  simplify the application and remove its custom dependencies from the Flickr API as much as possible, utilize the latest version of the Kendo UI widgets and publish the source code for the general public
  or
• replace the Aeroviewr with a different mid-size demo application developed with the Kendo UI Web package and disclose its source code once it is done and goes live

Please stand by updates on this topic in the next few months.

As for other mid-sized sample apps with source code that you can get your hands on - here are several posted on our blogs that you might be interested in:

Kendo UI Q1'12 Webinar Tech Resources
Kendo UI Mobile PhoneGap application
Kendo UI Web in PHP app Part 1
Kendo UI Web in PHP app Part 2
Kendo UI ToDo list 

Kind regards,
Sebastian
the Telerik team

[Matt]

Thank you for the forthright answer. I have used your asp.NET AJAX controls and am now evaluating what to use for other projects. MVC, Kendo, etc. So I am very interested in what Kendo brings. The aeroviewr caught my attention as a powerful demo of Kendo's capabilites. My question now is "Can you describe what portions of aeroviewr can be done with Kendo widgets vs custom code?"

Specific questions:

1) aeroviewr accesses flickr photos very quickly. Is this due to Kendo UI or custom code? If it's a Kendo widget, can you share how that was implemented? If it's custom, are you willing to share?

2) The touch response of aeroviewr on an iPad is outstanding. Smooth. Makes use of multi-touch in a nice way. Very responsive. Again, is this because of Kendo's capabilites or the custom code?

3) The search capability of aeroviewr is handy. Kendo or custom?

4) The animations and fades on loading and scrolling are well done. Kendo or custom?

5) Window resizing was handled decently. Kendo or custom.

Your answers would help me greatly as I continue to evaluate.

[Dimo]

Hi Matthew,

1. The photos are retrieved with the Kendo DataSource, which requests image URLs via the Flickr API.

2. The touch and multi-touch capabilities are achieved with a custom Kendo-based widget, which we later decided to not include in the official product.

3. The search functionality is implemented with a Kendo AutoComplete widget.

4. Animations are Kendo-based.

5. The layout adjustments on browser window resize are a custom implementation - the ListVew is rebound and we calculate how many images to show and how large they should be.

Regards,
Dimo
the Telerik team

[Nick]

So from what I gather in this thread, we shouldn't be expecting AeroViewr on Github anytime soon? Have you considered licensing the just the slideshow component? It's a great resource we could all learn a lot from, hope you can share somehow.

[Richard]

hi,

i would like to get access to the source code for this demo as well.  it would be nice to see how it was put together.

I would also like to see the unit tests for the code packaged with the source.  Presuming that there are unit tests....


Richard

[Brett]

How about posting a demo with the current Kendo API.  I don't care about the Flickr framework, in fact, I prefer not to.  You guys have been deliberating over the photo gallery app for months, how about some sample code?

[Blake Versiga]

I agree, just stub out the flicker interface with 3 stock kendo ui logos.  It is really rude to say, our product can do this..... but we won't show you how.....