This might be a general question, but I can't seem to figure it out. What are containers in DNN? Skins are essentially a layout plus a colour scheme for the whole portal. So are containers the skin for desktopmodules?
Sorry if this question is novice. I am not confident in DNN yet, and am reading the doco. However i need this answer quite quickly.
Cheers.
Containers allow you to add style and markup to any module independently of the page skin or the particular module.
The layout goes like this:
Default.aspx
Skin (.ascx control, either the
Portal default or selected on the
given tab) - this has panels on it
Container (.ascx control, this can allow you position some edit
buttons and have a configurable wrapper around any module)
Module (.ascx control, usually coming from /DesktopModules)
I hope this helps,
-Eric
Yes, container is like a skin for single module. Using one skin for entire page, and several skins (container skins) for modules you can quicker create expected appearance.
In general this is a simple html snippet with several placeholders.
Related
Is there any best practices?
Say, I need to develop a flip-flop block with title/icon on front and text on reverse side.
And I want that user can simply insert that block in a grid. With params, I said above.
From here - I see only macros-way (simple). I mean - develop each block in macros, so umbraco-engine can paste it (macros) to grid "from-a-box". But, I don't believe it, I can not even create a folder from backoffice for macro!
Harder way - dive into custom property editor, many setups, many moves. And I don't sure - can I paste result into grid?
I see, that people talks about some great package that called "ARCHETYPE", but project is closed for now... Should anyone bet on that?
Which way is right?
If I understand correctly, you are using Umbraco Grid and want to create a custom grid edtior. If that is the case, I would recommend you looking into LeBlender. It basically enables you to create grid types in the same way you make document types, including templates.
I am developing a jsp web application, no framework (sadly...), that will be used for differents customers. Each customer have their own set of colors and company logos.
The css layout will not change, only some divs colors, font colors, button colors, so and so.
I trying solve this problem implementing a filter that receive a general request and then redirect the request to correct folder depending on the customer.
By example, the index.jsp request css/index.css, then filter verify the customer and then change the request to 'customer1_css/index.css'. This works fine, by now...
But, when I need to add or modify some css element, I have to do it in each css file of each customer.
I want to simplify this process for us and the web designer. So, I though in using FreeMarker, parametrizing all dynamics elements, and make a db table where I put each parameter value. But is very cumbersome.
I know that I am not the first developer with this problem.
Please, give me some ideas for solve this.
Thanks in advance!!!
I would stay away from generating the CSS dynamically. If you change the layout of the page so that it requires a change to the CSS, there's nothing you can do but make all the changes in the CSS files. How would you stay away from that by generating the CSS dynamically? You'd still be restricted to only changing the properties (class names, ids) you've decided upfront.
A better solution involves writing semantic HTML, that is, improve your HTML so changing its layout doesn't require as many changes to the CSS See How to avoid locking my HTML structure when using jQuery to create rich client experiences?
I have made a couple of simple Joomla websites before. Those are using a custom template made by myself. They are easy websites as they have a simple linear menu, all pages have the same layout, just some articles are changing between pages.
But in my new project, I have a ready html website that I have to convert to Joomla. The problem is, there is no one repeating menu and there is no consistent layout. To simplify a bit: there are 10 pages and they all have different layouts. Between pages background changes, menu position changes, menu content changes, content box positions change, everything changes. This means I'm not able to do this site as I've done before, using one template index.php which simply contained my repeating page structure.
I am dreaming of a way to simply change ready_page1.html to ready_page1.php, adding some modules inside the php (which are then available for online editing, which is the reason switching to Joomla). I would do this to each page. The custom menus inside each page I would "manually" point to the according php files instead of the old html files. Is this method possible somehow? I couldn't figure out how to do this.
I don't care loosing lots of Joomla basic functionality due to this crude method, I just want the simplest way to do this.
In the end, I just want the exact same website I already have on html, but I want some chosen rectangular areas in the html pages to be editable Joomla modules. The modules would have the pen icon for editing. That's it, no other functionality is necessary.
Sounds like the site you are converting is a usability nightmare. Consistency is part of giving the user a positive experience. That said, if you have to make it exactly the same, then the easiest way is to do it the right way to begin with.
First, you need to learn about page class suffixes. You can add those to a menu item so that you can control the CSS on a per page basis. This will allow you to change backgrounds and other elements on each page.
Documentation - http://docs.joomla.org/Page_Class_Suffix
Next, you will need to make a template so that each of the module positions is collapsible. If you plan out the positions, you should be able to use a single index.php for the entire site. We have a custom template that we use for every site we do and it rarely needs to be touched because all of the positions we would possibly want to use are already there, they just don't get used until a module is put in the position.
Documentation - http://docs.joomla.org/Collapsing_columns
You will also want to make sure you understand menu assignments. You should be able to assign the modules to the pages as needed to create the layout you want for each page. If you are using 2.5.x, then you can probably get by with the built in menu assignment features. If you are using 1.5.x then (you really should upgrade) you will probably want to use Advanced Module Manager as it makes menu assignments much easier and more flexible.
Documentation - http://docs.joomla.org/Help15:Screen.modules.edit.15#Menu_Assignment
Once you get a good grasp of how Joomla templates work and how they are supposed to be used you will find that you can basically do anything you want within the framework so you don't lose any functionality.
build your website and create those 10 pages (contents, heirarcy, and so on..).
then create your templates based on those html files. this is where you adapt the html into a joomla template. after this step, you should end up with at most 10 templates depending on your styles (crude but quick)
as far as i know and from the documentation, Joomla 1.7 supports "template per page" (see the screenshot). you can pick out which style will be applied to which item. it even applies to subpages. another documentation here
I've created a number of skins for various components recently. Some of these were for Spark components and the default behavior of Flash Builder is to take the source code of the original skin and copy into your skin as a starting point.
Normally, I am 90% ok with the original skin, I just want to tweak or add one little thing. It seems to me that duplicating 3 pages of source code to do this is a bad idea. What do I do when I upgrade Flex SDKs? Do I have to go back through the source of all these original skins and (re)compare? This sounds like a disaster.
Is there a way I can create a new skin in MXML that inherits from the old skin? Can I do this via ActionScript?
If you upgrade your Flex SDK I don't think there should be any modification in the skinParts of components. Anyway if there were, you would have a compilation error if one of your implemented skinparts is not of the right type or if you miss a required skinPart. So I wouldn't worry if I were you :)
Another tip would be to use as much as possible CSS styling to avoid this kind of problems.
And no, I don't think you can inherit from a skin and modify its elements (but I'd be glad to be proved wrong).
I required to write a small web application that allow customer to select predefined layout template in html and be able to modify it. The application need to allow customer to add block text to pre defined area and images. The block texts need to be able to reorder based on customer need. eg. move up , move down or move to sidebar. THe complete layout will be able to convert to table layout and inline css due to email program doesn't like div & css. I don't know where should I looking for the information to make this happen, could anyone show me how to do this.
Thank you
Of course, I may be misunderstanding you. You might consider using a standard content management system such as:
linux based
joomla
Mambo
Windows based
DotNetNuke
Sharepoint
Those systems have the functionality you described built in with the added benefit that most of them are free and open source.
I'm not sure why someone downvoted you, but check out a javascript framework like script.aculo.us or Yahoo's YUI
Those will go a long way towards creating the interface you need. Also they have a lot of examples.
The Yahoo framework has an inplace html editor (I think that is what you are asking for). Another editing is the fckeditor.