[
https://issues.apache.org/jira/browse/FLEX-33427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13606157#comment-13606157
]
Mikko Torniainen commented on FLEX-33427:
-
it's fi_FI not fi_FL
>
I'm pretty sure that the docs here are wrong:
https://flex.apache.org/asdoc/flashx/textLayout/elements/TextFlow.html
It says: A TextFlow object can have ParagraphElement and DivElement objects as
children.
If I'm not mistaken, a TextFlow can have a ListElement as a child as well, so
that should
> Also, I'd think that flow.getElementsByTypeName("ParagraphElement") should
> return an array of the ParagraphElements in the flow. This does not seem to
> work. It retruns an empty array in my tests. Am I going about it wrong, or is
> this a bug?
Okay. This was my error. This: flow.getElemen
I think it would be interesting if the DateField were combined with
"MaskedTextInput" component. By MaskedTextInput I mean a TextInput that has
a text mask (e.g. dd/mm/ for a date) in which the user can type his
values (numeric only in case of DateField) without using the mouse. In a
DateField
@Nicholas ...
*> Dosen't FXG also support bitmaps, effects, and other things as well?
[...] *
*> Would those elements be able to be supported with SVG? (I really am
asking*
*> on that one. The last time I dealt with SVG was in 2002 for a mapping
application).
*
SVG 1.1 document [1] recommends the
same problem here, and there's nowhere a way to register or login as a
guest... :(
On 19 March 2013 07:22, Erik de Bruin wrote:
> The link ends on a login page… But I can't log in with my regular Adobe
> login. What to do?
>
>
> EdB
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3
[
https://issues.apache.org/jira/browse/FLEX-33427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13606202#comment-13606202
]
spiros aggelopoulos commented on FLEX-33427:
greek or el_GR translation
inval
Anyone who has problem with watching the Apache Flex Update Meeting, here is a
workaround that I found:
01. Open this url in your browser
https://experts.adobeconnect.com/randori_does_apache/
02. Choose "Enter as a Guest", type your name and press "Enter Room" button
03. Wait until Adobe Connec
Sorry, my initial question wasn't answered yet ...
Does anyone know where I can download the FXG Extension for
Photoshop CS5 (or later) that is mentioned here [1]? The Flash
Catalyst site [2] does not provide this link anymore. Did anyone
have downloaded it in the past and can share the link with
Hi,
> you are the right person for doing the next one
Be better if we had a few people that are comfortable doing a release.
> and I want to help you, like that we can prepare the ground for others.
> Is that this is possible?
Possible. I will help out where I can but I may not have a large amou
HI,
> I think the docs should be clearer on what to specify here. I propose the
> following:
>
> Instead of: Returns all elements that have typeName set to typeNameValue.
>
> Returns all elements that have typeName as the TextFlow markup tag set to
> typeNameValue.
The docs are generate from
[
https://issues.apache.org/jira/browse/FLEX-33427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Mclean updated FLEX-33427:
-
Description:
Missing translation of error messages for the postcode componets.
In English they
[
https://issues.apache.org/jira/browse/FLEX-33427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Mclean updated FLEX-33427:
-
Description:
Missing translation of error messages for the postcode componets.
In English they
[
https://issues.apache.org/jira/browse/FLEX-33427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13606282#comment-13606282
]
Justin Mclean commented on FLEX-33427:
--
Fixed fi_FI and added el_GR. Added to git dev
[
https://issues.apache.org/jira/browse/FLEX-33190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13606283#comment-13606283
]
Justin Mclean commented on FLEX-33190:
--
Applied patch. Run mustella datagrid test bef
[
https://issues.apache.org/jira/browse/FLEX-33190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Mclean resolved FLEX-33190.
--
Resolution: Fixed
> GridEvent.GRID_DOUBLE_CLICK is dispatched even when two different cells
[
https://issues.apache.org/jira/browse/FLEX-33248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13606290#comment-13606290
]
Trevor North commented on FLEX-33248:
-
Unfortunately this issue is still not fully res
Hi,
As I was watching the datagrid tests I noticed that one of the early tests had
some broken images in it - looks to be an error to me. Can someone more
familiar with the tests take a look at this.
Thanks,
Justin
Hi,
Very odd as I've made no changes to README - any idea what''s happen here?
Justin
On 19/03/2013, at 11:37 PM, jmcl...@apache.org wrote:
> Updated Branches:
> refs/heads/develop b5fce9368 -> 4f6c47d2e
>
>
> Merge branch 'develop' of https://git-wip-us.apache.org/repos/asf/flex-sdk
> into
yeah, you shoud run this[1] once to allow automatic rebasing on merge which
I referenced here [2] as Suggested pratices, that what I was talking about
yesterday about messing the history.
-Fred
[1] git config --global branch.autosetuprebase always
[2] http://flex.apache.org/dev-sourcecode.html
I wanted to send you a pic of the history but I can't, instead you can run
[1]
-Fred
[1] git log --graph --oneline --all
-Message d'origine-
From: Frédéric THOMAS
Sent: Tuesday, March 19, 2013 2:06 PM
To: dev@flex.apache.org
Subject: Re: [3/3] git commit: Merge branch 'develop' of
h
Hi Alex,
I'd try to new zip (19-Mar-2013).
New version of FlexOverLay.zip contains SimpleCSSValuesImpl.js!
So I can compile the swf & js version of FlexJSTestAgainApp on Flash
Builder without error.
I feel so happy!
thanks.
--
Jun Funakura
2013/3/16 Alex Harui :
> Hi Jun,
>
> Yes, I saw there
HI,
> yeah, you shoud run this[1] once to allow automatic rebasing on merge which I
> referenced here [2] as Suggested pratices, that what I was talking about
> yesterday about messing the history.
There's nothing about this here:
https://git-wip-us.apache.org
And if it causes issue why isn't
HI,
> [1] git log --graph --oneline --all
Which produces nothing that's meaningful to IMO. ie README isn't mentioned.
* 4f6c47d Merge branch 'develop' of
https://git-wip-us.apache.org/repos/asf/flex-sdk into develop
|\
| * b5fce93 FLEX-33435 added more details
| * 9c7c97e Updated for the Sv
That's there [1], it's not the git default because in git we're soppose to
work on branches for features and "more than one commit" bug fixes, then
merge without rebasing allows the history to keep track of this set of
changes, it creates a merge commit.
What you did is only do few commits as
Hi,
> it's not the git default because in git we're soppose to work on branches for
> features and "more than one commit" bug fixes,
All my bug fixes were a single commit. Are we really support to make a branch
for that then merge the branch and then commit for a changing in a single file?
AFAI
Hi,
> If you look at the history, you can see that your commits has been placed
> before mines even though I pushed before and the first line is the merge
> commit, the reason why it touched the README I committed.
I guess the question is is README in a correct state or not? And if it didn't
m
Harbs created FLEX-33436:
Summary: Improved descriptons in TextFlow class
Key: FLEX-33436
URL: https://issues.apache.org/jira/browse/FLEX-33436
Project: Apache Flex
Issue Type: Documentation
Affe
[
https://issues.apache.org/jira/browse/FLEX-33436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harbs updated FLEX-33436:
-
Priority: Minor (was: Major)
> Improved descriptons in TextFlow class
>
[
https://issues.apache.org/jira/browse/FLEX-33436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harbs updated FLEX-33436:
-
Attachment: TextFlow.diff
Patch attached
> Improved descriptons in TextFlow class
>
Okay. Done.
On Mar 19, 2013, at 1:51 PM, Justin Mclean wrote:
> HI,
>
>> I think the docs should be clearer on what to specify here. I propose the
>> following:
>>
>> Instead of: Returns all elements that have typeName set to typeNameValue.
>>
>> Returns all elements that have typeName as the
[
https://issues.apache.org/jira/browse/FLEX-33436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harbs updated FLEX-33436:
-
Summary: Improved descriptions in TextFlow class (was: Improved
descriptons in TextFlow class)
> Improved d
[
https://issues.apache.org/jira/browse/FLEX-33248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Mclean reopened FLEX-33248:
--
> Spark GridItemEditor cannot edit nested properties
>
All my bug fixes were a single commit. Are we really support to make a
branch for that then merge the branch and then commit for a changing in a
single file?
If I where you, I would create a branch named for a such hudge
bugfix, do all my commits relative to this bugfix to it, even push the
That's correspond to the 2 commits modifications I did on this file.
-Fred
-Message d'origine-
From: Justin Mclean
Sent: Tuesday, March 19, 2013 3:05 PM
To: dev@flex.apache.org
Subject: Re: [3/3] git commit: Merge branch 'develop' of
https://git-wip-us.apache.org/repos/asf/flex-sdk in
Hi,
> Yes, look at [1] and see hotfixes.
Hotfixes apply to the release branch not the develop branch.
> And you should have done a git pull -rebase instead, because they will forget
> to do so, it is better to instruct git to automaticly rebase on pull (the
> command I gave you in the previous
Hotfixes apply to the release branch not the develop branch.
Oh, true but features and bugfixes are treated in the same way anyway except
if the all bugfix is 1 or 2 little commits, in this last case, rebasing is
the rule.
From my understanding a rebase can mess up history. Do we really want
The --rebase option can be used to ensure a linear history by preventing
unnecessary merge commits. Many developers prefer rebasing over merging,
since it’s like saying, “I want to put my changes on top of what everybody
else has done.” In this sense, using git pull with the --rebase flag is eve
Hi,
> NO, that's the opposite
Really?
https://wincent.com/wiki/git_rebase:_you're_doing_it_wrong
Dozen of stack overflow question on the issue which warn about rebasing. For
instance:
http://stackoverflow.com/questions/8939977/git-push-rejected-after-feature-branch-rebase
"Rebase and a shared
The first link says exactly what I'm saying, you want to put your changes on
top of what everybody else has done.
'So "git rebase" is not wrong. But it's right only if it's YOUR VERY OWN
PRIVATE git tree.'
When you do a pull --rebase, you're rebasing only your commits on the top of
the other
But to be short and resume what those links means:
You rebase your own commits, git pull --rebase (internaly: git fetch/ git
rebase) because you stay on your own branch
you git pull (internaly: git fetch / git merge) from another branch your
feature/bugfix branch you just completely coded.
[
https://issues.apache.org/jira/browse/FLEX-33398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13606449#comment-13606449
]
Vladimir Cicmanec commented on FLEX-33398:
--
Not a bug, the component behaves corr
[
https://issues.apache.org/jira/browse/FLEX-33398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13606449#comment-13606449
]
Vladimir Cicmanec edited comment on FLEX-33398 at 3/19/13 4:16 PM:
-
And now it's really time to explain this to - or rather: prescribe this for -
us mere mortals. I think a couple of simple use cases with the exact
steps/commands on the wiki (checkout, commit, push, pull) should be an
excellent start.
Time for some of the other very vocal git proponents to step
Hi Erik,
I added a comment to the wiki with a link which to git basics explanations
but must be read and understood by all new git user IMO, once those basics
clear, which cover all what every boby asks at the moment, I might go
further writing someting on the wiki but before that I don't want
On 3/19/13 6:22 AM, "jun funakura" wrote:
> Hi Alex,
>
> I'd try to new zip (19-Mar-2013).
> New version of FlexOverLay.zip contains SimpleCSSValuesImpl.js!
> So I can compile the swf & js version of FlexJSTestAgainApp on Flash
> Builder without error.
>
> I feel so happy!
> thanks.
>
> --
Spark or MX?
On 3/19/13 5:48 AM, "Justin Mclean" wrote:
> Hi,
>
> As I was watching the datagrid tests I noticed that one of the early tests had
> some broken images in it - looks to be an error to me. Can someone more
> familiar with the tests take a look at this.
>
> Thanks,
> Justin
--
When exactly it will take place
On Mar 19, 2013 2:28 AM, "JP Bader" wrote:
> For anyone interested in watching/participating in tonight's talk about
> Apache Flex from Nick Kwiatkowski (@quetwo), or Randori and it's exciting
> new announcement from Michael Labriola (@labriola) please sign in here
It was last night.
On Tue, Mar 19, 2013 at 12:13 PM, Saleh Abdulawal wrote:
> When exactly it will take place
> On Mar 19, 2013 2:28 AM, "JP Bader" wrote:
>
> > For anyone interested in watching/participating in tonight's talk about
> > Apache Flex from Nick Kwiatkowski (@quetwo), or Randori and
I'm just hoping for mostly agreed upon way of doing business... So if I was
starting from scratch to create a patch for a JIRA issue I would then do
something like...
1) Clone Flex-SDK; the whole thing (creates local from remote apache servers)
2) Checkout the develop branch from the new loc
Fred,
Don't get me wrong, I really appreciate your tireless efforts of the last few
weeks! I was specifically addressing - as of now unnamed - 'others' with this
request. What I'm hoping to see is more task-based and Flex/Apache/NVIE
oriented step-by-steps. All the tutorials and most comments b
This is the best explanation of when to merge vs. rebase that I've seen:
http://blog.sourcetreeapp.com/2012/08/21/merge-or-rebase/
There's also now a public beta of SourceTree for Windows available:
http://blog.sourcetreeapp.com/2013/03/19/introducing-sourcetree-for-windows-a-free-desktop-client-f
Hi,
This document is perfect, the maybe only little point it didn't cover in
"Keeping the feature branch up to date" is the possibility interactively
rebase your commit, which allows in case of too much conflicts, to abord it,
reset --hard and pull (fecth/merge).
Thanks for sharing,
-Fred
-
This is the best explanation of when to merge vs. rebase that I've seen:
http://blog.sourcetreeapp.com/2012/08/21/merge-or-rebase/
Added as comment to the wiki
-Fred
-Message d'origine-
From: Frédéric THOMAS
Sent: Tuesday, March 19, 2013 7:23 PM
To: dev@flex.apache.org
Subject: Re: [3
Not sure I understand the question, (and please use us...@flex.apache.org
for SDK usage questions as opposed to SDK development questions), but I
generally have a separate container and widgets that I use for print preview
instead of trying to re-use the interactive container and widgets.
On 3/19
can you provide me any example..
On Wed, Mar 20, 2013 at 12:14 AM, Alex Harui wrote:
> Not sure I understand the question, (and please use us...@flex.apache.org
> for SDK usage questions as opposed to SDK development questions), but I
> generally have a separate container and widgets that I use
Moving thread to us...@flex.apache.org. Madhusudan, you need to be
subscribed to that list to see further replies in this thread.
Thanks,
Om
On Tue, Mar 19, 2013 at 11:46 AM, Madhu Dutta wrote:
> can you provide me any example..
>
> On Wed, Mar 20, 2013 at 12:14 AM, Alex Harui wrote:
>
> > Not
On 3/19/13 11:46 AM, "Madhu Dutta" wrote:
> can you provide me any example..
I don't have one handy, but if I had:
Then the print review might look like:
If both views are bound to the same data model, then the print preview is
automatically updated.
>
> On Wed, Ma
Alex,
Please re-post your reply on the users list.
Thanks,
Om
On Tue, Mar 19, 2013 at 11:51 AM, Alex Harui wrote:
>
>
>
> On 3/19/13 11:46 AM, "Madhu Dutta" wrote:
>
> > can you provide me any example..
> I don't have one handy, but if I had:
>
>
> change="model.country=countryCB.s
Back on topic: Can we get flex-asjs open for r/w?
On 3/19/13 12:33 AM, "Justin Mclean" wrote:
> Hi,
>
>> you are the right person for doing the next one
> Be better if we had a few people that are comfortable doing a release.
>
>> and I want to help you, like that we can prepare the ground fo
ok.. thanks..
On Wed, Mar 20, 2013 at 12:21 AM, Alex Harui wrote:
>
>
>
> On 3/19/13 11:46 AM, "Madhu Dutta" wrote:
>
> > can you provide me any example..
> I don't have one handy, but if I had:
>
>
> change="model.country=countryCB.selectedItem"/>
>
>
> Then the print review might
Here's one way to avoid having "git pull" create a merge commit on your develop
branch. Checkout your develop branch and then run:
$ git pull --ff-only
If this give you an error it means you have commits on your develop branch that
are ahead of the remote develop branch. So then, run:
$ git r
I find it "interesting" that you apparently can't use Git well without
appending all sorts of obscure switches such as --ff-only, --preserve-merges,
and --rebase to your commands.
- Gordon
-Original Message-
From: Dasa Paddock [mailto:dpadd...@esri.com]
Sent: Tuesday, March 19, 2013 12
On Tue, Mar 19, 2013 at 1:35 PM, Gordon Smith wrote:
> I find it "interesting" that you apparently can't use Git well without
> appending all sorts of obscure switches such as --ff-only,
> --preserve-merges, and --rebase to your commands.
>
> - Gordon
>
Which is why I use GUI tool. Most stuff c
It partly depends our your personal workflow and the tools that you use. For
example, I work in feature branches and I don't leave un-pushed commits sitting
on my develop branch for long. I also use the SourceTree app which is doing a
fetch on the remote automatically every 10 minutes and shows
Hi,
> Spark or MX?
./mini_run.sh components/DataGrid
Justin
Hi,
> I find it "interesting" that you apparently can't use Git well without
> appending all sorts of obscure switches such as --ff-only, --preserve-merges,
> and --rebase to your commands.
And everyone seems to have a slightly different opinion on which one to use :-)
If you don;t use the com
Hi,
> What I'm hoping to see is more task-based and Flex/Apache/NVIE oriented
> step-by-steps.
+100 to this.
Justin
I'm having a hard time with the fact that, although Git branches are cheap and
fast, you can work on only one of them at a time. In Subversion, of course,
they're just different directories and you can have editable files for multiple
branches simultaneously.
So suppose I'm editing files on one
I used a test git repo to experiment with different scenarios by first going
through this tutorial:
http://try.github.com
You could of course skip the tutorial and just create a test git repo directly
at github.com
--Dasa
On Mar 19, 2013, at 2:30 PM, Justin Mclean wrote:
> If you don;t use t
Hi,
Interesting discussion re rebase here:
http://notes.envato.com/developers/rebasing-merge-commits-in-git/
Down in the comments teh author states:
"The moral is: it doesn’t need to be used, but it’s not a horrible thing when
used correctly.
Just don’t teach it to fledgeling svn -> git users. T
You could use the stash command:
http://git-scm.com/book/en/Git-Tools-Stashing
http://git-scm.com/docs/git-stash
--Dasa
On Mar 19, 2013, at 3:25 PM, Gordon Smith
wrote:
> I'm having a hard time with the fact that, although Git branches are cheap
> and fast, you can work on only one of them a
Is that what you do?
- Gordon
-Original Message-
From: Dasa Paddock [mailto:dpadd...@esri.com]
Sent: Tuesday, March 19, 2013 3:38 PM
To:
Subject: Re: Git's "branches are cheap and fast but modal" model
You could use the stash command:
http://git-scm.com/book/en/Git-Tools-Stashing
http
When you work on a branch, and you want to work on another branch, you
first have to commit in the current branch you working on to save your work.
Then, you git checkout the branch you want to work on, and so on...
Cheers !
2013/3/19 Gordon Smith
> Is that what you do?
>
> - Gordon
>
> -
I stash if I want a clean working directory, but I use the SourceTree GUI since
it also has a nice diff view builtin.
--Dasa
On Mar 19, 2013, at 3:41 PM, Gordon Smith wrote:
> Is that what you do?
>
> - Gordon
>
> -Original Message-
> From: Dasa Paddock [mailto:dpadd...@esri.com]
>
That seems silly. I wouldn't want to commit if the code is in some bad state.
What would I put for the commit message... "Oops, gotta go."?
- Gordon
-Original Message-
From: Sylvain Lecoy [mailto:sylvain.le...@gmail.com]
Sent: Tuesday, March 19, 2013 3:57 PM
To: dev@flex.apache.org
Subj
Ha,
I just had this same scenario today and was talking to Roland about it.
I'm learning the darker recesses if GIT now to Gordon since I am
working with more people. Its really easy when the team is not
complicated.
I asked this exact same question, "Why would I commit, if I'm not
ready
Hi,
> I used a test git repo to experiment with different scenarios by first going
> through this tutorial:
> http://try.github.com
>
> You could of course skip the tutorial and just create a test git repo
> directly at github.com
I think most of us are aware and can use the basic git commands
Hi,
> When you work on a branch, and you want to work on another branch, you first
> have to commit in the current branch you working on to save your work.
Git checkout branch is not quite the same as switching branches in SVN. If
there is no conflicting changes all of your current changes will
My initial impression is that Git is designed to make complicated team
workflows possible rather than simple team workflows easy. The fact that nobody
agrees on how to do things is indicative that it is overly complex.
I've read the chapter of the Git book about how it just stores files, trees,
> If there is no conflicting changes all of your current changes will be kept
> but you'll now be working in the new branch.
That's exactly the problem, because this is hardly ever what I want. The
solution seems to be to commit prematurely, or stash into a stack where you
lose track which bra
The stash name includes the branch it came from.
On Mar 19, 2013, at 4:20 PM, Gordon Smith
wrote:
>> If there is no conflicting changes all of your current changes will be kept
>> but you'll now be working in the new branch.
>
> That's exactly the problem, because this is hardly ever what I
True,
I'm no fan boy Gordon... I have read many times this has been the
problem with GIT for years is that it was created be developers for
developers. They add things in the core that make sense to them or as
an after thought no thinking of the implications of what they are doing.
So yes
Of course, as the page says, the most current version of this primer course
has been moved here: http://git-scm.com/course/svn.html Please use this
link instead.
Thanks,
Om
On Tue, Mar 19, 2013 at 4:33 PM, Om wrote:
> Here is an excellent primer comparing the commands available in Git for
> t
Hi,
> Of course, as the page says, the most current version of this primer course
> has been moved here: http://git-scm.com/course/svn.html Please use this
> link instead.
A nice primer but it lacks context for our project and has nothing about all
the options Git people are saying we need to
In discussing 'git add', 'git rm', and 'git mv', this document says "So, just
like in SVN, you need to tell Git when you add, move or remove any files." It
makes it sound like these work the same way in Git and in SVN.
In fact, don't I have to use 'git add' after I have simply edited an existing
I'll take a shot at these :)
On Mar 19, 2013, at 4:04 PM, Justin Mclean wrote:
> Hi,
>
>> I used a test git repo to experiment with different scenarios by first going
>> through this tutorial:
>> http://try.github.com
>>
>> You could of course skip the tutorial and just create a test git repo
Hi,
It would be great to have docs along the line of this for our project:
http://git-scm.com/docs/everyday
Describing what commands users, committers and release managers need to be
aware of and use in real situations.
A rough outline (and we should know most of the answers here).
Users
1. H
+1
For Users and Committers, we also need
1.5 How do I update my project to have the latest changes that committers have
made?
- Gordon
-Original Message-
From: Justin Mclean [mailto:jus...@classsoftware.com]
Sent: Tuesday, March 19, 2013 5:15 PM
To: dev@flex.apache.org
Subject: Re: G
Hi,
> [DP] - I think you did a pull and had local commits on your develop branch
> and there were commits on the remote so it had to create a merge commit on
> your develop branch to bring them together. This could have been avoided
> using git pull --rebase or see my earlier email.
Understand
I've looked on the apache flex web site yesterday and the source code was
available only for svn, did they change the repository to git recently? Its
just for curiosity, I don't know if I was crazy :)
On Tue, Mar 19, 2013 at 5:06 PM, Gordon Smith wrote:
> In discussing 'git add', 'git rm', and 'git mv', this document says "So,
> just like in SVN, you need to tell Git when you add, move or remove any
> files." It makes it sound like these work the same way in Git and in SVN.
In fact, don't I
There are 5 ways listed here to specify the contents of a commit:
http://git-scm.com/docs/git-commit
Options 3 and 4 do not use the index/stage:
• by listing files as arguments to the commit command, in which case
the commit will ignore changes staged in the index, and instead record the
Hi,
> I've looked on the apache flex web site yesterday and the source code was
> available only for svn, did they change the repository to git recently?
We're still in the process of moving to git and not everything is read/write
yet. Currently the github mirrors are broken.
The Apache Flex SD
Yes. That's why this list currently has lots of discussions about Git.
- Gordon
-Original Message-
From: Eliezer Reis [mailto:eliezerr...@gmail.com]
Sent: Tuesday, March 19, 2013 5:26 PM
To: dev@flex.apache.org
Subject: Now source code is available on git?
I've looked on the apache flex
Option 1 for specifying what to commit is
> by using git add to incrementally "add" changes to the index before using
the commit command (Note: even modified files must be "added");
Every tutorial I read used the 'add'-after-editing-before-committing approach.
Even more "interesting", if I u
Jude,
Sorry for the late response. I am still in the middle of trying out
certain things to first of all, convince myself that this approach is
viable. Responses inline on to thoughts:
On Sun, Mar 17, 2013 at 2:26 PM, jude wrote:
> Om,
>
> There's FXG and SVG but there's also HTML5 canvas el
Eugene Walden created FLEX-33437:
Summary: Embed image with compression=true causes artifacts around
transparent edges (like a halo)
Key: FLEX-33437
URL: https://issues.apache.org/jira/browse/FLEX-33437
Hi,
I have added two more design tools to our
"Designer & Developer Tools" wiki page [1] ...
1) Adobe Illustrator CS5.5 & CS6
* Save Artboard to FXG file
2) Radiate - Flex Designer GUI (Thanks to ... @jude)
* About Radiate, http://www.radii8.com/blog/?page_id=2
* Radiate Demo, http://www.r
Hmm.
I had a bunch of outstanding SVN changes that got locked out during the
migration. I was able to copy them over to the git repo and make a series
of commits. It was much like SVN. "add" new files. "commit" with
messages. "diff" was a bit tricker but I got it to work. I'll definitely
hav
1 - 100 of 116 matches
Mail list logo
