Can we use ClouldScribe for non-content scenarios like Classifieds Posting?
Planning to develop a Classifieds Posting web application. Here I want to use cloudscribe's engine and another part (like add posting, listing, search) I will write on my own.Is it possible with cloudscribe or its overkill of cloudscribe ?
You can use cloudscribe Core for management of users, roles, claims etc and then build custom features for anything you need.
The idea is for cloudscribe to provide some things so you don't have to build them yourself, ie user management and role and claim management, so you can focus on what you want to build, ie classified posting application.
cloudscribe puts no limits or constraints on your development approach. You could also use cloudscribe SimpleContent for marketing/information pages of your site if you need that, but you can use cloudscribe Core without using SimpleContent if you don't need that.
Related
Is there are web framework that allows creating of custom Web UI designers that can be embedded into a webpage/webapp?
What I am looking for is to create a web UI that allows users to edit the UI in a drag and drop style editor. It should be possible to select some widgets (like these: http://scaffy.railsware.com/futurico/#pagination) and to select a data source (will be provided by back-end, nodejs).
Background: I am not a web designer and have no previous web experience. I just want to know if it possible to create what I am looking for and how much effort it would be. My background is in embedded Linux development and I would like to create an easy way for people to create machines with single board computers. The embedded stuff is pretty much complete and I am exploring ways to create nice and user editable user interfaces.
I think what you want is possible.
However... as far I know nothing exists which will do exactly what you require.
There are thousands of UI widgets on the Web to choose from but you would need a custom built backend cms developed especially for your needs
There plenty of Web agencies who could provide a bespoke solution. They could also assist with updates and adding new widgets.
So it can be done (and may encounter some browser incompatability issues), but you'll just have to be prepared to spend money.
VS2013 update 5, MVC5 using Areas
I have a stand-alone function programmed for a website. The functionality is a specific user interface to collect survey responses in a particular way. It has several controllers, a model and a group of views. The functionality is completely contained in an Area of the project, except for the Shared _Layout file that provides the main menu for consistency.
'Is it possible for me to' / 'how do I' compile this Area into a single or set of .dll file(s) that I could then add conveniently to other websites? I'm assuming creating something for transfer/download is very standard functionality. For example, I used Elmah.MVC for this site. What I want to do is pretty much create a package that can be downloaded in a similar way to how we integrate Elmah.MVC into a site. (Be certain I'm not talking about creating error logging software, I'm only using Elmah.MVC as an example of software that is easily integrated into other website applications.)
I've never compiled any website functionality into a .dll(s) for use elsewhere and would appreciate either some specific guidance, or perhaps what would be easier is to provide a link with a good step by step tutorial or explanation for how to do this. Most of what I've found on the web describes bits and pieces of doing this, but it's not enough for me to feel confident with it.
It seems to me there are a lot of 'moving parts' to taking a particular piece of an MVC application and turning it into something that is easily added to other projects.
A particular issue I don't quite grasp is the difference in downloaded packages between getting code and getting just the .dll(s). For instance, when I download an MVC5 site, I get controllers, models and views, but when I download Elmah I get a .dll and no code files. Also, I do understand the concept of transforms, but I'm just struggling right now with even getting from my programmed application into a 'package' regardless of the transforms that make it easy to integrate into another website.
These are just some of my questions I have about how to perform this particular process in developing deliverable and/or shareable software.
What you are looking to do is create a portable MVC Area project. A Portable Area is a set of reusable multi page functionality can be dropped into an application to provide rich functionality without having to custom build functionality that is literally the same in every application. An MVC Portable Area is really just a dll that contains the views, controllers, scripts, etc… needed to use in a website that is either a Web Forms website or an MVC website. A developer can use them for a reusable widget or a complete engine. I have actually used them for both. Here is a link with some basic info to get started. http://elegantcode.com/2012/04/06/mvc-portable-areas/
I have an app we've developed that will be translated to tagalog. No big deal, I thought. We've done translation dozens of times. However, apparently this culture is not supported by default. So I looked and found CultureAndRegionInfoBuilder, but that requires admin privileges, something my azure web site most definitely will not have.
Is there a way to use a custom culture without registering it, or alternatively, register a custom culture on a reserved Azure web site instance?
I find it absolutely mind boggling that I might have to use something other than Azure Websites simply because of the lack of forethought and design surrounding globalization.
I know this question is old but I did end up finding an alternative.
https://github.com/turquoiseowl/i18n
It sits outside your app as an IHttpModule that intercepts responses and does localization by replacing screens with a specific delimiter ([[[ and ]]] respectively, by default). It uses gettext/po standards and IMHO, is everything ASP.NET localization should have been from the beginning.
I want to create an enterprise intranet , that provides authentication of employees and management profiles, messaging, calendar, document management...
I think I can use php or java CMS , for the moment after some research I decided to use Liferay or Alfresco. The problem is that I don't really know the difference between them , and what I have to choose .
They're quite different products, solving different business needs.
Liferay
It's a Java Portal. It focuses on creating web sites that are able to integrate data coming from different sources and applications in the same page. Using portlets, you compose a page to enrich it with such mini applications. It's mostly used to create web sites that aggregate information and contain interactive features such as online chat, blogs and the like. It also provides document management as part of its features, with the possibility of integrating Alfresco as a backend.
Alfresco
It's an Enterprise Content Management system. It revolves around documents, their lifecycle and collaboration capabilities over such documents. With the advent of Share, Alfresco now offers a lightweight portal-like application that lets you place "dashlets" in both an User Dashboard and a Site Dashboard (sites are shared workspaces).
While you can have non-document centric dashlets, blogs and wikis, they're not extremely sophisticated, and most of Alfresco features focus on document management and online collaboration.
I have not worked with portals for quite a while, but I guess the answer is : It really depends. :)
Seriously, in your requirements context I would compare Alfresco Share with Liferay. Both compose pages in a similiar fashion with Webscripts/Portlets components and have security baked in.
I think the most important factor to consider is your skill set.
If you feel at home with Java, the Portlet spec and server side logic : Lean towards Liferay. Alfresco Share/Spring Surf should serve you better if you prefer Javascript in the browser and JSON/REST style programming.
Besides, validate how strong your document management requirements are.
Do you really need super sophisticated search, workflow, versioning, security and the like ?
Sophistication increases complexity. That is also why I would be careful before introducing them both at the same time.
Another point to have in mind may be documentation - guess this point goes to Liferay.
Liferay's primary strength is as a portal where you use existing "applications" to fit your need, or create your own using the Portlet spec. Alfresco is a CMS, so it focuses on content management.
Why not use both?
A client wants us to develop a Picture Library system for them. The requirements are pretty typical - need to add pictures, tag them with metadata, store different sized versions and so on.
The client is keen on it being developed as a component which plugs into their existing SharePoint system. However, my feeling is that we would be better served building a standalone app - that way we don't have to shoehorn it into a SharePoint page and muck about integrating with SharePoint's APIs.
I am trying to look at this objectively and would welcome any arguments either way that people have.
Using an existing framework like Sharepoint imposes a lot of constraints on the design which makes the software architecture more uniform.
It does require some work on the part of the developer, because the developer does have to understand the API architecture and API's, etc.
However, developing a standalone application is the way that business's software architecture becomes a mix of 200 applications, using 20 different languages/architectures/platforms, half of which were developed by people no longer there - in short, a mess.
Sharepoint is documented, and will be supported probably long after you leave the company. Can you guarantee support for the application that you develop for as long as Microsoft will support Sharepoint?
You should do a cost/benefit analysis of integrating with SharePoint. You have listed some cons for integrating with SharePoint. Here are some pros.
Widely adopted platform.
Existing functionality to store/retreive/update images to data store.
Existing functionality to tag images.
Existing functionality to group several images together and treat as one virtual document (if using SharePoint 2010).
Keep in mind that you can integrate any custom ASP.NET page/application in Sharepoint so you can approach development like a standalone app. Your client wishes might include synchronization with Sharepoint's own picture library functionality and in that case you'll have to work with it's API.
It seems with SharePoint you are already done because it can more or less do what you describe already. What requirements do you have that cannot be met by OOB SharePoint?
I've used picture libraries for something similar before. While they have their quirks you do get a lot 'for free' like a UI, bulk uploading, metadata and 2 alternate sizes rendered.. My biggest gripe is they don't support the datagrid view so I cannot edit list metadata en masse like you can with other list types.