A, V and I pretty much covered it. Sometimes we'll decide to hard code
width/height a few times too. It's nice to be able to set component IDs
quickly. Think tweaking and positioning of components, not mock ups.
Sometimes we'll find that the original layout of a large form doesn't
quite work (data turns out to be too verbose for a field's width, etc),
and it'll require drag/drop to *quickly* reorganize things.
Yes, some of these forms are packing a lot of fields, but that's how the
users always want/need it, rather than having ten different pages of a
workflow to click around. In fact I'm in the process of changing a
"workflow form" type UI into a consolidated 2-3 page one now. I can't
elaborate on type of work, but it's usually a lot of data collection
which needs to be efficiently entered.
If it were up to me, we'd have the tools needed, but that'll never be
easy. Based on an article I read once, a lot of devs are in this same
boat - usually cheap or otherwise ignorant management refuse to buy
tools, or a "process" makes your life hell to do so. Allegedly this is
one of the reasons FOSS tools are popular.
Just to note, I don't expect the Apache Flex team or anyone else to
"solve our problem", but maybe this helps raise awareness. I want this
SDK to be a long term success.
-Eric
On 10/13/2013 10:03 AM, Avi Kessner wrote:
I'm a bit perplexed by the notion that inkscape can help someone correct
CSS percentages, or x,y values for flex components when the border gets
drawn on the outside of the boundaries or on the center of it, or when a
half pixel gets rounded up vs rounded down.
brought to you by the letters A, V, and I
and the number 47
On Sun, Oct 13, 2013 at 5:16 AM, Nick Collins <ndcoll...@gmail.com> wrote:
I would be interested to know what you are doing that you can't accomplish
with Gimp and Inkscape (since free seems to be high on your priority list).
Personally, from my perspective if this is something you are doing
professionally, you need to invest in your tools. Same as does a carpenter,
a mechanic, etc.
The base tool can be a FOSS application, but then invest in writing your
own plugins and extensions to enhance your workflow and meet your needs.
- Nick
On Sat, Oct 12, 2013 at 11:19 AM, Eric <eh.fx...@gmail.com> wrote:
I've already beaten this horse before, but I have to wonder if the lack
of
a first class + free design view tool is also a significant factor. I
know
that for us, it's a primary factor. We don't want to risk losing the
capability for doing major UI redesigns or tweaks for our production
stuff,
and don't want to be in the business of having to change component
sizes/coords in code and then navigate the application to see how it
looks.
Maybe I should build a demo interface which illustrates why this is so
important to us, and to see if we just have rare requirements.
A poll (preferably one using multi-select checkboxes, not radiobutton)
asking why devs haven't switched yet would be interesting if it can reach
enough of the right people. I'd suspect the main reason is "no need",
and
possibly custom component support (a factor for us too with some Flextras
stuff), but other than that I'm not sure.
-Eric
On 10/4/2013 10:09 AM, Rushme Nayak wrote:
really good news :)
http://blog.jetbrains.com/**idea/2013/10/how-is-flex-**
doing-quick-start-guides-and-**tutorials/<
http://blog.jetbrains.com/idea/2013/10/how-is-flex-doing-quick-start-guides-and-tutorials/
