veosotano

11 ms·

1.
by veosotano 15y ago
What I wanted to put in the final license was something along the lines of "an implementation of the specification is only granted the permission to use the technology if at the time of being released (out of beta) it is absolutely complian
2.
by veosotano 15y ago
I've looked at it and it seems to share goals with AXR, but how good is it for semantics, accessibility and backwards-compatibility? Those are quite essential requirements.
3.
by veosotano 15y ago
The people that I usually see getting wowed are web designers and devs, that know the pains of dealing with all those issues that this project is trying to solve. I don't know your background, but if you don't do CSS you probably don't know
4.
by veosotano 15y ago
Well for starters its open source instead of proprietary. I think that already deserves some respect on its own. Then, this is based on doing websites in the web standards spirit of using plain-text files, where multiple components are link
5.
by veosotano 15y ago
The goals of the project are way beyond just making "A as wide as B is high". That is just a drop in the ocean. Once we do effects (such as shadows, blur, noise, etc) and more advanced processing we'll need as much performance as we can.
6.
by veosotano 15y ago
Sorry about that. It's not fully fleshed out yet. Are you interested in helping us figure out how to make the reparenting syntax as nice as possible? If so, I think the mailing list would be the best place for that... :)
7.
by veosotano 15y ago
You're rising some interesting questions. Mind posing them on the mailing list? That would be awesome :D Cheers.
8.
by veosotano 15y ago
The plan is to make the rendering engine an auto-updateable library, that's independent of the browser's release schedule. Thus, users would stay current faster. On the other hand, there will be a versioning system, so that authors can spec
9.
by veosotano 15y ago
I know we don't have anything to show right now, I didn't put this on HNews... we're still about 2 months from actually doing something like a public release, so sorry about that. But be assured that we'll have something to play with pretty
10.
by veosotano 15y ago
Suggestions on how to improve the phrasing of the website are always welcome :D I'd love to hear if, once you've read through the spec you still feel that the features are perceivably as complex as C++... I think they feel very naturally in
11.
by veosotano 15y ago
The reason is because that's one of the main pieces of the project. Providing a library that browsers can USE, not IMPLEMENT. Why would anyone do that? That's WAY too much work just for fucking something up just for the heck of it.
12.
by veosotano 15y ago
So can you do "myElement { alignY: 50% }" or something like that to automatically center vertically in your browser? Or can you do "100% - ref(width of sideColumns)" to create two fixed-width and one fluid column in the middle? Or can you r
13.
by veosotano 15y ago
It does indeed use JavaScript. Sorry about not being more clear about it in the spec, but that's a part we're still working on. It will feature a completely new DOM, integrating the properties of the HSS side and the JS ones all into one. F
14.
by veosotano 15y ago
You're right: HTML is going to stay with us for a long, long time. This is not about eliminating it, but to try something new as an alternative. It's not XML with vector shapes, that's exactly what SVG is . Vector shapes would live all ins
15.
by veosotano 15y ago
Hi there! My name is Miro Keller, and I'm the founder of AXR, so I'll probably be the best person to answer any questions you guys may have. So feel free to ask me anything about this project :) I'll try to answer all questions posed here,