Re: [Sugar-devel] [Sur] Introducing SimpleActivity / Introduciendo SimpleActivity
Hi, now the StopButton is added automatically you don't have to call
self.add_stopbutton anymore :)
Regards,
aguz
2013/11/25 Manuel Quiñones ma...@laptop.org
2013/11/24 Agustin Zubiaga Sanchez a...@sugarlabs.org:
Manu,
I just added the __init__.py file.
About the StopButton, I added the function add_stopbutton in order to be
called when the activity developer finish its toolbar, because
SimpleActivity can't know where it's ready, I think the only way to do
this
is when the user adds any item to the toolbar, move (actually, remove and
insert again) the stopbutton with its separator to the end of the
toolbar,
but we would doing that every time an item is added and I think it
doesn't
make sense.
If there is a way to fix an item position, please let me know.
I guess you can consider this in the implementation of the add_to*
methods of SimpleActivity.
What I would do:
- in the constructor of simple activity, add the main toolbar and the
items that are always required: activity button, separator, stop
button.
- in the add_to* methods, consider the separator and stop button when
inserting the new elements. Insert them before.
About new signals style:
They look nicer, when I want to define a signal without a function, I
can do
my_signal = GObject.Signal('my_signal', arg_types=(int)) as you said,
then
where I should put that?
self.mysignal = GObject.Signal( ?
Yes, making the signal an attribute of the class sounds right.
--
.. manuq ..
___
Lista olpc-Sur
olpc-...@lists.laptop.org
http://lists.laptop.org/listinfo/olpc-sur
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Sur] Introducing SimpleActivity / Introduciendo SimpleActivity
Manu,
I just added the __init__.py file.
About the StopButton, I added the function add_stopbutton in order to be
called when the activity developer finish its toolbar, because
SimpleActivity can't know where it's ready, I think the only way to do this
is when the user adds any item to the toolbar, move (actually, remove and
insert again) the stopbutton with its separator to the end of the toolbar,
but we would doing that every time an item is added and I think it doesn't
make sense.
If there is a way to fix an item position, please let me know.
About new signals style:
They look nicer, when I want to define a signal without a function, I can
do
my_signal = GObject.Signal('my_signal', arg_types=(int)) as you said, then
where I should put that?
self.mysignal = GObject.Signal( ?
Regards,
aguz
2013/11/23 Manuel Quiñones ma...@laptop.org
Nice! I will try to use it in Browse. We should aim to zero code
duplication and make activities code easier.
I gave a quick look at the code. I think SimpleActivity should take
care of adding the Stop button. All activities will (must) have it.
Please add an empty __init__.py file so we can use it as a module.
A minor implementation thing: we started to use new style signals.
They are more pythonic. So instead of adding a class attribute
__gsignals__ you do:
my_signal = GObject.Signal('my_signal', arg_types=(int,))
other_gobject.connect('my_signal', my_signal_handler)
my_signal.emit(42)
Example: https://git.gnome.org/browse/pygobject/tree/examples/signal.py
Docstrings:
https://git.gnome.org/browse/pygobject/tree/gi/_gobject/signalhelper.py
2013/11/21 Agustin Zubiaga Sanchez a...@sugarlabs.org:
= English (Español debajo) =
Hi everyone,
I am writing to show you what I was developing those last days, in order
to
make simpler the developing of Sugar Activities, this module, micro
library
or whatever you want to call it, makes much more easier the processes
that
every activity does, for example create ToolButtons, add them to a
Toolbar
or implement collaboration which is difficult for any starter developer.
The main idea is include SimpleAcivity in our toolkit, but thinking about
all the review processes it takes, you can add it to your activity for
now
or you can take a look about how it works in the Demo activity I did [1],
where you can see how easy is to implement sharing or create the toolbar.
* SimpleActivity classes *
simpleactivity.SimpleActivity:
The activities which doesn't want to implement collaboration, can derive
from this class (instead of sugar3.activity.activity.Activity), this
class
automatically adds the toolbar to the activity with his
ActivityToolbarButton and it makes easier some processes related to the
design, e.g. add buttons, separators, or whatever to the toolbar in only
one
line and also other things related to the operation for example any
number,
string, dictionary or list that is saved into the self.data variable
will be
auto kept in the journal, and when the instance runs again, in self.data
will be what you leaved when the activity was closed.
Among these there are many other simple features, that after all, they do
everything much easier.
simpleactivity.SharedActivity (derives from SimpleActivity, you can use
all
its methods): :
From this class should derive every activity which needs to be shared,
the
process is greatly simplified cause the communication is done
automatically
and the system works with something like an event manager, so we only
need
to worry about register our events in a python dict, where the keys are
the
names of the events and the values are the functions to call when we
receive
an event, and when we want to emit an event with the values we need or
not, all we have to do is to call send_event(event_name, data)... And
that's
all, we don't have to worry about telepathy, dbus or anything like that,
SimpleActivity does everything for you :)
Also it includes an option to send files in a very easy way, using the
method send_file(file_path, data) that notifies every peer that a file is
available, and it can be downloaded just calling the download_file
method,
and then SharedActivity will start emiting signals with information
related
to the download progress, etc.
The process of downloading is done using another independent tube, then
nothing gets blocked while the file is sent/downloaded, we can continue
sending events while, and everything will continue working.
Notes:
- Both classes derives from the natives classes of sugar, so we can
continue using every method of sugar.activity.activity.Activity or
whatever,
without any problem.
- Whole SimpleActivity (module) is only one .py file, then we can put it
into our activity directory easily as we do with HelpButton or
FontComboBox,
even if it isn't in sugar toolkit.
- It only supports GTK3, I think
Re: [Sugar-devel] Python modules (Re: Introducing SimpleActivity / Introduciendo SimpleActivity
Yes, I was just thinking about that would be great to have a repository where to put every Sugar python modules, and what thinking about using git submodule but it doesn´t makes send for just a .py file, but we could use it for bigger libs as I do with sugar-pycha (lib) [1], that every activity can use, or the speak engine that Memorize for example uses. [1] http://git.sugarlabs.org/sugar-pycha Regards, aguz 2013/11/22 Daniel Narvaez dwnarv...@gmail.com Nice work, Augustin. I'm going a bit off topic here but in the future I think it would be nice if we had an easy way for activities to pull and update modules like these and include them directly in the bundle, a la nodejs/volojs. It should be easy to build something around distribute/pypi. That makes experimentation much easier because it doesn't force requirements on a new version of the OS, it allows to change the API without breaking the world etc. The disk space waste is negligible and the need of rebuilds to include fixes can be automated away. Really I think the toolkit shipped with the OS should completely go away in the long run. I know this will be controversial, but I thought it was worth to share the tought at least :) On 22 November 2013 02:19, Agustin Zubiaga Sanchez a...@sugarlabs.orgwrote: = English (Español debajo) = Hi everyone, I am writing to show you what I was developing those last days, in order to make simpler the developing of Sugar Activities, this module, micro library or whatever you want to call it, makes much more easier the processes that every activity does, for example create ToolButtons, add them to a Toolbar or implement collaboration which is difficult for any starter developer. The main idea is include SimpleAcivity in our toolkit, but thinking about all the review processes it takes, you can add it to your activity for now or you can take a look about how it works in the Demo activity I did [1], where you can see how easy is to implement sharing or create the toolbar. * SimpleActivity classes * simpleactivity.SimpleActivity: The activities which doesn't want to implement collaboration, can derive from this class (instead of sugar3.activity.activity.Activity), this class automatically adds the toolbar to the activity with his ActivityToolbarButton and it makes easier some processes related to the design, e.g. add buttons, separators, or whatever to the toolbar in only one line and also other things related to the operation for example any number, string, dictionary or list that is saved into the self.data variable will be auto kept in the journal, and when the instance runs again, in self.data will be what you leaved when the activity was closed. Among these there are many other simple features, that after all, they do everything much easier. simpleactivity.SharedActivity (derives from SimpleActivity, you can use all its methods): : From this class should derive every activity which needs to be shared, the process is greatly simplified cause the communication is done automatically and the system works with something like an event manager, so we only need to worry about register our events in a python dict, where the keys are the names of the events and the values are the functions to call when we receive an event, and when we want to emit an event with the values we need or not, all we have to do is to call send_event(event_name, data)... And that's all, we don't have to worry about telepathy, dbus or anything like that, SimpleActivity does everything for you :) Also it includes an option to send files in a very easy way, using the method send_file(file_path, data) that notifies every peer that a file is available, and it can be downloaded just calling the download_file method, and then SharedActivity will start emiting signals with information related to the download progress, etc. The process of downloading is done using another independent tube, then nothing gets blocked while the file is sent/downloaded, we can continue sending events while, and everything will continue working. Notes: - Both classes derives from the natives classes of sugar, so we can continue using every method of sugar.activity.activity.Activity or whatever, without any problem. - Whole SimpleActivity (module) is only one .py file, then we can put it into our activity directory easily as we do with HelpButton or FontComboBox, even if it isn't in sugar toolkit. - It only supports GTK3, I think it is not necessary to make it compatible with GTK2, because nowadays the new activities should be did in GTK3. - I advice everyone who is interested to take a look of the documentation that you can found in the docstrings in the file for now (I will create a cleaner documentation with sphinx), to learn about all you can do with SimpleActivity. Also I started a Feature wiki page [2], but is not ready yet. Could anyone help me with that? I need some documentation
Re: [Sugar-devel] [Olpc-uruguay] [Sugar-desarrollo] Introducing SimpleActivity / Introduciendo SimpleActivity
Muchas gracias por todo Eduardo, voy a ver si me doy una vuelta algun dia, yo les aviso :) Saludos, aguz 2013/11/22 eduardo duarte duarteeduardo...@gmail.com Felicitaciones Agustín !! desde Centro RAP y Espacio Ceibal Toledo - Canelones - Uruguay . Y nuestro impulso para que sigas adelante con todos tus proyectos que nos muestran en el mundo con toda tu capacidad innovadora con la tecnología de la herramienta Ceibal.- Estamos a las órdenes en nuestro Centro por si tenés tiempo uno de estos días y querés darte una vuelta, si llega a ser posible en el tiempo que sea organizamos (con previo aviso y tiempo) para que des tus charlas a todos nosotros e nuestras atenciones del Centro RAP y Espacio Ceibal de los miércoles en estas vaciones ! No te sientas comprometido, es solamente una invitación cordial para cuando te sobre un poquito de tiempo, y desde ya muchísimas gracias por tus aportes ! Nosotros estamos en la Biblioteca Mario Benedetti del Municipio de Toledo en la ciudad de Toledo - Canelones , ruta 6 , por cualquier contacto: duarteeduardo...@gmail.com y mi cel: 099139186 soy el responsable en territorio del Centro RAP y Espacio Ceibal Toledo, e integrante de RAP-Ceibal Uruguay.- Un abrazo. Eduardo Duarte - Centro RAP y Espacio Ceibal Toledo. duarteeduardo...@gmail.com centroraptol...@gmail.com 2013/11/22 Gonzalo Odiard gonz...@laptop.org Separated files to SimpleActivity and SharedActivity would be good, to avoid importing all the telepathy and network stuff if will not be used. I would like to see a HelloWorld example, the extreme minimal needed to create a activity. Gonzalo On Fri, Nov 22, 2013 at 10:18 AM, Agustin Zubiaga Sanchez a...@sugarlabs.org wrote: Thank you! James: I take your point... I am going to make separated branches one for collaboration and another for just a SimpleActivity Activity. I will try to do that today, anyway I will notify. Regards, aguz 2013/11/22 James Cameron qu...@laptop.org +1 I have reviewed simpleactivity.py and testactivity.py This code is very legible and explains well what it does, and can serve as an example for new activity authors. The docstrings in simpleactivity.py are an effective explanation of the simplified API, so perhaps you can generate the documentation from them in the usual Python fashion. Next to do is for a few activities to be developed using SimpleActivity, so that you can see what remains common to the new activities. The common code might then be added to SimpleActivity. testactivity.py is derived from SharedActivity, and so it is complex, because a collaborating activity is complex. I'd like to see also an activity example derived from SimpleActivity. The number of imports done by testactivity.py still seems high, and a SimpleActivity example may be able to reduce that. -- James Cameron http://quozl.linux.org.au/ ___ Sugar-Desarrollo mailing list sugar-desarro...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-desarrollo ___ Olpc-uruguay mailing list olpc-urug...@lists.laptop.org http://lists.laptop.org/listinfo/olpc-uruguay ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Olpc-uruguay] [Sugar-desarrollo] Introducing SimpleActivity / Introduciendo SimpleActivity
Thanks everyone and UPDATE: The classes are now in separated files for don't import all the sharing stuff if it is not necessary (simpleactivity.py - sharedactivity.py): If you want to implement collaboration you will have to put both files (because SharedActivity depends of SimpleActivity) in your activity, if not, you just have to include simpleactivity.py This change was proposed by Gonzalo. And now I am using the mainline repository is [1] just for these two files. The demo I tell you in my first email is now in the sharing-demo repository [2], and there is one more repository which is called demo where I will (not yet) put the demo without collaboration as requested by James. And also I cloned HelloWorld [3], and I make it use SimpleActivity, and was done in 14 lines (of code) plus license and other commented lines. [1] https://git.sugarlabs.org/simpleactivity/mainline [2] https://git.sugarlabs.org/simpleactivity/sharing-demo [3] https://git.sugarlabs.org/~aguzubiaga/hello-world/simpleactivity-helloworld Thank you for your review, aguz 2013/11/22 Agustin Zubiaga Sanchez a...@sugarlabs.org Muchas gracias por todo Eduardo, voy a ver si me doy una vuelta algun dia, yo les aviso :) Saludos, aguz 2013/11/22 eduardo duarte duarteeduardo...@gmail.com Felicitaciones Agustín !! desde Centro RAP y Espacio Ceibal Toledo - Canelones - Uruguay . Y nuestro impulso para que sigas adelante con todos tus proyectos que nos muestran en el mundo con toda tu capacidad innovadora con la tecnología de la herramienta Ceibal.- Estamos a las órdenes en nuestro Centro por si tenés tiempo uno de estos días y querés darte una vuelta, si llega a ser posible en el tiempo que sea organizamos (con previo aviso y tiempo) para que des tus charlas a todos nosotros e nuestras atenciones del Centro RAP y Espacio Ceibal de los miércoles en estas vaciones ! No te sientas comprometido, es solamente una invitación cordial para cuando te sobre un poquito de tiempo, y desde ya muchísimas gracias por tus aportes ! Nosotros estamos en la Biblioteca Mario Benedetti del Municipio de Toledo en la ciudad de Toledo - Canelones , ruta 6 , por cualquier contacto: duarteeduardo...@gmail.com y mi cel: 099139186 soy el responsable en territorio del Centro RAP y Espacio Ceibal Toledo, e integrante de RAP-Ceibal Uruguay.- Un abrazo. Eduardo Duarte - Centro RAP y Espacio Ceibal Toledo. duarteeduardo...@gmail.com centroraptol...@gmail.com 2013/11/22 Gonzalo Odiard gonz...@laptop.org Separated files to SimpleActivity and SharedActivity would be good, to avoid importing all the telepathy and network stuff if will not be used. I would like to see a HelloWorld example, the extreme minimal needed to create a activity. Gonzalo On Fri, Nov 22, 2013 at 10:18 AM, Agustin Zubiaga Sanchez a...@sugarlabs.org wrote: Thank you! James: I take your point... I am going to make separated branches one for collaboration and another for just a SimpleActivity Activity. I will try to do that today, anyway I will notify. Regards, aguz 2013/11/22 James Cameron qu...@laptop.org +1 I have reviewed simpleactivity.py and testactivity.py This code is very legible and explains well what it does, and can serve as an example for new activity authors. The docstrings in simpleactivity.py are an effective explanation of the simplified API, so perhaps you can generate the documentation from them in the usual Python fashion. Next to do is for a few activities to be developed using SimpleActivity, so that you can see what remains common to the new activities. The common code might then be added to SimpleActivity. testactivity.py is derived from SharedActivity, and so it is complex, because a collaborating activity is complex. I'd like to see also an activity example derived from SimpleActivity. The number of imports done by testactivity.py still seems high, and a SimpleActivity example may be able to reduce that. -- James Cameron http://quozl.linux.org.au/ ___ Sugar-Desarrollo mailing list sugar-desarro...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-desarrollo ___ Olpc-uruguay mailing list olpc-urug...@lists.laptop.org http://lists.laptop.org/listinfo/olpc-uruguay ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Introducing SimpleActivity / Introduciendo SimpleActivity
= English (Español debajo) = Hi everyone, I am writing to show you what I was developing those last days, in order to make simpler the developing of Sugar Activities, this module, micro library or whatever you want to call it, makes much more easier the processes that every activity does, for example create ToolButtons, add them to a Toolbar or implement collaboration which is difficult for any starter developer. The main idea is include SimpleAcivity in our toolkit, but thinking about all the review processes it takes, you can add it to your activity for now or you can take a look about how it works in the Demo activity I did [1], where you can see how easy is to implement sharing or create the toolbar. * SimpleActivity classes * simpleactivity.SimpleActivity: The activities which doesn't want to implement collaboration, can derive from this class (instead of sugar3.activity.activity.Activity), this class automatically adds the toolbar to the activity with his ActivityToolbarButton and it makes easier some processes related to the design, e.g. add buttons, separators, or whatever to the toolbar in only one line and also other things related to the operation for example any number, string, dictionary or list that is saved into the self.data variable will be auto kept in the journal, and when the instance runs again, in self.data will be what you leaved when the activity was closed. Among these there are many other simple features, that after all, they do everything much easier. simpleactivity.SharedActivity (derives from SimpleActivity, you can use all its methods): : From this class should derive every activity which needs to be shared, the process is greatly simplified cause the communication is done automatically and the system works with something like an event manager, so we only need to worry about register our events in a python dict, where the keys are the names of the events and the values are the functions to call when we receive an event, and when we want to emit an event with the values we need or not, all we have to do is to call send_event(event_name, data)... And that's all, we don't have to worry about telepathy, dbus or anything like that, SimpleActivity does everything for you :) Also it includes an option to send files in a very easy way, using the method send_file(file_path, data) that notifies every peer that a file is available, and it can be downloaded just calling the download_file method, and then SharedActivity will start emiting signals with information related to the download progress, etc. The process of downloading is done using another independent tube, then nothing gets blocked while the file is sent/downloaded, we can continue sending events while, and everything will continue working. Notes: - Both classes derives from the natives classes of sugar, so we can continue using every method of sugar.activity.activity.Activity or whatever, without any problem. - Whole SimpleActivity (module) is only one .py file, then we can put it into our activity directory easily as we do with HelpButton or FontComboBox, even if it isn't in sugar toolkit. - It only supports GTK3, I think it is not necessary to make it compatible with GTK2, because nowadays the new activities should be did in GTK3. - I advice everyone who is interested to take a look of the documentation that you can found in the docstrings in the file for now (I will create a cleaner documentation with sphinx), to learn about all you can do with SimpleActivity. Also I started a Feature wiki page [2], but is not ready yet. Could anyone help me with that? I need some documentation experts ;) I hope you find it useful, as I always say, I love developing for Sugar, because it causes a great feeling to know that the lines of code I wrote will be used directly or indirectly by millions of children around the world. [1] https://git.sugarlabs.org/simpleactivity/ [2] http://wiki.sugarlabs.org/go/Features/SimpleActivity Thank you very much, aguz - = Español = Hola a todos, Les escribo para presentarles lo que he estado desarrollando estos últimos días, con el fin de hacer más simple la creación de actividades para Sugar, este modulo, micro librería, o como quieran llamarle, hace mucho más fácil los procesos que todas las actividades hacen, como crear ToolButtons, agregarlos a una Toolbar o implementar colaboración para cualquier desarrollador que esté comenzando. La idea principal es incluir SimpleActivity en la toolkit de sugar, pero tomando en cuenta todos los procesos de revisados que lleva, pueden ver como funciona en el repositorio de la actividad de ejemplo HelloSimpleActivity [1], que implementa un montón de características, y donde pueden ver lo fácil que es implementar la colaboración o hacer la barra de herramientas. * Clases de simpleactivity * simpleactivity.SimpleActivity: Las actividades que NO deseen implementar colaboración, pueden simplemente heredar de esta clase (en lugar de
[Sugar-devel] Jukebox, reorder capability to playlist
Hi everyone! I am thinking in add this feature to Jukebox [1], in the next days for GCI 2013, but I need some tips about how implementing it (design). Some time ago I did some similar for Chart [2], with two simple arrow buttons [3] that work with the selected item. But in Jukebox, when you change the selection, it plays the selected item, and then this method won't work because you have to change the current playing track to reorder the list. So, what can I do? Use double-click to play the track and implement that feature like in Chart, or do something like drag and drop (I think it isn't a good idea)? I want you opinions :) [1] http://bugs.sugarlabs.org/ticket/4484 [2] http://activities.sugarlabs.org/es-ES/sugar/addon/4534 [3] http://people.sugarlabs.org/aguz/reorder-chart.png Greetings, aguz ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Jukebox, reorder capability to playlist
Yes, that's true...It will look strange but is better than double-click. Thank you Daniel, aguz 2013/11/17 Daniel Francis fran...@sugarlabs.org On Sunday, November 17, 2013 06:34:49 PM Agustin Zubiaga Sanchez wrote: So, what can I do? Use double-click to play the track and implement that feature like in Chart, or do something like drag and drop (I think it isn't a good idea)? I want you opinions :) Sugar was one of the first interfaces with no double-click. Specially now, running it on touch devices, forget the idea of double-click. Drag and drop is what most music players do for this case. If Drag and Drop doesn't look nice with TreeViews on Sugar, it could be a bug in sugar-artwork and we are in the right moment to make a design proposal :) Regards, Daniel. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar 0.100 Release Notes
Great! I did a minor change in the Background section [1] where it said Google Summer of Code instead of Google Code-IN 2012. Regards, aguz 2013/10/16 Martin Abente martin.abente.lah...@gmail.com Hey guys, Waiting for my connection at miami... I will arrive tonight 10:40 to SFC. Saludos, Tincho On Oct 16, 2013 1:08 PM, Gonzalo Odiard gonz...@laptop.org wrote: Testing 0.99 wiki page: http://wiki.sugarlabs.org/go/0.100/Testing Gonzalo On Wed, Oct 16, 2013 at 11:43 AM, Daniel Narvaez dwnarv...@gmail.comwrote: Nice work!!! On 16 October 2013 16:38, Gonzalo Odiard gonz...@laptop.org wrote: Martin Abente is traveling to SF and is a good opportunity to share the work we did in Sugar 0.100, request help to the community in testing, and promote the update of remote deployments. To help with this, I started a page with the format of our Release Notes http://wiki.sugarlabs.org/go/0.100/Notes I used information of the Feature pages, and tried to add information about who worked on what, as I think recognition is important. If you can fix / improve, can be a base for the official release notes. Remember my English is not very good, language bugs can happen. I am working in a Testing page and if have time, will update the testing images. Comments are welcome. Gonzalo -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [ASLO] Release Image Viewer-59
Here is the tarball for this release: http://people.sugarlabs.org/aguz/ImageViewer-59.tar.bz2 Thanks, aguz 2013/9/9 Sugar Labs Activities activit...@sugarlabs.org Activity Homepage: http://activities.sugarlabs.org/addon/4032 Sugar Platform: 0.98 - 0.100 Download Now: http://activities.sugarlabs.org/downloads/file/28766/image_viewer-59.xo Release notes: - Enable collaboration only when a file is loaded - SL#4549 - Replace the gtk dialog used to show transferece progress by a Alert - Pep8 fixes - New activity icon Sugar Labs Activities http://activities.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [ASLO] Release Image Viewer-58
Better late than never! Sorry for the long delay, releasing this version, here is the tarball: http://people.sugarlabs.org/aguz/ImageViewer-58.tar.bz2 Regards, aguz 2013/7/25 Sugar Labs Activities activit...@sugarlabs.org Activity Homepage: http://activities.sugarlabs.org/addon/4032 Sugar Platform: 0.100 - 0.100 Download Now: http://activities.sugarlabs.org/downloads/file/28706/image_viewer-58.xo Release notes: Avoid error opening the image with the object chooser - SL #4540 Sugar Labs Activities http://activities.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [ASLO] Release Image Viewer-56
Hi, everyone! I am alive :) The tarball for this release is here: [1] Thank you, aguz [1] http://people.sugarlabs.org/aguz/files/activities/ImageViewer-56.tar.bz2 2013/6/3 Sugar Labs Activities activit...@sugarlabs.org Activity Homepage: http://activities.sugarlabs.org/addon/4032 Sugar Platform: 0.96 - 0.100 Download Now: http://activities.sugarlabs.org/downloads/file/28642/image_viewer-56.xo Release notes: Fixing collaboration - SL #4520 Sugar Labs Activities http://activities.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [ASLO] Release Image Viewer-56
Yes, I know but I don't have permission to upload it there, could I get it? (for next releases, this one was uploaded by Gonzalo)... Thanks, aguz 2013/6/3 Peter Robinson pbrobin...@gmail.com On Mon, Jun 3, 2013 at 8:45 PM, Agustin Zubiaga Sanchez a...@sugarlabs.org wrote: Hi, everyone! I am alive :) The tarball for this release is here: [1] They're normally published here http://download.sugarlabs.org/sources/sucrose/fructose/ImageViewer/ Thank you, aguz [1] http://people.sugarlabs.org/aguz/files/activities/ImageViewer-56.tar.bz2 2013/6/3 Sugar Labs Activities activit...@sugarlabs.org Activity Homepage: http://activities.sugarlabs.org/addon/4032 Sugar Platform: 0.96 - 0.100 Download Now: http://activities.sugarlabs.org/downloads/file/28642/image_viewer-56.xo Release notes: Fixing collaboration - SL #4520 Sugar Labs Activities http://activities.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] We have a problem: activity._shared_activity
Gonzalo, Maybe would be good to create also the _shared_activity variable, with the purpose to let the activities continue working while the developers change _shared_actvity by shared_activity. What do you think? Regards, aguz 2013/2/27 Gonzalo Odiard gonz...@laptop.org After more testing, I found the problem is only with activities ported to gtk3, then the list of activities we need modify is reduced: distance: (activity.py) pippy: groupthink/sugar_tools.py and pippy/mainline/pippy_app.py) portfolio: (PortfolioActivity.py) (already solved in git) stopwatch: (activity.py) write: (AbiWordActivity.py) I have updated http://bugs.sugarlabs.org/ticket/4446. Gonzalo ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] Fwd: [gci-announce] Google Code-in 2012 Grand Prize Winners announced
Thanks Walter, and everyone in this great community, as I said in G+, I am very proud to be a a Sugar Labs Developer. :) thanks again, aguz 2013/2/4 Walter Bender walter.ben...@gmail.com I know most of you have already heard the news... Congratulations to Aguz and Aneesh. But also, thanks to all 52 contestants who completed Sugar Labs tasks. And thanks to their mentors from the community. We are still consolidating patches, but this work will have a major impact on Sugar 1.0. regards. -walter -- Forwarded message -- From: Google Code-in Announce gci-annou...@googlegroups.com Date: Mon, Feb 4, 2013 at 1:11 PM Subject: [gci-announce] Google Code-in 2012 Grand Prize Winners announced To: gci-annou...@googlegroups.com Congratulations to all 334 students who participated in Google Code-in 2012. The work all of you submitted was awesome! We hope you all learned more about open source development and are excited to continue working with these organizations or explore more open source organizations in the years to come. The Google Code-in 2012 Grand Prize Winners are listed below alphabetically by first name: Agustín Zubiaga, Uruguay - Sugar Labs Akshay S Kashyap, India - BRL-CAD Aleksandar Ivanov, Bulgaria - RTEMS Aneesh Dogra, India - Sugar Labs Aviral Dasgupta, India - Sahana Software Foundation Cezar El-Nazli, Romania - BRL-CAD Conor Flynn, Ireland - Apertium Drew Gottlieb, United States - Copyleft Games Group Illya Kovalevskyy, Ukraine - KDE Liezl Puzon, United States - Sahana Software Foundation Mathew Kallada, Canada - RTEMS Matthew Bauer, United States - The NetBSD Project Mingzhe Wang, China - The NetBSD Project Mohammed Nafees, India - KDE Nicolás Satragno, Argentina - The Fedora Project Przemysław Buczkowski, Poland - Haiku Qasim Iqbal, Canada - Apertium Samuel Kim, United States - Copyleft Games Group Vladimir Angelov, Bulgaria - Haiku Ze Yue Wu, Australia - The Fedora Project You can check out our blog post on the Google Open Source blog at: http://google-opensource.blogspot.com/2013/02/google-code-in-2012-grand-prize-winners.html Great job everyone! -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ IAEP -- It's An Education Project (not a laptop project!) i...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PROPOSAL] Inform the user when an activity is being installed and more
I'm not sure what is the proper behavior should be implemented. So, we could vote: Option 1: Don't install the activity automatically and show a message in the journal when we click it for first time, to confirm or cancel the installation. Option 2: Show an alert when we download or copy (from an external device) a .xo, immediately. That Alert could appear in the journal or in Browse, respectively. Vote for (you think is) the best option or suggest your own idea. Thanks, aguz 2013/1/16 Manuel Quiñones ma...@laptop.org 2013/1/16 Agustin Zubiaga Sanchez a...@sugarlabs.org: Well, so I will provide a patch the next week, I think. Go Agus, go! -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PROPOSAL] Inform the user when an activity is being installed and more
Well, so I will provide a patch the next week, I think. Regards. 2013/1/14 Manuel Quiñones ma...@laptop.org 2013/1/12 fors...@ozonline.com.au: On Sat, Jan 12, 2013 at 4:31 PM, Agustin Zubiaga Sanchez a...@sugarlabs.org wrote: Hi everybody, Now, if we download or copy a .xo to the journal, it is installed automatically and doesn't informs to the user that the activity is being installed. Is this a change in 13.1.0? I think in the past we installed the activity when was launched by first time. No, I don't think this is a recent change, its been this way for a long time. Your question though is good because it illustrates the merit of the proposal. The current behaviour is counter intuitive. Copying/downloading to Journal installs but deleting from Journal does not uninstall. Strangely, deleting from the Journal details view does uninstall or prevents the install when you arrive there from 'show in journal'. Sugar should make the process understandable, not black box, I support the proposal. Yes, Sugar should behave better in XO installs, and I celebrate Agustin proposal. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [PROPOSAL] Inform the user when an activity is being installed and more
Hi everybody, Now, if we download or copy a .xo to the journal, it is installed automatically and doesn't informs to the user that the activity is being installed. We could show an alert with a countdown to tell the user that one activity will be installed and give the option to cancel this installation. That alert can appear on the journal (when we copy a .xo from a external device) and in Browse when we are downloading one (instead of the alert which appears when the file is fully downloaded). And could be good to show the summary and another information about the bundle on the detail view of journal. What do you think about? Cheers, aguz ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Activities without summaries
Done in Chart, http://git.sugarlabs.org/simplegraph/simplegraph/commit/b7cde604937c2fb0160555d4cb3738b6188d942e Regards, aguz 2012/11/14 Manuel Kaufmann humi...@gmail.com On Wed, Nov 14, 2012 at 9:22 AM, Gonzalo Odiard gonz...@laptop.org wrote: -InfoSlicer.activity/activity/activity.info Done. http://git.sugarlabs.org/infoslicer/mainline/commit/142d6f43c28e2eb5364c9c93fedd91b15ec0dbad Thank you for this email. -- Kaufmann Manuel Blog: http://humitos.wordpress.com/ Porfolio: http://fotos.mkaufmann.com.ar/ PyAr: http://www.python.com.ar/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH sugar-artwork] Use 0px radius in GtkToolButton prelight state
Thanks manu!
Regards,
aguz
2012/11/2 Manuel Quiñones ma...@laptop.org
After discussion with Agus I now understand what is this about. The
main problem that needs to be solved is #3936 . But I don't see a
problem pushing this meanwhile.
Pushed as b3d4fad9 . Thank you Agustín!
2012/10/1 Agustin Zubiaga Sanchez a...@sugarlabs.org:
Hi Manu, if you put the mouse over a toolbutton with the gtk2 theme, you
will see a black square in the background (a toolbutton without a
border-radius). And this patch implements it...
Do you understand?
Regards,
aguz
2012/10/1 Manuel Quiñones ma...@laptop.org
Hey Agus,
What is the issue you are trying to fix? You must tell this in the
commit message.
If we change the border size in the different toolbutton states, is
possible that they provoke a resize in the toolbar.
2012/9/23 Agustin Zubiaga a...@sugarlabs.org:
Signed-off-by: Agustin Zubiaga a...@sugarlabs.org
---
gtk3/theme/gtk-widgets.css.em |1 +
1 file changed, 1 insertion(+)
diff --git a/gtk3/theme/gtk-widgets.css.em
b/gtk3/theme/gtk-widgets.css.em
index 24a4c17..97b9c23 100644
--- a/gtk3/theme/gtk-widgets.css.em
+++ b/gtk3/theme/gtk-widgets.css.em
@@ -543,6 +543,7 @@ SugarPaletteWindowWidget GtkToolButton .button {
.toolbar GtkToolButton .button:prelight,
SugarPaletteWindowWidget GtkToolButton .button:prelight {
background-color: @black;
+border-radius: 0px;
}
.toolbar SugarRadioToolButton *:active,
--
1.7.10.4
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
--
.. manuq ..
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
--
.. manuq ..
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [ASLO] Release Terminal-41
Hi all again, Manu, I think that we can get the maxium number of tabs based on the width of the screen What do you think? Regards, aguz 2012/10/10 Gonzalo Odiard gonz...@laptop.org This activity is compatible with sugar = 0.98 Gonzalo On Wed, Oct 10, 2012 at 4:36 PM, Coltivare Fiori coltivarefi...@connettivo.net wrote: On 10/10/2012 21:12, S. Daniel Francis wrote: 2012/10/10 Coltivare Fiori coltivarefi...@connettivo.net: I updated the Terminal Activity to version 41 on Sugar 0.96.1 and it failed to start. We already received a report. Try removing the Journal entries of Terminal, and then open the new version. No way Else, would be well received a log in this mailing list or in bugs.sugarlabs.org . 1349897498.414353 ERROR root: Could not find any typelib for Vte Traceback (most recent call last): File /usr/bin/sugar-activity, line 146, in module main() File /usr/bin/sugar-activity, line 104, in main module = __import__(module_name) File /home/me/Activities/Terminal.activity/terminal.py, line 29, in module from gi.repository import Vte ImportError: cannot import name Vte 1349897498.416679 DEBUG root: _cleanup_temp_files Exited with status 1, pid 1571 data (None, open file 'fdopen', mode 'w' at 0xadad498, '3df368412fb05d697135b6e37392c9ffdc8c8f66') Those logs are in ~/.sugar/default/logs/ or in the Log activity. You can find the log for a specific activity by its bundle id. In the case of Terminal, the bundle id is org.laptop.Terminal See you, Daniel. Ciao Ernesto ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [ASLO] Release Terminal-41
Yes Rafa, thanks for releasing it... El 09/10/2012 20:03, S. Daniel Francis fran...@sugarlabs.org escribió: 2012/10/9 Rafael Ortiz raf...@activitycentral.com: Release notes: * Initial GTK3 release (Port by S. Daniel Francis fran...@sugarlabs.org,Agustin Zubiaga Sanchez a...@sugarlabs.org). * Adding summary, Rafael Ortiz raf...@activitycentral.com * Testing by Flavio Danesse fdane...@activitycentral.com * Same tabs as Browse. (Also fill all the allowed space correctly.) Thanks for releasing it, Rafael. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] ImageViewer (gtk3) traceback
I added the message that is shown when no image is opened. [1] [2] [1] git.sugarlabs.org/imageviewer/mainline/commit/b845688a [2] people.sugarlabs.org/aguz/files/imageviewer-noimage.png Regards, aguz 2012/10/4 Agustin Zubiaga Sanchez a...@sugarlabs.org Well, I reversed this change [1] I will add the message in the empty canvas. [1] git.sugarlabs.org/imageviewer/mainline/commit/2269f7a8 Regards, aguz 2012/10/4 Manuel Quiñones ma...@laptop.org 2012/10/4 Agustin Zubiaga Sanchez a...@sugarlabs.org: +1 for all. Daniel, I have to discard the close, when the user don't choose any image? Yes just revert that change as it was before, then you can add the message in the empty canvas in another commit. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] ImageViewer (gtk3) traceback
Yes, It's intentional because If you not open any image it instance will be unusable. Is that ok? Regards, aguz 2012/10/4 Daniel Narvaez dwnarv...@gmail.com Hi Agus, I noticed a difference between the gtk2 and the gtk3 version. If you close the file picker in the gtk3 version the activity is also closed. Is that intentional? (I'm asking mostly because it breaks the UI tests, but there is probably also the problem of consistency with other activities like read and jukebox). ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] ImageViewer (gtk3) traceback
+1 for all. Daniel, I have to discard the close, when the user don't choose any image? Regards, aguz 2012/10/4 Manuel Quiñones ma...@laptop.org 2012/10/4 Manuel Kaufmann humi...@gmail.com: On Thu, Oct 4, 2012 at 1:54 PM, Gary Martin garycmar...@googlemail.com wrote: /me wonders if he dare mention this to Gonzalo as a solution for the same issue in Read Maybe we can design a widget for this and include it in sugar-toolkit-gtk3 so we will have more consistency between activities. What do you think? Yes, I'm sure we will get that generalized at one point, there's also duplicated code for the same in the Journal and home list view when there are not matches. Just not this cycle. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] ImageViewer (gtk3) traceback
Well, I reversed this change [1] I will add the message in the empty canvas. [1] git.sugarlabs.org/imageviewer/mainline/commit/2269f7a8 Regards, aguz 2012/10/4 Manuel Quiñones ma...@laptop.org 2012/10/4 Agustin Zubiaga Sanchez a...@sugarlabs.org: +1 for all. Daniel, I have to discard the close, when the user don't choose any image? Yes just revert that change as it was before, then you can add the message in the empty canvas in another commit. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] ImageViewer (gtk3) traceback
Hi Daniel, The bug is fixed in the repository [1] Do you want to have a new release? [1] git.sugarlabs.org/imageviewer/mainline/commit/7591e459 Regards, aguz 2012/10/3 Daniel Narvaez dwnarv...@gmail.com Hello, I added the gtk3 branch of the ImageViewer activity to buildbot but it's failing to show the file picker, which breaks our UI test. I get the following traceback Traceback (most recent call last): File /home/dnarvaez/Development/sugar-build/master/install/share/sugar/activities/ImageViewer.activity/ImageViewerActivity.py, line 266, in _show_picker_cb what_filter=mime.GENERIC_TYPE_IMAGE) TypeError: __init__() takes at most 3 arguments (5 given) -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [ASLO] Release Image Viewer-50
Hi, Peter and Alan, I did not know I had to create a tarball for the core activities. It's in the attachment. Regards, aguz 2012/10/2 Peter Robinson pbrobin...@gmail.com On Tue, Oct 2, 2012 at 6:51 AM, Alan Jhonn Aguiar Schwyn alan...@hotmail.com wrote: Date: Tue, 2 Oct 2012 06:46:37 +0100 Subject: Re: [Sugar-devel] [ASLO] Release Image Viewer-50 From: pbrobin...@gmail.com To: alan...@hotmail.com CC: sugar-devel@lists.sugarlabs.org On Tue, Oct 2, 2012 at 6:41 AM, Alan Jhonn Aguiar Schwyn alan...@hotmail.com wrote: Date: Tue, 2 Oct 2012 06:17:47 +0100 From: pbrobin...@gmail.com To: sugar-devel@lists.sugarlabs.org Subject: Re: [Sugar-devel] [ASLO] Release Image Viewer-50 On Tue, Oct 2, 2012 at 6:02 AM, Sugar Labs Activities activit...@sugarlabs.org wrote: Activity Homepage: http://activities.sugarlabs.org/addon/4032 Sugar Platform: 0.98 - 0.98 Download Now: http://activities.sugarlabs.org/downloads/file/28253/image_viewer-50.xo Release notes: Activity ported to gtk3. Draw the image using cairo. Can we have a tar ball release? For what are the tar ball?? All core Activity releases should have a corresponding tar file release. http://download.sugarlabs.org/sources/sucrose/fructose/ImageViewer/ For what? Make the .rpm / .deb installers? Yes ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ImageViewer-50.tar.bz2 Description: BZip2 compressed data ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] New release ImageViewer gtk3
Hi Simon, I think that would be nice, to have the gtk3 version in the master branch, but the master mantainer don't want to do it... Aleksey, can you tell us the reasons? Regards, aguz 2012/10/2 Gonzalo Odiard gonz...@laptop.org can we do the branching layout as discussed in [1]? The GTK+ 3 work should happen on master and the the gtk2 branch should be named sugar-0.96. See browse as an example [2]. It is important to keep the same style in all the activities to find the way around. In this case, the maintainer don't want work in master with the gtk3 version, and use the number scheme we decided. Aleksey say there are kids using Sugar without support for dotted versions, then don't want release gtk2 versions in this way. Gonzalo ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] touch_test.py resutls
Yes, I can help you but I don't have a touch XO, so I can't test it. However, I could program it hypothetically, if you want (and you can), to test my changes. Regards, aguz 2012/10/2 Manuel Kaufmann humi...@gmail.com On Mon, Oct 1, 2012 at 11:59 PM, Agustin Zubiaga Sanchez a...@sugarlabs.org wrote: Would be nice to have a touch example Activity. What do you think? Yes. I started a HelloTouchGestures some time ago when SugarGestures weren't developed yet and I used a known algorithm to match gestures. Do you want to migrate this activity to the new way (using from gi.repository import SugarGestures)? If you say yes, I can add you as commiter. This is the repo: * http://git.sugarlabs.org/hello-touch-gesture -- Kaufmann Manuel Blog: http://humitos.wordpress.com/ Porfolio: http://fotos.mkaufmann.com.ar/ PyAr: http://www.python.com.ar/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [ASLO] Release Image Viewer-50
Mhh, the server don't allow me to put the tarball. I can only access to my user [1] [1] people.sugarlabs.org/aguz Regards, aguz 2012/10/2 Gonzalo Odiard gonz...@laptop.org On Tue, Oct 2, 2012 at 9:55 AM, Simon Schampijer si...@schampijer.dewrote: On 10/02/2012 02:44 PM, Gonzalo Odiard wrote: Agus, You can upload the tar.bz2 to shell.sugarlabs.org:/upload/**sources/sucrose/fructose/**ImageViewer/ with scp Gonzalo (if he has permissions) True. He has a sugarlabs user, I don't know if can write in the dir. Agus, if you have any problem tell me. Gonzalo __**_ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.**org Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/**listinfo/sugar-develhttp://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [ASLO] Release Image Viewer-50
Hi Chris, For me is a pleasure to contribute to the sugar development, is a pleasure to program with the people who made possible for me to enter the world of the computers :) I received my XO when I was 9, at the primary school and two years later I started python programming and now it is my favourite hobbie. Thanks for everything! Regards, aguz 2012/10/2 Chris Leonard cjlhomeaddr...@gmail.com On Tue, Oct 2, 2012 at 11:02 AM, Manuel Quiñones ma...@laptop.org wrote: 2012/10/2 Agustin Zubiaga Sanchez a...@sugarlabs.org: Mhh, the server don't allow me to put the tarball. Please ask the infra team so you can do it by yourself the next time. Agustin, Amidst the discussion of how to submit new versions so that it is seamlessly farmed out for packaging, etc. I wanted to pause and thank you for creating an improved version of ImageViewer. I think there is a certain understandable tendency among people as busy and productive as our Sugar Developers to forget that it can take a little time for a new contributor to get indoctrinated in to the way we do things, but as you also see, there are people who are more than eager to help teach you the ropes. Thanks for your contributions. cjl ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH sugar-artwork] Use 0px radius in GtkToolButton prelight state
Hi Manu, if you put the mouse over a toolbutton with the gtk2 theme, you
will see a black square in the background (a toolbutton without a
border-radius). And this patch implements it...
Do you understand?
Regards,
aguz
2012/10/1 Manuel Quiñones ma...@laptop.org
Hey Agus,
What is the issue you are trying to fix? You must tell this in the
commit message.
If we change the border size in the different toolbutton states, is
possible that they provoke a resize in the toolbar.
2012/9/23 Agustin Zubiaga a...@sugarlabs.org:
Signed-off-by: Agustin Zubiaga a...@sugarlabs.org
---
gtk3/theme/gtk-widgets.css.em |1 +
1 file changed, 1 insertion(+)
diff --git a/gtk3/theme/gtk-widgets.css.em
b/gtk3/theme/gtk-widgets.css.em
index 24a4c17..97b9c23 100644
--- a/gtk3/theme/gtk-widgets.css.em
+++ b/gtk3/theme/gtk-widgets.css.em
@@ -543,6 +543,7 @@ SugarPaletteWindowWidget GtkToolButton .button {
.toolbar GtkToolButton .button:prelight,
SugarPaletteWindowWidget GtkToolButton .button:prelight {
background-color: @black;
+border-radius: 0px;
}
.toolbar SugarRadioToolButton *:active,
--
1.7.10.4
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
--
.. manuq ..
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] touch_test.py resutls
Hi, everybody Would be nice to have a touch example Activity. What do you think? Regards, aguz 2012/10/1 Gonzalo Odiard gonz...@laptop.org Well, multitouch is supported by that example, for gestures, I am waiting have the api a little more defined. Gonzalo Be nice to fold in gesture and multitouch as well... -walter Gonzalo On Fri, Sep 28, 2012 at 6:49 PM, Walter Bender walter.ben...@gmail.com wrote: I've modified Gonzalo's touch_test.py program [1] in order to test combining touch and pointer events and in order to analyze differences between XO 1.75T and XO 4.0. The attached program seems to behave as expected on 1.75 (dragging works with both touch and pointer), but not on 4.0 (dragging only works with the pointer). regards. -walter -- Walter Bender Sugar Labs http://www.sugarlabs.org [1] http://git.sugarlabs.org/many-tests/mainline/blobs/master/touch_test.py -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] New release ImageViewer gtk3
Hi Gonzalo! Can you apply the attached patches, and release a activity version,only for Sugar 0.98 to 0.98? As we need use integer version numbers, we can use a big number, may be 50 or 100, The patches are great, I already applied them [1] [2]. Yes, I will release the new version today or tomorrow. A pending task with the port to cairo is center the image on the screen. I uploaded a new patch [3] that put the image in the center of the screen. [1] git.sugarlabs.org/imageviewer/mainline/commit/e7f0e684 [2] git.sugarlabs.org/imageviewer/mainline/commit/ecb1f865 [3] git.sugarlabs.org/imageviewer/mainline/commit/03e5e85f Regards, aguz 2012/10/1 Gonzalo Odiard gonz...@laptop.org Hi Agustin, Looks like your gtk branch is the more official place to continue the work to port to gtk3 and add touch support. Can you apply the attached patches, and release a activity version,only for Sugar 0.98 to 0.98? As we need use integer version numbers, we can use a big number, may be 50 or 100, to allow release of new integer versions of gtk2 branch too. A pending task with the port to cairo is center the image on the screen. I already added you as a ImageViewer developer on ASLO. Touch support is a ongoing task, we will be in contact. Gonzalo ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] Sugar Digest 2012-09-18
Hi, everybody. Like Daniel, I'm from Uruguay and I feel identified with the Walter message. I'm fourteen years old, and I started using sugar when I was ten, when I receive my XO was the first time that I used linux and it liked me a lot. About the young programmers: I was a student of Flavio Danesse, and he taught me a lot but for obvious reasons I had to appeal the internet to found more information, where the most are in english, for me it wasn't a problem, because I have learned english. But the most of the children in Latin America hasn't this luck, and they find it difficult to program. About sugar and the teachers: Unfortunately, when I was in primary school, no teacher was concerned with explaining how to use my XO, and the logical sugar activities, such as Turtle Art and Scratch, but luckily their interfaces are very intuitive. And when I started the high school was the same, no teacher was interested in the XO, except Mr. Flavio Danesse :) For this reason the most of my classmates, only use their XO to browse in Facebook and other social networks. Regards, Agustin Zubiaga ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] sugar-build broken
Yes, I did make 'git pull' But doing 'make build-gtk+', the problem was solved. Sorry, for the noise Regards, aguz 2012/9/10 Simon Schampijer si...@schampijer.de On 09/11/2012 03:25 AM, Agustin Zubiaga Sanchez wrote: Hello everybody, Today, I have compiled sugar-build again and it finished successful, but when I opened sugar (make run), appeared only the home toolbar and in some seconds, it has closed. I send my shell.log in the attachment. Regards, aguz Hi Augustin, did you make a 'git pull' in sugar-build first and then a 'make build'? The error points to your build missing a patch in GTK+, in latest sugar-build we do build GTK+ as well inside it containing this patch. If you updated an existing sugar-build maybe the new dep has not been build automatically. You can do 'make build-gtk+' then but you would probably miss other dependencies then. Regards, Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] sugar-build broken
Hi Daniel, I sent the logs to your e-mail. 2012/9/11 Daniel Narvaez dwnarv...@gmail.com Hi, could you please make bug-report and send me the resulting tarball. I would like to understand why gtk+ was not built the first time. On 11 September 2012 14:25, Agustin Zubiaga Sanchez a...@sugarlabs.org wrote: Yes, I did make 'git pull' But doing 'make build-gtk+', the problem was solved. Sorry, for the noise Regards, aguz 2012/9/10 Simon Schampijer si...@schampijer.de On 09/11/2012 03:25 AM, Agustin Zubiaga Sanchez wrote: Hello everybody, Today, I have compiled sugar-build again and it finished successful, but when I opened sugar (make run), appeared only the home toolbar and in some seconds, it has closed. I send my shell.log in the attachment. Regards, aguz Hi Augustin, did you make a 'git pull' in sugar-build first and then a 'make build'? The error points to your build missing a patch in GTK+, in latest sugar-build we do build GTK+ as well inside it containing this patch. If you updated an existing sugar-build maybe the new dep has not been build automatically. You can do 'make build-gtk+' then but you would probably miss other dependencies then. Regards, Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] sugar-build broken
Hello everybody, Today, I have compiled sugar-build again and it finished successful, but when I opened sugar (make run), appeared only the home toolbar and in some seconds, it has closed. I send my shell.log in the attachment. Regards, aguz shell.log Description: Binary data ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Design] Accelerometer icon
Hi Manu, thanks for your feedback. What do you (everybody) say? Can I apply the patch? Regards, aguz 2012/9/3 Manuel Quiñones ma...@laptop.org 2012/9/3 Agustin Zubiaga Sanchez a...@sugarlabs.org: Great, +1 to auto screen rotation Agustin, your patch works great, thanks! Let's see what happens with auto-rotate first. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Design] Accelerometer icon
Ok, I think the auto rotation is better, because all the GUI is rotated. 2012/9/4 Manuel Quiñones ma...@laptop.org 2012/9/4 Agustin Zubiaga Sanchez a...@sugarlabs.org: Hi Manu, thanks for your feedback. What do you (everybody) say? Can I apply the patch? Agus, I was suggesting wait to see what happens with the system-wide auto rotation. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Design] Accelerometer icon
Hi everybody, Some days ago I sent a patch for ImageViewer, that adds the use of the accelerometer to rotate images in this activity. I am maintainer then I can apply this patch, but I want to know your opinion. Regards, aguz 2012/8/31 Gary Martin garycmar...@googlemail.com On 31 Aug 2012, at 13:44, Manuel Kaufmann humi...@gmail.com wrote: On Thu, Aug 30, 2012 at 7:21 AM, Walter Bender walter.ben...@gmail.com wrote: I use the accelerometer if it available. If not, I fall; back to the keyboard. I think that would be a reasonable approach for Maze as well. I think in Maze would be good to have the option to use the accelerometer or not because Maze can be played with more that one player, and in that case you need the keyboard. It could be really difficult to play a multiplayer Maze Game if one of them is using the accelerometer :) +1, Maze and Physics both need to provide a toggle option, although sometimes fun, accelerometer input is often impractical, inaccurate, and non obvious in many cases *, though the default state should be up to the activity author. * phone size devices are more practicle, but tablet size and up are only good for limited use or in special use cases of the sensor (landscape/portrait detection, movement monitoring, how bumpy is your journey to school, pedometer counting activity/game). Regards, --Gary -- Kaufmann Manuel Blog: http://humitos.wordpress.com/ Porfolio: http://fotos.mkaufmann.com.ar/ PyAr: http://www.python.com.ar/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Design] Accelerometer icon
Great, +1 to auto screen rotation 2012/9/2 Gary Martin garycmar...@googlemail.com Hi Agustin, Early in the current development cycle there were/are plans to enable system wide auto screen rotation using the accelerometer when in ebook mode (there was a chance we might loose the physical rotate button on the display). Using the accelerometer to rotate the image inside Image Viewer would likely prove frustrating if the system was also auto rotating the screen. If we enable system wide auto rotate (in ebook mode) this does raise the case for allowing Activities the option of blocking accelerometer auto rotation if they are the front most activity so they can customise the experience. Walter, this probably affects you more than others at the moment, what are your thought on auto rotate an activity accelerometer use? Regards, --Gary On 2 Sep 2012, at 21:31, Agustin Zubiaga Sanchez a...@sugarlabs.org wrote: Hi everybody, Some days ago I sent a patch for ImageViewer, that adds the use of the accelerometer to rotate images in this activity. I am maintainer then I can apply this patch, but I want to know your opinion. Regards, aguz 2012/8/31 Gary Martin garycmar...@googlemail.com On 31 Aug 2012, at 13:44, Manuel Kaufmann humi...@gmail.com wrote: On Thu, Aug 30, 2012 at 7:21 AM, Walter Bender walter.ben...@gmail.com wrote: I use the accelerometer if it available. If not, I fall; back to the keyboard. I think that would be a reasonable approach for Maze as well. I think in Maze would be good to have the option to use the accelerometer or not because Maze can be played with more that one player, and in that case you need the keyboard. It could be really difficult to play a multiplayer Maze Game if one of them is using the accelerometer :) +1, Maze and Physics both need to provide a toggle option, although sometimes fun, accelerometer input is often impractical, inaccurate, and non obvious in many cases *, though the default state should be up to the activity author. * phone size devices are more practicle, but tablet size and up are only good for limited use or in special use cases of the sensor (landscape/portrait detection, movement monitoring, how bumpy is your journey to school, pedometer counting activity/game). Regards, --Gary -- Kaufmann Manuel Blog: http://humitos.wordpress.com/ Porfolio: http://fotos.mkaufmann.com.ar/ PyAr: http://www.python.com.ar/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] questions
About it, I would like to have a module in the sugar-toolkit, that would gives accelerometer data, such as inclination angle. What do you think? 2012/8/8 Gonzalo Odiard gonz...@laptop.org On Wed, Aug 8, 2012 at 4:18 PM, Flavio Danesse fdane...@gmail.com wrote: questions: 1 - You have to migrate to TelepathyGlib telepathy? I suppose so, but it was migrated to Sugar? I suppose no, but erikos can confirm. 2 - How I can I query the system to check for touch monitor? This is a good question. Should be good have in sugar-toolkit-gtk3 a way to know: * If we are in a XO or not. * XO version. * Acceleromenter available * Touch screen available. We already have code to ask this questions in a lot of activities, and this (or the moment when are ported to gtk3) is a good moment to replace it Gonzalo Preguntas: 1- Hay que migrar telepathy a TelepathyGlib ? Supongo que si, pero ya se migró esto en Sugar ? 2- Como puedo debo consultar al sistema para saber si tiene monitor touch ? ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Examples objects support for activities.
Hi, some days ago I was talking with Walter also about it. And I have started with the examplechooser, it isn't very difficult to do, only using a treeview and modifying his base color to white, you can obtain a very similar widget. I sent my advance in the attachment, lacks a lot, but we can start from here. Regards, aguz. 2012/7/20 Walter Bender walter.ben...@gmail.com On Thu, Jul 19, 2012 at 8:02 PM, Gonzalo Odiard gonz...@laptop.org wrote: Hello Tincho! Nice to read you here again :) Yes. Nice that Tincho is back. I agree this can be a very good addition, and I see think we need solve two different parts: 1) Access the examples in the activities: using a widget similar to the object chooser, but showing files in a directory. I think Silbe said, the actual Object Chooser can't do it, due to limitations in the actual Journal implementation. (Sascha, can you confirm?) Probably we can create a a similar widget if is not possible use the original ObjectChooser, and should be great can show a preview if available. 2) Distribution of examples: This can be more controversial, but is related and should be good address in a related proposal. Today, there are activities as Turtle Confusion or Amazonas Tortugas, based on TurtleArt and may be can be data files added to TurtleArt. Also, if we provide a way to distribute examples, the deployments could generate them based in local needs. Other activities can be enhanced using examples, and if they have text should be difficult support i18n in the data files. May be we can create a variation of the infamous XOL files, with the information about what activity should manage them, and improve the installation to install them in a different place than Library (or the activities can look at the Library for examples) Gonzalo Sounds dangerously close to the plugin mechanism I implemented for Turtle Art. Be nice to think that through in a more general way but I think that would be a different thread. regards. -walter On Thu, Jul 19, 2012 at 2:40 PM, Martin Abente martin.abente.lah...@gmail.com wrote: Hello Everyone: In a recent conversation with Walter, he mentioned that it would be very useful if activities could include examples objects. From my experience in the field, I can tell this feature can be a really useful indeed. Therefore I would like to bring this idea to the general discussion and see what others think. The idea is simple: Activities include examples objects that can be bundled with and accessed from the activity. For the ones that also think this could be useful: I am sure you must have your own vision of how this feature should work and look like, so please share it here. In general terms and from my POV it should be something: (a) simple to access. (b) with a familiar interface to the users. (c) low-cost for activities developers to include. (d) Safe. One of the ideas, that meets these requirements, is to include a standard Examples folder in the activities root directory that would be accessible through a regular ObjetChooser. The ObjectChooser is already capable of presenting any folder's contents, thanks to recent years improvement in the journal to present external-media and documents-folder contents. Accessing to these objects would be as easy as just opening a ObjectChooser instance, many activities already do this (but limited to journal content). As I just said, the ObjectChooser interface is widely used, therefore users are already familiar with it. To ease the costs for activities developers I think that having this standard folder approach is crucial. One open question I still have is how this ObjectChooser should be opened from the activities in a standard way (suggestions?). By safe I mean that it should guarantee that it only presents this standard folder objects in read-only mode (at least from the GUI POV). I will stop here and I would like to hear what you guys think regarding the general idea first. Saludos. tincho. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel examplechooser.py Description: Binary data ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH ImageViewer] GTK3 Port
Hi, I created the gtk3 branch [1] and I uploaded my patch [2]. Thanks. [1] git.sugarlabs.org/imageviewer/mainline/commits/gtk3 [2] git.sugarlabs.org/imageviewer/mainline/commit/c5fda0d0 2012/7/17 Gonzalo Odiard gonz...@laptop.org The name of the branches is not related with having gtk2 or gtk3 releases, you can continue releasing gtk2 versions without problem. The only issue should be adding strings to pootle, but can be solved. Using the proposed branching [1] and versioning [2] should be good to have uniformity in the project. Also branching for a gtk2 version means you ever will have a gtk2 version available, if you branch for gtk3, and later merge with master, you will loose the ability to do new gtk2 releases (or need create later a gtk2 branch, as is proposed today) Gonzalo [1] http://wiki.sugarlabs.org/go/Features/GTK3/Porting#Preparation [2] http://wiki.sugarlabs.org/go/Features/GTK3/Porting#Versioning Sorry, I disagree here for one simple reason. The purpose of Image Viewer existance is not switching to new GUI toolkit version as fast as it appears, but do something useful for people who use it. So, the master branch should have version that the most poeple use (to simplify regular development process). Since the most of Image Viewer users are from Sugar deployemnts and use gtk2, gtk2 should be in master until people will start switching to gtk3. The exception is if Image Viewer will, somehow, handle gtk2/gtk3 at once (didn't look for such possibility). I've added you to http://git.sugarlabs.org/imageviewer. Flavio Danesse: if you are also will take part in gtk3 porting, post you nick on git.sl.o to add. -- Aleksey ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH ImageViewer] GTK3 Port
Great, but the correct way to do this is leaving gtk3 in the master branch and creating a new one for the gtk2. Thanks! 2012/7/16 Rafael Ortiz raf...@activitycentral.com On Mon, Jul 16, 2012 at 4:49 AM, Aleksey Lim alsr...@sugarlabs.orgwrote: On Sun, Jul 08, 2012 at 07:02:27AM -0300, Agustin Zubiaga Sanchez wrote: Feedbacks? Could you and/or Flavio Danesse, if I got dirakx right, take care about gtk3 branch? And maybe preparing gtk3 releases. If yes, I can create gtk3 branch in Image Viewer sources and grant you access. +1 thanks aleksey. -- Aleksey ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH ImageViewer] GTK3 Port
Feedbacks?
2012/7/1 Agustin Zubiaga a...@sugarlabs.org
Signed-off-by: Agustin Zubiaga a...@sugarlabs.org
Signed-off-by: Flavio Danesse fdane...@gmail.com
---
ImageView.py | 123
+---
ImageViewerActivity.py | 75 ++---
ProgressDialog.py | 14 +++---
3 files changed, 108 insertions(+), 104 deletions(-)
diff --git a/ImageView.py b/ImageView.py
index 538c5b5..39556d7 100644
--- a/ImageView.py
+++ b/ImageView.py
@@ -17,9 +17,11 @@
from __future__ import division
-import gtk
-from gtk import gdk
-import gobject
+from gi.repository import Gtk
+from gi.repository import Gdk
+from gi.repository import GdkPixbuf
+from gi.repository import cairo
+from gi.repository import GObject
import sys
import logging
@@ -27,39 +29,42 @@ import logging
import random
-class ImageViewer(gtk.DrawingArea):
+class ImageViewer(Gtk.DrawingArea):
__gsignals__ = {
-'expose-event': (
-'override'),
+#'expose-event': (
+#'override'),
'zoom-changed': (
-gobject.SIGNAL_RUN_FIRST, gobject.TYPE_NONE, []),
+GObject.SignalFlags.RUN_FIRST, None, []),
'angle-changed': (
-gobject.SIGNAL_RUN_FIRST, gobject.TYPE_NONE, []),
+GObject.SignalFlags.RUN_FIRST, None, []),
}
__gproperties__ = {
'zoom': (
-gobject.TYPE_FLOAT, 'Zoom Factor', 'Factor of zoom',
-0, 4, 1, gobject.PARAM_READWRITE),
+GObject.TYPE_FLOAT, 'Zoom Factor', 'Factor of zoom',
+0, 4, 1, GObject.PARAM_READWRITE),
'angle': (
-gobject.TYPE_INT, 'Angle', 'Angle of rotation',
-0, 360, 0, gobject.PARAM_READWRITE),
+GObject.TYPE_INT, 'Angle', 'Angle of rotation',
+0, 360, 0, GObject.PARAM_READWRITE),
'file_location': (
-gobject.TYPE_STRING, 'File Location', 'Location of the image
file',
-'', gobject.PARAM_READWRITE),
+GObject.TYPE_STRING, 'File Location', 'Location of the image
file',
+'', GObject.PARAM_READWRITE),
}
def __init__(self):
-gtk.DrawingArea.__init__(self)
+GObject.GObject.__init__(self)
self.set_app_paintable(True)
self.pixbuf = None
self.zoom = None
+self.parent = None
self.file_location = None
self._temp_pixbuf = None
self._image_changed_flag = True
self._optimal_zoom_flag = True
+self.connect('draw', self.draw)
+
self.angle = 0
def do_get_property(self, pspec):
@@ -90,19 +95,7 @@ class ImageViewer(gtk.DrawingArea):
if self._optimal_zoom_flag:
self._set_zoom(self._calc_optimal_zoom())
-#def do_size_request(self, requisition):
-#requisition.width = self.pixbuf.get_width()
-#requisition.height = self.pixbuf.get_height()
-
-def do_expose_event(self, event):
-ctx = self.window.cairo_create()
-
-ctx.rectangle(event.area.x, event.area.y,
-event.area.width, event.area.height)
-ctx.clip()
-self.draw(ctx)
-
-def draw(self, ctx):
+def draw(self, widget, ctx):
if not self.pixbuf:
return
if self.zoom is None:
@@ -130,7 +123,7 @@ class ImageViewer(gtk.DrawingArea):
self.set_size_request(self._temp_pixbuf.get_width(),
self._temp_pixbuf.get_height())
-ctx.set_source_pixbuf(self._temp_pixbuf, x, y)
+Gdk.cairo_set_source_pixbuf(ctx, self._temp_pixbuf, x, y)
ctx.paint()
@@ -144,12 +137,15 @@ class ImageViewer(gtk.DrawingArea):
self.angle = angle
-if self.window:
+if self.props.window:
alloc = self.get_allocation()
-rect = gdk.Rectangle(alloc.x, alloc.y,
-alloc.width, alloc.height)
-self.window.invalidate_rect(rect, True)
-self.window.process_updates(True)
+rect = cairo.RectangleInt()
+rect.x = alloc.x
+rect.y = alloc.y
+rect.width = alloc.width
+rect.height = alloc.height
+self.props.window.invalidate_rect(rect, True)
+self.props.window.process_updates(True)
self.emit('angle-changed')
@@ -168,24 +164,27 @@ class ImageViewer(gtk.DrawingArea):
return True
def set_file_location(self, file_location):
-self.pixbuf = gtk.gdk.pixbuf_new_from_file(file_location)
+self.pixbuf = GdkPixbuf.Pixbuf.new_from_file(file_location)
self.file_location = file_location
self.zoom = None
self._image_changed_flag = True
-if self.window:
+if self.props.window:
alloc = self.get_allocation()
-rect =
Re: [Sugar-devel] [PATCH sugar-toolkit-gtk3] Fixing deprecations: Using Gtk.Orientation
+1 for the Daniel's idea. El 27/06/2012 09:52, S. Daniel Francis fran...@sugarlabs.org escribió: 2012/6/27 Gonzalo Odiard gonz...@laptop.org: Why not? Lets migrate all our gtk3 components to GtkGrid! We should check if the move to GtkGrid is really free of charge. There are a lot to change right now, and if changing the boxes break (or change visuals) in subtle ways, will be a headache. If we want to get the same visual appearance than with the Gtk Boxes I suggest make a Box class which inherits from GtkGrid in the Sugar API. Because the way to get the same results can be very long with grids. Then, should be good test it, before doing a massive search and replace. Gonzalo ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH Read] Use Box, ButtonBox, Scrollbar instead of his deprecated form
Hi, James
sorry, I didn't want to do it.
Can you remove it?
2012/6/27 Rafael Ortiz raf...@activitycentral.com
On Tue, Jun 26, 2012 at 9:20 PM, James Cameron qu...@laptop.org wrote:
Thanks for the patch. I have review comments for one change:
On Tue, Jun 26, 2012 at 10:53:57PM -0300, Agustin Zubiaga wrote:
[...]
diff --git a/readtopbar.py b/readtopbar.py
index d0da3d0..b6fe196 100644
--- a/readtopbar.py
+++ b/readtopbar.py
@@ -33,15 +33,16 @@ _UP_DEVICE_IFACE = 'org.freedesktop.UPower.Device'
_UP_TYPE_BATTERY = 2
-class _TopBar(Gtk.HBox):
+class _TopBar(Gtk.Box):
__gproperties__ = {
'completion-level': (float, None, None, 0.0, 100.0, 0.0,
GObject.ParamFlags.WRITABLE),
}
def __init__(self):
-Gtk.HBox.__init__(self)
+Gtk.Box.__init__(self)
+self.set_orientation(Gtk.Orientation.VERTICAL)
self.set_border_width(int(style.DEFAULT_SPACING / 2.0))
self.set_spacing(style.DEFAULT_SPACING * 4)
In this change you move from an Horizontal Box to a Box, but set the
orientation to vertical. I could not tell if this was desired. If
this is a desired change, perhaps it should be mentioned in the patch
comment.
The other changes looked fine.
Same comment as James, other than that is +1.
.
--
James Cameron
http://quozl.linux.org.au/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
--
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH Read] Use Box, ButtonBox, Scrollbar instead of his deprecated form
Ok, In this message I send my patch again but without this line. Regards, aguz 2012/6/27 James Cameron qu...@laptop.org On Wed, Jun 27, 2012 at 12:19:55AM -0300, Agustin Zubiaga Sanchez wrote: sorry, I didn't want to do it. Can you remove it? No, not me. This brings up an interesting process question. If I was a committer, I would modify and apply the patch. You would then have to merge the conflict. However, often I see people being asked to resubmit, which for a simple change seems a waste of time. -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- 0001-Use-Box-ButtonBox-Scrollbar-instead-of-his-deprecate.patch Description: Binary data ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH] Help Button with useful commands
Ok,
I uploaded this patch to the remote repository [1]
I commited the deprecation corrections [2]
And I uploaded some help corrections [3]
I think the help must be only the utility and the description. In the
start/end (I'm not sure), a paragraph describing something like 'Type:
{command} --help to see it's usage'
I like your idea, it's simple and more friendly for the children.
Let's go!
[1] git.sugarlabs.org/terminal/mainline/commit/e44a2997
[2] git.sugarlabs.org/terminal/mainline/commit/6f706a0c
[3] git.sugarlabs.org/terminal/mainline/commit/1f3c5148
Regards,
aguz
2012/6/22 Rafael Ortiz raf...@activitycentral.com
Hi Agus.
On 6/21/12, Agustin Zubiaga a...@sugarlabs.org wrote:
Gonzalo's button ported to GTK3
Bugs:
Wrap mode doesn't work
Grey background
Signed-off-by: Agustin Zubiaga a...@sugarlabs.org
---
helpbutton.py | 85
+++
icons/help-icon.svg | 14 +
terminal.py | 33
3 files changed, 132 insertions(+)
create mode 100644 helpbutton.py
create mode 100644 icons/help-icon.svg
diff --git a/helpbutton.py b/helpbutton.py
new file mode 100644
index 000..1f01851
--- /dev/null
+++ b/helpbutton.py
@@ -0,0 +1,85 @@
+#!/usr/bin/env python
+# -*- coding: utf-8 -*-
+# Copyright (C) 2012, Gonzalo Odiard godi...@gmail.com
+
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 3 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write to the Free Software
+# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301
USA
+
+# HelpButton widget
+
+from gettext import gettext as _
+
+from gi.repository import Gtk
+from gi.repository import Gdk
+from gi.repository import GObject
+
+from sugar3.graphics.toolbutton import ToolButton
+from sugar3.graphics.icon import Icon
+from sugar3.graphics import style
+
+
+class HelpButton(Gtk.ToolItem):
+
+def __init__(self, **kwargs):
+GObject.GObject.__init__(self)
+
+help_button = ToolButton('help-icon')
+help_button.set_tooltip(_('Help'))
+self.add(help_button)
+
+self._palette = help_button.get_palette()
+
+sw = Gtk.ScrolledWindow()
+sw.set_size_request(int(Gdk.Screen.width() / 2.8),
+Gdk.Screen.height() - style.GRID_CELL_SIZE * 3)
+sw.set_policy(Gtk.PolicyType.NEVER, Gtk.PolicyType.AUTOMATIC)
+
+self._max_text_width = int(Gdk.Screen.width() / 3) - 600
+self._vbox = Gtk.VBox()
+self._vbox.set_homogeneous(False)
+
+hbox = Gtk.HBox()
+hbox.pack_start(self._vbox, False, True, 0)
+
+sw.add_with_viewport(hbox)
+
+self._palette.set_content(sw)
+sw.show_all()
+
+help_button.connect('clicked', self.__help_button_clicked_cb)
+
+def __help_button_clicked_cb(self, button):
+self._palette.popup(immediate=True, state=1)
+
+def add_section(self, section_text):
+hbox = Gtk.HBox()
+label = Gtk.Label()
+label.set_use_markup(True)
+label.set_markup('b%s/b' % section_text)
+label.set_line_wrap(True)
+hbox.pack_start(label, False, False, 0)
+hbox.show_all()
+self._vbox.pack_start(hbox, False, False, padding=5)
+
+def add_paragraph(self, text, icon=None):
+hbox = Gtk.HBox()
+label = Gtk.Label(label=text)
+label.set_justify(Gtk.Justification.LEFT)
+label.set_line_wrap(True)
+hbox.pack_start(label, False, False, 0)
+if icon is not None:
+_icon = Icon(icon_name=icon)
+hbox.add(_icon)
+hbox.show_all()
+self._vbox.pack_start(hbox, False, False, padding=5)
diff --git a/icons/help-icon.svg b/icons/help-icon.svg
new file mode 100644
index 000..f6c92bf
--- /dev/null
+++ b/icons/help-icon.svg
@@ -0,0 +1,14 @@
+?xml version=1.0 encoding=UTF-8?
+svg xmlns=http://www.w3.org/2000/svg; version=1.1 width=55px
height=55px
+ path
+
style=fill:none;stroke:#ff;stroke-width:3;stroke-linejoin:round
+ d=M 48,28 A 20,20 0 1 1 8,28 A 20,20 0 1 1 48,28 z/
+ path
+
style=fill:none;stroke:#ff;stroke-width:6;stroke-linecap:round;stroke-linejoin:round
+ d=M 22,20 C 22,20 25,17 29,17 C 33,17 36,19 36,23 C 36,27 31,29
28,29
Re: [Sugar-devel] [DESIGN] Terminal activity, become root functionality issues
I think will be nice have a help button in terminal... I would like to describe the most used and basic Linux commands (such as cd, ls, cp, rm, etc) :-) Regards, aguz El 20/06/2012 12:24, Rafael Ortiz raf...@activitycentral.com escribió: On Wed, Jun 20, 2012 at 9:26 AM, Manuel Quiñones ma...@laptop.org wrote: 2012/6/20 Manuel Quiñones ma...@laptop.org: 2012/6/19 Rafael Ortiz raf...@activitycentral.com: On Tue, Jun 19, 2012 at 7:49 PM, Gary Martin garycmar...@googlemail.com wrote: On 19 Jun 2012, at 23:38, Manuel Quiñones wrote: Forgot to raise this in today's Dev Meeting. Become root presents the following issues. Should we just remove it? What is the gain of having it, isn't just a shortcut for manually writting su? * http://bugs.sugarlabs.org/ticket/3689 * http://bugs.sugarlabs.org/ticket/2756 * http://bugs.sugarlabs.org/ticket/2597 +1 from me at least for removing it. Based on feedback: http://git.sugarlabs.org/terminal/mainline/commit/cba0197dbd7160693d4944734a10ebebc386cafe I see you are just removing commented out lines in this commit? Now I did git pull and I see two commits, one that marks as comments the become root functionality, the other that remove the commented out lines. Strange but.. ok. Do we have the change applied in the gtk3 port already? it's also on the gtk3 port now. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH Terminal] Drag And Drop from Clipboard / Uncomment some lines from Gtk3 Port
Hi. I feel happy about your patch, but I'm getting the same message :( I also tried to comment that method and works perfectly, maybe it was solved in GTK3. Regards, aguz 2012/6/19 S. Daniel Francis fran...@sugarlabs.org 2012/6/19 Manuel Kaufmann humi...@gmail.com On Tue, Jun 19, 2012 at 2:10 PM, Daniel Francis fran...@sugarlabs.org wrote: The port to GTK3 is finished with this patch. Solved the drag and drop clipboard utility. This is really really good to read! There is a problem here, this is what I'm getting when I try to start the Terminal Activity: This is strange, because it's working very well in my computer, I'll try it on my XO. File /home/humitos/Activities/Terminal.activity/terminal.py, line 151, in _update_accelerators self._update_accelerators(child.get_page()) This method is called to solve this bug http://dev.laptop.org/ticket/10930, but I commented this line and the accelerators work perfectly, try to comment the line 121 in terminal.py and tell us. Cheers. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] SimpleGraph rename?
+1 for Charts! 2012/4/30 Manuel Quiñones ma...@laptop.org Hi, SimpleGraph Activity [1] is being considered for inclusion in the activities shipped by olpc. Is the name ok? Some suggest remove the camel case separating the words: Simple Graph. And there is another option, Simple Chart. Or maybe just Graph or Chart? Graph can be used as a verb, and Chart may be more specific? [1] http://wiki.sugarlabs.org/go/Activities/SimpleGraph -- .. manuq .. -- ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Disable the XO keyboard
Hello, I've a XO with a broken keyboard (writes: ] steadily) I have to wait a week to send to fix, and I thought I could connect an external keyboard so I have to disable the internal keyboard... ¿Somebody can help me to disable the XO keyboard? Thanks! Sorry, my English isn't good... ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] RFC:Simple Help widget for activities
Looks great!
Good work :)
El 9 de marzo de 2012 01:36, Manuel Quiñones ma...@laptop.org escribió:
Hi Gonzalo,
El día 7 de marzo de 2012 09:37, Gonzalo Odiard gonz...@laptop.org
escribió:
We receive many times request about adding help in the activities,
and if is true Sugar propose a exploratory approach,
not all the people learn in the same way,
and there are people who prefer a little guidance.
For the development we need a simple api, and easy i18n,
and a non obtrusive experience for the user.
Inspired by the DescriptionItem, I was experimenting with a widget to add
simple help to activities.
This is not:
* A manual
* Lessons
* Tips
Is a short startup help for the activity.
I think tips can be better than direct guidance. Do this, then do
that manner is counterproductive for exploration. Of course tips can
be ordered in a convenient way, is a matter of manners. Would be
better to see each section at once instead of a large scrollable list.
I imagine a slideshow with back/forward buttons.
Also I think visual help can be used instead of text when possible, so
would be great if the widget allows it. Images can be understand by
early children, and are universal, so no need to translate. Of course
a little paragraph below the image can be convenient too.
Here is a mockup I did for the same activity with this ideas:
http://dev.laptop.org/~manuq/simple_help_mock.png
What do people think?
Use only text and the icons already used by the activity.
A example can be seen here:
http://dev.laptop.org/~gonzalo/images/simple_graph_help.png
In the activity we only need do:
helpitem = HelpButton()
toolbar.insert(helpitem, -1)
helpitem.show()
helpitem.add_section(_('Basic usage'))
helpitem.add_paragraph(_('First you need add data to create the
graphic'))
helpitem.add_paragraph(_('You can add data with this button'),
'row-insert')
helpitem.add_paragraph(_('...or remove data with this button'),
'row-remove')
helpitem.add_paragraph(_('To change the graphic title, just change
the
activity title'))
This proposal is late for sugar 0.96, but may be we can try it in one or
two
activities,
and start thinking about this topic.
I really like the help in the Implode activity, but have the following
problems:
* I don't know if apply to other type of activities.
* Is modal
* need a lot of code to implement it.
Comments?
Gonzalo
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
--
.. manuq ..
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
