It is a complex issue, let me try to summarize my understanding of it
* We support multiple toolkits and we need a good to find out which toolkit
each activity uses.
* IMO trying to figure that out by analyzing the code is not good. Too
complicated and too fragile.
* We have a decent way to
2014-01-31 23:14 GMT-03:00 Daniel Narvaez dwnarv...@gmail.com:
On 1 February 2014 03:00, Sam Parkinson sam.parkins...@gmail.com wrote:
Hi,
Dnarvaez and I were discussing this on the irc; we really need to do
distinction between the tool kit version in activity.info.
This would be needed
2014-01-31 Daniel Narvaez dwnarv...@gmail.com:
On 1 February 2014 03:00, Sam Parkinson sam.parkins...@gmail.com wrote:
Hi,
Dnarvaez and I were discussing this on the irc; we really need to do
distinction between the tool kit version in activity.info.
This would be needed to for:
view
in the exec property in the activity.info file,
we have the information about the class to start.
Is not good enough check in that file?
Another easy alternative is check in the file setup.py
Honestly, I don't think we should add a new field in the activity.info file.
Gonzalo
Hi,
Dnarvaez and I were discussing this on the irc; we really need to do
distinction between the tool kit version in activity.info.
This would be needed to for:
- view source
- because now changes to sugar-toolkit-gtk3 can break the gtk2 toolkit
(!)
Basically we were thinking to make
On 1 February 2014 03:00, Sam Parkinson sam.parkins...@gmail.com wrote:
Hi,
Dnarvaez and I were discussing this on the irc; we really need to do
distinction between the tool kit version in activity.info.
This would be needed to for:
- view source
- because now changes to
6 matches
Mail list logo
