Are users able to view source of web apps on ChromeOS? - google-chrome-os

If yes, is there a way to compile (NOT obfuscate) JS code for deployment in ChromeOS?

From quickly looking at the codebase using the Chromium.org Git browser, it appears that Google haven't gone out of their way to remove the "View page source" menu item from the version of Chrom(e|ium) shipped in Chrom(e|ium) OS.
Of course, there's nothing to prevent them from hiding the option in the UI, or removing the feature all together by #ifdef-ing it out, though.

Related

Module Selection tab is missing in Prestashop 1.7.4

I've just installed two instances of Prestashop on my local server from the same downloaded zip. However on one install, the module "selection" tab is missing, preventing me from installing modules placed into the module folder.
I've tried clearing the cache folder to no avail.
Would appreciate any insight into the matter.
Kind Regards
Musaffar
That's a bug!
Waiting for the team to fix it.
But here is a work around:
Access the installed modules tab.
Above in the url, change manage with catalog as follow:
And finally, if you want to search a module you are building, or any other module, directly search it using the search bar (the category menu, can suffer problems, it doesn't show well, you can use the developer inspector, and change the css (set the z-index to a big number, something like 5000)), so it can be shown if you want! but it's faster to directly search for what you want.
And here you can see your module, you are building. If that's what you're searching, you can install it too.

Developing theme locally using stencil

Is there a reason I need to install stencil CLI framework and supporting javascript etc... rather than just download a theme and edit it with notepad, then re-upload it?
Is seems that this has been made overly complicated
The advantage of using the Stencil CLI is that you can test your work locally, so you can be sure you haven't broken anything. If you just want to make a small edit, then rather than downloading and uploading, try editing files within the Control Panel. Go to Storefront->My Themes->Customize, and then at the bottom, click Edit Theme Files. This way you can make a small edit and have the ability to do a preview (so again, you test your work before changing your live store).

Cannot select latest uploaded version to add to testflight

I cannot select the latest version I have uploaded to seed to beta in external testing. First of all whenever I upload a build two version appearing, that have upload time difference of 5 to 15 minutes between them. One of them gets changed from processing to normal available state, but other does not. But now selecting the available build also selects the processing one and my selection is blocked and I cannot select the OK button because probably my selection is blocked by the processing one. I think it is UI frontend issue at itunesconnect side but it could be something I am doing wrong. Please help me if anyone has been able to tackle this issue if they faced. Please see checkout the attached image.
Update:
I Included <key>ITSAppUsesNonExemptEncryption</key><false/> in my subsequent builds that I uploaded according to the new Export compliance message on the iTunes Connect home page. I am still facing the issue. I have contacted Apple Dev support, will keep you updated if I find a solution.
The issue has been mysteriously solved by uploading the application from Application Loader with Aspera turned off instead of using Xcode's organizer window as suggested by Apple Developer support. Make sure you add: <key>ITSAppUsesNonExemptEncryption</key><false/> in your info.plist file before archiving the build. Although mysteriously my previously uploaded builds have also become available for external testing.
Body of email that helped solve the issue:
After further research, it looks like their may be an issue from your
end with your network while trying to upload to this app record in
iTunes Connect.
First, for the best upload experience make sure that all ports and IP
addresses are accessible. Additionally, it’s important to make sure
the internet connection is very good, and that there are no firewalls
blocking the uploads. More information can be found here:
http://help.apple.com/itc/apploader/#/itc8e7ec5a60
Second, it may be beneficial to try using the latest version of
Application Loader. Please note that you can export your project from
Xcode to upload through Application Loader. As a temporary workaround,
once you have Application Loader open, you can go to the File menus
and select the following:
Application Loader > Preferences
Then, select Advanced, and as a temporary workaround you can try
deselecting Aspera and upload the build again. You can follow the
steps below to use the latest version of Application Loader.
Download the latest version of Xcode from the Mac App Store:
-http://help.apple.com/itc/apploader/#/itc8e7ec5a60
Open the latest version of Xcode
Go to the File menu and select Xcode > Open Developer Tool > Application Loader
Lastly, try uploading again to see if the issue persists.
Hello my dear friend there,
I am also having your issue yesterday, I have this similar screen with yours:
The build is duplicated which one of them are processing forever until today.
My personal problem solving was:
Increase my build number in Xcode so that I can reupload my build
Rearchive the build then export for iOS App Store Deployment in Xcode Organizer
Reupload the build using Application Loader
Then try to reconfigure the build in iTunes Connect. For a while it is processing like usual, but it will not take forever, after one hour, the build will be available for testing.
Hope my personal troubleshooting can be applied to your issue too.

Programmatically install extensions on Safari 8 OSX 10.10

I'm trying to fix a couple of bugs for SafariDriver/Selenium.
Here is the problem:
On Safari 7 and bellow, to install a new plug in all you had to do is put the extension into ~/Library/Safari/Extensions. Next all you have to do is activate the plugin by adding it to the ~/Library/Safari/Extensions/Extensions.plist after this the Safari will have the plugin installed.
Starting with 10.10, this is no longer possible to do. The location of the extension is the same but i'm not sure how to activate the extension, since the Extensions.plist no longer exists.
My understanding is that there is some file that is controlled via "Safari Extensions List" password in the keychain under login but I have no idea which file this may apply to.
If I compile and install the extention by hand, everything works just fine but the automatic installation of the latest plugin is broken. (documentation for this https://code.google.com/p/selenium/wiki/SafariDriverInternals)
"Safari Extensions List" password is not password actually but a binary plist same as ~/Library/Safari/Extensions/Extensions.plist
Read it, modify it, write it back.
The correct thing to do is to have the user install the extension by opening it manually (double-click or command o). That's what Apple is trying to get you to do.
Apple never really wanted anybody messing about with plists for other apps.
Most preferences plists are cached in memory anyway and would require a new login session to blow them away and get new copies.
plists are updated on ending the session or the app in question.
They were never intended as a means to modify another app's behavior. That is a security risk.
In the case of Selenium, the intent is clearly to create an automated test environment. Setting up a nice installer pre-empts that to some degree.
The right thing to do is to file a bug with Apple letting them know what kind of functionality you need in Safari.

how do i chnage the desktop icon for a visual basic program (.exe)

im making a vb.net app and i want to set the icon, how can i do this?
--edit--
turns out i was a bit confused, and it was working. but the answers can still be useful for others.
If I understand the question and issue, your setup/installer might be missing something.
It would seem you did create a shortcut, add it to the Setup project to install to the Desktop (else you wouldnt have one at all)
Select the shortcut in your setup project, open the properties window
Click Target. The list of files you are installing will come up. Select the App.Exe (ie the main executable "MyApp.exe" ususally the primary output). I think Icon is supposed to be set to "Icon" as well.
I think those 2 things combined link the Desktop Shortcut's Icon property to Use the App.Exe's. If there is also a shortcut in the user's programs menu do the same thing (or drag drop a copy).
You are basically doing to the Setup Project's shortcut what you would do to a normal desktop icon to change it or set it. The proj apparently fills in the actual path etc at install.
EDIT
PUBLISH simply compiles everything and produces files for the dev to distribute. It is called PUBLISH because in many cases the output includes a ready to use Setup program for the END USER to install on the PC. (Based on your new Pic, you are trying to reinstall everytime you click the icon or file inside the folder.)
Again, if you do not add a Setup proj to your project, the default one is used and it gives no option for where to install and does not add a shortcut.
Just delete all that junk, Publish again to the default location (VS Studio\...Project name\bin\Publish). Go to that folder and run setup. It will still install to Users\AppData.. but will add a shortcut (to the program) to the start menu.
For a desktop icon, do the "Send To Desktop ..." thing. To INSTALL an icon, you have to add and modify a Setup proj to your Solution.
HTH
'The folder shows the icon for the app, but the icon for the form is different. change the form's icon(in the property grid) to the same as the app and you should see it then.
When you publish it there's 2 files produced that are basically setup files. One relies on the ClickOnce Application Deployment Support Library and the other is a standalone setup app. Since neither one is the actual app you designed, they aren't going to have the icon you want. You'll probably have to investigate other more configurable deployment options.