Maybe, but I hit this with my mock up of the Royale website as well.
Since a lot of things are composed from other smaller pieces, I think we
want defaults where the CSS applied to the outer element of a component
applies to its children. It looks like inherited properties have lower
priority
I don’t think moving it to Application is going to help for things like
dialogs. (Or will it?)
> On Jan 2, 2018, at 8:03 PM, Alex Harui wrote:
>
> Maybe, but I hit this with my mock up of the Royale website as well.
> Since a lot of things are composed from other
Hi -
For my own business I want to create a product and want to try Royale for the
UX. I’ll have less than ten pages and want to start with three pages one of
which will be a simple login.. I will have web services. I’ll need to have a
file upload button. I want to serve the site through
Hi,
Over the next day or so you will see release branches being created and
commits being made to those branches and other branches by me. Do not
make commits to these release branches. This is just practice for the
automated scripts that will produce our release candidates. Hopefully I
will
Hi Dave,
I see two directions:
1) Going with Basic/Express module where you will be able to styling things
by CSS mostly to have it looking good.
2) Going with MDL module + things from other modules - where I believe
stuff there maybe a bit more www oriented.
Resources will be:
[1] - Look into
I really like doing things and moving forward.
I see only one problem in case of website which has been raised - License.
If you guys figure out whether problematic stuff is ok, we should export
and public that website now. There is no point to wait, building new one
using Royale can always
Still no success... other ideas?
Thanks,
Olaf
--
Sent from: http://apache-royale-development.20373.n8.nabble.com/
The first task is to determine if a list's selectedIndex or selectedItem
should be preserved.
For selectedIndex, adding or removing an item will get the same row
selected until that row no longer exists.
For selectedItem, adding or removing an item will keep the same item
selected until that
Hi,
I've successfully captured the ACE editor but there's one issue left [1]:
It seems to me that the Royale default font-family is always Arial and also
'overwrites' other settings.
The ACE editor depends on the monospace font but I am not able to set it
just for the surrounding group/div by
Hi Olaf,
Try inside js:Group -> https://paste.apache.org/NsUC
Thanks, Piotr
2018-01-02 22:08 GMT+01:00 Olaf Krueger :
> Hi,
> I've successfully captured the ACE editor but there's one issue left [1]:
> It seems to me that the Royale default font-family is always Arial and
When you have compiled everything, what actually are you seeing in CSS for
this Group and what, are you seeing in the children for that Group ?
Piotr
2018-01-02 22:37 GMT+01:00 Olaf Krueger :
> Still no success... other ideas?
>
> Thanks,
> Olaf
>
>
>
>
>
> --
> Sent
How are you doing that preservation, by simply saving item somewhere before
remove/add operation ?
I'm not following the part where we you wanted some opinion. Actually in
case of refreshing I didn't even thing about saving selection, but it's
true that it should happen! It's surprises me that in
Peter,
You didn't misread, but my thoughts probably didn't far away into problem
resolution. That's why I was surprise why I haven't thought about
preserving selection. :)
Thanks, Piotr
2018-01-02 22:10 GMT+01:00 Peter Ent :
> I thought because you mentioned that
And this one reason we have beads as a pattern. There is no one right way
to preserve selection and selection should not always be preserved for
certain kinds of data provider changes. So, create a bead that performs
the selection preservation you need and give it a name that makes it clear
what
Did you try this?
.aceEditor * {
font-family: monospace;
}
> On Jan 2, 2018, at 5:28 PM, Olaf Krueger wrote:
>
> Hi Alex,
>
>> The key piece, I think, is that inherited properties in CSS have a lower
>> importance that *...
>
> Yes, I think that's the problem:
>
> /*
>Did you try this?
Ha, this works!!!... and I guess it makes sense.
However, I'll check out the type selector tomorrow...
Thanks!
Olaf
--
Sent from: http://apache-royale-development.20373.n8.nabble.com/
I haven't looked at his ACEEditor class, but it is also possible that the
following would work.
.ACEEditor {
font-family: monospace;
}
And that should be a goal as well: to have the defaults.css for the
ACEEditor class to use an "ACEEditor" selector (instead of lowercase
"aceEditor"). If the
Hi Alex,
>The key piece, I think, is that inherited properties in CSS have a lower
>importance that *...
Yes, I think that's the problem:
/* Generated by Apache Royale Compiler */
* {
font-family: Arial;
border-width: 1px;
font-size: 12px;
}
>IMO, that should be
the
I’m guessing that the ACE Editor has sub-elements that are picking up the
globals rather than the ones for the ACEEditor element. I have not looked into
this at all…
Harbs
> On Jan 2, 2018, at 5:50 PM, Alex Harui wrote:
>
> I haven't looked at his ACEEditor class,
19 matches
Mail list logo