I think "Express" isn't a bad name for this. It implies that you can get
something running quickly.
Another name I thought of was "Star" (FlexJS Star).
A third choice might be "Prime", meaning the main one to use.
‹peter
On 1/3/17, 12:14 PM, "Dev LFM" wrote:
>I've been listening this thread,
t; I like Express too!
>>
>> - Josh
>>
>> On Jan 3, 2017 10:31 AM, "Peter Ent" wrote:
>>
>> > I think "Express" isn't a bad name for this. It implies that you can
>>get
>> > something running quickly.
>>
to a single file.
Regards,
Peter Ent
Adobe Systems/Apache Flex Project
I've given this some thought and I've come up with an idea:
Create a new DataGridView that creates the pieces. Use a horizontal
Container for the column headers, placing buttons in them and then have
the DataGrid's controller (your own version) listen for clicks on those
buttons. That will signal
Oops. First time in awhile I forgot those. Will take care of it shortly.
Peter
On Jan 9, 2017, at 5:49 PM, OmPrakash Muppirala wrote:
>>
>> http://git-wip-us.apache.org/repos/asf/flex-asjs/blob/
>> d1b6c5d2/frameworks/projects/Express/src/main/flex/org/
>> apache/flex/express/List.as
>> ---
Thanks. Should have been more careful.
Much appreciated.
Peter
On 1/10/17, 3:27 AM, "omup...@gmail.com on behalf of OmPrakash Muppirala"
wrote:
>I was having build issues, so I fixed it.
>
>Thanks,
>Om
>
>On Mon, Jan 9, 2017 at 4:42 PM, Peter Ent wrote:
>
similar. I think keeping
the project separate from the FlexJS SDK would allow it to be released on its
own schedule and not tie up the FlexJS release with more issues.
Let me know what you think. Alex has suggested using the ASDoc example as the
starting point.
Regards,
Peter Ent
Adobe Systems/Apache Flex Project
if you set numeric="true" it will add the numeric
input filter bead from the accessories pack.
Regards,
Peter Ent
Adobe Systems/Apache Flex Project
On 1/11/17, 4:00 AM, "sankar" wrote:
>Hi,
>
>Is there any existing bead available to restrict text input to TextInput
>
Question in-line below.
Thanks,
Peter
On 1/11/17, 4:43 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
wrote:
>Hi Alex,
>
>I think many people in this thread are saying "No, we'll not go to
>production without AMF and basic module support". IMHO, it would be very
>difficult to say we h
lose the opportunity to propose FlexJS for that migrations
>(projects)
>we are loosing a great portfolio of projects that could trust in FlexJS as
>its next technology.
>
>
>
>2017-01-11 14:22 GMT+01:00 Peter Ent :
>
>>
>> Are people in your company already using
her than trying to disable pointer events.
What do you thing? I would also like to move this bead into the accessories
package rather than the main bead list.
Regards,
Peter Ent
Adobe Systems/Apache Flex Project
On the SWF side, the TextInput is actually a flash.display.TextField and
it is that thing that needs to be disabled, not the UIBase element
($displayObject). The FlexJS TextInput, on the SWF side, has a
TextInputView which creates the TextField that's used for the actual
input. So the DisableBead n
rce files for
presentation and, optionally, a loadable live example.
Do you think there is any reason to have a SWF version or should it just
be JS?
Regards,
Peter
On 1/11/17, 6:03 AM, "Kessler CTR Mark J"
wrote:
>+1
>
>-Mark
>
>-Original Message-
>From: Peter Ent [ma
The repo has been created. I added a small file to make it official.
https://git-wip-us.apache.org/repos/asf/flex-tourjs.git
On 1/12/17, 9:18 AM, "Peter Ent" wrote:
>I've put the request in for the flex-tourjs repo; should have that today.
>I honestly do not know how the
I was speaking to a friend that has some JavaScript developers working for
him. They use React and React/Native for their mobile apps. His feeling is
that web-centric apps (e.g. Amazon.com) are going to be replaced with
mobile apps since mobile devices are cheaper than laptops. They are
concentrati
See in-line.
‹peter
On 1/13/17, 1:35 PM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
wrote:
>Hi Peter,
>
>2017-01-13 19:22 GMT+01:00 Peter Ent :
>
>> I was speaking to a friend that has some JavaScript developers working
>>for
>> him. They use
See comment in-line.
‹peter
On 1/17/17, 9:11 AM, "yishayw" wrote:
>Kessler CTR Mark J wrote
>> the ability to compile it using our existing spark based projects
>>without
>> having to having to create hundreds of JS beads / customizations.
>> Understandably heavier, but compatibility is more imp
I've pushed an initial project to the flex-tourjs repo. I did a couple of
prototypes and I like this one best. It is of course, a work in progress.
Basically, the TourJS directory holds the source to the project and the
configuration file in its resources directory. This configuration file is a
oo committed to this.
Let me know what you think.
Regards,
Peter Ent
Adobe Systems/Apache Flex Project
On 1/20/17, 5:26 AM, "piotrz" wrote:
>Alex,
>
>I'll start work from adding Maven pom to build.:)
>
>Piotr
>
>
>
>-
>Apache Flex PMC
>pio
This sounds good. We will need to run a build at the top-level in
flex-tourjs so that it builds all of the examples which have the same
structure.
—peter
On 1/20/17, 9:17 AM, "piotrz" wrote:
>Thanks Peter for concept.
>
>Let's say that I have this structure for "alert":
>
> alert/
>bin/ ‹ the j
It is on the develop branch.
‹peter
On 1/24/17, 2:52 AM, "piotrz" wrote:
>Peter,
>
>I just commited first pom version to tourjs repository. I'm wondering why
>I
>don't see in github [1] our commits ? Do you know ?
>
>[1] https://github.com/apache/flex-tourjs
>
>Piotr
>
>
>
>
>
>-
>Apache Fl
I assume Trevor is looking for a consensus on which style of button to use
which would then lead to styles for checkboxes, sliders, etc.
My preference is the flat buttons: the second row.
How would the over, down, emphasized, focused, and disabled states for
those buttons look?
Thanks for doing
I've just pushed an initial examples directory with ANT build scripts. I'm
not 100% sure this is the best structure, but I think it could work.
The examples/build.xml only builds the examples, it does not yet copy them
into the TourJS resources folder.
On a side-note, I had to clean up some FlexJ
he.org/repos/asf/flex-asjs/commit/b22fcdba
>> Tree: http://git-wip-us.apache.org/repos/asf/flex-asjs/tree/b22fcdba
>> Diff: http://git-wip-us.apache.org/repos/asf/flex-asjs/diff/b22fcdba
>>
>> Branch: refs/heads/develop
>> Commit: b22fcdbafb21ec56588f2d04567703eb1d6a1b
Of course the moment I tell you I can't find the problem, I find it. Way
down at the bottom of the list of staged files was the defaults.css that I
didn't commit and push. My apologies.
‹peter
On 1/24/17, 4:21 PM, "piotrz" wrote:
>That's another component (ToggleTextButton) where model is in us
ersion of the TourJS
that I'm looking into now.
Regards,
Peter Ent
Adobe Systems/Apache Flex Project
I have not looked at the change yet, but the mouse events should be handled in
the controller for radio button. The idea is that a controller (mouse, touch,
keyboard) intercepts the "raw" event and dispatches a universal event (change).
This way you just switch the controller bead based on the d
On 1/31/17, 9:03 AM, "Peter Ent" wrote:
>I have not looked at the change yet, but the mouse events should be
>handled in the controller for radio button. The idea is that a controller
>(mouse, touch, keyboard) intercepts the "raw" event and dispatches a
>univer
The MDL radio button is composed as:
Label You See
The first click event has target=, currentTarget= while the
second click event has target=, currentTarget=. The click is
being dispatched from the input Radio (or Check) and from the label that's
identifying it.
In Dat
I need to look into this more. My memory isn't what it used to be, so I do
not recall how this was taking place in CreateJS (React is a very
different thing), but that was also before the refactor wrapping Sprite.
The FlexJS/HTML/RadioButton JS code has no explicit event listener
attached to it. T
y more problems then replacing them. And if they are
replaced, I think we need an event ("beadsRemoved") be sent so that any
beads which might be active and consuming resources can close down
properly.
Peter Ent
Adobe Systems/Apache Flex Project
On 2/1/17, 10:56 AM, "Alex Harui&q
ibuting to what's being seen.
—peter
On 2/1/17, 11:33 AM, "Alex Harui" wrote:
>Do we have a really simple test case so we don't have to wade through the
>MDLExample?
>
>-Alex
>
>On 2/1/17, 6:16 AM, "Peter Ent" wrote:
>
>>I need to look
I should have responded sooner. This is fine. I can work with it.
‹peter
On 2/1/17, 1:57 PM, "piotrz" wrote:
>Alex,
>
>You need to go to the MDL RadioButton and comment line where we are adding
>event listener for click - It should be enough.
>
>Let me know.
>
>Piotr
>
>
>
>-
>Apache Flex PM
The event being received by the MDL RadioButton looks to me like a real
browser event; not a google'd event, not a FlexJS event, but a real
browser event. And there are two of them coming in, one with target
and the other with target . My guess is that MDL additional
material.min.js must be adding
JS/bin/js-release or
TourJS/bin-debug version. Each has a few quirks/bugs to work out, but in
general the Alert and Button examples will run (note: the SWF version does not
run the ImageButton example yet).
Regards,
Peter Ent
Adobe Systems/Apache Flex Project
You guys have done a great job. The MDLExample is very impressive.
‹peter
On 2/3/17, 5:52 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
wrote:
>Hi,
>
>just let you know that I think we have done with MDL feature set.
>
>So all components in MDL website are implemented and working. I
Do you think we should make more use of the MVC pattern in the component
architecture? We have hard-coded these components to listen for "click"
events.
Isn't MDL the theme used on both browsers and Android apps? I might have
that confused, not being an Android user. But at some point touch events
I've renamed "Module" class to "SubAppLoader" since it is really just
loading one app into an another and not really what you'd expect "Module"
to do.
The flexes-tour has also been updated to reflect that change.
‹peter
On 2/2/17, 5:05 PM, "Peter En
How about giving the Express package a whirl. Try the VView component
which packages up the vertical layout with data binding.
‹peter
On 2/7/17, 8:56 AM, "Harbs" wrote:
>Same here.
>
>This is the HTML that it outputs (and they are stacked on top of each
>other):
>
>
>
> new
all a discussion about this months ago. Does anyone mind if I go ahead and
make this change tomorrow (24 hours from now)?
Thanks,
Peter Ent
Adobe Systems/Apache Flex Project
I forgot about ImageAndTextButton. That uses "image" to specify the
location. So there's yet another property.
‹peter
On 2/8/17, 1:23 PM, "Peter Ent" wrote:
>Hi,
>
>I'm working the TourJS and needed to make some changes to ImageButton. I
>see that Ima
017, at 8:25 PM, Peter Ent wrote:
>>
>> I forgot about ImageAndTextButton. That uses "image" to specify the
>> location. So there's yet another property.
>>
>> ‹peter
>>
>> On 2/8/17, 1:23 PM, "Peter Ent" wrote:
>>
>&
src is used on the HTML img tag. The same can be done
>in
>CSS where you need to use url.
>
>In our world, I prefer src as people might be more familiar with that.
>
>Thanks,
>Om
>
>On Wed, Feb 8, 2017 at 11:48 AM, Peter Ent wrote:
>
>> Would you prefer it to be
Yeah!
Thanks so much.
‹peter
On 2/8/17, 6:07 PM, "piotrz" wrote:
>Hi Peter,
>
>I just add to poms ability to copying built resources require in
>content.json to TourJS content folder. All examples were working once I
>run
>my Maven build. :)
>
>Piotr
>
>
>
>-
>Apache Flex PMC
>piotrzarzyck.
trol.
I did not touch the ImageAndTextButton control since the "image" property made
sense for this control.
I have also updated the examples to reflect these changes. I did not change any
of the models, although one or two interfaces in Core were changed.
Regards,
Peter Ent
Adobe Systems/Apache Flex Project
.
Peter Ent
Adobe Systems/Apache Flex Project
On 2/12/17, 6:07 AM, "Harbs" wrote:
>Documentation is the key. I don¹t know what to say, but we need a
>solution to that problem.
>
>The current BasicLayout seems to be pretty inefficient as-is for HTML
>layout. It currently
I'm going to try to incorporate this discussion into the Express package;
seems like a great candidate for inclusion there.
Peter Ent
Adobe Systems/Apache Flex Project
On 2/14/17, 12:54 AM, "Alex Harui" wrote:
>
>
>On 2/13/17, 9:40 PM, "Justin Mclean" wro
You can use CSS Flexbox[1] on the JS side to handle these situations. I'm
thinking about making a layout that makes it possible to specify Flexbox
and have some/all of it work on the SWF side as well.
Its a bit of work but I think it will be worth it. If anyone is interested
in helping, let me kno
I had to figure it out as well and looked at FlexJSStore. You use
to add this to a component, like a Container:
Then you use the id to change it: borderStyles.backgroundColor = "#CC";
I can't get it to work, though.
I'm not sure what the "Bindable" part is yet. Doing
background
When you change one of the properties of BindableCSSStyles it dispatches a
valueChange event. You need to make a bead, like SolidBackgroundBead
(which is SWF only) listen for this event and then redraw itself using the
new style(s) that were changed. I am hoping that the JS side "just works"
but I
cussed upthread. I think a call to applyStyles
>is needed, especially on the JS side and on the SWF side the
>BackgroundBead needs to be notified.
>
>-Alex
>
>On 2/14/17, 1:31 PM, "Peter Ent" wrote:
>
>>I had to figure i
ents to
use this new bead as its background and try to make it much easier and
less verbose to use from the Express package.
—peter
On 2/14/17, 5:05 PM, "Peter Ent" wrote:
>Yes, writing a special bead for detecting changes to the styles and
>applying them does work. I have a So
Don’t bother using this code. I spoke with Alex at length about this and
I'm going to try a different way.
—peter
On 2/15/17, 11:25 AM, "Peter Ent" wrote:
>Hi,
>I just pushed a new bead to the HTML project:
>SolidBackgroundWithChangeListenerBead. It is designed to work
This is what I have at the moment:
SolidBackgroundWithChangeListenerBead (extends SolidBackgroundBead) grabs
the style from its strand and sets up a listener for ValueChangeEvent. If
the style dispatches it, SBWCLB then invokes its super class's methods,
setupStyles and handleChange (both of which
for the border styles and then roll it into the Express
package Container element.
—peter
On 2/15/17, 2:48 PM, "Peter Ent" wrote:
>This is what I have at the moment:
>
>SolidBackgroundWithChangeListenerBead (extends SolidBackgroundBead) grabs
>the style from its strand and
I'll try and look into this next.
‹peter
On 2/16/17, 5:40 PM, "Justin Mclean" wrote:
>Hi,
>
>Anyone have thought on this?
>
>It looks to be a serious bug to me and there¹s no workaround except in
>the simplest cases.
>
>One alternative is to wrap a component in 4 boxes to simulate the padding
>b
A lot of this work is mine and it seems to need to be thought through once
again. The dichotomy of SWF & JS has presented problems for me in the past.
Maybe the layouts, for JS platform, should do as little as possible,
replying on CSS as much as possible. Then make the SWF platform mimic that.
O
e have circle-layout, we should have a "circleLayout" css class
>selector, that we could assign to out flexjs "list component"
>
>2.- in SWF -> we should stick with the way this was done in Flex4 but
>implementing as a bead and with the "updateDisplayList" per
,top,bottom properties to do proper constrained
>layout. I think that constrained layout (right,left,top,bottom) is common
>enough that it doesn’t warrant a separate layout as long as we have the
>bare-bones CSSLayout for cases that need it.
>
>> For sure, we need to the the JS sid
Alex will need to chime in here, but I believe his philosophy has been to
keep the number of specialized events to a minimum. I'm not 100% sure I
agree with that since it can be a lot easier to write code when you are
responding to specific events, but it does expand the final footprint of
the app
I'll be including the issues of spacing and positioning in my work with
layouts.
‹peter
On 2/21/17, 5:56 AM, "yishayw" wrote:
>That sounds like a good idea. Let me know if I can help.
>
>
>
>--
>View this message in context:
>http://apache-flex-development.247.n4.nabble.com/FlexJS-Spacers-a
olyfill that could do the job for not supported browsers for now. At the
>end browsers will support it, and polyfill will end in no use (and we
>could
>eventually remove)
>
>2017-02-22 14:47 GMT+01:00 Peter Ent :
>
>> I'm going to try some experiments in my own space. Basica
hanks!
>
>2017-02-22 16:53 GMT+01:00 Peter Ent :
>
>> That's a good strategy. My experiments this morning look like Flexbox is
>> the way to go. Its widely supported now and seems pretty easy to use.
>>
>> I'm going to create VerticalFlexLayout and Horizon
.
Percentage sizing for the children works, too, although the Flexbox will
override them if it feels it must. Personally, I think it does a great job
of presenting the information.
On 2/22/17, 8:55 AM, "Peter Ent" wrote:
>I'll be including the issues of spacing and positioni
otally agree with this.
>>>
>>> There should be a simple Container (with H and V variants) and a
>>>separate
>>> ChromeContainer. The vast majority of Containers do not need the extra
>>>div.
>>>
>>> Moving Panel to Express is an option,
t looks like Flexbox is not supported at all in IE prior to IE10 and
>>>even in IE10 and 11, it only has buggy support.[1]
>>>
>>> [1]http://caniuse.com/#feat=flexbox <http://caniuse.com/#feat=flexbox>
>>>
>>>> On Feb 22, 2017, at 11:40 PM, Peter Ent
Not sure yet but I will look into it tomorrow.
Peter
> On Feb 22, 2017, at 5:45 PM, Justin Mclean wrote:
>
> Hi,
>
> Anyone have any ideas here?
>
> Thanks,
> Justin
k at the generated HTML, there's way too much forcing
of size and position that a natural HTML author would not use. But I'm not
sure how to really do this programmatically while allowing all sorts of
situations to work.
>
>My 2 cents,
>-Alex
>
>On 2/22/17, 2:31 PM, &q
Easy enough to add
for JS of course.
—peter
On 2/23/17, 8:25 AM, "Peter Ent" wrote:
>
>
>On 2/23/17, 1:54 AM, "Alex Harui" wrote:
>
>>A few comments/questions:
>>
>>What does flex-box do when it runs out of room? Doesn't it wrap to a new
>
Maybe we need a big refactor. Things like effects are pretty advanced and maybe
they should get coupled with more advanced/complex layouts that are in a
different package than HTML.
The basic packages could be simpler layouts that do minimal settings. The HTML
package could be JS only and just
Hi,
I've been wrestling with Container all day. I was working on the Flex layouts,
but then went down the rabbit hole of Containers while trying to get the
layouts to look right.
The issue really isn't the HTML/JS side. That's pretty easy really (in
concept). A FlexJS Container's element is a
t would return 10 due to the
padding on its Container parent.
Right now Container has this inner contentArea that tries to make sure
testButton is (0,0) but it is a headache to maintain, I think.
[1] https://paste.apache.org/IM1W
Regards,
Peter Ent
Adobe Systems/Apache Flex Project
I believe at this point, Container and perhaps the layouts need a
re-write. These are fundamental to FlexJS and must be correct. FlexJS is
trying to bridge two worlds with different ideas about coordinate systems
and it is behaving erratically at times, like this.
I think the solution is more comp
x27;t this what localToGlobal etc.. did for Flex?
>
>Personally I would like testButton.x to return 0 in all instances. Unless
>I
>want it's actual screen position where I use the helper functions like
>localToGlobal etc..
>
>On Tue, Feb 28, 2017 at 8:50 PM, Peter Ent wrote:
>
&g
es where that¹s important (which I think is a lot more rare than is
>currently assumed).
>
>My $0.02.
>Harbs
>
>> On Mar 1, 2017, at 3:56 PM, Peter Ent wrote:
>>
>> I think we have confusion over what FlexJS is trying to deliver. If we
>>are
>> trying to make
fsetX.
>
>For the Flex-like components in Basic, we could make everything always use
>absolute positioning. And Container would have a more Flex-like
>coordinate space. Don't know if that would help or not.
>
>Thoughts?
>-Alex
>
>On 3/1/17, 7:28 AM, "Peter Ent&
We still have to have FlexJS work on both JS and SWF sides with some
compatibility. We could do this:
x,y sets "native" values. Reading them back on SWF vs JS might yield
different results if padding, border, and margins are set on the parent
element. If you don't want your coordinates messed with
ve our
layout issues once complete.
Regards,
Peter
On 3/2/17, 9:37 AM, "Peter Ent" wrote:
>We still have to have FlexJS work on both JS and SWF sides with some
>compatibility. We could do this:
>
>x,y sets "native" values. Reading them back on SWF vs JS might yiel
the examples) to be based on Group rather than Container which will also
eliminate another layer.
Please give Group a test if you can.
Thanks.
Peter Ent
Adobe Systems/Apache Flex Project
.org/repos/asf/flex-asjs/commit/79d45cba
>> Tree: http://git-wip-us.apache.org/repos/asf/flex-asjs/tree/79d45cba
>> Diff: http://git-wip-us.apache.org/repos/asf/flex-asjs/diff/79d45cba
>>
>> Branch: refs/heads/develop
>> Commit: 79d45cba0616e394fddb68835859b1ffc87e6c48
>&g
This is the theory, yes. A way to do your own thing using AS and MXML to
construct the app which then generates the right amount of HTML structure,
making it easier to style. Or use pre-built constructions and layouts as
templates that also generate the right amount of HTML structure.
I'm thinking
r
>effort of create a good layout strategy, but an important previous step if
>we want to implement theming in FlexJS.
>
>Great! :D
>
>Carlos
>
>
>2017-03-07 14:23 GMT+01:00 Peter Ent :
>
>> This is the theory, yes. A way to do your own thing using AS and MXML to
&
nents implementing IChrome interface) or should it just be for
scrollable content?
Thanks,
Peter
On 3/7/17, 10:31 AM, "Peter Ent" wrote:
>Thanks for the feedback!
>
>As I go through the examples, I see that we (mostly me) created a number
>of nested elements, such as a for an it
ernative, Panel can be re-constructed to look as it does now without
the use of chrome simply by using Group for the Panel itself and Group for the
TitleBar and ControlBar and a Container with a ScrollingViewport for the
content.
Please let me know your thoughts.
Thanks,
Peter Ent
Adobe Systems/Apache Flex Project
The idea of "chrome" is that these are components that do not count as
regular children and have special locations within the component. The
TitleBar and ControlBar are considered chrome because if you ask for the
children of the Panel, they are not listed and if you have so many
children in the Pa
The way things are set up right now, due to the nesting of containers (div
or DisplayObjectContainer), you do get (0,0) at the top. It will usually
be necessary to have nested containers for scrolling purposes if nothing
else.
As I'm going through the code, I don't see that IChrome is actually bei
concerns or questions, please let me know.
Regards,
Peter Ent
Adobe Systems/Apache Flex Project.
Thanks for letting me know. I will try to be quick.
‹peter
On 3/16/17, 4:11 AM, "Justin Mclean" wrote:
>Hi,
>
>The current changes have broken the layout in our application (not
>unexpected). When you feel it at a stable state just say so and we set if
>we can fix it up and report back any issu
I just saw this - sorry for the delay.
I'm working on changing the structure of the container classes which also
affects list and therefore DataGrid. Once I have things stable and checked
in I'll look at the bugs and see if they are resolved and if not, start
addressing them.
Regards,
Hi,
I've fixed a number of layout issues. I'm still putting things together
and testing, but this problem should be addressed in my next commit.
‹peter
On 3/20/17, 3:26 AM, "yishayw" wrote:
>I think some of your changes in BasicLayout have broken some layout
>behavior
>on the JS side. In this
Hi,
I'm am making progress toward simplifying the JS output generated from the
components. I should be making a commit either tomorrow or the next day. There
will be some things not working 100% correctly, mostly because they need to be
tuned to use the new layouts or are making assumptions abo
Hi,
One more thing: When I make this commit, I'm pretty sure Charts will be
broken until I address it. I can hold off the commit and address Charts
first, but I would prefer to commit Core and HTML and then fix Charts and
anything else.
Would that strategy (commit first, fix Charts etc after) im
I just re-sync'd myself since I am planning to merge my code and I'm
having the same issue. I did try maven and that does build, so that's
good. But the ant build should work, too.
Thanks,
Peter
On 3/22/17, 10:34 AM, "Christofer Dutz" wrote:
>Hi Sankar,
>
>Have you tried building with Maven? Th
Hi,
I have some before and after code to show you. I sent it out earlier but since
I didn't see it come back into my inbox I'll assume the HTML I put into it
didn't pass the filters, so I've put the code into a paste[1] below.
I ran an example of the following MXML snippet. It is a series of n
Hi, I have some before and after code to show you. I don't know if the HTML
will come through and if it does not I'll put it into an Apache paste.
I ran an example of the following MXML snippet. It is a series of nested
Containers with different layouts.
This is what the HTM
Update: I'm 99% ready to commit. I will do this tomorrow morning, my time.
I've spent today fixing some last issues in HTML package, while cosmetic,
just didn't make things look too good. There are a couple more but I'll do
them later.
I did a local merge of the latest FlexJS code and my changes a
know what breaks. I will tell you that the
biggest difference is the UIBase no longer sets position style so any
elements you have that require positioning via x,y, will need to use a
Group or Container that has the BasicLayout.
Regards,
Peter
On 3/22/17, 5:02 PM, "Peter Ent" wrote:
>U
I guess I should have used a feature branch. I'm not sure how long Charts
will take. I wrote most of that code and it got pretty gnarly using List
as a basis. It probably is better to use a feature branch. Let me see if I
understand the rollback process and can get that going. Definitely a
lesson l
sition
on all of the layouts, but the common ones have tested correctly.
Regards,
Peter Ent
Adobe Systems/Apache Flex Project
Yes, Chris does have a good point and from now on* I will definitely use
feature branches. I thought I could squeeze this through.
I checked in changes to Chart that should make it compile. I doubt it will
run, but that is on the list. I will look into MDL now. That will take
longer.
I am leary a
101 - 200 of 662 matches
Mail list logo
