I'm researching how to using iDempiere fw. I tried using ZK theme into iDempiere fw by link here.
First time, I put the zk-bootstrap.jar file under WEB-INF/lib folder in org.adempiere.ui.zk project.
In zk.xml file, I insert lines of code:
<library-property>
<name>org.zkoss.zul.Button.mold</name>
<value>bs</value>
</library-property>
<library-property>
<name>org.zkoss.zul.Menupopup.mold</name>
<value>bs</value>
</library-property>
<library-property>
<name>org.zkoss.zkmax.zul.Navbar.mold</name>
<value>bs</value>
</library-property>
<library-property>
<name>org.zkoss.zul.Paging.mold</name>
<value>bs</value>
</library-property>
<library-property>
<name>org.zkoss.zul.Panel.mold</name>
<value>bs</value>
</library-property>
And I run iDempiere fw again. But it doesn't work. It only display this screen:
.
Please help!
There is a published way to add ZK Theme as another plugin into the project. You can refer to its online documentation here http://wiki.idempiere.org/en/Add_your_theme
Related
I try to install PWA in an existing project in react. There is a manifest.json file and a serviceworker.ts file in the project.
I try using PWA Studio on VS Code to diagnose the existing code but when it ask me the manifest, ok and when it ask me the serviceworker the file is grey...
Should I create new manifest and serviceworker file? Should I edit these files?
I tried with manifest.json but when I use the "generate icons" tool of PWA Studio, I have an error "you first need a web manifest".
Maybe the location of the files are not ok? Manifest.json is in the frontend/public folder and serviceworker.ts is in frontend/src. I don't know why it was chosen that these files were put in these folder, I think I cannot move them but I'm not sure...
I don't understand what I did wrong... Could someone guide me, please?
For my project, I have customized my launch.json file.
How can I save my own customized launch configuration as a template? Just like C++ (GDB/LLDB) template
So that I can re-use it easily every time I open a new folder(project).
I don't want to add it under global launch configuration. Adding it there would start showing up my launch configurations even for other kind of projects where this launch configuration is inappropriate.
I wanted to have the same behavior that is achieved for C++ (GDB/LLDB) template. How is that achieved?
Edit - I have raised an enhancement request VSCode GitHub-
https://github.com/microsoft/vscode/issues/109234
They are part of the debugger configuration in the language extension.
Way too much trouble to create an extension for this.
Just create a snippet for a .json file and use it while editing the .vscode/launch.json
I want my webapp to be able to open a given file in VS code. For example, when I click a button on my webapp, a file say, C:\Users\...\myProject\index.html is opened, if myProject is already opened it should navigate to index.html
I know its a peculiar use case but I want to know if its possible in vscode.
Its also completely fine if it requires using browser or vscode extension.
vscode://file/{full path to project}/
Thanks to fbg13 for providing this link
It is possible if you are using Firefox:
Open the about:config page.
Set the view_source.editor.external to true.
Set the view_source.editor.path to the VSCode's executable absolute path.
It is possible if you add this link:
vscode://file/{fullpath}:{numrow}
Example for Symfony 5.3 and higher
For example in Symfony to use the link that appears in the debug bar of the controller used you can do it as described in the examples. You have to edit your project config.
Only for VS Code:
config\packages\framework.yaml
framework:
ide: 'vscode://file/%%f:%%l'
For any editor through env:
config\packages\framework.yaml
framework:
ide: '%env(resolve:CODE_EDITOR)%'
And don't forget to add value for CODE_EDITOR into .env or .env.local.
Local
This is an example for local projects.
.env or .env.local:
CODE_EDITOR=vscode
# or
CODE_EDITOR=vscode://file/%%f:%%l
Docker
If you use Docker or trying to open a file from remote server, you may use this example.
.env or .env.local:
# Template
CODE_EDITOR=vscode://file/%%f:%%l&/PATH/TO/YOUR/SERVER/APP>/PATH/TO/YOUR/LOCAL/APP
# Real paths
CODE_EDITOR=vscode://file/%%f:%%l&/app/>/home/user/projects/symfony_project/
For more details see these pages:
Symfony Framework Configuration Reference - ide
Opening VS Code with URLs
You can install vscode-handler to open files like this
vscode://open?url=file://%file&line=%line
I'm trying to learn Vue.js as well so I create a simple folder called VueTest.
I have two files in the folder:
app.js
index.html
I found the info on how to configure the task runner to open up the current file and I have that setup to open in Chrome, which it does. However, because it's not running as a project, my index.html doesn't see the app.js file and so my Vue project is not working correctly. I just runs the HTML code an all I see is my mustache code (ex: {{Title}}).
How do I run files as a project?
If get it correct - you want to launch js app without opening teminals outside 'VS Code' then you have to see this
Have fun
I found my mistake, it's actually easy and I should have figured this out before posting.
To run Index.html on it's own, all I had to do was make a script reference in the page pointing to the app.js file. I didn't have to do that in JsFiddle.
you can't run files as a project in VS Code. it is just a text editor.
I have created a web part using VSeWSS 1.3. It creates a wsp file and my web part gets installed, everything works great.
I would like to also create a folder in the LAYOUTS directory of the 12 hive and place a couple files in there. How do I go about doing this? I know that I can manually place the files there, but I would prefer to have it all done in one fell swoop when I uses stsadm to install my solution.
Is there a best practices guide out there for using VSeWSS 1.3 to do this? They changed a bunch of stuff with this new version and I want to make sure I don't mess anything up.
You can create a new folder structure in your webpart project, like:
Templates/Layouts/CustomFolder and put your files in the CustomFolder directory and include them in your project.
When you go to the WSP View in Visual Studio, you can see in the manifest.xml that your files are being included in the deployment.
I have done this successfully on multiple projects now.
In case anyone is wondering, the VSeWSS 1.3 user guide is incredibly helpful. It is installed to the same directory as the tool itself, default in C:\Program Files\Microsoft SharePoint Developer Tools 9.0\VSeWSS13.CHM
You can see a working example with screenshots Here
A simple step-by-step tutorial for the above, along with deploy/retract scripts is here at Add New Files To 12-Hive Through A SharePoint Solution. Just follow the steps and in a few minutes you'll be able to add whatever you want to the 12-Hive!