On 20 May 2014, 9:06 am, derekzinger wrote:
Um, I am learning the code side of things. Which by the way also makes me want easier ways to edit the code from Freeway.
Excellent and agreed
And who’s complaining the box-model here? As I mentioned above, up to now, I’ve preferred to build my sites from scratch, and I primarily use the box-model.
Nobody - but “responsive” is complained all over the place and without the one, the other won’t be reachable ever. And if you can deal with inflow-items, why not start to play with @media breakpoints?
So if, as you say, Thomas, experienced FW users build their templates in minutes, who are SP aiming their templates at? Just the Express users?
No - cause Express can’t handle relative positioned items. But there are way more people here on board (not in this list here) that could be the target ( the “I’ve been chosen Freeway cause I don’t want to deal with code” audience). I’m looking forward how they try to adjust the templates with their table-drop-and-drag I have to move items all over the place philosophy.
And yeah, I do want a nice friendly workspace in which to build responsive sites. Something that speeds up my workflow. Freeway already does this in many different areas, so I fail to see why responsiveness, at least in theory, shouldn’t be added to the mix.
As well agreed here. But responsive means decisions prepared now and adjusted later. And for this we need as I already said a dynamic workspace and relative propositioned items.
Caleb has done an awesome job with Backdraft,
but it would be great to see SP implement other responsive features directly into the app.
We don’t need responsive features on first place, but features help us to quicker adjust things such as a small, small code-editor like surrounding for ALL mark-up places.
… and way more in mind.
freewaytalk mailing list
Update your subscriptions at: