• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Import XML

komobu

Member
I found a web site where a guy has an xml file that should be ablt to be imported. I cant figure out how to do it. Any help importing xml files would be appreciated.
 
You copy the .xml file to you machine and then check every <nme></nme> pair to see if there are any name conflicts with what you already have installed. They will overwrite matching profiles, projects, and tasks without prompting.

Is it a Project or a Task?

... Thom
 
To import a task ...

copy the tsk.xml file to your device.
Verify there is no name conflict on :nme></nme> card.
Open Tasker.
Press on the TASKS heading
When the dialog appears choose Import
Select the xml file to import

... Thom
 
so I downloaded all 8 of these files and placed them in my Taskers/Projects directory on my phone. I try to import them and all I get is a message stating "ERROR: bad bile name must match .prj .xml
 
What are you trying to do?

I suggest that you start out simple and chip away at it.

Import will overwrite a task or profile with the same name.

When you EXPORT a task it is put in the tasks folder as a tsk.xml file

You don't have any projects in what you referenced.

To import a task ... see message above.

To import a profile ... do the same procedure clicking on PROFILES to start the process.

... Thom
 
In Tasker you are telling it to load some data and use it for a specific purpose ... like Project or Task. I don't see where a generic import file capability addresses the need.

What is needed is a safeguard that a liked-name element is not accidently overwritten by the import by asking fir permission when it finds one.

Global data access in Tasker is a little "fluid" and becomes an issue when you start creating .apk files. What was global in Tasker is not what is global in the .apk.

... Thom
 
Perhaps make the interface less complicated? I've seen a few of these questions on forums, it would certainly eliminate that need. There's four different locations for Import commands, a generic button with subselecting the mode, or even Tasker recognizing the format and importing accordingly... I'm sure it wouldn't hurt. But I've been wrong before.
 
I don't see anything that it solves and it adds the potential for even more errors.

The way it is now you have to know if you are dealing with a Project, Profile, Task, or Scene and manually adjust for the varying implications of each.

That manual intervention is still required. Displaying profile, task. and scene names in a different color in the SML listing might help.

... Thom
 
Back
Top Bottom