Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
Can you give several indications (pro and cons) concerning the fact to put the menus of a web application inside the database?
Mainly it depends upon your requirement of your application. Its not always a good approach to bring a drill machine to make hole in sand. Every approach has some limitations and need more efforts if you do apply some alternate approaches.
In cons you can consider
Performance ( to prepare dynamic menu every time you load the master page also the static text less time to process in compare to dynamic)
Configuration will be always an issue while adding or modifying the menu
(Always need a database guy at the time of any change)
Pros
Highly configurable and completely dynamic
Can add/remove the attribute and change the text without affecting anything in code.
We have some solutions also to overcome from the cons
In case of performance we can use caching but everytime the menu change you need to recycle the application pool.
For configuration you can provide a page to control the menu content. (No Sql guy needed)
So as I said earlier you can go either way as your application adopt easily and in much better way.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
What are some ways including machine learning that I can use in my projects to generate things related to another. Like related apps, related websites, related products, etc.
I've been brainstorming these are strategies...
one way i can think of is show items from same category. But that would be too broad.
2nd way improves upon previous step, it's to keep track of what people click next and promote that item. Meanwhile keep bottom list randomized to let other relevant items show up and get clicked.
3rd way is to use machine learning and provide training data somehow and use that.
I want something simple but smart, as it gets better with time.
Collaborative filtering is designed for solving exactly this problem. The problem with this approach is that produces good results having a lot of data only. I mean... A LOT. And it's not a really simple thing to use. However, any machine learning technique is not simple. There are some node.js packages for CF available, but I have no idea how good are they.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
I am creating an application where each user will have his own workspace which will consist of some text files. He will be editing and saving these files excessively.
I want to implement a version control system for each user to keep track of his work and revert back and forth to any previous version if he wants to.
I would also like users be able to fork into each others workspace to copy the content to their own workspace just like in plnkr.co, make changes and commit easily.
My stack is node.js and angular.js
Where should I start, to implement it. I guess there should some way to use git or some other open source project. Does anybody have any idea what plunker is using?
Super late response, but for anyone stumbling across this, try checking out git=annex
We used this at one of my old jobs for keeping track of fMRI datasets. It's best used for large data though, so one may want to find something similar but perhaps better aligned for what they need.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
At the moment I have about 2000 trades which are priced using excel. I have found that the sheets aren't very reliable and 4 out of 5 days will break for no reason. Also, the way the pricing sheets work is the pull the market data piece by piece, use it then delete it again. This is a nightmare if I need to re-run pricing as it is so slow.
Ideally I would love to build a GUI in a more reliable language, which is less liable to break down and faster. However, outside of excel my skills are limited.
I would like a few tabs on the GUI:
One to view the basics of the trades - type, maturity etc etc.
One to view the market data
Another to display the results of EOD p&l
All market data, trade data and static data come in XML form.
What is the best language to build this in? What kind of database could handle this data and how would it be setup?
I realise that this is a pretty big task, but its not something I want to do asap. I plan on doing it piece by piece. I'm also doing it for the experience! I would appreciate any help given!
I would recommend that you use Java. It is a very easy language to learn compared to other languages with similar capabilities. Java has a very simple GUI API called Swing that is effective and very easy to learn. It supports a similar display to excel using the class JTable. Setting up a database to work with Java is also relatively simple: you can write your own or use an SQL server.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
It seems that Indexhibit (www.indexhibit.org) is a sort of standard when it comes to building portfolio websites for artists. I just received a mail from an artist asking me whether I use Indexhibit. Beside the issues of the customer poking their nose into technical stuff, I need to know what's so special about Indexhibit?
I took a look at it and saw nothing more then a somewhat original CMS. I have my own system/libraries that I use to build simple websites and prefer sticking to these, but would like to know first... why does Indexhibit have this place among artists... and why do they say "an Indexhibit site" and not "a website built on Indexhibit"... what's the difference between an Indexhibit website and a plain website? Is there any advantage when using Indexhibit?
That's it, you got it, it's just a blank slate that makes it easy to pump out a small portfolio in a short amount of time. It's the helvetica of portfolio web design. Nothing fancy, but it's classic, the art can breath.
I come from a ASP.NET MVC and Django Background, and I've actually been having a bit of fun about working with Indexhibit. I got over my fear of PHP and there is some thing refreshing about just firing a query off, and building html straight out of it. Would never use it for a really custom job, but for things that fit the model, it gets quite out of your way for getting things done.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
I have a custom SharePoint solution which requires several list instances on a particular site (SPWeb). Now some of these lists are generic, for example a 'Pages' document library, wheras others are highly specific custom lists.
My question is which (if any) apsects of customisations should be cleaned up on feature deactivation. My instincts would say that generic lists which may be used by multiple solutions should be left, but the more specific customisations should be cleaned up. Does anyone have any experience of and/or advice on this type of sceanrio?
Its really hard to come up with a strict rule, as it will depend on your specific solution, however I would start with something like this:
On deactivation a feature should remove any artifacts created during feature activation that:
Have not been created by an end user AND that end users could not reasonably expect would remain
Is not required by any other feature, or that causes a failure in the broader solution it supports
Does not prohibit the re-activation of the feature at some later time.
On the project I'm currently working on we created a new exception for preventing the deactivation of features. We found that in many cases the activation of features was a one way street. This was largely because a solution was typically made up of a number of features, and disabling one caused a break down in the entire solution.
Often, a site only existed in order to host the feature, disabling the feature then left no purpose for the site.
Adding on to Daniel...
If another feature depends on this feature, they should be activated & deactivated together through feature dependencies