Best practice for responsive projects

Does anyone have tips on best practices for responsive project?
I understand that 3 different layouts can be created. What happens if a learner is not using one of the 3 devices that were set up in a responsive project, and their screen size is different from any of those

Jay,
Dr. Pooja Jaisingh offered very valuable tips for good practice in responsive design last week in her webinar. 'Do's and Don'ts of creating Responsive Projects with Captivate 8'. I don't see the recording yet On Demand, but keep an eye on it.
Did you test a responsive project with F11 (Preview in Browser)? You will be able to change the resolution of the browser window and see that the content, if well designed (you can have absolute positioning, size as well) will move, shrink to adapt. The break points (3 devices) allow you to make more invasive changes at those points: dragging some objects out of the stage in the scratch area because they take up too much space for phones is one example. Or replacing a big screenshot with many details by a zoomed in detail screenshot for the mobile breakpoint. That is my way of explaining, responsive is not just have the three layouts for devices, it is also adapting between those breakpoints.

Similar Messages

FAQ: Are there best practices for building projects within the 20 page/state limit?

The 20 page/state limit in Flash Catalyst is there to prevent Catalyst (and your finished application) from running slowly. You can however build efficient applications that have more than 20 states by using custom components. Custom components can contain states as well; so by creating an app that has several states, and using custom components that have states, you can get more unique views of your app while keeping it efficiently built.
Try this:
1. Select some of your arwork where you need more states. Right click and choose "Convert to Custom Component"
2. Double-click to edit the custom component. Note that you can now create states in the custom component. Try creating a few states here.
3. To exit editing the component, double click a blank area on the artboard.
4. If you try creating an "On click transition to state" interaction now you will see that you can choose from both the states of the application as well as the states of the custom component.
Answered by: Ty Voliter. See entire discussion.
More help:
Video tutorial on custom components
Video/demo discussing the benefits of "pushing interactivity down" into custom components, by Ian Giblin @ MAX 2009
(jump to the 11:15 mark, and watch through to about 20:30)
Another forum post by Ty:
Here's an ASCII diagram to illustrate one way of pushing application or top-level pages/states down into a custom component:
Before:
State1     State2     State3     State4     State5     State6     State7...
After (project refactored to push three top-level states down into a custom component):
State1     State2     State3      State7...
                    |
Custom Component
State4     State5     State6
For some projects this can be an inconvenient workaround, and for others it can really clean things up by reducing complexity. If you have several top-level pages in your app that are completely different than other pages (for example, they don't share any objects with the other states) than pushing these down into a custom component makes things a lot more manageable in Catalyst. The layers panel, for example, shows all objects across all states-- this is useful when your states share many objects. If however, your states don't share a lot of objects, the layers panel can get a bit unmanageable. Refactoring into a custom component allows you to fix this by grouping content into a container.

The 20 page/state limit in Flash Catalyst is there to prevent Catalyst (and your finished application) from running slowly. You can however build efficient applications that have more than 20 states by using custom components. Custom components can contain states as well; so by creating an app that has several states, and using custom components that have states, you can get more unique views of your app while keeping it efficiently built.
Try this:
1. Select some of your arwork where you need more states. Right click and choose "Convert to Custom Component"
2. Double-click to edit the custom component. Note that you can now create states in the custom component. Try creating a few states here.
3. To exit editing the component, double click a blank area on the artboard.
4. If you try creating an "On click transition to state" interaction now you will see that you can choose from both the states of the application as well as the states of the custom component.
Answered by: Ty Voliter. See entire discussion.
More help:
Video tutorial on custom components
Video/demo discussing the benefits of "pushing interactivity down" into custom components, by Ian Giblin @ MAX 2009
(jump to the 11:15 mark, and watch through to about 20:30)
Another forum post by Ty:
Here's an ASCII diagram to illustrate one way of pushing application or top-level pages/states down into a custom component:
Before:
State1     State2     State3     State4     State5     State6     State7...
After (project refactored to push three top-level states down into a custom component):
State1     State2     State3      State7...
                    |
Custom Component
State4     State5     State6
For some projects this can be an inconvenient workaround, and for others it can really clean things up by reducing complexity. If you have several top-level pages in your app that are completely different than other pages (for example, they don't share any objects with the other states) than pushing these down into a custom component makes things a lot more manageable in Catalyst. The layers panel, for example, shows all objects across all states-- this is useful when your states share many objects. If however, your states don't share a lot of objects, the layers panel can get a bit unmanageable. Refactoring into a custom component allows you to fix this by grouping content into a container.

Best practice for this project?

Hello,
Total n00b here, so please bare with me!
I'm working on one of my first AE projects getting my feet wet as well as following along with some books and Lynda.com training vids, but I thought I'd post here as well.
The project I'm working on is nothing more than a glorified slideshow. Basically, it consists of a 30 different still images (each image is different). For each still, there is a basic title sequence (fades in/out), then the still fades in, there's a pan/zoom, then fades out, then on to the next one. Total time per still is 30-40 seconds. Finally, there will be a single audio track playing over the full piece. Like I said, pretty simple.
What I'm wondering is, what's the best way to set this up. Should each still's sequence be it's own composition and then nest each composition within a master composition, should this all be done in a single composition, etc.?
Basically, I'm curious as to how to best deal with having this all reviewed, having to make changes, etc. For example, once I put the initial piece together, I'll render out a version for review. If I have to make a change to one of the sequences, is there a way to deal with this so I don't have to spend the time rendering the entire job out again, just for a short 1 second change to 1 sequence within the entire job? What's the best way to deal with this?
I'd love to hear what suggestions people may have!?
Thanks!
Kristin.

My personal approach would be just one comp, one text layer, and one black solid layer under the text and on top of the images to control the fading (I got the impression you want to go blank, rather than transition directly from one image to another).
Create a new solid, set it to your BG color, and make it "comp size".
Use the text tool and type your first title.
Select them both and use the align window to center your text horz and vert (actually your centering it to the solid, which happens to be the size of your comp)
Set up opacity fades on your title, and BG solid to reveal the 1st image, and set it up to pan and scan, then fade the BG solid back up.
Now go to where you want to fade up the next title, and open the text properties until you see Source Text, and enable keyframing.
Drag the new created square "hold" keyframe to the begining of time, then select all the text and change it to your 2nd title.
Then copy and paste your fade keyframes, tweak as needed, and repeat...
I prefer this approach as it keeps everything in one comp where you can see it (handy for syncing to your music layer), and you dont have a bunch of duplicate title layers that are essentially the same thing.
As for needing to change just a small part of it, depends on your finally delivery format. If you are giving them one long file, and just need to change a small part in the middle, make the change, then import your last rendered animation (best way to import is to drag the file from an OS browser window to the AE project window).
Bring the old anim into your comp as the top layer, so AE doesnt have think much about constructing each frame, then go to the beginning of the part you have changed, and with this cover layer selected "ctrl shift D" to split the layer. Then move to the end of your fixed portion and with the 2nd half of you cover layer selected, "alt [" which will jump the beginning of the cover to there, so AE only has to deeply contemplate the frames that you have changed. Although with this project it shouldnt take long to render any how.
Well, thats my two cents, or more like a buck thirty five.

Best Practice for documenting projects BW

Hi people.
We are studing at the moment a way of documenting new developments of applications of SAP BW.
Is there a standard of documentation recommended by SAP, or a good practice that I use to create and document objects developed in SAP BW.
Can someone help me?

Hi Marques, From my experience this varies from one costumer to another. Everywhere they have different practices, formats of documents, tools, habits, etc.
What I found very useful in BW is using of meta data repository part of TA RSA1. You can easily get some nice screen shots like data flows. Moreover in BW 7.x you have possibility to get documentation of particular transformations, DTPs etc. This can be done when you select particular object via left click of mouse and then hit F1 key.
BR
m./

Best practices for folder structure in SOA Project

Actually, In my project, I have more than 10 BPEL process and several DBAdapters and some HumanTasks. For each BPEL process, JDeveloper creates .bpel, .componentType, wsdl files. For DBAdapters JDeveloper creates lot of files, and same for HumanTasks as well.
By default Jdeveloper puts all these files in root directory of the Project. It looks messy having 100's of files in root directory.
How can I organize all these files?
What are the best practices for folder structure in SOA Project ?
Thanks

Yes Yatan. I did noticed that Polling service WSDL disabled in EM . But I want to try this approach beacause I want to move all database related stuff to one composite. I have another composite with 3 BPEL Processes. One BPEL queries external webservice and save the response in DB. One BPEL just fires the first Process(Query) and respond to caller with an unique id. I have Another BPEL which keeps polling on database for 5 sec(I'm using PICK Activity), if there is any new record in database it will retrun to caller. If no new records in database, returns empty to the caller after 5 sec.
If I put all these in one composite, having lot of files in root directory, the composite really looks very messy.
As you said, I want to have 2 composites. First Compoiste will have 3 BPEL processes, and 2nd Composite will have DB Polling and DB Save. I will have another project for MDS to store XSDs.
So because I can't have Polling service as exposed service, I have to keep Polling service in the same Composite where the BPEL is. Now again it goes back to Big and messy project.
Is there any way I can separate all DB related including polling in a separate Composite ?
Thanks
--Sreeny

Best Practices for Defining NDS Java Projects...

We are doing a Proof of Concept on using NDS to develop non-SAP Java applications. We are attempting to determine if we can replace our current Java development tools with NDS/WAS.
We are struggling with SAP's terminology and "plumbing" for setting up/defining Java projects. For example, what is and when do you define Tracks, Software Components, Development Components, etc. All of these terms are totally foreign to us and do not relate to our current Java environment (at least not that we can see). We are also struggling with how the DTR and activities tie in to those components.
If any one has defined best practices for setting up Java projects or has struggled with and overcome these same issues, please provide us with some guidance. This is a very frustrating and time-consuming issue for us.
Thank you!!

Hi Peggy,
In Component Model we divide software projects into small components.Components can use other components in well defined manner.
A development object is a part of a component that can be changed or developed in some way; it provides the component with a certain part of its functionality. A development object may be a Java class, a Web Dynpro view, a table definition, a JSP page, and so on. Development objects are always stored as sources in a repository.
A development component can be defined as a frame shared by a number of objects, which are part of the software.
Software components combine components (DCs) to larger units for delivery and deployment.
A track comprises configurations and runtime systems required for developing software component versions.It ensures stable states of deliverables used by subsequent tracks.
The Design Time Repository is for versioning source code management. Distributed development of software in teams. Transport and replication of sources.
You can also find lot of support in SDN for the above concepts with tutorials.
Refer this Link for a overview on Java development Infrastructure(JDI)
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webas/java/java development infrastructure jdi overview.pdf
To understand further
Working with Net Weaver Development Infrastructure :
http://help.sap.com/saphelp_nw04/helpdata/en/03/f6bc3d42f46c33e10000000a11405a/content.htm
In the above link you can find all the concepts clearly explained.You can also find the required tutorials for development.
Regards,
Vijith

Best practices for setting up projects

We recently adopted using Captivate for our WBT modules.
As a former Flash and Director user, I can say it’s
fast and does some great things. Doesn’t play so nice with
others on different occasions, but I’m learning. This forum
has been a great source for search and read on specific topics.
I’m trying to understand best practices for using this
product. We’ve had some problems with file size and
incorporating audio and video into our projects. Fortunately, the
forum has helped a lot with that. What I haven’t found a lot
of information on is good or better ways to set up individual
files, use multiple files and publish projects. We’ve decided
to go the route of putting standalones on our Intranet. My gut says
yuck, but for our situation I have yet to find a better way.
My question for discussion, then is: what are some best
practices for setting up individual files, using multiple files and
publishing projects? Any references or input on this would be
appreciated.

Hi,
Here are some of my suggestions:
1) Set up a style guide for all your standard slides. Eg.
Title slide, Index slide, chapter slide, end slide, screen capture,
non-screen capture, quizzes etc. This makes life a lot easier.
2) Create your own buttons and captions. The standard ones
are pretty ordinary, and it's hard to get a slick looking style
happening with the standard captions. They are pretty easy to
create (search for add print button to learn how to create
buttons). There should instructions on how to customise captions
somewhere on this forum. Customising means that you can also use
words, symbols, colours unique to your organisation.
3) Google elearning providers. Most use captivate and will
allow you to open samples or temporarily view selected modules.
This will give you great insight on what not to do and some good
ideas on what works well.
4) Timings: Using the above research, I got others to
complete the sample modules to get a feel for timings. The results
were clear, 10 mins good, 15 mins okay, 20 mins kind of okay, 30
mins bad, bad, bad. It's truly better to have a learner complete
2-3 short modules in 30 mins than one big monster. The other
benefit is that shorter files equal smaller size.
5) Narration: It's best to narrate each slide individually
(particularly for screen capture slides). You are more likely to
get it right on the first take, it's easier to edit and you don't
have to re-record the whole thing if you need to update it in
future. To get a slicker effect, use at least two voices: one male,
one female and use slightly different accents.
6) Screen capture slides: If you are recording filling out
long window based databse pages where the compulsory fields are
marked (eg. with a red asterisk) - you don't need to show how to
fill out every field. It's much easier for the learner (and you) to
show how to fill out the first few fields, then fade the screen
capture out, fade the end of the form in with the instructions on
what to do next. This will reduce your file size. In one of my
forms, this meant the removal of about 18 slides!
7) Auto captions: they are verbose (eg. 'Click on Print
Button' instead of 'Click Print'; 'Select the Print Preview item'
instead of 'Select Print Preview'). You have to edit them.
8) PC training syntax: Buttons and hyperlinks should normally
be 'click'; selections from drop down boxes or file lists are
normally 'select': Captivate sometimes mixes them up. Instructions
should always be written in the correct order: eg. Good: Click
'File', Select 'Print Preview'; Bad: Select 'Print Preview' from
the 'File Menu'. Button names, hyperlinks, selections are normally
written in bold
9) Instruction syntax: should always be written in an active
voice: eg. 'Click Options to open the printer menu' instead of
'When the Options button is clicked on, the printer menu will open'
10) Break all modules into chapters. Frame each chapter with
a chapter slide. It's also a good idea to show the Index page
before each chapter slide with a progress indicator (I use an
animated arrow to flash next to the name of the next chapter), I
use a start button rather a 'next' button for the start of each
chapter. You should always have a module overview with the purpose
of the course and a summary slide which states what was covered and
they have complete the module.
11) Put a transparent click button somewhere on each slide.
Set the properties of the click box to take the learner back to the
start of the current chapter by pressing F2. This allows them to
jump back to the start of their chapter at any time. You can also
do a similar thing on the index pages which jumps them to another
chapter.
12) Recording video capture: best to do it at normal speed
and be concious of where your mouse is. Minimise your clicks. Most
people (until they start working with captivate) are sloppy with
their mouse and you end up with lots of unnecessarily slides that
you have to delete out. The speed will default to how you recorded
it and this will reduce the amount of time you spend on changing
timings.
13) Captions: My rule of thumb is minimum of 4 seconds - and
longer depending on the amount of words. Eg. Click 'Print Preview'
is 4 seconds, a paragraph is longer. If you creating knowledge
based modules, make the timing long (eg. 2-3 minutes) and put in a
next button so that the learner can click when they are ready.
Also, narration means the slides will normally be slightly longer.
14) Be creative: Capitvate is desk bound. There are some
learners that just don't respond no matter how interactive
Captivate can be. Incorporate non-captivate and desk free
activities. Eg. As part of our OHS module, there is an activity
where the learner has to print off the floor plan, and then wander
around the floor marking on th emap key items such as: fire exits;
first aid kit, broom and mop cupboard, stationary cupboard, etc.
Good luck!

Best Practice for Using Static Data in PDPs or Project Plan

Hi There,
I want to make custom reports using PDPs & Project Plan data.
What is the Best Practice for using "Static/Random Data" (which is not available in MS Project 2013 columns) in PDPs & MS Project 2013?
Should I add that data in Custom Field (in MS Project 2013) or make PDPs?
Thanks,
EPM Consultant
Noman Sohail

Hi Dale,
I have a Project Level custom field "Supervisor Name" that is used for Project Information.
For the purpose of viewing that "Project Level custom field Data" in
Project views , I have made Task Level custom field
"SupName" and used Formula:
[SupName] = [Supervisor Name]
That shows Supervisor Name in Schedule.aspx
============
Question: I want that Project Level custom field "Supervisor Name" in
My Work views (Tasks.aspx).
The field is enabled in Task.aspx BUT Data is not present / blank column.
How can I get the data in "My Work views" ?
Noman Sohail

Best practice for putting together scenes in a Flash project?

Hi, I'm currently working on a flash project with the following characteristics:
using a PC
2048x1080 pixels
30 fps
One audio file that plays (once) continuously across the whole project
there are actions that relate to the audio, so the timing is important
at least 10 scenes
about 7 minutes long total
current intent is for it to be played in a modern theater as a surprise
What is the best practice for working on this project and then compiling it together?
Do it all in one project file?
Split the work into different project (xfl) files for each scene and then put it together when all the scenes are finalized?
Use one project file but create different "scenes" for each respective scene? I think this is the "classic" way (?).
Make the scenes "movie clips" and then insert them into the timeline with the audio as its own layer?
Other?
I'm currently working on it by having it all in one project file. But I've noticed that there's some lag (or it gets choppy) at certain parts during playback and the SWF history shows 3.1 MB with a yellow triangle with exclamation point symbol. Thanks in advance.

you would only do that if it makes your job easier. generally speaking, it would not.
when trying to sync sound and animation i think most authors find it easiest to use graphic symbols because you can see their animation when scrubbing the main timeline. with movieclips you only see their animation when testing.
however, if you're going to use actionscript to control some of your symbols, those symbols should be movieclips.

Best Practices for multiple authors using single project?

We are having many issues, particularly with moving, renaming, and multiple check out warnings. We have a single project with many authors and it seems like RH is not designed to work that way. There is an article in the RH devnet-archive in an article entitled "Sharing RoboHelp Project Among Multiple Authors" that says"
"At first there may be the temptation to let every author work on every file in a project. This is certainly not a best practice. Regardless of source contraol, it is always best to designate certain authors as owning certain content-related sections, folders, or topics within a project -particulary at the folder level."
This statement, and our experience seems to indicate that RH is not a true CMS as we had envisioned. What are the best practices for this scenario to avoid stepping on each others toes and having problems with source control.

I have moved this to the source control forum for the gurus there to answer.
Meantime I must admit I read that statement the same way as you first time. However, on rereading I think what the author is saying is not that what you want cannot be done, rather it is best practice to guide authors to work in discrete areas.
I will leave it to the author or another guru to give you a more complete answer.
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge

Best practice for SWC's in shared projects?

I'm creating a number of Flex components in Flash for a project where the development responsibilities will be shared between myself and another developer via SVN.
My question is regarding linking the SWC's in the Flex Build Path. The .swc files are stored in the project src folder (src/components/swc/Tab.swc) It doesn't look like I can use a relative path. When the other developer opens the project on his local workspace, will he have have to relink the SWC's?
What's the best practice for a scneario like this?

Um... ok. But, don't you still have to link the swc?
What I mean is, once I do that (place the swc in the library), I am unable to access that component. Seems as though I'm missing a step.
Will continue to consult the documentation, but some clarity on this would be appreciated. Thanks!

Validation Best Practice for an javafx project

Hello,
I am investigating how to validate a JavaFX project and specifically where to display the validation results with appropriate icons and text. Do you have any thoughts on best practice for this? Are there any features in JavaFX to do this? Are there any third-party library that does this?
Thanks

See:
Re: Forms and validations - here's some of my ideas, what are yours? "Thread: Forms and validations - here's some of my ideas, what are yours?"
And messages in this mailing list thread:
http://mail.openjdk.java.net/pipermail/openjfx-dev/2012-February/000717.html "Validate Me"

Help Please!! Best Practices for building an NDS Project...

We are doing a Proof of Concept on using NDS to develop non-SAP Java applications. We are attempting to determine if we can replace our current Java development tools with NDS/WAS.
We are struggling with SAP's terminology and "plumbing" for setting up/defining Java projects. For example, what is and when do you define Tracks, Software Components, Development Components, etc. All of these terms are totally foreign to us and do not relate to our current Java environment (at least not that we can see). We are also struggling with how the DTR and activities tie in to those components.
If any one has defined best practices for setting up Java projects or has struggled with and overcome these same issues, please provide us with some guidance. This is a very frustrating and time-consuming issue for us.
Thank you!!

Hello Peggy,
this is my first post but I hope it helps you anyway.
To learn the SAP "language" I additionally used the a SAP Presentation regarding the SAP JDI.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/documents/a1-8-4/java development infrastructure real world use webinar.pdf
I think this one is quite useful as an addon to the other links for information you already got. Your name also indicates that your mother-tongue language is German. If so, the german version of the book (Java-Programming with the SAP WAS) is already available for purchase and really useful. Then, you can also use the information provided by the University of Potsdam. They have an introduction about how to setup a track in the SLD and then how to setup SCs.
http://epic.hpi.uni-potsdam.de/nwlab/SC+Track.html
Hope this helps...

Best Practices for Maintaining SSAS Projects

We started using SSAS recently and we maintain we one project to deploy to both DEV and PROD instances by changing the deployment properties. However, this gets messy when we introduce new fact tables in to DEV data warehouse (that are not promoted to
Production data warehouse). While we work on adding new measure groups and calculations (based on new fact tables in DEV) we are unable to make any changes to production cube (such as changes to calculations, formatting etc) requested by business
users. Sorry for long question but is there is a best practice to manage projects and migrations? Thanks.

While we work on adding new measure groups and calculations (based on new fact tables in DEV) we are unable to make any changes to production cube (such as changes to calculations, formatting etc) requested by business users.
Hi Sbc_wisc,
You can create a new project by importing the metadata from the production cube on the server, using the template, Import from Server (Multidimensional and Data Mining) Project, in SQL Server Data Tools (SSDT). And then make some changes on this project
and then redeploy it to production server.
Referencec:
Import a Data Mining Project using the Analysis Services Import Wizard
Regards,
Charlie Liao
TechNet Community Support

Best practice for setting or detecting screen size?

Hi All,
Trying to determine a best practice for setting or detecting the screen size. For playbook and iOS, I can set them. But for Android, the number of devices is too large so I'd rather detect. My first choice is to use the stage.stageHeight and stage.stageWidth. This works fine if I set my stage properties with standard meta data:
[SWF(height="320", width="480", frameRate="64", backgroundColor="#010101")]
However, if I use the application descriptor file to set the stage dimentions (as suggested by Christian Cantrell here http://www.adobe.com/devnet/flash/articles/authoring_for_multiple_screen_sizes.html)
<initialWindow>
<aspectRatio>landscape</aspectRatio>
<autoOrients>false</autoOrients>
<width>320</width>
<height>480</height>
<fullScreen>true</fullScreen>
</initialWindow>
Then the stage.stageHeight and stage.stageWidth are not the correct numbers when my main class is added to the stage. Sometime after the main class is added to the stage, then those numbers are fine. Is there an event I can wait for to know that the stage.stageHeight and stage.stageWidth are correct?
Thanks in advance!

Hi Lee,
Thanks for the quick response! However, for some reason the heightPercent & widthPercent metadata tags are not working as expected for me.
I have a wrapper class that I target for compiling, WagErgApplePhone.as where I've got my metadata
[SWF(heightPercent="100%", widthPercent="100%", frameRate="64", backgroundColor="#010101")]
sets some stage properties
stage.quality=StageQuality.LOW;
stage.scaleMode = StageScaleMode.NO_SCALE;
stage.align = StageAlign.TOP_LEFT;
and instantiates my main class
var main:Main = new Main();
addChild(main);
my main class constructor even waits for the stage
public function Main(){
if (stage) init();
else addEventListener(Event.ADDED_TO_STAGE, init);
in my init function, stage.stageHeight traces out as 375 (expecting 320).
i have a function which is called via a button press event by the user, and stage.stageHeight traces out correctly (320) there. that's what makes me think that if i wait long enough, i can get the correct stageHeight before init/drawing. but i'm not sure what event to listen for, or if there's another trick.
if i use Capabilities.screenResolutionX and Capabilities.screenResolutionY the correct values are provided for mobile, but these values are not useful for the desktop and web version of the app. if there's no other solution, i'll execute different code depending on platform.
again, for reference, my app descriptor:
<initialWindow>
<aspectRatio>landscape</aspectRatio>
<autoOrients>false</autoOrients>
<width>320</width>
<height>480</height>
<content>bin-iOS/WagErgApplePhone.swf</content>
<title>WAG ERG</title>
<fullScreen>true</fullScreen>
<renderMode>cpu</renderMode>
</initialWindow>
looking forward to any other ideas to try out & thanks so much for your thoughts! if you want to really dig in, this is an opensource project at code.google.com/p/wag-erg/

Best practice for responsive projects

Similar Messages

Maybe you are looking for