Hello,

 

I’m not sure if I’m right.

I thought Tizen common platform should be independent from any app framework. 

On current implementation every framework may install it’s own applications 
which are represented by file extension and provide installer for it.

 

Are you sure that any type applications can be installed by one flow? What will 
proposed generic installer cover? Crosswalk and native framework? What native 
framework?

Application manifests, directory structure and other are specific to given 
framework.

Basicly, I always thought that this crosswalk provides integration with tizen 
platform 

not a tizen (common) platform provides integration with crosswalk.

 

Secondly, many feature of web runtime requires changes in runtime part and 
installer part (I think its strongly connected). That would be pretty annoying 
to provides duplicated implementation of parsing some data structures on 
crosswalk (to load app) and then again on generic installer (or part of it that 
handles “wgt”, “xpk”). By the way, in current crosswalk implementation, 
“loading app“ and “installing app“ shares common code.

 

Those are my concerns. It’s surely implementation point of view. I’m probably 
not aware about architecture decisions. Could you explain a bit more?

Could you provides more arguments about detaching installer from crosswalk and 
why this approach is better for architecture?

 

Regards,

Tomasz Iwanek

 

From: Crosswalk-dev [mailto:[email protected]] 
On Behalf Of Baptiste Durand
Sent: Wednesday, November 05, 2014 9:12 AM
To: [email protected]; [email protected]
Subject: [Crosswalk-dev] Tizen Application Installation process

 

Hi all, 



As announced a week ago, The web Installer is moving from crosswalk git to 
Tizen git.

https://www.mail-archive.com/[email protected]/msg01850.html

This has 1 direct consequence

-> All features related to crosswalk installer need to move from crosswalk JIRA 
to Tizen JIRA.

 

 

We want also introduce a new Framework or a new implementation for all 
installers ( for each type of applications)


We thinks that we need to harmonize all installers for all type of applications.
because all installer follows the same workflow/logic detailed here
https://wiki.tizen.org/wiki/Applications_Installer

In my opinion be sure that installers have the same workflow permits enforce 
the security of Tizen by enforce the security check

 

 

-> are there any objections to harmonize all installers ?

 

If not, any help is welcomed to improve this proposition

 

Thanks you

BR

Baptiste 

-- 

Baptiste DURAND
Eurogiciel Vannes/FR

_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev

Reply via email to