Compiling with mxmlc vs Flash - apache-flex

I have some ActionScript code that I got from some website. I've tried to compile the code and it seems to have compiled with no errors. However, it doesn't work as expected and I am wondering how I can debug this?
It seems that the website uses Flash to compile it because there's a .fla file located as well. Does anyone have any idea?
Forgot to mention that I am on Unix and will be compiling on Solaris.

Download Flash demo version and find out! The .fla may contain some assets or even had some code, I don't know of any other ways to compile the .fla!

Related

Visual Studio CSS not working in compiled app

I am new to Visual Studio 2019 and I am having a bit of a problem with my CSS stylesheet location. I am using the Peachpie.App NuGet and everything works perfectly when I run the Debug (F5) with the correct stylesheet being used but if I run the compiled application executable I loose all of the CSS formatting. I assume I have got the style.css file in the wrong location for the compiling process to pick it up but I don't know how to resolve that, can anyone provide some advice on this?
Thanks,
Gerry
I manually copied the style.css file to the "\bin\Release\net5.0\wwwroot" directory and it resolved the problem but I should have expected that that would have been down during the Build process.

Cannot load sqlite.dll with QSQLITE2 Qt plugin

I use QtCreator + mingw.
I have compiled QSQLITE2 plugin. I simply entered plugin directory in Qt source code:
c:\Qt\Qt5.2.0\5.2.0\Src\qtbase\src\plugins\sqldrivers\sqlite
and I built it with my sqlite 2.8.17 that I have locally (as dll and header):
qmake "LIBS+=-Lc:\projects\lib -lsqlite" "INCLUDEPATH+=c:\projects\include"
make
make install
Everything builds okay.
Now, I have another DLL (also implemented as Qt plugin, a custom one), which makes use of QSQLITE2 Qt plugin. My own dll is also linked to sqlite.dll. So it looks like this:
my.dll depends on sqlite.dll
%QT_PLUGINS%\qsqlite2d.dll depends on sqlite.dll
my.dll uses qsqlite2d.dll through Qt's plugin engine
myApp.exe loads my.dll
Problem is that my application cannot load my.dll, because of invalid location access or something like that. I don't know any details and that's the problem.
The sqlite.dll is in the application directory when running it.
When I run application in debug mode, it crashes in some assembly file, but in stack trace I can see that it's somewhere inside sqlite.dll, in sqlite_step symbol. That's all I know.
Note 1) I have another plugin dll, the my3.dll, which uses QSQLITE plugin (it's for sqlite3) and is linked with sqlite3.dll and this one loads just fine. I have compiled QSQLITE plugin myself as well (even there was the one provided with Qt, that's because Qt linked statically to sqlite3 and I wanted it to link dynamically to sqlite3.dll).
Note 2) Both plugins work just fine under Linux.
Any hints what might be wrong? What else can I check?
EDIT:
I've just performed a test: I deleted my.dll from plugins to avoid loading it at all. Then I added code to main.cpp:
QSqlDatabase::addDatabase("QSQLITE2", ":memory:");
Thing is, that it also crashed, with the very same stack trace (at this very line, I debugged it). Thus I think there's something wrong with sqlite2 Qt plugin, but I'm still unable to tell what. I looked up for other sqlite.dll, I just downloaded the one from sqlite.org: http://www.sqlite.org/sqlitedll-2_8_17.zip - so it's official build, but it's the exactly the same file I had and it also fails the same way.
It turned out that qsqlite2d.dll cannot be linked sqlite.dll, because sqlite.dll is not compiled in debug mode. After recompiling application in release mode (thus using qsqlite2.dll, not qsqlite2d.dll), the plugin loads correctly and works.
This makes sense, but just one more thing that bugs me - qsqlited.dll (for sqlite3) had no problem linking with sqlite3.dll. No matter if I compiled debug or release - the single sqlite3.dll worked with both debug and release plugins. Anyone has an idea how is that possible? Please comment if you do, I'd appreciate it.

boilerplate has a 4mb footprint - why?

I'm using eclipse for html5, js & css3.
On starting a new project, eclipse offered to start it using boilerplate. After a little research, it seemed a good thing to try. But on zipping the project up to send to a tester, I found I had a small app with a very large 4mb footprint...
I've found the culprit in myProject/.git/objects/pack
the file is
pack-8bbfc27fb4f49b9b8418123879a14af5e5dd861c.pack and is 3.8mb
Any ideas what this is for? Is it something eclipse has added?
Cheers
The .git directory is only used by the Git version control system. We use Git - as many other open source projects do - to manage the source code of the project.

Build swf using mxmlc (Ant) - Code compiles when code not changed

I am using mxmlc task to generate swf for our project.
Problem is, even when I dont change any flex code, swf compiles every time, which is comparatively lengthy process.
Does anyone know how to avoid it? Is there any solution to this?
Thanks in advance,
Miral.
Incremental compilation should be what you are looking for. It's on by default when you compile from Flash Builder but not when you compile from the command line or Ant. The gist is that, with incremental compile on, mxmlc inspects your code looking for changes and only compiles what it needs to.

Problem While swf embedding in Flex

A problem that is waste my one hour
I am embedding swf in the flex application it works fine.
But when i embed one swf the compiler through an error
unable to resolve 'com/assets/swf/flash_ad.swf' for transcoding
Unable to transcode com/assets/swf/flash_ad.swf.
pls help me.
Actually that swf is compiled and published in older version of action script.
So when i de-compile the swf and generate my own swf with latest version of action script the problem is gone.
Anyway Thanks
Make sure your flex compiler is able to locate the swf first. Try refreshing your workspace, so compiler finds it.
Also ensure your swf is built correctly. Corrupted swf's wont get embedded.
Check if this helps: http://www.brightworks.com/flex_ability/?p=38

Resources