Sencha cmd separate folder in build - extjs

I need to separate an folder in my application in another app.js build
generated by sencha cmd, this folder is being used by another applications and i need to have in web cache.
I read the documentation and I dont found nothing related to this
Exists another way to do this, without having to create a unique application for the specific folder ?

Related

Structure/ method for folder storage

Is anyone aware of what method / structure does google drive use to upload a whole folder?
And how to use the same method with git push for uploading that folder in a similar way as github does.
1- Storing folder as a zip and unzipping and showing it on.the client side would be inefficient i think.
2- Creating a new row for each file and storing it along with the path and then getting all the rowa related to the path is also a very inefficient approach.
Thanks in advance.
Git is a version control system and GitHub is a place to store your project which you use Git. Let's give an example. GitHub is like Instagram but for code commits not for photos. So all other developers can see/fetch/push/comment on those commits. It's not like Google Drive. Google Drive is a "file storage".
If you want to push (upload) a folder or a .zip file, first you need to commit it with Git and later push it to GitHub. Don't forget to create a repository on GitHub first and remember to set it as "private" if you need.
I suggest you read this e-book: https://git-scm.com/book/en/v2

Check if a folder exist on client system in ReactJs

So, I have a project in Reactjs where in I am getting some String data from JSON . and I am writing it to a file. Now I want to save this file in a folder on client side.
So is there a way to create a folder (for the first time execution) and check if a folder already exist on system. and save file on that folder?
I tried and searched a lot but couldn't find anything useful. I can save the file in downloads folder but I don't want that, I want my custom folder.
Thankyou.

Kylo plugin for UI is not working

I would like to extend Kylo user interface. From documentation, i understood that I can use Plugin mechanism to add new features and I am referring to the examples available here.
I have built this example code and deployed the generated jar files to /opt/kylo/kylo-services/plugin folder and restarted the kylo-services.
But I am dont see any changes in the UI. As per my understanding, there should be a new group in left hand navigation pane but there are no UI level changes in the kylo UI.
I am using dladmin userid and logs (kylo-ui and kylo-services) really did not indicate any error.
Where can I see if the plugin is really picked up by kylo? Which logs tell me what is going on with this plugin? Any suggestions will be of great help.
Thanks
Gana
The mistake i did is copying kylo UI into /opt/kylo/kylo-services/plugin folder.
The generated jar files should go into different plugin folders.
Kylo Services plugin should be copied to /opt/kylo/kylo-services/plugin folder.
Kylo UI plugin should be copied to /opt/kylo/kylo-ui/plugin folder.
service kylo-services restart
service kylo-ui restart
And its my bad that i mistakenly copied kylo-ui plugin into kylo-services folder. After I copied into correct folders and service restart, I am able to find the UI changes.
Thanks for your attention.

Manually Create composite.generated.dll

I'm new to composite C1 CMS and am trying to update a site from 4.1 to 4.2.
I'm running into some build errors because the 4.2 generated.dll file doesn't know about the custom data types etc that were in the 4.1 generated.dll.
Do you have to create the generated.dll manually somehow?
The Composite.Generated.dll is usually regenerated when the website restarts.
The quickest way to fix it would be to:
put the old DLL back
start the site
restart the website in IIS
If the DLL isn't updated, there should be errors in the log files
Way #2:
Delete the /bin/Composite.Generated.dll
Temporary remove DLL-s and App_Code files that were referencing classes from Composite.Generated.dll
Start and restart the website
Check the log files for errors if the file wasn't re-created

Deployment of new pages from Local to Production

I've a copy of DotNetNuke website on my local machine in which I've added few pages and created new modules.
I've to move these new pages to production so have copied the pages to respective folders. I know there are few database entries that are also to be made on production database to recognize these pages and modules on production.
Please tell me how I can register these pages on production website
I searched on Google but may be I'm not getting the right keywords to search. Currently I've to restore my local db to production to run those pages. I'm using version 7 of DNN
This isn't something that DNN handles very well, publishing from a local environment to production.
The most common way (Besides backup/restore of the database) is to use page Templates. You can "Export" a page in DNN, that will generate an XML document with the modules and content referenced into the portals/#/ folder (where # is the portal id)
You can upload that file to your production site (same path) and then create a new page based on that page template.
Your question implies that you are creating .aspx files and copying those to the production server. That really isn't the way that DNN works, and you probably are creating a real mess.
How did you create the pages on your local site? Did you use the DNN functionality to create new pages, add modules to those pages, etc.? Or, did you do something else?
Use the built-in funtionality to create pages on your local installation and, as Chris
To add modules - Go to your web site in production, login as super user, and install the module, then go to the page in the web site and add it. The same as you would do with 3rd party module. This will properly add the info to db.
To add pages - You could do it within the code, using the
To create DNN page (the tab):
TabController tbc = new TabController();
//...populating the page's info
tbc.AddTab(destinationTabInfo);
To create ascx control as global (meaning doesn't belong to any module) ModuleControl.
var moduleControl = new ModuleControlInfo
{
... populate the fields
};
ModuleControlController.AddModuleControl(moduleControl);

Resources