User Tag List

Page 1 of 5 1 2 3 ... LastLast
Results 1 to 10 of 46

Thread: Limitations of Vitalize! applications

  1. #1
    Clickteam Clickteam

    Join Date
    Jun 2006
    Location
    France
    Posts
    13,697
    Mentioned
    247 Post(s)
    Tagged
    3 Thread(s)

    Limitations of Vitalize! applications

    You cannot do everything in Vitalize! applications :

    - Some extensions are disabled, because they are not safe. Refer to the list of vitalized extensions for more info.

    - The actions that could allow you to retrieve private information from the user's machine are disabled.

    - The Load actions are "Download" actions. For example, the Load action of the Active Picture object will try to download
    the file from the server, it won't load it from the local machine. Refer to the "How to use external files" section below for more info.

    - You cannot save files. The Save actions are disabled, except for 1 or 2 actions that prompt the user for a filename, and for the INI and Hi-Score objects. See below.


    How to use external files in Vitalize! applications

    If your application uses external files, like picture files loaded by the Active Picture object, text files loaded by the Edit box object :

    1. These external files must be in the directory of your MFA file, or in a sub-directory.

    2. When you build your CCN file, build it in the directory of your MFA file.

    3. If you load the files with expressions in the event editor, you should specify the full path : Apppath$ + "name_of_your_file".

    4. Upload these files to the directory of the CCN file on the server (or to the same sub-directory, if they are in a sub-directory).

    If you follow these rules, Vitalize! will download your external files.

    Note for MMF2 users : you can also embed the files in the CCN application if you add them to the Binary Data tab in the Data Elements editor.


    Special case : INI object

    As in Vitalize! 3, when you write .INI files with the INI object, Vitalize! 4 writes the data to a unique Vitalize.ini file.

    In Vitalize! 4 this INI file is usually located in the Application Data\Clickteam directory of the current user.

    However if you use Internet Explorer on Vista and are playing a CCN file from a non-trusted zone, Internet Explorer is executed
    in protected mode and in this mode the file system is virtualized. In this case, Vitalize.ini is usually stored in :

    C:\Users\%UserName%\AppData\Local\Microsoft\Window s\Temporary Internet Files\Virtualized\C\Users\%UserName%\AppData\Roami ng\Clickteam

    This may cause issues if the user uses Internet Explorer and then FireFox and your application uses INI files to store data,
    as the data saved in IE won't be the same as the one read in FF.


    Special case : Hi-Score object

    The same rules apply to the Hi-Score object. The scores are saved in a unique cncscore.ini file in the Application Data directory (or in the virtualized Application Data directory).


  2. #2
    Clicker Multimedia Fusion 2
    BrandonC's Avatar
    Join Date
    Jun 2006
    Location
    PA, USA
    Posts
    931
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Limitations of Vitalize! applications

    If you want my personal opinion, I don't think that features should be disabled, but perhaps add something into Vitalize! that will have a required prompt or perhaps a Yes or No confirm when some of these suspicious actions are taking place.

    This way you're not stripping power to be safe, you're just taking precautions.

  3. #3
    Clicker Fusion 2.5 DeveloperFusion 2.5+ DLCSWF Export Module
    Alonso's Avatar
    Join Date
    Jul 2006
    Posts
    681
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Limitations of Vitalize! applications

    Not being able to save kind of ruins the point of many applications. I understand some users might use these features in a negative way, but there's not much you can do--I'm sure lots of viruses have been compiled with a Microsoft program.

  4. #4
    No Products Registered

    Join Date
    Dec 2006
    Posts
    1,332
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Limitations of Vitalize! applications

    You can still save with the INI object if I am not mistaken.

  5. #5
    Clickteam Clickteam
    Jeff's Avatar
    Join Date
    Jun 2006
    Location
    Battle Ground Washington
    Posts
    11,824
    Mentioned
    8 Post(s)
    Tagged
    2 Thread(s)

    Re: Limitations of Vitalize! applications

    Yes you can use the INI to save limted amounts of data on the users computer. You can always send data to a PHP script (or other script) on your server and store data -- Handy if you want the data used by other clients using Vitalize.

  6. #6
    Clicker Multimedia Fusion 2

    Join Date
    Jul 2007
    Posts
    138
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Limitations of Vitalize! applications

    Just wondering... would a popup subapp work with Vitalize!? Also... would you be able to use the Server-side ini option of the MooGame object? I hope so because my game is based on that pretty much...

    EDIT: I tested and the popup subapp works, but I still need to know about the MooGame thing. Thanks!

  7. #7
    Clicker Fusion 2.5 (Steam)Fusion 2.5 Developer (Steam)Universal Windows Platform Export Module (Steam)

    Join Date
    Jul 2006
    Posts
    2,023
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Limitations of Vitalize! applications

    yes MOOGame stores the INI on the server you are connected to, not the client PC

  8. #8
    Clicker Fusion 2.5 DeveloperSWF Export ModuleInstall Creator Pro

    Join Date
    Jun 2006
    Location
    France
    Posts
    1,266
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Limitations of Vitalize! applications

    NO PLEASE do not disable saving! We need it one way or another. It REALY cuts on the strenght of Vitalize? 4. And this all for security reasons? It would be much better to allow THE USER to decide. Just as with shockwave and flash. Do you know what flash can do? man! Really, anyone can do harm to someones PC. What is important is that you garuantee safty on your own behalf. Meening, ClickTeam is responsible for Vitalize, the developer is responsible for the application or game utilizing Vitalize. If one of those parties does not guarentee the safty, the user knows what he/she is downloading. I respect the vision of ClickTeam tough. But should both parties not at least be given an option?

    Man i hoped i could create a folder in someones programfiles and there store downloaded maps for Fantasaar, etc..
    And OFCORSE i would well inform my users of that, because it is my own reputation and my own game.
    Do i now tell them? "Ah guys, bad luck for all of you, because someone that is beond my control, whos software i happen to use to make this game decided for you and me it is best to not allow this." that is a big choice and a big responsibility taken there.
    I strongly doubt it would be apriciated.

    If i really would want todo some damage or spy on somes PC i wouldnt be using MMF2 for that.

    Is it not a fair proposal, to just LIKE windows, like Flash, like shockwave, to PROPOSE in the form of lets say a dialog, wheter a certan action is allowed or not.
    What if Windows would just block all the ports because Bill things its safer that way.

    Anyway, having said that i wonder:
    1) Is MooClick Supported as in MMF2 standalone apps?
    2) Is MooSock Supported as in MMF2 standalone apps?
    3) Is the download object supported as in MMF2 standalone apps?
    4) Will i be able to talk with my server-side(s) without javascript, using extensions or other in-build features?

  9. #9
    Clickteam Clickteam
    Jeff's Avatar
    Join Date
    Jun 2006
    Location
    Battle Ground Washington
    Posts
    11,824
    Mentioned
    8 Post(s)
    Tagged
    2 Thread(s)

    Re: Limitations of Vitalize! applications

    The current behavior of Vitalize is the same as the past but Vitalize now has more features. Nothing in regards to features has been removed from it.

    Perhaps more features will be added in the future in regards to warnings and popups incase wide open access to the users computer is granted but I don't know. Most people enjoy knowing there is no way the Vitalize! application can do any damage.

    You can save data to the vitalize.ini and download files into the temporary internet cache.

    I am also under the assumption for applications on a web page you would want to store all your data server side so your player/visitor can log in on other computer and not have to download a bunch of stuff. They would log in and retrieve any saved info from online and not have to start over just because they are on a different computer.


    Of course Moo is still supported.

  10. #10
    Clicker Multimedia Fusion 2 DeveloperiOS Export ModuleSWF Export ModuleUnicode Add-on
    LIJI's Avatar
    Join Date
    Jun 2006
    Location
    Israel
    Posts
    1,175
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Limitations of Vitalize! applications

    I suggest being able to save files to the browser's Cache folder. Flash does that and no one ever complained.

Page 1 of 5 1 2 3 ... LastLast

Similar Threads

  1. Limitations
    By Corlagon in forum XNA Export Module Version 2.0
    Replies: 2
    Last Post: 5th June 2012, 12:24 PM
  2. Any limitations on MMF2
    By ASD in forum Multimedia Fusion 2 - Technical Support
    Replies: 5
    Last Post: 11th August 2011, 07:58 PM
  3. Replies: 56
    Last Post: 4th July 2011, 03:23 PM
  4. Limitations of OS
    By dollar in forum Install Creator and Patch Maker
    Replies: 5
    Last Post: 7th April 2007, 12:45 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •