I have a form which I would like to reuse across multiple projects. I add the form into the projects by linking them, therefore have one version with one set of changes which will affect all the projects.
My problem is that the form will display the images in the original project, but in any subsequent projects, the images on the toolbar have disappeared.
Do I have to add the images into the resources (which doesn't seem to work)?
Related
Usually I see myself developing a component in react, for example, and every time I edit this component I need to edit also related files like css ones or inner components. I, moreover, like to have this files organized in different panes, see the image for an example. Do you know if, while working in my project, can I open/close this whole pane/files configurations? Thanks!
How about this: https://atom.io/packages/save-workspace. I don't think it is quite what you were looking for but it should work - instead of providing tab configurations for a specific project, it keeps a global set of configurations including open project directories, tab/pane configurations, and active cursors.
I've made 2 custom builds of CKEditor for my CMS:
For general purposes
Just for creating of maps with Leaflet plugin
In general every page can consist of several "general" CKeditor blocks (and all is OK here). But some pages (like "Contacts", for example) can also contain "maps" instances. The instances are totally independent, it's not the same repo with different configs, it's 2 different builds. So I need to connect some textareas with the 1st build, and some with the 2nd. Is it possible?
Screenshots are attached below:
Folders with different repos
Maps editor
You can't use different CKEditor builds on the same page. There's only a single CKEDITOR namespace, so there's no way to tell apart which build do you want to use.
Instead, you should use the extraPlugins and removePlugins config options to adjust each instance the way that you want.
Please I need some guidelines (or link of tutorials) in creating Joomla (3 - 3.5) website with the purchased template design. I wonder how professionals with experience are solving my doubts in practice.
Do you recommend the installation of the purchased blank template with a single installation and configuration of modules and components or installation of template with demo examples (Quickstart)? I know the differences but I was wondering how you are doing.
Till now I've almost always used the Quickstart installation.
I wonder if you clone the main menu (and other navigation and modules) and than you rename a copy for your needs and you change the content or you delete all navigation items except Home and than you are re-creating items according to your needs.
I'm not sure if I can copy the main menu or I copy only his necessary items and than delete overage of template.
It happens to me sometimes if I click on some of category it leads me to the main menu from original item, not to the desired custom copy, even though the path is set (the default items). Therefore, I am not sure which is better... copy main menu and items or to delete all navigation and content of the Quickstart installation and form my own navigation, content and modules.
In short, how to sort out all unnecessary items, and those that I am using should I copy and modify, modify existing, or delete all and make my own needed items.
I believe you will know my concerns.
Thank you and regards,
John
I have created several websites in Joomla with blank template and also with quickstart package.
Advantages with Blank Template
You will get the core theme without any unnecessary content and
basic modules and plugins. You dont have to delete any
contents/articles later.
You will be having authority to place modules at your desired positions. To check the modules position at the frontend simply do this http://example.com/?tp=1.
Disadvantage of Blank Template
There are some module style settings embedded in quickstart package that you wont be able to set yourself without going through full documentation. So sometimes your menu seems distorted.
Disadvantage of Quickstart Package
Deleteing unnecessary articles, removing unnecessary modules is a big headache.
Database size unnecessarily increases.
Steps I follow
I create a quickstart package in localhost and create a blank site with blank template in live site. Whatever settings I need I copy from the local website so that I am saved from removing unnecessary contents from live site. Also sometimes deleting some contents give rise to some other issues. Its better t go with a Blank template.
I have a WP7 application which I need to rebrand. I'm using Visual Studio 2012.
My problem is how manage brands in the most automatic way.
Lets say I developed the app for the Main Brand, and I need to restyle for the Secondary Brand.
Secondary Brand consist in change of Images and part some base styles (the base style are used and thus referenced by other style and templates which are shared).
I would prefer to have the XAP with only Images for its own Brand.
I need also to have the possibility to use the designer with one brand or another.
I tried to use a TFS Branch for this purpose, it is satisfing but at every merge (new features or bug fix in the Main Branch that must be merged in the Secondary Branch), I need to pay attention to not overwrite Images and Styles (if changed), it is an error prone process and lead to undetected and critical mistake.
I thinking about bring everything back on the main branch and manage Brands by moving all Images and Style that differs, into different 'theme' class libraries but how can I easily switch between references (I need the designer, so at design time) ? Is there a way to have different references for different solution configuration ?
Another option could be to use the Branch and the 2 theme class library, in the secondary branch the app will reference the secondary theme class library. On the paper it seems the best options, both branch will link statically the resources, they will have their designer branded, merge should not impact anything modified in the 'theme' libraries. Before try it i would like to know if anyone has a better option or foresee any problem on this.
Thank You.
I had similar project, and I can share the way I was trying to solve it.
I had following project structure
AppName.Common - here all common code, views and data templates defined
AppName.Main - here is App.xaml for main project, Resources with specific styles and images
AppName.Branded - here is App.xaml for branded project, Resources with specific styles and images. Also in App.xaml I configure IoC container, because some of behaviors were different for Branded and for Main proj.
All styles are defined in App.xaml in Resourced dictionary. So, in runtime app can resolve them. Sometimes you need to reopen solution, and also ReSharper can't support in, it fails to resolve you styles.
Blend for VS can support this structure. You just select current project as a Start-up proj.
Hope it will help you.
Don't forget, that if you navigate to View from other assembly, you need to change path.
I am a newbie to Joomla 1.7 & Virtuemart. I have used many CMS so far and in Joomla I need to do very common task. I need to have different layout for homepage, for product list and product details and so on. Every single page is generated from index.php which is in *joomla root/templates/my_own_template/* folder.
And one more question. Is there any Virtuemart 2.0 or Joomla 1.7 documentation? Because what I could see is that the versions are really different from old ones for which most documentation are written.
Thank you in advance for answers.
You're probably not going to find much documentation yet since that is usually the last thing that a developer does once the code is out and tested.
As for changing templates, you don't necessarily need to change templates to have different layouts. First, VM has several different theme files (theme is a VM template) that render the various pages. There are already different layouts you control in the admin. You can also change a particular page by adding or removing the various modules from pages. You can associate a module with all pages in the site, a selection of pages, an exclusion of pages, and no pages at all. Components like Advanced Module Manager give you even more control over where and when a module displays. A properly coded template will have collapsible module positions. So a page with no modules in the left column will not have a left column.
Lastly, Joomla 1.7 also allows the use of template styles. When you install a template, it creates a default style. You can duplicate and edit that style, then assign it to various menu items to achieve very different looks from one page to another. http://docs.joomla.org/Help16:Extensions_Template_Manager_Styles_Edit
Brent's answer is good – he's right that the look of a page can be determined by which modules are assigned, which VM layout is used, and by assigning different Joomla Templates/Styles to different menu items.
One issue that arises a lot with complex components like VirtueMart is that it can be awkward to assign different templates (or modules) to different menu items. This can mess up your menu structure, and there are times when VM will decide on a different menu item to display something rather than what you thought it should. So that messes up the modules and templates/styles. This is part of the down-side of having a menu-item-driven assignment system.
AMM is good for assigning modules to different pages independent of menu item - as is MetaMod (which has explicit VM support).
For assigning templates/styles to different pages in VM I would suggest Chameleon. Chameleon has form controls for selecting lots of different factors about VM (e.g. all the sub-page types, category of the item, cart contents and more) and you can use any of those factors to trigger a certain template/style. It can also trigger other actions like adding CSS/JS to the page, removing arbitrary menu items, switching the home page, etc.
So ultimately, using Brent's techniques and with Chameleon, MetaMod and/or AMM, you have a huge amount of control about how individual pages in VM look.