I'm looking into adding a state management to my web app.
I'm using Angular 6.
I've seen this library, which looks promising:
https://github.com/angular-redux/store
But I'm agreeing with the writer of NGXS that decorators are probably the right way.
I also want to add undo-redo to the state management and it seems that angular-redux has this with redux-undo:
https://github.com/omnidan/redux-undo
Is there an equivalent to this in NGXS? (I don't need something that fancy)
Do I need to manually to write it?
Right now NGXS dont have any support for "undo" functionality.
Also, if you can explain why you need undo functionality, i try to help with possible way.
Check this issue : https://github.com/ngxs/store/issues/269
Related
I'm building a web app using ReactJS.
I'd like to implement something like this:
So my question is:
How is this effect called?
How could I implement it?
I don't want the code, I'd like really to learn how to, but I don't know how to look for it.
I've done all components I need, I just need to know how to implement this particular effect.
Of course, a simple "look at this post" will be apreciated too much.
According to the documentation given by Facebook, using JQuery is not a good practice when you are using ReacJS, that's why I don't know where to start.
Thanks is advance.
I think you want a sticky header, you can use this library for an easy implementation with React.
I have been searching for and have not located (I fear it doesn't exist) a wire frame application that will use our current css for objects.
We have spent a lot of time perfecting our css to get the look we want, now I want to be able to use that css for new mockups without creating new objects each time we add something (as we would have to in photoshop).
In a perfect world, it would even handle the page layout so all that remains is the logic.
Has anyone heard of a tool that can do this?
I haven't used it, and I can't vouch for it, but https://alpha.easel.io/ might fit the bill. It's still in beta, but looks very interesting.
From their homepage: "Implement designs quickly using exact CSS properties rather than guessing from a mockup."
http://axure.com is a popular wireframing tool. There ways to make it use custom CSS: http://enterpriseux.tumblr.com/post/8972215862/an-axure-html-prototype-hack
We're running one of our apps on a 8" touch screen and want to add help to it.
Launching Qt Assistant from a menu item works fine for desktop applications, but for touch applications it's far from ideal.
I haven't been able to figure out if it is possible, or permitted to do so?
QAssistant.exe itself seems to come with some license restrictions, but maybe there's another way to do this, like embedding a small web-browser or something.
Have anyone else tackled this, or something similar?
Check out how QtCreator does this, they have integrated QtHelp which looks exactly like what you're trying to do. The library they use for that is the QtHelp module (I think).
You should check the documentation for QHelpEngine and QHelpContentWidget. I think that these classes will meet your needs.
Another way would be to actually see how Qt Assistant is implemented, by looking at the source.
Hi I have to do a small CMS application in MS ASP.NET using WebForms.
I do everything on my own: front-end and back-end and Data Base schema.
Now that I want to develop the site, I wonder if I should start from front-end first, or back-end.
Considering this is a small project, could you guys give me a list of steps I do better following to help to determinate what is the best order for developing my application?
Thanks once again for your time.
You'll develop all tiers as you go most of the time
For some page you may first create database schema and fill it up with some dummy data and than work your way up.
For others you may start with a page itself and then write functionality that's needed to get it working. Especially when this page hasn't been envisioned enough. This is not bad nor good. It's just the way development tends to be.
Some considerations
Follow agile development
Write down some requirements in a form of user stories (and keep track of them), that don't give any info about page, data etc. Just something like As a user I would like to have primary navigation on my page. This kind of a story will permit later changes to code/pages without the story becoming invalid.
Don't haste into something fully functional at first. Don't over-engineer your code. Because you'll end up doing changes later = follow YAGNI. For instance don't fully design your DB at first. Do just as much as you need per story being developed. But do think of future things that you'll have to integrate into existing codebase.
Refactor existing code right away when you see something should be changed.
If you have someone to test your code, let them do it. Don't develop next stories before existing bugs have been fully resolved. You'll be grateful for this later.
If your code is semi-complex I suggest you write unit tests, so future code changes won't break existing functionality.
Most of all: learn as you go and change existing code while doing so. Since you're learning these technologies I suggest you stick to simplicity at first. You'll add more complex things when needed. Some of them won't get done at all. So in the end youl realise YIDNI (yep, I didn't need it).
I usually write out what my requirements are first, if I need to use a database, I create that first, always. After my database I start working on front end that connects and uses my already created database.
I worry about the front-end last, can you can always change that pretty easily
I would say that in many systems, the back-end is there to support what is needed for the front-end to work. If you don't know what the front-end needs, there is little chance of successfully designing the back-end. So I'd start off with putting at least a rough front-end in place first (if even just a paper prototype).
I tend to approach all of my projects with a back-to-front approach for one simple reason - testability. Writing solid tests against a back-end early will will make it easier to work on the other tiers progressively. It also, as "bonus" helps to keep business logic out of places it does not belong.
I find it easier to develop the logic and back-end first, so that I get that right, then apply the interface to it. This way you avoid writing functionality based on what you think you need from the front end.
It is important to get a good scope of what you want to do/tackle, and try to implement that in the back-end first. Then wrap it in a nice interface!
I am looking at building the login/registration part of a website (ASP.NET) and would like to see some example code or instructions on how to do this properly. For example, how to correctly use cookies and how to encrypt what is stored in the cookie to ensure the session persists until they logout/timeout.
I do not want to use the builtin ASP.NET Membership/Provider stuff as it looks painful to use and not very flexible. Please do not answer with 'This is how easy the ASP.NET Membership/Providre stuff is to use, just check this out and you will use it!' as I don't want to use it!
Don't get me wrong, I'm just wondering what exactly do you find painful and not flexible about the ASP.NET providers? I've used them a lot and I find them very flexible. I've even written some custom providers which is a straight forward process.
If you don't want to use ASP.NET providers, what are your exact requirements? I might help you out if I understand a bit better what you are trying to achieve.
Michael