I am new with ckeditor5, I have reviewed and read the documentation on a and b, I can't understand or find a clear example of when to use one of them or both.
When should I use downcast?
When should I use dataDowncast ?
When should I use both?
Thanks.
Related
Is there any way to get a reference to a Fragment without using findFragmentById or findFragmentByTag ??
There is very little information in your question. I assume you use the FragmentManager? There is a getFragments method, you could find your fragment using that. https://developer.android.com/reference/kotlin/androidx/fragment/app/FragmentManager#getFragments()
You could also catch the fragment when it attaches, I believe there is an onAttach callback.
If these solutions are not what you are looking for, please provide more information
Max, I want to update my extension to the new format, but I am running into issues with placement of custom code. It seems that the extension framework has been updated a lot since I added an extension 4 years ago. Is there a way to get better documentation on getting started with adding a extension? I am happy to help write up the documentation if you can help answer some questions that I think would help get people started. Let me know.
The only thing that really changed is that the scaffolder creates a webpack project for you. The extension registering procedure is the same: http://js.cytoscape.org/#extensions/api
For example, cytoscape( 'collection', 'fooBar', function(){ return 'baz'; } ) registers eles.fooBar().
I guess the main thing is that there are a lot more files than what the previous scaffolder generated, so it might be harder to find things. The layout output has lots of files, because it creates a skeleton impl for each of the continuous case and the discrete case.
The scaffolder isn't strictly necessary. You could use another build system (or none at all) as long as you call cytoscape(). For example, if you only care about publishing to npm for people who use webpack/browserify/rollup, then you could just use cjs require('cytoscape') to pull in the peer dependency. Exporting a register function is nice if you want to allow the client to decide the order of extension registrations with cytoscape.use(extension) (or extension(cytoscape)).
You're right that there should be some more docs on the output of the scaffolder. Maybe a summary of the files would suffice. We could add a tutorial in the blog later if need be. Both the docs and the blog just use markdown, so the content could go in either place.
It seems doesn't add anything to the regular java hot-swapping. I'd like to get the groovy class hot-swapped in a case of method adding/removing/signature changing. Is it possible with this agent?
Dany's answer is correct, but doesn't answer the question fully. No, this agent doesn't help you to hot-swap when fields or methods are changed. You might want to consider using DCEVM for that.
Removes all timestamp-related Groovy fields on class loading
Also clears Groovy's call site cache
As stated in
https://github.com/JetBrains/intellij-community/blob/master/plugins/groovy/hotswap/agentSrc/org/groovy/debug/hotswap/ResetAgent.java
Methods of yii\caching\Cache:
madd(),
mget() and
mset(),
are the only (known to me) in entire Yii2 core, that are using abbreviated names. Following naming convetions used everywhere else, they should be named multiAdd, multiGet and multiSet.
Does anyone know, why exception has been made for this one (?) class?
I'm reviewing a book about Yii2 right now, and I was so extremely surprised to findout these names, that at first I'd bet a lot, that book author made a mistake! Abreviated methods names in Yii2?
I think it was done in haste and is inherited from Yii1.
http://www.yiiframework.com/doc/api/1.1/CCache#mget-detail
No one thought about it then. And now it is BC
UPD: Added in Ideas for 2.1
UPD2 https://github.com/yiisoft/yii2/pull/10296
Well, I guess it was named so for short. For now we can create multiSet, multiGet, multiAdd methods, and make the existing mset, mget and madd method as aliases for them. Then mark old methods as DEPRECATED until Yii 2.1, then just drop them.
I got multiply .orm.yml-entites which actually need to be extended by another one. As it is described here:
http://docs.doctrine-project.org/projects/doctrine-orm/en/latest/reference/inheritance-mapping.html#mapped-superclasses
But I do not found a solution there for orm.yml-files, this is only for annotations.
How can i achieve this?