Alright, so since PHP 5.3, users can define anonymous functions. One way which I use anonymous functions is by storing them in an array:
array (
'protocol' => function() {
echo 'something';
}
);
However, Dreamweaver CS5 doesn't like this and throws me a syntax error and it is quite annoying when trying to find other real syntax errors that might occur on my code. Is there a way to add new syntax into Dreamweaver's configuration and ignore this?
According To This Link at Adobe Forums Website
Dreamweaver supports any version of PHP. However, Dreamweaver's code hints support only PHP 5.2.
Dynamic Code Hinting in DW CS5 supports PHP 5.2, but DW CS5.5 supports PHP 5.3.
Related
Is there any standard (possibly created after-the-fact) that governs <!DOCTYPE NETSCAPE-Bookmark-file-1> files? If you export bookmarks from either Chrome or Firefox (tried on Windows 10) you get this kind of file, which seems to be HTML of sorts.
I've tried searching the web but found only pragmatic results like parsers in specific programming stacks, or tips and tricks on importing and exporting it.
Is there any standard, RFC, format description, or reference parser, or something similar?
Not even valid HTML it is, neither technically, nor semantically. And it seems that modern browsers interpret the factual standard loosely when writing such files, but luckily also when importing.
The best available format description (probably reverse engineered, yes) seems to be this one:
https://learn.microsoft.com/en-us/previous-versions/windows/internet-explorer/ie-developer/platform-apis/aa753582(v=vs.85)
And it's by Microsoft of all things...
I'm having some trouble with Pattern Lab 3 plus Twig.
Following the instructions at https://patternlab.io/docs/installation.html:
I install with: npm create pattern-lab.
I choose Twig (PHP) as the templating language.
I choose Twig (PHP) demo patterns (full demo website and patterns) as the the initial patterns
I do see the note The PHP version of Pattern Lab is being deprecated in favor of a new unified Pattern Lab core. The PHP docs for this topic can be viewed here.. Clicking on the link just takes me to installtion page for PHP edition of PL v.2. Not helpful. So I press on to https://patternlab.io/docs/generating-pattern-lab.html.
Next I'm supposed to run php core/console --watch. There is no core sub-directory. Things are not looking promising.
I remove my PL installation and try again with handlebars templating. With one exception, all is good. The exception: I wanted twig templates.
Ideas?
Indeed, the PatternLab website you saw around the time you posted this still reflected the 2.x/3.x days. Work is being done to get the legacy out and the current state in.
Last month, I contributed to this package: #pattern-lab/engine-twig. This engine is a pure Javascript based twig engine which prevents the need for PHP. It uses the Twing library under the hood (since v5.8.0). There are still things to iron out, but I welcome you to try it. Please file bugs here:
https://github.com/pattern-lab/patternlab-node/issues
I look for a tutorial, help or an example that tells me what I have to do to write a grid element like 2-colums in basic typo3 (v9) with fluid but no other extension like gridelements, DCE, Templa Voila, etc. I want the same gridelements can do but I dont want to be depended to this extention and move it in my own site extention.
I tried the same with normal content elements (CE) like here:
https://docs.typo3.org/c/typo3/cms-fluid-styled-content/9.5/en-us/AddingYourOwnContentElements/Index.html
But how can I nest a CE in a CE? And how can I do this by drag&drop in the backend?
You can't. The page module doesn't support nesting
You can't nest CEs in a CE. On database level this would mean that you have to make a tt_content record a subrecord of a parent tt_content record. You run into several problems, basically the multilanguage support will be broken and the shortcut element does not function as you will expect it to. That is why the extensions "gridelements" and "mask" exist.
I integrated the gridelements configuration into my sitepackage. So I do not need to bother anymore with it.
Just for your info:
There is now an initiative that works on integrating this functionality into the core (Structured Content Initiative, https://typo3.org/article/a-structured-content-initiative/). Stay tuned to it.
There is nothing special about providing Gridelements via external files, since it's based on TSconfig, TypoScript and Fluid. That's why there is not that much about it in the documentation, since it's the same thing you would do with any other kind of sitepackage. The TSconfig and TypoScript parameters are already explained there, while the Fluid would be up to you anyway.
To have a kind of kickstarter just take any extensions providing Gridelements layouts as an example. A very popular one would be bootstrap_grids, which can be found in the TER or here: https://github.com/laxap/bootstrap_grids
You don't necessarily need the flexform controller of that extension, but the Configuration and Resources folders, show you how to configure stuff and you can see how that is included via ext_localconf.php
There are even comments i.e. in the TSconfig files to explain what is possible there and how to handle i.e. mixed environments with record and file based setups. Although it would be recommended to go for files.
You would at least have to add the necessary backend rendering methods to a draw item hook, that will modify the preview of the container element.
So basically you would have to rewrite everything that DCE, Flux, Gridelements or other similar extensions already do.
Which brings us to the question, why you want to avoid those extensions, since especially those three are well known, widely spread, well supported and available for currently supported TYPO3 versions.
I have tried any posible way of importing this framework in my custom extension keyboard, but I have failed all the trials that I think is possible.
1st.
I have tried it in full swift code, importing that framwork using bridging header. But, Most of its command isn't compatible with swift, got an error in enumeration -> NSUInteger in ObjC -> swift always complains, can't even use convert type.
2nd
I have also tried full Objective-C coding. Implementing its function was easy task. But Fails to use this framework. Can't import it in extension App. I have also use bridging header but got an error. "File not found" even though if you do command click, you'll be jumped to its framework. (means indexing is success. and xcode find it clear.). In the end, I think this framework doesn't work with extension, so far.
so, Any idea of how to implement this correctly? advice will be appreciated. Thanks in advance :)
I'm making extensive use of Markdown in a new project that I'm working on, and I would love to be able to configure an AutoMapper convention that maps all instances of Property X to XMarkdown, and converts the resultant output to Markdown.
So, if I give any destination string property the suffix Markdown and the source is a string then I want to transform the output.
p.s. I know how to render Markdown, so what I'm really after is the convention to get AutoMapper to take the tedium away for me. Thanks.
If things are really consistent, like FirstNameMarkdown, you can use some built in functions.
Mapper.Initialize(cfg => cfg.RecognizeDestinationPostfixes(new[] { "Markdown" }));