>From folks who have been in the ipmc longer and advise on whether this is a
>category x dependency.
Sent via the PANTECH Discover, an AT&T 4G LTE smartphone.
Justin Mclean wrote:
Hi,
> Do you think we need confirmation before proceeding?
Confirmation of exactly what and from who?
Justin
Hi,
> Do you think we need confirmation before proceeding?
Confirmation of exactly what and from who?
Justin
Yes, please a separate repo. 'flex-radii8' sound appropriate ;-)
EdB
On Fri, Aug 29, 2014 at 8:08 PM, Alex Harui wrote:
> So, we are all set to commit to Git. I was just going to put it in
> flex-utilities or flex-external, but in light of the merge issues found
> after TDF, should we just a
So, we are all set to commit to Git. I was just going to put it in
flex-utilities or flex-external, but in light of the merge issues found
after TDF, should we just ask for a repo for it? Is flex-radii8 ok with
folks?
Thanks,
-Alex
Welcome Darkstone.
-Message d'origine-
De : Justin Mclean [mailto:jus...@classsoftware.com]
Envoyé : mercredi 13 août 2014 02:15
À : dev@flex.apache.org
Objet : Please welcome Darkstone as an Apache Flex committer
Hi,
Sorry for being a little late in announcing this.
I am pleased to an
Welcome on board, Chris.
-Message d'origine-
De : Jose Barragan [mailto:jose.barra...@codeoscopic.com]
Envoyé : dimanche 17 août 2014 13:02
À : dev@flex.apache.org
Objet : Re: Please welcome Chris Martin as an Apache Flex committer
Welcome!! :)
__
Jose Barragan
Senio
+1
-Message d'origine-
De : Chris Martin [mailto:windo...@gmail.com]
Envoyé : mardi 19 août 2014 18:03
À : dev@flex.apache.org
Objet : Re: [POLL] Accept Radii8 Code Donation
+1
On Mon, Aug 18, 2014 at 11:36 PM, Frédéric THOMAS
wrote:
>
>
>
> And that's a +1 indeed
>
> Frédéric THOMAS
Hey Curtis,
First off, thanks for contributing a Spark RichTextEditor component. I'm
sure others will find it useful as well, and the process you went through
(filing a JIRA [1], submitting patches, tweaking the code) will serve as a
good example for others who are wondering how to contribute to
Hi,
Is there any guide or tutorial for adding a patch to JIRA? As I see this is
not completed:
https://cwiki.apache.org/confluence/display/FLEX/7.2+Adding+patch+to+JIRA+issue
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/Adding-patch-to-JIRA-issue-guide-t
That was exactly what I was looking for ... thanks :-)
Von: Justin Mclean
Gesendet: Freitag, 29. August 2014 16:16
An: dev@flex.apache.org
Betreff: Re: [DISCUSSION] Squiggly 1.0 release candidate 0
Hi,
> we have 7 swcs and I bet there are dependencies.
Do you think we need confirmation before proceeding? I think we should.
Practically speaking, how many folks will be able to use the release
without downloading a category X file?
For fonts, you can definitely use Flex without having to download a
category X font.
-Alex
On 8/29/14 7:21 AM, "Jus
Hi,
> Doesn't that create a dependency on category x?
Don't think so, it's more a dependency on a file format not a specific bit of
software, basically the same as a font file. eg Flex (and users of flex) can
use lots of different fonts, but we could only bundled a small subset of fonts
that a
Hi,
> we have 7 swcs and I bet there are dependencies.
Some of the swcs are dependent on the others.
ApacheFlexLinguisticUtils.swc
ApacheflexSpellingEngine.swc
ApacheFlexSpellingFramework.swc -> ApacheFlexLinguisticUtils.swc +
ApacheflexSpellingEngine.swc
ApacheFlexSpellingUI.swc -> ApacheFlexL
Hi,
> Hunspell format which is the same format as MySpell which is based on
> Ispell.
And I should of said Ispell is ancient [1] - " Ispell has a very long history
that can be traced back to a program that was originally written in 1971 in
PDP-10 Assembly language". That predates my program
Well in that case ... we have 7 swcs and I bet there are dependencies. So
either I simply generate one squiggly artifact, that depends on all of these 7
swcs or I am able to do this a little more fine-grained ... so if I only want
the spelling engine, what parts do I need. I would assume the pro
Hi,
> To use Squiggly, is the Hunspell dictionaries included at compile time or is
> it downloaded at runtime (or something else)?
Hunspell is not actually required at all, a dictionary may be required (if
specified) and that dictionary is in Hunspell format which is the same format
as MySpell
Hi,
> Could someone here quickly write down how the squiggly artifacts depend on
> each other and extenal dependencies?
Basically there are no complication dependancies other than you need the Flex
SDK (ie mxml and asdoc) to compile it. The ANE not in this release would
require air.
Justin
On 28/08/14 18:53, chayankhoidream wrote:
> Adobe/Apache Flex tech is slowly being flushed down into the toilet because
> some programmers helping build the framework didn't know what they were
> doing
As one of the people who helped build that framework, even before the
SDK was open sourced to Apa
Yup. Pixel perfect text layout is the kicker.
There’s currently three approaches to this problem that I know of:
1) Google Docs separates words (and sometimes letters) into separate divs and
places each div separately. Selection rectangles and cursors are separate divs
that are imposed over the
To use Squiggly, is the Hunspell dictionaries included at compile time or is it
downloaded at runtime (or something else)?
On Aug 29, 2014, at 1:24 AM, Justin Mclean wrote:
>> I am wondering how Hunspell is integrated here? Was it a port from C++ to
>> AS3?
>
> I'm not 100% sure but from what
Could someone here quickly write down how the squiggly artifacts depend on each
other and extenal dependencies? This would speed up my task greatly and I could
concentrate on the targets themselves.
Chris
Von: Christofer Dutz
Gesendet: Freitag, 29. Aug
Hi,
> just one thing ... while starting to work on a general maven release feature
> to our ant builds, I noticed that we don't actually have a consistent way of
> defining the version of a library.
All of the source and binary releases have a version number in the artifact
name, internally mo
?Hi guys,
just one thing ... while starting to work on a general maven release feature to
our ant builds, I noticed that we don't actually have a consistent way of
defining the version of a library. Usually we simply produce some artifact
without a version number. I would like to at least incl
I think I'll whip up something in my +1 day today.
Well usually you deploy the jar/swc/rsl whatever and if you're really nice you
bundle the source zipped up in a jar together with the binary to allow IDEs to
show the code.
Well the minimum requirement to such a pom would be minimal, but it sems
24 matches
Mail list logo
