Re: [royale-asjs] branch develop updated: join all emphasis button styles in one single property and its constants, and update all examples accordingly

I like “emphasis”. Nice. > On Jun 14, 2018, at 4:17 PM, carlosrov...@apache.org wrote: > > This is an automated email from the ASF dual-hosted git repository. > > carlosrovira pushed a commit to branch develop > in repository https://gitbox.apache.org/repos/asf/royale-asjs.git > > > The

Problem with "this" inside static method

.loca.struct.process = __localFn0__; What is the purpose of pulling the inline function out? Harbs

Re: Problem with "this" inside static method

remained the global this in the static function. I’m really not sure why passing in this does not work on static functions. I was surprised myself. FWIW, I rewrote the code to avoid using “this”, but it’s probably not a bad idea to fix this if possible… Harbs > On Jun 18, 2018, at 7:0

Re: [royale-asjs] branch develop updated: Fixes #258. But is that a proper fix?

> On Jun 8, 2018, at 1:11 AM, Alex Harui wrote: > >In your animation code example, having the offsetParent code in the setter > makes the animation *way* less efficient. There is a an extra forced reflow > for every assignment of the new value. > > I don't understand this point. Can you

Re: [royale-asjs] branch develop updated: Fixes #258. But is that a proper fix?

rd Hello is actually 10,10 rather than 30,30, but the *logical* placement of it is 30,30. The reason is because the x and y values have no effect. To make the visual placement match the logical placement, the position of “child” needs to be changed to relative. Harbs > On Jun 8, 2018, at 1:

Re: [royale-asjs] branch develop updated: Fixes #258. But is that a proper fix?

not sure what the specificity is on that. Harbs > On Jun 11, 2018, at 10:11 AM, Alex Harui wrote: > > The emulation Application is based on Container and thus creates a Div. It > may not stay that way, but we did it so that the SystemManager can parent the > app like it does in

Re: [royale-asjs] branch develop updated: Fixes #258. But is that a proper fix?

try to raise only essential issues > > > > 2018-06-11 9:36 GMT+02:00 Harbs : > >> We could always have a bead which sets: >> >> .foo *{ >> position: static; >> } >> To reset the defaults of all elements below “foo” to static. >> >&g

Re: [royale-asjs] branch develop updated: fix latest commit, since binary data to string method was not really working

conversions should be handled using utility functions if needed. There are ways to get cross-browser support similar to TextEncoder, but it’s not very PAYG either.[1] My $0.02, Harbs [1]https://stackoverflow.com/questions/6965107/converting-between-strings-and-arraybuffers <ht

Re: [royale-asjs] branch develop updated: Fixes #258. But is that a proper fix?

The problem is that the child does not have a way of knowing what the extra space surrounding the parent (such as padding) will be. One day, I’m probably going to work on a constrained layout… > On Jun 11, 2018, at 1:20 PM, Yishay Weiss wrote: > > I guess we’re a bit prejudiced coming from

Re: [royale-asjs] branch develop updated: fix latest commit, since binary data to string method was not really working

ve the same in all that class, but wasn't aware of that problem. > So I'll change to what we had, and make to String do the same. I think it > should work the same and as well work on IE/Edge > > I'll take a look right now > > 2018-06-11 11:13 GMT+02:00 Harbs <mailto:harbs.li...@gmai

Re: [royale-asjs] branch develop updated: Fixes #258. But is that a proper fix?

ote: > > So yeah, % works differently in Royale compared to Flex for some layouts, but > may not for other layouts. It is ok if Harbs app couldn't use some of our > Basic layouts without adding calc(). If other sites can go to production > without using calc() then our simplest la

Re: BinaryData and odd bytes

DataView works in IE10+. The problem with DataView as that it’s slow. > On Jun 19, 2018, at 9:24 PM, Carlos Rovira wrote: > > Hi Harbs, > > for me any improvement seems ok, just ensure it works in all browsers > (specially IE11) > > thanks > > 2018-06

Re: BinaryData and odd bytes

> On 6/19/18, 10:07 AM, "Harbs" wrote: > >BinaryData uses TypedArrays to read data. It seems that if the ArrayBuffer > does not divide evenly into the target TypedArray, you get a runtime error. > >For example: > >readShort() works like this: >

Re: Migrating Enterprise Flex Application

ng minified issues is difficult. 2. I’ve found some difficulty with layout situations that was easier in Flex. Of course, these problems are no better using other JS frameworks — probably worse. I have other smaller applications developed with Royale as well. I don’t regret going this path a

BinaryData and odd bytes

number), this causes a RTE. readInt() has a similar problem that _position needs to be divisible by 4, etc. Am I correct that Flash’s ByteArray works correctly in this situation? We can use DataViews to solve the problem or we can read the bytes directly. Thanks, Harbs

Re: [Discussion] Package change names (was Re: 0.9.3 Release)

from this discussion feeling like we're making the right decisions. Are we on the same page here? I think this is important. Thanks, Harbs > On May 30, 2018, at 5:17 PM, Carlos Rovira wrote: > > I think so... but hope this resolves soon, I think this discussions should > be more

Re: [Discussion] Package change names (was Re: 0.9.3 Release)

a concrete negative effect on an app, I agree that it would be a problem, but I think we’ve determined that to not be the case. Thanks, Harbs

Re: Type Selector Approximation (was Re: [DISCUSS] Explanation of the changes)

which acts as a compiler directive to specify exactly what to output. If you have another suggestion on how we can achieve that goal, that’s fine too. Makes sense? Harbs > On May 31, 2018, at 12:30 AM, Alex Harui wrote: > > There has always been an option to keep/strip metadata in t

Re: [Discussion] Package change names (was Re: 0.9.3 Release)

I’m planning on working on this. I think it’s very solvable. > On May 31, 2018, at 9:02 AM, Carlos Rovira wrote: > >> >> I believe we still need a volunteer to change the royale-asjs code to >> eliminate use of class selectors in its defaults.css files. >> > > I think this should be done by

Re: [Discussion] Package change names (was Re: 0.9.3 Release)

ms or less, I don’t think it’s worth worrying about. Thanks, Harbs > On May 31, 2018, at 9:02 AM, Carlos Rovira wrote: > >> I see a claim that there is a problem because of the compiler parsing a >> CSS file from a SWC where that CSS will not be used. Is there proof that >

Re: Type Selector Approximation (was Re: [DISCUSS] Explanation of the changes)

would be great > improvement > > I think Alex is thinking in some kind of metadata at runtime, but I > understand this is not the case. > > thanks > > 2018-05-31 8:58 GMT+02:00 Harbs <mailto:harbs.li...@gmail.com>>: > >> I’m not talking about solving

Re: [Discussion] Package change names (was Re: 0.9.3 Release)

? Harbs > On May 31, 2018, at 12:12 PM, Carlos Rovira wrote: > > Hi Harbs, > > concreting more over if Jewel should or not extend Basic TLCs. That I think > is the real point now to discuss. I'm sure it should not be the case. To > sum to all that I exposed, it was not clea

Re: [royale-asjs] branch feature/revert-refactor updated: Item Renderer firing itemChanged when mouse is dragged over item renderer and released

This change looks correct to me and fixed the bug as I observed it. Any idea why was mouse up used instead of click in the first place? I assume the same fix should be applied to the swf block? Harbs > On May 27, 2018, at 2:24 PM, ha...@apache.org wrote: > > This is an automated e

Re: [royale-asjs] branch feature/revert-refactor updated: Item Renderer firing itemChanged when mouse is dragged over item renderer and released

anything wrong with that, > although it looks like your fix is good. I hope to check it once all stuff > back to normal in develop. > > Thanks, > Piotr > > 2018-05-27 13:26 GMT+02:00 Harbs <harbs.li...@gmail.com>: > >> This change looks correct to me and fixed the bug as I

Re: [Discussion] Package change names (was Re: 0.9.3 Release)

at your main point comes back to CSS. If we can’t fix the bugs related to the CSS, then I completely agree with you. We can’t have Basic CSS causing lots of classes and CSS to be included in apps for no good reason. However, I think those bugs are very fixable. I’d also like to comment

Re: [Discussion] Package change names (was Re: 0.9.3 Release)

o you agree as well? (I would be willing to help out with a rename, but I want to make sure it doesn't cause too much disruption. Thanks, Harbs > On May 23, 2018, at 12:43 AM, Alex Harui wrote: > > Hi Carlos, > > I guess I don't understand why separating beads from TLCs is better.

Re: Type Selector Approximation (was Re: [DISCUSS] Explanation of the changes)

could somehow strip out the bracket metadata, I prefer that. Using metadata would allow different component sets to make their own decisions. Thanks, Harbs > On May 21, 2018, at 7:41 PM, Alex Harui wrote: > > I think we are in agreement. My most recent posts were intended to show t

Re: [Discussion] Summarizing all discussion about Royale organization and structure

> On May 29, 2018, at 4:48 PM, Olaf Krueger wrote: > > Hi Carlos, > > thanks for summarizing all this stuff. > > @all > I have not followed all the discussions, but I would like to ask if that > what Carlos has presented is consensual. Foundation Is what Carlos is proposing as a new way of

Re: Royale - BlazeDS working

Very impressive! Great work! :-) Harbs > On May 31, 2018, at 9:51 PM, Carlos Rovira wrote: > > Forgot to share the info in Github page :) > > https://github.com/apache/royale-asjs/wiki/Apache-Royale-communication-with-AMF-and-RemoteObject > > <https://github.com

Last class selectors

The only class selectors left in Basic defaults.css is: .Application *, .royale *, . royale *:before, . royale *:after { -moz-box-sizing: border-box; -webkit-box-sizing: border-box; box-sizing: border-box; } I’m not sure how to best get rid of this. Thoughts? Harbs

Re: [royale-asjs] branch develop updated: Removed unselectable selector

It does add the style to the class list. The only question is how to add the selector to the CSS. Thanks, Harbs > On Jun 4, 2018, at 10:24 AM, Carlos Rovira wrote: > > Hi, > > I think as Alex that better way for this is the bead add the css style to > classList. > >

Incorrect descendent CSS output

; height: 16px; } I think this is a bug. Harbs

Re: [royale-asjs] branch develop updated: Added utility function to dynamically add CSS selectors

M, Carlos Rovira wrote: > > Great! This seems to be very useful! > > thanks! :) > > 2018-06-04 10:22 GMT+02:00 : > >> This is an automated email from the ASF dual-hosted git repository. >> >> harbs pushed a commit to branch develop >> in reposito

Re: [royale-asjs] branch develop updated: Added utility function to dynamically add CSS selectors

to clear out your local cache. HTH, Harbs > On Jun 4, 2018, at 12:30 PM, Carlos Rovira wrote: > > ok, but then don't understand that we have code that is not usable by our > own. > I think if that code can't be used, it should be as well in Royale-extras > libs, so people wan

Re: [royale-asjs] branch develop updated: remove invalid "; utf8" in all inlined svg images

; } The same for secondary, strokes, etc. It might even make sense to specify classes for primary and secondary colors and background colors, etc. Doing so, might make it easier to swap color schemes. It’ll probably also result in simpler CSS. Just a thought, :-) Harbs > On Jun 4, 2018, at 1

Re: [royale-asjs] branch develop updated: Removed unselectable selector

with the UnselectableBead and could apply CSS properties. That would free the user from having to know which selectors are used. Harbs > On Jun 4, 2018, at 7:24 PM, Alex Harui wrote: > > I think it is too early Monday for me. I don't understand what you mean by > "styling could also be a bead&q

Re: [royale-asjs] branch develop updated: Fixes #258. But is that a proper fix?

No. It’s one css selector in the CSS. No inline styles. > On Jun 4, 2018, at 11:38 PM, Piotr Zarzycki wrote: > > Doing that does this mean that we are getting back to the previous state, > where we have had position=relative everywhere ? > > pon., 4 cze 2018 o 22

Re: [royale-asjs] branch develop updated: Fixes #258. But is that a proper fix?

Sorry I was a bit confused. The selector that works is: .Application * { position: relative; } > On Jun 4, 2018, at 11:32 PM, Harbs wrote: > > Yes. But it cascades down. > > I manually made this change to the TreeExample project, and it fixed the bug. > >> On

Re: Descendent selector issue

now whether those are omitted. My point is that if the ancestor is not used, the selector is not needed in the app and it should be omitted. Hope that’s clearer… ;-) Harbs > On Jun 1, 2018, at 11:51 AM, Idylog - Nicolas Granon > wrote: > > May I remind that the space betwee

Descendent selector issue

-color: #d8d8d8; border: 1px solid #808080; padding: 4px; } does get omitted if ToggleTextButton is not used. Is it correct to assume that this is a bug and if the parent/ancestor the selector is not used, the CSS should be omitted? Harbs

Re: [Discussion] Package change names (was Re: 0.9.3 Release)

during compilation is an issue and try and figure out our options if it is. 6. If we can’t make all the pieces of Basic truly optional, I’ll help you pull the Basic TLCs and CSS out into a separate project. Would this be acceptable? Thanks, Harbs > On Jun 1, 2018, at 11:25 AM, Carlos Rov

Re: [Discussion] Package change names (was Re: 0.9.3 Release)

nly can be making just what I can avoid. What problems do you envision that are stopping the 0.9.3 release? Can we get things working for the release and then take it from there? I’m working on getting rid of all the class selectors which are bringing Basic pieces into Jewel. Please give me a chance to finish this work. Thanks, Harbs

Re: Descendent selector issue

ke we are replacing other > class selectors with subclasses, the same should be done for whatever is > being assigned the className TitleBarTitle. > > HTH, > -Alex > > On 6/1/18, 2:09 AM, "Harbs" wrote: > >Of course. That was the distinction I was making. Sorry for

Re: [Discussion] Package change names (was Re: 0.9.3 Release)

list of files at the moment, but a sampling of the files that you view as “bad dependencies” would make it much clearer for me (and others). If you prefer, I could compose a list of files myself, but I’d like to hear from you what you think. Thanks, Harbs > On Jun 1, 2018, at 5:55 PM, Car

Re: [royale-asjs] 01/02: global point should ignore window scrolling

hould probably clean out the “offset” code. Harbs [1]https://caniuse.com/#search=getBoundingClientRect <https://caniuse.com/#search=getBoundingClientRect> > On Jun 1, 2018, at 7:22 PM, Alex Harui wrote: > > For PAYG, should we have a version of the API that worries about window

Re: [royale-asjs] branch develop updated: Removed unselectable selector

What I really wanted to do here was create some self invoking code which was run when the UnselectableElementBead class was loaded. Is there any way of doing that without writing a static method and invoking that? Thanks, Harbs > On Jun 2, 2018, at 11:39 PM, ha...@apache.org wr

Re: [royale-asjs] branch develop updated: Fixes #258. But is that a proper fix?

? > > -Alex > > On 6/4/18, 1:56 PM, "Harbs" wrote: > >Sorry I was a bit confused. The selector that works is: > >.Application * { > position: relative; >} > >> On Jun 4, 2018, at 11:32 PM, Harbs wrote: >>

Re: Incorrect descendent CSS output

gn: left;*/ border-radius: 5px; width: calc(100% - 10px); /* padding: 45px 40px 40px 40px; */ padding-left: 10px; /* background-color: white; */ } > On Jun 4, 2018, at 8:22 PM, Alex Harui wrote: > > I pushed a change tha

Re: [royale-asjs] branch develop updated: Fixes #258. But is that a proper fix?

one (static leads to unexpected layout). Even describing what static does is complicated as opposed to relative which is conceptually simple.[2] All in all, relative seems like the right default for Royale apps to have. My $0.02, Harbs [1]https://css-tricks.com/what-if-there-was-no-position

Re: Last class selectors

actual application*! > On Jun 5, 2018, at 2:38 PM, Carlos Rovira wrote: > > Congrats Harbs! :) > > as I just responded to Alex, I hope to give a try to all this soon as I get > finish some work I have in my hands right now. Maybe in one or two days > from now. > > Thank

Re: Incorrect descendent CSS output

That one snuck in by mistake. It’s not being stripped out… > On Jun 5, 2018, at 10:24 PM, Harbs wrote: > > .tab__content > li .content__wrapper

Re: How to replace Flex Path in Royale

Does this help? http://royale.apache.org/asdoc/#!org.apache.royale.svg/Path > On Jun 5, 2018, at 11:08 PM, Piotr Zarzycki wrote: > > Hi Guys, > > I have a component where 90% of it is Path [1] class which is drawing for > me. If I

Re: How to replace Flex Path in Royale

sn't work for me. Can you post code in > paste.apache.org <http://paste.apache.org/>. > > Thanks, > Piotr > > wt., 5 cze 2018 o 22:45 Harbs <mailto:harbs.li...@gmail.com>> napisał(a): > >> Does this help? >> http://royale.apache.org/asdoc/#!org.a

Re: Incorrect descendent CSS output

what the easiest way to solve this problem is. I’m pretty sure we also still have to deal with avoiding component conflicts. So, my problem is now working, but we’re not out of the woods… ;-) Harbs > On Jun 6, 2018, at 12:08 AM, Alex Harui wrote: > > > > On 6/5/18, 2:01 PM,

Re: Incorrect descendent CSS output

drag other > selectors back in. > > -Alex > > On 6/4/18, 9:48 PM, "Harbs" wrote: > >Thanks. > >I just observed a new problem. I have not pulled in your changes, so I > don’t know if it’s fixed, but it used to work correctly. > >

Re: Last class selectors

elease, does not had anything. I'm still confusing with > it... > > 2018-06-05 21:09 GMT+02:00 Harbs : > >> The js.map file is used for debugging source code. >> >>> so very good right? ;) >> >> Yup! :-) >> >>> On Jun 5, 2018, at 8:35 PM

Re: Incorrect descendent CSS output

OK. And that will only work for the html namespace? > On Jun 5, 2018, at 11:57 PM, Alex Harui wrote: > > > > On 6/5/18, 12:24 PM, "Harbs" wrote: > >It doesn’t look like the fix helped. > >The following selectors are still being stripped out. I

Re: Incorrect descendent CSS output

JSCSSCompilationSession.cssRuleToString? > On Jun 6, 2018, at 1:01 AM, Harbs wrote: > > I’m not using menu, and it’s pretty doubtful anyone else is using it yet > either, so yeah, it’s probably safe to remove it temporarily. Not sure which > other elements might cause problems. > > Another one which

Re: Type Selector Approximation (was Re: [DISCUSS] Explanation of the changes)

gt; > My 2 cents, > -Alex > > On 5/30/18, 11:58 PM, "Harbs" <mailto:harbs.li...@gmail.com>> wrote: > >I’m not talking about solving subclassing here. > >I’m talking about one thing: How to determine what classnames the compiler > write

Re: [royale-asjs] branch develop updated: Fixes #258. But is that a proper fix?

Yes. There is a lot to be said for your approach of using strictly classes for assigning layouts using CSS. It prevents a lot of the reflowing problems. I’m interested in seeing how far you can get with it. :-) Harbs > On Jun 6, 2018, at 10:58 AM, Carlos Rovira wrote: > > Hi Yishay

Re: Incorrect descendent CSS output

types. FWIW, I think all selectors are case insensitive. Harbs > On Jun 6, 2018, at 12:32 AM, Alex Harui wrote: > > > > On 6/5/18, 2:29 PM, "Harbs" wrote: > >Done. > >That does seem to fix the problem. > >Of course, things like .M

Re: Incorrect descendent CSS output

to have a prefix, but no namespace (unless I’m missing something). Harbs > On Jun 6, 2018, at 12:51 AM, Alex Harui wrote: > > The data structure seems to have a slot to hold a namespace. I think there > is code somewhere that checks the namespace to avoid the outputting some > er

Re: [royale-asjs] branch develop updated: Fixes #258. But is that a proper fix?

I think the point was that the inline style needed to be removed in certain cases. > On Jun 6, 2018, at 8:52 AM, Yishay Weiss wrote: > > Ok, but why does that get in the way of ‘flex’ and other display/layout > styles? > > > > > From: Alex Harui > Sent:

Re: [royale-asjs] branch develop updated: Fixes #258. But is that a proper fix?

in the first place and I think it’s worth-while. The change will also enable us to get rid of forced reflow when setting x and y values to UIBase which is a major performance sore-spot. Harbs > On Jun 5, 2018, at 8:00 AM, Alex Harui wrote: > > Ah, ok. How would a user disable that

Re: Type Selector Approximation (was Re: [DISCUSS] Explanation of the changes)

and the class is not written a second time into Express.swc. HTH, Harbs > On Jun 6, 2018, at 11:29 AM, Carlos Rovira wrote: > > Hi Harbs, > > I reach to the same conclusion that "typeNames" set in the class code is > not the best way to go, and not PAYG. A rule to follow shoul

Re: Type Selector Approximation (was Re: [DISCUSS] Explanation of the changes)

change that to type selectors and declaring the selectors in the manifest would enable that. This might be something I could work on, but I’d likely need direction. Thanks, Harbs > On Jun 6, 2018, at 6:33 PM, Alex Harui wrote: > > This just seems like too much work for the hopefully seldom

Re: [royale-asjs] branch develop updated: Fixes #258. But is that a proper fix?

-Have the x,y setters add a class selector to the parent. > -Have a bead, like we've discussed for UnselectableElement, that brings in > the selector. > -Have the layouts that allow for absolute positioning set the right styles or > selector on the parent. > > My 2 cents, > -Alex

Re: [royale-asjs] branch develop updated: Fixes #258. But is that a proper fix?

which is not PAYG both in terms of code and performance. Simply put: static is a bad default. Default relative positioning gives more expected results in 99% of use cases and usually results in *less* code. My $0.02, Harbs > On Jun 6, 2018, at 7:37 PM, Alex Harui wrote: > > Setting position:

Re: New blog example post "Using View States to show or hide content"

FWIW, I tried to remove that from the page, but it had no effect. I don’t know why. I also tried to see how it was constructed in WordPress and I couldn’t see the code block at all. What was I missing there? Harbs > On Jun 7, 2018, at 10:50 AM, Carlos Rovira wrote: > > Hi Om, &g

Re: Type Selector Approximation (was Re: [DISCUSS] Explanation of the changes)

> IMO, if we all pitched in on emulation > Perfection can be the enemy of success. Sorry to be so selfish, but I am > just trying to keep my job. Fair enough. If I were to pitch in with the emulation, what would you recommend I work on? Harbs > On Jun 6, 2018, at 9:24 PM, Alex

Re: [royale-asjs] branch develop updated: Fixes #258. But is that a proper fix?

hich > means that it shouldn't matter what style.position is. > > My 2 cents, > -Alex > > On 6/6/18, 2:12 PM, "Harbs" <mailto:harbs.li...@gmail.com>> wrote: > > >> On Jun 6, 2018, at 11:05 PM, Harbs wrote: >> >>

Re: [royale-asjs] branch develop updated: Fixes #258. But is that a proper fix?

Here’s one example very similar to the RoyaleStore problem: Which produces: The dockAndOuterContainer needed the y=“40” or it occupies the same space as the controlPalette. With a default

Re: [Discussion] Summarizing all discussion about Royale organization and structure

visuals (i.e. subcomponents) Beads that modify visuals Beads that add or remove functionality Harbs > On May 29, 2018, at 5:26 PM, Carlos Rovira wrote: > > About beads: Right now all beads are mixed and the major problem I > experience is to know what beads already exists and wher

Re: [Discussion] Package change names (was Re: 0.9.3 Release)

a new package. I’d rather wait to discuss this until we have some clarity on the ones above. Can you think of any other questions we should be asking ourselves? Thanks, Harbs > On May 29, 2018, at 4:41 PM, Carlos Rovira wrote: > > Hi, > > completely. > > two things: &g

Re: [Discussion] Package change names (was Re: 0.9.3 Release)

> On May 29, 2018, at 5:34 PM, Carlos Rovira wrote: > > Hi > > 2018-05-29 16:00 GMT+02:00 Harbs <mailto:harbs.li...@gmail.com>>: >> >> >> 1. How do we define what is “Core"? >> > > *Core*: This classes are needed to build a Ro

Re: [Discussion] Summarizing all discussion about Royale organization and structure

Do you have ideas for a naming structure? > On May 29, 2018, at 5:50 PM, Carlos Rovira wrote: > > +1 Agree. > > 2018-05-29 16:35 GMT+02:00 Harbs : > >> I agree that beads could use organization. >> >> Model view and controller are easy ones. The res

Re: [Discussion] Package change names (was Re: 0.9.3 Release)

inue as Piotr proposed in a fork and abandone Royale as others > did? Or can we go forward and take the best of what all think? Definitely work this through. :-) I think we can come to an agreement. I think we’re not so far apart. Thanks, Harbs

Re: [royale-asjs] branch develop updated: Removed duplicate Container

Sorry about that. Before this commit the build was failing. That was due to the fact that there were two different Container classes and mixed up references. I’m out of time for today. If you don’t get to this before Saturday night, I’ll look at this then. Harbs > On Jun 1, 2018, at 6:13

Re: [royale-asjs] branch develop updated: Removed duplicate Container

I just looked at things and I have no idea what about my commit would have caused those errors. I’ll look more when I come back online… Harbs > On Jun 1, 2018, at 6:40 PM, Harbs wrote: > > Sorry about that. > > Before this commit the build was failing. That was

Re: Restructuring Composite Components

primarily trying to figure out the best way to declare the “skin pieces” of the view. Harbs > On May 31, 2018, at 5:17 PM, Piotr Zarzycki wrote: > > Hi Harbs, > > What if ComboBox will extend DataContainer? It will be at some point list > itself. Than the rest responsibility i

Re: [Discussion] Package change names (was Re: 0.9.3 Release)

I’m right and they will. I don’t see how restructuring Basic is necessary until we’re sure of the outcome of that. Thoughts? Harbs > On May 31, 2018, at 2:10 PM, Carlos Rovira wrote: > >> 2, Composite TLCs are components such as ComboBox, DataGrid, possibly >> ImageButon e

Restructuring Composite Components

we add interfaces (i.e. IButton) and declare the classes using interfaces? I mean something similar to IItemRenderer. Maybe just use ValuesManager to just lookup some other “name”? We’re currently doing something similar with ColumnClassName in DynamicDataGrid. Other ideas? Thanks, Harbs

Re: Restructuring Composite Components

An additional wrinkle in this problem is wether there’s any way to specify the parts of the view using MXML, or it has to be in CSS. If they are beads, that problem is simplified. If not, is there a way to add to ValueManager via MXML? Harbs > On May 31, 2018, at 6:09 PM, Harbs wrote: >

Re: Last class selectors

. Harbs > On Jun 4, 2018, at 4:27 PM, Harbs wrote: > > The only class selectors left in Basic defaults.css is: > > .Application *, .royale *, . royale *:before, . royale *:after { > -moz-box-sizing: border-box; > -webkit-box-sizing: border-box; >

Re: [royale-asjs] branch develop updated: Removed unselectable selector

ongly it should be a “proper” selector, I’ll do that. Thanks, Harbs > On Jun 4, 2018, at 7:07 PM, Alex Harui wrote: > > Feel free to change the name of the bead so that the Type Selector name looks > "better". I think we agreed to drop the "Bead" portion of names go

Re: [royale-asjs] branch develop updated: Fixes #258. But is that a proper fix?

. The default would be relative, but beads would be free to change that to whatever they want. Of course, that would dictate that UIBase belongs in Basic and not Core… ;-) Harbs > On Jun 4, 2018, at 7:10 PM, Alex Harui wrote: > > I’m not sure exactly what change you are proposing, but UI

Re: [royale-asjs] branch develop updated: Removed unselectable selector

y 2 cents, > -Alex > > On 6/4/18, 9:11 AM, "Harbs" <mailto:harbs.li...@gmail.com>> wrote: > >> I don't know why someone would want to override unselectable styles, but the >> first idea that popped into my head was a different background color so >&g

Re: [royale-asjs] branch develop updated: Removed unselectable selector

That would probably work. I’m not totally happy with that selector name. I can switch the implementation if you think that’s better. I’m not sure why a user would override an “unelectable” style though. Harbs > On Jun 4, 2018, at 6:45 PM, Alex Harui wrote: > > Hi Harbs, > >

Re: [royale-asjs] branch develop updated: Fixes #258. But is that a proper fix?

: relative. That would have a major positive impact on performance. Thoughts? Harbs > On Jun 4, 2018, at 6:36 PM, Alex Harui wrote: > > Hi Yishay, > > IMO, the new fix is better. And you took the right approach by examining the > code flow in the debugger. When layout fail

Re: [royale-compiler] branch develop updated: compiler-jx: added js-dynamic-access-unknown-members compiler option to have emitter use dynamic bracket access when the right side of a member access exp

think it should default to true. Thanks, Harbs > On Jun 26, 2018, at 9:56 PM, joshtynj...@apache.org wrote: > > This is an automated email from the ASF dual-hosted git repository. > > joshtynjala pushed a commit to branch develop > in repository https://gitbox.apache.or

Re: [royale-compiler] branch develop updated: compiler-jx: added js-dynamic-access-unknown-members compiler option to have emitter use dynamic bracket access when the right side of a member access exp

references to quoted references. This means object literals will have property names quoted (i.e. {“name”:”Harbs”} instead of {name:”Harbs”} and foo[“name”] instead of foo.name. This is the recommended practice by Google when renaming properties might have unwanted consequences. https

Re: [royale-asjs] branch develop updated: Shifting 24 bits converted to negative int value

24 >>0 is two operations instead of one, so I’m guessing that performance gains over multiplication will be less (but I could be wrong). Thanks, Harbs > On Jun 25, 2018, at 8:08 PM, Alex Harui wrote: > > My main concern is having Royale "do the right thing". I believ

Re: [royale-asjs] branch develop updated: Shifting 24 bits converted to negative int value

t; > FWIW, I'm not clear that ">>> 0" actually results in a call to the CPU's > shift operator or even the Browser's shift code. It might just be used for > type inferencing. > > My 2 cents, > -Alex > > On 6/25/18, 10:18 AM, "Harbs" <ma

Re: [royale-asjs] branch develop updated: Shifting 24 bits converted to negative int value

the last byte. I don’t see how we could get a different result after adding the four byte values together. Thanks, Harbs > On Jun 25, 2018, at 10:46 AM, Alex Harui wrote: > > Here's an article that might help. > https://stackoverflow.com/questions/6798111/bitwise-operations-on

Re: [royale-asjs] branch develop updated: Shifting 24 bits converted to negative int value

gt; > On 6/24/18, 12:25 PM, "ha...@apache.org <mailto:ha...@apache.org>" > mailto:ha...@apache.org>> wrote: > >This is an automated email from the ASF dual-hosted git repository. > >harbs pushed a commit to branch develop >in

Re: [royale-asjs] branch develop updated: Shifting 24 bits converted to negative int value

that’s the simplest way to resolve this. Thanks, Harbs > On Jun 25, 2018, at 9:32 AM, Alex Harui wrote: > > Yeah, that article is addressing what I meant by "out of range" or an "signed > int read". What method is this that you are changing? If this is all

Re: BinaryData and odd bytes

Done. Thanks. > On Jun 25, 2018, at 1:41 AM, Greg Dove wrote: > > btw, a quick scan of the code let me find something that is an obvious typo > (mine I expect) >

Re: BinaryData and odd bytes

). There should be test cases to cover everything. (Unless I missed some edge cases.) It’s possible that the float methods could be improved with math, but I’m done for now. If anyone wants to improve things further, feel free… Harbs > On Jun 24, 2018, at 4:46 AM, Greg Dove wrote: > >

Re: MD5 [was: Re: BinaryData and odd bytes]

cions as described in the article you > linked to. Which browser(s) did you test with? Chrome, Firefox and Safari. All on Mac. I’ve used BinaryData pretty extensively and I haven’t had issues. I don’t understand why MD5 was failing, but it seems like whatever the issue is is prett

Re: BinaryData and odd bytes

times the multiplication. I only tested 16 bit uints. It might be worthwhile adding ints and 32 bit. Thanks, Harbs > On Jun 22, 2018, at 8:58 AM, Alex Harui wrote: > > It is definitely true that I don't know how expensive instantiation of small > instances is in the browser. Might

<    1   2   3   4   5   6   7   8   9   10   >