11–20 of 48 posts
That's not to say it's not a great bit of effort, but I can't think of anybody that has a job to build widgets like on the demo page, yet cannot build them via pure CSS2/3 or JQuery.
I'm no designer, but i'd find it easier using CSS examples I find off the web combined with the information-glue that is StackOverflow, if something goes wrong with UILang, I'm on my own.
The same design taste is evident in the project webpage itself.
I think this is a solution to a problem that doesn't exist. That's not to say it's not a great bit of effort, but I can't think of anybody that has a job to build widgets like on the demo page, yet cannot build them via pure CSS2/3 or JQuery. I'm no designer, but i'd find it easier using CSS examples I find off the web combined with the information-glue that is StackOverflow, if something goes wrong with UILang, I'm…
I personally teach all of our designers enough jQuery so they can animate their designs. The issue is its a steep learning curve and to be honest the Javascript is normally throw away as once we come to build the interface we normally use a framework like Ember or Backbone.
Nice work Benjamin!
Extend uilang with more commands (like "after that", "then") and conditions and it would be really powerfull language, that can be used for complex things too.
At the moment every developer with little complex instructions have to comment the code, uilang can reduce this work.
A separate npm module and source files with uilang could be parsed and compiled (like browserify) - (reactjs is a good example for that, include directly in frontend or compile jsx in backend).
I really think you should rethink the project and focus not only on beginners. -> i am not sure they will use it, because you find tons of ressources for things like bootstrap, purecss, ....
I really like this. I think its an interesting approach to a problem designers have. I personally teach all of our designers enough jQuery so they can animate their designs. The issue is its a steep learning curve and to be honest the Javascript is normally throw away as once we come to build the interface we normally use a framework like Ember or Backbone. Nice work Benjamin!
When i add a complex jQuery sequence, i comment the code -> my comments look like uilang. It would be nice to reduce the work and do it in one language.
I think this is a solution to a problem that doesn't exist. That's not to say it's not a great bit of effort, but I can't think of anybody that has a job to build widgets like on the demo page, yet cannot build them via pure CSS2/3 or JQuery. I'm no designer, but i'd find it easier using CSS examples I find off the web combined with the information-glue that is StackOverflow, if something goes wrong with UILang, I'm…
Maybe if "you're no designer" you're not the target audience? There are definitely a wide variety of other ways to do this, but extending a designer's knowledge of CSS to include minimal interactions is a nice way of leveraging existing know-how. jQuery is a bit of a mess conceptually, outside the core.
All of the examples are basically differently-styled variations of "clicking on X adds/removes class Y on element Z". Is this all it can do? Would have liked to see some slightly more varied use cases.
I was thinking the same. From the few examples given, it seems to be only useful to toggling classes from click events. Would like to see some more use cases.
I guess if you only need support for adding/removing/toggling classes, and you have no plans of using jQuery, this could be useful. It's 1kb of Javascript, compared to jQuery, which is over 80kb minified. Now, everyone and their dog likely has jQuery cached from a CDN, but it's a good way to reduce unnecessary bloat. If they added one or two common features from jQuery, and used a normal syntax instead of this written non-sense, I could see some people using it as a light version of jQuery.
Mine is a little nicer (IMO of course) and supports a little more than just class toggling (the workhorse of interaction design) such as multiple chained actions per target, and more.
I've always thought of this as an intermediate step - designers for whom this type of thing would be useful would know CSS selectors at least, and could work with a bootstrap-alike. The more useful state would be to expose something like this directly in a web preview environment.