I'm working in a theme for gnome 42, but i found that many attributes of css do not work. i have the doubt about over what version of css the themes are working, but i can't find documentation. it's a little annoying, because the theme file have 3800 code lines, and create a customization is modify again and again values in the .elements and restart gnome to know what the hell can do the .element or #id in question. in addition not all time the names or nomenclature in the .elements or #ids is intuitive. anyone can help me with any information or documentation? this exist? would be interesting found something that give some more information that about how change the more basic things. I've been working on this for several days, and my theme is almost finished, but there are still many elements of the code that I don't know what they apply to.
Related
I'm playing with Joomla 2.5.9 (The latest 2.X download). Do you know how you can add additional menu's to the "Article Manager: Edit Article" page? (This is in the Administration)
Their API gives me some hint on several things but I am don't know what this right "Slide Down Option Area" is called in the Administration.
In the right area there are things such as:
Publishing options
Article Options
Configure Edit Screen
Images and Links
etc..
I want to know where to start to add my own, or where they are already built in the system so I can base mine off it -- Is this a plugin, module, or something else? :)
As i say don't change any of the core file in Joomla. If you want to add any functionality into the article manager you can make your own plugin to add functionality in it. For doing this see this link :
Creating a content plugin
I hope this is what you looking for.Good luck.
There are some extensions that allow you to do that.
I recommend (although somewhat buggy and a code mess) this one:
FieldsAttach
It does exactly what you want.
Or, you could make your own as Toretto suggests, there are some tutorials on creating a plugin for extra items in the article form, but the already-made-extension route seems to make more sence.
I've been using FieldsAttach for this sort of thing, for a few years, the code is often a little messy, that is true, but the the concepts are clean and eloquent. Brian Teeman explains it well from an integrator point of view in his talk at https://www.youtube.com/watch?v=f2WLKWbRj5U but in some ways it is even more compelling from a developer's perspective.
However, after watching Marco Ding's Joomla Day UK 2016 talk on https://www.youtube.com/watch?v=KDh1IPuZAVA I think DPFields may be a better choice. The architecture is perhaps more rugged and neater, but also because it may well end up being a core extension in Joomla in the near future. More info on DPFields is at http://extensions.joomla.org/extension/dpfields , https://joomla.digital-peak.com/products/dpfields and https://joomla.digital-peak.com/documentation/162-dpfields .
A good number of the tutorials I've found on Magento theme development recommend starting off with using blank as a guideline for making your own custom theme. A lot of these articles are pretty old, as of the current version (1.7), is this still the case?
P.S. - If there are any good/relevant theme development articles out there, aside from Magento's official design guide, please feel free to link them.
In my opinion you should never 'carve out' your own theme from a base theme. You aren't learning theme development in its entirety. You will potentially run into unforeseen consequences. You will likely have excess code and templates by the time you are done.
I wrote a Magento 1.6.1 tutorial on creating a theme that should hold up for 1.7:
http://zaclee.net/magento/make-magento-1-6-theme-from-scratch
If you run into any problems with 1.7 let me know and I'll be glad to take a gander.
I would agree with the above answer in the sense that converting an existing theme (ie a commercial theme you've purchased) to fit a design you've been given or done yourself can be more consuming. You end up doing more deleting than adding, and inevitably end up with a tonne of code that isn't being used (because taking it out might cause problems, the deadline is approaching....sod it, it's only a few Kb, you just leave it in).
However I disagree with the statement that the Magento blank theme will result in excess code and templates. For a start you only pull in the templates you need and the theme is about as bare bones as it gets. I always use the blank theme as a basis. It may well be the case that I am not then learning theme development in it's entirety but the work has to go out, bills have to be paid - and I'm not about to sit and build everything from scratch every time.
To further this discussion, for some time I have really been bugged by the default CSS that Magento ships with. It is a pain to work on, and when you start developing in an environment where multiple people are working on the CSS, you inevitably run into CSS Kudzu.
It's been on my plate for awhile to completely rewrite the default CSS to something more maintainable and trimmed down, but like rabmcnab mentioned, there are deadlines, bills to pay, etc.
I've been searching google for a while to determine the most coder-friendly example boxes.
I'm wanting to share varying forms of ECMA script (JS for example) etc that provides the user with color coding and a simple way of copying the code. I know there are several out there, but I wanted to get some opinions from SOF since you guys probably have good experience with code.
so- What's the code-sharing tool you [would] use?
the solution
I ended up using Gist for complete snippets and am using Syntax Highlighter for *incomplete * code samples. There's a Drupal plugin for the Syntax Highlighter, but I dare say it's more of a pain to figure out the plugin than it is to just do things the old fashioned way (old fashioned being like 5 years ago..)
I use http://jsfiddle.net/
Color coding — check
HTML, CSS, JS — check
Live demo — check
gist has syntax highlighting and users can download the files separately, as a zip archive or using git. You can embed the files easily on other sites.
Additionally, the site tracks changes and other users can add comments or fork a gist to change it themselves.
I know some of the tutorials for creating Xcode project templates, for example this one here: http://robnapier.net/blog/project-templates-364
This is the best one I could find. All others basically repeat the same info, or are no longer up to date, or worse tell me that even they don't know what they're doing. Possibly useful tools that are linked to here and in other places are no longer available.
I keep running into roadblocks, and would like to gather as much information as possible on the process of creating Xcode project templates. Info that is most importantly up to date (at least it must be relevant for Xcode 3 or higher).
For example, what I'd like to see is:
a description of the
TemplateChooser.plist and similar
plist files and what these options do
(in my case, once I add a
TemplateChooser.plist, my project
disappears from the Xcode project
template list)
how to create a project template that references another .xcodeproj (when I do that, the other .xcodeproj appears in the project template list even though it doesn't use the special naming convention)
processes that can be applied, for example is it possible to run a script during the creating of a project from a template? This would be useful to unzip certain files into the newly created project.
If you have the answer or suggestions to any of the issues above, I'd appreciate that. Otherwise any link to good Xcode project template resources would be highly recommended. Especially if there is an official documentation from Apple - I haven't found one yet which seems to imply that project templates are undocumented.
Have you seen these:
http://www.sodeso.nl/?p=895
http://www.codeproject.com/KB/iPhone/CreatingXcodeProject.aspx
If you say you have searched, I'm pretty sure you've already seen the links but these are the best resources I could find with my 'googlabilities'
You might try contact this guy - http://linkedin.com/in/mottishneor he has some related messages around the web
The links suggested by FX are also not bad at all!
There is indeed little XCode template info out there. What I have found of interest are the following links (I documented myself on the topic, but haven't yet gone any further):
a Google Code search reveals a few examples, but not much
in particular, I found interesting to look at the code provided by Three20; they have some basic examples, like here
referencing another project worked for me, so maybe you could open a specific question about that giving more details?
there is information scattered on the Apple mailing-lists
there is no official documentation from Apple, as is evidenced by the lack of results to this query
I'm sorry if this is not a Enlighting, concise answer. As you said, it's not well documented, and sources are all over the place. I just hope I could highlight some places to find information that your own searches might not have reached :)
I don't have a Mac anymore, so this is as much as I can give you without testing this myself. As far as I can tell, Xcode templates are undocumented by Apple.
This guy has some guides for messing with Xcode templates but the info is pretty sparse. My suggestion for working with templateChooser.plist is to try to only edit that file in the interface builder.
This guide is a good example of how to add a reference to another .xcodeproj. For the reason you were having trouble adding a reference to your project we probably need more information.
If you scroll way down in this doc you can that each template already includes a script called myscript.sh. This script will show up in the scripts menu for projects built with that template. That isn't quite as convenient as running scripts automatically, but it's better than nothing.
In conclusion, Xcode template documentation is a nightmare. It looks like there are a lot of powerful features there, but they are obscured because of lack of user friendlyness and because documentation lags far behind Apples updates of Xcode. It just doesn't seem to be a priority for them. I hope this helps.
And yet another video link http://howtomakeiphoneapps.com/2010/10/how-to-make-custom-xcode-templates-with-video/
I want to ask one of those broad questions so please go easy on me. I know that phil is doing well with pyrocms but I would like to use pyro for my sites and also know how to write custom additions to the cms to suit my needs so what bums me out is how do you use it? where do i add my additions? how is it laid out? Like I said before go easy with me cos there is no documentation for pyrocms.
Thanks
I suppose this is one for me then :-)
modules can be added to the system by adding the folder to application/modules and copying the folder structure. To understand the modular structure better read the documentation for Matchbox by Zacharius K. I'm on my iPhone on a train so not going to look I up for you :-)
look a details.XML within the module to see how to set frontend/backend module type and when you have set a module with is_backend_sidebar clear the cache (or wait 6 hours :-p).
Documentation WILL come soon, my Internet has been down 2 months longer than expected so finishing v0.9.8 then documenting the lot will take a while.
Tweet or email me for more help.