My goal is creating help section like on http://www.telerik.com/help/aspnet-ajax/introduction.html with cascade menu folding on DotNetNuke. Should I use DNN standard tools or special module?
Thank you in advance.
There are a number of ways of doing this, however, the management overhead is really going to dictate how to do this.
One option would be to simply create individual pages for each section, then create a skin with the proper menu style to handle the left side process. Honestly, this is the "easiest" way of doing it. But if you have a lot of documentation this could take a while.
Another option would be to see if there is a way to re-purpose another module to help with this. News Articles from Ventrian with Categories could help, but you would need a fair bit of work to get the "Tree" style behavior to the left.
I would probably start by looking at the News Articles module from Ventrian for a project like that.
Related
I know that DNN doesn't support inserting of one module inside another one. But I wonder if 2sxc module has workaround for it and just like you can, lets say, insert gallery application in blog post content, is there a way to insert there external module object?
The short answer is no. 2sxc doesn't have this functionality built in.
BUT: DNN does have some APIs to do this - there were modules that did this kind of stuff. So I would continue in the DNN APIs to figure out how to do this.
I believe that the answer is yes, and that you should take a look at https://docs.2sxc.org/api/dot-net/ToSic.Sxc.Dnn.Factory.html. I think that you should be looking at CmsBlock.
Some other references:
https://docs.2sxc.org/specs/architecture/data-flow.html
https://docs.2sxc.org/api/dot-net/ToSic.Sxc.DataSources.CmsBlock.html
I've never done anything like this, and I'm not really familiar with the content on this page. Perhaps Daniel and give us both some pointers.
I posted a question on the Drupal forum about whether I should build my database in Drupal using content-types or the database abstraction layer and schema module: [here][1]
Any advice would be greatly appreciated.
[1]: https://drupal.stackexchange.com/questions/98020/should-i-use-content-types-or-database-abstraction-layer
I'd recommend using content types.
For a PHP coder, sometimes using the Drupal User Interface to build things feels non-intuitive, but in the long run you're going to benefit a lot from doing things "the drupal way.
Once you reverse engineer your need into a content type and all it's associated fields, install the modules that provide those field types and set things up, you'll start to see the benefits.
Validation on all the data-entry froms will already be done for you.
Multiple display modes are available for your data (email addresses can be shown with or without mailto: links, images can be shown using any of Drupal's image styles)
Integration with other Drupal modules already exists, and will be supported (almost anything built with fields is available to views)
By writing your own schema you'll need to handle all these things yourself (and more), and not just once, but you'll need to maintain all that custom code over time.
Learn to leverage the community and all the great work that's been done already, you'll save yourself time in the long run :)
What i see you are going to have shop site.
You may tray this:
https://drupal.org/project/commerce_kickstart
, i've found it usefull once. It's drupal distribution with nice themed shop rady to use straight forward.
And of course do it with content type + views + entity reference modules.
Here is a link to a comment that answers the question I asked. It backs up what arpitr outlined in their answer on the orignal post on the drupal forum, whose answer is also in agreement with jenlampton's suggestion above.
https://drupal.org/comment/7848011#comment-7848011
I will implement my system using node entities until the need arises to build a custom entity (if it ever does).
The top answer in this forum give a good way to evaluate whether to use nodes or custom build an entity:
https://drupal.stackexchange.com/questions/22586/when-is-it-appropriate-to-create-an-entity-versus-just-adding-a-new-content-type
By good, I mean using hooks/filters.
Basically, by default the two options are Images and Uploaded to this page. I would like to add an additional option in there. I know how to add a new tab to the media manager (see here), but that doesn't achieve what I need.
I've been looking through the limited documentation on 3.5 and have found the media_view_strings/settings filters, but, based on what I can tell, neither could be used in this case. I've also done quite a bit of digging through the core source, but the number of files relating to the media uploader is daunting to say the least.
I thought about running JS after page load to modify the DOM and just add the extra select option in, but this seems very hackish and I'd like to avoid it if there is a better, more robust solution.
Any thoughts on the best way to approach this would be greatly appreciated!
Note: I didn't post this to the WordPress SE Site since it gets much less traffic and the questions tend to be much less programming-related.
Most of those select-dropdowns are from wp-includes/media-template.php, which has a lot of Underscore templating (<script type="text/html" tags), but few action hooks for php code. With Javascript you can bind the Backbone.js hooks for wp.media events, such as wp.media's open/close events. From such event you could grab that Images/uploaded-to-page selectbox with jQuery('.media-modal-content:visible .attachment-filters'), add item(s) and listeners as needed. I'm pretty sure there should be a much better Backbone.js-style solution, though.
Here is a tutorial by Shiba Shake on this subject ...
How to Expand the WordPress Media Manager Interface
Hope this is helpful to you!
In my search for a good social login package for App Engine, I am giving gae-boilerplate a try. But I find there is no documentation except the readme file, which I think it is not enough at all.
I have many questions, among them:
Should the boilerplate be used as a library or download and modify as needed?
How should the boilerplate be updated?
What does each model do?
Where should my templates go?
Should I have a different routes file?
Should I derive my Handlers from BaseHandler?
In general, what things should I implement in my pages? For example, I found out that I have to include a csrf_token in all POST requests. It would have been nice to know this in advance, and the many other things that I'm having to find out along the way, and which I implement without being sure if I'm supposed to be doing that.
And some more...
My biggest problem is that Social login is not working, and I feel this boilerplate is a big monster with which I don't know where to start. To make things worse, it is hard to debug social auth from any machine that is not the production one. Thats why I'm desperately looking for some docs.
I have not found anything in SO, and I guess there must be more people in my situation. So, any pointers to documentation that could help to understand gae-boilerplate a little bit better would be very appreciated.
EDIT: I switched to gae-boilerplate in a site that I had previously working. Maybe most of my problems come from the way that I have tried to integrate gae-boilerplate and my existing site. As a result I have tried to treat gae-boilerplate as a library, and keep my own templates, handlers, static files and such.
Thank you guys!
EDIT 2: After trying other options, I have to say that I am very happy with gae-simpleauth. It works really well, and Alex's support is superb.
I will try to answer most of your questions below:
Should the boilerplate be used as a library or download and modify as needed?
You can modify it as needed based on your specific requirements.
How should the boilerplate be updated?
What do you mean?
What does each model do?
User and SocialUser are pretty self explanatory. LogVisit and LogEmail are used for auditing purposes.
Where should my templates go?
In the templates directory
Should I have a different routes file?
No, you can use the existing file for all your routes.
Should I derive my Handlers from BaseHandler?
It't not mandatory but I would recommend to do so. BaseHandler is very handy and provides a lot of good stuff.
In general, what things should I implement in my pages?
What exactly do you mean?
In general, you can use gae-boilerplate as a reference on top of which you will built your own project. Study the code step by step, try to figure out what is the purpose of each file and library used and how they work together. This way you will gain good knowledge of a lot of things like jinja templating, oauth2, etc.
Hope this helps.
I'm just starting up a new, big project that will be using WPF for the front end. I'm looking for some kind of solution for an integrated help system. The basic use case for this is that the user needs to be able to reach context sensitive help at any time when using the system. The help content should be localized and displayed within the application (not popup an external .chm file).
I'm looking for real world experience in creating and/or using a third party system that can handle the complete flow for this, including a work flow for localizing the help content. Any input is appreciated! Thank you.
One suggestion is to compose help as FlowDocuments. They're simple to compose (and you can whip up an editor using RichTextBox. They can be stored as resources in your assembly and you just use a FlowDocumentReader to view them. That basically lets you fully integrate help into your app the way you want it without needing any external tools or controls.
How about using tooltips ? Wpf tooltips can have any kind of content... can't think of a more integrated help system ;o)
Here is an article by Pete O'Hanlon Easy help with WPF
I suppose you can customize this solution to fit your needs.
Is there a particular reason that you can't popup an external .chm file, or is it for aesthetic purposes? If you must wrap your own implementation, you might want to look at this article on Code Project. It's not WPF specific, but it should serve as a real starting point for you.