[Pro] Fair question?

I’ve been thinking a lot about some things related to Freeway Pro. Would it be fair to suggest that the usability of the application, among pro users at least, is due in large part to the efforts of Action developers?


offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

I’ve always thought so. If you take an honest look there isn’t a lot of core functionality or tools, take the actions away and what do you have, really? A scaffold. The actions flesh out the app, no doubt, but to me an action is not the same thing as an actual “tool”. I would like to see more tools. More CSS tools. More code tools. More standalone core features and tools.

Todd

I’ve been thinking a lot about some things related to Freeway Pro. Would it be fair to suggest that the usability of the application, among pro users at least, is due in large part to the efforts of Action developers?


offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

I would like to see more tools. More CSS tools. More code tools. More standalone core features and tools.

But is there such a thing?

With FW6 and native HTML5 support what should be added that someone like you cannot do already?

D


offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

There are some incredibly useful actions that quite frankly should be core features, not actions. Things like Walter’s Crowbar, or Remove Div Styles, or Tim’s Externalize, or any number of the other more “techy” actions, all of which perform practical real-world functions that many of the Pro users frequently rely on that should be a core tool, not a bolt-on action. Really, why should I have to rely on a 3rd Party action to remove inline styles or a

tag? I shouldn’t. To me actions make sense for things like Carousels and things like that but the daily nut-n-bolt work should be the responsibility of the mother app, not actions. There should be a deeper integration of practical core tools to do this common and mundane stuff. The CSS Editor is ripe for more tools so we can tweak it the way some of us want to.

Also, with regard to actions, a much deeper API access for the action devs so the actions they do write can really sing. I know for a fact that a lot of devs have their wings clipped by the currently limited API and it’s very frustrating for them.

Todd

I would like to see more tools. More CSS tools. More code tools. More standalone core features and tools.

But is there such a thing?

With FW6 and native HTML5 support what should be added that someone like you cannot do already?


offtopic mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options