New member here. I am using Code Effects with ASP.NET Core. I want to have a custom UI to define rules and actions, using drop downs. How hard would this be?
It's just a matter of generating custom xml and adding it to an xml document for execution # run time.
You need to create such a UI from scratch by yourself. Code Effects' rule editor does not support the alteration of the rule selection flow.
Related
As a front-end designer converting designs (PSD, Sketch, AdobeXD, ..etc) to dynamic HTML pages manual. I'm using bootstrap framework with jQuery library.
When I started this job it took long time to convert the designs to html, after that the time decreased because the work becomes classic and it is routine. But every design is different and I start from the scratch using bootstrap component then adding my override CSS and JS.
I wondering if there is tools or ideas to improve my work and do things faster??
What I know is that I can create my own JS or CSS codes that I use
usually (common things). Then, I can include these files all projects
that I'm working on.
I need other tools and ideas to use.
There are different front end starter tools (boilerplate) which you may use as a basis and write you code on top of them each time.
Also consider remove bootstrap if you need everytime to override it, as you said.
It is better to have less dependencies for sure.
Also try to write your html/css as like you create page full of components, which are independent. Use CSS BEM methodology and try to make components as reausable as you can.
In that into mind you may create something like your own library / framework of most used common components between projects and just to include them everytime.
You may provide simple customization via CSS native variables or LESS/SASS ones with help of mixins.
Is there any way to change the underlying function of innerHTML() so a custom function will be responsible to add things to the DOM? Is there a way to change the prototype function of innerHTML()?
The reason I ask is because the Samsung TV's do not like when innerHTML() is used. Instead, Samsung suggests using their own API to write to the DOM. However, it would be nice if my app's codebase can be used across other non-Samsung platforms. So it would be ideal if I could change how innerHTML() works in one JS file so it uses the Samsung function, rather than creating conditional statements throughout the code. Plus, since I am using jquery, it would be nice if I can affect innerHTML() directly since jquery also uses innerHTML().
Consider using this. It adds elements to the DOM in a more standard way, but allows you to still write HTML code to add to the DOM.
http://www.optimalworks.net/resources/betterinnerhtml/
I'm working on a school project using Swing and NetBeans. As a result, I have a lot of automatically generated code in my project. We have to follow strict style guidelines using CheckStyle. Is it possible to have the automatically generated source code formatted a certain way? As an example, is it possible to make the lines not go over 80 characters width?
If you're allowed to use generated code, the teacher should understand that this code is not generated by you, but by the IDE, and shouldn't care that it doesn't respect the formatting rules.
If he doesn't understand it, then let Netbeans generate the code, and then edit it using any text editor before giving it to the teacher.
If I were your teacher, I wouldn't allow the use of Netbeans's wysiwig editor, though. You learn how to use Swing (and use it properly) by hand-crafting the code, not by dragging and dropping Swing components.
We want to use Orbeon Forms to build and run some forms, however these forms require some more explaining than is possible in the 'hint' or 'help' sections. ('hint' is supposed to be rather short, 'help' does not support any kind of formatting, as far as i can tell) Therefore, I'd like to put some HTML above or below some of the questions (controls).
Now, I know that there is an option that shows you the source and allows you to make changes. This is, however, quite complex for a non-technical person.
Is there a(nother) way of inserting pieces of HTML in a form?
Also, I have looked at ways of creating a control that outputs/shows HTML, however it seems that both XBL and the Java classes for XForms controls always assume that it should be bound to some variable that's also in the resulting XML document. (And I'd rather not have that, since it will just be clarifying text.) Though it could be that I overlooked another possible option in XBL or Java.
Is it possible to create a component that does not get bound to the XML instance? (That I can then use to create a control that provides HTML functionality.)
For HTML in help message, Form Builder supports form authors entering a help message as HTML since version 4.4.
We often get requests for a control allowing form authors to enter their own HTML from Form Builder, this isn't yet implemented, at the point of this writing, and we have an RFE (#507) to cover this.
Is there a place (website) where I can the the standalone parts of jQuery Mobile? I'm interested in the radiobutton.
I don't want to use jQuery Mobile as I'm already using jQTouch.
jQM is now decoupled:
http://jquerymobile.com/blog/2011/08/03/jquery-mobile-beta-2-released/
Widgets: Now decoupled for flexible builds
We’ve wanted to decouple all our widgets from the page plugin for a
long time now and we’re happy to announce that we finally landed this
change. So what exactly does decoupled mean anyway? Well, the
individual widgets and utilities have always been broken out into
separate script files. However, the page plugin was responsible for
handling the auto-initialization all of the official plugins found in
the markup at page creation. This situation made it impossible to
remove plugins you don’t need without causing errors, and generally
set a bad precedent for future widget additions.
Now, pretty much all the UI widgets in the jQuery Mobile library are
completely decoupled so they can simply be deleted if not needed for a
particular project. This change allows you to dramatically reduce the
size of the library by only including the specific set of widgets or
features you need, in addition to the handful of required, core files.
While we still plan to do more decoupling and cleanup, the following
files are now decoupled and can safely be removed from the make file
before you do a custom build:
page header/content/footer
collapsible
controlgroup
fieldcontain
fixheaderfooter
button
checkboxradio
select
slider
textinput
links theming
listview
navbar
grid
We will work on a dependency map because a few widgets rely on others
to work. For example, the button markup plugin is called by many of
the widgets above, so it can only be excluded but if you’re not using
any of the widgets that depend on buttons.
We’re still working out our recommendations for mapping plugin
dependencies and decoupling things even further. Ultimately, this will
be surfaced in a download builder tool, so stay tuned!
You can head over to their GIT Repo and just download what you want:
https://github.com/jquery/jquery-mobile/tree/master/js