O'Reilly Apache Flex book help

[Joseph Balderson <ne...@joeflash.ca>]

Hi all,

The latest news on the Apache Flex book with O'Reilly is that I'm currently in
negotiations with them to have this book made, i.e. "Programming Apache Flex" as
a continuance of that same series. It's taking some convincing to be honest,
because the perception in the tech publishing industry right now is that Flash
and Flex books are a lost leader, and more or less a dead ecosystem.

In response I mentioned to them that since Flex is now truly open source under
Apache, that O'Reilly would be seen to be promoting open source software, which
is very much within their mandate. And that, of course, Flex is not dead; in
fact it has every indication of making somewhat of a comeback, according to the
"word on the street," evidenced by a slow trickle of client work back to Flex,
supported by AIR winning an award at the 2013 CES for "Best Consumer Application
Development Platform for Mobile" (1,2)

However, I may be able to convince O'Reilly to go ahead with a digital-only
version which would minimize their costs. And if they agree to this, I have
offered to waive any fees or royalties associated with the book on my part, to
be considered "my donation" to the Apache Flex community. If O'Reilly breaks
even or even makes a slight profit (and the profit margins on tech books are
insanely low), then the project will stand a chance of going forward, and
waiving my fees might just be what tips the balance. And of course I mentioned
that, wouldn't it be embarrassing when Flex springs back in this next year and
there are no Flex books with the O'Reilly name on it? ;)

We'll see what happens, if O'Reilly accepts my proposal. I understand how
perception is in part largely responsible for driving sales of tech books. But
stakeholders and students are not the only ones who can drive book sales: a
niche community of developers can also do so.

And so I need your help, everyone in the Flex community. I'll need an
experienced tech editor who is willing to help out with this, to donate their
time to the project. And I will need everyone's help in promoting this book when
it comes out, and to buy one, so that O'Reilly can justify the ROI to go ahead
with the project.

This book will be seen as a huge boon to Apache Flex, to prove to all the
managers and stakeholders drinking the HTML5 koolaid, that Flex isn't dead, and
it is very much alive and well.

Thanks all in advance for your support,

Joseph


(1)
http://www.beedigital.net/2014/01/09/air-wins-award-at-ces-for-the-best-mobile-application-product-in-2014/
(2)
http://www.compassintelligence.com/?q=press/compass-intelligence-announces-winners-2014-mobility-awards-wireless-m2m-and-green-technology


-- 
_______________________________________________________________________

Joseph Balderson, Flex & Flash Platform Developer :: http://joeflash.ca
Author, Professional Flex 3 :: http://tinyurl.com/proflex3book

Re: O'Reilly Apache Flex book help

[Joseph Balderson <ne...@joeflash.ca>]

I do not think that will help. Like I said earlier, my agent, who knows anyone
who's anyone in tech publishing, spoke to two senior acquisition editors at
O'Reilly, and forwarded me their reply. They are not interested. O'Reilly is off
the table.


_______________________________________________________________________

Joseph Balderson, Flex & Flash Platform Developer :: http://joeflash.ca
Author, Professional Flex 3 :: http://tinyurl.com/proflex3book

jude wrote:
> Do you want us to email the O'Reilly guys? One suggestion since books can
> take a great deal of time is to get a few tech editors. Maybe one or two
> per chapter?
> 
> 
> On Sat, Jan 25, 2014 at 10:06 AM, Joseph Balderson <ne...@joeflash.ca> wrote:
> 
>> Anyone is free to do as they wish... I am not standing in the way of
>> anyone who
>> wants to write a Flex book. This is simply the path that I am taking.
>>
>> In this day and age of self-publishing, of what relevance are traditional
>> publishing houses? That's a good question. It's not because they print
>> physical
>> books anymore, that model has long since died. It's for other reasons.
>>
>> 1) Perception: stakeholders and managers still look upon traditional
>> publishing
>> houses as thought leaders, or at least responsive to tech market trends as
>> opposed to developer fanbase trends. The perception is that the dog (market
>> trends) wags the tail (developer adoption), but in many cases it's
>> actually the
>> tail which wags the dog. What's the same in either case is the dog and the
>> tail,
>> they are part of the same ecosystem. Self-published books sidestep this
>> perception. So that you have only the tail, so to speak. All of which
>> means that
>> a self/community-published book needs to have an awful lot of buzz to wag
>> the dog.
>>
>> In the case of O'Reilly, they are a publishing house and they're
>> considered a
>> thought leader in the tech space, which is why it would have been nice to
>> have
>> such a title. An O'Reilly book would have been as good as an endorsement
>> of the
>> continued viability of the tech, but that's merely the perception. In
>> reality
>> O'Reilly is not so much a thought leader as a thought promoter: they still
>> respond to perceived market trends as much as everyone else.
>>
>> 2) Reach. Traditional publishing houses can guarantee books in
>> brick-and-mortar
>> stores and online marketplaces. The former is becoming less and less
>> relevant,
>> but the latter is key. No matter what self-publishing capabilities exist on
>> Amazon and other online marketplaces, the distribution is fragmented. In
>> the
>> case of a major publishing house, brand recognition helps distribution and
>> sales. And increased sales means increased reach. That's not to say that
>> self-publishing cannot do the same, but it takes more work and more buzz.
>>
>> 3) Infrastructure. This one is key. Many people do not realize it, but the
>> resources a publishing house brings to the table are not only about graphic
>> design and distribution. They have full-time staff editors with literary
>> qualifications to ensure that the book itself is well written with no
>> glaring
>> typos and grammatical mistakes. Having been through the publishing process
>> on
>> several occasions, I can emphatically say that I am eternally grateful for
>> editors who had my back. The tech editor, usually chosen by the author,
>> verifies
>> the quality of the technical aspects of the book. But it takes a literary
>> editor
>> to ensure that the book as a whole is well-written. We are so used to
>> well-written books that all you have to do is read a few reviews of books
>> from
>> lesser publishing houses which basically exist to rubber-stamp
>> self-published
>> works, and you can feel the heat from the flames in the reviews: it doesn't
>> matter how engaging the material, but if the grammar is sloppy and the
>> text is
>> rife with uncaught typos, the book will tank.
>>
>> Not to mention that they have access to legal resources that a
>> self-publisher
>> would not have or would be a real pain to do oneself. When I write an
>> Apache
>> book, I don't have to worry a whit about copyright or trademark issues: the
>> publisher deals directly with the trademark suits at Apache, Adobe or
>> anyone
>> else referenced in the book. I can use the words "Apache Flex" in the book
>> title
>> without getting into long and frustrating conversations with Apache's legal
>> department. It's already taken care of, because chances are that that
>> publishing
>> house already has a few Apache-related books under its belt and the process
>> becomes automatic. One less headache for the author. I have enough
>> headaches
>> just writing the thing, I don't need to deal with that as well.
>>
>> 4) Remuneration. No one makes a living writing tech books, it's like
>> working
>> retail for the amount of hours one puts in. But at least there is a slight
>> chance you'll get paid; there is an advance, and if you're lucky the
>> publisher
>> will break even and you may even see a dollar or two of royalties. If one
>> is
>> fortunate enough to be in a tech that's popular and you have a reputation,
>> some
>> authors can write several books a year and make it into a nice part time
>> job.
>> For most of us though, after working on a book for 500-1000 hours, it's
>> nice to
>> see a few dollars in the bank at the end of it all. With self-publishing,
>> that's
>> all up in the air.
>>
>>
>> _______________________________________________________________________
>>
>> Joseph Balderson, Flex & Flash Platform Developer :: http://joeflash.ca
>> Author, Professional Flex 3 :: http://tinyurl.com/proflex3book
>>
>> Jeffry Houser wrote:
>>> On 1/24/2014 5:10 PM, Justin Mclean wrote:
>>>> Hi,
>>>>
>>>>> Well, I just heard back from O'Reilly. And unfortunately they're not
>>>>> interested
>>>>> in publishing an Apache Flex book of any kind
>>>> While it would of been nice to have them as a publisher (print book,
>>>> distribution, marketing etc etc) do we actually need a publisher?
>>>>
>>>> In this day and age it's easy enough to publish ebooks.
>>>   I was thinking the same thing.  The big benefit of having a
>>> traditional publisher is that they can get 'paper copy' books into real
>>> bookstores.
>>>   The real drawback of 'paper' books in real bookstores is that
>>> programmers will never know this book existed.
>>>
> 

Re: O'Reilly Apache Flex book help

[jude <fl...@gmail.com>]

Do you want us to email the O'Reilly guys? One suggestion since books can
take a great deal of time is to get a few tech editors. Maybe one or two
per chapter?


On Sat, Jan 25, 2014 at 10:06 AM, Joseph Balderson <ne...@joeflash.ca> wrote:

> Anyone is free to do as they wish... I am not standing in the way of
> anyone who
> wants to write a Flex book. This is simply the path that I am taking.
>
> In this day and age of self-publishing, of what relevance are traditional
> publishing houses? That's a good question. It's not because they print
> physical
> books anymore, that model has long since died. It's for other reasons.
>
> 1) Perception: stakeholders and managers still look upon traditional
> publishing
> houses as thought leaders, or at least responsive to tech market trends as
> opposed to developer fanbase trends. The perception is that the dog (market
> trends) wags the tail (developer adoption), but in many cases it's
> actually the
> tail which wags the dog. What's the same in either case is the dog and the
> tail,
> they are part of the same ecosystem. Self-published books sidestep this
> perception. So that you have only the tail, so to speak. All of which
> means that
> a self/community-published book needs to have an awful lot of buzz to wag
> the dog.
>
> In the case of O'Reilly, they are a publishing house and they're
> considered a
> thought leader in the tech space, which is why it would have been nice to
> have
> such a title. An O'Reilly book would have been as good as an endorsement
> of the
> continued viability of the tech, but that's merely the perception. In
> reality
> O'Reilly is not so much a thought leader as a thought promoter: they still
> respond to perceived market trends as much as everyone else.
>
> 2) Reach. Traditional publishing houses can guarantee books in
> brick-and-mortar
> stores and online marketplaces. The former is becoming less and less
> relevant,
> but the latter is key. No matter what self-publishing capabilities exist on
> Amazon and other online marketplaces, the distribution is fragmented. In
> the
> case of a major publishing house, brand recognition helps distribution and
> sales. And increased sales means increased reach. That's not to say that
> self-publishing cannot do the same, but it takes more work and more buzz.
>
> 3) Infrastructure. This one is key. Many people do not realize it, but the
> resources a publishing house brings to the table are not only about graphic
> design and distribution. They have full-time staff editors with literary
> qualifications to ensure that the book itself is well written with no
> glaring
> typos and grammatical mistakes. Having been through the publishing process
> on
> several occasions, I can emphatically say that I am eternally grateful for
> editors who had my back. The tech editor, usually chosen by the author,
> verifies
> the quality of the technical aspects of the book. But it takes a literary
> editor
> to ensure that the book as a whole is well-written. We are so used to
> well-written books that all you have to do is read a few reviews of books
> from
> lesser publishing houses which basically exist to rubber-stamp
> self-published
> works, and you can feel the heat from the flames in the reviews: it doesn't
> matter how engaging the material, but if the grammar is sloppy and the
> text is
> rife with uncaught typos, the book will tank.
>
> Not to mention that they have access to legal resources that a
> self-publisher
> would not have or would be a real pain to do oneself. When I write an
> Apache
> book, I don't have to worry a whit about copyright or trademark issues: the
> publisher deals directly with the trademark suits at Apache, Adobe or
> anyone
> else referenced in the book. I can use the words "Apache Flex" in the book
> title
> without getting into long and frustrating conversations with Apache's legal
> department. It's already taken care of, because chances are that that
> publishing
> house already has a few Apache-related books under its belt and the process
> becomes automatic. One less headache for the author. I have enough
> headaches
> just writing the thing, I don't need to deal with that as well.
>
> 4) Remuneration. No one makes a living writing tech books, it's like
> working
> retail for the amount of hours one puts in. But at least there is a slight
> chance you'll get paid; there is an advance, and if you're lucky the
> publisher
> will break even and you may even see a dollar or two of royalties. If one
> is
> fortunate enough to be in a tech that's popular and you have a reputation,
> some
> authors can write several books a year and make it into a nice part time
> job.
> For most of us though, after working on a book for 500-1000 hours, it's
> nice to
> see a few dollars in the bank at the end of it all. With self-publishing,
> that's
> all up in the air.
>
>
> _______________________________________________________________________
>
> Joseph Balderson, Flex & Flash Platform Developer :: http://joeflash.ca
> Author, Professional Flex 3 :: http://tinyurl.com/proflex3book
>
> Jeffry Houser wrote:
> > On 1/24/2014 5:10 PM, Justin Mclean wrote:
> >> Hi,
> >>
> >>> Well, I just heard back from O'Reilly. And unfortunately they're not
> >>> interested
> >>> in publishing an Apache Flex book of any kind
> >> While it would of been nice to have them as a publisher (print book,
> >> distribution, marketing etc etc) do we actually need a publisher?
> >>
> >> In this day and age it's easy enough to publish ebooks.
> >
> >   I was thinking the same thing.  The big benefit of having a
> > traditional publisher is that they can get 'paper copy' books into real
> > bookstores.
> >   The real drawback of 'paper' books in real bookstores is that
> > programmers will never know this book existed.
> >
>

Re: O'Reilly Apache Flex book help

[Joseph Balderson <ne...@joeflash.ca>]

Anyone is free to do as they wish... I am not standing in the way of anyone who
wants to write a Flex book. This is simply the path that I am taking.

In this day and age of self-publishing, of what relevance are traditional
publishing houses? That's a good question. It's not because they print physical
books anymore, that model has long since died. It's for other reasons.

1) Perception: stakeholders and managers still look upon traditional publishing
houses as thought leaders, or at least responsive to tech market trends as
opposed to developer fanbase trends. The perception is that the dog (market
trends) wags the tail (developer adoption), but in many cases it's actually the
tail which wags the dog. What's the same in either case is the dog and the tail,
they are part of the same ecosystem. Self-published books sidestep this
perception. So that you have only the tail, so to speak. All of which means that
a self/community-published book needs to have an awful lot of buzz to wag the dog.

In the case of O'Reilly, they are a publishing house and they're considered a
thought leader in the tech space, which is why it would have been nice to have
such a title. An O'Reilly book would have been as good as an endorsement of the
continued viability of the tech, but that's merely the perception. In reality
O'Reilly is not so much a thought leader as a thought promoter: they still
respond to perceived market trends as much as everyone else.

2) Reach. Traditional publishing houses can guarantee books in brick-and-mortar
stores and online marketplaces. The former is becoming less and less relevant,
but the latter is key. No matter what self-publishing capabilities exist on
Amazon and other online marketplaces, the distribution is fragmented. In the
case of a major publishing house, brand recognition helps distribution and
sales. And increased sales means increased reach. That's not to say that
self-publishing cannot do the same, but it takes more work and more buzz.

3) Infrastructure. This one is key. Many people do not realize it, but the
resources a publishing house brings to the table are not only about graphic
design and distribution. They have full-time staff editors with literary
qualifications to ensure that the book itself is well written with no glaring
typos and grammatical mistakes. Having been through the publishing process on
several occasions, I can emphatically say that I am eternally grateful for
editors who had my back. The tech editor, usually chosen by the author, verifies
the quality of the technical aspects of the book. But it takes a literary editor
to ensure that the book as a whole is well-written. We are so used to
well-written books that all you have to do is read a few reviews of books from
lesser publishing houses which basically exist to rubber-stamp self-published
works, and you can feel the heat from the flames in the reviews: it doesn't
matter how engaging the material, but if the grammar is sloppy and the text is
rife with uncaught typos, the book will tank.

Not to mention that they have access to legal resources that a self-publisher
would not have or would be a real pain to do oneself. When I write an Apache
book, I don't have to worry a whit about copyright or trademark issues: the
publisher deals directly with the trademark suits at Apache, Adobe or anyone
else referenced in the book. I can use the words "Apache Flex" in the book title
without getting into long and frustrating conversations with Apache's legal
department. It's already taken care of, because chances are that that publishing
house already has a few Apache-related books under its belt and the process
becomes automatic. One less headache for the author. I have enough headaches
just writing the thing, I don't need to deal with that as well.

4) Remuneration. No one makes a living writing tech books, it's like working
retail for the amount of hours one puts in. But at least there is a slight
chance you'll get paid; there is an advance, and if you're lucky the publisher
will break even and you may even see a dollar or two of royalties. If one is
fortunate enough to be in a tech that's popular and you have a reputation, some
authors can write several books a year and make it into a nice part time job.
For most of us though, after working on a book for 500-1000 hours, it's nice to
see a few dollars in the bank at the end of it all. With self-publishing, that's
all up in the air.


_______________________________________________________________________

Joseph Balderson, Flex & Flash Platform Developer :: http://joeflash.ca
Author, Professional Flex 3 :: http://tinyurl.com/proflex3book

Jeffry Houser wrote:
> On 1/24/2014 5:10 PM, Justin Mclean wrote:
>> Hi,
>>
>>> Well, I just heard back from O'Reilly. And unfortunately they're not
>>> interested
>>> in publishing an Apache Flex book of any kind
>> While it would of been nice to have them as a publisher (print book,
>> distribution, marketing etc etc) do we actually need a publisher?
>>
>> In this day and age it's easy enough to publish ebooks.
> 
>   I was thinking the same thing.  The big benefit of having a
> traditional publisher is that they can get 'paper copy' books into real
> bookstores.
>   The real drawback of 'paper' books in real bookstores is that
> programmers will never know this book existed.
> 

RE: O'Reilly Apache Flex book help

[Sugan Naicker <Su...@Dev-X.co.za>]

Hi Nigel,

+1 - Fully agree!

Regards,

Sugan Naicker
South Africa


-----Original Message-----
From: Nigel Hillier [mailto:nigel555666@hotmail.com] 
Sent: 25 January 2014 03:15 PM
To: users@flex.apache.org
Subject: RE: O'Reilly Apache Flex book help

There are many ways to skin a cat.
Ask the major IDE vendors how many licences they sold in the last 24 months,
and for the names of their top 50 corporate sites Then approach those top
corporates and ask them to donate a week of their top architects or standard
materials It's in their interests
a) they have standard guides in-house for MVC, test & OOP anyway, and
putting some in a book will help attract new talent they need
b) they can show off why flex is the only solution for their immersive
experiences
c) they can afford 1 week from a team of 50 or more
d) the book gets written quicker
e) the vendors get the message out that there's demand for programmers
f) the programmers buy the book as they see the need for their skills
g) corporates can fund face-face meetings which will help
h) the book is guided in content to what is needed in the real world

I'm sure someone can go on all the way to z :)

-----Original Message-----
From: Phil [mailto:philip.medlam@gmail.com]
Sent: 25 January 2014 08:43
To: users@flex.apache.org
Subject: Re: O'Reilly Apache Flex book help

I run a small startup publishing company and would be happy to create an
ePub and publish it on amazon and Apple stores.

Check out GlowBooks.biz if this is of interest.

Phil 

Sent from my iPad

> On 24 Jan 2014, at 22:36, modjklist@comcast.net wrote:
> 
> I'd think as long as you can get it on Amazon, that should be sufficient.
Here's an example of a DSP book that's sold on Amazon and available online
as well. 
> 
> http://www.dspguide.com/editions.htm
> 
> ----- Original Message -----
> 
> From: "Jeffry Houser" <je...@dot-com-it.com>
> To: users@flex.apache.org
> Sent: Friday, January 24, 2014 2:26:54 PM
> Subject: Re: O'Reilly Apache Flex book help
> 
>> On 1/24/2014 5:10 PM, Justin Mclean wrote: 
>> Hi,
>> 
>>> Well, I just heard back from O'Reilly. And unfortunately they're not 
>>> interested in publishing an Apache Flex book of any kind
>> While it would of been nice to have them as a publisher (print book,
distribution, marketing etc etc) do we actually need a publisher? 
>> 
>> In this day and age it's easy enough to publish ebooks.
> 
> I was thinking the same thing. The big benefit of having a traditional 
> publisher is that they can get 'paper copy' books into real 
> bookstores.
> The real drawback of 'paper' books in real bookstores is that 
> programmers will never know this book existed.
> 
> --
> Jeffry Houser
> Technical Entrepreneur
> http://www.jeffryhouser.com
> 203-379-0773
> 
> 

RE: O'Reilly Apache Flex book help

[Nigel Hillier <ni...@hotmail.com>]

There are many ways to skin a cat.
Ask the major IDE vendors how many licences they sold in the last 24 months,
and for the names of their top 50 corporate sites
Then approach those top corporates and ask them to donate a week of their
top architects or standard materials
It's in their interests
a) they have standard guides in-house for MVC, test & OOP anyway, and
putting some in a book will help attract new talent they need
b) they can show off why flex is the only solution for their immersive
experiences
c) they can afford 1 week from a team of 50 or more
d) the book gets written quicker
e) the vendors get the message out that there's demand for programmers
f) the programmers buy the book as they see the need for their skills
g) corporates can fund face-face meetings which will help
h) the book is guided in content to what is needed in the real world

I'm sure someone can go on all the way to z :)

-----Original Message-----
From: Phil [mailto:philip.medlam@gmail.com] 
Sent: 25 January 2014 08:43
To: users@flex.apache.org
Subject: Re: O'Reilly Apache Flex book help

I run a small startup publishing company and would be happy to create an
ePub and publish it on amazon and Apple stores.

Check out GlowBooks.biz if this is of interest.

Phil 

Sent from my iPad

> On 24 Jan 2014, at 22:36, modjklist@comcast.net wrote:
> 
> I'd think as long as you can get it on Amazon, that should be sufficient.
Here's an example of a DSP book that's sold on Amazon and available online
as well. 
> 
> http://www.dspguide.com/editions.htm
> 
> ----- Original Message -----
> 
> From: "Jeffry Houser" <je...@dot-com-it.com>
> To: users@flex.apache.org
> Sent: Friday, January 24, 2014 2:26:54 PM
> Subject: Re: O'Reilly Apache Flex book help
> 
>> On 1/24/2014 5:10 PM, Justin Mclean wrote: 
>> Hi,
>> 
>>> Well, I just heard back from O'Reilly. And unfortunately they're not 
>>> interested in publishing an Apache Flex book of any kind
>> While it would of been nice to have them as a publisher (print book,
distribution, marketing etc etc) do we actually need a publisher? 
>> 
>> In this day and age it's easy enough to publish ebooks.
> 
> I was thinking the same thing. The big benefit of having a traditional 
> publisher is that they can get 'paper copy' books into real 
> bookstores.
> The real drawback of 'paper' books in real bookstores is that 
> programmers will never know this book existed.
> 
> --
> Jeffry Houser
> Technical Entrepreneur
> http://www.jeffryhouser.com
> 203-379-0773
> 
> 

Re: O'Reilly Apache Flex book help

[Phil <ph...@gmail.com>]

I run a small startup publishing company and would be happy to create an ePub and publish it on amazon and Apple stores.

Check out GlowBooks.biz if this is of interest.

Phil 

Sent from my iPad

> On 24 Jan 2014, at 22:36, modjklist@comcast.net wrote:
> 
> I'd think as long as you can get it on Amazon, that should be sufficient. Here's an example of a DSP book that's sold on Amazon and available online as well. 
> 
> http://www.dspguide.com/editions.htm 
> 
> ----- Original Message -----
> 
> From: "Jeffry Houser" <je...@dot-com-it.com> 
> To: users@flex.apache.org 
> Sent: Friday, January 24, 2014 2:26:54 PM 
> Subject: Re: O'Reilly Apache Flex book help 
> 
>> On 1/24/2014 5:10 PM, Justin Mclean wrote: 
>> Hi, 
>> 
>>> Well, I just heard back from O'Reilly. And unfortunately they're not interested 
>>> in publishing an Apache Flex book of any kind
>> While it would of been nice to have them as a publisher (print book, distribution, marketing etc etc) do we actually need a publisher? 
>> 
>> In this day and age it's easy enough to publish ebooks.
> 
> I was thinking the same thing. The big benefit of having a 
> traditional publisher is that they can get 'paper copy' books into real 
> bookstores. 
> The real drawback of 'paper' books in real bookstores is that 
> programmers will never know this book existed. 
> 
> -- 
> Jeffry Houser 
> Technical Entrepreneur 
> http://www.jeffryhouser.com 
> 203-379-0773 
> 
> 

Re: O'Reilly Apache Flex book help

[mo...@comcast.net]

I'd think as long as you can get it on Amazon, that should be sufficient. Here's an example of a DSP book that's sold on Amazon and available online as well. 

http://www.dspguide.com/editions.htm 

----- Original Message -----

From: "Jeffry Houser" <je...@dot-com-it.com> 
To: users@flex.apache.org 
Sent: Friday, January 24, 2014 2:26:54 PM 
Subject: Re: O'Reilly Apache Flex book help 

On 1/24/2014 5:10 PM, Justin Mclean wrote: 
> Hi, 
> 
>> Well, I just heard back from O'Reilly. And unfortunately they're not interested 
>> in publishing an Apache Flex book of any kind 
> While it would of been nice to have them as a publisher (print book, distribution, marketing etc etc) do we actually need a publisher? 
> 
> In this day and age it's easy enough to publish ebooks. 

I was thinking the same thing. The big benefit of having a 
traditional publisher is that they can get 'paper copy' books into real 
bookstores. 
The real drawback of 'paper' books in real bookstores is that 
programmers will never know this book existed. 

-- 
Jeffry Houser 
Technical Entrepreneur 
http://www.jeffryhouser.com 
203-379-0773 

Re: O'Reilly Apache Flex book help

[Jeffry Houser <je...@dot-com-it.com>]

On 1/24/2014 5:10 PM, Justin Mclean wrote:
> Hi,
>
>> Well, I just heard back from O'Reilly. And unfortunately they're not interested
>> in publishing an Apache Flex book of any kind
> While it would of been nice to have them as a publisher (print book, distribution, marketing etc etc) do we actually need a publisher?
>
> In this day and age it's easy enough to publish ebooks.

   I was thinking the same thing.  The big benefit of having a 
traditional publisher is that they can get 'paper copy' books into real 
bookstores.
   The real drawback of 'paper' books in real bookstores is that 
programmers will never know this book existed.

-- 
Jeffry Houser
Technical Entrepreneur
http://www.jeffryhouser.com
203-379-0773

Re: O'Reilly Apache Flex book help

[Angelo Anolin <an...@gmail.com>]

How about LeanPub? Would that be an option?
On 2014-01-24 4:47 PM, "Jeffry Houser" <je...@dot-com-it.com> wrote:

> On 1/24/2014 5:31 PM, Joseph Balderson wrote:
>
>> These days, if you want to get on Amazon, you need to be with a major
>> publisher.
>>
>  In my version of the world, this isn't true:
>
> https://kdp.amazon.com/
>
>
>
> --
> Jeffry Houser
> Technical Entrepreneur
> http://www.jeffryhouser.com
> 203-379-0773
>
>

Re: O'Reilly Apache Flex book help

[Jeffry Houser <je...@dot-com-it.com>]

On 1/24/2014 5:31 PM, Joseph Balderson wrote:
> These days, if you want to get on Amazon, you need to be with a major publisher.
  In my version of the world, this isn't true:

https://kdp.amazon.com/



-- 
Jeffry Houser
Technical Entrepreneur
http://www.jeffryhouser.com
203-379-0773

Re: O'Reilly Apache Flex book help

[Joseph Balderson <ne...@joeflash.ca>]

These days, if you want to get on Amazon, you need to be with a major publisher.
If it were a work of fiction I'd say sure, self-publish, and let it coast on
buzz. Having had experience with publishers, I can categorically state that
going with a major publisher is not just about distribution of paper books: how
often and how recently a tech is published in books is directly related to the
perception of the relevance of that technology.

So an Apache Flex book is more than just a reference manual: this book needs to
be a statement to the world that Flex isn't dead, that it is still very much
alive and kicking, to show all the doubters that they were wrong, and that the
move to Apache was a step forward, not backwards.

And for that we need the reputation, the reach and the distribution of a major
publisher. So self-publishing is self-defeating to that purpose, because it says
to the world that Flex is no longer prime time, which is not the message we
should be sending.

I have a list of publishers and an excellent agent who knows everyone who's
everyone in tech publishing. I'll find a publisher who's willing to do this. And
with everyone's help, it will be a huge success for the community and for the
publisher.


_______________________________________________________________________

Joseph Balderson, Flex & Flash Platform Developer :: http://joeflash.ca
Author, Professional Flex 3 :: http://tinyurl.com/proflex3book

Justin Mclean wrote:
> Hi,
> 
>> Well, I just heard back from O'Reilly. And unfortunately they're not interested
>> in publishing an Apache Flex book of any kind
> 
> While it would of been nice to have them as a publisher (print book, distribution, marketing etc etc) do we actually need a publisher?
> 
> In this day and age it's easy enough to publish ebooks.
> 
> Thanks,
> Justin

Re: O'Reilly Apache Flex book help

[Justin Mclean <ju...@classsoftware.com>]

Hi,

> Well, I just heard back from O'Reilly. And unfortunately they're not interested
> in publishing an Apache Flex book of any kind

While it would of been nice to have them as a publisher (print book, distribution, marketing etc etc) do we actually need a publisher?

In this day and age it's easy enough to publish ebooks.

Thanks,
Justin

Re: O'Reilly Apache Flex book help

[Joseph Balderson <ne...@joeflash.ca>]

It's a nice idea, but, different projects, different O'Reilly managers,
different policies. It's been made clear to me by two senior acquisition staff
members at O'Reilly that they are simply not interested in a Flex book of any
kind at this time, there wasn't even an opening for negotiation. Unfortunate --
but then, O'Reilly's loss will be another publisher's gain, won't it?

An O'Reilly book was my first choice because of its reputation and its reach, so
it would have been a huge win for Apache Flex. And there are still the other
major publishers: Wrox, Wiley, Peachpit, Manning, Apress, all of which I plan to
pursue. The book idea isn't dead by a long shot, just the O'Reilly one.


_______________________________________________________________________

Joseph Balderson, Flex & Flash Platform Developer :: http://joeflash.ca
Author, Professional Flex 3 :: http://tinyurl.com/proflex3book

Alex Harui wrote:
> I stumbled on the fact today that the Apache Subversion project drafts its
> O'Reilly book as part of the project.  It is checked in to their
> repository, gets updated as needed, and then every once in a while,
> O'Reilly prints a bunch.
> 
> Could we/should we do the same?
> 
> On 1/24/14 1:48 PM, "Joseph Balderson" <ne...@joeflash.ca> wrote:
> 
>> Well, I just heard back from O'Reilly. And unfortunately they're not
>> interested
>> in publishing an Apache Flex book of any kind, because their official
>> position
>> is that "We're not interested in publishing titles that we feel don't
>> have a
>> significant market demand. Flex falls into this category."
>>
>> We know differently of course, but you can't blame O'Reilly for
>> responding to
>> market perception. I guess this book exemplifies somewhat of a
>> chicken-and-the-egg scenario: to some extent we need the book to show the
>> world
>> that Flex isn't dead (far from it), but we can't get one published (from
>> O'Reilly at least) until the perception is that it is very much alive.
>> Hopefully
>> other more progressive publishers will see things differently.
>>
>> I'm currently pursuing my contacts with other publishers. I'll let you
>> all know
>> how that works out.
>>
>> _______________________________________________________________________
>>
>> Joseph Balderson, Flex & Flash Platform Developer :: http://joeflash.ca
>> Author, Professional Flex 3 :: http://tinyurl.com/proflex3book
>>
>> Joseph Balderson wrote:
>>> Hi all,
>>>
>>> The latest news on the Apache Flex book with O'Reilly is that I'm
>>> currently in
>>> negotiations with them to have this book made, i.e. "Programming Apache
>>> Flex" as
>>> a continuance of that same series. It's taking some convincing to be
>>> honest,
>>> because the perception in the tech publishing industry right now is
>>> that Flash
>>> and Flex books are a lost leader, and more or less a dead ecosystem.
>>>
>>> In response I mentioned to them that since Flex is now truly open
>>> source under
>>> Apache, that O'Reilly would be seen to be promoting open source
>>> software, which
>>> is very much within their mandate. And that, of course, Flex is not
>>> dead; in
>>> fact it has every indication of making somewhat of a comeback,
>>> according to the
>>> "word on the street," evidenced by a slow trickle of client work back
>>> to Flex,
>>> supported by AIR winning an award at the 2013 CES for "Best Consumer
>>> Application
>>> Development Platform for Mobile" (1,2)
>>>
>>> However, I may be able to convince O'Reilly to go ahead with a
>>> digital-only
>>> version which would minimize their costs. And if they agree to this, I
>>> have
>>> offered to waive any fees or royalties associated with the book on my
>>> part, to
>>> be considered "my donation" to the Apache Flex community. If O'Reilly
>>> breaks
>>> even or even makes a slight profit (and the profit margins on tech
>>> books are
>>> insanely low), then the project will stand a chance of going forward,
>>> and
>>> waiving my fees might just be what tips the balance. And of course I
>>> mentioned
>>> that, wouldn't it be embarrassing when Flex springs back in this next
>>> year and
>>> there are no Flex books with the O'Reilly name on it? ;)
>>>
>>> We'll see what happens, if O'Reilly accepts my proposal. I understand
>>> how
>>> perception is in part largely responsible for driving sales of tech
>>> books. But
>>> stakeholders and students are not the only ones who can drive book
>>> sales: a
>>> niche community of developers can also do so.
>>>
>>> And so I need your help, everyone in the Flex community. I'll need an
>>> experienced tech editor who is willing to help out with this, to donate
>>> their
>>> time to the project. And I will need everyone's help in promoting this
>>> book when
>>> it comes out, and to buy one, so that O'Reilly can justify the ROI to
>>> go ahead
>>> with the project.
>>>
>>> This book will be seen as a huge boon to Apache Flex, to prove to all
>>> the
>>> managers and stakeholders drinking the HTML5 koolaid, that Flex isn't
>>> dead, and
>>> it is very much alive and well.
>>>
>>> Thanks all in advance for your support,
>>>
>>> Joseph
>>>
>>>
>>> (1)
>>>
>>> http://www.beedigital.net/2014/01/09/air-wins-award-at-ces-for-the-best-m
>>> obile-application-product-in-2014/
>>> (2)
>>>
>>> http://www.compassintelligence.com/?q=press/compass-intelligence-announce
>>> s-winners-2014-mobility-awards-wireless-m2m-and-green-technology
>>>
>>>
> 
> 

Re: O'Reilly Apache Flex book help

[Alex Harui <ah...@adobe.com>]

I stumbled on the fact today that the Apache Subversion project drafts its
O'Reilly book as part of the project.  It is checked in to their
repository, gets updated as needed, and then every once in a while,
O'Reilly prints a bunch.

Could we/should we do the same?

On 1/24/14 1:48 PM, "Joseph Balderson" <ne...@joeflash.ca> wrote:

>Well, I just heard back from O'Reilly. And unfortunately they're not
>interested
>in publishing an Apache Flex book of any kind, because their official
>position
>is that "We're not interested in publishing titles that we feel don't
>have a
>significant market demand. Flex falls into this category."
>
>We know differently of course, but you can't blame O'Reilly for
>responding to
>market perception. I guess this book exemplifies somewhat of a
>chicken-and-the-egg scenario: to some extent we need the book to show the
>world
>that Flex isn't dead (far from it), but we can't get one published (from
>O'Reilly at least) until the perception is that it is very much alive.
>Hopefully
>other more progressive publishers will see things differently.
>
>I'm currently pursuing my contacts with other publishers. I'll let you
>all know
>how that works out.
>
>_______________________________________________________________________
>
>Joseph Balderson, Flex & Flash Platform Developer :: http://joeflash.ca
>Author, Professional Flex 3 :: http://tinyurl.com/proflex3book
>
>Joseph Balderson wrote:
>> Hi all,
>> 
>> The latest news on the Apache Flex book with O'Reilly is that I'm
>>currently in
>> negotiations with them to have this book made, i.e. "Programming Apache
>>Flex" as
>> a continuance of that same series. It's taking some convincing to be
>>honest,
>> because the perception in the tech publishing industry right now is
>>that Flash
>> and Flex books are a lost leader, and more or less a dead ecosystem.
>> 
>> In response I mentioned to them that since Flex is now truly open
>>source under
>> Apache, that O'Reilly would be seen to be promoting open source
>>software, which
>> is very much within their mandate. And that, of course, Flex is not
>>dead; in
>> fact it has every indication of making somewhat of a comeback,
>>according to the
>> "word on the street," evidenced by a slow trickle of client work back
>>to Flex,
>> supported by AIR winning an award at the 2013 CES for "Best Consumer
>>Application
>> Development Platform for Mobile" (1,2)
>> 
>> However, I may be able to convince O'Reilly to go ahead with a
>>digital-only
>> version which would minimize their costs. And if they agree to this, I
>>have
>> offered to waive any fees or royalties associated with the book on my
>>part, to
>> be considered "my donation" to the Apache Flex community. If O'Reilly
>>breaks
>> even or even makes a slight profit (and the profit margins on tech
>>books are
>> insanely low), then the project will stand a chance of going forward,
>>and
>> waiving my fees might just be what tips the balance. And of course I
>>mentioned
>> that, wouldn't it be embarrassing when Flex springs back in this next
>>year and
>> there are no Flex books with the O'Reilly name on it? ;)
>> 
>> We'll see what happens, if O'Reilly accepts my proposal. I understand
>>how
>> perception is in part largely responsible for driving sales of tech
>>books. But
>> stakeholders and students are not the only ones who can drive book
>>sales: a
>> niche community of developers can also do so.
>> 
>> And so I need your help, everyone in the Flex community. I'll need an
>> experienced tech editor who is willing to help out with this, to donate
>>their
>> time to the project. And I will need everyone's help in promoting this
>>book when
>> it comes out, and to buy one, so that O'Reilly can justify the ROI to
>>go ahead
>> with the project.
>> 
>> This book will be seen as a huge boon to Apache Flex, to prove to all
>>the
>> managers and stakeholders drinking the HTML5 koolaid, that Flex isn't
>>dead, and
>> it is very much alive and well.
>> 
>> Thanks all in advance for your support,
>> 
>> Joseph
>> 
>> 
>> (1)
>> 
>>http://www.beedigital.net/2014/01/09/air-wins-award-at-ces-for-the-best-m
>>obile-application-product-in-2014/
>> (2)
>> 
>>http://www.compassintelligence.com/?q=press/compass-intelligence-announce
>>s-winners-2014-mobility-awards-wireless-m2m-and-green-technology
>> 
>> 

Re: O'Reilly Apache Flex book help

[OmPrakash Muppirala <bi...@gmail.com>]

On Fri, Jan 24, 2014 at 1:48 PM, Joseph Balderson <ne...@joeflash.ca> wrote:

> Well, I just heard back from O'Reilly. And unfortunately they're not
> interested
> in publishing an Apache Flex book of any kind, because their official
> position
> is that "We're not interested in publishing titles that we feel don't have
> a
> significant market demand. Flex falls into this category."
>
> We know differently of course, but you can't blame O'Reilly for responding
> to
> market perception. I guess this book exemplifies somewhat of a
> chicken-and-the-egg scenario: to some extent we need the book to show the
> world
> that Flex isn't dead (far from it), but we can't get one published (from
> O'Reilly at least) until the perception is that it is very much alive.
> Hopefully
> other more progressive publishers will see things differently.
>
> I'm currently pursuing my contacts with other publishers. I'll let you all
> know
> how that works out.
>

Joe, thanks for being so dedicated to put out a book on Apache Flex!

For future reference, here are some stats about Apache Flex's popularity:

* Close to 1 Million page views (770K+ unique views) of the
flex.apache.orgwebsite in less than a year [1]
* More than 250K unique visitors in under a year [1]
* More than 32K unique installs of the Apache Flex SDK in the past 9 months
[breakdown available on demand]
* Apache Flex blog has been consistently featured in the top 5 most visited
blogs of the Apache Software Foundation [2]

These stats should be a good starting point to say that Flex is not dead.

Hope this helps.  Do let us know if you need more detailed stats, I can
hook you up with a read-only account of flex.apache.org's Google Analytics
account.

Thanks,
Om

[1] http://www.seethestats.com/site/flex.apache.org
[2] http://blogs.apache.org/


>
> _______________________________________________________________________
>
> Joseph Balderson, Flex & Flash Platform Developer :: http://joeflash.ca
> Author, Professional Flex 3 :: http://tinyurl.com/proflex3book
>
> Joseph Balderson wrote:
> > Hi all,
> >
> > The latest news on the Apache Flex book with O'Reilly is that I'm
> currently in
> > negotiations with them to have this book made, i.e. "Programming Apache
> Flex" as
> > a continuance of that same series. It's taking some convincing to be
> honest,
> > because the perception in the tech publishing industry right now is that
> Flash
> > and Flex books are a lost leader, and more or less a dead ecosystem.
> >
> > In response I mentioned to them that since Flex is now truly open source
> under
> > Apache, that O'Reilly would be seen to be promoting open source
> software, which
> > is very much within their mandate. And that, of course, Flex is not
> dead; in
> > fact it has every indication of making somewhat of a comeback, according
> to the
> > "word on the street," evidenced by a slow trickle of client work back to
> Flex,
> > supported by AIR winning an award at the 2013 CES for "Best Consumer
> Application
> > Development Platform for Mobile" (1,2)
> >
> > However, I may be able to convince O'Reilly to go ahead with a
> digital-only
> > version which would minimize their costs. And if they agree to this, I
> have
> > offered to waive any fees or royalties associated with the book on my
> part, to
> > be considered "my donation" to the Apache Flex community. If O'Reilly
> breaks
> > even or even makes a slight profit (and the profit margins on tech books
> are
> > insanely low), then the project will stand a chance of going forward, and
> > waiving my fees might just be what tips the balance. And of course I
> mentioned
> > that, wouldn't it be embarrassing when Flex springs back in this next
> year and
> > there are no Flex books with the O'Reilly name on it? ;)
> >
> > We'll see what happens, if O'Reilly accepts my proposal. I understand how
> > perception is in part largely responsible for driving sales of tech
> books. But
> > stakeholders and students are not the only ones who can drive book
> sales: a
> > niche community of developers can also do so.
> >
> > And so I need your help, everyone in the Flex community. I'll need an
> > experienced tech editor who is willing to help out with this, to donate
> their
> > time to the project. And I will need everyone's help in promoting this
> book when
> > it comes out, and to buy one, so that O'Reilly can justify the ROI to go
> ahead
> > with the project.
> >
> > This book will be seen as a huge boon to Apache Flex, to prove to all the
> > managers and stakeholders drinking the HTML5 koolaid, that Flex isn't
> dead, and
> > it is very much alive and well.
> >
> > Thanks all in advance for your support,
> >
> > Joseph
> >
> >
> > (1)
> >
> http://www.beedigital.net/2014/01/09/air-wins-award-at-ces-for-the-best-mobile-application-product-in-2014/
> > (2)
> >
> http://www.compassintelligence.com/?q=press/compass-intelligence-announces-winners-2014-mobility-awards-wireless-m2m-and-green-technology
> >
> >
>

Re: O'Reilly Apache Flex book help

[Joseph Balderson <ne...@joeflash.ca>]

Well, I just heard back from O'Reilly. And unfortunately they're not interested
in publishing an Apache Flex book of any kind, because their official position
is that "We're not interested in publishing titles that we feel don't have a
significant market demand. Flex falls into this category."

We know differently of course, but you can't blame O'Reilly for responding to
market perception. I guess this book exemplifies somewhat of a
chicken-and-the-egg scenario: to some extent we need the book to show the world
that Flex isn't dead (far from it), but we can't get one published (from
O'Reilly at least) until the perception is that it is very much alive. Hopefully
other more progressive publishers will see things differently.

I'm currently pursuing my contacts with other publishers. I'll let you all know
how that works out.

_______________________________________________________________________

Joseph Balderson, Flex & Flash Platform Developer :: http://joeflash.ca
Author, Professional Flex 3 :: http://tinyurl.com/proflex3book

Joseph Balderson wrote:
> Hi all,
> 
> The latest news on the Apache Flex book with O'Reilly is that I'm currently in
> negotiations with them to have this book made, i.e. "Programming Apache Flex" as
> a continuance of that same series. It's taking some convincing to be honest,
> because the perception in the tech publishing industry right now is that Flash
> and Flex books are a lost leader, and more or less a dead ecosystem.
> 
> In response I mentioned to them that since Flex is now truly open source under
> Apache, that O'Reilly would be seen to be promoting open source software, which
> is very much within their mandate. And that, of course, Flex is not dead; in
> fact it has every indication of making somewhat of a comeback, according to the
> "word on the street," evidenced by a slow trickle of client work back to Flex,
> supported by AIR winning an award at the 2013 CES for "Best Consumer Application
> Development Platform for Mobile" (1,2)
> 
> However, I may be able to convince O'Reilly to go ahead with a digital-only
> version which would minimize their costs. And if they agree to this, I have
> offered to waive any fees or royalties associated with the book on my part, to
> be considered "my donation" to the Apache Flex community. If O'Reilly breaks
> even or even makes a slight profit (and the profit margins on tech books are
> insanely low), then the project will stand a chance of going forward, and
> waiving my fees might just be what tips the balance. And of course I mentioned
> that, wouldn't it be embarrassing when Flex springs back in this next year and
> there are no Flex books with the O'Reilly name on it? ;)
> 
> We'll see what happens, if O'Reilly accepts my proposal. I understand how
> perception is in part largely responsible for driving sales of tech books. But
> stakeholders and students are not the only ones who can drive book sales: a
> niche community of developers can also do so.
> 
> And so I need your help, everyone in the Flex community. I'll need an
> experienced tech editor who is willing to help out with this, to donate their
> time to the project. And I will need everyone's help in promoting this book when
> it comes out, and to buy one, so that O'Reilly can justify the ROI to go ahead
> with the project.
> 
> This book will be seen as a huge boon to Apache Flex, to prove to all the
> managers and stakeholders drinking the HTML5 koolaid, that Flex isn't dead, and
> it is very much alive and well.
> 
> Thanks all in advance for your support,
> 
> Joseph
> 
> 
> (1)
> http://www.beedigital.net/2014/01/09/air-wins-award-at-ces-for-the-best-mobile-application-product-in-2014/
> (2)
> http://www.compassintelligence.com/?q=press/compass-intelligence-announces-winners-2014-mobility-awards-wireless-m2m-and-green-technology
> 
> 

Re: O'Reilly Apache Flex book help

[bobk544 <bo...@yahoo.com>]

Hello, yes i would very interested in a book on "Programming Apache Flex"
after seeing this youtube on how WebFilings is using FLEX:  
http://tv.adobe.com/watch/max-2011-develop/case-study-webfilings-a-cloudpowered-innovative-enterprise-application/
And I found out last week that WebFilings is using FLEX to generate our
agencies 10Ks, 10Qs & XBRL reports and I think if FLEX can handle this kind
of financial reporting on the WEB, it definitely has a lot of great
potential. 
I’m also hoping that FLEX might be able to evolve to the capability to
convert MXML to JS or even Objective-C, just based on what I’m seeing is
possible from this XMLVM initiative:
http://xmlvm.org/overview/




--
View this message in context: http://apache-flex-users.2333346.n4.nabble.com/O-Reilly-Apache-Flex-book-help-tp4539p4622.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.

Re: O'Reilly Apache Flex book help

[Sumudu Chinthaka <cs...@gmail.com>]

Great Work Guys, Ill definitely pre order a copy

thanks
Sumudu


On Thu, Jan 23, 2014 at 8:25 AM, Justin Mclean <ju...@classsoftware.com>wrote:

> Hi,
>
> > You'll do fine, Justin. As long as you're willing to put in the time to
> read and
> > double-read the entire book (usually as it's written chapter by chapter)
> OK I'm in - but that shouldn't stop other people from wanting to help out
> as well.
>
> Thanks,
> Justin

Re: O'Reilly Apache Flex book help

[Mathieu St-Gelais <ma...@gmail.com>]

Hi. As a software engineer with five years of Flex experience, and a "not
bad at all almost-reusable" Flex mobile software architecture (that I'll
show you guys someday), I'd be really happy to help in the tech review, or
any other way you see fit.

I'm trying to find some ways to promote Flex as I think it's still the only
true  multiplatform mobile solution. That book would truly be a good start
in this"quest".

Let me know if you think I can help.

Matt
On Jan 22, 2014 9:56 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:

> Hi,
>
> > You'll do fine, Justin. As long as you're willing to put in the time to
> read and
> > double-read the entire book (usually as it's written chapter by chapter)
> OK I'm in - but that shouldn't stop other people from wanting to help out
> as well.
>
> Thanks,
> Justin

Re: O'Reilly Apache Flex book help

[fl...@dfguy.us]

I would just like to comment that I have followed the flash platform closely for years and have always just enjoyed doing work with it. As it improved while I was getting my degree years ago and grew my professional experience I was always very happy and excited about it. I was just really digging into flex and combining it with serious enterprise applications in a massive company in a perfectly logical and appropriate way with all kinds of opportunity when all of this ridiculous flash madness was unleashed on everyone. I have continued to study the platform and follow things even after Adobe literally shot itself in the foot for whatever bizarre reasons it had. I'm very happy to see things continuing positively at Apache. Perhaps this is what needed to happen in order for the platform to work with enterprise given Adobes focus more on graphics and gaming given their target audience of creatives or whatever it is that is going on with them.

I wrote a personal project using Apache flex mobile and it works great! I was able to write a few simple pop we services and flex literally just eats json data and does what you want! It's great! If there was a way to just trick or force Adobe to support their own dang platform I wish I could do that lol!

David



-----Original Message-----
From: Peter Ent <pe...@adobe.com>
To: "users@flex.apache.org" <us...@flex.apache.org>
Sent: Thu, 23 Jan 2014 9:01 AM
Subject: Re: O'Reilly Apache Flex book help

To anyone who is interested in working on this project with Joseph: I
worked with him a few years ago on the WROX Press book, "Adobe Flex 3",
with a number of other authors. Joseph is a really good project leader and
helped guide me through the process and help me shape the chapters I wrote.

I think Flex is doing really well, especially given the number of
downloads it gets with each release. It is surprising that it gets panned
sometimes as being 'dead' or going away considering all of the activity.
The focus on the mobile platform is so strong at the moment so I hope that
is a major element in the book.

I don't have time to participate on the book project due to personal
commitments, but I think anyone who does participate will enjoy the
process.

Best,
Peter Ent
Adobe Systems

On 1/23/14 9:13 AM, "John Gardiner" <jw...@gmail.com> wrote:

>An Apache Flex book will be a great statement of intent for the future of
>the technology. I hope this can be realised.
>
>My own experience is that Apache Flex is being re-adopted in a number of
>significant domains, especially when used in conjunction with Adobe Air.
>However, as I am sure others here have experienced, the quantity of stale
>information on the web (broken links to blogs, wikis, examples, libraries,
>etc.) is incredibly frustrating and can be a massive time thief.
>
>Therefore, assuming an Apache Flex Cookbook in future, my personal
>suggestion would be to use the initial book to rationalise this and other
>information on the wiki. Walkthrough examples of how to Mavenise an SDK
>and
>configure builds using the latest versions of Flexmojos and Flexunit (the
>other projects donated to Apache) would also be really powerful.
>
>I offer my services towards this project in any capacity and will
>certainly
>pre-order if this is helpful to the cause.
>
>Keep up the great work everyone.
>
>
>On 23 January 2014 08:38, Arne Broedel <ar...@googlemail.com>
>wrote:
>
>> Great I love to read this thread and feel the engagement. I would want a
>> copy just because this community drives it.
>> Am 23.01.2014 09:07 schrieb "Patel Amit" <am...@gmail.com>:
>>
>> > Here what I want to into the wishlist as following ::
>> >
>> > -  Apache Flex new sdks and improvement on Adobe flex 4.6
>> > -  New Apache Flex components related to 4.10 sdks if any
>> > - Connect with different technologies [Java , Dot net ,PHP]
>> > - There should be some Mobile and Tablets demo
>> > - Also we can cover the Falcon
>> > - There should be also the demo to build the application using
>>Mustella
>> > framework
>> > - FlexUnit
>> > - some reference link related to Apache flex showcase
>> >
>> >
>> > Regards,
>> >
>> >
>> >
>> >
>> >
>> > On Thu, Jan 23, 2014 at 11:01 AM, Joseph Balderson <ne...@joeflash.ca>
>> > wrote:
>> >
>> > > Thanks for your contributions Thiago. Let's table wish list items
>>to a
>> > > separate
>> > > thread.
>> > >
>> > > 
>>_______________________________________________________________________
>> > >
>> > > Joseph Balderson, Flex & Flash Platform Developer ::
>> http://joeflash.ca
>> > > Author, Professional Flex 3 :: http://tinyurl.com/proflex3book
>> > >
>> > > a00s@a00s.com wrote:
>> > > > Hi
>> > > >
>> > > >     Wish list, that I think it is important to those who want to
>> start.
>> > > > Just my opinion, things that took me long time to understand, that
>> > could
>> > > > be very simple and quickly if I could found in one place.
>> > > >
>> > > > 1) How to download Flex. Looks stupid but once you download and
>> install
>> > > > you start to wondering. OK now what I do? It was my first reaction
>> when
>> > > > moved to apache. It was my first time downloading separately from
>> Adobe
>> > > > builder.
>> > > > 2) How to setup Flex with adobe builder
>> > > > 3) How to setup Flex with Intelij
>> > > > 4) Probably the most important in my view: How to connect a flex
>> > > > application with a database (maybe how to setup tomcat, blazeds)
>> > > > 5) How to use external resourses with Flex like javascript. To
>>show
>> > that
>> > > > Flex its not a competitor of other languages but a language to
>>build
>> > the
>> > > > entire application, doesnt matter if will need to put together
>> > > > javascript, applet...
>> > > > 6) Show how to make 3d objects, not sure if the 3rd solution will
>> allow
>> > > > this one.
>> > > > 7) How to print. Any business application will need that at some
>> point,
>> > > > and many times we need a clear text to print, not a postscript
>>image,
>> > > > maybe how to convert in PDF.
>> > > > 8) How to check why your application is crashing the browser and
>>how
>> to
>> > > > debug.
>> > > >
>> > > > thanks for starting this book
>> > > >
>> > > > Thiago Maia
>> > > >
>> > > >
>> > > > On 1/22/2014 7:59 PM, Joseph Balderson wrote:
>> > > >> Thanks Justin.
>> > > >>
>> > > >> One rule of thumb for time involved is 1-2 hours per page for
>> authors
>> > > >> -- that's
>> > > >> me -- and 5-10 minutes per page for tech editing -- that's you
>> Justin.
>> > > >> Which is
>> > > >> why, if a book goes past 400 pages, you need more than one
>>author,
>> > > >> unless you're
>> > > >> David Gassner who can crack off a 1000-page Flex Bible book all
>>by
>> > > >> himself (god
>> > > >> only knows how the hell he does it). Given the scope of the book,
>> I'm
>> > > >> probably
>> > > >> looking at 6 months to write, with tech editing as it's written,
>>so
>> > > >> there's
>> > > >> time. Professional Adobe Flex 3 only had two tech editors, and
>>that
>> > was
>> > > a
>> > > >> 1400-page book (in retrospect we probably should have had three,
>>but
>> > > >> whaddyagonnado?) If you find you need help with the tech editing
>> > > >> Justin, we'll
>> > > >> cross that bridge when we get to it, but for now consider that
>>post
>> to
>> > > >> be filled
>> > > >> by you.
>> > > >>
>> > > >> There are three possible classic "animal" books I could do with
>> > > >> O'Reilly for
>> > > >> Apache Flex -- one is the "Programming Foo" series, the other is
>>the
>> > > "Foo
>> > > >> Cookbook" series, and the third are "Developing Fum Applications
>>for
>> > > Foo"
>> > > >> micro-books. The last book on Flex in the "Programming" series
>>was
>> > > >> "Programming
>> > > >> Flex 3" by Chafic Kazoun & Joey Lott, so we're due for an update.
>> > > >> There is a
>> > > >> "Flex 4 Cookbook" and some Flex 4.5 micro-books by Rich Tretola
>>back
>> > > >> in 2011,
>> > > >> but nothing recent.
>> > > >>
>> > > >> I think we'll go with a "Programming Apache Flex" book this time,
>> with
>> > > an
>> > > >> emphasis on the Spark portion of the framework, and what's been
>> > > >> updated since
>> > > >> Adobe Flex 4.6, rather than going over everything, considering
>>the
>> > > >> wealth of
>> > > >> information already published on Flex 3 and 4. And also because I
>> > > >> don't want to
>> > > >> embark on another monster book project; we'll keep it at around
>>400
>> > > >> pages, which
>> > > >> would be easier to sell to O'Reilly.
>> > > >>
>> > > >> Doing an "Apache Flex Cookbook" would be a nice second book, but
>>as
>> a
>> > > >> collaborative effort, because it would be a bit of a monster to
>>do,
>> > > >> considering
>> > > >> that the "Flex 4 Cookbook" weighed in at 740 pages. If O'Reilly
>> gets a
>> > > >> good ROI
>> > > >> (i.e. it breaks even ;) on this first book, they might consider
>> doing
>> > > the
>> > > >> cookbook. But we'll cross that bridge when we get to it.
>> > > >>
>> > > >> What I will need people's input on, when the book proposal is
>> > > >> approved, are
>> > > >> general ideas, or rather a wish list of "what you'd like to see
>>in
>> the
>> > > >> book",
>> > > >> keeping in mind what kind of book this will be.
>> > > >>
>> > > >>
>> > > >> I'll keep everyone updated as I hear from them.
>> > > >>
>> > > >>
>> > 
>>_______________________________________________________________________
>> > > >>
>> > > >> Joseph Balderson, Flex & Flash Platform Developer ::
>> > http://joeflash.ca
>> > > >> Author, Professional Flex 3 :: http://tinyurl.com/proflex3book
>> > > >>
>> > > >> Justin Mclean wrote:
>> > > >>> Hi,
>> > > >>>
>> > > >>>> You'll do fine, Justin. As long as you're willing to put in the
>> time
>> > > >>>> to read and
>> > > >>>> double-read the entire book (usually as it's written chapter by
>> > > >>>> chapter)
>> > > >>> OK I'm in - but that shouldn't stop other people from wanting to
>> help
>> > > >>> out as well.
>> > > >>>
>> > > >>> Thanks,
>> > > >>> Justin
>> > > >
>> > > >
>> > >
>> >
>>

Re: O'Reilly Apache Flex book help

[Diogo Vieira <di...@gmail.com>]

Excelent news....

+1 for pre order!!!

Att,
Diogo.



2014/1/24 Joseph Balderson <ne...@joeflash.ca>

> Thanks for the testimonial, Peter. It was a great pleasure working with
> you and
> the others on the Wrox book back in '09.
>
> I'm not looking for writing partners on the upcoming Flex book at the
> moment,
> but we'll see how it goes. I did need a tech editor, but the position has
> been
> filled by Justin Mclean.
>
> Do keep posting your suggestions to the "Apache Flex Book Topic Wish List"
> thread though, that would be appreciated. See start of the thread for
> details.
>
> I'll keep everyone updated when I hear back from O'Reilly.
>
> _______________________________________________________________________
>
> Joseph Balderson, Flex & Flash Platform Developer :: http://joeflash.ca
> Author, Professional Flex 3 :: http://tinyurl.com/proflex3book
>
> Peter Ent wrote:
> > To anyone who is interested in working on this project with Joseph: I
> > worked with him a few years ago on the WROX Press book, "Adobe Flex 3",
> > with a number of other authors. Joseph is a really good project leader
> and
> > helped guide me through the process and help me shape the chapters I
> wrote.
> >
> > I think Flex is doing really well, especially given the number of
> > downloads it gets with each release. It is surprising that it gets panned
> > sometimes as being 'dead' or going away considering all of the activity.
> > The focus on the mobile platform is so strong at the moment so I hope
> that
> > is a major element in the book.
> >
> > I don't have time to participate on the book project due to personal
> > commitments, but I think anyone who does participate will enjoy the
> > process.
> >
> > Best,
> > Peter Ent
> > Adobe Systems
> >
> > On 1/23/14 9:13 AM, "John Gardiner" <jw...@gmail.com> wrote:
> >
> >> An Apache Flex book will be a great statement of intent for the future
> of
> >> the technology. I hope this can be realised.
> >>
> >> My own experience is that Apache Flex is being re-adopted in a number of
> >> significant domains, especially when used in conjunction with Adobe Air.
> >> However, as I am sure others here have experienced, the quantity of
> stale
> >> information on the web (broken links to blogs, wikis, examples,
> libraries,
> >> etc.) is incredibly frustrating and can be a massive time thief.
> >>
> >> Therefore, assuming an Apache Flex Cookbook in future, my personal
> >> suggestion would be to use the initial book to rationalise this and
> other
> >> information on the wiki. Walkthrough examples of how to Mavenise an SDK
> >> and
> >> configure builds using the latest versions of Flexmojos and Flexunit
> (the
> >> other projects donated to Apache) would also be really powerful.
> >>
> >> I offer my services towards this project in any capacity and will
> >> certainly
> >> pre-order if this is helpful to the cause.
> >>
> >> Keep up the great work everyone.
> >>
> >>
> >> On 23 January 2014 08:38, Arne Broedel <ar...@googlemail.com>
> >> wrote:
> >>
> >>> Great I love to read this thread and feel the engagement. I would want
> a
> >>> copy just because this community drives it.
> >>> Am 23.01.2014 09:07 schrieb "Patel Amit" <am...@gmail.com>:
> >>>
> >>>> Here what I want to into the wishlist as following ::
> >>>>
> >>>> -  Apache Flex new sdks and improvement on Adobe flex 4.6
> >>>> -  New Apache Flex components related to 4.10 sdks if any
> >>>> - Connect with different technologies [Java , Dot net ,PHP]
> >>>> - There should be some Mobile and Tablets demo
> >>>> - Also we can cover the Falcon
> >>>> - There should be also the demo to build the application using
> >>> Mustella
> >>>> framework
> >>>> - FlexUnit
> >>>> - some reference link related to Apache flex showcase
> >>>>
> >>>>
> >>>> Regards,
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> On Thu, Jan 23, 2014 at 11:01 AM, Joseph Balderson <ne...@joeflash.ca>
> >>>> wrote:
> >>>>
> >>>>> Thanks for your contributions Thiago. Let's table wish list items
> >>> to a
> >>>>> separate
> >>>>> thread.
> >>>>>
> >>>>>
> >>> _______________________________________________________________________
> >>>>> Joseph Balderson, Flex & Flash Platform Developer ::
> >>> http://joeflash.ca
> >>>>> Author, Professional Flex 3 :: http://tinyurl.com/proflex3book
> >>>>>
> >>>>> a00s@a00s.com wrote:
> >>>>>> Hi
> >>>>>>
> >>>>>>     Wish list, that I think it is important to those who want to
> >>> start.
> >>>>>> Just my opinion, things that took me long time to understand, that
> >>>> could
> >>>>>> be very simple and quickly if I could found in one place.
> >>>>>>
> >>>>>> 1) How to download Flex. Looks stupid but once you download and
> >>> install
> >>>>>> you start to wondering. OK now what I do? It was my first reaction
> >>> when
> >>>>>> moved to apache. It was my first time downloading separately from
> >>> Adobe
> >>>>>> builder.
> >>>>>> 2) How to setup Flex with adobe builder
> >>>>>> 3) How to setup Flex with Intelij
> >>>>>> 4) Probably the most important in my view: How to connect a flex
> >>>>>> application with a database (maybe how to setup tomcat, blazeds)
> >>>>>> 5) How to use external resourses with Flex like javascript. To
> >>> show
> >>>> that
> >>>>>> Flex its not a competitor of other languages but a language to
> >>> build
> >>>> the
> >>>>>> entire application, doesnt matter if will need to put together
> >>>>>> javascript, applet...
> >>>>>> 6) Show how to make 3d objects, not sure if the 3rd solution will
> >>> allow
> >>>>>> this one.
> >>>>>> 7) How to print. Any business application will need that at some
> >>> point,
> >>>>>> and many times we need a clear text to print, not a postscript
> >>> image,
> >>>>>> maybe how to convert in PDF.
> >>>>>> 8) How to check why your application is crashing the browser and
> >>> how
> >>> to
> >>>>>> debug.
> >>>>>>
> >>>>>> thanks for starting this book
> >>>>>>
> >>>>>> Thiago Maia
> >>>>>>
> >>>>>>
> >>>>>> On 1/22/2014 7:59 PM, Joseph Balderson wrote:
> >>>>>>> Thanks Justin.
> >>>>>>>
> >>>>>>> One rule of thumb for time involved is 1-2 hours per page for
> >>> authors
> >>>>>>> -- that's
> >>>>>>> me -- and 5-10 minutes per page for tech editing -- that's you
> >>> Justin.
> >>>>>>> Which is
> >>>>>>> why, if a book goes past 400 pages, you need more than one
> >>> author,
> >>>>>>> unless you're
> >>>>>>> David Gassner who can crack off a 1000-page Flex Bible book all
> >>> by
> >>>>>>> himself (god
> >>>>>>> only knows how the hell he does it). Given the scope of the book,
> >>> I'm
> >>>>>>> probably
> >>>>>>> looking at 6 months to write, with tech editing as it's written,
> >>> so
> >>>>>>> there's
> >>>>>>> time. Professional Adobe Flex 3 only had two tech editors, and
> >>> that
> >>>> was
> >>>>> a
> >>>>>>> 1400-page book (in retrospect we probably should have had three,
> >>> but
> >>>>>>> whaddyagonnado?) If you find you need help with the tech editing
> >>>>>>> Justin, we'll
> >>>>>>> cross that bridge when we get to it, but for now consider that
> >>> post
> >>> to
> >>>>>>> be filled
> >>>>>>> by you.
> >>>>>>>
> >>>>>>> There are three possible classic "animal" books I could do with
> >>>>>>> O'Reilly for
> >>>>>>> Apache Flex -- one is the "Programming Foo" series, the other is
> >>> the
> >>>>> "Foo
> >>>>>>> Cookbook" series, and the third are "Developing Fum Applications
> >>> for
> >>>>> Foo"
> >>>>>>> micro-books. The last book on Flex in the "Programming" series
> >>> was
> >>>>>>> "Programming
> >>>>>>> Flex 3" by Chafic Kazoun & Joey Lott, so we're due for an update.
> >>>>>>> There is a
> >>>>>>> "Flex 4 Cookbook" and some Flex 4.5 micro-books by Rich Tretola
> >>> back
> >>>>>>> in 2011,
> >>>>>>> but nothing recent.
> >>>>>>>
> >>>>>>> I think we'll go with a "Programming Apache Flex" book this time,
> >>> with
> >>>>> an
> >>>>>>> emphasis on the Spark portion of the framework, and what's been
> >>>>>>> updated since
> >>>>>>> Adobe Flex 4.6, rather than going over everything, considering
> >>> the
> >>>>>>> wealth of
> >>>>>>> information already published on Flex 3 and 4. And also because I
> >>>>>>> don't want to
> >>>>>>> embark on another monster book project; we'll keep it at around
> >>> 400
> >>>>>>> pages, which
> >>>>>>> would be easier to sell to O'Reilly.
> >>>>>>>
> >>>>>>> Doing an "Apache Flex Cookbook" would be a nice second book, but
> >>> as
> >>> a
> >>>>>>> collaborative effort, because it would be a bit of a monster to
> >>> do,
> >>>>>>> considering
> >>>>>>> that the "Flex 4 Cookbook" weighed in at 740 pages. If O'Reilly
> >>> gets a
> >>>>>>> good ROI
> >>>>>>> (i.e. it breaks even ;) on this first book, they might consider
> >>> doing
> >>>>> the
> >>>>>>> cookbook. But we'll cross that bridge when we get to it.
> >>>>>>>
> >>>>>>> What I will need people's input on, when the book proposal is
> >>>>>>> approved, are
> >>>>>>> general ideas, or rather a wish list of "what you'd like to see
> >>> in
> >>> the
> >>>>>>> book",
> >>>>>>> keeping in mind what kind of book this will be.
> >>>>>>>
> >>>>>>>
> >>>>>>> I'll keep everyone updated as I hear from them.
> >>>>>>>
> >>>>>>>
> >>> _______________________________________________________________________
> >>>>>>> Joseph Balderson, Flex & Flash Platform Developer ::
> >>>> http://joeflash.ca
> >>>>>>> Author, Professional Flex 3 :: http://tinyurl.com/proflex3book
> >>>>>>>
> >>>>>>> Justin Mclean wrote:
> >>>>>>>> Hi,
> >>>>>>>>
> >>>>>>>>> You'll do fine, Justin. As long as you're willing to put in the
> >>> time
> >>>>>>>>> to read and
> >>>>>>>>> double-read the entire book (usually as it's written chapter by
> >>>>>>>>> chapter)
> >>>>>>>> OK I'm in - but that shouldn't stop other people from wanting to
> >>> help
> >>>>>>>> out as well.
> >>>>>>>>
> >>>>>>>> Thanks,
> >>>>>>>> Justin
> >>>>>>
> >
> >
>

Re: O'Reilly Apache Flex book help

[Joseph Balderson <ne...@joeflash.ca>]

Thanks for the testimonial, Peter. It was a great pleasure working with you and
the others on the Wrox book back in '09.

I'm not looking for writing partners on the upcoming Flex book at the moment,
but we'll see how it goes. I did need a tech editor, but the position has been
filled by Justin Mclean.

Do keep posting your suggestions to the "Apache Flex Book Topic Wish List"
thread though, that would be appreciated. See start of the thread for details.

I'll keep everyone updated when I hear back from O'Reilly.

_______________________________________________________________________

Joseph Balderson, Flex & Flash Platform Developer :: http://joeflash.ca
Author, Professional Flex 3 :: http://tinyurl.com/proflex3book

Peter Ent wrote:
> To anyone who is interested in working on this project with Joseph: I
> worked with him a few years ago on the WROX Press book, "Adobe Flex 3",
> with a number of other authors. Joseph is a really good project leader and
> helped guide me through the process and help me shape the chapters I wrote.
> 
> I think Flex is doing really well, especially given the number of
> downloads it gets with each release. It is surprising that it gets panned
> sometimes as being 'dead' or going away considering all of the activity.
> The focus on the mobile platform is so strong at the moment so I hope that
> is a major element in the book.
> 
> I don't have time to participate on the book project due to personal
> commitments, but I think anyone who does participate will enjoy the
> process.
> 
> Best,
> Peter Ent
> Adobe Systems
> 
> On 1/23/14 9:13 AM, "John Gardiner" <jw...@gmail.com> wrote:
> 
>> An Apache Flex book will be a great statement of intent for the future of
>> the technology. I hope this can be realised.
>>
>> My own experience is that Apache Flex is being re-adopted in a number of
>> significant domains, especially when used in conjunction with Adobe Air.
>> However, as I am sure others here have experienced, the quantity of stale
>> information on the web (broken links to blogs, wikis, examples, libraries,
>> etc.) is incredibly frustrating and can be a massive time thief.
>>
>> Therefore, assuming an Apache Flex Cookbook in future, my personal
>> suggestion would be to use the initial book to rationalise this and other
>> information on the wiki. Walkthrough examples of how to Mavenise an SDK
>> and
>> configure builds using the latest versions of Flexmojos and Flexunit (the
>> other projects donated to Apache) would also be really powerful.
>>
>> I offer my services towards this project in any capacity and will
>> certainly
>> pre-order if this is helpful to the cause.
>>
>> Keep up the great work everyone.
>>
>>
>> On 23 January 2014 08:38, Arne Broedel <ar...@googlemail.com>
>> wrote:
>>
>>> Great I love to read this thread and feel the engagement. I would want a
>>> copy just because this community drives it.
>>> Am 23.01.2014 09:07 schrieb "Patel Amit" <am...@gmail.com>:
>>>
>>>> Here what I want to into the wishlist as following ::
>>>>
>>>> -  Apache Flex new sdks and improvement on Adobe flex 4.6
>>>> -  New Apache Flex components related to 4.10 sdks if any
>>>> - Connect with different technologies [Java , Dot net ,PHP]
>>>> - There should be some Mobile and Tablets demo
>>>> - Also we can cover the Falcon
>>>> - There should be also the demo to build the application using
>>> Mustella
>>>> framework
>>>> - FlexUnit
>>>> - some reference link related to Apache flex showcase
>>>>
>>>>
>>>> Regards,
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Thu, Jan 23, 2014 at 11:01 AM, Joseph Balderson <ne...@joeflash.ca>
>>>> wrote:
>>>>
>>>>> Thanks for your contributions Thiago. Let's table wish list items
>>> to a
>>>>> separate
>>>>> thread.
>>>>>
>>>>>
>>> _______________________________________________________________________
>>>>> Joseph Balderson, Flex & Flash Platform Developer ::
>>> http://joeflash.ca
>>>>> Author, Professional Flex 3 :: http://tinyurl.com/proflex3book
>>>>>
>>>>> a00s@a00s.com wrote:
>>>>>> Hi
>>>>>>
>>>>>>     Wish list, that I think it is important to those who want to
>>> start.
>>>>>> Just my opinion, things that took me long time to understand, that
>>>> could
>>>>>> be very simple and quickly if I could found in one place.
>>>>>>
>>>>>> 1) How to download Flex. Looks stupid but once you download and
>>> install
>>>>>> you start to wondering. OK now what I do? It was my first reaction
>>> when
>>>>>> moved to apache. It was my first time downloading separately from
>>> Adobe
>>>>>> builder.
>>>>>> 2) How to setup Flex with adobe builder
>>>>>> 3) How to setup Flex with Intelij
>>>>>> 4) Probably the most important in my view: How to connect a flex
>>>>>> application with a database (maybe how to setup tomcat, blazeds)
>>>>>> 5) How to use external resourses with Flex like javascript. To
>>> show
>>>> that
>>>>>> Flex its not a competitor of other languages but a language to
>>> build
>>>> the
>>>>>> entire application, doesnt matter if will need to put together
>>>>>> javascript, applet...
>>>>>> 6) Show how to make 3d objects, not sure if the 3rd solution will
>>> allow
>>>>>> this one.
>>>>>> 7) How to print. Any business application will need that at some
>>> point,
>>>>>> and many times we need a clear text to print, not a postscript
>>> image,
>>>>>> maybe how to convert in PDF.
>>>>>> 8) How to check why your application is crashing the browser and
>>> how
>>> to
>>>>>> debug.
>>>>>>
>>>>>> thanks for starting this book
>>>>>>
>>>>>> Thiago Maia
>>>>>>
>>>>>>
>>>>>> On 1/22/2014 7:59 PM, Joseph Balderson wrote:
>>>>>>> Thanks Justin.
>>>>>>>
>>>>>>> One rule of thumb for time involved is 1-2 hours per page for
>>> authors
>>>>>>> -- that's
>>>>>>> me -- and 5-10 minutes per page for tech editing -- that's you
>>> Justin.
>>>>>>> Which is
>>>>>>> why, if a book goes past 400 pages, you need more than one
>>> author,
>>>>>>> unless you're
>>>>>>> David Gassner who can crack off a 1000-page Flex Bible book all
>>> by
>>>>>>> himself (god
>>>>>>> only knows how the hell he does it). Given the scope of the book,
>>> I'm
>>>>>>> probably
>>>>>>> looking at 6 months to write, with tech editing as it's written,
>>> so
>>>>>>> there's
>>>>>>> time. Professional Adobe Flex 3 only had two tech editors, and
>>> that
>>>> was
>>>>> a
>>>>>>> 1400-page book (in retrospect we probably should have had three,
>>> but
>>>>>>> whaddyagonnado?) If you find you need help with the tech editing
>>>>>>> Justin, we'll
>>>>>>> cross that bridge when we get to it, but for now consider that
>>> post
>>> to
>>>>>>> be filled
>>>>>>> by you.
>>>>>>>
>>>>>>> There are three possible classic "animal" books I could do with
>>>>>>> O'Reilly for
>>>>>>> Apache Flex -- one is the "Programming Foo" series, the other is
>>> the
>>>>> "Foo
>>>>>>> Cookbook" series, and the third are "Developing Fum Applications
>>> for
>>>>> Foo"
>>>>>>> micro-books. The last book on Flex in the "Programming" series
>>> was
>>>>>>> "Programming
>>>>>>> Flex 3" by Chafic Kazoun & Joey Lott, so we're due for an update.
>>>>>>> There is a
>>>>>>> "Flex 4 Cookbook" and some Flex 4.5 micro-books by Rich Tretola
>>> back
>>>>>>> in 2011,
>>>>>>> but nothing recent.
>>>>>>>
>>>>>>> I think we'll go with a "Programming Apache Flex" book this time,
>>> with
>>>>> an
>>>>>>> emphasis on the Spark portion of the framework, and what's been
>>>>>>> updated since
>>>>>>> Adobe Flex 4.6, rather than going over everything, considering
>>> the
>>>>>>> wealth of
>>>>>>> information already published on Flex 3 and 4. And also because I
>>>>>>> don't want to
>>>>>>> embark on another monster book project; we'll keep it at around
>>> 400
>>>>>>> pages, which
>>>>>>> would be easier to sell to O'Reilly.
>>>>>>>
>>>>>>> Doing an "Apache Flex Cookbook" would be a nice second book, but
>>> as
>>> a
>>>>>>> collaborative effort, because it would be a bit of a monster to
>>> do,
>>>>>>> considering
>>>>>>> that the "Flex 4 Cookbook" weighed in at 740 pages. If O'Reilly
>>> gets a
>>>>>>> good ROI
>>>>>>> (i.e. it breaks even ;) on this first book, they might consider
>>> doing
>>>>> the
>>>>>>> cookbook. But we'll cross that bridge when we get to it.
>>>>>>>
>>>>>>> What I will need people's input on, when the book proposal is
>>>>>>> approved, are
>>>>>>> general ideas, or rather a wish list of "what you'd like to see
>>> in
>>> the
>>>>>>> book",
>>>>>>> keeping in mind what kind of book this will be.
>>>>>>>
>>>>>>>
>>>>>>> I'll keep everyone updated as I hear from them.
>>>>>>>
>>>>>>>
>>> _______________________________________________________________________
>>>>>>> Joseph Balderson, Flex & Flash Platform Developer ::
>>>> http://joeflash.ca
>>>>>>> Author, Professional Flex 3 :: http://tinyurl.com/proflex3book
>>>>>>>
>>>>>>> Justin Mclean wrote:
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>>> You'll do fine, Justin. As long as you're willing to put in the
>>> time
>>>>>>>>> to read and
>>>>>>>>> double-read the entire book (usually as it's written chapter by
>>>>>>>>> chapter)
>>>>>>>> OK I'm in - but that shouldn't stop other people from wanting to
>>> help
>>>>>>>> out as well.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Justin
>>>>>>
> 
> 

Re: O'Reilly Apache Flex book help

[Peter Ent <pe...@adobe.com>]

To anyone who is interested in working on this project with Joseph: I
worked with him a few years ago on the WROX Press book, "Adobe Flex 3",
with a number of other authors. Joseph is a really good project leader and
helped guide me through the process and help me shape the chapters I wrote.

I think Flex is doing really well, especially given the number of
downloads it gets with each release. It is surprising that it gets panned
sometimes as being 'dead' or going away considering all of the activity.
The focus on the mobile platform is so strong at the moment so I hope that
is a major element in the book.

I don't have time to participate on the book project due to personal
commitments, but I think anyone who does participate will enjoy the
process.

Best,
Peter Ent
Adobe Systems

On 1/23/14 9:13 AM, "John Gardiner" <jw...@gmail.com> wrote:

>An Apache Flex book will be a great statement of intent for the future of
>the technology. I hope this can be realised.
>
>My own experience is that Apache Flex is being re-adopted in a number of
>significant domains, especially when used in conjunction with Adobe Air.
>However, as I am sure others here have experienced, the quantity of stale
>information on the web (broken links to blogs, wikis, examples, libraries,
>etc.) is incredibly frustrating and can be a massive time thief.
>
>Therefore, assuming an Apache Flex Cookbook in future, my personal
>suggestion would be to use the initial book to rationalise this and other
>information on the wiki. Walkthrough examples of how to Mavenise an SDK
>and
>configure builds using the latest versions of Flexmojos and Flexunit (the
>other projects donated to Apache) would also be really powerful.
>
>I offer my services towards this project in any capacity and will
>certainly
>pre-order if this is helpful to the cause.
>
>Keep up the great work everyone.
>
>
>On 23 January 2014 08:38, Arne Broedel <ar...@googlemail.com>
>wrote:
>
>> Great I love to read this thread and feel the engagement. I would want a
>> copy just because this community drives it.
>> Am 23.01.2014 09:07 schrieb "Patel Amit" <am...@gmail.com>:
>>
>> > Here what I want to into the wishlist as following ::
>> >
>> > -  Apache Flex new sdks and improvement on Adobe flex 4.6
>> > -  New Apache Flex components related to 4.10 sdks if any
>> > - Connect with different technologies [Java , Dot net ,PHP]
>> > - There should be some Mobile and Tablets demo
>> > - Also we can cover the Falcon
>> > - There should be also the demo to build the application using
>>Mustella
>> > framework
>> > - FlexUnit
>> > - some reference link related to Apache flex showcase
>> >
>> >
>> > Regards,
>> >
>> >
>> >
>> >
>> >
>> > On Thu, Jan 23, 2014 at 11:01 AM, Joseph Balderson <ne...@joeflash.ca>
>> > wrote:
>> >
>> > > Thanks for your contributions Thiago. Let's table wish list items
>>to a
>> > > separate
>> > > thread.
>> > >
>> > > 
>>_______________________________________________________________________
>> > >
>> > > Joseph Balderson, Flex & Flash Platform Developer ::
>> http://joeflash.ca
>> > > Author, Professional Flex 3 :: http://tinyurl.com/proflex3book
>> > >
>> > > a00s@a00s.com wrote:
>> > > > Hi
>> > > >
>> > > >     Wish list, that I think it is important to those who want to
>> start.
>> > > > Just my opinion, things that took me long time to understand, that
>> > could
>> > > > be very simple and quickly if I could found in one place.
>> > > >
>> > > > 1) How to download Flex. Looks stupid but once you download and
>> install
>> > > > you start to wondering. OK now what I do? It was my first reaction
>> when
>> > > > moved to apache. It was my first time downloading separately from
>> Adobe
>> > > > builder.
>> > > > 2) How to setup Flex with adobe builder
>> > > > 3) How to setup Flex with Intelij
>> > > > 4) Probably the most important in my view: How to connect a flex
>> > > > application with a database (maybe how to setup tomcat, blazeds)
>> > > > 5) How to use external resourses with Flex like javascript. To
>>show
>> > that
>> > > > Flex its not a competitor of other languages but a language to
>>build
>> > the
>> > > > entire application, doesnt matter if will need to put together
>> > > > javascript, applet...
>> > > > 6) Show how to make 3d objects, not sure if the 3rd solution will
>> allow
>> > > > this one.
>> > > > 7) How to print. Any business application will need that at some
>> point,
>> > > > and many times we need a clear text to print, not a postscript
>>image,
>> > > > maybe how to convert in PDF.
>> > > > 8) How to check why your application is crashing the browser and
>>how
>> to
>> > > > debug.
>> > > >
>> > > > thanks for starting this book
>> > > >
>> > > > Thiago Maia
>> > > >
>> > > >
>> > > > On 1/22/2014 7:59 PM, Joseph Balderson wrote:
>> > > >> Thanks Justin.
>> > > >>
>> > > >> One rule of thumb for time involved is 1-2 hours per page for
>> authors
>> > > >> -- that's
>> > > >> me -- and 5-10 minutes per page for tech editing -- that's you
>> Justin.
>> > > >> Which is
>> > > >> why, if a book goes past 400 pages, you need more than one
>>author,
>> > > >> unless you're
>> > > >> David Gassner who can crack off a 1000-page Flex Bible book all
>>by
>> > > >> himself (god
>> > > >> only knows how the hell he does it). Given the scope of the book,
>> I'm
>> > > >> probably
>> > > >> looking at 6 months to write, with tech editing as it's written,
>>so
>> > > >> there's
>> > > >> time. Professional Adobe Flex 3 only had two tech editors, and
>>that
>> > was
>> > > a
>> > > >> 1400-page book (in retrospect we probably should have had three,
>>but
>> > > >> whaddyagonnado?) If you find you need help with the tech editing
>> > > >> Justin, we'll
>> > > >> cross that bridge when we get to it, but for now consider that
>>post
>> to
>> > > >> be filled
>> > > >> by you.
>> > > >>
>> > > >> There are three possible classic "animal" books I could do with
>> > > >> O'Reilly for
>> > > >> Apache Flex -- one is the "Programming Foo" series, the other is
>>the
>> > > "Foo
>> > > >> Cookbook" series, and the third are "Developing Fum Applications
>>for
>> > > Foo"
>> > > >> micro-books. The last book on Flex in the "Programming" series
>>was
>> > > >> "Programming
>> > > >> Flex 3" by Chafic Kazoun & Joey Lott, so we're due for an update.
>> > > >> There is a
>> > > >> "Flex 4 Cookbook" and some Flex 4.5 micro-books by Rich Tretola
>>back
>> > > >> in 2011,
>> > > >> but nothing recent.
>> > > >>
>> > > >> I think we'll go with a "Programming Apache Flex" book this time,
>> with
>> > > an
>> > > >> emphasis on the Spark portion of the framework, and what's been
>> > > >> updated since
>> > > >> Adobe Flex 4.6, rather than going over everything, considering
>>the
>> > > >> wealth of
>> > > >> information already published on Flex 3 and 4. And also because I
>> > > >> don't want to
>> > > >> embark on another monster book project; we'll keep it at around
>>400
>> > > >> pages, which
>> > > >> would be easier to sell to O'Reilly.
>> > > >>
>> > > >> Doing an "Apache Flex Cookbook" would be a nice second book, but
>>as
>> a
>> > > >> collaborative effort, because it would be a bit of a monster to
>>do,
>> > > >> considering
>> > > >> that the "Flex 4 Cookbook" weighed in at 740 pages. If O'Reilly
>> gets a
>> > > >> good ROI
>> > > >> (i.e. it breaks even ;) on this first book, they might consider
>> doing
>> > > the
>> > > >> cookbook. But we'll cross that bridge when we get to it.
>> > > >>
>> > > >> What I will need people's input on, when the book proposal is
>> > > >> approved, are
>> > > >> general ideas, or rather a wish list of "what you'd like to see
>>in
>> the
>> > > >> book",
>> > > >> keeping in mind what kind of book this will be.
>> > > >>
>> > > >>
>> > > >> I'll keep everyone updated as I hear from them.
>> > > >>
>> > > >>
>> > 
>>_______________________________________________________________________
>> > > >>
>> > > >> Joseph Balderson, Flex & Flash Platform Developer ::
>> > http://joeflash.ca
>> > > >> Author, Professional Flex 3 :: http://tinyurl.com/proflex3book
>> > > >>
>> > > >> Justin Mclean wrote:
>> > > >>> Hi,
>> > > >>>
>> > > >>>> You'll do fine, Justin. As long as you're willing to put in the
>> time
>> > > >>>> to read and
>> > > >>>> double-read the entire book (usually as it's written chapter by
>> > > >>>> chapter)
>> > > >>> OK I'm in - but that shouldn't stop other people from wanting to
>> help
>> > > >>> out as well.
>> > > >>>
>> > > >>> Thanks,
>> > > >>> Justin
>> > > >
>> > > >
>> > >
>> >
>>

Re: O'Reilly Apache Flex book help

[Mathieu St-Gelais <ma...@gmail.com>]

Chris: that would be awesome!


On Thu, Jan 23, 2014 at 10:15 AM, Christofer Dutz <christofer.dutz@c-ware.de
> wrote:

> Guess I could definitely jump in to help with the Maven + Flexmojos part
> :-)
> Think this has never actually been covered by any printed book.
>
> Chris
> ________________________________________
> Von: John Gardiner <jw...@gmail.com>
> Gesendet: Donnerstag, 23. Januar 2014 15:13
> An: users@flex.apache.org
> Betreff: Re: O'Reilly Apache Flex book help
>
> An Apache Flex book will be a great statement of intent for the future of
> the technology. I hope this can be realised.
>
> My own experience is that Apache Flex is being re-adopted in a number of
> significant domains, especially when used in conjunction with Adobe Air.
> However, as I am sure others here have experienced, the quantity of stale
> information on the web (broken links to blogs, wikis, examples, libraries,
> etc.) is incredibly frustrating and can be a massive time thief.
>
> Therefore, assuming an Apache Flex Cookbook in future, my personal
> suggestion would be to use the initial book to rationalise this and other
> information on the wiki. Walkthrough examples of how to Mavenise an SDK and
> configure builds using the latest versions of Flexmojos and Flexunit (the
> other projects donated to Apache) would also be really powerful.
>
> I offer my services towards this project in any capacity and will certainly
> pre-order if this is helpful to the cause.
>
> Keep up the great work everyone.
>
>
> On 23 January 2014 08:38, Arne Broedel <ar...@googlemail.com>
> wrote:
>
> > Great I love to read this thread and feel the engagement. I would want a
> > copy just because this community drives it.
> > Am 23.01.2014 09:07 schrieb "Patel Amit" <am...@gmail.com>:
> >
> > > Here what I want to into the wishlist as following ::
> > >
> > > -  Apache Flex new sdks and improvement on Adobe flex 4.6
> > > -  New Apache Flex components related to 4.10 sdks if any
> > > - Connect with different technologies [Java , Dot net ,PHP]
> > > - There should be some Mobile and Tablets demo
> > > - Also we can cover the Falcon
> > > - There should be also the demo to build the application using Mustella
> > > framework
> > > - FlexUnit
> > > - some reference link related to Apache flex showcase
> > >
> > >
> > > Regards,
> > >
> > >
> > >
> > >
> > >
> > > On Thu, Jan 23, 2014 at 11:01 AM, Joseph Balderson <ne...@joeflash.ca>
> > > wrote:
> > >
> > > > Thanks for your contributions Thiago. Let's table wish list items to
> a
> > > > separate
> > > > thread.
> > > >
> > > >
> _______________________________________________________________________
> > > >
> > > > Joseph Balderson, Flex & Flash Platform Developer ::
> > http://joeflash.ca
> > > > Author, Professional Flex 3 :: http://tinyurl.com/proflex3book
> > > >
> > > > a00s@a00s.com wrote:
> > > > > Hi
> > > > >
> > > > >     Wish list, that I think it is important to those who want to
> > start.
> > > > > Just my opinion, things that took me long time to understand, that
> > > could
> > > > > be very simple and quickly if I could found in one place.
> > > > >
> > > > > 1) How to download Flex. Looks stupid but once you download and
> > install
> > > > > you start to wondering. OK now what I do? It was my first reaction
> > when
> > > > > moved to apache. It was my first time downloading separately from
> > Adobe
> > > > > builder.
> > > > > 2) How to setup Flex with adobe builder
> > > > > 3) How to setup Flex with Intelij
> > > > > 4) Probably the most important in my view: How to connect a flex
> > > > > application with a database (maybe how to setup tomcat, blazeds)
> > > > > 5) How to use external resourses with Flex like javascript. To show
> > > that
> > > > > Flex its not a competitor of other languages but a language to
> build
> > > the
> > > > > entire application, doesnt matter if will need to put together
> > > > > javascript, applet...
> > > > > 6) Show how to make 3d objects, not sure if the 3rd solution will
> > allow
> > > > > this one.
> > > > > 7) How to print. Any business application will need that at some
> > point,
> > > > > and many times we need a clear text to print, not a postscript
> image,
> > > > > maybe how to convert in PDF.
> > > > > 8) How to check why your application is crashing the browser and
> how
> > to
> > > > > debug.
> > > > >
> > > > > thanks for starting this book
> > > > >
> > > > > Thiago Maia
> > > > >
> > > > >
> > > > > On 1/22/2014 7:59 PM, Joseph Balderson wrote:
> > > > >> Thanks Justin.
> > > > >>
> > > > >> One rule of thumb for time involved is 1-2 hours per page for
> > authors
> > > > >> -- that's
> > > > >> me -- and 5-10 minutes per page for tech editing -- that's you
> > Justin.
> > > > >> Which is
> > > > >> why, if a book goes past 400 pages, you need more than one author,
> > > > >> unless you're
> > > > >> David Gassner who can crack off a 1000-page Flex Bible book all by
> > > > >> himself (god
> > > > >> only knows how the hell he does it). Given the scope of the book,
> > I'm
> > > > >> probably
> > > > >> looking at 6 months to write, with tech editing as it's written,
> so
> > > > >> there's
> > > > >> time. Professional Adobe Flex 3 only had two tech editors, and
> that
> > > was
> > > > a
> > > > >> 1400-page book (in retrospect we probably should have had three,
> but
> > > > >> whaddyagonnado?) If you find you need help with the tech editing
> > > > >> Justin, we'll
> > > > >> cross that bridge when we get to it, but for now consider that
> post
> > to
> > > > >> be filled
> > > > >> by you.
> > > > >>
> > > > >> There are three possible classic "animal" books I could do with
> > > > >> O'Reilly for
> > > > >> Apache Flex -- one is the "Programming Foo" series, the other is
> the
> > > > "Foo
> > > > >> Cookbook" series, and the third are "Developing Fum Applications
> for
> > > > Foo"
> > > > >> micro-books. The last book on Flex in the "Programming" series was
> > > > >> "Programming
> > > > >> Flex 3" by Chafic Kazoun & Joey Lott, so we're due for an update.
> > > > >> There is a
> > > > >> "Flex 4 Cookbook" and some Flex 4.5 micro-books by Rich Tretola
> back
> > > > >> in 2011,
> > > > >> but nothing recent.
> > > > >>
> > > > >> I think we'll go with a "Programming Apache Flex" book this time,
> > with
> > > > an
> > > > >> emphasis on the Spark portion of the framework, and what's been
> > > > >> updated since
> > > > >> Adobe Flex 4.6, rather than going over everything, considering the
> > > > >> wealth of
> > > > >> information already published on Flex 3 and 4. And also because I
> > > > >> don't want to
> > > > >> embark on another monster book project; we'll keep it at around
> 400
> > > > >> pages, which
> > > > >> would be easier to sell to O'Reilly.
> > > > >>
> > > > >> Doing an "Apache Flex Cookbook" would be a nice second book, but
> as
> > a
> > > > >> collaborative effort, because it would be a bit of a monster to
> do,
> > > > >> considering
> > > > >> that the "Flex 4 Cookbook" weighed in at 740 pages. If O'Reilly
> > gets a
> > > > >> good ROI
> > > > >> (i.e. it breaks even ;) on this first book, they might consider
> > doing
> > > > the
> > > > >> cookbook. But we'll cross that bridge when we get to it.
> > > > >>
> > > > >> What I will need people's input on, when the book proposal is
> > > > >> approved, are
> > > > >> general ideas, or rather a wish list of "what you'd like to see in
> > the
> > > > >> book",
> > > > >> keeping in mind what kind of book this will be.
> > > > >>
> > > > >>
> > > > >> I'll keep everyone updated as I hear from them.
> > > > >>
> > > > >>
> > > _______________________________________________________________________
> > > > >>
> > > > >> Joseph Balderson, Flex & Flash Platform Developer ::
> > > http://joeflash.ca
> > > > >> Author, Professional Flex 3 :: http://tinyurl.com/proflex3book
> > > > >>
> > > > >> Justin Mclean wrote:
> > > > >>> Hi,
> > > > >>>
> > > > >>>> You'll do fine, Justin. As long as you're willing to put in the
> > time
> > > > >>>> to read and
> > > > >>>> double-read the entire book (usually as it's written chapter by
> > > > >>>> chapter)
> > > > >>> OK I'm in - but that shouldn't stop other people from wanting to
> > help
> > > > >>> out as well.
> > > > >>>
> > > > >>> Thanks,
> > > > >>> Justin
> > > > >
> > > > >
> > > >
> > >
> >
>

RE: AW: O'Reilly Apache Flex book help

[Miguel Ferreira <mi...@hotmail.com>]

That would be great!
+1 for pre order
But, as we can see topics exists in quantity!

> From: christofer.dutz@c-ware.de
> To: users@flex.apache.org
> Subject: AW: O'Reilly Apache Flex book help
> Date: Thu, 23 Jan 2014 15:15:42 +0000
> 
> Guess I could definitely jump in to help with the Maven + Flexmojos part :-)
> Think this has never actually been covered by any printed book.
> 
> Chris
> ________________________________________
> Von: John Gardiner <jw...@gmail.com>
> Gesendet: Donnerstag, 23. Januar 2014 15:13
> An: users@flex.apache.org
> Betreff: Re: O'Reilly Apache Flex book help
> 
> An Apache Flex book will be a great statement of intent for the future of
> the technology. I hope this can be realised.
> 
> My own experience is that Apache Flex is being re-adopted in a number of
> significant domains, especially when used in conjunction with Adobe Air.
> However, as I am sure others here have experienced, the quantity of stale
> information on the web (broken links to blogs, wikis, examples, libraries,
> etc.) is incredibly frustrating and can be a massive time thief.
> 
> Therefore, assuming an Apache Flex Cookbook in future, my personal
> suggestion would be to use the initial book to rationalise this and other
> information on the wiki. Walkthrough examples of how to Mavenise an SDK and
> configure builds using the latest versions of Flexmojos and Flexunit (the
> other projects donated to Apache) would also be really powerful.
> 
> I offer my services towards this project in any capacity and will certainly
> pre-order if this is helpful to the cause.
> 
> Keep up the great work everyone.
> 
> 
> On 23 January 2014 08:38, Arne Broedel <ar...@googlemail.com> wrote:
> 
> > Great I love to read this thread and feel the engagement. I would want a
> > copy just because this community drives it.
> > Am 23.01.2014 09:07 schrieb "Patel Amit" <am...@gmail.com>:
> >
> > > Here what I want to into the wishlist as following ::
> > >
> > > -  Apache Flex new sdks and improvement on Adobe flex 4.6
> > > -  New Apache Flex components related to 4.10 sdks if any
> > > - Connect with different technologies [Java , Dot net ,PHP]
> > > - There should be some Mobile and Tablets demo
> > > - Also we can cover the Falcon
> > > - There should be also the demo to build the application using Mustella
> > > framework
> > > - FlexUnit
> > > - some reference link related to Apache flex showcase
> > >
> > >
> > > Regards,
> > >
> > >
> > >
> > >
> > >
> > > On Thu, Jan 23, 2014 at 11:01 AM, Joseph Balderson <ne...@joeflash.ca>
> > > wrote:
> > >
> > > > Thanks for your contributions Thiago. Let's table wish list items to a
> > > > separate
> > > > thread.
> > > >
> > > > _______________________________________________________________________
> > > >
> > > > Joseph Balderson, Flex & Flash Platform Developer ::
> > http://joeflash.ca
> > > > Author, Professional Flex 3 :: http://tinyurl.com/proflex3book
> > > >
> > > > a00s@a00s.com wrote:
> > > > > Hi
> > > > >
> > > > >     Wish list, that I think it is important to those who want to
> > start.
> > > > > Just my opinion, things that took me long time to understand, that
> > > could
> > > > > be very simple and quickly if I could found in one place.
> > > > >
> > > > > 1) How to download Flex. Looks stupid but once you download and
> > install
> > > > > you start to wondering. OK now what I do? It was my first reaction
> > when
> > > > > moved to apache. It was my first time downloading separately from
> > Adobe
> > > > > builder.
> > > > > 2) How to setup Flex with adobe builder
> > > > > 3) How to setup Flex with Intelij
> > > > > 4) Probably the most important in my view: How to connect a flex
> > > > > application with a database (maybe how to setup tomcat, blazeds)
> > > > > 5) How to use external resourses with Flex like javascript. To show
> > > that
> > > > > Flex its not a competitor of other languages but a language to build
> > > the
> > > > > entire application, doesnt matter if will need to put together
> > > > > javascript, applet...
> > > > > 6) Show how to make 3d objects, not sure if the 3rd solution will
> > allow
> > > > > this one.
> > > > > 7) How to print. Any business application will need that at some
> > point,
> > > > > and many times we need a clear text to print, not a postscript image,
> > > > > maybe how to convert in PDF.
> > > > > 8) How to check why your application is crashing the browser and how
> > to
> > > > > debug.
> > > > >
> > > > > thanks for starting this book
> > > > >
> > > > > Thiago Maia
> > > > >
> > > > >
> > > > > On 1/22/2014 7:59 PM, Joseph Balderson wrote:
> > > > >> Thanks Justin.
> > > > >>
> > > > >> One rule of thumb for time involved is 1-2 hours per page for
> > authors
> > > > >> -- that's
> > > > >> me -- and 5-10 minutes per page for tech editing -- that's you
> > Justin.
> > > > >> Which is
> > > > >> why, if a book goes past 400 pages, you need more than one author,
> > > > >> unless you're
> > > > >> David Gassner who can crack off a 1000-page Flex Bible book all by
> > > > >> himself (god
> > > > >> only knows how the hell he does it). Given the scope of the book,
> > I'm
> > > > >> probably
> > > > >> looking at 6 months to write, with tech editing as it's written, so
> > > > >> there's
> > > > >> time. Professional Adobe Flex 3 only had two tech editors, and that
> > > was
> > > > a
> > > > >> 1400-page book (in retrospect we probably should have had three, but
> > > > >> whaddyagonnado?) If you find you need help with the tech editing
> > > > >> Justin, we'll
> > > > >> cross that bridge when we get to it, but for now consider that post
> > to
> > > > >> be filled
> > > > >> by you.
> > > > >>
> > > > >> There are three possible classic "animal" books I could do with
> > > > >> O'Reilly for
> > > > >> Apache Flex -- one is the "Programming Foo" series, the other is the
> > > > "Foo
> > > > >> Cookbook" series, and the third are "Developing Fum Applications for
> > > > Foo"
> > > > >> micro-books. The last book on Flex in the "Programming" series was
> > > > >> "Programming
> > > > >> Flex 3" by Chafic Kazoun & Joey Lott, so we're due for an update.
> > > > >> There is a
> > > > >> "Flex 4 Cookbook" and some Flex 4.5 micro-books by Rich Tretola back
> > > > >> in 2011,
> > > > >> but nothing recent.
> > > > >>
> > > > >> I think we'll go with a "Programming Apache Flex" book this time,
> > with
> > > > an
> > > > >> emphasis on the Spark portion of the framework, and what's been
> > > > >> updated since
> > > > >> Adobe Flex 4.6, rather than going over everything, considering the
> > > > >> wealth of
> > > > >> information already published on Flex 3 and 4. And also because I
> > > > >> don't want to
> > > > >> embark on another monster book project; we'll keep it at around 400
> > > > >> pages, which
> > > > >> would be easier to sell to O'Reilly.
> > > > >>
> > > > >> Doing an "Apache Flex Cookbook" would be a nice second book, but as
> > a
> > > > >> collaborative effort, because it would be a bit of a monster to do,
> > > > >> considering
> > > > >> that the "Flex 4 Cookbook" weighed in at 740 pages. If O'Reilly
> > gets a
> > > > >> good ROI
> > > > >> (i.e. it breaks even ;) on this first book, they might consider
> > doing
> > > > the
> > > > >> cookbook. But we'll cross that bridge when we get to it.
> > > > >>
> > > > >> What I will need people's input on, when the book proposal is
> > > > >> approved, are
> > > > >> general ideas, or rather a wish list of "what you'd like to see in
> > the
> > > > >> book",
> > > > >> keeping in mind what kind of book this will be.
> > > > >>
> > > > >>
> > > > >> I'll keep everyone updated as I hear from them.
> > > > >>
> > > > >>
> > > _______________________________________________________________________
> > > > >>
> > > > >> Joseph Balderson, Flex & Flash Platform Developer ::
> > > http://joeflash.ca
> > > > >> Author, Professional Flex 3 :: http://tinyurl.com/proflex3book
> > > > >>
> > > > >> Justin Mclean wrote:
> > > > >>> Hi,
> > > > >>>
> > > > >>>> You'll do fine, Justin. As long as you're willing to put in the
> > time
> > > > >>>> to read and
> > > > >>>> double-read the entire book (usually as it's written chapter by
> > > > >>>> chapter)
> > > > >>> OK I'm in - but that shouldn't stop other people from wanting to
> > help
> > > > >>> out as well.
> > > > >>>
> > > > >>> Thanks,
> > > > >>> Justin
> > > > >
> > > > >
> > > >
> > >
> >
 		 	   		  

AW: O'Reilly Apache Flex book help

[Christofer Dutz <ch...@c-ware.de>]

Guess I could definitely jump in to help with the Maven + Flexmojos part :-)
Think this has never actually been covered by any printed book.

Chris
________________________________________
Von: John Gardiner <jw...@gmail.com>
Gesendet: Donnerstag, 23. Januar 2014 15:13
An: users@flex.apache.org
Betreff: Re: O'Reilly Apache Flex book help

An Apache Flex book will be a great statement of intent for the future of
the technology. I hope this can be realised.

My own experience is that Apache Flex is being re-adopted in a number of
significant domains, especially when used in conjunction with Adobe Air.
However, as I am sure others here have experienced, the quantity of stale
information on the web (broken links to blogs, wikis, examples, libraries,
etc.) is incredibly frustrating and can be a massive time thief.

Therefore, assuming an Apache Flex Cookbook in future, my personal
suggestion would be to use the initial book to rationalise this and other
information on the wiki. Walkthrough examples of how to Mavenise an SDK and
configure builds using the latest versions of Flexmojos and Flexunit (the
other projects donated to Apache) would also be really powerful.

I offer my services towards this project in any capacity and will certainly
pre-order if this is helpful to the cause.

Keep up the great work everyone.


On 23 January 2014 08:38, Arne Broedel <ar...@googlemail.com> wrote:

> Great I love to read this thread and feel the engagement. I would want a
> copy just because this community drives it.
> Am 23.01.2014 09:07 schrieb "Patel Amit" <am...@gmail.com>:
>
> > Here what I want to into the wishlist as following ::
> >
> > -  Apache Flex new sdks and improvement on Adobe flex 4.6
> > -  New Apache Flex components related to 4.10 sdks if any
> > - Connect with different technologies [Java , Dot net ,PHP]
> > - There should be some Mobile and Tablets demo
> > - Also we can cover the Falcon
> > - There should be also the demo to build the application using Mustella
> > framework
> > - FlexUnit
> > - some reference link related to Apache flex showcase
> >
> >
> > Regards,
> >
> >
> >
> >
> >
> > On Thu, Jan 23, 2014 at 11:01 AM, Joseph Balderson <ne...@joeflash.ca>
> > wrote:
> >
> > > Thanks for your contributions Thiago. Let's table wish list items to a
> > > separate
> > > thread.
> > >
> > > _______________________________________________________________________
> > >
> > > Joseph Balderson, Flex & Flash Platform Developer ::
> http://joeflash.ca
> > > Author, Professional Flex 3 :: http://tinyurl.com/proflex3book
> > >
> > > a00s@a00s.com wrote:
> > > > Hi
> > > >
> > > >     Wish list, that I think it is important to those who want to
> start.
> > > > Just my opinion, things that took me long time to understand, that
> > could
> > > > be very simple and quickly if I could found in one place.
> > > >
> > > > 1) How to download Flex. Looks stupid but once you download and
> install
> > > > you start to wondering. OK now what I do? It was my first reaction
> when
> > > > moved to apache. It was my first time downloading separately from
> Adobe
> > > > builder.
> > > > 2) How to setup Flex with adobe builder
> > > > 3) How to setup Flex with Intelij
> > > > 4) Probably the most important in my view: How to connect a flex
> > > > application with a database (maybe how to setup tomcat, blazeds)
> > > > 5) How to use external resourses with Flex like javascript. To show
> > that
> > > > Flex its not a competitor of other languages but a language to build
> > the
> > > > entire application, doesnt matter if will need to put together
> > > > javascript, applet...
> > > > 6) Show how to make 3d objects, not sure if the 3rd solution will
> allow
> > > > this one.
> > > > 7) How to print. Any business application will need that at some
> point,
> > > > and many times we need a clear text to print, not a postscript image,
> > > > maybe how to convert in PDF.
> > > > 8) How to check why your application is crashing the browser and how
> to
> > > > debug.
> > > >
> > > > thanks for starting this book
> > > >
> > > > Thiago Maia
> > > >
> > > >
> > > > On 1/22/2014 7:59 PM, Joseph Balderson wrote:
> > > >> Thanks Justin.
> > > >>
> > > >> One rule of thumb for time involved is 1-2 hours per page for
> authors
> > > >> -- that's
> > > >> me -- and 5-10 minutes per page for tech editing -- that's you
> Justin.
> > > >> Which is
> > > >> why, if a book goes past 400 pages, you need more than one author,
> > > >> unless you're
> > > >> David Gassner who can crack off a 1000-page Flex Bible book all by
> > > >> himself (god
> > > >> only knows how the hell he does it). Given the scope of the book,
> I'm
> > > >> probably
> > > >> looking at 6 months to write, with tech editing as it's written, so
> > > >> there's
> > > >> time. Professional Adobe Flex 3 only had two tech editors, and that
> > was
> > > a
> > > >> 1400-page book (in retrospect we probably should have had three, but
> > > >> whaddyagonnado?) If you find you need help with the tech editing
> > > >> Justin, we'll
> > > >> cross that bridge when we get to it, but for now consider that post
> to
> > > >> be filled
> > > >> by you.
> > > >>
> > > >> There are three possible classic "animal" books I could do with
> > > >> O'Reilly for
> > > >> Apache Flex -- one is the "Programming Foo" series, the other is the
> > > "Foo
> > > >> Cookbook" series, and the third are "Developing Fum Applications for
> > > Foo"
> > > >> micro-books. The last book on Flex in the "Programming" series was
> > > >> "Programming
> > > >> Flex 3" by Chafic Kazoun & Joey Lott, so we're due for an update.
> > > >> There is a
> > > >> "Flex 4 Cookbook" and some Flex 4.5 micro-books by Rich Tretola back
> > > >> in 2011,
> > > >> but nothing recent.
> > > >>
> > > >> I think we'll go with a "Programming Apache Flex" book this time,
> with
> > > an
> > > >> emphasis on the Spark portion of the framework, and what's been
> > > >> updated since
> > > >> Adobe Flex 4.6, rather than going over everything, considering the
> > > >> wealth of
> > > >> information already published on Flex 3 and 4. And also because I
> > > >> don't want to
> > > >> embark on another monster book project; we'll keep it at around 400
> > > >> pages, which
> > > >> would be easier to sell to O'Reilly.
> > > >>
> > > >> Doing an "Apache Flex Cookbook" would be a nice second book, but as
> a
> > > >> collaborative effort, because it would be a bit of a monster to do,
> > > >> considering
> > > >> that the "Flex 4 Cookbook" weighed in at 740 pages. If O'Reilly
> gets a
> > > >> good ROI
> > > >> (i.e. it breaks even ;) on this first book, they might consider
> doing
> > > the
> > > >> cookbook. But we'll cross that bridge when we get to it.
> > > >>
> > > >> What I will need people's input on, when the book proposal is
> > > >> approved, are
> > > >> general ideas, or rather a wish list of "what you'd like to see in
> the
> > > >> book",
> > > >> keeping in mind what kind of book this will be.
> > > >>
> > > >>
> > > >> I'll keep everyone updated as I hear from them.
> > > >>
> > > >>
> > _______________________________________________________________________
> > > >>
> > > >> Joseph Balderson, Flex & Flash Platform Developer ::
> > http://joeflash.ca
> > > >> Author, Professional Flex 3 :: http://tinyurl.com/proflex3book
> > > >>
> > > >> Justin Mclean wrote:
> > > >>> Hi,
> > > >>>
> > > >>>> You'll do fine, Justin. As long as you're willing to put in the
> time
> > > >>>> to read and
> > > >>>> double-read the entire book (usually as it's written chapter by
> > > >>>> chapter)
> > > >>> OK I'm in - but that shouldn't stop other people from wanting to
> help
> > > >>> out as well.
> > > >>>
> > > >>> Thanks,
> > > >>> Justin
> > > >
> > > >
> > >
> >
>

Re: O'Reilly Apache Flex book help

[John Gardiner <jw...@gmail.com>]

An Apache Flex book will be a great statement of intent for the future of
the technology. I hope this can be realised.

My own experience is that Apache Flex is being re-adopted in a number of
significant domains, especially when used in conjunction with Adobe Air.
However, as I am sure others here have experienced, the quantity of stale
information on the web (broken links to blogs, wikis, examples, libraries,
etc.) is incredibly frustrating and can be a massive time thief.

Therefore, assuming an Apache Flex Cookbook in future, my personal
suggestion would be to use the initial book to rationalise this and other
information on the wiki. Walkthrough examples of how to Mavenise an SDK and
configure builds using the latest versions of Flexmojos and Flexunit (the
other projects donated to Apache) would also be really powerful.

I offer my services towards this project in any capacity and will certainly
pre-order if this is helpful to the cause.

Keep up the great work everyone.


On 23 January 2014 08:38, Arne Broedel <ar...@googlemail.com> wrote:

> Great I love to read this thread and feel the engagement. I would want a
> copy just because this community drives it.
> Am 23.01.2014 09:07 schrieb "Patel Amit" <am...@gmail.com>:
>
> > Here what I want to into the wishlist as following ::
> >
> > -  Apache Flex new sdks and improvement on Adobe flex 4.6
> > -  New Apache Flex components related to 4.10 sdks if any
> > - Connect with different technologies [Java , Dot net ,PHP]
> > - There should be some Mobile and Tablets demo
> > - Also we can cover the Falcon
> > - There should be also the demo to build the application using Mustella
> > framework
> > - FlexUnit
> > - some reference link related to Apache flex showcase
> >
> >
> > Regards,
> >
> >
> >
> >
> >
> > On Thu, Jan 23, 2014 at 11:01 AM, Joseph Balderson <ne...@joeflash.ca>
> > wrote:
> >
> > > Thanks for your contributions Thiago. Let's table wish list items to a
> > > separate
> > > thread.
> > >
> > > _______________________________________________________________________
> > >
> > > Joseph Balderson, Flex & Flash Platform Developer ::
> http://joeflash.ca
> > > Author, Professional Flex 3 :: http://tinyurl.com/proflex3book
> > >
> > > a00s@a00s.com wrote:
> > > > Hi
> > > >
> > > >     Wish list, that I think it is important to those who want to
> start.
> > > > Just my opinion, things that took me long time to understand, that
> > could
> > > > be very simple and quickly if I could found in one place.
> > > >
> > > > 1) How to download Flex. Looks stupid but once you download and
> install
> > > > you start to wondering. OK now what I do? It was my first reaction
> when
> > > > moved to apache. It was my first time downloading separately from
> Adobe
> > > > builder.
> > > > 2) How to setup Flex with adobe builder
> > > > 3) How to setup Flex with Intelij
> > > > 4) Probably the most important in my view: How to connect a flex
> > > > application with a database (maybe how to setup tomcat, blazeds)
> > > > 5) How to use external resourses with Flex like javascript. To show
> > that
> > > > Flex its not a competitor of other languages but a language to build
> > the
> > > > entire application, doesnt matter if will need to put together
> > > > javascript, applet...
> > > > 6) Show how to make 3d objects, not sure if the 3rd solution will
> allow
> > > > this one.
> > > > 7) How to print. Any business application will need that at some
> point,
> > > > and many times we need a clear text to print, not a postscript image,
> > > > maybe how to convert in PDF.
> > > > 8) How to check why your application is crashing the browser and how
> to
> > > > debug.
> > > >
> > > > thanks for starting this book
> > > >
> > > > Thiago Maia
> > > >
> > > >
> > > > On 1/22/2014 7:59 PM, Joseph Balderson wrote:
> > > >> Thanks Justin.
> > > >>
> > > >> One rule of thumb for time involved is 1-2 hours per page for
> authors
> > > >> -- that's
> > > >> me -- and 5-10 minutes per page for tech editing -- that's you
> Justin.
> > > >> Which is
> > > >> why, if a book goes past 400 pages, you need more than one author,
> > > >> unless you're
> > > >> David Gassner who can crack off a 1000-page Flex Bible book all by
> > > >> himself (god
> > > >> only knows how the hell he does it). Given the scope of the book,
> I'm
> > > >> probably
> > > >> looking at 6 months to write, with tech editing as it's written, so
> > > >> there's
> > > >> time. Professional Adobe Flex 3 only had two tech editors, and that
> > was
> > > a
> > > >> 1400-page book (in retrospect we probably should have had three, but
> > > >> whaddyagonnado?) If you find you need help with the tech editing
> > > >> Justin, we'll
> > > >> cross that bridge when we get to it, but for now consider that post
> to
> > > >> be filled
> > > >> by you.
> > > >>
> > > >> There are three possible classic "animal" books I could do with
> > > >> O'Reilly for
> > > >> Apache Flex -- one is the "Programming Foo" series, the other is the
> > > "Foo
> > > >> Cookbook" series, and the third are "Developing Fum Applications for
> > > Foo"
> > > >> micro-books. The last book on Flex in the "Programming" series was
> > > >> "Programming
> > > >> Flex 3" by Chafic Kazoun & Joey Lott, so we're due for an update.
> > > >> There is a
> > > >> "Flex 4 Cookbook" and some Flex 4.5 micro-books by Rich Tretola back
> > > >> in 2011,
> > > >> but nothing recent.
> > > >>
> > > >> I think we'll go with a "Programming Apache Flex" book this time,
> with
> > > an
> > > >> emphasis on the Spark portion of the framework, and what's been
> > > >> updated since
> > > >> Adobe Flex 4.6, rather than going over everything, considering the
> > > >> wealth of
> > > >> information already published on Flex 3 and 4. And also because I
> > > >> don't want to
> > > >> embark on another monster book project; we'll keep it at around 400
> > > >> pages, which
> > > >> would be easier to sell to O'Reilly.
> > > >>
> > > >> Doing an "Apache Flex Cookbook" would be a nice second book, but as
> a
> > > >> collaborative effort, because it would be a bit of a monster to do,
> > > >> considering
> > > >> that the "Flex 4 Cookbook" weighed in at 740 pages. If O'Reilly
> gets a
> > > >> good ROI
> > > >> (i.e. it breaks even ;) on this first book, they might consider
> doing
> > > the
> > > >> cookbook. But we'll cross that bridge when we get to it.
> > > >>
> > > >> What I will need people's input on, when the book proposal is
> > > >> approved, are
> > > >> general ideas, or rather a wish list of "what you'd like to see in
> the
> > > >> book",
> > > >> keeping in mind what kind of book this will be.
> > > >>
> > > >>
> > > >> I'll keep everyone updated as I hear from them.
> > > >>
> > > >>
> > _______________________________________________________________________
> > > >>
> > > >> Joseph Balderson, Flex & Flash Platform Developer ::
> > http://joeflash.ca
> > > >> Author, Professional Flex 3 :: http://tinyurl.com/proflex3book
> > > >>
> > > >> Justin Mclean wrote:
> > > >>> Hi,
> > > >>>
> > > >>>> You'll do fine, Justin. As long as you're willing to put in the
> time
> > > >>>> to read and
> > > >>>> double-read the entire book (usually as it's written chapter by
> > > >>>> chapter)
> > > >>> OK I'm in - but that shouldn't stop other people from wanting to
> help
> > > >>> out as well.
> > > >>>
> > > >>> Thanks,
> > > >>> Justin
> > > >
> > > >
> > >
> >
>

Re: O'Reilly Apache Flex book help

[Arne Broedel <ar...@googlemail.com>]

Great I love to read this thread and feel the engagement. I would want a
copy just because this community drives it.
Am 23.01.2014 09:07 schrieb "Patel Amit" <am...@gmail.com>:

> Here what I want to into the wishlist as following ::
>
> -  Apache Flex new sdks and improvement on Adobe flex 4.6
> -  New Apache Flex components related to 4.10 sdks if any
> - Connect with different technologies [Java , Dot net ,PHP]
> - There should be some Mobile and Tablets demo
> - Also we can cover the Falcon
> - There should be also the demo to build the application using Mustella
> framework
> - FlexUnit
> - some reference link related to Apache flex showcase
>
>
> Regards,
>
>
>
>
>
> On Thu, Jan 23, 2014 at 11:01 AM, Joseph Balderson <ne...@joeflash.ca>
> wrote:
>
> > Thanks for your contributions Thiago. Let's table wish list items to a
> > separate
> > thread.
> >
> > _______________________________________________________________________
> >
> > Joseph Balderson, Flex & Flash Platform Developer :: http://joeflash.ca
> > Author, Professional Flex 3 :: http://tinyurl.com/proflex3book
> >
> > a00s@a00s.com wrote:
> > > Hi
> > >
> > >     Wish list, that I think it is important to those who want to start.
> > > Just my opinion, things that took me long time to understand, that
> could
> > > be very simple and quickly if I could found in one place.
> > >
> > > 1) How to download Flex. Looks stupid but once you download and install
> > > you start to wondering. OK now what I do? It was my first reaction when
> > > moved to apache. It was my first time downloading separately from Adobe
> > > builder.
> > > 2) How to setup Flex with adobe builder
> > > 3) How to setup Flex with Intelij
> > > 4) Probably the most important in my view: How to connect a flex
> > > application with a database (maybe how to setup tomcat, blazeds)
> > > 5) How to use external resourses with Flex like javascript. To show
> that
> > > Flex its not a competitor of other languages but a language to build
> the
> > > entire application, doesnt matter if will need to put together
> > > javascript, applet...
> > > 6) Show how to make 3d objects, not sure if the 3rd solution will allow
> > > this one.
> > > 7) How to print. Any business application will need that at some point,
> > > and many times we need a clear text to print, not a postscript image,
> > > maybe how to convert in PDF.
> > > 8) How to check why your application is crashing the browser and how to
> > > debug.
> > >
> > > thanks for starting this book
> > >
> > > Thiago Maia
> > >
> > >
> > > On 1/22/2014 7:59 PM, Joseph Balderson wrote:
> > >> Thanks Justin.
> > >>
> > >> One rule of thumb for time involved is 1-2 hours per page for authors
> > >> -- that's
> > >> me -- and 5-10 minutes per page for tech editing -- that's you Justin.
> > >> Which is
> > >> why, if a book goes past 400 pages, you need more than one author,
> > >> unless you're
> > >> David Gassner who can crack off a 1000-page Flex Bible book all by
> > >> himself (god
> > >> only knows how the hell he does it). Given the scope of the book, I'm
> > >> probably
> > >> looking at 6 months to write, with tech editing as it's written, so
> > >> there's
> > >> time. Professional Adobe Flex 3 only had two tech editors, and that
> was
> > a
> > >> 1400-page book (in retrospect we probably should have had three, but
> > >> whaddyagonnado?) If you find you need help with the tech editing
> > >> Justin, we'll
> > >> cross that bridge when we get to it, but for now consider that post to
> > >> be filled
> > >> by you.
> > >>
> > >> There are three possible classic "animal" books I could do with
> > >> O'Reilly for
> > >> Apache Flex -- one is the "Programming Foo" series, the other is the
> > "Foo
> > >> Cookbook" series, and the third are "Developing Fum Applications for
> > Foo"
> > >> micro-books. The last book on Flex in the "Programming" series was
> > >> "Programming
> > >> Flex 3" by Chafic Kazoun & Joey Lott, so we're due for an update.
> > >> There is a
> > >> "Flex 4 Cookbook" and some Flex 4.5 micro-books by Rich Tretola back
> > >> in 2011,
> > >> but nothing recent.
> > >>
> > >> I think we'll go with a "Programming Apache Flex" book this time, with
> > an
> > >> emphasis on the Spark portion of the framework, and what's been
> > >> updated since
> > >> Adobe Flex 4.6, rather than going over everything, considering the
> > >> wealth of
> > >> information already published on Flex 3 and 4. And also because I
> > >> don't want to
> > >> embark on another monster book project; we'll keep it at around 400
> > >> pages, which
> > >> would be easier to sell to O'Reilly.
> > >>
> > >> Doing an "Apache Flex Cookbook" would be a nice second book, but as a
> > >> collaborative effort, because it would be a bit of a monster to do,
> > >> considering
> > >> that the "Flex 4 Cookbook" weighed in at 740 pages. If O'Reilly gets a
> > >> good ROI
> > >> (i.e. it breaks even ;) on this first book, they might consider doing
> > the
> > >> cookbook. But we'll cross that bridge when we get to it.
> > >>
> > >> What I will need people's input on, when the book proposal is
> > >> approved, are
> > >> general ideas, or rather a wish list of "what you'd like to see in the
> > >> book",
> > >> keeping in mind what kind of book this will be.
> > >>
> > >>
> > >> I'll keep everyone updated as I hear from them.
> > >>
> > >>
> _______________________________________________________________________
> > >>
> > >> Joseph Balderson, Flex & Flash Platform Developer ::
> http://joeflash.ca
> > >> Author, Professional Flex 3 :: http://tinyurl.com/proflex3book
> > >>
> > >> Justin Mclean wrote:
> > >>> Hi,
> > >>>
> > >>>> You'll do fine, Justin. As long as you're willing to put in the time
> > >>>> to read and
> > >>>> double-read the entire book (usually as it's written chapter by
> > >>>> chapter)
> > >>> OK I'm in - but that shouldn't stop other people from wanting to help
> > >>> out as well.
> > >>>
> > >>> Thanks,
> > >>> Justin
> > >
> > >
> >
>

Re: O'Reilly Apache Flex book help

[Patel Amit <am...@gmail.com>]

Here what I want to into the wishlist as following ::

-  Apache Flex new sdks and improvement on Adobe flex 4.6
-  New Apache Flex components related to 4.10 sdks if any
- Connect with different technologies [Java , Dot net ,PHP]
- There should be some Mobile and Tablets demo
- Also we can cover the Falcon
- There should be also the demo to build the application using Mustella
framework
- FlexUnit
- some reference link related to Apache flex showcase


Regards,





On Thu, Jan 23, 2014 at 11:01 AM, Joseph Balderson <ne...@joeflash.ca> wrote:

> Thanks for your contributions Thiago. Let's table wish list items to a
> separate
> thread.
>
> _______________________________________________________________________
>
> Joseph Balderson, Flex & Flash Platform Developer :: http://joeflash.ca
> Author, Professional Flex 3 :: http://tinyurl.com/proflex3book
>
> a00s@a00s.com wrote:
> > Hi
> >
> >     Wish list, that I think it is important to those who want to start.
> > Just my opinion, things that took me long time to understand, that could
> > be very simple and quickly if I could found in one place.
> >
> > 1) How to download Flex. Looks stupid but once you download and install
> > you start to wondering. OK now what I do? It was my first reaction when
> > moved to apache. It was my first time downloading separately from Adobe
> > builder.
> > 2) How to setup Flex with adobe builder
> > 3) How to setup Flex with Intelij
> > 4) Probably the most important in my view: How to connect a flex
> > application with a database (maybe how to setup tomcat, blazeds)
> > 5) How to use external resourses with Flex like javascript. To show that
> > Flex its not a competitor of other languages but a language to build the
> > entire application, doesnt matter if will need to put together
> > javascript, applet...
> > 6) Show how to make 3d objects, not sure if the 3rd solution will allow
> > this one.
> > 7) How to print. Any business application will need that at some point,
> > and many times we need a clear text to print, not a postscript image,
> > maybe how to convert in PDF.
> > 8) How to check why your application is crashing the browser and how to
> > debug.
> >
> > thanks for starting this book
> >
> > Thiago Maia
> >
> >
> > On 1/22/2014 7:59 PM, Joseph Balderson wrote:
> >> Thanks Justin.
> >>
> >> One rule of thumb for time involved is 1-2 hours per page for authors
> >> -- that's
> >> me -- and 5-10 minutes per page for tech editing -- that's you Justin.
> >> Which is
> >> why, if a book goes past 400 pages, you need more than one author,
> >> unless you're
> >> David Gassner who can crack off a 1000-page Flex Bible book all by
> >> himself (god
> >> only knows how the hell he does it). Given the scope of the book, I'm
> >> probably
> >> looking at 6 months to write, with tech editing as it's written, so
> >> there's
> >> time. Professional Adobe Flex 3 only had two tech editors, and that was
> a
> >> 1400-page book (in retrospect we probably should have had three, but
> >> whaddyagonnado?) If you find you need help with the tech editing
> >> Justin, we'll
> >> cross that bridge when we get to it, but for now consider that post to
> >> be filled
> >> by you.
> >>
> >> There are three possible classic "animal" books I could do with
> >> O'Reilly for
> >> Apache Flex -- one is the "Programming Foo" series, the other is the
> "Foo
> >> Cookbook" series, and the third are "Developing Fum Applications for
> Foo"
> >> micro-books. The last book on Flex in the "Programming" series was
> >> "Programming
> >> Flex 3" by Chafic Kazoun & Joey Lott, so we're due for an update.
> >> There is a
> >> "Flex 4 Cookbook" and some Flex 4.5 micro-books by Rich Tretola back
> >> in 2011,
> >> but nothing recent.
> >>
> >> I think we'll go with a "Programming Apache Flex" book this time, with
> an
> >> emphasis on the Spark portion of the framework, and what's been
> >> updated since
> >> Adobe Flex 4.6, rather than going over everything, considering the
> >> wealth of
> >> information already published on Flex 3 and 4. And also because I
> >> don't want to
> >> embark on another monster book project; we'll keep it at around 400
> >> pages, which
> >> would be easier to sell to O'Reilly.
> >>
> >> Doing an "Apache Flex Cookbook" would be a nice second book, but as a
> >> collaborative effort, because it would be a bit of a monster to do,
> >> considering
> >> that the "Flex 4 Cookbook" weighed in at 740 pages. If O'Reilly gets a
> >> good ROI
> >> (i.e. it breaks even ;) on this first book, they might consider doing
> the
> >> cookbook. But we'll cross that bridge when we get to it.
> >>
> >> What I will need people's input on, when the book proposal is
> >> approved, are
> >> general ideas, or rather a wish list of "what you'd like to see in the
> >> book",
> >> keeping in mind what kind of book this will be.
> >>
> >>
> >> I'll keep everyone updated as I hear from them.
> >>
> >> _______________________________________________________________________
> >>
> >> Joseph Balderson, Flex & Flash Platform Developer :: http://joeflash.ca
> >> Author, Professional Flex 3 :: http://tinyurl.com/proflex3book
> >>
> >> Justin Mclean wrote:
> >>> Hi,
> >>>
> >>>> You'll do fine, Justin. As long as you're willing to put in the time
> >>>> to read and
> >>>> double-read the entire book (usually as it's written chapter by
> >>>> chapter)
> >>> OK I'm in - but that shouldn't stop other people from wanting to help
> >>> out as well.
> >>>
> >>> Thanks,
> >>> Justin
> >
> >
>

Re: O'Reilly Apache Flex book help

[Joseph Balderson <ne...@joeflash.ca>]

Thanks for your contributions Thiago. Let's table wish list items to a separate
thread.

_______________________________________________________________________

Joseph Balderson, Flex & Flash Platform Developer :: http://joeflash.ca
Author, Professional Flex 3 :: http://tinyurl.com/proflex3book

a00s@a00s.com wrote:
> Hi
> 
>     Wish list, that I think it is important to those who want to start.
> Just my opinion, things that took me long time to understand, that could
> be very simple and quickly if I could found in one place.
> 
> 1) How to download Flex. Looks stupid but once you download and install
> you start to wondering. OK now what I do? It was my first reaction when
> moved to apache. It was my first time downloading separately from Adobe
> builder.
> 2) How to setup Flex with adobe builder
> 3) How to setup Flex with Intelij
> 4) Probably the most important in my view: How to connect a flex
> application with a database (maybe how to setup tomcat, blazeds)
> 5) How to use external resourses with Flex like javascript. To show that
> Flex its not a competitor of other languages but a language to build the
> entire application, doesnt matter if will need to put together
> javascript, applet...
> 6) Show how to make 3d objects, not sure if the 3rd solution will allow
> this one.
> 7) How to print. Any business application will need that at some point,
> and many times we need a clear text to print, not a postscript image,
> maybe how to convert in PDF.
> 8) How to check why your application is crashing the browser and how to
> debug.
> 
> thanks for starting this book
> 
> Thiago Maia
> 
> 
> On 1/22/2014 7:59 PM, Joseph Balderson wrote:
>> Thanks Justin.
>>
>> One rule of thumb for time involved is 1-2 hours per page for authors
>> -- that's
>> me -- and 5-10 minutes per page for tech editing -- that's you Justin.
>> Which is
>> why, if a book goes past 400 pages, you need more than one author,
>> unless you're
>> David Gassner who can crack off a 1000-page Flex Bible book all by
>> himself (god
>> only knows how the hell he does it). Given the scope of the book, I'm
>> probably
>> looking at 6 months to write, with tech editing as it's written, so
>> there's
>> time. Professional Adobe Flex 3 only had two tech editors, and that was a
>> 1400-page book (in retrospect we probably should have had three, but
>> whaddyagonnado?) If you find you need help with the tech editing
>> Justin, we'll
>> cross that bridge when we get to it, but for now consider that post to
>> be filled
>> by you.
>>
>> There are three possible classic "animal" books I could do with
>> O'Reilly for
>> Apache Flex -- one is the "Programming Foo" series, the other is the "Foo
>> Cookbook" series, and the third are "Developing Fum Applications for Foo"
>> micro-books. The last book on Flex in the "Programming" series was
>> "Programming
>> Flex 3" by Chafic Kazoun & Joey Lott, so we're due for an update.
>> There is a
>> "Flex 4 Cookbook" and some Flex 4.5 micro-books by Rich Tretola back
>> in 2011,
>> but nothing recent.
>>
>> I think we'll go with a "Programming Apache Flex" book this time, with an
>> emphasis on the Spark portion of the framework, and what's been
>> updated since
>> Adobe Flex 4.6, rather than going over everything, considering the
>> wealth of
>> information already published on Flex 3 and 4. And also because I
>> don't want to
>> embark on another monster book project; we'll keep it at around 400
>> pages, which
>> would be easier to sell to O'Reilly.
>>
>> Doing an "Apache Flex Cookbook" would be a nice second book, but as a
>> collaborative effort, because it would be a bit of a monster to do,
>> considering
>> that the "Flex 4 Cookbook" weighed in at 740 pages. If O'Reilly gets a
>> good ROI
>> (i.e. it breaks even ;) on this first book, they might consider doing the
>> cookbook. But we'll cross that bridge when we get to it.
>>
>> What I will need people's input on, when the book proposal is
>> approved, are
>> general ideas, or rather a wish list of "what you'd like to see in the
>> book",
>> keeping in mind what kind of book this will be.
>>
>>
>> I'll keep everyone updated as I hear from them.
>>
>> _______________________________________________________________________
>>
>> Joseph Balderson, Flex & Flash Platform Developer :: http://joeflash.ca
>> Author, Professional Flex 3 :: http://tinyurl.com/proflex3book
>>
>> Justin Mclean wrote:
>>> Hi,
>>>
>>>> You'll do fine, Justin. As long as you're willing to put in the time
>>>> to read and
>>>> double-read the entire book (usually as it's written chapter by
>>>> chapter)
>>> OK I'm in - but that shouldn't stop other people from wanting to help
>>> out as well.
>>>
>>> Thanks,
>>> Justin
> 
> 

Re: O'Reilly Apache Flex book help

["a00s@a00s.com" <a0...@a00s.com>]

Hi

     Wish list, that I think it is important to those who want to start. 
Just my opinion, things that took me long time to understand, that could 
be very simple and quickly if I could found in one place.

1) How to download Flex. Looks stupid but once you download and install 
you start to wondering. OK now what I do? It was my first reaction when 
moved to apache. It was my first time downloading separately from Adobe 
builder.
2) How to setup Flex with adobe builder
3) How to setup Flex with Intelij
4) Probably the most important in my view: How to connect a flex 
application with a database (maybe how to setup tomcat, blazeds)
5) How to use external resourses with Flex like javascript. To show that 
Flex its not a competitor of other languages but a language to build the 
entire application, doesnt matter if will need to put together 
javascript, applet...
6) Show how to make 3d objects, not sure if the 3rd solution will allow 
this one.
7) How to print. Any business application will need that at some point, 
and many times we need a clear text to print, not a postscript image, 
maybe how to convert in PDF.
8) How to check why your application is crashing the browser and how to 
debug.

thanks for starting this book

Thiago Maia


On 1/22/2014 7:59 PM, Joseph Balderson wrote:
> Thanks Justin.
>
> One rule of thumb for time involved is 1-2 hours per page for authors -- that's
> me -- and 5-10 minutes per page for tech editing -- that's you Justin. Which is
> why, if a book goes past 400 pages, you need more than one author, unless you're
> David Gassner who can crack off a 1000-page Flex Bible book all by himself (god
> only knows how the hell he does it). Given the scope of the book, I'm probably
> looking at 6 months to write, with tech editing as it's written, so there's
> time. Professional Adobe Flex 3 only had two tech editors, and that was a
> 1400-page book (in retrospect we probably should have had three, but
> whaddyagonnado?) If you find you need help with the tech editing Justin, we'll
> cross that bridge when we get to it, but for now consider that post to be filled
> by you.
>
> There are three possible classic "animal" books I could do with O'Reilly for
> Apache Flex -- one is the "Programming Foo" series, the other is the "Foo
> Cookbook" series, and the third are "Developing Fum Applications for Foo"
> micro-books. The last book on Flex in the "Programming" series was "Programming
> Flex 3" by Chafic Kazoun & Joey Lott, so we're due for an update. There is a
> "Flex 4 Cookbook" and some Flex 4.5 micro-books by Rich Tretola back in 2011,
> but nothing recent.
>
> I think we'll go with a "Programming Apache Flex" book this time, with an
> emphasis on the Spark portion of the framework, and what's been updated since
> Adobe Flex 4.6, rather than going over everything, considering the wealth of
> information already published on Flex 3 and 4. And also because I don't want to
> embark on another monster book project; we'll keep it at around 400 pages, which
> would be easier to sell to O'Reilly.
>
> Doing an "Apache Flex Cookbook" would be a nice second book, but as a
> collaborative effort, because it would be a bit of a monster to do, considering
> that the "Flex 4 Cookbook" weighed in at 740 pages. If O'Reilly gets a good ROI
> (i.e. it breaks even ;) on this first book, they might consider doing the
> cookbook. But we'll cross that bridge when we get to it.
>
> What I will need people's input on, when the book proposal is approved, are
> general ideas, or rather a wish list of "what you'd like to see in the book",
> keeping in mind what kind of book this will be.
>
>
> I'll keep everyone updated as I hear from them.
>
> _______________________________________________________________________
>
> Joseph Balderson, Flex & Flash Platform Developer :: http://joeflash.ca
> Author, Professional Flex 3 :: http://tinyurl.com/proflex3book
>
> Justin Mclean wrote:
>> Hi,
>>
>>> You'll do fine, Justin. As long as you're willing to put in the time to read and
>>> double-read the entire book (usually as it's written chapter by chapter)
>> OK I'm in - but that shouldn't stop other people from wanting to help out as well.
>>
>> Thanks,
>> Justin

Re: O'Reilly Apache Flex book help

[Joseph Balderson <ne...@joeflash.ca>]

Thanks Justin.

One rule of thumb for time involved is 1-2 hours per page for authors -- that's
me -- and 5-10 minutes per page for tech editing -- that's you Justin. Which is
why, if a book goes past 400 pages, you need more than one author, unless you're
David Gassner who can crack off a 1000-page Flex Bible book all by himself (god
only knows how the hell he does it). Given the scope of the book, I'm probably
looking at 6 months to write, with tech editing as it's written, so there's
time. Professional Adobe Flex 3 only had two tech editors, and that was a
1400-page book (in retrospect we probably should have had three, but
whaddyagonnado?) If you find you need help with the tech editing Justin, we'll
cross that bridge when we get to it, but for now consider that post to be filled
by you.

There are three possible classic "animal" books I could do with O'Reilly for
Apache Flex -- one is the "Programming Foo" series, the other is the "Foo
Cookbook" series, and the third are "Developing Fum Applications for Foo"
micro-books. The last book on Flex in the "Programming" series was "Programming
Flex 3" by Chafic Kazoun & Joey Lott, so we're due for an update. There is a
"Flex 4 Cookbook" and some Flex 4.5 micro-books by Rich Tretola back in 2011,
but nothing recent.

I think we'll go with a "Programming Apache Flex" book this time, with an
emphasis on the Spark portion of the framework, and what's been updated since
Adobe Flex 4.6, rather than going over everything, considering the wealth of
information already published on Flex 3 and 4. And also because I don't want to
embark on another monster book project; we'll keep it at around 400 pages, which
would be easier to sell to O'Reilly.

Doing an "Apache Flex Cookbook" would be a nice second book, but as a
collaborative effort, because it would be a bit of a monster to do, considering
that the "Flex 4 Cookbook" weighed in at 740 pages. If O'Reilly gets a good ROI
(i.e. it breaks even ;) on this first book, they might consider doing the
cookbook. But we'll cross that bridge when we get to it.

What I will need people's input on, when the book proposal is approved, are
general ideas, or rather a wish list of "what you'd like to see in the book",
keeping in mind what kind of book this will be.


I'll keep everyone updated as I hear from them.

_______________________________________________________________________

Joseph Balderson, Flex & Flash Platform Developer :: http://joeflash.ca
Author, Professional Flex 3 :: http://tinyurl.com/proflex3book

Justin Mclean wrote:
> Hi,
> 
>> You'll do fine, Justin. As long as you're willing to put in the time to read and
>> double-read the entire book (usually as it's written chapter by chapter)
> OK I'm in - but that shouldn't stop other people from wanting to help out as well.
> 
> Thanks,
> Justin

Re: O'Reilly Apache Flex book help

[Justin Mclean <ju...@classsoftware.com>]

Hi,

> You'll do fine, Justin. As long as you're willing to put in the time to read and
> double-read the entire book (usually as it's written chapter by chapter)
OK I'm in - but that shouldn't stop other people from wanting to help out as well.

Thanks,
Justin

Re: O'Reilly Apache Flex book help

[Joseph Balderson <ne...@joeflash.ca>]

You'll do fine, Justin. As long as you're willing to put in the time to read and
double-read the entire book (usually as it's written chapter by chapter), and
you have an eye for technical detail (which I figure you do ;), you don't need
traditional editing experience. I've tech edited several books myself, what's
required is a knowledgeable person who knows the tech looking out for errata
before the book goes to press. All I need to know is if you can spare the time.

Thanks,


_______________________________________________________________________

Joseph Balderson, Flex & Flash Platform Developer :: http://joeflash.ca
Author, Professional Flex 3 :: http://tinyurl.com/proflex3book

Justin Mclean wrote:
> Hi,
> 
>> Note that I'll need an official "tech editor",
> You said you wanted an experienced tech editor - not really sure I qualify. 
> 
> While I know Flex and Apache Flex well and have just finished writing a book myself (so have some familiarity with the process) I've not been a tech editor for a book before.
> 
> Thanks,
> Justin

Re: O'Reilly Apache Flex book help

[Angelo Anolin <an...@gmail.com>]

I'd like to be involved in any way possible.

I've just completed a small end to end business app for a client using flex
and although I admit that I have to dive deeper into Flex, contributing to
the book would facilitate a lot of learning on my part.
On 2014-01-22 7:42 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:

> Hi,
>
> > Note that I'll need an official "tech editor",
> You said you wanted an experienced tech editor - not really sure I qualify.
>
> While I know Flex and Apache Flex well and have just finished writing a
> book myself (so have some familiarity with the process) I've not been a
> tech editor for a book before.
>
> Thanks,
> Justin

Re: O'Reilly Apache Flex book help

[Justin Mclean <ju...@classsoftware.com>]

Hi,

> Note that I'll need an official "tech editor",
You said you wanted an experienced tech editor - not really sure I qualify. 

While I know Flex and Apache Flex well and have just finished writing a book myself (so have some familiarity with the process) I've not been a tech editor for a book before.

Thanks,
Justin

Re: O'Reilly Apache Flex book help

[Joseph Balderson <ne...@joeflash.ca>]

Thanks Justin, you're hired! :) Note that I'll need an official "tech editor",
responsible for tech proofreading the entire book, and you'll get a credit
listing. Are you up for that?


_______________________________________________________________________

Joseph Balderson, Flex & Flash Platform Developer :: http://joeflash.ca
Author, Professional Flex 3 :: http://tinyurl.com/proflex3book

Justin Mclean wrote:
> Hi,
> 
>> And so I need your help, everyone in the Flex community.
> I can certainly review + proofread etc. Also being the release manager for several versions I can help out with what new, what been fixed etc
> 
> Thanks,
> Justin

Re: O'Reilly Apache Flex book help

[Justin Mclean <ju...@classsoftware.com>]

Hi,

> And so I need your help, everyone in the Flex community.
I can certainly review + proofread etc. Also being the release manager for several versions I can help out with what new, what been fixed etc

Thanks,
Justin

Re: O'Reilly Apache Flex book help

[Joseph Balderson <ne...@joeflash.ca>]

It might... I'll mention to O'Reilly that people in the community are willing to
pre-order if that helps the book go forward :)

I'll keep you posted.

_______________________________________________________________________

Joseph Balderson, Flex & Flash Platform Developer :: http://joeflash.ca
Author, Professional Flex 3 :: http://tinyurl.com/proflex3book

Mark Fuqua wrote:
> I'll buy one...would pre orders help?
> 
> Mark
> 
> -----Original Message-----
> From: Joseph Balderson [mailto:news@joeflash.ca] 
> Sent: Wednesday, January 22, 2014 8:43 PM
> To: users@flex.apache.org
> Subject: O'Reilly Apache Flex book help
> 
> Hi all,
> 
> The latest news on the Apache Flex book with O'Reilly is that I'm currently
> in negotiations with them to have this book made, i.e. "Programming Apache
> Flex" as a continuance of that same series. It's taking some convincing to
> be honest, because the perception in the tech publishing industry right now
> is that Flash and Flex books are a lost leader, and more or less a dead
> ecosystem.
> 
> In response I mentioned to them that since Flex is now truly open source
> under Apache, that O'Reilly would be seen to be promoting open source
> software, which is very much within their mandate. And that, of course, Flex
> is not dead; in fact it has every indication of making somewhat of a
> comeback, according to the "word on the street," evidenced by a slow trickle
> of client work back to Flex, supported by AIR winning an award at the 2013
> CES for "Best Consumer Application Development Platform for Mobile" (1,2)
> 
> However, I may be able to convince O'Reilly to go ahead with a digital-only
> version which would minimize their costs. And if they agree to this, I have
> offered to waive any fees or royalties associated with the book on my part,
> to be considered "my donation" to the Apache Flex community. If O'Reilly
> breaks even or even makes a slight profit (and the profit margins on tech
> books are insanely low), then the project will stand a chance of going
> forward, and waiving my fees might just be what tips the balance. And of
> course I mentioned that, wouldn't it be embarrassing when Flex springs back
> in this next year and there are no Flex books with the O'Reilly name on it?
> ;)
> 
> We'll see what happens, if O'Reilly accepts my proposal. I understand how
> perception is in part largely responsible for driving sales of tech books.
> But stakeholders and students are not the only ones who can drive book
> sales: a niche community of developers can also do so.
> 
> And so I need your help, everyone in the Flex community. I'll need an
> experienced tech editor who is willing to help out with this, to donate
> their time to the project. And I will need everyone's help in promoting this
> book when it comes out, and to buy one, so that O'Reilly can justify the ROI
> to go ahead with the project.
> 
> This book will be seen as a huge boon to Apache Flex, to prove to all the
> managers and stakeholders drinking the HTML5 koolaid, that Flex isn't dead,
> and it is very much alive and well.
> 
> Thanks all in advance for your support,
> 
> Joseph
> 
> 
> (1)
> http://www.beedigital.net/2014/01/09/air-wins-award-at-ces-for-the-best-mobi
> le-application-product-in-2014/
> (2)
> http://www.compassintelligence.com/?q=press/compass-intelligence-announces-w
> inners-2014-mobility-awards-wireless-m2m-and-green-technology
> 
> 
> --
> _______________________________________________________________________
> 
> Joseph Balderson, Flex & Flash Platform Developer :: http://joeflash.ca
> Author, Professional Flex 3 :: http://tinyurl.com/proflex3book
> 
> 
> ---
> This email is free from viruses and malware because avast! Antivirus protection is active.
> http://www.avast.com
> 
> 
> 

RE: O'Reilly Apache Flex book help

[Mark Fuqua <ma...@availdata.com>]

I'll buy one...would pre orders help?

Mark

-----Original Message-----
From: Joseph Balderson [mailto:news@joeflash.ca] 
Sent: Wednesday, January 22, 2014 8:43 PM
To: users@flex.apache.org
Subject: O'Reilly Apache Flex book help

Hi all,

The latest news on the Apache Flex book with O'Reilly is that I'm currently
in negotiations with them to have this book made, i.e. "Programming Apache
Flex" as a continuance of that same series. It's taking some convincing to
be honest, because the perception in the tech publishing industry right now
is that Flash and Flex books are a lost leader, and more or less a dead
ecosystem.

In response I mentioned to them that since Flex is now truly open source
under Apache, that O'Reilly would be seen to be promoting open source
software, which is very much within their mandate. And that, of course, Flex
is not dead; in fact it has every indication of making somewhat of a
comeback, according to the "word on the street," evidenced by a slow trickle
of client work back to Flex, supported by AIR winning an award at the 2013
CES for "Best Consumer Application Development Platform for Mobile" (1,2)

However, I may be able to convince O'Reilly to go ahead with a digital-only
version which would minimize their costs. And if they agree to this, I have
offered to waive any fees or royalties associated with the book on my part,
to be considered "my donation" to the Apache Flex community. If O'Reilly
breaks even or even makes a slight profit (and the profit margins on tech
books are insanely low), then the project will stand a chance of going
forward, and waiving my fees might just be what tips the balance. And of
course I mentioned that, wouldn't it be embarrassing when Flex springs back
in this next year and there are no Flex books with the O'Reilly name on it?
;)

We'll see what happens, if O'Reilly accepts my proposal. I understand how
perception is in part largely responsible for driving sales of tech books.
But stakeholders and students are not the only ones who can drive book
sales: a niche community of developers can also do so.

And so I need your help, everyone in the Flex community. I'll need an
experienced tech editor who is willing to help out with this, to donate
their time to the project. And I will need everyone's help in promoting this
book when it comes out, and to buy one, so that O'Reilly can justify the ROI
to go ahead with the project.

This book will be seen as a huge boon to Apache Flex, to prove to all the
managers and stakeholders drinking the HTML5 koolaid, that Flex isn't dead,
and it is very much alive and well.

Thanks all in advance for your support,

Joseph


(1)
http://www.beedigital.net/2014/01/09/air-wins-award-at-ces-for-the-best-mobi
le-application-product-in-2014/
(2)
http://www.compassintelligence.com/?q=press/compass-intelligence-announces-w
inners-2014-mobility-awards-wireless-m2m-and-green-technology


--
_______________________________________________________________________

Joseph Balderson, Flex & Flash Platform Developer :: http://joeflash.ca
Author, Professional Flex 3 :: http://tinyurl.com/proflex3book


---
This email is free from viruses and malware because avast! Antivirus protection is active.
http://www.avast.com