I'm working on a large web project based on LAMP stack.
I have to create a 'look and feel standard' for the aplication and i don't know how to begin. What parts must have this standard? Is somewhere a model?
I don't have large experience on web development so maybe i need to inspire in some good standards. Do you know where can i find some standards?
Thank you very much :D
The jQuery UI ThemeRoller provides a great GUI for playing with their stock themes, or customizing them. Worth while investigating.
Related
So I'm new to node.js, javascript frameworks, and meteor.com. I'm trying to learn how to build social networks, and I'm naive/struggling to understand why Meteor.js (meteor.com) wouldn't be able to do all the great things you see now that twitter, facebook, instagram are doing?
There's the comet technology between client/server, authentication configs, asynchronous coding for scaling and performance, and built on top of node.js.
I'm trying to learn more about long polling, comet, gridFS or how files are stored, and in general things like replication sets, and sharding to help with performance (esp since Redhat has this openshift platform that we can build our own private clouds with).
I have some computer science background, but it seems like magic, so what am I missing? If you all could think of a few buzz words that make a social network tick that Meteor.js doesn't support, what would it be?
I hear things about parallel and concurrency (webworkers fixes that in part, no?), websockets, that high level languages like python or java are better off supporting. There's only one to learn my answers, and thats by doing, but thought someone could sway me one way or the other via this thread. Thanks!
This question encompasses a really broad idea and just focusing on using meteor alone would solve this issue. Here are a few points to consider:
I don't think this framework would be a good starting point to learn long-polling, gridFS, etc etc. Meteor aims to be a framework that tends to be more of an ecosystem of packages e.g. you can certainly roll your own aformentioned strategies -- however for dynamic updates, Meteor uses its own Data Delivery Protocol (DDP) supported/implemented by (surprise) a good bunch of core packages such as Spark.
Parallel processing and concurrency can be better off done using other languages, but why not with? Since Meteor is largely based on node.js, and node.js is really good with the aforementioned stuff plus it can play very well with other languages so you could integrate smoothly. Meteor doesn't really require you purely rely on it, as other languages would say the same thing. It's all in the general engineering / planning for your project. There are already lots of really good stuff out there that rely on Meteor, join in! don't be afraid. It all boils down to planning (and the courage/perseverance to pull it off, of course).
Right now, we cannot tell if Meteor would be incapable of the usual great stuff by gigantic websites. Sure, we can do live updates, (its own kind of) publish/subscribe patterns, and powerful stuff to boost development (look at the seven core concepts of meteor to best understand this). It is not impossible to replicate what is already out there, really. We can only say it with uncertainty at the moment mainly because.. (see next point)
The framework is so young! it's still at 0.6.x at the time of writing. Please take time to look at the Meteor Roadmap to see how things are going in terms of broader support for persistence/databases, performance considerations, and the official DDP specification.
I hope I have answered your enquiry (and more, I hope). I'm really excited for meteor myself as it could easily be the next big thing. We have a couple of (for-)production projects using Meteor as well, so you're getting direct insight from a person who has done quite a bit of hacking (and tons of research and first-hand experience) in Meteor. Not that i'm saying i'm an expert or so, it's just so much fun to work with Meteor and i'm totally not kidding you.
Hope this helps!
P.S.: Fair warning though, resources and documentation is really sparse at this point. I try to contribute to the community as much as I can about it (one of my starting points is here, on SO).
I am designing a light-weight accounting application that suits small to medium
business (eg .shops), any reference to materials that help or ideas from anyone who did this kind of software before would be great.
NOTE : reference to a (C# preferably) library would be great.
There are many open-source accounting applications out there; i'm not sure if this one was done in c# but here's a link:
FrontAccounting(accounting software) Note: This one is a web-app.
The links for downloading the software are all the way at the bottom of the page in the "references" section. Hope that helps!
List of other accounting softwares(open source):
Other Softwares Scroll down to "Finance".
Try to keep it generic as possible and consider the adoption a plugin framework to forsee further extension. A good business analysis eventually is a prerequisite.
I was reading these days about large projects implementation in python and Flex, and very often people praise the use of framework (like Cairngorm, PureMVC or others) over traditional OOP coding.
I think i dont really understand the advantage of using FW, which is the strong point over classic programming? how big should be the project in order to use FW? it is intended mainly for web-applications? or can be used for desktop apps as well?
hope, all these doubts dont sound stupid to you, i am not Computer engineer, just electronic, so my knowledge of sw architecture is very limited.
Br
Using a framework is not really any different from classic OOP programming.
When you write projects in a similar environment, you will probably see yourself writing a framework (or a set of tools) over and over again.
A framework is really just code reuse - instead of you writing the logic for managing a common task, someone else (or you) has written it already for you to use in your project.
A well designed framework will keep you focused on your task, rather than spending time solving problems that has been solved already.
I would add my 2 cents here, using a framework will also help a better organized collaborative environment too. Your team mates will get to know about the code easily if you are following a standard framework.
In enterprise applications using framework helps meeting the deadline and better code quiality.
I work in a shop that is mostly .NET based, and we're trying to pick out a content management system to use. This means we mostly likely won't be able to use any of the common open source CMS projects (Plone, phpNuke, anthing not based on .NET, etc.).
Since I'm a huge usability nerd (just finished reading The Design of Everyday Things by Norman), I've been looking at them from that point of view. Frankly, I haven't been too impressed. This quote sums it up:
Most open source content management software is useless. The only thing worse is every commercial CMS I’ve used. - Jeffrey Veen
Here's a short list of our requirements:
Has to be .NET based
Prefer open source or on the inexpensive side
Limited feature set (we don't need too many features and they make things harder to use)
Does need Active Directory integration and robust permissions
Should be focused on web standards and usability
I know it's probably an impossible feature list, but are there any content management systems that kinda sorta look like they might not suck more than a Dyson?
Edit:
Here's the current situation:
I'm going to push for N2. I've got Active Directory integration working well (I even wrote a custom role provider). The only thing missing is workflow functionality. Hopefully I can get something going with that since it's the last sticking point. The N2Contrib project might provide a starting point if I can figure it out.
I would still love to check out Stencil CMS if/when it gets off the ground.
One of my co-workers was trying to get Umbraco going but wasn't having much luck.
Thanks for the help!
Self-plug is lame, but what you're describing is pretty much exactly what I am getting ready to release for $79 a pop. If you're still looking in a few weeks, take a peek. If you'd like, shoot me an email (rex#stencilcms.com).
I've heard both positive and negative feedback about Umbraco. A lot of people like Graffiti, but it's more blog-oriented than a full-blown CMS.
Check out N2 (http://n2cms.com/). I think that it covers most, if not all, of your requirements (I don't think it has Active Directory capability at this time). We are using N2 and I have really enjoyed how flexible it has been.
My company just completed a review of several commercial .NET-based CMS/portal platforms and, while I can't reveal who was in them (thanks, NDAs!), I can tell you that IMO they all sucked very, very badly.
Good luck on your search. I'll keep an eye on this thread in the hopes that there's something we missed.
We had a similar set of requirements and chose Telerik Sitefinity. It's got it's faults but overall I've been happy with it so far.
Unfortunately Jeffery speaks the truth. Which is probably why I build a new custom cms from the ground up every few years. Basically, the motivation for "boxed" CMS packages is to have every feature on earth and be everything to everyone and therefore do nothing particularly well for anyone. With the feature bloat comes the usability nightmares. Unless you start customizing and then you usually end up forking the project and losing the advantage of community updates.
Kentico CMS according your list:
Has to be .NET based
It's .net based, .NET Framework 2.0 or later
Prefer open source or on the inexpensive side
Free edition which can be used for commercial purposes is available, paid license starts at $750, source code is an option
Limited feature set (we don't need too many features and they make things harder to use)
Many built-in modules/features, anyway they can be easily disabled to keep the UI simple to use
Does need Active Directory integration and robust permissions
AD, Forms and Live Id! Integration
Should be focused on web standards and usability
UTF-8 Support including RTL languages, WAI Compliant, XHTML Compliant, XML, XHTML, HTML, XSLT, CSS.
Instant on-line demo or download available at:
http://www.kentico.com/Download.aspx
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions asking us to recommend or find a tool, library or favorite off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it.
Closed 9 years ago.
Improve this question
Having not done ASP.NET since v1.1, and now blitzing through the Wrox Pro ASP.NET v3.5 book, what other resources are available to get me developing enterprise ASP.NET apps the fastest?
I've been developing in DotNet since Beta and have been doing Winform & middle-layer architecture/design/dev for 3.5 years now (as this has been my client's desires). But I'm finding my falling behind has hurt me concerning a new client. :(
I'd appreciate any advice on moving forward as fast as possible. I'm looking for anything RAD related or even just great books on the subject that you recommend. Right now, I'm having fun consuming the Wrox book though. Thanx much!
I'd start with the QuickStart tutorials. That'll get you into the code, get you some exposure to the programming, architecture, controls, data access, and so on. You can also watch videos of how to accomplish various tasks in ASP.NET at the ASP.NET web site.
Assuming you already have substantial VB.NET or C# experience, you should get deep into ASP.NET fairly quickly.
Take a look to the ASP.NET Dynamic Data Scaffolding Framework (included in the .NET Framework 3.5 SP1), it allows you to build really quickly data driven web applications. Here you can find more good videos and resources about this RAD feature.
Not that easy, since "enterprise" is a word that can encompass lots of things. First off, I would suggest just getting to know which new frameworks are available, both out-of-the-box and not. And there's been a lot of those since .NET 1.1.
WCF, for example. Dynamic Data, as mentioned in another comment. ASP.NET MVC. LINQ, ADO.NET EF, WF.
I'm not suggesting you learn all of them, at least not all at once. Rather, be at least familiar with what they are and what they bring to the table. Browse through the base class library reference and familiarize yourself with the available namespaces. This will help you know what's there and what you will have to write. Try your hand at the bits that interest you.
After you're a bit more well-versed with the .NET framework, it's time to take a look at the other stuff you'll need for enterprise development. Frameworks such as CSLA and NHibernate. Testing stuff like TypeMock. As before just knowing what's out there, even without knowing the details, can help quite a lot.
Write code. Nothing quite like writing code if you want to learn quickly. Choose one of the apps you wrote back in the 1.1 days, and try to write a shorter, cleaner and/or more maintainable version with the new tools at your disposal.
And don't forget to have fun. If you're not enjoying what you're doing, you won't really be learning much. Good luck!
You probably shouldn't mix "enterprise" with "rad" as the two generally have extreme connotations on opposite ends of the spectrum.
Enterprise typically draws up ideas of, large, line-of-business applications, large complexity, large configuration, (and some would probably relate to pain, nightmares, etc..)
RAD typically refers to the drag & drop garbage that you see in awesome conference demos, but then you go back home and try to build and maintain and app built with dragging and dropping controls & data acccess components on your UI and you quickly see that it breaks down.
Pick a good balance of tools & techniques that make you productive, but at the same time don't sacrifice maintainability.
You'll find no shortage of opinions of "how you should work" here on Stack Overflow, but the best advice I can give you is to be pragmatic, read as much as you can stand, and code-code-code. I code on the bus, at home, at work, on a plane, in a hotel room, etc. Try out different tools/frameworks, see what their communities say, try building a simple todo-list app, etc. Get your feel for what's out there.
You're on the right path by reaching out to the community.