New to UKI

[Miloš Rašić]

Hi, I've never used UKI before. I'm considering using it for a
project. I have some questions before I adopt UKI as a good solution.

What scares me the most about UKI is the version number. What exactly
does 0.3.8 mean? What's missing and preventing the framework from
being version 1.0 or above?

Are there any tutorials to help new users get started? Having to
reverse engineer complex examples is not the most time-efficient way
to learn.

From what I have seen in the examples, UKI generates DOM elements. How
well does UKI handle html loaded via AJAX or already present in the
DOM before the framework is initialized? How well does it handle
custom styling with CSS?

How well does UKI work with jQuery? Can I give ids and classes to
elements I create with UKI so that I can easily select them with
jQuery?

What's uki.more? Does uki.more TreeList support drag and drop of tree
nodes? Why is there no sorting in uki.more SplitTree example? Not
supported or just not implemented in the example?

[xangelo]

I'm not sure what the Vladimir is considering "complete" for a 1.0
release, but as it stands right now, UKI is fairly complete. If you
take a look at the github page https://github.com/voloko/uki/ you'll
see what is planned for the next release, but not anything further.

As for tutorials, there are few and even documentation is fairly
sparse, but getting started is fairly straight forward if you take a
look through the individual code samples http://ukijs.org/examples/ or
https://github.com/voloko/uki/wiki/ and check out the different Pages
for a couple of tutorials.

UKI works fine with any other library and yes you can give your
elements id's and classes, however, because of HOW the elements are
drawn on the page, I'd suggest that you don't access their content via
any other library except for uki. You can, however, perform other
actions as needed (hide, animations).

Uki is not very well styled with CSS at all right now. Theme files are
created in JavaScript (as far as I know) and seem to be, more or less,
straightforward. Version 0.4 is supposed to remove this and push the
styling over the CSS.

Uki.more, from my understanding, is a set of views that provide
advanced functionality that not every project may need.However, if you
look through the project on github you'll notice that it's pretty much
been removed from there. Not sure whether this means that support is
discontinued or if it will be coming back...

[Johan Rydberg]

Uki is not very well styled with CSS at all right now. Theme files are
created in JavaScript (as far as I know) and seem to be, more or less,
straightforward. Version 0.4 is supposed to remove this and push the
styling over the CSS.

And just have the layout done with "inline css"?

 

[Miloš Rašić]

"Use css instead of js based themes" is what it says in the readme. For some reason, I connect the word 'themes' with an external file. Inline css would be a bad idea for themes. In thick web clients, it is a good idea to have default styles in external css and use dynamic inline css to manipulated the elements. You can then remove the inline css to revert to default. Not possible if you use inline css for default styles because it gets overwritten by your js code.

[xangelo]

I would think themes would be external packages that could be applied
to whatever uki project you're working on currently.

Personally, I would save positioning/size for inline styles and
everything else should be external. As long as there are a few rules
set out when creating your theme files (like no margins) I think
external css files would work well.


On Mar 7, 5:51 am, Miloš Rašić <milos.ra...@gmail.com> wrote:

[Vladimir Kolesnikov]

1. Ukijs is now using normal css in separate files to style the views. Ex: https://github.com/voloko/uki/blob/master/src/uki-view/view/splitPane/splitPane.css
2. Css and other resources are usually tied to js views. The dependencies are resolved using the uki tools. Ex: https://github.com/voloko/uki/blob/master/src/uki-view/view/splitPane.js#L1 If you're using dev tools it will just work.
3. Css can be defiantly overridden in your own css files. You still can extend the default views to change something more substantial then styling.

[Vladimir Kolesnikov]

Exactly. That's what my goal is now.