I'm sure you could make this work. You might, for instance, load different 
partials for your content and you could do the same with your directives by 
using a function in your templateUrl property. Controllers, and other 
application logic could remain the same.

On Tuesday, March 18, 2014 3:18:29 AM UTC-4, Iain Duncan wrote:
>
>
> On Mon, Mar 17, 2014 at 11:06 PM, Luke Kende <[email protected]<javascript:>
> > wrote:
>
>> Well, based on how the question points are posed, it doesn't sound like 
>> you quite have a grasp of angular, but I will offer some direction.  
>>
>> - First, go through the main tutorial if you have not done so: 
>> http://docs.angularjs.org/tutorial
>>
>
> Thanks, have done so already. 
>
>>
>> - Used as a single page app, angular uses partials when switching views 
>> that are retrieved via XHR not via RESTful API.  To do this, review the use 
>> of ng-router and ng-view.  One you've set up your routes via 
>> $routeProvider, then angular will handle loading the different views.  If 
>> you need nested views and "states" then you might look into to ui-router.
>>
>>  
> Well technically Representation State Transfer refers to the idempotent 
> URL schema used on the server side API. So yes, an Angular app can of 
> course interact with a backend over XHR via a Restful API. 
>  
>
>>
>> - Instead of sending viewport size to your api, I'd recommend reading up 
>> on css media queries or simply loading a different index.html file based on 
>> the device requesting the page.
>>
>
> Perhaps my question was not very well put. I know how to make mobile sites 
> with media queries and breakpoints (and how to make ReSTful web services) 
> but that isn't all I want to do. The issue with only using media queries 
> for mobile sites is that you have to have already downloaded content for 
> all form factors. CSS media queries can only be used to adjust CSS for 
> different breakpoints, they just hide things or resize them.  I 
> specifically want to be able query for different version of *content* if 
> the admin (via a separate admin interface backend) has decided to write 
> smaller versions of pages for smaller form factors or upload smaller 
> images. The point of the architecture I have in mind is to do more than 
> just the standard responsive design "shuffle the bits around and hide" 
> thing, enabling the admin to serve up different menus, focus on different 
> content, etc, without having to maintain a separate mobile site at a 
> separate domain. By having the client side load the page and then fetch 
> content asynchronously I do not have to send desktop content to a phone and 
> the hide whatever isn't relevant, I can have the initial app load with the 
> first request (as an agular app) and then have the actual page content and 
> images fetched via ajax hits.
>
> Has anyone else on here done anything like what I'm describing?
>
>
>> Personally, I do not know of any CMS's using angular.  The server is 
>> agnostic, so it does not really matter, but there are some good seeds to 
>> start with based on using NodeJs.  
>>
>> Here's a link I found that list a few:  
>> http://www.jquery4u.com/angular-js/5-angular-js-seeds-bootstrap-apps/
>>
>
> Thanks, I'll check those out!
>
> iain
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"AngularJS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.

Reply via email to