I am trying to extend the Multi Node Tree Picker (MNTP) in Umbraco but am running into some trouble. I am used to writing property editors in the new umbraco 7 angular style, so the MNTP is a bit foreign to me. I want to be able to connect my uCommerce Catalog Tree to the MNTP. I feel like this should be fairly simple as all that I should need to do is hook up the uCommerce tree to the MNTP. I am in the Umbraco.Web.PropertyEditors dll, but it isn't really helping me too much. Any pointers to get me started in the right direction would be much appreciated. I could then share this as a new package if I can get it working.
Thanks!
I would recommend creating your own property editor that simply uses the Umbraco dialogService to pick the uCommerce product.
You can use the Yo Umbraco template generator to build a scaffolded package:
https://github.com/warrenbuckley/generator-umbraco
Related
VS2013, MVC5, VB
I am nearing the completion of a small project to manage the roles tables in a standard MVC5 application. The code is pretty much encapsulated. What are my options for using this 'package' in other projects?
Can I compile it into something? I know this type of action is possible, I'm just not familiar with the options available to me or the steps to do this. Links to sites that have tutorials are fine. Is creating a Nu Get package the only way to go, or is that even in the ballpark of what I'm asking. I say Nu Get, but I don't mean for public consumption, only for my consumption.
Will the finished 'whatever' include it's controller class, view models and views? Will I be able to easily manage updates? etc.
Creating a Nuget package is one way. I have created a local repository of common utilities for this purpose. But I usually use it just for DLLs. I use Nuget Package Explorer for its ease of use since its just me using the packages most of the time. Not sure its possible to place the files in specific directories.
Files in the content folder are copied to the root of your application when the package is installed. - Nuget
The alternative is to create an item template. I used to use this method for class files I want in my code but I can't see why you couldn't do it for the rest. Works well and isn't too hard to set up. There are dozens if not 100s of tutorials on the subject. Here is one on code project.
I need to create new version of my current project - take all features and rewrite it, add new features.
What tools or gems do we have for Rails project to build for me some kind of catalogue of existing features? Maybe in form of models and associations between it or some kind of graphs.
After it I will be able to customize such information for my needs. Anyway it should be simpler than go through all code and make it from scratch by myself.
All help appreciated.
I found such gem for my case:
https://github.com/voormedia/rails-erd
It's not totally what I was seeking for, but still useful.
I'm hoping someone can shed some light as to why this is happening. I've just started creating my own packages in Umbraco and am having issues with something that should be quite straight forward.
I've created a fairly simple package consisting of a Content page and child pages, doc types, templates, some css and some scripts. I install the package on another Umbraco site and all seems fine. The problem is when I come to uninstall the package, it is trying to remove its parents Document Types, which it cannot do, and it's shouldn't do as these were not in the original package I created.
What am I missing here people?
Thanks in advance!
The package manager will attempt to package up all required dependencies.
When you created your package did you select doctypes that were nested under the parent doctype? If so this is probably why as the parent doctype then becomes a dependency and most likely was actually included in your package. It should be pretty easy to see from the uninstallation page what it is trying to remove and if that doctype is listed it was in your package.
We are currently looking at the newest version (2.60) of NopCommerce in MVC and we will be integrating it pretty soon…We’ve downloaded the Source Code and paid the 20$ for the User Guide documentation. The documentation is great! I mean…it is great in the sense that it explains how to deploy, install and how to work around the UI Frontend and Backend. This is great for an overall overview but what it lacks is the understanding of how to work with NopCommerce as a team. What are/is the best practices etc...
As an example (or parallel), if you decide to work with Dotnetnuke as a team, you usually work in the following fashion:
Each developer downloads/installs Dotnetnuke locally on their
machine.
You also download/install Dotnetnuke on a dedicated server (let’s say
dev-server).
As a developer, you work and create modules which you test locally
within your Dotnetnuke installation.
Once it is done, you package your module (and any SQL scripts that
comes with your module) into a zip file.
Once the package is ready, you upload/install that package on the
dedicated server (dev-server).
This approach works great for Dotnetnuke and more importantly if you have a team of developers creating modules.
My question is how does a team work with NopCommerce MVC?
I’m assuming it is a bad idea to directly work within the source code in case your team decides to modify core elements/source which will make any upgrade to newer versions impossible (or break changes).
I’m not sure if my parallel to Dotnetnuke is a correct one…but would anyone have any idea (or help me clarify) how does a team work with NopCommerce MVC.
In addition, should the team only rely on creating plugins for NopCommerce and stay away from modifying the core or should this be irrelevant?
What about adding new objects in SQL (or modifying existing ones) should we prefix our objects in case an eventual NopCommerce MVC upgrade creates similar objects and/or overwrites them?
Thank you for helping me shed some light on this.
Sincerely
Vince
Plugins in NopCommerce are almost like modules in DNN. Depending on what you need to do, it sometimes is necessary to modify the core code.
What I've been doing for the Services is create a new class and inherit from the existing service, then override the function you want to change. Create a new DependencyRegistrar class and set your new service classes as the implementation for that particular interface. Also make sure the Order property is 1 so that your DR class is loaded after the stock one. Since you're inheriting from the core class, any functions you didn't override will be handled by the parent class. If I need to add a new function, I'm just modifying the interface, putting a stub in the stock class, and implementing it in my own.
Views in the Nop.Web project can be overridden by Themes. The Admin stuff and the Web Controllers get trickier. I'm just modifying those files directly.
The Core and Data classes can be done using partial classes to add your new fields.
In any case you will still need to merge changes with your solution when an update is released. My opinion is that you are better off writing clean, readable code now and bite the merge bullet when it comes.
I don't really worry about SQL scripts right now because I'm a single developer but maybe you add a folder for ALTER scripts and name them after the day they were created. Then each dev knows which scripts they need to run when they get latest.
I wanted to know if there were a Canvas external library for DART like Fabric.js ?
If it doesn't exist is there a project to make one ? Cause I'm thinking of starting this project, but I would prefer joining a existing project on GIT.
Or maybe there is things integrated in DART that I don't know ?
I've not worked with Fabric.js, but after taking a look at the website, I'd point you to the projects listed below. Neither project is exactly what you are looking for, but should give you a starting point.
2D (Flash object model) - The project changed to StageXL
https://github.com/bp74/StageXL
WebGL
https://github.com/johnmccutchan/spectre
I don't know of any serious Canvas abstraction libs for Dart but maybe these two projects could provide a good inspiration foundation to create one.
Drag & Draw approach
Animation approach